John Hodges wrote:
> I've just started using Linux in the last week or so. I got FC2 up and
> running without any problems, uptime of about 5 days or so, then I get
> home from work and my keyboard is not responding. My first instinct was
> to reboot
Kenneth Porter replied:
> How are you rebooting? If from a shell over the network, are there any
> messages in the log files (eg. /var/log/messages) that might suggest
> something failing?
John posted:
> I logged out of GNOME using GUI interface, since mouse worked and
> keyboard didn't. Rebooted the machine from GUI login screen for same reason.
>
> /var/log/messages contains the following entries
>
> Sep 21 19:49:24 localhost kernel: APIC error on CPU1: 00(60)
> Sep 21 19:49:24 localhost kernel: APIC error on CPU1: 60(60)
> Sep 21 20:13:57 localhost kernel: APIC error on CPU1: 60(60)
> Sep 21 20:20:40 localhost kernel: APIC error on CPU1: 60(60)
> Sep 21 20:23:53 localhost kernel: APIC error on CPU1: 60(60)
> Sep 21 22:00:37 localhost kernel: APIC error on CPU1: 60(60)
> Sep 22 04:02:03 localhost logrotate: ALERT exited abnormally with [1]
Try adding " noapic" to the end of the kernel line in
/boot/grub/grub.conf
Are your mouse and keyboard PS/2 or USB?
What does /proc/interrupts show? (It would be interesting to see a
"before and after" for the noapic change.
Is this an SMP system or a hyperthreading one?
Thanks,
James.
--
E-mail address: james | "Hardware simply does not work like the manual says
@westexe.demon.co.uk | and no amount of Zen contemplation will ever make you
| at one with a 3c905B ethernet card."
| -- Alan Cox
