| View previous topic :: View next topic |
| Author |
Message |
ozak
n00b
Joined: 02 Jan 2004
Posts: 36
Location: USA
|
 Posted: Fri Jan 09, 2004 12:48 pm Post subject: Random freezes |
 |
|
Ok, this has been happening for a while, and I'd really like to know what's cuaseing it.
But, I'll leave my system for the night, turn the monitor off.
And when i wake up in the morning, my system has frozen, and the scroll lock, and num lock lights are flashing.
Any idea what that would be? |
|
| Back to top |
|
 |
dkaplowitz
Guru
Joined: 22 Nov 2003
Posts: 596
Location: Philadelphia, PA
|
| Posted: Fri Jan 09, 2004 12:51 pm Post subject: |
|
|
does your /var/log/messages say anything? (why not post it here, just for the hell of it).
How do you get out of the freeze? Do you have to hard boot the machine? Are you getting any errors on startup?
_________________
http://dkap.info |
|
| Back to top |
|
|
ozak
n00b
Joined: 02 Jan 2004
Posts: 36
Location: USA
|
| Posted: Fri Jan 09, 2004 1:00 pm Post subject: |
|
|
I don't have a /var/log/messages
/var/log/messages/lastlog
has a bunch of weird chars and no real info and
/var/log/everything/the onefor last night is
| Code: |
Jan 7 06:07:37 [kernel] Linux version 2.4.20-gaming-r3 (root@deadhatemachine) (gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)) #1 Mon Jan 5 06:54:07 EST 2004
Jan 7 06:07:37 [kernel] 8139too Fast Ethernet driver 0.9.26
Jan 7 06:07:37 [kernel] eth0: RealTek RTL8139 Fast Ethernet at 0xe439f000, 00:e0:18:6d:06:38, IRQ 10
Jan 7 06:07:37 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:37 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:37 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:37 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:37 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:37 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:37 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:37 [kernel] Creative EMU10K1 PCI Audio Driver, version 0.20, 07:15:19 Jan 5 2004
Jan 7 06:07:38 [kernel] parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
Jan 7 06:07:38 [kernel] eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
Jan 7 06:07:38 [kernel] parport_pc: Via 686A parallel port: io=0x378
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:38 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:38 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:38 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:38 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:38 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:39 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:39 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:39 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:39 [kernel] 8139cp: 10/100 PCI Ethernet driver v0.3.0 (Sep 29, 2002)
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: init_module: No such device
Jan 7 06:07:39 [insmod] Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o failed
Jan 7 06:07:39 [insmod] /lib/modules/2.4.20-gaming-r3/kernel/drivers/net/8139cp.o: insmod 8139cp failed
Jan 7 06:07:39 [pci.agent] ... can't load module 8139cp
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver 8139cp
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver emu10k1
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver uhci
Jan 7 06:07:39 [pci.agent] missing kernel or user mode driver parport_pc
Jan 7 06:07:45 [kernel] usb.c: registered new driver usb_mouse
Jan 7 06:07:45 [modprobe] modprobe: Can't locate module mousedev
Jan 7 06:07:51 [cron] (CRON) STARTUP (fork ok)
Jan 7 06:08:00 [login(pam_unix)] session opened for user mindrot by (uid=0)
Jan 7 06:08:01 [kernel] inserting floppy driver for 2.4.20-gaming-r3
Jan 7 06:08:01 [kernel] FDC 0 is a post-1991 82077
Jan 7 06:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 06:19:32 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 06:30:01 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 06:40:28 [kernel] keyboard: unknown scancode e0 3c
Jan 7 06:40:28 [kernel] keyboard: unknown scancode e0 3c
Jan 7 06:40:36 [login(pam_unix)] session opened for user mindrot by (uid=0)
Jan 7 06:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 06:59:48 [gconfd (root-24955)] starting (version 1.0.8), pid 24955 user 'root'
Jan 7 06:59:48 [gconfd (root-24955)] Unable to open saved state file '/root/.gconfd/saved_state': No such file or directory
Jan 7 06:59:48 [gconfd (root-24955)] Exiting
Jan 7 06:59:48 [gconfd (root-24958)] starting (version 1.0.8), pid 24958 user 'root'
Jan 7 06:59:48 [gconfd (root-24958)] Exiting
Jan 7 07:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 07:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 07:01:42 [gconfd (root-5418)] starting (version 1.0.8), pid 5418 user 'root'
Jan 7 07:01:42 [gconfd (root-5418)] Exiting
Jan 7 07:01:42 [gconfd (root-5421)] starting (version 1.0.8), pid 5421 user 'root'
Jan 7 07:01:42 [gconfd (root-5421)] Exiting
Jan 7 07:01:44 [gconfd (root-5474)] starting (version 2.4.0.1), pid 5474 user 'root'
Jan 7 07:01:44 [gconfd (root-5474)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 07:01:44 [gconfd (root-5474)] Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jan 7 07:01:44 [gconfd (root-5474)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 07:01:49 [gconfd (root-5477)] starting (version 2.4.0.1), pid 5477 user 'root'
Jan 7 07:01:49 [gconfd (root-5477)] Failed to get lock for daemon, exiting: Failed to lock '/var/tmp/portage/gconf-2.4.0.1/temp/gconfd-root/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Jan 7 07:01:49 [gconfd (root-5474)] Exiting
Jan 7 07:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 07:26:59 [gconfd (mindrot-29017)] starting (version 2.4.0.1), pid 29017 user 'mindrot'
Jan 7 07:26:59 [gconfd (mindrot-29017)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 07:26:59 [gconfd (mindrot-29017)] Resolved address "xml:readwrite:/home/mindrot/.gconf" to a writable config source at position 1
Jan 7 07:26:59 [gconfd (mindrot-29017)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 07:29:46 [gconfd (mindrot-29017)] Received signal 1, shutting down cleanly
Jan 7 07:29:46 [gconfd (mindrot-29017)] Exiting
Jan 7 07:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 07:34:03 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 07:35:03 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:03 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:03 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:03 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:03 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:24 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:24 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:24 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:24 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:35:24 [kernel] hda: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 7 07:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 08:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 08:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 08:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 08:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 08:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 09:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 09:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 09:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 09:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 09:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 10:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 10:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 10:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 10:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 10:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 11:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 11:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 11:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 11:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 11:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 12:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 12:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 12:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 12:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 12:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 13:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 13:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 13:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 13:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 13:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 14:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 14:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 14:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 14:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 14:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 15:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 15:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 15:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 15:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 15:42:21 [su(pam_unix)] session closed for user root
Jan 7 15:42:30 [gconfd (mindrot-19955)] starting (version 2.4.0.1), pid 19955 user 'mindrot'
Jan 7 15:42:30 [gconfd (mindrot-19955)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 15:42:30 [gconfd (mindrot-19955)] Resolved address "xml:readwrite:/home/mindrot/.gconf" to a writable config source at position 1
Jan 7 15:42:30 [gconfd (mindrot-19955)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 15:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 15:48:24 [gnome-name-server] starting
Jan 7 15:48:24 [gnome-name-server] name server starting
Jan 7 16:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 16:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 16:00:47 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:02:00 [su(pam_unix)] session closed for user root
Jan 7 16:03:18 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:03:37 [su(pam_unix)] session closed for user root
Jan 7 16:06:10 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:06:13 [su(pam_unix)] session closed for user root
Jan 7 16:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 16:16:45 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:27:47 [su(pam_unix)] session closed for user root
Jan 7 16:27:49 [gconfd (mindrot-19955)] Received signal 1, shutting down cleanly
Jan 7 16:27:49 [gnome-name-server] input condition is: 0x11, exiting
Jan 7 16:27:49 [gconfd (mindrot-19955)] Exiting
Jan 7 16:27:56 [gconfd (mindrot-22213)] starting (version 2.4.0.1), pid 22213 user 'mindrot'
Jan 7 16:27:56 [gconfd (mindrot-22213)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 16:27:56 [gconfd (mindrot-22213)] Resolved address "xml:readwrite:/home/mindrot/.gconf" to a writable config source at position 1
Jan 7 16:27:56 [gconfd (mindrot-22213)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 16:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 16:31:09 [gconfd (mindrot-22213)] Received signal 1, shutting down cleanly
Jan 7 16:31:10 [gconfd (mindrot-22213)] Exiting
Jan 7 16:31:11 [login(pam_unix)] session closed for user mindrot
Jan 7 16:31:15 [login(pam_unix)] session opened for user root by (uid=0)
Jan 7 16:31:21 [gconfd (root-22598)] starting (version 2.4.0.1), pid 22598 user 'root'
Jan 7 16:31:21 [gconfd (root-22598)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 16:31:21 [gconfd (root-22598)] Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jan 7 16:31:21 [gconfd (root-22598)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 16:34:15 [gconfd (root-22598)] Received signal 1, shutting down cleanly
Jan 7 16:34:16 [gconfd (root-22598)] Exiting
Jan 7 16:34:19 [login(pam_unix)] session closed for user root
Jan 7 16:34:27 [login(pam_unix)] session opened for user mindrot by (uid=0)
Jan 7 16:34:38 [gconfd (mindrot-22739)] starting (version 2.4.0.1), pid 22739 user 'mindrot'
Jan 7 16:34:38 [gconfd (mindrot-22739)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 16:34:38 [gconfd (mindrot-22739)] Resolved address "xml:readwrite:/home/mindrot/.gconf" to a writable config source at position 1
Jan 7 16:34:38 [gconfd (mindrot-22739)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 16:43:12 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:43:26 [gconfd (root-23218)] starting (version 2.4.0.1), pid 23218 user 'root'
Jan 7 16:43:26 [gconfd (root-23218)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 16:43:26 [gconfd (root-23218)] Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jan 7 16:43:26 [gconfd (root-23218)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 16:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 16:48:24 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 16:51:00 [su(pam_unix)] session closed for user root
Jan 7 16:51:26 [gconfd (root-23218)] GConf server is not in use, shutting down.
Jan 7 16:51:26 [gconfd (root-23218)] Exiting
Jan 7 16:52:15 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 17:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 17:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 17:08:02 [gconfd (root-16932)] starting (version 2.4.0.1), pid 16932 user 'root'
Jan 7 17:08:02 [gconfd (root-16932)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 17:08:02 [gconfd (root-16932)] Resolved address "xml:readwrite:/root/.gconf" to a writable config source at position 1
Jan 7 17:08:02 [gconfd (root-16932)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 17:08:08 [su(pam_unix)] session closed for user root
Jan 7 17:10:02 [gconfd (root-16932)] GConf server is not in use, shutting down.
Jan 7 17:10:02 [gconfd (root-16932)] Exiting
Jan 7 17:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 17:17:24 [su(pam_unix)] session closed for user root
Jan 7 17:17:25 [gconfd (mindrot-22739)] Received signal 1, shutting down cleanly
Jan 7 17:17:25 [gconfd (mindrot-22739)] Exiting
Jan 7 17:17:31 [gconfd (mindrot-17228)] starting (version 2.4.0.1), pid 17228 user 'mindrot'
Jan 7 17:17:31 [gconfd (mindrot-17228)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0
Jan 7 17:17:31 [gconfd (mindrot-17228)] Resolved address "xml:readwrite:/home/mindrot/.gconf" to a writable config source at position 1
Jan 7 17:17:31 [gconfd (mindrot-17228)] Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Jan 7 17:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 17:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 17:50:05 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 17:51:58 [su(pam_unix)] session closed for user root
Jan 7 17:59:52 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 18:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 18:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 18:00:37 [su(pam_unix)] session closed for user root
Jan 7 18:07:06 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 18:07:22 [su(pam_unix)] session closed for user root
Jan 7 18:12:44 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 18:12:54 [su(pam_unix)] session closed for user root
Jan 7 18:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 18:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 18:45:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 19:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 19:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 19:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 19:30:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 19:45:01 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 19:49:23 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 19:51:18 [su(pam_unix)] session opened for user root by mindrot(uid=1002)
Jan 7 19:52:14 [su(pam_unix)] session closed for user root
Jan 7 20:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Jan 7 20:00:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 7 20:15:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
|
Also, I have to hard shutdown the box, by pulling out the plug.
The power button won't even shut it off. |
|
| Back to top |
|
|
ozak
n00b
Joined: 02 Jan 2004
Posts: 36
Location: USA
|
| Posted: Fri Jan 09, 2004 7:09 pm Post subject: |
|
|
| anyone have any idea? |
|
| Back to top |
|
|
dkaplowitz
Guru
Joined: 22 Nov 2003
Posts: 596
Location: Philadelphia, PA
|
| Posted: Fri Jan 09, 2004 9:45 pm Post subject: |
|
|
| ozak wrote: | | anyone have any idea? |
I don't actually. But looking at your log there, it appears you have a lot of stuff not configured or misconfigured. A lot of modules that are supposed to be loading but are not, etc. What else is not working on your PC? Also, the hard drive errors are a little alarming to my eyes, but maybe they're no big deal.
What kind of hardware is on the box (cpu, RAM, mobo, sound card, grafix card, etc. etc.). And how much of this have you actually configured support for into the kernel?
You might also want to search the forums for certain errors your getting to see what other people did to fix them.
_________________
http://dkap.info |
|
| Back to top |
|
|
ozak
n00b
Joined: 02 Jan 2004
Posts: 36
Location: USA
|
| Posted: Fri Jan 09, 2004 11:40 pm Post subject: |
|
|
My cpu is an AMD athlon XP 1600+
mobo is an asus, but it came with the pc, and I'm not exactly sure what model.
ram is 512 mb od SDRAM PC133
Sound Card is a Sound blaster PCI
graphics is Nvidia Geforce 2 MX 400
Most of it is configured for the kernel. I'll work on those errors and see if that's whats cuaseing it.
A friend of mine said he thinks the kernel might be panicing, becuase the scroll lock lights and etc do that when it does sometimes, (well, for me too sometimes).
Thanks for the advice. |
|
| Back to top |
|
|
mr.twemlow
Tux's lil' helper
Joined: 12 Nov 2003
Posts: 90
Location: Illinois
|
| Posted: Sat Jan 17, 2004 7:00 pm Post subject: |
|
|
I seem to have the same problem. I first noticed it when trying to emerge Open Office. It took me about 4 tries, because it kept freezing, usually upon unpacking the source.
Then it started freezing when I would try to move large amounts of files. I wanted to move some music, and treid twice--it locked up both times. When I moved it in small chunks it was fine.
Now it just freezes randomly. At first I thought it had to do with disk access or using swap, but now I don't know. I'll be doing something and then there'll be a total freeze. This is a pretty new gentoo install, so I don't know what's up.
Any suggestions?
##EDIT
The last two lock ups have occured right at 45 minutes past the hour. When I look at /var/log/messages this is right after:
| Code: | Jan 17 17:45:00 abdiel CRON[1207]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Jan 17 18:02:44 abdiel syslog-ng[3195]: syslog-ng version 1.6.0rc3 starting |
I don't have any cron jobs specified. And, looking at the logs, this same command is run every 15 minutes. Could this have anything to do with it?
##EDIT AGAIN
And again, about 2 hours after the last it locked up at 7:15 this time, right after that command up there.
_________________
Get Gentoo icons: http://boxturtleme.2ya.com/gentoo-icons.xml
Gentium--A typeface for the nations: https://forums.gentoo.org/viewtopic.php?p=1351563 |
|
| Back to top |
|
|
mr.twemlow
Tux's lil' helper
Joined: 12 Nov 2003
Posts: 90
Location: Illinois
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
