-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Buesch wrote:
> On Saturday 27 May 2006 23:19, you wrote:
>> On Thu, May 25, 2006 at 02:02:37PM +0200, Michael Buesch wrote:
>>> Uh, don't let me dangling like this. :)
>>> Could you please try to reproduce the lockup and catch
>>> an oops? It's important, because it may be caused by bcm43xx.
>> I tried this setup again, and yes, it looks like bcm43xx. I have a photo
>> of the oops here:
>>
>> http://gehennom.net/~lunz/bcm43xx_crash.jpg
>>
>> It takes an hour or two of traffic flood to reproduce the crash. Let me
>> know if you need any more information.
>
> Oh, yes. That's really an interresting oops.
> I guess the interrupt, which is used for bcm, is used by another
> device, too. Is that right? Could you show us your /proc/interrupts
> please?
> In the "interrupt-shared" case it is indeed possible to deadlock.
> I will do an updated patch, which tries to solve this.
>
[ anarchy - ~ ] cat /proc/interrupts
CPU0
0: 225952473 XT-PIC timer
1: 44163 XT-PIC i8042
2: 0 XT-PIC cascade
8: 0 XT-PIC rtc
9: 198 XT-PIC acpi
10: 17825426 XT-PIC yenta, ATI IXP, ATI IXP Modem, eth0,
bcm43xx, fglrx
11: 0 XT-PIC ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
12: 4538501 XT-PIC i8042
14: 2801404 XT-PIC ide0
15: 25 XT-PIC ide1
NMI: 63794
LOC: 225919079
ERR: 2317
MIS: 0
As you can see the interrupt is gonna be shared by more then most would
like to see. Just some info for the examining
Jory
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEecvsGDfjNg8unQIRArWbAKCXB5XJzcr9YqGqS8PGBcDX1yrLygCgqIO9
vFR67pY8qufrfqm0Yoe11os=
=8XCw
-----END PGP SIGNATURE-----
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
