![]() | |||||||||||||
Messages in this thread |
Hi! > If you've looked at this bug you will know that myself at and atleast > one other person experience a reboot on resume at a specific line in > the wakeup code: > http://bugme.osdl.org/show_bug.cgi?id=3586 > > One note about the code in the bug, my code for detecting PM is > backwards, so ignore it, what I say in this email is still valid. > > Specifically, if I get rid of the pushl;popl then the computer does > not reboot. See the attached diff. The question is 1) is this > pushl;popl the final nail in the coffin? 2) Does windows not clear the > flags completely, but instead sets them to some "special value"? > > The reason for (1) is because as I understand it, when a certain > number of illegal operations (3 iirc) are issued at certain times > (real mode iirc) the machine automatically reboots. That could be > what we are seeing here. You got this wrong. It is three illegal instructions but *nested*. Like error, error in fault handler, error in doublefault handler. Try replacing flags manipulation with any stack manipulation to see what is wrong. > Also, what flags are being cleared? What is their meaning? Can you > or someone on this list point me to the approriate documentation? I'd > love to look at it and try to understand my hardware better. Like perhaps processor docs? Pavel -- teflon -- maybe it is a trademark, but it should not be. - 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/ | ||||||||||||
| Last update: 2005-06-14 11:11 [from the cache] ©2003-2008 | |||||||||||||