[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.00.0909142147220.30373@chino.kir.corp.google.com>
Date: Mon, 14 Sep 2009 21:59:12 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Suresh Jayaram <sureshjayaram@...il.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Jin Dongming <jin.dongming@...css.fujitsu.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: mmotm 2009-09-09-22-56 uploaded
On Mon, 14 Sep 2009, Suresh Jayaram wrote:
> Hi Andrew,
>
> On Thu, Sep 10, 2009 at 11:31 AM, <akpm@...ux-foundation.org> wrote:
> >
> > The mm-of-the-moment snapshot 2009-09-09-22-56 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
> >
> > git://git.zen-sources.org/zen/mmotm.git
> >
>
> The current mmotm doesn't boot my T60p. It hangs (hardlock) very early
> during the boot after Uncompressing the kernel image. The last message
> I see on the screen is
>
> "Probing EDD (edd=off to disable)...
>
> Trying with edd=off didn't help. Other commandline options that didn't
> help include (acpi=off, noapic,nolapic,pci=no). It appears that it
> hardlocks during hardware detection.
>
> Attached is my kernel config:
>
There're a couple of known problems in booting the latest mmotm,
2009-09-14-01-57, on T60p.
The first is passing a NULL pointer to a workqueue from
clocksource_mark_unstable(). This is fixed by reverting 7285dd7
"clocksource: Resolve cpu hotplug dead lock with TSC unstable" from the
x86 timers/core tree; Martin's fix had no affect on this crash.
[ I notice Thomas has since provided patches for this problem, so I'll
check if it solves this issue on T60p. ]
The second is an issue with the i8042 driver's laptop table not being NULL
terminated. This is fixed by Jin Dongming's patch at
http://marc.info/?l=linux-kernel&m=125263897713267.
The config you attached, however, is very different from
mmotm-2009-09-14-01-57, so perhaps try this kernel with the above two
fixes to see if you can successfully boot?
Powered by blists - more mailing lists