2.6.17-mm1
On 16x NUMA-Q, got a panic running dbench across different fs's.
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c0154030 *pde = 2589f001 *pte = 00000000 Oops: 0000 [#1] 8K_STACKS SMP last sysfs file: /devices/pci0000:00/0000:00:0a.0/resource Modules linked in: CPU: 1 EIP: 0060:[<c0154030>] Not tainted VLI EFLAGS: 00010006 (2.6.17-mm1-autokern1 #1)
EIP is at s_show+0xe5/0x28e
eax: c038efe0 ebx: e744ef60 ecx: 00000000 edx: 00000000
esi: c038efe0 edi: 00000000 ebp: e744b2c0 esp: e67aff14
ds: 007b es: 007b ss: 0068
Process cp (pid: 7295, ti=e67ae000 task=e1521570 task.ti=e67ae000)
Stack: 00000000 00000000 00000000 00000072 00000c66 e64a78c0 e744b2c0 00000000
00001000 c01724e5 e64a78c0 e744b2c0 0000087e 00000000 0000005c
00000000
0000005b 00000000 e6754720 bfc8afa0 e67affa4 00001000 c0156e80
e6754720
Call Trace:
[<c01724e5>] seq_read+0x195/0x262
[<c0156e80>] vfs_read+0x88/0x11e
[<c0157160>] sys_read+0x3b/0x63
[<c036d07f>] syscall_call+0x7/0xb
Code: 10 3b 8d d4 00 00 00 75 0a 85 f6 b8 a0 ef 38 c0 0f 44 f0 85 c9 75 0a 85 f6 b8 e0 ef 38 c0 0f 44 f0 01 4c 24 10 ff 44 24 0c 8b 12 <8b> 02 0f 18 00 90 39 da 75 c9 8b 53 10 8b 02 0f 18 00 90 8d 43
EIP: [<c0154030>] s_show+0xe5/0x28e SS:ESP 0068:e67aff14Got a very similar panic on a flat SMP box too:
BUG: unable to handle kernel paging request at virtual address 00100100 printing eip: c0154030 *pde = 2f2fa001 *pte = 00000000 Oops: 0000 [#1] 8K_STACKS SMP last sysfs file: /devices/pci0000:00/0000:00:0a.0/resource Modules linked in: CPU: 1 EIP: 0060:[<c0154030>] Not tainted VLI EFLAGS: 00010006 (2.6.17-mm1-autokern1 #1)
EIP is at s_show+0xe5/0x28e
eax: c038efe0 ebx: dffead60 ecx: 00000000 edx: 00100100
esi: c038efe0 edi: 00000000 ebp: dffe7660 esp: f69a7f14
ds: 007b es: 007b ss: 0068
Process cp (pid: 7190, ti=f69a6000 task=f64dc570 task.ti=f69a6000)
Stack: 00000000 00000000 00000000 0000003f 00000328 f650a620 dffe7660 00000000
00001000 c01724e5 f650a620 dffe7660 00000909 00000000 0000005d
00000000
0000005c 00000000 ed4d3200 bff47a70 f69a7fa4 00001000 c0156e80
ed4d3200
Call Trace:
[<c01724e5>] seq_read+0x195/0x262
[<c0156e80>] vfs_read+0x88/0x11e
[<c0157160>] sys_read+0x3b/0x63
[<c036d07f>] syscall_call+0x7/0xb
Code: 10 3b 8d d4 00 00 00 75 0a 85 f6 b8 a0 ef 38 c0 0f 44 f0 85 c9 75 0a 85 f6 b8 e0 ef 38 c0 0f 44 f0 01 4c 24 10 ff 44 24 0c 8b 12 <8b> 02 8d 74 26 00 39 da 75 c9 8b 53 10 8b 02 8d 74 26 00 8d 43
EIP: [<c0154030>] s_show+0xe5/0x28e SS:ESP 0068:f69a7f14Quoted 33 lines · On Fri, 23 Jun 2006 12:23:54 -0700 Martin Bligh <[email protected]> wrote:
On 16x NUMA-Q, got a panic running dbench across different fs's.
BUG: unable to handle kernel NULL pointer dereference at virtual address00000000
printing eip:c0154030
*pde =2589f001
*pte = 00000000Oops: 0000 [#1] 8K_STACKS SMP last sysfs file: /devices/pci0000:00/0000:00:0a.0/resource Modules linked in: CPU: 1 EIP: 0060:[<c0154030>] Not tainted VLI EFLAGS: 00010006 (2.6.17-mm1-autokern1 #1)EIP is at
s_show+0xe5/0x28e
eax:c038efe0ebx:e744ef60ecx: 00000000 edx: 00000000
esi:c038efe0edi: 00000000 ebp:e744b2c0esp:e67aff14
ds: 007b es: 007b ss: 0068
Process cp (pid: 7295, ti=e67ae000 task=e1521570 task.ti=e67ae000)Stack: 00000000 00000000 00000000 00000072 00000c66 e64a78c0 e744b2c0 00000000 00001000 c01724e5 e64a78c0 e744b2c0 0000087e 00000000 0000005c 00000000 0000005b 00000000 e6754720 bfc8afa0 e67affa4 00001000 c0156e80 e6754720 Call Trace: [<c01724e5>] seq_read+0x195/0x262 [<c0156e80>] vfs_read+0x88/0x11e [<c0157160>] sys_read+0x3b/0x63 [<c036d07f>] syscall_call+0x7/0xb Code: 10 3b 8d d4 00 00 00 75 0a 85 f6 b8 a0 ef 38 c0 0f 44 f0 85 c9 75
Quoted 3 lines
0a 85 f6 b8 e0 ef 38 c0 0f 44 f0 01 4c 24 10 ff 44 24 0c 8b 12 <8b> 02 0f 18 00 90 39 da 75 c9 8b 53 10 8b 02 0f 18 00 90 8d 43
EIP: [<c0154030>]s_show+0xe5/0x28eSS:ESP 0068:e67aff14
That's a null-pointer deref
Quoted 31 lines
Got a very similar panic on a flat SMP box too:
BUG: unable to handle kernel paging request at virtual address 00100100 printing eip: c0154030 *pde = 2f2fa001 *pte = 00000000 Oops: 0000 [#1] 8K_STACKS SMP last sysfs file: /devices/pci0000:00/0000:00:0a.0/resource Modules linked in: CPU: 1 EIP: 0060:[<c0154030>] Not tainted VLI EFLAGS: 00010006 (2.6.17-mm1-autokern1 #1)EIP is at
s_show+0xe5/0x28e
eax:c038efe0ebx:dffead60ecx: 00000000 edx: 00100100
esi:c038efe0edi: 00000000 ebp:dffe7660esp:f69a7f14
ds: 007b es: 007b ss: 0068
Process cp (pid: 7190, ti=f69a6000 task=f64dc570 task.ti=f69a6000)Stack: 00000000 00000000 00000000 0000003f 00000328 f650a620 dffe7660 00000000 00001000 c01724e5 f650a620 dffe7660 00000909 00000000 0000005d 00000000 0000005c 00000000 ed4d3200 bff47a70 f69a7fa4 00001000 c0156e80 ed4d3200 Call Trace: [<c01724e5>] seq_read+0x195/0x262 [<c0156e80>] vfs_read+0x88/0x11e [<c0157160>] sys_read+0x3b/0x63 [<c036d07f>] syscall_call+0x7/0xb Code: 10 3b 8d d4 00 00 00 75 0a 85 f6 b8 a0 ef 38 c0 0f 44 f0 85 c9 75
Quoted 3 lines
0a 85 f6 b8 e0 ef 38 c0 0f 44 f0 01 4c 24 10 ff 44 24 0c 8b 12 <8b> 02 8d 74 26 00 39 da 75 c9 8b 53 10 8b 02 8d 74 26 00 8d 43
EIP: [<c0154030>]s_show+0xe5/0x28eSS:ESP 0068:f69a7f14
And that's LIST_POISON1.
The only s_show()s I can see are in slab and in kallsyms.
It would help if you could gdb these guys, work out file-n-line.
And it would be super-good if you could revert
slab-stop-using-list_for_each.patch and retest.
Quoted 5 lines · Andrew Morton
And that's
LIST_POISON1.The only s_show()s I can see are in slab and in kallsyms.
It would help if you could gdb these guys, work out file-n-line.
I just checked s_show in kernel/kallsyms.c and I can not see how it could BUG without BUG'ing in s_next first, because that function only formats the information that has been gathered by s_next.
Quoted 2 lines
And it would be super-good if you could revert
slab-stop-using-list_for_each.patch and retest.
My bet goes to slab's s_show, too. Besides, that code in kallsyms has been like that for a very long time, IIRC.
Signature · 4 lines
Paulo Marques - www.grupopie.com
Pointy-Haired Boss: I don't see anything that could stand in our way.
Dilbert: Sanity? Reality? The laws of physics?