linux-kernel - Re: latest -git: BUG: unable to handle kernel paging request (numaq_tsc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0808200918n54aba154ta3c06dd7fbdf383f@mail.gmail.com>
Date:	Wed, 20 Aug 2008 18:18:26 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>,
	"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 6:12 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> 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 :-)

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

Download attachment "0001-x86-numaq-fix-section-mismatch.patch" of type "application/octet-stream" (890 bytes)