2003-08-25 09:18:55

by Mario Mikocevic

[permalink] [raw]
Subject: OOPS 2.6.0-test4 repeatable


IBM Thinkpad R40 with 2.6.0-test4, alsa compiled as module.
If I plug in D-link DWL-650+ (_just_ a plug in a slot) and _then_
modprobe snd-intel8x0 within seconds this oops barfs on me.


ksymoops 2.4.9 on i686 2.6.0-test4. Options used
-V (default)
-K (specified)
-L (specified)
-o /lib/modules/2.6.0-test4/ (default)
-m /boot/System.map-2.6.0-test4 (specified)

No modules in ksyms, skipping objects
Aug 25 10:42:48 mozz-r40 kernel: invalid operand: 0000 [#1]
Aug 25 10:42:48 mozz-r40 kernel: CPU: 0
Aug 25 10:42:48 mozz-r40 kernel: EIP: 0060:[<d082300d>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Aug 25 10:42:48 mozz-r40 kernel: EFLAGS: 00010286
Aug 25 10:42:48 mozz-r40 kernel: eax: fffffbfa ebx: d090c400 ecx: d090c3a0 edx: d090c3a0
Aug 25 10:42:48 mozz-r40 kernel: esi: ffffffed edi: cf039400 ebp: cf0394a8 esp: cf48de6c
Aug 25 10:42:48 mozz-r40 kernel: ds: 007b es: 007b ss: 0068
Aug 25 10:42:48 mozz-r40 kernel: Stack: c01a837c cf039400 d090c3a0 cf039400 d090c400 ffffffed c01a84cd d090c400
Aug 25 10:42:48 mozz-r40 kernel: cf039400 d090c400 cf039400 c01a850c d090c400 cf039400 d090c428 cf039454
Aug 25 10:42:48 mozz-r40 kernel: c01ecddb cf039454 d090c428 d090c458 cf039454 c032661c c01ece47 cf039454
Aug 25 10:42:48 mozz-r40 kernel: Call Trace:
Aug 25 10:42:48 mozz-r40 kernel: [<c01a837c>] pci_device_probe_static+0x52/0x63
Aug 25 10:42:48 mozz-r40 kernel: [<c01a84cd>] __pci_device_probe+0x3b/0x4e
Aug 25 10:42:48 mozz-r40 kernel: [<c01a850c>] pci_device_probe+0x2c/0x4a
Aug 25 10:42:48 mozz-r40 kernel: [<c01ecddb>] bus_match+0x3f/0x6a
Aug 25 10:42:48 mozz-r40 kernel: [<c01ece47>] device_attach+0x41/0x91
Aug 25 10:42:48 mozz-r40 kernel: [<c01ed006>] bus_add_device+0x5b/0x9f
Aug 25 10:42:48 mozz-r40 kernel: [<c01ec0cb>] device_add+0xca/0x100
Aug 25 10:42:48 mozz-r40 kernel: [<c01a4df1>] pci_bus_add_devices+0xcf/0x114
Aug 25 10:42:48 mozz-r40 kernel: [<d08cc04a>] cb_alloc+0xab/0xe5 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c90e3>] socket_insert+0x7f/0x92 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c9281>] socket_detect_change+0x58/0x82 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c93cb>] pccardd+0x120/0x1c1 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<c011d155>] default_wake_function+0x0/0x2e
Aug 25 10:42:48 mozz-r40 kernel: [<c010b0de>] ret_from_fork+0x6/0x14
Aug 25 10:42:48 mozz-r40 kernel: [<c011d155>] default_wake_function+0x0/0x2e
Aug 25 10:42:48 mozz-r40 kernel: [<d08c92ab>] pccardd+0x0/0x1c1 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<c0109215>] kernel_thread_helper+0x5/0xb
Aug 25 10:42:48 mozz-r40 kernel: Code: d9 09 dc cc d8 c7 db 9a d8 2b dc b8 d8 39 dd 16 d9 a1 de 62


>>EIP; d082300d <__crc_neigh_parms_release+357e3/b22398> <=====

>>eax; fffffbfa <__kernel_rt_sigreturn+17ba/????>
>>ebx; d090c400 <__crc_neigh_parms_release+11ebd6/b22398>
>>ecx; d090c3a0 <__crc_neigh_parms_release+11eb76/b22398>
>>edx; d090c3a0 <__crc_neigh_parms_release+11eb76/b22398>
>>esi; ffffffed <__kernel_rt_sigreturn+1bad/????>
>>edi; cf039400 <__crc_truncate_inode_pages+49f68d/bf945e>
>>ebp; cf0394a8 <__crc_truncate_inode_pages+49f735/bf945e>
>>esp; cf48de6c <__crc_truncate_inode_pages+8f40f9/bf945e>

