SuSE 8.0 System rebooting unwantedly
Hello everybody, i have been looking around the support knowledge base at SuSE i am almost convinced that the reason why the system reboots unwantedly without no apparent reason is a BIOS or hardware issue. The are some lines in the system log that to a newbie like me dont look good at all, here they are: Aug 2 20:28:20 linux kernel: VFS: Disk change detected on device fd(2,0) Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-80 Aug 2 20:28:23 linux last message repeated 15 times Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-104 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-105 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-106 Aug 2 20:28:25 linux last message repeated 15 times Aug 2 20:28:25 linux modprobe: modprobe: Can't locate module block-major-107 Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,0) Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,64) I think its more of a hardware issue my PC is a: CPU: PIII 1.0 Ghz Mainboard: Gigabyte GA-6VXE7+ RAM: 512 MB SDRAM HD: hda (win 98 SE)= Seagate 80Gb ST380021A hdb (linux)= Seagate 40 Gb ST340014A Graphic card: Nvidia GeForce 3 Ti 500 Sound card: Soundblaster live 1024 NIC: SMC 1244TX So, my question is how would you go around looking for hints as to what is going on? and please if you can point out the problem i would very much appreciate it. All the best, Gabriel
On Sat, 2003-08-02 at 23:17, José Gabriel Arnewi wrote:
Hello everybody,
i have been looking around the support knowledge base at SuSE i am almost convinced that the reason why the system reboots unwantedly without no apparent reason is a BIOS or hardware issue. The are some lines in the system log that to a newbie like me dont look good at all, here they are:
Aug 2 20:28:20 linux kernel: VFS: Disk change detected on device fd(2,0)
You mounted a floppy disk
Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-80 Aug 2 20:28:23 linux last message repeated 15 times
Something you ran checked if you have an I2O connected hard drive in your system
Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-104 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-105 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-106 Aug 2 20:28:25 linux last message repeated 15 times Aug 2 20:28:25 linux modprobe: modprobe: Can't locate module block-major-107
Something you ran checked if you have a Compaq drive controller
Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,0) Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,64)
/dev/hdc and /dev/hdd got mounted. Two cd drives in your system? All in all, no signs of problems so far
On Saturday 02 August 2003 19:30, Anders Johansson wrote:
On Sat, 2003-08-02 at 23:17, José Gabriel Arnewi wrote:
Hello everybody,
i have been looking around the support knowledge base at SuSE i am almost convinced that the reason why the system reboots unwantedly without no apparent reason is a BIOS or hardware issue. The are some lines in the system log that to a newbie like me dont look good at all, here they are:
All in all, no signs of problems so far
Here you have the complete system log for today, i had an unwanted reboot a few minutes after login in (cant be more precise, unfortunately): Aug 2 19:18:34 linux syslogd 1.4.1: restart. Aug 2 19:18:37 linux insmod: Using /lib/modules/2.4.18-4GB/kernel/drivers/media/video/videodev.o Aug 2 19:18:37 linux insmod: Symbol version prefix '' Aug 2 19:18:37 linux insmod: Using /lib/modules/2.4.18-4GB/kernel/drivers/usb/ov511.o Aug 2 19:18:39 linux kernel: klogd 1.4.1, log source = /proc/kmsg started. Aug 2 19:18:39 linux kernel: Inspecting /boot/System.map-2.4.18-4GB Aug 2 19:18:39 linux kernel: Loaded 12771 symbols from /boot/System.map-2.4.18-4GB. Aug 2 19:18:39 linux kernel: Symbols match kernel version 2.4.18. Aug 2 19:18:39 linux kernel: Loaded 257 symbols from 11 modules. Aug 2 19:18:39 linux kernel: Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001) Aug 2 19:18:39 linux kernel: PCI: Found IRQ 11 for device 00:08.0 Aug 2 19:18:39 linux kernel: eth0: ADMtek Comet rev 17 at 0xd800, 00:50:BF:9E:4B:C5, IRQ 11. Aug 2 19:18:39 linux kernel: usb.c: registered new driver usbdevfs Aug 2 19:18:39 linux kernel: usb.c: registered new driver hub Aug 2 19:18:39 linux kernel: usb-uhci.c: $Revision: 1.275 $ time 14:22:01 Mar 27 2002 Aug 2 19:18:39 linux kernel: usb-uhci.c: High bandwidth mode enabled Aug 2 19:18:39 linux kernel: PCI: Found IRQ 10 for device 00:07.2 Aug 2 19:18:39 linux kernel: usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 Aug 2 19:18:39 linux kernel: usb-uhci.c: Detected 2 ports Aug 2 19:18:39 linux kernel: usb.c: new USB bus registered, assigned bus number 1 Aug 2 19:18:39 linux kernel: hub.c: USB hub found Aug 2 19:18:39 linux kernel: hub.c: 2 ports detected Aug 2 19:18:39 linux kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Aug 2 19:18:39 linux kernel: hub.c: USB new device connect on bus1/2, assigned device number 2 Aug 2 19:18:39 linux kernel: usb.c: USB device 2 (vend/prod 0x5a9/0xa511) is not claimed by any active driver. Aug 2 19:18:39 linux kernel: Linux video capture interface: v1.00 Aug 2 19:18:39 linux kernel: usb.c: registered new driver ov511 Aug 2 19:18:39 linux kernel: ov511.c: USB OV511+ camera found Aug 2 19:18:39 linux kernel: ov511.c: model: Generic Camera (no ID) Aug 2 19:18:39 linux kernel: ov511.c: Sensor is an OV7620 Aug 2 19:18:39 linux kernel: ov511.c: Device registered on minor 0 Aug 2 19:18:39 linux kernel: ov511.c: v1.50 for Linux 2.4 : OV511 USB Camera Driver Aug 2 19:18:39 linux kernel: isapnp: Scanning for PnP cards... Aug 2 19:18:39 linux kernel: isapnp: No Plug & Play device found Aug 2 19:18:39 linux kernel: IPv6 v0.8 for NET4.0 Aug 2 19:18:39 linux kernel: IPv6 over IPv4 tunneling driver Aug 2 19:18:39 linux sshd[604]: Server listening on :: port 22. Aug 2 19:18:39 linux kernel: PCI: Found IRQ 5 for device 00:09.0 Aug 2 19:18:41 linux /usr/sbin/cron[692]: (CRON) STARTUP (fork ok) Aug 2 19:18:48 linux /etc/hotplug/net.agent[606]: No HW description found ... exiting Aug 2 19:18:50 linux kernel: eth0: no IPv6 routers present Aug 2 19:19:16 linux kdm[886]: pam_unix2: session started for user josarn, service xdm pam_unix2: session finished for user root, service su Aug 2 20:28:07 linux su: (to root) josarn on /dev/pts/2 Aug 2 20:28:07 linux su: pam_unix2: session started for user root, service su Aug 2 20:28:18 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 20:28:18 linux kernel: lp0: using parport0 (polling). Aug 2 20:28:18 linux kernel: lp0: compatibility mode Aug 2 20:28:18 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 20:28:19 linux kernel: Non-volatile memory driver v1.1 Aug 2 20:28:20 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 20:28:20 linux kernel: lp0: using parport0 (polling). Aug 2 20:28:20 linux kernel: lp0: compatibility mode Aug 2 20:28:20 linux kernel: imm: Version 2.05 (for Linux 2.4.0) Aug 2 20:28:20 linux kernel: ppa: Version 2.07 (for Linux 2.4.x) Aug 2 20:28:20 linux kernel: WARNING - no ppa compatible devices found. Aug 2 20:28:20 linux kernel: As of 31/Aug/1998 Iomega started shipping parallel Aug 2 20:28:20 linux kernel: port ZIP drives with a different interface which is Aug 2 20:28:20 linux kernel: supported by the imm (ZIP Plus) driver. If the Aug 2 20:28:20 linux kernel: cable is marked with "AutoDetect", this is what has Aug 2 20:28:20 linux kernel: happened. Aug 2 20:28:20 linux kernel: VFS: Disk change detected on device fd(2,0) Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-80 Aug 2 20:28:23 linux last message repeated 15 times Aug 2 20:28:23 linux modprobe: modprobe: Can't locate module block-major-104 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-105 Aug 2 20:28:24 linux last message repeated 15 times Aug 2 20:28:24 linux modprobe: modprobe: Can't locate module block-major-106 Aug 2 20:28:25 linux last message repeated 15 times Aug 2 20:28:25 linux modprobe: modprobe: Can't locate module block-major-107 Aug 2 20:28:25 linux last message repeated 15 times Aug 2 20:28:27 linux kernel: cdrom: open failed. Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,0) Aug 2 20:28:27 linux kernel: cdrom: open failed. Aug 2 20:28:27 linux kernel: VFS: Disk change detected on device ide1(22,64) Aug 2 20:32:18 linux su: pam_unix2: session finished for user root, service su Aug 2 20:51:00 linux -- MARK -- Aug 2 20:54:07 linux su: (to root) josarn on /dev/pts/2 Aug 2 20:54:07 linux su: pam_unix2: session started for user root, service su Aug 2 20:54:07 linux su: pam_unix2: session finished for user root, service su Aug 2 20:54:07 linux su: (to root) josarn on /dev/pts/2 Aug 2 20:54:07 linux su: pam_unix2: session started for user root, service su Aug 2 20:59:00 linux /USR/SBIN/CRON[1532]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) Aug 2 21:09:42 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 21:09:42 linux kernel: lp0: using parport0 (polling). Aug 2 21:09:42 linux kernel: lp0: compatibility mode Aug 2 21:09:42 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 21:09:44 linux kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Aug 2 21:09:44 linux kernel: lp0: using parport0 (polling). Aug 2 21:09:44 linux kernel: lp0: compatibility mode Aug 2 21:09:44 linux kernel: imm: Version 2.05 (for Linux 2.4.0) Aug 2 21:09:44 linux kernel: ppa: Version 2.07 (for Linux 2.4.x) Aug 2 21:09:44 linux kernel: WARNING - no ppa compatible devices found. Aug 2 21:09:44 linux kernel: As of 31/Aug/1998 Iomega started shipping parallel Aug 2 21:09:44 linux kernel: port ZIP drives with a different interface which is Aug 2 21:09:44 linux kernel: supported by the imm (ZIP Plus) driver. If the Aug 2 21:09:44 linux kernel: cable is marked with "AutoDetect", this is what has Aug 2 21:09:44 linux kernel: happened. Aug 2 21:09:47 linux modprobe: modprobe: Can't locate module block-major-80 Aug 2 21:09:48 linux last message repeated 15 times Aug 2 21:09:48 linux modprobe: modprobe: Can't locate module block-major-104 Aug 2 21:09:48 linux last message repeated 15 times Aug 2 21:09:48 linux modprobe: modprobe: Can't locate module block-major-105 Aug 2 21:09:49 linux last message repeated 15 times Aug 2 21:09:49 linux modprobe: modprobe: Can't locate module block-major-106 Aug 2 21:09:49 linux last message repeated 15 times Aug 2 21:09:49 linux modprobe: modprobe: Can't locate module block-major-107 Aug 2 21:09:50 linux last message repeated 15 times Aug 2 21:09:51 linux kernel: cdrom: open failed. Aug 2 21:09:51 linux kernel: VFS: Disk change detected on device ide1(22,0) Aug 2 21:09:51 linux kernel: cdrom: open failed. Aug 2 21:09:51 linux kernel: VFS: Disk change detected on device ide1(22,64) Aug 2 21:17:59 linux su: pam_unix2: session finished for user root, service su Aug 2 21:31:00 linux -- MARK -- Aug 2 21:40:25 linux kdm[1088]: pam_unix2: session finished for user josarn, service xdm Aug 2 21:43:19 linux kdm[1870]: pam_unix2: session started for user josarn, service xdm Aug 2 21:46:40 linux su: (to root) josarn on /dev/pts/2 Aug 2 21:46:40 linux su: pam_unix2: session started for user root, service su Aug 2 21:46:40 linux su: pam_unix2: session finished for user root, service su Aug 2 21:46:40 linux su: (to root) josarn on /dev/pts/2 Aug 2 21:46:40 linux su: pam_unix2: session started for user root, service su Aug 2 21:46:44 linux su: pam_unix2: session finished for user root, service su Aug 2 21:46:57 linux su: (to root) josarn on /dev/pts/2 Aug 2 21:46:57 linux su: pam_unix2: session started for user root, service su Aug 2 21:46:57 linux su: pam_unix2: session finished for user root, service su Aug 2 21:46:57 linux su: (to root) josarn on /dev/pts/2 Aug 2 21:46:57 linux su: pam_unix2: session started for user root, service su
José Gabriel Arnewi wrote:
Hello everybody,
i have been looking around the support knowledge base at SuSE i am almost convinced that the reason why the system reboots unwantedly without no apparent reason is a BIOS or hardware issue. The are some lines in the system log that to a newbie like me dont look good at all, here they are:
I had a similar thing about a month ago. My system would reboot at random times, it was just after I had put some more ram in so I originally suspected that. But it continued after removing it so I ended up taking my pc apart, cleaning it of dust (power supply too - only if you are competent to do so) then reassembling making sure everything was correctly seated and plugged in. Everything has been fine since, with the additional ram too. Steve -- Linux merlin 2.4.19-4GB #2 Tue Dec 17 22:14:48 GMT 2002 i686 unknown 8:30pm up 24 days, 12:37, 4 users, load average: 0.18, 0.40, 0.34
José Gabriel Arnewi wrote:
Hello everybody,
i have been looking around the support knowledge base at SuSE i am almost convinced that the reason why the system reboots unwantedly without no apparent reason is a BIOS or hardware issue. The are some lines in the system log that to a newbie like me dont look good at all, here they are:
As a thought only. What about a bad connection on the power supply pins and or the power suppy itself. A drop of the 5 Volt supply would reset it to reboot. I would re-seat the CPU and memory just for the heck of it. Then when the board gets hot (after running awhile) use a pencil eraser or plastic stick to push on the board to see if it is a foil related problem. Besides once Linux/SuSE is up the BIOS is not used. -- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.net
participants (4)
-
Anders Johansson -
Donn aka n5xwb Washburn -
José Gabriel Arnewi -
Stephen