[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0808200912y3f9cd132hee6cd7ea9852d112@mail.gmail.com>
Date: Wed, 20 Aug 2008 18:12:28 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Yinghai Lu" <yhlu.kernel@...il.com>,
"the arch/x86 maintainers" <x86@...nel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: latest -git: BUG: unable to handle kernel paging request (numaq_tsc_disable)
On Wed, Aug 20, 2008 at 5:40 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> On Wed, Aug 20, 2008 at 5:28 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
>> Hi,
>>
>> This actually hardlocked my machine and I had to add an extra patch to
>> get any output at all. Base version is latest git, commit
>> 1fca25427482387689fa27594c992a961d98768f.
>>
>
> ...
>
>> Booting processor 1/1 ip 6000
>> <1>BUG: unable to handle kernel paging request at c08a45f0
>> <1>IP: [<c08a45f0>] numaq_tsc_disable+0x0/0x40
>> <0> [<c0678676>] ? init_intel+0x196/0x360
>
> Seems to be a section mismatch; init_intel() is __cpuinit while
> numaq_tsc_disable() is __init. Seems to be introduced in:
>
> commit 64898a8bad8c94ad7a4bd5cc86b66edfbb081f4a
> Author: Yinghai Lu <yhlu.kernel@...il.com>
> Date: Sat Jul 19 18:01:16 2008 -0700
>
> x86: extend and use x86_quirks to clean up NUMAQ code
Oops, I am wrong about numaq_tsc_disable() being __init. Still, I
believe that Yinghai might be able to say what's really wrong :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists