bcm43xx causes touchpad instability and system freezes

Bug #63919 reported by Aleksander Kamil Modzelewski
4
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux-source-2.6.17 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I use a Lenovo 3000 N100 laptop with a BCM4310 UART PCI Express card (pci-id 14e4:4312, rev 01). When using ndiswrapper the card works ok. Using it with the native driver causes the touchpad to go unstable (it sometimes goes to the point when it locks up, getting normal only after switching to another vt and back, but usually just locks/hops/random clicks for several seconds every couple of minutes) when trying to actually *use* the card (i.e. connect to a network, do a scan, transfer something). The card more or less works (it is unstable as well, but not as much as the touchpad). Last time during test unloading the module for about third time without reboot caused an oops and froze the system.

I will attach some logs and pci -nvv output.

Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

This is the log. I have configured the interface for my WEP before. The instabilities occur with WPA as well (I have successfully connected with WPA/Network Manager at my friends, but the system was unstable. Regretfully I don't have any logs from that time)

Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :
Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

Well, I'll just note that on 10.27 the issue is still present.

Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

Bug #61388 claims to be solved, seems a bit different (like, similiar but not the same), and here it persists with 2.6.20-12.19...

Changed in linux-source-2.6.17:
importance: Undecided → Medium
Changed in linux-source-2.6.20:
importance: Undecided → Medium
Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
status: Unconfirmed → Confirmed
Revision history for this message
Mike Dahlgren (dahlgren) wrote :

I believe I have the same issue, when the issue arises I get the following in dmesg:

 TouchPad at isa0060/serio4/input0 lost sync at byte 1

I believe this is a duplicate of Bug #12124

Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

It is similiar and quite probably both bugs are related to some buggy irq/other resources assignment. But I would consider a wireless/touchpad and USB/touchpad to be related but separate bugs, related either to the wireless card and USB controller or to the BIOSes of both laptops

Anyway, I suppose I have a bigger problem because some time ago I had a similiar problem with reading audio-cds (normals work). I'll try to reproduce it at some time.

Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

On linux-image-2.6.22-3-generic 2.6.22-3.9 on gutsy the problem gets both worse and better: ndiswrapper doesn't work anymore (I don't know why), but I can effectively work using the bcm43xx driver. Still, there *are* problems when connecting (I'm using WEP) and then, after periods of stability, the mouse gets chunky again, then gets stable. Sometimes this causes the touchpad to loose some of its features (i.e. touchscroll), but logging in and out helps.

No system crashes this time.

Revision history for this message
Ben Collins (ben-collins) wrote :

Likely we wont be able to do much here. bcm43xx is still a work in progress.

As for ndiskwrapper, make sure you have linux-ubuntu-modules-2.6.22-3-generic installed (installing linux-image-generic should bring it in).

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

Without that, I wouldn't be able to use ndiswrapper at all. In my case, ndiswrapper loads and binds the interface, but NetworkManager fails to configure it.

As for bcm43xx - *sigh*, back to the big wait, then.

Changed in linux:
status: Unknown → Confirmed
Changed in linux-source-2.6.17:
status: New → Won't Fix
Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux-source-2.6.22:
status: Confirmed → Triaged
Changed in linux:
status: Confirmed → Incomplete
Changed in linux:
status: Incomplete → Invalid
Revision history for this message
Aleksander Kamil Modzelewski (aleander) wrote :

I just installed hardy and 2.6.24-1-generic. With the b43 driver everything works. I had to clean up a bit (removed /etc/udev/rules.d/70-persistent-net.rules line becaused it clashed with the old setting somehow) and it works perfectly.

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

I had the same issue with a new HP Pavilion dv6605us laptop, running gutsy. Compiling the b43 driver from linuxwireless.org, for the gutsy kernel, fixed the problem.

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

Hardy includes the b43 driver instead. Is anyone seeing this problem on Hardy?

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

Changing to "Fix Released", since the newer b43 driver doesn't show this problem. If anyone still has problems, please reopen the bug.

Changed in linux-source-2.6.22 (Ubuntu):
status: Triaged → Fix Released
Changed in linux:
importance: Unknown → Medium
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.