prism54 regression

Bug #138979 reported by Alexandre Otto Strube
12
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-2.6.22-11-generic

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... :(

Revision history for this message
Alexandre Otto Strube (surak) wrote :

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.

Revision history for this message
Dave Meikle (dmk-uk) wrote :

I have this problem too. The LiveCD worked fine, then when I installed it failed with the above errors.

Revision history for this message
Alexandre Otto Strube (surak) wrote :

Actually, the prism54 driver is borked for quite some time. Removing prism54 and loading p54pci and p54common makes network work again

Revision history for this message
Michael Monreal (mimox) wrote :

As I just noted on bug #153350, adding a "blacklist prism54" can be used as a workaround for this. Still, a proper fix would be great.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2 which is set to come out around Dec 20. However, here are the instructions to install if you choose to do so, otherwise just wait for Alpha2 to come out:

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This report is remaining open against the actively developer kernel. However, against linux-source-2.6.22 this bug does not meet the criteria for a stable release update and is being closed. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
nglnx (nglnx) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.