Prism54pci WLAN driver seems broken...

[Norbert Schultz]

Binary package hint: linux-image-2.6-amd64-generic

Hi there,

On Feisty/AMD64 the "prism54pci" (with isl3890) module produces problems
- on Removing kernel module: kernel panic
- After long time heavy network load (bittorrent, but not websurfing) kernel panic
- Sometimes after long time, strange disconnection from AP. Reconnection works, but it won't take long until next disconnection. /var/log/messages is full of
May 16 12:29:19 shodan kernel: [ 7457.952947] wiphy0: tx overflow.
when this happens.

uname -a
Linux shodan 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 GNU/Linux

WLAN Adapter (according to lspci)
01:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow]
It's a "T-Sinus 154pcicard", labeled from german ISP.

There are several other Bugs affecting prism54 in Launchpad, but they are all USB or PCMCIA. In contrast to Bug #108602 the kernel doesn't report "Kernel BUG" (or does this only happens with debug kernels?)

[Simon (simon-leiser)]

Hi there,

I can confirm this bug reported by Norbert. I didn't experience any problems under breezy/dapper/edgy, only after upgrading to feisty the trouble with the wlan card began, in particular (not to say only) in combination with heavy network load (torrent, mule, etc.)
What I experienced was in best case the strange disconnect from AP mentioned above with a similar output in /var/log/messages. However, in 9 of 10 cases the machine entirely froze (what Norbert maybe referred to as kernel panic). Unlike Bug #108602, I also don't get a "kernel bug" message, either a total freeze, or the disconnect from the AP, that's it. I have no output from dmesg available because I switched to wired connection again, as I want to use the computer.

I'm running a feisty 7.04 with all patches available.
Output from uname -a:
Linux simon-PC 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

from lspci I get for the wlan adapter:
02:00.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
        Subsystem: Z-Com, Inc. XG-600 and clones Wireless Adapter
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (2500ns min, 7000ns max), Cache Line Size: 128 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: Memory at fa400000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: <access denied>

I'd be really grateful for any hint how I can enjoy my Feisty in the same way I did with it's predecessors!

[incy wincy2k (j-northcott)]

I have also had this frustrating problem since upgrading to feisty. I had no problems with this card on previous versions.It's become so bad once i loose connection i am unable to even scan for wireless AP's.
My log's are full of the: "Jul 9 23:51:38 laptop01 kernel: [ 1918.424000] wiphy0: tx overflow." message

Also the addition of a wmaster0 interface has appeared since updating, I am curious if this is the cause of the problems?
wlan0 Link encap:Ethernet HWaddr 00:60:B3:91:F0:6C
          inet6 addr: fe80::260:b3ff:fe91:f06c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:633 errors:0 dropped:0 overruns:0 frame:0
          TX packets:790 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:511954 (499.9 KiB) TX bytes:167704 (163.7 KiB)

wmaster0 Link encap:UNSPEC HWaddr 00-60-B3-91-F0-6C-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

uname -a
Linux laptop01 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

01:0a.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
        Subsystem: Z-Com, Inc. XG-600 and clones Wireless Adapter
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at cfffc000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [dc] Power Management version 1

Any help in resolving this problem would be gratefully appreciated.

[DarkAeons (darkaeons)]

I've posted my stuff here: https://bugs.launchpad.net/ubuntu/+bug/121224
didn't notice this thread sooner, I get the same problem.

darkaeons@indadark1:/media/hdb1$ uname -a
Linux indadark1 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux

[DarkAeons (darkaeons)]

did I mention I also got total system freezes?
caps lock and scroll lock blinking, also did sysrq keys (Ctrl+Alt+SystReq+R,Ctrl+Alt+SystReq+S,Ctrl+Alt+SystReq+E,Ctrl+Alt+SystReq+I,Ctrl+Alt+SystReq+U,Ctrl+Alt+SystReq+B)
and all it did was stop the led blink, I had to reset the computer.

[Simon (simon-leiser)]

Hi there,

being a bit frustrated about the way this bug described here was dealt with, I tried with an upgrade to gutsy: same symptoms! After some hours of heavy traffic load the system freezes entirely without writing anything into any log file when running on wireless; no problems with wired network.
Is there anything I can contribute to the solution of this problem besides changing distribution?

Any help would be greatly acknowledged!

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Andy Whitcroft (apw)]

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . If the issue remains in Jaunty, Please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-2.6.28-11-generic <bug #>

If you could also test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance!

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]