From: Michael Ellerman <michael@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: "test" branch update
Date: Mon, 27 Jul 2009 18:45:50 +1000 [thread overview]
Message-ID: <1248684350.4691.19.camel@concordia> (raw)
In-Reply-To: <1248668057.5706.2.camel@pasglop>
[-- Attachment #1: Type: text/plain, Size: 2679 bytes --]
On Mon, 2009-07-27 at 14:14 +1000, Benjamin Herrenschmidt wrote:
> Hi !
>
> I've started collecting things for my -next branch. For now I put
> everything in -test, I'll move it over to -next in the upcoming couple
> of days if there's no major issue found.
I'm seeing this on Power 6 (Didgo3), haven't had a chance to look any
closer, 100% reproducible, using SLUB.
HugeTLB registered 16 MB page size, pre-allocated 0 pages
HugeTLB registered 16 GB page size, pre-allocated 0 pages
HugeTLB registered 64 KB page size, pre-allocated 0 pages
Unable to handle kernel paging request for data at address 0x00000000
Faulting instruction address: 0xc00000000003ea98
cpu 0x0: Vector: 300 (Data Access) at [c0000000fe6e3840]
pc: c00000000003ea98: .strcmp+0x10/0x24
lr: c0000000001c8e60: .sysfs_find_dirent+0x3c/0x78
sp: c0000000fe6e3ac0
msr: 8000000000009032
dar: 0
dsisr: 40000000
current = 0xc0000000fe6d8000
paca = 0xc000000000ab3200
pid = 1, comm = swapper
enter ? for help
[link register ] c0000000001c8e60 .sysfs_find_dirent+0x3c/0x78
[c0000000fe6e3ac0] c0000000001c939c .sysfs_addrm_start+0x70/0xec
(unreliable)
[c0000000fe6e3b50] c0000000001c6f50 .sysfs_hash_and_remove+0x58/0xb0
[c0000000fe6e3c10] c0000000001ca8a4 .sysfs_remove_link+0x4c/0x6c
[c0000000fe6e3cb0] c00000000014612c .sysfs_slab_alias+0x64/0x154
[c0000000fe6e3d60] c00000000090e22c .slab_sysfs_init+0xd4/0x130
[c0000000fe6e3e00] c000000000009848 .do_one_initcall+0x90/0x1b8
[c0000000fe6e3ef0] c0000000008ef4c0 .kernel_init+0x1f8/0x278
[c0000000fe6e3f90] c00000000002f570 .kernel_thread+0x54/0x70
0:mon> r
R00 = c0000000001c6f50 R16 = 0000000000000000
R01 = c0000000fe6e3ac0 R17 = 0000000004d2dbb8
R02 = c000000000a72248 R18 = c00000000092da50
R03 = 0000000000000073 R19 = 0000000000000000
R04 = ffffffffffffffff R20 = 0000000002f1fed0
R05 = c0000000feb70460 R21 = 0000000004d2da78
R06 = c0000000fec19640 R22 = 0000000004400000
R07 = 0000000000000001 R23 = c00000000092da48
R08 = ffffffffffffffff R24 = c00000000092da58
R09 = c000000000bd6080 R25 = 00000000010ad378
R10 = 0000000000000816 R26 = c000000000aa7ac0
R11 = 0000000000000012 R27 = 0000000000000000
R12 = 0000000024000084 R28 = 0000000000000000
R13 = c000000000ab3200 R29 = c0000000fec19690
R14 = 0000000000000000 R30 = c0000000009ddd98
R15 = 0000000000000000 R31 = c0000000fe6e3ac0
pc = c00000000003ea98 .strcmp+0x10/0x24
lr = c0000000001c8e60 .sysfs_find_dirent+0x3c/0x78
msr = 8000000000009032 cr = 24000048
ctr = 0000000000000000 xer = 000000002000000b trap = 300
dar = 0000000000000000 dsisr = 40000000
0:mon>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-27 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 4:14 "test" branch update Benjamin Herrenschmidt
2009-07-27 8:45 ` Michael Ellerman [this message]
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=1248684350.4691.19.camel@concordia \
--to=michael@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--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).