Trace; c01a837c <pci_device_probe_static+52/63>
Trace; c01a84cd <__pci_device_probe+3b/4e>
Trace; c01a850c <pci_device_probe+2c/4a>
Trace; c01ecddb <bus_match+3f/6a>
Trace; c01ece47 <device_attach+41/91>
Trace; c01ed006 <bus_add_device+5b/9f>
Trace; c01ec0cb <device_add+ca/100>
Trace; c01a4df1 <pci_bus_add_devices+cf/114>
Trace; d08cc04a <__crc_neigh_parms_release+de820/b22398>
Trace; d08c90e3 <__crc_neigh_parms_release+db8b9/b22398>
Trace; d08c9281 <__crc_neigh_parms_release+dba57/b22398>
Trace; d08c93cb <__crc_neigh_parms_release+dbba1/b22398>
Trace; c011d155 <default_wake_function+0/2e>
Trace; c010b0de <ret_from_fork+6/14>
Trace; c011d155 <default_wake_function+0/2e>
Trace; d08c92ab <__crc_neigh_parms_release+dba81/b22398>
Trace; c0109215 <kernel_thread_helper+5/b>

Code; d082300d <__crc_neigh_parms_release+357e3/b22398>
00000000 <_EIP>:
Code; d082300d <__crc_neigh_parms_release+357e3/b22398> <=====
0: d9 09 (bad) (%ecx) <=====
Code; d082300f <__crc_neigh_parms_release+357e5/b22398>
2: dc cc fmul %st,%st(4)
Code; d0823011 <__crc_neigh_parms_release+357e7/b22398>
4: d8 c7 fadd %st(7),%st
Code; d0823013 <__crc_neigh_parms_release+357e9/b22398>
6: db 9a d8 2b dc b8 fistpl 0xb8dc2bd8(%edx)
Code; d0823019 <__crc_neigh_parms_release+357ef/b22398>
c: d8 39 fdivrs (%ecx)
Code; d082301b <__crc_neigh_parms_release+357f1/b22398>
e: dd 16 fstl (%esi)
Code; d082301d <__crc_neigh_parms_release+357f3/b22398>
10: d9 a1 de 62 00 00 fldenv 0x62de(%ecx)


--
Mario Mikocevic (Mozgy)
mozgy at hinet dot hr
It's never too late to have a good childhood!
The older you are, the better the toys!
My favourite FUBAR ...


2003-08-25 09:40:39

by Russell King

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable

On Mon, Aug 25, 2003 at 11:18:46AM +0200, Mario Mikocevic wrote:
> IBM Thinkpad R40 with 2.6.0-test4, alsa compiled as module.
> If I plug in D-link DWL-650+ (_just_ a plug in a slot) and _then_
> modprobe snd-intel8x0 within seconds this oops barfs on me.

After asking akpm what an "invalid operand" on x86 means, he says its
a BUG() statement. So, can you please supply both the ksymoops'd
*and* the raw undecoded kernel messages. Apparantly ksymoops cuts off
the lines which indicate that it was a bug and where the BUG() statement
was.

Thanks.

--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html

2003-08-25 10:25:30

by Mario Mikocevic

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable


On 2003.08.25 11:40, Russell King wrote:
> On Mon, Aug 25, 2003 at 11:18:46AM +0200, Mario Mikocevic wrote:
> > IBM Thinkpad R40 with 2.6.0-test4, alsa compiled as module.
> > If I plug in D-link DWL-650+ (_just_ a plug in a slot) and _then_
> > modprobe snd-intel8x0 within seconds this oops barfs on me.
>
> After asking akpm what an "invalid operand" on x86 means, he says its
> a BUG() statement. So, can you please supply both the ksymoops'd
> *and* the raw undecoded kernel messages. Apparantly ksymoops cuts off
> the lines which indicate that it was a bug and where the BUG() statement
> was.

