Re: thinkpad testers wanted (was Re: 2.6.22-rc[23]: blinking capslockled, stuck keys?)

[Michael Tokarev]

Pavel Machek wrote:
[]
>>> pavel@amd:~$ while true; do setleds +num; setleds -num; done
>>> Hm,m so thiis  iis  a teest of fkeyboarad behaviour  under lloadd.
>>>
>>> ...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.
> 
> Hmm, this needs to be ran from console (not X). Can someone with
> thinkpad try this?

I don't have a thinkpad, but I tried it - just for fun - with my desktop
PC here.  And it also shows some.. strangeness.  Namely, after several
secounds, it starts spewing:

drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full
drivers/usb/input/hid-core.c: control queue full

messages on the screen on every setleds (above) invocation.  Even if I
stop the loop and execute single setleds manually, it also shows this
same message.  And the led isn't working anymore too - even if I press
NumLock key, NumLock mode activates/deactivates correctly, but not the
led -- ditto for other leds (CapsLock & ScrollLock).  And it doesn't
restore when I switch to X and back.

(My keyboard is USB-connected).

I think it's something about count of setleds/etc operations.  Rebooting
and counting from 0...

(2.6.21.3 here)

/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/