On Fri, Nov 12, 2004 at 05:27:38PM +0900, Horms wrote:
On Sun, Nov 07, 2004 at 01:36:04AM +0100, Joerg Morbitzer wrote:
Package: kernel-image-2.6.9-1-686
Version: 2.6.9-1
Severity: normal
Hi all,
with kernel-image 2.6.8 I could send my IBM R40 into suspend using apm and
resume
afterwards without a problem. Since using kernel-image 2.6.9-686 the
laptop still suspends and resumes, but right after the machines wakes up
it behaves really strange: all the icons on my KDE desktop flicker when
moving my mouse and using the keyboard ends into the following error
messages on the console (pressing ALT-F4):
Nov 7 01:04:38 rocket kernel: atkbd.c: Unknown key pressed (translated
set 2, code 0x66 on isa0060/serio0).
Nov 7 01:04:38 rocket kernel: atkbd.c: Use 'setkeycodes 66 keycode'
to make it known.
Nov 7 01:04:39 rocket kernel: atkbd.c: Unknown key pressed (translated
set 2, code 0x66 on isa0060/serio0).
Nov 7 01:04:39 rocket kernel: atkbd.c: Use 'setkeycodes 66 keycode'
to make it known.
Nov 7 01:04:39 rocket kernel: atkbd.c: Unknown key pressed (translated
set 2, code 0x66 on isa0060/serio0).
Nov 7 01:04:39 rocket kernel: atkbd.c: Use 'setkeycodes 66 keycode'
to make it known.
Nov 7 01:04:39 rocket kernel: atkbd.c: Unknown key pressed (translated
set 2, code 0x66 on isa0060/serio0).
Nov 7 01:04:39 rocket kernel: atkbd.c: Use 'setkeycodes 66 keycode'
to make it known.
Nov 7 01:04:39 rocket kernel: atkbd.c: Unknown key pressed (translated
set 2, code 0x66 on isa0060/serio0).
Nov 7 01:04:39 rocket kernel: atkbd.c: Use 'setkeycodes 66 keycode'
to make it known.
Only rebooting my IBM laptop solves this problem as far as I can see.
You can find the boot messages of kernel 2.6.8-686 and 2.6.9-686 here:
http://www.morbitzer.de/tmp/boot-2.6.8-686.txt
http://www.morbitzer.de/tmp/boot-2.6.9-686.txt
As I said, suspending and resuming my laptop with 2.6.8-686 works fine.
Hi,
Thanks for the bug report.
I took a quick look and unfortunately there seem to
be quite a lot of changes to atkb.c between 2.6.8 and 2.6.9.
It is a bit hard to tell which change might have caused this
problem.
The only thing I found that may help is
http://ozlabs.org/pipermail/linuxppc64-dev/2004-March/001315.html
but it seems like a long-shot at best.
I have CCed the maintainer + linux-input mailing list in
the hope of some help.
Does this still happen with 2.6.10 or 2.6.11-rc3? If yes, please use
i8042.debug=1 on the kernel command line to get a trace of the
communication with the keyboard in the kernel messages.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]