GumbyNoTalent
June 4th, 2009, 02:06 AM
messages.log
Jun 4 04:28:13 xxxxxxxxx -- MARK --
Jun 4 04:30:44 xxxxxxxxx kernel: [474959.951010] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 04:43:31 xxxxxxxxx kernel: [475725.971203] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 05:00:00 xxxxxxxxx kernel: [476713.876115] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 05:12:51 xxxxxxxxx kernel: [477484.354637] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
The system is a IBM x3250, Xeon 2.0Ghz, 4GB memory, 2xSATA 160GB Raid 1, the system is in a rack and connected to a HP 4 port KVM PS2 mouse and keyboard and VGA.
OS is Ubuntu 8.04.1 Server plain with SSH server nothing else and is up to date (2.6.24-19-server).
Any ideas?
EDIT :: Additional Information
I detached the KVM for 2 hours and in that time there are no messages, so the KVN was sending a signal that caused the messages ?
Jun 4 04:28:13 xxxxxxxxx -- MARK --
Jun 4 04:30:44 xxxxxxxxx kernel: [474959.951010] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 04:43:31 xxxxxxxxx kernel: [475725.971203] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 05:00:00 xxxxxxxxx kernel: [476713.876115] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
Jun 4 05:12:51 xxxxxxxxx kernel: [477484.354637] atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.
The system is a IBM x3250, Xeon 2.0Ghz, 4GB memory, 2xSATA 160GB Raid 1, the system is in a rack and connected to a HP 4 port KVM PS2 mouse and keyboard and VGA.
OS is Ubuntu 8.04.1 Server plain with SSH server nothing else and is up to date (2.6.24-19-server).
Any ideas?
EDIT :: Additional Information
I detached the KVM for 2 hours and in that time there are no messages, so the KVN was sending a signal that caused the messages ?