Public bug reported:
Binary package hint: linux-source-2.6.20
Problem:
ipw3945 driver crash with following output to dmesg. Only way to repair problem
is to reboot. i.e. unloading ,reloading module and restarting helper does not
work:
...
[37954.280000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[37954.880000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[37955.380000] ipw3945: Error sending cmd #07 to daemon: time out after 500ms.
[37955.880000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[37956.524000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[37957.024000] ipw3945: Error sending cmd #08 to daemon: time out after 500ms.
[37957.524000] ipw3945: Error sending ADD_STA: time out after 500ms.
[37958.024000] ipw3945: Error sending SCAN_ABORT_CMD: time out after 500ms.
[37967.032000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[37967.136000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[38017.024000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[38017.524000] ipw3945: Error sending LEDS_CMD: time out after 500ms.
[38017.796000] ------------[ cut here ]------------
[38017.796000] kernel BUG at kernel/workqueue.c:323!
[38017.796000] invalid opcode: 0000 [#1]
....
(Full dmesg attached to bug.)
Steps to reproduce:
This driver crash randomly happens after a fair amount of uptime (often 10-24
h). Most frequently while running bittorrent.
Hardware:
Fujitsu-Siemens Amilo Si1520. Relevant lspci (-nvv) parts:
01:00.0 0280: 8086:4222 (rev 02)
Subsystem: 8086:1001
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at da000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [e0] Express Legacy Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
Device: Latency L0s <512ns, L1 unlimited
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 0
Link: Latency L0s <128ns, L1 <64us
Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk+ ExtSynch-
Link: Speed 2.5Gb/s, Width x1
(Full lspci attached to bug.)
Software:
Kernel: 2.6.20-15.27 (linux.image-2.6.20-15-generic)
Note:
#1: This bug might be related to bug #108090
#2: I have never had this problem with earlier feisty kernel versions (during
alpha and beta stage)
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
