From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Alex Chiang <achiang@hp.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: SLUB ia64 linux-next crash bisected to 756dee75
Date: Thu, 14 Jan 2010 21:17:55 +0200 [thread overview]
Message-ID: <84144f021001141117o6271244cmbe9ba790f9616b2c@mail.gmail.com> (raw)
In-Reply-To: <20100114182214.GB4545@ldl.fc.hp.com>
Hi Alex,
On Thu, Jan 14, 2010 at 8:22 PM, Alex Chiang <achiang@hp.com> wrote:
> * Christoph Lameter <cl@linux-foundation.org>:
>> @@ -2086,7 +2086,7 @@ init_kmem_cache_node(struct kmem_cache_n
>> #endif
>> }
>>
>> -static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[SLUB_PAGE_SHIFT]);
>> +static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[KMALLOC_CACHES]);
>>
>> static inline int alloc_kmem_cache_cpus(struct kmem_cache *s, gfp_t flags)
>> {
>>
>
> Sorry, still crashes.
>
> /ac
>
> INIT: version 2.86 booting
> System Boot Control: Running /etc/init.d/boot
> Mounting procfs at /proc done
> Mounting sysfs at /sys done
> Remounting tmpfs at /dev done
> Initializing /dev done
> Mounting devpts at /dev/pts done
> Starting udevd: udevd version 128 started
> done
> Loading drivers, configuring devices: input: Power Button as /class/input/input2
> ACPI: Power Button [PWRB]
> input: Sleep Button as /class/input/input3
> ACPI: Sleep Button [SLPF]
> sd 0:0:6:0: Attached scsi generic sg0 type 0
> scsi 1:0:2:0: Attached scsi generic sg1 type 5
> sd 2:0:6:0: Attached scsi generic sg2 type 0
> sd 4:0:6:0: Attached scsi generic sg3 type 0
> scsi 5:0:2:0: Attached scsi generic sg4 type 5
> sd 6:0:6:0: Attached scsi generic sg5 type 0
> Unable to handle kernel paging request at virtual address a07ffffe5a7838a8
> modprobe[6234]: Oops 8813272891392 [1]
> Modules linked in: sr_mod(+) sg button container(+) usbhid ohci_hcd ehci_hcd usbcore fan thermal processor thermal_sys
>
> Pid: 6234, CPU 14, comm: modprobe
> psr : 0000101008526030 ifs : 8000000000000b1d ip : [<a0000001001a9ca0>] Not tainted (2.6.33-rc3-next-20100111-dirty)
> ip is at kmem_cache_open+0x420/0xb20
I don't speak ia-64 so I'm having difficulties figuring out where
exactly it's crashing. Can you use addr2line or similar tool to show
us the exact location of the oops?
> unat: 0000000000000000 pfs : 0000000000000b1d rsc : 0000000000000003
> rnat: 0000000000000000 bsps: 0000000000000000 pr : aa99aaa6aa566659
> ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
> csd : 0000000000000000 ssd : 0000000000000000
> b0 : a0000001001a99c0 b6 : a00000010035db20 b7 : a000000100087640
> f6 : 0fff5fffffffff0000000 f7 : 0ffeb8000000000000000
> f8 : 1000f8000000000000000 f9 : 100088000000000000000
> f10 : 10005fffffffff0000000 f11 : 1003e0000000000000080
> r1 : a000000101447ff0 r2 : 0000000000010007 r3 : 0000000000080800
> r8 : 0000000000000001 r9 : a0000001010375f8 r10 : 0000000000000000
> r11 : a000000101265d58 r12 : e000078627dffdf0 r13 : e000078627df0000
> r14 : 0000000000000009 r15 : a000000101037668 r16 : 0000000040004000
> r17 : 0000000000000009 r18 : 0000000000000fff r19 : 0000000000000000
> r20 : a000000101037658 r21 : 00000000000003ff r22 : 0000000000003fff
> r23 : 0000000000003fff r24 : 00000000000017ff r25 : 0000000000002fff
> r26 : a000000101037604 r27 : a000000101037600 r28 : a0000001010396e8
> r29 : a000000101037610 r30 : 0000000000000080 r31 : 0000000000000080
>
> Call Trace:
> [<a000000100016970>] show_stack+0x50/0xa0
> sp=e000078627dff9c0 bsp=e000078627df14b8
> [<a0000001000171e0>] show_regs+0x820/0x860
> sp=e000078627dffb90 bsp=e000078627df1460
> [<a00000010003bc60>] die+0x1a0/0x300
> sp=e000078627dffb90 bsp=e000078627df1420
> [<a0000001000688c0>] ia64_do_page_fault+0x8c0/0x9e0
> sp=e000078627dffb90 bsp=e000078627df13c8
> [<a00000010000c8a0>] ia64_native_leave_kernel+0x0/0x270
> sp=e000078627dffc20 bsp=e000078627df13c8
> [<a0000001001a9ca0>] kmem_cache_open+0x420/0xb20
> sp=e000078627dffdf0 bsp=e000078627df12e0
> [<a0000001001aabb0>] dma_kmalloc_cache+0x2d0/0x440
> sp=e000078627dffdf0 bsp=e000078627df1290
> [<a0000001001aae30>] get_slab+0x110/0x1a0
> sp=e000078627dffdf0 bsp=e000078627df1268
> [<a0000001001ab600>] __kmalloc+0xa0/0x260
> sp=e000078627dffdf0 bsp=e000078627df1230
> [<a000000207dd16d0>] sr_probe+0x3b0/0xf20 [sr_mod]
> sp=e000078627dffdf0 bsp=e000078627df11c8
> [<a000000100481720>] driver_probe_device+0x180/0x300
> sp=e000078627dffe20 bsp=e000078627df1190
> [<a000000100481980>] __driver_attach+0xe0/0x140
> sp=e000078627dffe20 bsp=e000078627df1160
> [<a000000100480380>] bus_for_each_dev+0xa0/0x140
> sp=e000078627dffe20 bsp=e000078627df1128
> [<a000000100481340>] driver_attach+0x40/0x60
> sp=e000078627dffe30 bsp=e000078627df1108
> [<a00000010047f1a0>] bus_add_driver+0x180/0x520
> sp=e000078627dffe30 bsp=e000078627df10c0
> [<a000000100482140>] driver_register+0x260/0x400
> sp=e000078627dffe30 bsp=e000078627df1078
> [<a0000001004d5f40>] scsi_register_driver+0x40/0x60
> sp=e000078627dffe30 bsp=e000078627df1058
> [<a000000207e00070>] init_sr+0x70/0x140 [sr_mod]
> sp=e000078627dffe30 bsp=e000078627df1038
> [<a00000010000a960>] do_one_initcall+0xe0/0x360
> sp=e000078627dffe30 bsp=e000078627df0ff0
> [<a000000100105ec0>] sys_init_module+0x1e0/0x4c0
> sp=e000078627dffe30 bsp=e000078627df0f78
> [<a00000010000c700>] ia64_ret_from_syscall+0x0/0x20
> sp=e000078627dffe30 bsp=e000078627df0f78
> [<a000000000010720>] __kernel_syscall_via_break+0x0/0x20
> sp=e000078627e00000 bsp=e000078627df0f78
> Disabling lock debugging due to kernel taint
> udevd-event[6232]: '/sbin/modprobe' abnormal exit
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-14 19:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 0:29 SLUB ia64 linux-next crash bisected to 756dee75 Alex Chiang
2010-01-13 14:59 ` Christoph Lameter
2010-01-14 0:53 ` Alex Chiang
2010-01-14 15:01 ` Christoph Lameter
2010-01-14 18:01 ` Alex Chiang
2010-01-14 15:18 ` Christoph Lameter
2010-01-14 18:22 ` Alex Chiang
2010-01-14 19:17 ` Pekka Enberg [this message]
2010-01-14 20:32 ` Alex Chiang
2010-01-14 20:58 ` Christoph Lameter
2010-01-14 21:29 ` Alex Chiang
2010-01-14 21:31 ` Pekka Enberg
2010-01-14 21:59 ` Christoph Lameter
2010-01-14 22:01 ` Christoph Lameter
2010-01-15 20:07 ` Christoph Lameter
2010-01-15 20:35 ` Lee Schermerhorn
2010-01-15 23:32 ` Christoph Lameter
2010-01-19 18:53 ` Christoph Lameter
2010-01-19 20:02 ` Alex Chiang
2010-01-19 20:29 ` Christoph Lameter
2010-01-19 21:29 ` Alex Chiang
2010-01-19 21:50 ` Christoph Lameter
2010-01-20 22:46 ` Alex Chiang
2010-01-21 21:47 ` Alex Chiang
2010-01-21 22:45 ` Christoph Lameter
2010-01-21 23:05 ` Alex Chiang
2010-01-21 23:43 ` Christoph Lameter
2010-01-22 0:15 ` Alex Chiang
2010-01-22 14:43 ` Christoph Lameter
2010-01-22 16:37 ` Pekka Enberg
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=84144f021001141117o6271244cmbe9ba790f9616b2c@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=achiang@hp.com \
--cc=cl@linux-foundation.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.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).