Aug 25 10:41:55 mozz-r40 kernel: intel8x0: clocking to 48000
Aug 25 10:42:47 mozz-r40 kernel: spurious 8259A interrupt: IRQ7.
Aug 25 10:42:48 mozz-r40 kernel: invalid operand: 0000 [#1]
Aug 25 10:42:48 mozz-r40 kernel: CPU: 0
Aug 25 10:42:48 mozz-r40 kernel: EIP: 0060:[<d082300d>] Not tainted
Aug 25 10:42:48 mozz-r40 kernel: EFLAGS: 00010286
Aug 25 10:42:48 mozz-r40 kernel: EIP is at 0xd082300d
Aug 25 10:42:48 mozz-r40 kernel: eax: fffffbfa ebx: d090c400 ecx: d090c3a0 edx: d090c3a0
Aug 25 10:42:48 mozz-r40 kernel: esi: ffffffed edi: cf039400 ebp: cf0394a8 esp: cf48de6c
Aug 25 10:42:48 mozz-r40 kernel: ds: 007b es: 007b ss: 0068
Aug 25 10:42:48 mozz-r40 kernel: Process pccardd (pid: 3202, threadinfo=cf48c000 task=cf95cc80)
Aug 25 10:42:48 mozz-r40 kernel: Stack: c01a837c cf039400 d090c3a0 cf039400 d090c400 ffffffed c01a84cd d090c400
Aug 25 10:42:48 mozz-r40 kernel: cf039400 d090c400 cf039400 c01a850c d090c400 cf039400 d090c428 cf039454
Aug 25 10:42:48 mozz-r40 kernel: c01ecddb cf039454 d090c428 d090c458 cf039454 c032661c c01ece47 cf039454
Aug 25 10:42:48 mozz-r40 kernel: Call Trace:
Aug 25 10:42:48 mozz-r40 kernel: [<c01a837c>] pci_device_probe_static+0x52/0x63
Aug 25 10:42:48 mozz-r40 kernel: [<c01a84cd>] __pci_device_probe+0x3b/0x4e
Aug 25 10:42:48 mozz-r40 kernel: [<c01a850c>] pci_device_probe+0x2c/0x4a
Aug 25 10:42:48 mozz-r40 kernel: [<c01ecddb>] bus_match+0x3f/0x6a
Aug 25 10:42:48 mozz-r40 kernel: [<c01ece47>] device_attach+0x41/0x91
Aug 25 10:42:48 mozz-r40 kernel: [<c01ed006>] bus_add_device+0x5b/0x9f
Aug 25 10:42:48 mozz-r40 kernel: [<c01ec0cb>] device_add+0xca/0x100
Aug 25 10:42:48 mozz-r40 kernel: [<c01a4df1>] pci_bus_add_devices+0xcf/0x114
Aug 25 10:42:48 mozz-r40 kernel: [<d08cc04a>] cb_alloc+0xab/0xe5 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c90e3>] socket_insert+0x7f/0x92 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c9281>] socket_detect_change+0x58/0x82 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<d08c93cb>] pccardd+0x120/0x1c1 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<c011d155>] default_wake_function+0x0/0x2e
Aug 25 10:42:48 mozz-r40 kernel: [<c010b0de>] ret_from_fork+0x6/0x14
Aug 25 10:42:48 mozz-r40 kernel: [<c011d155>] default_wake_function+0x0/0x2e
Aug 25 10:42:48 mozz-r40 kernel: [<d08c92ab>] pccardd+0x0/0x1c1 [pcmcia_core]
Aug 25 10:42:48 mozz-r40 kernel: [<c0109215>] kernel_thread_helper+0x5/0xb
Aug 25 10:42:48 mozz-r40 kernel:
Aug 25 10:42:48 mozz-r40 kernel: Code: d9 09 dc cc d8 c7 db 9a d8 2b dc b8 d8 39 dd 16 d9 a1 de 62

The only missing lines were ->
Aug 25 10:42:48 mozz-r40 kernel: EIP is at 0xd082300d
Aug 25 10:42:48 mozz-r40 kernel: Process pccardd (pid: 3202, threadinfo=cf48c000 task=cf95cc80)

Do you need full dmesg and/or .config ?


--
Mario Mikocevic (Mozgy)
mozgy at hinet dot hr
It's never too late to have a good childhood!
The older you are, the better the toys!
My favourite FUBAR ...

2003-08-25 10:55:43

by Russell King

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable

On Mon, Aug 25, 2003 at 12:25:04PM +0200, Mario Mikocevic wrote:
> On 2003.08.25 11:40, Russell King wrote:
> > On Mon, Aug 25, 2003 at 11:18:46AM +0200, Mario Mikocevic wrote:
> > > IBM Thinkpad R40 with 2.6.0-test4, alsa compiled as module.
> > > If I plug in D-link DWL-650+ (_just_ a plug in a slot) and _then_
> > > modprobe snd-intel8x0 within seconds this oops barfs on me.
> >
> > After asking akpm what an "invalid operand" on x86 means, he says its
> > a BUG() statement. So, can you please supply both the ksymoops'd
> > *and* the raw undecoded kernel messages. Apparantly ksymoops cuts off
> > the lines which indicate that it was a bug and where the BUG() statement
> > was.

