> > Actually, it is bug in both X and kernel (well, locking up is X
> > problem, but lost keypresses are kernel's).
>
> Not really, if X does a hardware cli() and then never recovers from it,
> there is nothing the kernel can do about lost keypresses or anything else.
> When the interrupts are disabled like that, the kernel is essentially
> saying "You are a trusted binary and I'm giving you access to instructions
> that can bring the whole system down, USE THEM WITH CARE!" and in response
> the X server is saying "OK, I'm disabling interrupts" and then something
> goes wrong in the X server and those interrupts never get re-enabled. So,
> the X server obviously ignored that "USE THEM WITH CARE!" part of its
> permissions the kernel allowed it to have or else the hardware did
> something the X server didn't expect and things went downhill from there.
you really should check the sources first. then you'd see that
cli() is _used_with_care_ (and for almost all current cards it's
never ever used).
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu