Michael,

I decided to give the mb tree another go and pulled your latest (as of about 
00:00 GMT on 06-03).
When I boot, I get the following in dmesg:

ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243)
ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243)
ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243)
ssb: Switching to ChipCommon core, index 0
ssb: Switching to PCI-E core, index 3
ssb: Switching to USB 1.1 Host core, index 2   <=========== What's this??????

Unable to handle kernel NULL pointer dereference at 00000000000002d0 RIP:
 [<ffffffff8812fcfd>] :usbcore:usb_create_hcd+0x3b/0xe8
PGD 3e792067 PUD 3ed66067 PMD 0
Oops: 0002 [1] SMP
CPU 0
Modules linked in: ide_cd ohci1394 bcm43xx_mac80211 firmware_class cdrom 
mac80211 ieee1394 forcedeth
ohci_hcd cfg80211 ehci_hcd sdhci mmc_core i2c_nforce2 snd_hda_intel 
snd_hda_codec snd_pcm snd_timer
usbcore snd soundcore ssb snd_page_alloc ext3 mbcache jbd edd sg fan sata_nv 
libata amd74xx thermal
processor sd_mod scsi_mod ide_disk ide_core
Pid: 1795, comm: modprobe Not tainted 2.6.21-rc1-mb-g034cca79-dirty #2
RIP: 0010:[<ffffffff8812fcfd>]  [<ffffffff8812fcfd>] 
:usbcore:usb_create_hcd+0x3b/0xe8
RSP: 0000:ffff81003e039968  EFLAGS: 00010286
RAX: ffff81003d8d1178 RBX: ffff81003d8d1178 RCX: 0000000000000000
RDX: ffff81003dece498 RSI: ffff81003d8d1170 RDI: ffff81003d8d11f0
RBP: ffff81003e039988 R08: 0000000000000000 R09: ffff81003d8d1178
R10: 0000000000000001 R11: ffff810037f06730 R12: 0000000000000000
R13: ffffffff881fe340 R14: 0000000000000220 R15: ffff81003e4a7730
FS:  00002af2e87af6f0(0000) GS:ffffffff80505000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000000002d0 CR3: 000000003d939000 CR4: 00000000000006e0
Process modprobe (pid: 1795, threadinfo ffff81003e038000, task ffff81003ef82100)
Stack:  00000000fffffff4 ffff81003eb03028 ffff81003eb03028 0000000000000000
 ffff81003e0399b8 ffffffff881fcad3 ffffffff88200e80 ffff81003eb03028
 ffffffff88200eb8 ffff81003e04de30 ffff81003e0399d8 ffffffff88106266
Call Trace:
 [<ffffffff881fcad3>] :ohci_hcd:ssb_ohci_probe+0x58/0x105
 [<ffffffff88106266>] :ssb:ssb_device_probe+0x40/0x59
 [<ffffffff8035314f>] really_probe+0xce/0x162
 [<ffffffff80353291>] driver_probe_device+0xae/0xba
 [<ffffffff8035329d>] __device_attach+0x0/0xb
 [<ffffffff803532a6>] __device_attach+0x9/0xb
 [<ffffffff8035243e>] bus_for_each_drv+0x47/0x7d
 [<ffffffff80353336>] device_attach+0x6a/0x7e
 [<ffffffff80352389>] bus_attach_device+0x24/0x4c
 [<ffffffff803510d7>] device_add+0x459/0x630
 [<ffffffff802ead5f>] __spin_lock_init+0x31/0x52
 [<ffffffff803512c7>] device_register+0x19/0x1e
 [<ffffffff88105435>] :ssb:ssb_attach_queued_buses+0x154/0x24b
 [<ffffffff88105fad>] :ssb:ssb_bus_register+0x159/0x1b6
 [<ffffffff8810605d>] :ssb:ssb_bus_pcibus_register+0x1e/0x20
 [<ffffffff88107a43>] :ssb:ssb_pcihost_probe+0x7b/0xb0
 [<ffffffff802f3221>] pci_device_probe+0x4c/0x74
 [<ffffffff8035314f>] really_probe+0xce/0x162
 [<ffffffff80353291>] driver_probe_device+0xae/0xba
 [<ffffffff803533dd>] __driver_attach+0x93/0xd3
 [<ffffffff8035334a>] __driver_attach+0x0/0xd3
 [<ffffffff80352559>] bus_for_each_dev+0x49/0x7a
 [<ffffffff80352f8d>] driver_attach+0x1c/0x1e
 [<ffffffff803528d5>] bus_add_driver+0x78/0x19c
 [<ffffffff80353662>] driver_register+0x85/0x89
 [<ffffffff802f3412>] __pci_register_driver+0x95/0xd1
 [<ffffffff8810791f>] :ssb:ssb_pcihost_register+0x37/0x39
 [<ffffffff880a801a>] :bcm43xx_mac80211:bcm43xx_init+0x1a/0x50
 [<ffffffff80254014>] sys_init_module+0x15e9/0x1744
 [<ffffffff802bcc73>] dnotify_parent+0x28/0x73
 [<ffffffff8823bc93>] :mac80211:ieee80211_rx_irqsafe+0x0/0x6c
 [<ffffffff803d3f82>] trace_hardirqs_on_thunk+0x35/0x37
 [<ffffffff80209fae>] system_call+0x7e/0x83


Code: 49 89 84 24 d0 02 00 00 e8 fa 5b 1b f8 fc 48 8d 7b 20 31 c0
RIP  [<ffffffff8812fcfd>] :usbcore:usb_create_hcd+0x3b/0xe8
 RSP <ffff81003e039968>
CR2: 00000000000002d0

Is this problem related to the earlier discussion in the mailing list? If so, 
please ignore the noise.

Larry


_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to