From: Lee Schermerhorn <lee.schermerhorn@hp.com>
To: linux-ia64 <linux-ia64@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>
Subject: Unable to handle kernel paging request in 2.6.16-rc1-mm4
Date: Wed, 01 Feb 2006 15:20:07 +0000 [thread overview]
Message-ID: <1138807207.5211.39.camel@localhost.localdomain> (raw)
Just a "heads up" because I haven't found reference to this in the ia64
nor kernel lists. Maybe just happens on my platform?
I'm seeing this on an HP rx8620 [16xIA64, 4 NUMA nodes, 32GB], booting
subject kernel. Log excerpts:
---
Unable to handle kernel paging request at virtual address
a004037b4dc28110
events/12[62]: Oops 11012296146944 [1]
<snip>
Call Trace:
<snip>
[<a00000010000cca0>] ia64_leave_kernel+0x0/0x280
spà000721fe84fb80 bspà000721fe849290
[<a0000001001483b0>] free_block+0x90/0x360
spà000721fe84fd50 bspà000721fe849200
[<a0000001001489d0>] drain_array_locked+0x110/0x180
spà000721fe84fd50 bspà000721fe8491b8
[<a00000010014e6c0>] cache_reap+0x1a0/0x600
spà000721fe84fd50 bspà000721fe849140
[<a0000001000c61c0>] run_workqueue+0x180/0x2c0
spà000721fe84fd60 bspà000721fe8490f0
[<a0000001000c6540>] worker_thread+0x240/0x2c0
spà000721fe84fd60 bspà000721fe8490b8
<snip>
BUG: events/12/62, lock held at task exit time!
[a000000100867fe0] {cache_chain_mutex}
.. held by: events/12: 62 [e0000721fe848000, 110]
... acquired at: cache_reap+0x30/0x600
---
Eventually the boot hangs...
I did a bisection search of the mm4 broken out patches and isolated the
problem to the "export-cpu-topology-by-sysfs" patches. I.e., if I
comment these out, builds and boots fine [with a one-liner build fix
from Christoph Lameter for an SGI sn pci source file]. Something
overstepping a slab allocation? Still investigating.
Regards,
Lee
reply other threads:[~2006-02-01 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1138807207.5211.39.camel@localhost.localdomain \
--to=lee.schermerhorn@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin.zhang@intel.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