[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45C9D930.5010307@lwfinger.net>
Date: Wed, 07 Feb 2007 07:50:40 -0600
From: Larry Finger <larry.finger@...inger.net>
To: Johannes Berg <johannes@...solutions.net>
CC: Michael Buesch <mb@...sch.de>, netdev@...r.kernel.org,
Bcm43xx-dev@...ts.berlios.de, linux-wireless@...r.kernel.org
Subject: Re: [PATCH] bcm43xx: Fix for oops on resume
Johannes Berg wrote:
> On Wed, 2007-02-07 at 07:23 -0600, Larry Finger wrote:
>
>> As you suggested earlier, a slow clock setting in the bcm43xx device may be the cause of this
>> difficulty. If my laptop would suspend/resume correctly, then I could test various fixes based on
>> that hypothesis.
>
> Mine does suspend, but I don't see the problem...
Could you please apply this patch and tell me what gets printed after you resume, and whether you
did a suspend to RAM or disk?
I welcome the results of this test from anyone whose system will suspend/resume. Please also note if
any further action is needed to get wireless communication re-established.
Thanks,
Larry
==========
Index: linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===================================================================
--- linux-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_main.c
+++ linux-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
@@ -2401,6 +2401,7 @@ static int bcm43xx_chip_init(struct bcm4
}
udelay(10);
}
+ dprintk(KERN_INFO PFX "It took %d tries to set IRQ_READY\n", i);
bcm43xx_read32(bcm, BCM43xx_MMIO_GEN_IRQ_REASON); /* dummy read */
value16 = bcm43xx_shm_read16(bcm, BCM43xx_SHM_SHARED,
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists