On 6/4/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
Hi!
> > Are you sure that it's this dummy blink driver that makes the kernel
> > stuck? I can't see how it could be causing any hogs - see commit f038f9.
> >
> > Anyway, added Andi to CC.
>
> Hmm, in theory it could be triggering bugs in some buggy keyboard
> controller. But then a
>
> while true ; do setleds +caps +numlock ; sleep 1 ; setleds -caps -numlock ;
> sleep 1 ; done
>
> should trigger it too.
...and it does.
[EMAIL PROTECTED]:~$ while true; do setleds +num; setleds -num; done
Hm,m so thiis iis a teest of fkeyboarad behaviour under lloadd.
[EMAIL PROTECTED]:~$
...but I'm not quite sure it is a buggy keyboard. It happens _way_ too
often. Launch the line above and try to do some typing...
This used to work fine on my box last time I tried it (the switch
itself is offloaded to a keventd and shoud not get in the way) but
then they push all kind of ACPI/SMM crap together with KBC so who
knows... I should try it again when I get home.
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
