mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
Cc: "Suresh Siddha" <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Subject: Re: recent -git: BUG in free_thread_xstate
Date: Thu, 24 Jul 2008 00:05:45 +0200	[thread overview]
Message-ID: <19f34abd0807231505w1a25c2bak329a622f3a287e97@mail.gmail.com> (raw)
In-Reply-To: <b647ffbd0807231501va30f6d4kee49d1daa30227fc@mail.gmail.com>

On Thu, Jul 24, 2008 at 12:01 AM, Dmitry Adamushko
<dmitry.adamushko@gmail.com> wrote:
>> BUG: unable to handle kernel paging request at c0804358
>> IP: [<c057e38d>] schedule+0x1ed/0x850

[...]

> So I guess, 'cpu' value is slightly, well, out of reality. Check the
> address of "runqueues" in your kernel image...
> I guess, it should be quite close to the "fault" address... then we
> can even calculate 'cpu' :-)

Yup, that's right.

$ nm vmlinux | grep runqueues
c0803f00 d per_cpu__runqueues


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

  reply	other threads:[~2008-07-23 22:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 20:07 Vegard Nossum
2008-07-23 20:23 ` Vegard Nossum
2008-07-23 20:28   ` Vegard Nossum
2008-07-23 21:35     ` Vegard Nossum
2008-07-23 20:31 ` Suresh Siddha
2008-07-23 20:39   ` Vegard Nossum
2008-07-23 20:52   ` Vegard Nossum
2008-07-23 21:22     ` Dmitry Adamushko
2008-07-23 21:35       ` Dmitry Adamushko
2008-07-23 21:45         ` Vegard Nossum
2008-07-23 22:01           ` Dmitry Adamushko
2008-07-23 22:05             ` Vegard Nossum [this message]
2008-07-23 22:45               ` Vegard Nossum
2008-07-23 22:50                 ` Vegard Nossum
2008-07-23 23:20                   ` Vegard Nossum
2008-07-23 23:53                     ` Matt Mackall
2008-07-24  0:02                       ` Vegard Nossum
2008-07-23 21:22   ` Vegard Nossum
2008-07-23 22:42     ` Max Krasnyansky
2008-08-01 21:10   ` Paul E. McKenney
2008-08-08 18:46     ` Vegard Nossum
2008-08-08 20:40       ` Paul E. McKenney

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=19f34abd0807231505w1a25c2bak329a622f3a287e97@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=x86@kernel.org \
    /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®