20 Sep 14:01
I need some serious help to debug suspend to ram problem
From: Maxim Levitsky <maximlevitsky <at> gmail.com>
Subject: I need some serious help to debug suspend to ram problem
Newsgroups: gmane.linux.power-management.general
Date: 2008-09-20 12:03:17 GMT
Subject: I need some serious help to debug suspend to ram problem
Newsgroups: gmane.linux.power-management.general
Date: 2008-09-20 12:03:17 GMT
Hi, I hit a dead end when trying to understand why my notebook can't resume from suspend to ram if this is done two times a row. Single suspend/resume cycle works almost perfectly (beep that goes through the sound card is muted... no morse code for me...(Continue reading)) I compiled a minimal kernel (absolutely nothing but disk drivers, all experimental option like nohz turned off) But I had to turn SMP, since without it system won't resume first time I suspend it. (How could this affect suspend?) With SMP and minimal kernel (of course no closed drivers), I get same behavior, first resume works second hangs. I then added some debug code to real mode wakeup code, I put there in first place instructions, that will save some magic value to rtc (to alarm registers that I know are preserved during boot cycle), and I discovered sad thing that first time bios does pass control to linux, but second time (when it hangs), it doesn't. I tried to update bios, and I got same results. Of course it does work with that @#$%^& OS I then proceeded to test recently posted low memory corruption patch, and it did show that that @#$%^& BIOS
)
I compiled a minimal kernel (absolutely nothing but disk drivers, all experimental option like nohz
turned off)
But I had to turn SMP, since without it system won't resume first time I suspend it.
(How could this affect suspend?)
With SMP and minimal kernel (of course no closed drivers), I get same behavior, first resume works
second hangs.
I then added some debug code to real mode wakeup code, I put there in first place instructions, that will save
some magic value to rtc (to alarm registers that I know are preserved during boot cycle), and I discovered
sad thing that first time bios does pass control to linux, but second time (when it hangs), it doesn't.
I tried to update bios, and I got same results.
Of course it does work with that @#$%^& OS
I then proceeded to test recently posted low memory corruption patch, and it did show that that @#$%^& BIOS
RSS Feed