LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Dmitry <dbaryshkov@gmail.com>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>,
	Dirk@opfer-online.de, arminlitzel@web.de, pavel.urban@ct.cz,
	Cyril Hrubis <metan@ucw.cz>,
	thommycheck@gmail.com
Subject: Re: 2.6.28-rc3-git1: spitz still won't boot
Date: Wed, 5 Nov 2008 18:33:03 +0100	[thread overview]
Message-ID: <20081105173303.GC2038@elf.ucw.cz> (raw)
In-Reply-To: <bc64b4640811050713i4cfb1216x822274150e929e02@mail.gmail.com>

On Wed 2008-11-05 18:13:19, Dmitry wrote:
> 2008/11/5 Pavel Machek <pavel@suse.cz>:
> > On Fri 2008-10-31 16:06:01, Pavel Machek wrote:
> >> Hi!
> >>
> >> ...unfortunately, 2.6.27 contains the 'reset floating' bug, and from
> >> the point 'reset floating' is fixed, to 2.6.28-rc1, tree will not
> >> compile, so bisect is quite hard to do. Any ideas?
> >
> > It is still there in -rc3... And yes, it is a regression from 2.6.27.
> 
> Would you be so nice to provide a boot log of 2.6.28-rc3 with
> CONFIG_DEBUG_DRIVER enabled?

I'd love to, but it fails with black screen :-(. (But I guess I should
mention that I'm using kexec...)

Do you have "good" config for spitz I could try? (Similar
configuration worked in 2.6.27, but maybe it is a config difference?)

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2008-11-05 17:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 15:06 2.6.28-rc2-git1: spitz still won't boot Pavel Machek
2008-10-31 21:55 ` Rafael J. Wysocki
2008-11-03 10:40   ` Pavel Machek
2008-11-03 11:04     ` Russell King
2008-11-03 11:12       ` Pavel Machek
2008-11-05 14:23 ` 2.6.28-rc3-git1: " Pavel Machek
2008-11-05 15:13   ` Dmitry
2008-11-05 17:33     ` Pavel Machek [this message]
2008-11-05 23:00       ` Dmitry
2008-11-06  8:04         ` Pavel Machek
2008-11-06 19:14           ` Cyril Hrubis
2008-11-07 13:23             ` Eric Miao
2008-11-07 14:29               ` Pavel Machek
2008-11-07 14:57                 ` Dmitry
2008-11-07 18:23                   ` Russell King
2008-11-08 14:45                     ` Richard Purdie
2008-11-08 23:12                       ` Dmitry
2008-11-08 23:21                         ` Russell King
2008-11-08 23:25                           ` Dmitry
2008-11-08 23:28                             ` Russell King
2008-11-09 11:45                   ` Pavel Machek
2008-11-09 11:46                     ` Pavel Machek
2008-11-09 12:30                       ` Dmitry
2008-11-09 14:12                         ` Pavel Machek
2008-11-09 14:52                           ` Dmitry
2008-11-10  7:50                         ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081105173303.GC2038@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Dirk@opfer-online.de \
    --cc=arminlitzel@web.de \
    --cc=dbaryshkov@gmail.com \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metan@ucw.cz \
    --cc=pavel.urban@ct.cz \
    --cc=rmk@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    --cc=thommycheck@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).