On Saturday 21 January 2006 20:21, Larry Finger wrote: > My interface has been losing the WPA_PSK connection with my AP. The symptoms > are a "Failed to > syspend mac!" message followed by a transmit error. I think the error happens > because the hardware > is left in an illegal state. I put a printk before each of the calls to > bcm43xx_mac_suspend, and > found that failed attempt comes from periodic_work1. The following sequence > occurs in my logs: > > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Calling bcm43xx_mac_suspend from periodic_work1 > "bcm43xx": Failed to suspend mac! > "bcm43xx": XMIT ERROR > "bcm43xx": Generic Reason: 0x00044d80 > "bcm43xx": DMA reasons: 0x00000000, 0x00000000, 0x00000000, 0x00000000 > "bcm43xx": DMA TX status: 0x00002000, 0x63002630, 0x00002000, 0x00002000 > DEAUTH from AP > > Obviously, not every call to periodic_work1 fails. It seems as if something > is not thread safe and > the error depends on getting some kind of critical timing. Is this a case of > a missing spinlock > somewhere? > > Is there a macro that would cause the kernel to dump stack like happens when > there is a kernel oops?
dump_stack() > I tried the BUG() macro but that just dumped eip and the loaded madules, then > the machine hung. > > Larry -- Greetings Michael.
pgplhfyF4IRJv.pgp
Description: PGP signature
