[Bug 405712] [NEW] linux-backports-modules-jaunty: b43 and ssb regression

sten nick.steeves at shaw.ca
Tue Jul 28 09:12:40 UTC 2009

Public bug reported:

Binary package hint: linux-backports-modules

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-modules-jaunty-2.6.28-11 and *-2.6.28-13 are even worse.  No IP-level link at all.  No ping.  Route times out like there is a break in the physical layer...  Also, very, very strangely, the backports-modules version of ssb and/or b43 now load the pcmcia subsystem -- when it's absolutely not needed for my NIC.  This run-of-the-mill Linksys 802.11g PCI NIC isn't one of those PCMCIA/Cardbus-to-PCI adapters.

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.


** Affects: linux-meta (Ubuntu)
     Importance: Undecided
         Status: New

linux-backports-modules-jaunty: b43 and ssb regression
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.

More information about the kernel-bugs mailing list