From: Andrew Morton <akpm@linux-foundation.org>
To: Mikko Rapeli <mikko.rapeli@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: early boot lockup with 2.6.23-rc1
Date: Wed, 8 Aug 2007 22:09:18 -0700 [thread overview]
Message-ID: <20070808220918.1e5de16f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070809045743.GA2342@nalle>
On Thu, 9 Aug 2007 07:57:43 +0300 Mikko Rapeli <mikko.rapeli@iki.fi> wrote:
> On Wed, Aug 08, 2007 at 05:02:11PM -0700, Andrew Morton wrote:
> > On Thu, 9 Aug 2007 01:31:20 +0300
> > Mikko Rapeli <mikko.rapeli@iki.fi> wrote:
> >
> > > Since 2.6.23-rc1 I can't boot an old k6 (with a funky IDE drive worth testing
> > > with libata). The boot hangs without a sound or letter prints on the
> > > screen right after grub, while 2.6.22.1 works fine.
> >
> > Try adding the `earlyprintk=vga' parameter to the kernel command line?
>
> Tried but didn't see anything.
So it died super-early.
> I'll try some git snapshots...
That would be good, thanks.
Often such an early crash is due to a config problem. eg: chose the
wrong CPU type. So I'd recommend that you triple-check that config,
especially under "Processor type and features" before diving into into the
bisection hunt.
next prev parent reply other threads:[~2007-08-09 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:31 early boot lockup with 2.6.23-rc1 Mikko Rapeli
2007-08-09 0:02 ` Andrew Morton
2007-08-09 4:57 ` Mikko Rapeli
2007-08-09 5:09 ` Andrew Morton [this message]
2007-08-09 5:24 ` Mikko Rapeli
2007-08-09 7:25 ` H. Peter Anvin
2007-08-09 7:53 ` Mikko Rapeli
2007-08-09 18:23 ` Mikko Rapeli
2007-08-09 19:43 ` Mikko Rapeli
2007-08-09 22:26 ` H. Peter Anvin
2007-08-10 16:33 ` Mikko Rapeli
2007-08-10 16:45 ` H. Peter Anvin
2007-08-10 19:20 ` Mikko Rapeli
2007-08-10 19:32 ` H. Peter Anvin
2007-08-10 19:50 ` Mikko Rapeli
2007-08-10 22:38 ` Mikko Rapeli
2007-08-10 22:50 ` H. Peter Anvin
2007-08-11 4:42 ` Mikko Rapeli
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=20070808220918.1e5de16f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.rapeli@iki.fi \
/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