[hardy] Kernel panic with Zydas wifi and kernel 2.6.24
Bug #220013 reported by
Luke Plant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Intrepid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: linux-source-2.6.24
Upgraded to Hardy today, and never had the following problem in Gutsy:
After a connection attempt is made using my wireless USB Zydas dongle, if the connection fails, the system freezes and the keyboard LEDs start flashing - a hard reset is then necessary. I have not been able to find anything in kern.log indicating a kernel panic - I will try to get the crash to occur when I'm looking at a console.
If I am lucky and the connection attempt is successful, it works fine.
Kernel:
package: linux-image-
version: 2.6.24-16.30
Kernel module used: zd1211rw
Dongle info:
Bus 005 Device 002: ID 0ace:1215 ZyDAS WLA-54L WiFi
To post a comment you must log in.
I've got a backtrace at a text console: ------- ------- --
-------
Call Trace: softirq+ 0x9c/0x1c0 event+0x32/ 0x60 interrupt+ 0x185/0x1c0 timer+0x0/ 0x190 0x52/0xa0 0x45/0x50 timer_interrupt +0x3e/0x80 0x13/0x40 interrupt+ 0x28/0x30 safe_halt+ 0x2/0x10 0x245/0x2d0 bootoption+ 0x0/0x1e0
[<c01274dc>] run_timer_
[<c013a0a2>] tick_program_
[<c0134c65>] hrtimer_
[<c013a260>] tick_sched_
[<c0123f42>] __do_softirq+
[<c0123fd5>] do_softirq+
[<c011155e>] smp_apic_
[<c010a193>] sched_clock+
[<c01051b8>] apic_timer_
[<c0116542>] native_
[<c010261c>] cpu_idle+0x1c/0x70
[<c03fab05>] start_kernel+
[<c03fa370>] unknown_
===============
Code: 34 24 74 10 eb 25 8b 43 14 89 da 83 e0 fe 39 f0 75 19 89 cb 89 f0 e8 74 fe ff ff 39 fb 8b 0b 75 e5 83 c4 0c 89 e8 5b 5e 5f 5d c3 <0f> 0b eb fe 83 ec 0c 89 74 24 04 89 c6 89 7c 24 08 89 d7 89 1c
EIP: [<c012737c>] cascade+0x6c/0x70 SS:ESP 0068:c03f9f20
Kernel panic - not syncing: Fatal exception in interrupt.
------- ------- ------- ------- -
There were also what appeared to be timestamps at the beginning of each line. However, I didn't include these, as they were different each time, and it took me 3 attempts to get the full trace. This was because after a few minutes, the following started to scroll up the screen (along with some other occasional things which I could not catch):
zd1211rw 5-4:1.0: Could not allocate skb
Since I had to write down the backtrace on paper by hand, I had to try again. The 3rd time, I managed to get the 'Code' bit at the end. This time, the backtrace was identical to the above apart from it missed out the line with 'sched_clock'. I don't know if that makes a difference to the interpretation of the 'Code' section or not.
Thanks.