Ok so it isn't a BUG(). The next thing I'd consider is whether it was
a corrupted pci driver list, but it doesn't look like it.

Ok, lets try to get some extra info from your kernel - please apply
the patch below. This is likely to produce a fair amount of extra
messages at boot. It should also produce another raft of messages
when you insert the cardbus card but before the module, and another
raft afterwards.

I'm only interested in the ones around the time when you insert the
cardbus card and the module.

--- linux/drivers/pci/pci-driver.c.old Mon Aug 25 11:51:03 2003
+++ linux/drivers/pci/pci-driver.c Mon Aug 25 11:52:59 2003
@@ -66,7 +66,8 @@
{
int error = -ENODEV;
const struct pci_device_id *id;
-
+printk("pci_dev: %s driver: %p ", pci_name(pci_dev), drv);
+printk("name: %s table: %p probe: %p\n", drv->name, drv->id_table, drv->probe);
if (!drv->id_table)
return error;
id = pci_match_device(drv->id_table, pci_dev);


--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html

2003-08-25 12:45:50

by Mario Mikocevic

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable

Hi,

On 2003.08.25 12:55, Russell King wrote:
> Ok so it isn't a BUG(). The next thing I'd consider is whether it was
> a corrupted pci driver list, but it doesn't look like it.
>
> Ok, lets try to get some extra info from your kernel - please apply
> the patch below. This is likely to produce a fair amount of extra
> messages at boot. It should also produce another raft of messages
> when you insert the cardbus card but before the module, and another
> raft afterwards.
>
> I'm only interested in the ones around the time when you insert the
> cardbus card and the module.

OK, first some additional testing info, at first I thought it was
repeatable in the _very_ _same_ manner but not _quite_.
I have two possible scenarios ->

- after some time (never more than a minute or two) of plugging DWL-650+
into slot thinkpad-r40 just shuts itself down, no oops, _no_ nothing

- loading modules shortens time to shutdown to few seconds and _sometimes_
produces oops, so I have to do several plug_in/*plonk*/turn_on/fsck/reboot
iterations to get oops

Here's latest oops, this time provocated with loading modules snd-intel8x0 and
acx100_pci (yesterdays 0.1h version from http://acx100.sourceforge.net/) ->


Aug 25 13:42:09 mozz-r40 kernel: pci_dev: 0000:00:1f.5 driver: d0916580 name: Intel ICH table: d0915be0 probe: d0911f9e
Aug 25 13:42:10 mozz-r40 kernel: intel8x0: clocking to 48000
Aug 25 13:42:26 mozz-r40 kernel: pci_dev: 0000:03:00.0 driver: d090c400 name: acx100_pci table: d090c3a0 probe: d0823000
Aug 25 13:42:26 mozz-r40 kernel: Unable to handle kernel paging request at virtual address d0823000
Aug 25 13:42:26 mozz-r40 kernel: printing eip:
Aug 25 13:42:26 mozz-r40 kernel: d0823000
Aug 25 13:42:26 mozz-r40 kernel: *pde = 012d0067
Aug 25 13:42:26 mozz-r40 kernel: *pte = 00000000
Aug 25 13:42:26 mozz-r40 kernel: Oops: 0000 [#1]
Aug 25 13:42:26 mozz-r40 kernel: CPU: 0
Aug 25 13:42:26 mozz-r40 kernel: EIP: 0060:[<d0823000>] Not tainted
Aug 25 13:42:26 mozz-r40 kernel: EFLAGS: 00010286
Aug 25 13:42:26 mozz-r40 kernel: EIP is at 0xd0823000
Aug 25 13:42:26 mozz-r40 kernel: eax: d090c3a0 ebx: d090c400 ecx: d090c3a0 edx: d090c3a0
Aug 25 13:42:26 mozz-r40 kernel: esi: c135c400 edi: ffffffed ebp: c135c4a8 esp: ce037ba8
Aug 25 13:42:26 mozz-r40 kernel: ds: 007b es: 007b ss: 0068
Aug 25 13:42:26 mozz-r40 kernel: Process cardctl (pid: 3352, threadinfo=ce036000 task=cf1ba700)
Aug 25 13:42:26 mozz-r40 kernel: Stack: c01a604b c135c400 d090c3a0 d090c3a0 d0823000 c135c400 d090c400 ffffffed
Aug 25 13:42:26 mozz-r40 kernel: c01a619c d090c400 c135c400 d090c400 c135c400 c01a61db d090c400 c135c400
Aug 25 13:42:26 mozz-r40 kernel: d090c428 c135c454 c01eaaa7 c135c454 d090c428 d090c458 c135c454 c0322d1c
Aug 25 13:42:26 mozz-r40 kernel: Call Trace:
Aug 25 13:42:26 mozz-r40 kernel: [<c01a604b>] pci_device_probe_static+0x8d/0x9e
Aug 25 13:42:26 mozz-r40 kernel: [<c01a619c>] __pci_device_probe+0x3b/0x4e
Aug 25 13:42:26 mozz-r40 kernel: [<c01a61db>] pci_device_probe+0x2c/0x4a
Aug 25 13:42:26 mozz-r40 kernel: [<c01eaaa7>] bus_match+0x3f/0x6a
Aug 25 13:42:26 mozz-r40 kernel: [<c01eab13>] device_attach+0x41/0x91
Aug 25 13:42:26 mozz-r40 kernel: [<c01eacd2>] bus_add_device+0x5b/0x9f
Aug 25 13:42:26 mozz-r40 kernel: [<c01e9d97>] device_add+0xca/0x100
Aug 25 13:42:26 mozz-r40 kernel: [<c01a2a85>] pci_bus_add_devices+0xcf/0x114
Aug 25 13:42:26 mozz-r40 kernel: [<d08cc04a>] cb_alloc+0xab/0xe5 [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08c90e3>] socket_insert+0x7f/0x92 [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08cb63d>] pcmcia_insert_card+0x71/0x7e [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08bbbed>] ds_ioctl+0x285/0x670 [ds]
Aug 25 13:42:26 mozz-r40 kernel: [<c0179323>] padzero+0x28/0x2a
Aug 25 13:42:26 mozz-r40 kernel: [<c0179fe5>] load_elf_binary+0x522/0xb51
Aug 25 13:42:26 mozz-r40 kernel: [<c011b775>] pgd_alloc+0x18/0x1c
Aug 25 13:42:26 mozz-r40 kernel: [<c011e8ff>] mm_init+0x98/0xd2
Aug 25 13:42:26 mozz-r40 kernel: [<c013d963>] buffered_rmqueue+0xc1/0x15a
Aug 25 13:42:26 mozz-r40 kernel: [<c013da8e>] __alloc_pages+0x92/0x30c
Aug 25 13:42:26 mozz-r40 kernel: [<c0181921>] proc_alloc_inode+0x4c/0x75
Aug 25 13:42:26 mozz-r40 kernel: [<c0146d78>] do_anonymous_page+0x138/0x22a
Aug 25 13:42:26 mozz-r40 kernel: [<c01473b3>] handle_mm_fault+0xd9/0x16e
Aug 25 13:42:26 mozz-r40 kernel: [<c011ba26>] do_page_fault+0x23a/0x44b
Aug 25 13:42:26 mozz-r40 kernel: [<c0139e39>] find_get_page+0x2d/0x57
Aug 25 13:42:26 mozz-r40 kernel: [<c013af05>] filemap_nopage+0x223/0x303
Aug 25 13:42:26 mozz-r40 kernel: [<c0155667>] unlock_buffer+0x33/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c0156d17>] __find_get_block+0x6b/0xe0
Aug 25 13:42:26 mozz-r40 kernel: [<c0156db7>] __getblk+0x2b/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c0156d17>] __find_get_block+0x6b/0xe0
Aug 25 13:42:26 mozz-r40 kernel: [<c0156db7>] __getblk+0x2b/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c018bffb>] ext2_release_inode+0x7a/0xad
Aug 25 13:42:26 mozz-r40 kernel: [<c018c16a>] ext2_free_inode+0x13c/0x183
Aug 25 13:42:26 mozz-r40 kernel: [<c018f9d9>] ext2_destroy_inode+0x1b/0x1f
Aug 25 13:42:26 mozz-r40 kernel: [<c016c118>] destroy_inode+0x35/0x50
Aug 25 13:42:26 mozz-r40 kernel: [<c016d37a>] iput+0x62/0x7c
Aug 25 13:42:26 mozz-r40 kernel: [<c0163427>] sys_unlink+0x86/0x135
Aug 25 13:42:26 mozz-r40 kernel: [<c016598a>] sys_ioctl+0xf9/0x27b
Aug 25 13:42:26 mozz-r40 kernel: [<c010b1b5>] sysenter_past_esp+0x52/0x71
Aug 25 13:42:26 mozz-r40 kernel:
Aug 25 13:42:26 mozz-r40 kernel: Code: Bad EIP value.

