[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stan Hoeppner <stan@hardwarefreak.com> writes:

> What keyboard layout and system language are you using?
I am using a belgian keyboard (azerty) with be-fr layout.
>  Does the KB only lock
> up after a power management (i.e. sleep) event or screen saver engaging, or does
> it lock up while you are typing?
It always locks once the screen saver has been engaged.


Sorry to mention this so late, but, once the keyboard is blocked this
way, there is no interface (except the mouse) which would allow me to
communicate with the PC. For example, once the KB has blocked, moving
the mouse is OK, but even pushing the ON/OFF's chassis' button gives
nothing, when it turns the PC off if the KB is not blocked (I
configured it like this).

Furthermore, I tried various network things with my laptop. I have UPS
stuff, and the UPS network exchanges are still OK (i.e. the desktop PC
reads on USBs for the UPS, and share the info with my network, even
when the keyboard is blocked). Nevertheless, SSH services are, once
the keyboard is blocked, completely frozen, i.e.

$ ssh merciadriluca@merciadriluca-desktop

gives me nothing, when it directly works if the KB is not blocked.
Evidently, the PC still answers to pings, and that is quite normal, as
it still communicates with the network (except for pings).

Really strange, isn't it?

HTH.

- -- 
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAks95NAACgkQM0LLzLt8MhxR2wCdH51f8Xolag7RQsZP195tflrk
7dcAnibpUEj0oRaMT0uwGVLdLcN9EKTc
=SWnq
-----END PGP SIGNATURE-----


Reply to: