--On Wednesday, September 22, 2004 7:25 AM -0400 John Hodges <j.d.hodges@xxxxxxxxxxxx> 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
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?
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]
This last, clearly, is while I was sleeping. The following are from when I tried to reboot this morning
Sep 22 07:10:23 localhost gconfd (john-2526): Exiting
Sep 22 07:10:23 localhost gconfd (john-6703): starting (version 2.6.0), pid 6703 user 'john'
Sep 22 07:10:23 localhost gconfd (john-6703): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Sep 22 07:10:23 localhost gconfd (john-6703): Resolved address "xml:readwrite:/home/john/.gconf" to a writable config source at position 1
Sep 22 07:10:23 localhost gconfd (john-6703): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Sep 22 07:10:24 localhost shutdown: shutting down for system reboot
Sep 22 07:10:24 localhost init: Switching to runlevel: 6
Sep 22 07:10:25 localhost gdm(pam_unix)[2431]: session closed for user john
Sep 22 07:10:27 localhost gpm[2075]: O0o.oops(): [console.c(83)]:
Sep 22 07:10:27 localhost gpm[2075]: Opening console failed.
Sep 22 07:10:30 localhost init: open(/dev/console): Input/output error
Sep 22 07:10:30 localhost messagebus: messagebus -TERM succeeded
Sep 22 07:10:31 localhost atd: atd shutdown succeeded
Sep 22 07:10:31 localhost cups: cupsd shutdown succeeded
Sep 22 07:10:31 localhost xfs[2128]: terminating
Sep 22 07:10:31 localhost xfs: xfs shutdown succeeded
Sep 22 07:10:31 localhost gpm: gpm shutdown failed
Sep 22 07:10:31 localhost sshd: sshd -TERM succeeded
Sep 22 07:10:31 localhost sendmail: sendmail shutdown succeeded
Sep 22 07:10:31 localhost xfs: xfs shutdown succeeded
Here is the only failure
Sep 22 07:10:31 localhost gpm: gpm shutdown failed Sep 22 07:10:31 localhost sshd: sshd -TERM succeeded
Note the date on this next line...
Sep 21 07:10:31 localhost sendmail: sendmail shutdown succeeded
Sep 22 07:10:31 localhost sendmail: sm-client shutdown succeeded
Sep 22 07:10:31 localhost smartd[1781]: smartd received signal 15: Terminated
Sep 22 07:10:31 localhost smartd[1781]: smartd is exiting (exit status 0)
Sep 22 07:10:31 localhost smartd: smartd shutdown succeeded
Sep 22 07:10:32 localhost xinetd[2010]: Exiting...
Sep 22 07:10:32 localhost xinetd: xinetd shutdown succeeded
Sep 22 07:10:32 localhost acpid: acpid shutdown succeeded
Sep 22 07:10:32 localhost crond: crond shutdown succeeded
Sep 22 07:10:32 localhost dd: 1+0 records in
Sep 22 07:10:32 localhost dd: 1+0 records out
Sep 22 07:10:32 localhost random: Saving random seed: succeeded
Sep 22 07:10:32 localhost rpc.statd[1660]: Caught signal 15, un-registering and exiting.
Sep 22 07:10:32 localhost nfslock: rpc.statd shutdown succeeded
Sep 22 07:10:33 localhost portmap: portmap shutdown succeeded
Sep 22 07:10:33 localhost kernel: Kernel logging (proc) stopped.
Sep 22 07:10:33 localhost kernel: Kernel log daemon terminating.
Sep 22 07:10:34 localhost syslog: klogd shutdown succeeded
Sep 22 07:10:34 localhost exiting on signal 15
Sorry to post this flood of junk, but I really don't know what to look for here. The two entries I pointed out seem to be the only anomalies, but they also seem to be after the fact (ie. keyboard had already stopped working by the time I was trying to reboot.)
