From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Donald Parsons <dparsons@brightdsl.net>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 2.6.35
Date: Sun, 1 Aug 2010 21:38:38 -0600 [thread overview]
Message-ID: <201008012138.39036.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <1280716262.5125.42.camel@falcon.homelinux.org>
On Sunday, August 01, 2010 08:31:02 pm Donald Parsons wrote:
> 2.6.35 still fails to boot for me, as first reported here:
> http://lkml.indiana.edu/hypermail/linux/kernel/1007.3/01144.html
>
> I've manually bisected it down to around May 20 between
> 2.6.34-git4 (boots) and 2.6.34-git5 (boot fails)
> Also -git[23] boot, and -git8, -rc[126], rc6-git[136] all fail.
>
> Unfortunately first time I tried was with 2.6.35-rc6 and
> it failed to boot.
>
> Failure when switching from initramfs to real /root?
> Removing kernel "quiet" param appears to show several
> lines listing:
>
> usb drives/hubs? followed by
> dracut switching root (when booting works)
> or
> usb drives/hubs? followed by
> (missing dracut... line)
> No root device found
> Boot has failed, sleeping forever. (when it does not boot)
>
> Grub, typical entry:
> title Fedora (2.6.35)
> root (hd0,0)
> kernel /vmlinuz-2.6.35 ro
> root=UUID=686dc496-8814-4c36-8fb7-5ded2916e825 rhgb
> SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
> rdblacklist=nouveau init=/sbin/bootchartd
> initrd /initramfs-2.6.35.img
>
>
> My boot failure seems to be different than other two reported
> in the thread "2.6.35-rc6-git6: Reported regressions from 2.6.34"
> under Bug #16173 and #16228
Will it boot with the "pci=nocrs" option? If so, please open a
report at https://bugzilla.kernel.org, mark it a regression, assign
it to me, and attach the complete dmesg log. And please respond to
this thread with a pointer to the bugzilla.
Otherwise, a complete console log should have a clue. The best
thing would be a log from a serial console or netconsole, with
"ignore_loglevel".
Thanks a lot for your report!
Bjorn
next prev parent reply other threads:[~2010-08-02 3:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 2:31 Donald Parsons
2010-08-02 3:28 ` Randy Dunlap
2010-08-02 3:38 ` Bjorn Helgaas [this message]
2010-08-02 4:21 ` Donald Parsons
2010-08-02 13:48 ` Bjorn Helgaas
2010-08-02 15:59 ` Harald Hoyer
2010-08-02 22:09 ` Frédéric L. W. Meunier
2010-08-02 22:34 ` Frédéric L. W. Meunier
2010-08-02 18:38 ` Donald Parsons
2010-08-02 16:08 ` Harald Hoyer
2010-08-03 2:31 ` Donald Parsons
2010-08-03 4:42 ` Randy Dunlap
2010-08-03 10:24 ` Stefan Richter
2010-08-03 18:26 ` Donald Parsons
2010-08-03 16:26 ` Donald Parsons
2010-08-03 16:40 ` Randy Dunlap
2010-08-03 17:45 ` Donald Parsons
2010-08-03 18:35 ` Randy Dunlap
2010-08-03 22:34 ` Randy Dunlap
2010-08-04 20:15 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2010-08-01 23:52 Linus Torvalds
2010-08-02 0:32 ` Stephen Rothwell
2010-08-02 8:14 ` Nick Piggin
2010-08-02 8:52 ` Stephen Rothwell
2010-08-02 2:33 ` Dave Chinner
2010-08-02 2:50 ` Linus Torvalds
2010-08-02 5:58 ` Dave Chinner
2010-08-02 7:55 ` Nick Piggin
2010-08-02 8:24 ` Christoph Hellwig
2010-08-02 8:46 ` KOSAKI Motohiro
2010-08-02 9:05 ` Christoph Hellwig
2010-08-02 10:07 ` Nick Piggin
2010-08-02 9:51 ` Nick Piggin
2010-08-03 8:18 ` Andi Kleen
2010-08-03 9:28 ` Nick Piggin
2010-08-03 9:49 ` Andi Kleen
2010-08-03 15:05 ` Henrique de Moraes Holschuh
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=201008012138.39036.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=dparsons@brightdsl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®