http://bugzilla.kernel.org/show_bug.cgi?id=5989
------- Additional Comments From [EMAIL PROTECTED] 2006-03-23 21:48 ------- > Did you see any debug info before stopping tasks............ No, that was all there was. That makes sense though. The debug info is only in the I2RC (copy of I2RB), which is called only from THM0._TMP. With thermal polling off, there shouldn't be any calls to I2RC. Should I get rid of the UPDT and I2RB copies, and just modify I2RB itself to have the Debug objects? > I want to track the calls to I2RB, and understand if CHKS return > different. Following the depth-first strategy, let's make sure that the debug info is being printed as you want, then use it to investigate the hangs. Perhaps I'm not using the right debug_layer/level settings? 'acpi -t' will query the THM0 temperature and won't cause a hang, so I could use it to test various debug_level settings and see which ones produce the object you're looking for. Once that's settled, then I can use it on the sleep-wake cycles. > Actually, this problem is pretty wired. We need to know if last I2RB > works right before hang. I don't think I2RB (or its copy) is being called during the 2nd sleep. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
