-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2016-02-12 at 18:46 +0100, Per Jessen wrote:
Did you wait 10-15minutes after the first blank screen turns up? Once I got the cmdline changed to "noresume", it was easy tell when it stalled again and then get it going by pressing Enter. I now have ssh access and the system seems to be working normally - I don't know if that is because the network interface keeps generating interrupts.
Years ago I had problems with a machine that would simply stop. The screen would freeze, the clock would stop moving. But move the mouse, hit a key, and the clock would jump the lost seconds (or minutes) and everything normal. It happened after a kernel update, and we never found the cause in bugzilla. The solution was to permanently have another machine ping this one every few seconds, to awake it. Ethernet activity causes interrupts, and this broke the spell. I still have the hardware, though. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAla/P/8ACgkQtTMYHG2NR9U2dACeMYVxyrYHPwN3Gx151cERMUHq ToQAn2PsM0Nw6TL+KeyOBhzsA2JIligH =yuj9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org