the
problem goes away if I increase BADNESS_LIMIT to 20 in bcm43xx_main.c.
Therefore, my guess is that the new locking strategy isn't
preempt-safe. (I haven't tested a non-preemptable kernel though.)
--
Peter Osterlund - [EMAIL PROTECTED]
http://web.telia.com/~u89404340
Peter Osterlund [EMAIL PROTECTED] writes:
Michael Buesch [EMAIL PROTECTED] writes:
On Friday 04 August 2006 01:31, Peter Osterlund wrote:
Ivan Matveich [EMAIL PROTECTED] writes:
[interface works fine for a few hours, then this spontaneously happens]
[note: the computer does
Hacking options enabled
* and most important, with bcm43xx debugging enabled.
Unfortunately, it doesn't help on my computer. With current
wireless-2.6 tree, I see the same behavior as I reported before, ie
transmit timed out, followed by controller RESET and ksoftirqd
using 100% CPU.
--
Peter
);
bcm43xx_mac_suspend(bcm);
--
Peter Osterlund - [EMAIL PROTECTED]
http://web.telia.com/~u89404340
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
