prism54 regression
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-
It worked on feisty with prism54common and prism54pci
Now, on gutsy, it appears something like this:
[4294714.155000] eth1: resetting device...
[4294714.155000] eth1: uploading firmware...
[4294714.464000] eth1: firmware version: 1.0.4.3
[4294714.464000] eth1: firmware upload complete
[4294715.464000] eth1: no 'reset complete' IRQ seen - retrying
[4294716.464000] eth1: no 'reset complete' IRQ seen - retrying
[4294716.464000] eth1: interface reset failure
[4294716.464000] prism54: Your card/socket may be faulty, or IRQ line too busy :(
[4294716.514000] eth1: resetting device...
[4294716.514000] eth1: uploading firmware...
[4294716.633000] eth1: firmware version: 1.0.4.3
[4294716.634000] eth1: firmware upload complete
[4294717.634000] eth1: no 'reset complete' IRQ seen - retrying
[4294718.634000] eth1: no 'reset complete' IRQ seen - retrying
[4294718.634000] eth1: interface reset failure
[4294718.634000] prism54: Your card/socket may be faulty, or IRQ line too busy :(
I regret I erased the old kernel, which used to work so fine... :(
Just to clarify, this is not the message that appeared on MY machine. The firmware is way newer than it (2.7.0.0 I think). As I have no network on the machine now because of the bug, I just googled for it and found almost the same message.