ksymoops 2.4.9 on i686 2.6.0-test4-rk1. Options used
-V (default)
-K (specified)
-L (specified)
-o /lib/modules/2.6.0-test4-rk1/ (default)
-m /boot/System.map-2.6.0-test4-rk1 (specified)

No modules in ksyms, skipping objects
Aug 25 13:39:27 mozz-r40 kernel: Machine check exception polling timer started.
Aug 25 13:39:28 mozz-r40 kernel: e100: eth0: Intel(R) PRO/100 Network Connection
Aug 25 13:39:28 mozz-r40 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Aug 25 13:39:28 mozz-r40 kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Aug 25 13:39:28 mozz-r40 kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3df 0x4d0-0x4d7
Aug 25 13:39:28 mozz-r40 kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 25 13:42:26 mozz-r40 kernel: Unable to handle kernel paging request at virtual address d0823000
Aug 25 13:42:26 mozz-r40 kernel: d0823000
Aug 25 13:42:26 mozz-r40 kernel: *pde = 012d0067
Aug 25 13:42:26 mozz-r40 kernel: Oops: 0000 [#1]
Aug 25 13:42:26 mozz-r40 kernel: CPU: 0
Aug 25 13:42:26 mozz-r40 kernel: EIP: 0060:[<d0823000>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Aug 25 13:42:26 mozz-r40 kernel: EFLAGS: 00010286
Aug 25 13:42:26 mozz-r40 kernel: eax: d090c3a0 ebx: d090c400 ecx: d090c3a0 edx: d090c3a0
Aug 25 13:42:26 mozz-r40 kernel: esi: c135c400 edi: ffffffed ebp: c135c4a8 esp: ce037ba8
Aug 25 13:42:26 mozz-r40 kernel: ds: 007b es: 007b ss: 0068
Aug 25 13:42:26 mozz-r40 kernel: Stack: c01a604b c135c400 d090c3a0 d090c3a0 d0823000 c135c400 d090c400 ffffffed
Aug 25 13:42:26 mozz-r40 kernel: c01a619c d090c400 c135c400 d090c400 c135c400 c01a61db d090c400 c135c400
Aug 25 13:42:26 mozz-r40 kernel: d090c428 c135c454 c01eaaa7 c135c454 d090c428 d090c458 c135c454 c0322d1c
Aug 25 13:42:26 mozz-r40 kernel: Call Trace:
Aug 25 13:42:26 mozz-r40 kernel: [<c01a604b>] pci_device_probe_static+0x8d/0x9e
Aug 25 13:42:26 mozz-r40 kernel: [<c01a619c>] __pci_device_probe+0x3b/0x4e
Aug 25 13:42:26 mozz-r40 kernel: [<c01a61db>] pci_device_probe+0x2c/0x4a
Aug 25 13:42:26 mozz-r40 kernel: [<c01eaaa7>] bus_match+0x3f/0x6a
Aug 25 13:42:26 mozz-r40 kernel: [<c01eab13>] device_attach+0x41/0x91
Aug 25 13:42:26 mozz-r40 kernel: [<c01eacd2>] bus_add_device+0x5b/0x9f
Aug 25 13:42:26 mozz-r40 kernel: [<c01e9d97>] device_add+0xca/0x100
Aug 25 13:42:26 mozz-r40 kernel: [<c01a2a85>] pci_bus_add_devices+0xcf/0x114
Aug 25 13:42:26 mozz-r40 kernel: [<d08cc04a>] cb_alloc+0xab/0xe5 [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08c90e3>] socket_insert+0x7f/0x92 [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08cb63d>] pcmcia_insert_card+0x71/0x7e [pcmcia_core]
Aug 25 13:42:26 mozz-r40 kernel: [<d08bbbed>] ds_ioctl+0x285/0x670 [ds]
Aug 25 13:42:26 mozz-r40 kernel: [<c0179323>] padzero+0x28/0x2a
Aug 25 13:42:26 mozz-r40 kernel: [<c0179fe5>] load_elf_binary+0x522/0xb51
Aug 25 13:42:26 mozz-r40 kernel: [<c011b775>] pgd_alloc+0x18/0x1c
Aug 25 13:42:26 mozz-r40 kernel: [<c011e8ff>] mm_init+0x98/0xd2
Aug 25 13:42:26 mozz-r40 kernel: [<c013d963>] buffered_rmqueue+0xc1/0x15a
Aug 25 13:42:26 mozz-r40 kernel: [<c013da8e>] __alloc_pages+0x92/0x30c
Aug 25 13:42:26 mozz-r40 kernel: [<c0181921>] proc_alloc_inode+0x4c/0x75
Aug 25 13:42:26 mozz-r40 kernel: [<c0146d78>] do_anonymous_page+0x138/0x22a
Aug 25 13:42:26 mozz-r40 kernel: [<c01473b3>] handle_mm_fault+0xd9/0x16e
Aug 25 13:42:26 mozz-r40 kernel: [<c011ba26>] do_page_fault+0x23a/0x44b
Aug 25 13:42:26 mozz-r40 kernel: [<c0139e39>] find_get_page+0x2d/0x57
Aug 25 13:42:26 mozz-r40 kernel: [<c013af05>] filemap_nopage+0x223/0x303
Aug 25 13:42:26 mozz-r40 kernel: [<c0155667>] unlock_buffer+0x33/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c0156d17>] __find_get_block+0x6b/0xe0
Aug 25 13:42:26 mozz-r40 kernel: [<c0156db7>] __getblk+0x2b/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c0156d17>] __find_get_block+0x6b/0xe0
Aug 25 13:42:26 mozz-r40 kernel: [<c0156db7>] __getblk+0x2b/0x51
Aug 25 13:42:26 mozz-r40 kernel: [<c018bffb>] ext2_release_inode+0x7a/0xad
Aug 25 13:42:26 mozz-r40 kernel: [<c018c16a>] ext2_free_inode+0x13c/0x183
Aug 25 13:42:26 mozz-r40 kernel: [<c018f9d9>] ext2_destroy_inode+0x1b/0x1f
Aug 25 13:42:26 mozz-r40 kernel: [<c016c118>] destroy_inode+0x35/0x50
Aug 25 13:42:26 mozz-r40 kernel: [<c016d37a>] iput+0x62/0x7c
Aug 25 13:42:26 mozz-r40 kernel: [<c0163427>] sys_unlink+0x86/0x135
Aug 25 13:42:26 mozz-r40 kernel: [<c016598a>] sys_ioctl+0xf9/0x27b
Aug 25 13:42:26 mozz-r40 kernel: [<c010b1b5>] sysenter_past_esp+0x52/0x71
Aug 25 13:42:26 mozz-r40 kernel: Code: Bad EIP value.


