On Wednesday 07 May 2008 20:35:16 Larry Finger wrote: > Michael, > > On the current Ubuntu kernel (2.6.24), trying to load b43legacy causes a > kernel hang with BCM4301 and BCM4303 devices. In trying to debug this, I have > b43legacy blacklisted and I am trying to get useful information on the hang > from netconsole. > > Before getting started on the above, I have noticed the following in the > dmesg output: > > > > ssb: Core 0 found: IEEE 802.11 (cc 0x812, rev 0x02, vendor 0x4243) > ssb: Core 1 found: PCMCIA (cc 0x80D, rev 0x00, vendor 0x4243) > ssb: Core 2 found: Fast Ethernet (cc 0x806, rev 0x02, vendor 0x4243) > ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243) > ssb: Core 4 found: PCI (cc 0x804, rev 0x03, vendor 0x4243) > ssb: Sonics Silicon Backplane found on PCI device 0000:00:0b.0 > > --- snip --- > > b44.c:v2.0 > b44: Invalid MAC address found in EEPROM > b44 ssb0:1: Problem fetching invariants of chip, aborting. > b44: probe of ssb0:1 failed with error -22 > > The ssb core listing is exactly what I expected; however, the attempt to load > b44 is not. The only device with vendor code 0x14e4 is the BCM4301. In > addition, b44 is not being forced to load by /etc/modules. > > The loading of b44 is not the cause of the problem, but I would like to > understand it. Can you explain what I see? Are there any other places to look > for forced loading of modules?
Well, we got an ethernet core and ssb loads the driver for it. Broadcom should get kicked ass for designing this chip ;). I'd probably simply ignore this. We can put a workaround for it into ssb, but I'm not sure it's worth it. b44 probes and failes as the core is a dead core. We're fine. -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
