From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: recent -git: BUG in free_thread_xstate
Date: Wed, 23 Jul 2008 13:31:09 -0700 [thread overview]
Message-ID: <20080723203109.GH14380@linux-os.sc.intel.com> (raw)
In-Reply-To: <19f34abd0807231307y191c0ad7tfab4cda57ee88eb@mail.gmail.com>
On Wed, Jul 23, 2008 at 01:07:04PM -0700, Vegard Nossum wrote:
> Hi,
>
> I just got this on c010b2f76c3032e48097a6eef291d8593d5d79a6 (-git from
> yesterday):
Do you see this in 2.6.26 aswell? I suspect it is coming from post 2.6.26
changes.
>
> BUG: unable to handle kernel paging request at 00664381
> IP: [<c010b274>] free_thread_xstate+0x4/0x30
...
> EIP is at arch/x86/kernel/process.c:36:
>
> if (tsk->thread.xstate) {
>
It looks like the kernel stack of that process got corrupted, corrupting the
task pointer in thread_info. Can you send us your config file?
thanks,
suresh
next prev parent reply other threads:[~2008-07-23 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 20:07 recent -git: BUG in free_thread_xstate 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 [this message]
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
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=20080723203109.GH14380@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=vegard.nossum@gmail.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