Hi,
FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
with the 2.6.5 kernel.
It occured when I was typing some text in kmail. Everything worked just fine
except for the keyboard that was locked (dead - even capslock did not work).
Fortunately the (USB) mouse worked, so I could reboot the machine "gently" to
get my keyboard back in order.
I use RH9 with some modifications to support the 2.6.x kernels. Attached is
the .config.
Yours,
RJW
--
Rafael J. Wysocki,
SiSK
[tel. (+48) 605 053 693]
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
On Wed, 7 Apr 2004, R. J. Wysocki wrote:
> Hi,
>
> FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
> with the 2.6.5 kernel.
>
> It occured when I was typing some text in kmail. Everything worked just fine
> except for the keyboard that was locked (dead - even capslock did not work).
> Fortunately the (USB) mouse worked, so I could reboot the machine "gently" to
> get my keyboard back in order.
>
> I use RH9 with some modifications to support the 2.6.x kernels. Attached is
> the .config.
Hi,
Was anything in your logs about that?
I think that maybe you should disable PREEMPTION.
Or use different distribution than RH9. They often modify gcc and other
programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
change distribution: Gentoo works ok for me and my friends! :-)
regards
Grzegorz Kulewski
* Grzegorz Kulewski <[email protected]>:
> > FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
> > with the 2.6.5 kernel.
I've seen the very same on 2.6.5-rc3 as well!
Toshiba Satellite Pro 6100
> Was anything in your logs about that?
>
> I think that maybe you should disable PREEMPTION.
I see these problems without preemption.
> Or use different distribution than RH9. They often modify gcc and other
> programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> change distribution: Gentoo works ok for me and my friends! :-)
Debian
>From dmesg:
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte AIM. ralfpostfix
On Wed, 7 Apr 2004, Ralf Hildebrandt wrote:
> * Grzegorz Kulewski <[email protected]>:
>
> > > FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
> > > with the 2.6.5 kernel.
>
> I've seen the very same on 2.6.5-rc3 as well!
> Toshiba Satellite Pro 6100
>
> > Was anything in your logs about that?
> >
> > I think that maybe you should disable PREEMPTION.
>
> I see these problems without preemption.
>
> > Or use different distribution than RH9. They often modify gcc and other
> > programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> > 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> > change distribution: Gentoo works ok for me and my friends! :-)
>
> Debian
>
> From dmesg:
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: AT Translated Set 2 keyboard on isa0060/serio0
Did you see these messages 6 times at once? Was it after the boot process
ended? They only appear at boot time for me (just once of course). Maybe
your keyboard was disconnected or kernel was thinking that it was
disconnected and connected again?...
Grzegorz
* Grzegorz Kulewski <[email protected]>:
> On Wed, 7 Apr 2004, Ralf Hildebrandt wrote:
>
> > * Grzegorz Kulewski <[email protected]>:
> >
> > > > FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
> > > > with the 2.6.5 kernel.
> >
> > I've seen the very same on 2.6.5-rc3 as well!
> > Toshiba Satellite Pro 6100
> >
> > > Was anything in your logs about that?
> > >
> > > I think that maybe you should disable PREEMPTION.
> >
> > I see these problems without preemption.
> >
> > > Or use different distribution than RH9. They often modify gcc and other
> > > programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> > > 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> > > change distribution: Gentoo works ok for me and my friends! :-)
> >
> > Debian
> >
> > From dmesg:
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
>
> Did you see these messages 6 times at once?
No, I'm quite sure they happen sporadically. See:
# uptime
12:53:58 up 7 days, 4:14, 2 users, load average: 3.12, 2.46, 1.93
# grep "input: AT Translated Set" syslog
Apr 7 09:19:05 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:19:43 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:19:49 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:35:18 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:35:48 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:39:08 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:43:01 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 09:56:38 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 11:14:13 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 11:28:41 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 11:35:44 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 11:36:24 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 11:47:17 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
Apr 7 12:38:31 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Was it after the boot process ended?
Yes. See above.
> They only appear at boot time for me (just once of course). Maybe
> your keyboard was disconnected or kernel was thinking that it was
> disconnected and connected again?...
Nope. It's a laptop!
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte AIM. ralfpostfix
On Wed, 7 Apr 2004, Ralf Hildebrandt wrote:
> * Grzegorz Kulewski <[email protected]>:
>
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> > > input: AT Translated Set 2 keyboard on isa0060/serio0
> >
> > Did you see these messages 6 times at once?
>
> No, I'm quite sure they happen sporadically. See:
>
> # uptime
> 12:53:58 up 7 days, 4:14, 2 users, load average: 3.12, 2.46, 1.93
>
> # grep "input: AT Translated Set" syslog
> Apr 7 09:19:05 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:19:43 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:19:49 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:35:18 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:35:48 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:39:08 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:43:01 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 09:56:38 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 11:14:13 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 11:28:41 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 11:35:44 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 11:36:24 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 11:47:17 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
> Apr 7 12:38:31 hummus2 kernel: input: AT Translated Set 2 keyboard on isa0060/serio0
>
> > Was it after the boot process ended?
>
> Yes. See above.
>
> > They only appear at boot time for me (just once of course). Maybe
> > your keyboard was disconnected or kernel was thinking that it was
> > disconnected and connected again?...
>
> Nope. It's a laptop!
Ok, so it was connected (but it can still have not full electrical
contact...).
But kernel (because of some bug) can think it was reconnected and
initialize the driver second time making kb unusable... Can't it?
Grzegorz
* Grzegorz Kulewski <[email protected]>:
> > > They only appear at boot time for me (just once of course). Maybe
> > > your keyboard was disconnected or kernel was thinking that it was
> > > disconnected and connected again?...
> >
> > Nope. It's a laptop!
>
> Ok, so it was connected (but it can still have not full electrical
> contact...).
Rather unlikely, since thi snever happens with 2.4.x
> But kernel (because of some bug) can think it was reconnected and
> initialize the driver second time making kb unusable... Can't it?
Absolutely. This whole serio stuff causes nothing but grief.
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte AIM. ralfpostfix
On Wednesday 07 of April 2004 12:33, Grzegorz Kulewski wrote:
> On Wed, 7 Apr 2004, R. J. Wysocki wrote:
> > Hi,
> >
> > FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite
> > 1400-103) with the 2.6.5 kernel.
> >
> > It occured when I was typing some text in kmail. Everything worked just
> > fine except for the keyboard that was locked (dead - even capslock did
> > not work). Fortunately the (USB) mouse worked, so I could reboot the
> > machine "gently" to get my keyboard back in order.
> >
> > I use RH9 with some modifications to support the 2.6.x kernels. Attached
> > is the .config.
>
> Hi,
>
> Was anything in your logs about that?
No sign of anything related to the keyboard.
> I think that maybe you should disable PREEMPTION.
Well, maybe, but I was using all of the previous 2.6.x _with_ the preepmtion
enabled and nothing like this happened before.
> Or use different distribution than RH9. They often modify gcc and other
> programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> change distribution: Gentoo works ok for me and my friends! :-)
Look, I've been using different variants of the 2.6.x kernels on this very
machine/distro since early 2.6.0-test and I hadn't seen _anything_ like this
before 2.6.5-rc2 (then I saw something like this first). I _really_ don't
think it's a distribution-related issue.
--
Rafael J. Wysocki,
SiSK
[tel. (+48) 605 053 693]
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
On Wed, Apr 07, 2004 at 01:21:01PM +0200, R. J. Wysocki wrote:
> > Or use different distribution than RH9. They often modify gcc and other
> > programs, maybe even X - maybe try to compile your kernel on "vanilla" gcc
> > 3.3.3. I can give you a shell on computer with Gentoo and working gcc. Or
> > change distribution: Gentoo works ok for me and my friends! :-)
>
> Look, I've been using different variants of the 2.6.x kernels on this very
> machine/distro since early 2.6.0-test and I hadn't seen _anything_ like this
> before 2.6.5-rc2 (then I saw something like this first). I _really_ don't
> think it's a distribution-related issue.
Maybe you could enable debugging in i8042.c, and look at the log around
the unexpected reconnect of the keyboard.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
Ok, that should be easy to debug... I hope :-)
Try to apply this patch to check what kernel part call connect function
too many times. (Maybe it is some power management stuff?)
WARNING
It is my first "public" patch and I even not compiled it so maybe some
headers should be declared. But if it will compile and run, it should
display nice callstack in log for you for each call to this function.
happy testing
Grzegorz
--- linux-2.6.5/drivers/input/keyboard/atkbd.c.orig 2004-04-04
05:37:43.000000000 +0200
+++ linux-2.6.5/drivers/input/keyboard/atkbd.c 2004-04-07
14:23:26.719121672 +0200
@@ -679,6 +679,8 @@
{
struct atkbd *atkbd;
int i;
+
+ dump_stack();
if (!(atkbd = kmalloc(sizeof(struct atkbd), GFP_KERNEL)))
return;
RJW> FYI, I've just had a keyboard lockup on a Toshiba laptop (Satellite 1400-103)
RJW> with the 2.6.5 kernel.
I haven't tried 2.6.5 on my Toshiba yet but I had a similar problem on
my PC (Duron 600 with VIA KT-133 chipset). I was running X and the
keyboard forze, even Numlock didn't work. First time I solved it by
ending the session by mouse, this got me back to another session on VT7.
Later I had the problem on VT7 and solved it by logging in remotely and
doing "chvt 1" and "chvt 7" as root. Third time chvt didn't help either
but removing and replugging the keyboard (PS/2) worked. Mouse was USB.
--
Meelis Roos ([email protected])
On Wednesday 07 of April 2004 13:31, Grzegorz Kulewski wrote:
> Ok, that should be easy to debug... I hope :-)
>
> Try to apply this patch to check what kernel part call connect function
> too many times. (Maybe it is some power management stuff?)
>
> WARNING
> It is my first "public" patch and I even not compiled it so maybe some
> headers should be declared. But if it will compile and run, it should
> display nice callstack in log for you for each call to this function.
I've applied this and I've got something like this in the log after a (recent)
lockup:
Apr 9 10:47:03 albercik kernel: Uniform CD-ROM driver Revision: 3.20
Apr 9 10:47:03 albercik kernel: inserting floppy driver for 2.6.5
Apr 9 10:47:03 albercik kernel: Floppy drive(s): fd0 is 1.44M
Apr 9 10:47:03 albercik kernel: FDC 0 is a post-1991 82077
Apr 9 10:47:03 albercik kernel: SCSI subsystem initialized
Apr 9 10:51:11 albercik kernel: spurious 8259A interrupt: IRQ7.
Apr 9 15:00:24 albercik kernel: Call Trace:
Apr 9 15:00:24 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
Apr 9 15:00:24 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
Apr 9 15:00:24 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
Apr 9 15:00:24 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
Apr 9 15:00:24 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
Apr 9 15:00:24 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
Apr 9 15:00:24 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
Apr 9 15:00:24 albercik kernel:
Apr 9 15:00:24 albercik kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 9 15:42:19 albercik kernel: Call Trace:
Apr 9 15:42:19 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
Apr 9 15:42:19 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
Apr 9 15:42:19 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
Apr 9 15:42:19 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
Apr 9 15:42:19 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
Apr 9 15:42:19 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
Apr 9 15:42:19 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
Apr 9 15:42:19 albercik kernel:
Apr 9 15:42:19 albercik kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Apr 9 15:58:36 albercik kernel: Call Trace:
Apr 9 15:58:36 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
Apr 9 15:58:36 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
Apr 9 15:58:36 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
Apr 9 15:58:36 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
Apr 9 15:58:36 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
Apr 9 15:58:36 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
Apr 9 15:58:36 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
Apr 9 15:58:36 albercik kernel:
Here I had to reboot the machine.
--
Rafael J. Wysocki,
SiSK
[tel. (+48) 605 053 693]
----------------------------
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
-- Richard P. Feynman
On Fri, 9 Apr 2004, R. J. Wysocki wrote:
> On Wednesday 07 of April 2004 13:31, Grzegorz Kulewski wrote:
> > Ok, that should be easy to debug... I hope :-)
> >
> > Try to apply this patch to check what kernel part call connect function
> > too many times. (Maybe it is some power management stuff?)
>
> I've applied this and I've got something like this in the log after a (recent)
> lockup:
>
> Apr 9 10:47:03 albercik kernel: Uniform CD-ROM driver Revision: 3.20
> Apr 9 10:47:03 albercik kernel: inserting floppy driver for 2.6.5
> Apr 9 10:47:03 albercik kernel: Floppy drive(s): fd0 is 1.44M
> Apr 9 10:47:03 albercik kernel: FDC 0 is a post-1991 82077
> Apr 9 10:47:03 albercik kernel: SCSI subsystem initialized
> Apr 9 10:51:11 albercik kernel: spurious 8259A interrupt: IRQ7.
> Apr 9 15:00:24 albercik kernel: Call Trace:
> Apr 9 15:00:24 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
> Apr 9 15:00:24 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
> Apr 9 15:00:24 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
> Apr 9 15:00:24 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
> Apr 9 15:00:24 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
> Apr 9 15:00:24 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
> Apr 9 15:00:24 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
> Apr 9 15:00:24 albercik kernel:
> Apr 9 15:00:24 albercik kernel: input: AT Translated Set 2 keyboard on
> isa0060/serio0
> Apr 9 15:42:19 albercik kernel: Call Trace:
> Apr 9 15:42:19 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
> Apr 9 15:42:19 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
> Apr 9 15:42:19 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
> Apr 9 15:42:19 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
> Apr 9 15:42:19 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
> Apr 9 15:42:19 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
> Apr 9 15:42:19 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
> Apr 9 15:42:19 albercik kernel:
> Apr 9 15:42:19 albercik kernel: input: AT Translated Set 2 keyboard on
> isa0060/serio0
> Apr 9 15:58:36 albercik kernel: Call Trace:
> Apr 9 15:58:36 albercik kernel: [<c0277b29>] atkbd_connect+0x19/0x420
> Apr 9 15:58:36 albercik kernel: [<c027adca>] serio_find_dev+0x6a/0x70
> Apr 9 15:58:36 albercik kernel: [<c027aee9>] serio_handle_events+0xc9/0x120
> Apr 9 15:58:36 albercik kernel: [<c027af85>] serio_thread+0x45/0x140
> Apr 9 15:58:36 albercik kernel: [<c0117a40>] default_wake_function+0x0/0x20
> Apr 9 15:58:36 albercik kernel: [<c027af40>] serio_thread+0x0/0x140
> Apr 9 15:58:36 albercik kernel: [<c0105285>] kernel_thread_helper+0x5/0x10
> Apr 9 15:58:36 albercik kernel:
>
> Here I had to reboot the machine.
So we can see that atkbd_connect is called several times (and it probably
should not... - somebody correct me if I am wrong).
Apply attached patch to see what causes reconnection.
Grzegorz Kulewski
* Vojtech Pavlik <[email protected]>:
> > Look, I've been using different variants of the 2.6.x kernels on this very
> > machine/distro since early 2.6.0-test and I hadn't seen _anything_ like this
> > before 2.6.5-rc2 (then I saw something like this first). I _really_ don't
> > think it's a distribution-related issue.
>
> Maybe you could enable debugging in i8042.c, and look at the log around
> the unexpected reconnect of the keyboard.
How? Enlighten us...
--
Ralf Hildebrandt (Im Auftrag des Referat V a) [email protected]
Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte AIM. ralfpostfix
On Thu, Apr 15, 2004 at 08:54:14PM +0200, Ralf Hildebrandt wrote:
> * Vojtech Pavlik <[email protected]>:
>
> > > Look, I've been using different variants of the 2.6.x kernels on this very
> > > machine/distro since early 2.6.0-test and I hadn't seen _anything_ like this
> > > before 2.6.5-rc2 (then I saw something like this first). I _really_ don't
> > > think it's a distribution-related issue.
> >
> > Maybe you could enable debugging in i8042.c, and look at the log around
> > the unexpected reconnect of the keyboard.
>
> How? Enlighten us...
Edit i8042.c, #define DEBUG.
--
Vojtech Pavlik
SuSE Labs, SuSE CR