Bug 14149

Summary:	irq 11: nobody cared (try booting with the "irqpoll" option)
Product:	Drivers	Reporter:	Martin Mokrejs (mmokrejs)
Component:	PCMCIA	Assignee:	linux-pcmcia
Status:	CLOSED OBSOLETE
Severity:	normal	CC:	alan, linux
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	2.6.30.4	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	dmesg output

Description Martin Mokrejs 2009-09-09 18:52:38 UTC

While physically unloading the PCMCIA wifi card D-Link DWL-AG660 I got this kernel crash:

pcmcia_socket pcmcia_socket1: pccard: card ejected from slot 1
ath5k 0000:07:00.0: PCI INT A disabled
pcmcia_socket pcmcia_socket1: pccard: CardBus card inserted into slot 1
pci 0000:07:00.0: reg 10 32bit mmio: [0x000000-0x00ffff]
ath5k 0000:07:00.0: enabling device (0000 -> 0002)
ath5k 0000:07:00.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
ath5k 0000:07:00.0: registered as 'phy1'
phy1: Selected rate control algorithm 'minstrel'
irq 11: nobody cared (try booting with the "irqpoll" option)
Pid: 8832, comm: wpa_supplicant Not tainted 2.6.30.4 #4
Call Trace:
 [<c103a1e3>] __report_bad_irq+0x2e/0x6f
 [<c103a319>] note_interrupt+0xf5/0x14c
 [<c1039811>] ? handle_IRQ_event+0x24/0x97
 [<c103a832>] handle_level_irq+0x6b/0x8d
 [<c1003eb2>] handle_irq+0x1a/0x20
 [<c1003c55>] do_IRQ+0x34/0x6f
 [<c1002da9>] common_interrupt+0x29/0x30
 [<c1004d01>] ? i8259A_shutdown+0xc/0xd
 [<c1039803>] ? handle_IRQ_event+0x16/0x97
 [<c103a81e>] handle_level_irq+0x57/0x8d
 [<c1003eb2>] handle_irq+0x1a/0x20
 [<c1003c55>] do_IRQ+0x34/0x6f
 [<c1002da9>] common_interrupt+0x29/0x30
 [<c101d27b>] ? __do_softirq+0x2f/0xc7
 [<c101d338>] do_softirq+0x25/0x2a
 [<c101d3fd>] irq_exit+0x28/0x2a
 [<c1003c7d>] do_IRQ+0x5c/0x6f
 [<c1002da9>] common_interrupt+0x29/0x30
 [<c114fe01>] ? ioread32+0xc/0x2a
 [<f80407a3>] ath5k_hw_set_imr+0x15b/0x165 [ath5k]
 [<f8047df3>] ath5k_beacon_config+0x14c/0x154 [ath5k]
 [<f804298c>] ? ath5k_hw_set_opmode+0x143/0x161 [ath5k]
 [<f8048668>] ath5k_reset+0x187/0x1bd [ath5k]
 [<f804899f>] ath5k_start+0x56/0xbb [ath5k]
 [<c12ed55b>] ieee80211_open+0x29c/0x61c
 [<c1062f9d>] ? core_sys_select+0x23e/0x26d
 [<c1278d7f>] dev_open+0x66/0x9a
 [<c1278825>] dev_change_flags+0x96/0x145
 [<c12a76ce>] devinet_ioctl+0x20f/0x4f6
 [<c103c856>] ? find_get_page+0x1e/0x4d
 [<c12a872d>] inet_ioctl+0x8d/0xa6
 [<c126d054>] sock_ioctl+0x1d9/0x1fd
 [<c126ce7b>] ? sock_ioctl+0x0/0x1fd
 [<c10613ed>] vfs_ioctl+0x15/0x49
 [<c1061b85>] do_vfs_ioctl+0x423/0x45d
 [<c106373e>] ? __d_free+0x38/0x3b
 [<c1063766>] ? d_free+0x25/0x37
 [<c10637b9>] ? d_kill+0x41/0x47
 [<c1067e53>] ? mntput_no_expire+0x19/0x8a
 [<c10591d0>] ? __fput+0x157/0x15f
 [<c1061bed>] sys_ioctl+0x2e/0x48
 [<c1002748>] sysenter_do_call+0x12/0x26
handlers:
[<c1211043>] (yenta_interrupt+0x0/0xb9)
[<c1260c9f>] (snd_intel8x0_interrupt+0x0/0x1c0)
[<c126188e>] (snd_intel8x0_interrupt+0x0/0x17a)
[<f9388dd7>] (usb_hcd_irq+0x0/0x56 [usbcore])
[<f80e6fc6>] (rtl8139_interrupt+0x0/0x3a4 [8139too])
[<f804734f>] (ath5k_intr+0x0/0x1a7 [ath5k])
Disabling IRQ #11
ath5k phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
wlan0: direct probe to AP 00:04:0e:d5:ef:21 try 1
wlan0 direct probe responded
wlan0: authenticate with AP 00:04:0e:d5:ef:21
wlan0: authenticated
wlan0: associate with AP 00:04:0e:d5:ef:21
wlan0: RX AssocResp from 00:04:0e:d5:ef:21 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: no probe response from AP 00:04:0e:d5:ef:21 - disassociating

The hardware is an ASUS laptop L3C/S with Pentium4-M processor. I will attach the full dmesg output.

Comment 1 Martin Mokrejs 2009-09-09 18:54:38 UTC

Created attachment 23052 [details]
dmesg output

I cannot comment on this more that it just happened. I do not use the wifi card much often and thus no idea on reproducibility although I could try some more testing.

Comment 2 Dominik Brodowski 2010-03-06 14:12:08 UTC

It seems like the socket driver at least thought the card was re-inserted:

pcmcia_socket pcmcia_socket1: pccard: card ejected from slot 1
...
pcmcia_socket pcmcia_socket1: pccard: CardBus card inserted into slot 1

Unless you can reproduce this with recent kernels, I'd prefer to close this bug with INSUFFICIENT_DATA.

Comment 3 Martin Mokrejs 2010-03-07 18:05:00 UTC

(In reply to comment #2)
> It seems like the socket driver at least thought the card was re-inserted:
> 
> pcmcia_socket pcmcia_socket1: pccard: card ejected from slot 1
> ...
> pcmcia_socket pcmcia_socket1: pccard: CardBus card inserted into slot 1
> 
> Unless you can reproduce this with recent kernels, I'd prefer to close this
> bug
> with INSUFFICIENT_DATA.


Yes, this is what I really did. What I wanted to report is that removal of the card crashed the kernel. I can try to reproduce in the meantime,