From: Bjorn Helgaas <bhelgaas@google.com>
To: NeilBrown <neilb@suse.de>
Cc: Chris Jones <chrisjones@spin.net.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.1+ kernels unbootable
Date: Wed, 25 Apr 2012 09:34:23 -0600 [thread overview]
Message-ID: <CAErSpo7KCJ8osWUH_TLc9adwfjLkqgQbUer6wouT09XFYH3=Zg@mail.gmail.com> (raw)
In-Reply-To: <20120425144452.32a803fe@notabene.brown>
You might be seeing nothing because of the distro splash screen, so
you could try removing any boot options like "silent splash quiet
rhgb" and adding "debug ignore_loglevel" and maybe "vga=0xf07" (to get
more text on the screen). If you learn anything that way, maybe you
could collect a dmesg log from the newest working kernel and a digital
photo of the broken one for comparison.
Bjorn
next prev parent reply other threads:[~2012-04-25 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 2:49 3.1+ kernels unbootable Chris Jones
2012-04-25 3:21 ` NeilBrown
2012-04-25 4:20 ` Chris Jones
2012-04-25 4:44 ` NeilBrown
2012-04-25 15:34 ` Bjorn Helgaas [this message]
2012-04-29 2:21 ` Chris Jones
2012-05-21 21:40 ` Bjorn Helgaas
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='CAErSpo7KCJ8osWUH_TLc9adwfjLkqgQbUer6wouT09XFYH3=Zg@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=chrisjones@spin.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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).