roucaries bastien wrote: > On 1/26/07, Larry Finger <[EMAIL PROTECTED]> wrote: >> roucaries bastien wrote: >> >> 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. >> >> Does this oops happen every time, or is it intermittent? I'm looking >> at the code to find places to >> insert debugging statements. At present, I don't understand how it >> gets to the shutdown code while >> resuming! > Perhaps because syslog log it after resume... > I will investigate this evening
Thanks. One other thing to try is booting with the 'maxcpus=1' kernel option. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
