Re: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Completely disable ACPI Power Management in the ASUS BIOS and within Debian and
see if this makes a difference. From the behavior you mention this really
sounds like an ACPI problem.
Merciadri Luca put forth on 1/1/2010 6:04 AM:
> Stan Hoeppner <email@example.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?