>>EIP; d0823000 <__crc_neigh_parms_release+357d6/b22398> <=====

>>eax; d090c3a0 <__crc_neigh_parms_release+11eb76/b22398>
>>ebx; d090c400 <__crc_neigh_parms_release+11ebd6/b22398>
>>ecx; d090c3a0 <__crc_neigh_parms_release+11eb76/b22398>
>>edx; d090c3a0 <__crc_neigh_parms_release+11eb76/b22398>
>>esi; c135c400 <__crc_skb_under_panic+4125f/11200a>
>>edi; ffffffed <__kernel_rt_sigreturn+1bad/????>
>>ebp; c135c4a8 <__crc_skb_under_panic+41307/11200a>
>>esp; ce037ba8 <__crc_cdrom_mode_sense+211ce2/2a69c4>

Trace; c01a604b <pci_device_probe_static+8d/9e>
Trace; c01a619c <__pci_device_probe+3b/4e>
Trace; c01a61db <pci_device_probe+2c/4a>
Trace; c01eaaa7 <bus_match+3f/6a>
Trace; c01eab13 <device_attach+41/91>
Trace; c01eacd2 <bus_add_device+5b/9f>
Trace; c01e9d97 <device_add+ca/100>
Trace; c01a2a85 <pci_bus_add_devices+cf/114>
Trace; d08cc04a <__crc_neigh_parms_release+de820/b22398>
Trace; d08c90e3 <__crc_neigh_parms_release+db8b9/b22398>
Trace; d08cb63d <__crc_neigh_parms_release+dde13/b22398>
Trace; d08bbbed <__crc_neigh_parms_release+ce3c3/b22398>
Trace; c0179323 <padzero+28/2a>
Trace; c0179fe5 <load_elf_binary+522/b51>
Trace; c011b775 <pgd_alloc+18/1c>
Trace; c011e8ff <mm_init+98/d2>
Trace; c013d963 <buffered_rmqueue+c1/15a>
Trace; c013da8e <__alloc_pages+92/30c>
Trace; c0181921 <proc_alloc_inode+4c/75>
Trace; c0146d78 <do_anonymous_page+138/22a>
Trace; c01473b3 <handle_mm_fault+d9/16e>
Trace; c011ba26 <do_page_fault+23a/44b>
Trace; c0139e39 <find_get_page+2d/57>
Trace; c013af05 <filemap_nopage+223/303>
Trace; c0155667 <unlock_buffer+33/51>
Trace; c0156d17 <__find_get_block+6b/e0>
Trace; c0156db7 <__getblk+2b/51>
Trace; c0156d17 <__find_get_block+6b/e0>
Trace; c0156db7 <__getblk+2b/51>
Trace; c018bffb <ext2_release_inode+7a/ad>
Trace; c018c16a <ext2_free_inode+13c/183>
Trace; c018f9d9 <ext2_destroy_inode+1b/1f>
Trace; c016c118 <destroy_inode+35/50>
Trace; c016d37a <iput+62/7c>
Trace; c0163427 <sys_unlink+86/135>
Trace; c016598a <sys_ioctl+f9/27b>
Trace; c010b1b5 <sysenter_past_esp+52/71>



