From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>,
"the arch/x86 maintainers" <x86@kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: latest -git: BUG: unable to handle kernel paging request (numaq_tsc_disable)
Date: Wed, 20 Aug 2008 18:12:28 +0200 [thread overview]
Message-ID: <19f34abd0808200912y3f9cd132hee6cd7ea9852d112@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0808200840v17a8e5d4ge60c332f864abd81@mail.gmail.com>
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 :-)
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
next prev parent reply other threads:[~2008-08-20 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 15:28 Vegard Nossum
2008-08-20 15:40 ` Vegard Nossum
2008-08-20 16:12 ` Vegard Nossum [this message]
2008-08-20 16:18 ` Vegard Nossum
2008-08-21 10:52 ` Ingo Molnar
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=19f34abd0808200912y3f9cd132hee6cd7ea9852d112@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®