Messages in this thread | | | Date | Mon, 29 Jan 2007 11:58:42 +0000 | From | Pavel Machek <> | Subject | Re: Bcm43xx oops after suspend to disk |
| |
Hi!
> >> Do you have the log stuff that precedes this part? In particular, was > >> there a assertion that failed? > >> > > It is oops on resume and no asseertion failled this boot. However I > > have usually a lot of > > bcm43xx: ASSERTION FAILED (radio_attenuation < 10) at: > > drivers/net/wireless/bcm43xx/bcm43xx_phy.c:1496:bcm43xx_find_lopair() > > Those are well known and do not affect this problem. > > > Moreover after the first oops I have a second oops (Surelly a > > consequence of the first). > > I think that is right. > > Unfortunately, I cannot test for this problem on my system as it doesn't suspend at all.
Can you try to debug that? swsusp is very easy to get going these days. And with minimum drivers, it tends to work very reliably. Any help I can provide?
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |