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. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
