Messages in this thread | | | Date | Wed, 20 Aug 2008 18:18:26 +0200 | From | "Vegard Nossum" <> | Subject | Re: latest -git: BUG: unable to handle kernel paging request (numaq_tsc_disable) |
| |
On Wed, Aug 20, 2008 at 6:12 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote: > On Wed, Aug 20, 2008 at 5:40 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote: >> On Wed, Aug 20, 2008 at 5:28 PM, Vegard Nossum <vegard.nossum@gmail.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@gmail.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 :-)
Err... No, I am confusing myself! I had already applied a patch to change it to __cpuinit :-/
The good news is that the bug is now fixed. Patch attached.
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 [unhandled content-type:application/octet-stream] | |