Hi Michael
I did like you wanted and wrote the following output from screen (no
digicam at hand .-(
kernel 2.6.27.9 init=/bin/bash, no modules loaded so far
modprobe b43legacy:
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 0x803 rev 0x03 vendor 0x4243)
ssb: sonics silicon backplane found on PCI device 0000:02:02.0
b43legacy-phy0: Broadcom4301 WLAN found
Broadcom 43xx-legacy driver loaded [features PLRID, Firmware-ID: FW10]
now insmod b44__.ko:
ACPI PCI INterrupt Link LNKB enabled at irq7
b44 0000:02:01.0: PCI INTA-> LNKB->GSI 7 (level,low) ->IRQ7
ssb: Core 0 found: Fast Ethernet(cc 0x806 rev 0x4 vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807 rev 0x01 vendor 0x4243)
ssb: core 2 found: PCI (cc 0x804 rev 0x02 vendor 0x4243)
ssb: sonics silicon backplane found on pci device 0000:02:01.0
b44.c: v2.0
b44: invalid mac address found in EEPROM
b44 ssb0:1: Problem fetching invariants of chip,abording
b44: Probe of ssb0:1 faild with error -22
then the system is unresponsible.
Now I did the same thing with an up and working wlan connection and
insmod b44__.ko:
...
b44 ssb0:1: Problem fetching invariants of chip,abording
b44: Probe of ssb0:1 faild with error -22
ssb: fatal error: bus powerd down while accessing PCI MMIO space
Pid:4 comm: events/0 not tainted 2.6.27.9-ud5#5
[<e0812e56>] ssb_pci_assert_buspower+0x40/0x42[ssb]
[<e08135a6>] ssb_pci_read32+0x11/0x3d [ssb]
[<e087f878>] b43legacy_interrupt_handler+0x1e/0x1f6 [b43legacy]
[<c013a25a>] handle_IRQ_event+0x25/0x4a
[<c010531a>] do_IRQ+0x44/0x78
[<c0103a3b>} common_interrupt+0x23/0x28
[<c011007b>] do_page_fault+0x2fa/0x65f
[<c0275580>] __linkwatch_run_queue+0x86/0x129
[<c0275623>] linkwatch_event+0x0/0x22
[<c0275640>] linkwatch_event+0x1d/0x22
[<c012365f>] run_workqueue+0x8b/0x103
worker_thread
worker_thread
autoremove_wake_function
worker_thread
kthread
kthread
kernek_thread_helper
============================0
you see these are two different pci ids. maybe that's the problem?
good night and bye
Ulf
Michael Buesch schrieb:
> On Friday 26 December 2008 21:54:53 Ulf Dambacher wrote:
>> At manually inserting the b44 after b43legacy I got following error
>> message on console:
>> sbb: FATAL ERROR bus powered down while accessing PCI MMIO space
>
> I'd like to see the stackdump that follows the message.
>
> go to drivers/ssb/pci.c and search this code:
>
> 573 static int ssb_pci_assert_buspower(struct ssb_bus *bus)
> 574 {
> 575 if (likely(bus->powered_up))
> 576 return 0;
> 577
> 578 printk(KERN_ERR PFX "FATAL ERROR: Bus powered down "
> 579 "while accessing PCI MMIO space\n");
> 580 if (bus->power_warn_count <= 10) {
> 581 bus->power_warn_count++;
> 582 dump_stack();
> 583 }
> 584
> 585 return -ENODEV;
> 586 }
>
> Add the following line just before the "return -ENODEV;":
> local_irq_disable(); while (1) cpu_relax();
>
> Please catch the message with a digital photocamera.
>
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
