From: Nathan Lynch <ntl@pobox.com>
To: David Huffman <dhuffman@storix.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel Panic booting cdrom
Date: Fri, 13 Apr 2007 23:45:30 -0500 [thread overview]
Message-ID: <20070414044529.GE6062@localdomain> (raw)
In-Reply-To: <46202254.1090606@storix.com>
Hi David-
David Huffman wrote:
> I created a cdrom (using the same procedure that has been working for
> years), and received a kernel panic when booting a linux system on a
> System i p5 lpar. Here is a section of the boot messages, plus I added
> the output of .registers from OF. Anyone have an idea what could be the
> cause?
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=128 NUMA PSERIES LPAR
> NIP: C00000000012F210 XER: 0000000020000010 LR: C000000000476024
> REGS: c00000007ff5fab0 TRAP: 0380 Not tainted (2.6.5-7.244-pseries64
> SLES9_SP3_BRANCH-200512121832250000)
> MSR: 8000000000009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
> DAR: 0000000000000010, DSISR: 0000000000200000
> TASK: c00000007ff5b440[1] 'swapper' THREAD: c00000007ff5c000 CPU: 0
> GPR00: C000000000476024 C00000007FF5FD30 C00000000071DCC8 C000000000723338
> GPR04: C0000000028CC080 C0000000028CC088 C000000000954C98 C000000002692888
> GPR08: 0000000000000002 0000000000000001 C000000000643160 0000000000000001
> GPR12: 0000000024000042 C000000000491000 0000000000000000 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000000000 0000000000000010 00000000001BB591 0000000001C00000
> GPR24: C000000000491000 C00000000071D008 C00000000048B5F0 C0000000028CC080
> GPR28: 0000000000000000 C000000000723338 C0000000006316D0 C0000000028CC088
> NIP [c00000000012f210] .sysfs_create_link+0x30/0x134
> LR [c000000000476024] .register_cpu+0xc8/0x104
> Call Trace:
> [c00000007ff5fd30] [c0000000002753cc] .sysdev_register+0x98/0x250
> (unreliable)
> [c00000007ff5fdd0] [c000000000476024] .register_cpu+0xc8/0x104
> [c00000007ff5fe70] [c0000000004621dc] .topology_init+0x1b4/0x290
> [c00000007ff5ff00] [c00000000000c654] .init+0x1a0/0x360
> [c00000007ff5ff90] [c000000000017d24] .kernel_thread+0x4c/0x68
> <0>Fatal exception: panic in 5 seconds
>From the full version at http://www.storix.com/p5panic.txt:
Linux version 2.6.5-7.244-pseries64 (geeko@buildhost) (gcc version 3.3.3 (SuSE Linux)) #1 SMP Mon Dec 12 18:32:25 UTC 2005
[boot]0012 Setup Arch
NUMA associativity depth for CPU/Memory: 3
cpu 0 maps to domain 5
cpu 1 maps to domain 5
memory region 0 to 8000000 maps to domain 5
memory region 8000000 to 9000000 maps to domain 5
memory region 9000000 to a000000 maps to domain 5
....
Could you see whether adding numa=off on the kernel command line
helps?
I think it's crashing because kernels this old assume that numa node
numbering as given by firmware begins with 0. This partition has a
single node numbered 5.
next prev parent reply other threads:[~2007-04-14 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-14 0:37 Kernel Panic booting cdrom David Huffman
2007-04-14 4:45 ` Nathan Lynch [this message]
[not found] ` <4623F574.1030804@storix.com>
[not found] ` <20070417054537.GF6062@localdomain>
2007-04-20 21:05 ` David Huffman
2007-04-23 2:10 ` Michael Ellerman
2007-04-23 22:35 ` Linas Vepstas
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=20070414044529.GE6062@localdomain \
--to=ntl@pobox.com \
--cc=dhuffman@storix.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).