--
Mario Mikocevic (Mozgy)
mozgy at hinet dot hr
It's never too late to have a good childhood!
The older you are, the better the toys!
My favourite FUBAR ...

2003-08-25 13:07:39

by Mario Mikocevic

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 (almost) repeatable

Hi,

On 2003.08.25 12:55, Russell King wrote:
> Ok so it isn't a BUG().

I suspected ACPI so I tried booting it with :
acpi=off no shutdowns, no oops
pci=noacpi within seconds as I plug 650+ it shutdowns (tried three times)
pci=usepirqmask survives a _lot_ longer (several mins) but as soon as I
`cardctl insert` -> shutdown

ACPI problem ?

Any hints what to check next ? I'm welcome to patches ..


--
Mario Mikocevic (Mozgy)
mozgy at hinet dot hr
It's never too late to have a good childhood!
The older you are, the better the toys!
My favourite FUBAR ...

2003-08-25 13:30:47

by Russell King

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable

On Mon, Aug 25, 2003 at 02:45:36PM +0200, Mario Mikocevic wrote:
> OK, first some additional testing info, at first I thought it was
> repeatable in the _very_ _same_ manner but not _quite_.
> I have two possible scenarios ->
>
> - after some time (never more than a minute or two) of plugging DWL-650+
> into slot thinkpad-r40 just shuts itself down, no oops, _no_ nothing
>
> - loading modules shortens time to shutdown to few seconds and _sometimes_
> produces oops, so I have to do several plug_in/*plonk*/turn_on/fsck/reboot
> iterations to get oops
>
> Here's latest oops, this time provocated with loading modules snd-intel8x0 and
> acx100_pci (yesterdays 0.1h version from http://acx100.sourceforge.net/) ->

Well, acx100_pci seems to be buggy.

> Aug 25 13:42:09 mozz-r40 kernel: pci_dev: 0000:00:1f.5 driver: d0916580 name: Intel ICH table: d0915be0 probe: d0911f9e
> Aug 25 13:42:10 mozz-r40 kernel: intel8x0: clocking to 48000

> Aug 25 13:42:26 mozz-r40 kernel: pci_dev: 0000:03:00.0 driver: d090c400 name: acx100_pci table: d090c3a0 probe: d0823000
> Aug 25 13:42:26 mozz-r40 kernel: Unable to handle kernel paging request at virtual address d0823000

It's probe function is at address 0xd0823000 which is where your OOPS
is happening. I suspect you'll find the acx100 pci probe function is
marked with __init. That's a bug - it must not be.

Similarly, the PCI ID table must not be marked with __devinitdata nor
__initdata.

(I can't reach acx100.sourceforge.net currently.)

--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html

2003-08-25 14:07:04

by Russell King

[permalink] [raw]
Subject: Re: OOPS 2.6.0-test4 repeatable

On Mon, Aug 25, 2003 at 02:30:34PM +0100, Russell King wrote:
> > Aug 25 13:42:26 mozz-r40 kernel: pci_dev: 0000:03:00.0 driver: d090c400 name: acx100_pci table: d090c3a0 probe: d0823000
> > Aug 25 13:42:26 mozz-r40 kernel: Unable to handle kernel paging request at virtual address d0823000
>
> It's probe function is at address 0xd0823000 which is where your OOPS
> is happening. I suspect you'll find the acx100 pci probe function is
> marked with __init. That's a bug - it must not be.

Well, here it is:

static int __init
acx100_probe_pci(struct pci_dev *pdev, const struct pci_device_id *id)

Please report this to the ACX people as a bug - the probe function must
/not/ be marked as __init. If they want them to be discarded if hotplug
is disabled, they must be marked as __devinit. However, in 2.6 kernels,
they must not be marked as __init nor __devinit in any case.

--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html