Johannes Berg wrote: > On Tue, 2007-02-06 at 11:39 -0600, Larry Finger wrote: >> There is a kernel oops on bcm43xx when resuming due to an overly tight timeout loop. > > Come to think of it... Is there any chance of fixing the actual oops > that happens in this case? I can imagine broken hardware or firmware > that causes this as well and we don't really want to oops in that case > either... That's why we have the timeout in the first place, to not hang > there forever. > > Nothing against this patch though. 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. Since it does not, I think the band-aid approach is warranted. A proper fix is still on my agenda; however, getting full data rates still has priority. Larry - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
