linux-backports-modules-jaunty: b43 and ssb regression
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
kernel-xps-m1330 |
Invalid
|
Undecided
|
Unassigned | ||
linux-backports-modules-2.6.28 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: linux-backports
Background:
I have a PCI BCM4318 which worked flawlessly with Hardy, with the b43 module. I didn't test it when upgrading through Intrepid to Jaunty, so the following might also affect Intrepid. WIth Jaunty it has the forever-repeating:
b43-phy0 ERROR: PHY transmission error
during which the connection becomes unresponsive, or is dropped
The Bug:
Strangely, linux-backports
lspci -v -v reports:
02:01.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Subsystem: Linksys Device 0042
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32
Interrupt: pin A routed to IRQ 22
Region 0: Memory at f9800000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
This is wrong...I'm almost certain that it used to say that the b43 kernel driver or module was in use, in addition to the ssb. Additionally, that "b43-pci-bridge" sounds a lot like the a module for the type of card I don't have.
Did the PCI IDs get scrambled somewhere? Please advise which logs you need me to post.
Thanks!
Nick
Changed in linux-meta (Ubuntu): | |
status: | In Progress → Confirmed |
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in kernel-xps-1330: | |
status: | New → Invalid |
Changed in linux: | |
status: | Confirmed → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
Wow was I off with the "b43-pci-bridge" idea! At any rate, I decided to roll a custom, very lean 2.6.30.3 vanilla kernel to use as a baseline (and so I might have something that works if all else fails). b43 works marvelously. I'll post my logs. Next I'll try 2.6.28.10 vanilla and post those. If you would prefer for me to test a different 2.6.28.xy please mention which revision.qq
Then I'll post logs for linux-image- 2.6.28- 13-generic with linux-backports -modules installed.
And then without. All comments will contain:
1. `uname -a`
2. `dmesg > dmesg.log`
3. `lspci -vvnn > lspci-vvnn.log` (as root)
'hopefully the logs from all of these will encircle and help us to isolate where exactly the problem is. Please advise me which debugging opions I ought to enable. A few backtraces would probably make it much easier, but I don't know anything about kernel-specific debugging...