http://bugzilla.kernel.org/show_bug.cgi?id=11164
------- Comment #26 from yakui.z...@intel.com 2008-12-18 18:50 -------
Hi, Lorincz
Thanks for so quick response. From the test the value of mcount is still
what we expected. As it is incorrect, I can't judge whether the suspend/resume
hangs. In such case there exist the following two possibilities:
a. Maybe the BIOS already transfers control to the pre-defined waking
vector(this works in real mode) and the OS is not resumed correctly.(In real
mode the 0xA8A8A8A8 is written to 0x21-24 RTC cmos area. The 0x20 area is not
touched.)
b. Maybe it hangs in BIOS. In such case before the system enters sleeping
state, the system jiffies will be written to 0x21-24 RTC cmos area.
When the system is restarted, the RTC cmos area of 0x20-24 is rewritten by
BIOS. As the value of mcount is incorrect, we can't know the correct value that
is written to 0x20-24 RTC cmos area.
Do you have opportunity to know which part of RTC cmos area is available
for OS?(It won't be modified by BIOS).
If so, it can be used to track whether the suspend/resume hangs.
thanks.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
