Kubuntu Feisty reboots during bootup

Ashex · 05-22-2007, 11:58 PM

This has been an ongoing issue for me for a couple weeks. Kubuntu will randomly reboot during startup, it's generally a hit-and-miss. Occasionally it will just hang and I haven't really been able to isolate the issue yet.

From syslog, I pulled this from the latest occurance:

Code:

May 22 20:15:55 Phorin avahi-daemon[5085]: Registering new address record for fe80::250:56ff:fec0:1 on vmnet1.*.
May 22 20:15:55 Phorin avahi-daemon[5085]: Registering new address record for fe80::250:56ff:fec0:8 on vmnet8.*.
May 22 20:16:04 Phorin kernel: [   55.684000] vmnet1: no IPv6 routers present
May 22 20:16:04 Phorin kernel: [   55.724000] vmnet8: no IPv6 routers present
May 22 20:16:07 Phorin kdm_greet[5787]: Internal error: memory corruption detected
May 22 20:16:24 Phorin hcid[5491]: Default passkey agent (:1.12, /org/bluez/passkey_agent_6012) registered
May 22 20:16:42 Phorin gconfd (ahmed-6143): starting (version 2.18.0.1), pid 6143 user 'ahmed'
May 22 20:16:42 Phorin gconfd (ahmed-6143): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
May 22 20:16:42 Phorin gconfd (ahmed-6143): Resolved address "xml:readwrite:/home/ahmed/.gconf" to a writable configuration source at position 1
May 22 20:16:42 Phorin gconfd (ahmed-6143): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
May 22 20:16:42 Phorin gconfd (ahmed-6143): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
May 22 20:16:42 Phorin gconfd (ahmed-6143): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
May 22 20:18:52 Phorin syslogd 1.4.1#20ubuntu4: restart.

I also grabbed the events from kern.log at the same time:

Code:

May 22 20:15:43 Phorin kernel: [   33.688000] /dev/vmnet: open called by PID 5674 (vmnet-natd)
May 22 20:15:43 Phorin kernel: [   33.688000] /dev/vmnet: hub 8 does not exist, allocating memory.
May 22 20:15:43 Phorin kernel: [   33.688000] /dev/vmnet: port on hub 8 successfully opened
May 22 20:15:46 Phorin kernel: [   36.852000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 0 at 6:00.0] forgot to specify physical device; fix it!
May 22 20:15:46 Phorin kernel: [   36.856000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 1 at 6:00.0] forgot to specify physical device; fix it!
May 22 20:15:46 Phorin kernel: [   36.856000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 2 at 6:00.0] forgot to specify physical device; fix it!
May 22 20:15:52 Phorin kernel: [   43.512000] eth0: no IPv6 routers present
May 22 20:15:53 Phorin kernel: [   44.796000] /dev/vmnet: open called by PID 5792 (vmnet-netifup)
May 22 20:15:53 Phorin kernel: [   44.796000] /dev/vmnet: hub 1 does not exist, allocating memory.
May 22 20:15:53 Phorin kernel: [   44.796000] /dev/vmnet: port on hub 1 successfully opened
May 22 20:15:53 Phorin kernel: [   44.800000] /dev/vmnet: open called by PID 5793 (vmnet-netifup)
May 22 20:15:53 Phorin kernel: [   44.800000] /dev/vmnet: port on hub 8 successfully opened
May 22 20:15:53 Phorin kernel: [   44.864000] /dev/vmnet: open called by PID 5809 (vmnet-dhcpd)
May 22 20:15:53 Phorin kernel: [   44.864000] /dev/vmnet: port on hub 8 successfully opened
May 22 20:15:53 Phorin kernel: [   44.864000] /dev/vmnet: open called by PID 5815 (vmnet-dhcpd)
May 22 20:15:53 Phorin kernel: [   44.864000] /dev/vmnet: port on hub 1 successfully opened
May 22 20:16:04 Phorin kernel: [   55.684000] vmnet1: no IPv6 routers present
May 22 20:16:04 Phorin kernel: [   55.724000] vmnet8: no IPv6 routers present
May 22 20:18:52 Phorin kernel: Inspecting /boot/System.map-2.6.20-15-generic

Anyone know what would cause it to restart randomly on startup or where to look?

Matir · 05-23-2007, 12:15 AM

Odd. Nothing unusual in the logs. Does it just suddenly reboot (i.e., hard reboot) or does it act like it is doing a proper shutdown first?

Ashex · 05-23-2007, 12:23 AM

it just does a hard reboot without any warning. Is it possible that bad RAM would cause this? I don't experience random reboots after I login.

Matir · 05-23-2007, 01:24 AM

Bad RAM, bad settings/BIOS, or bad PSU could all be the culprit. Try running memtest86+ to try to rule out RAM.

Ashex · 05-23-2007, 01:46 AM

I'll give that a shot. I'll start memtest when i leave for work tomorrow.

Ashex · 05-23-2007, 07:42 PM

Memtest ran for 9.5 hours with 28 passes, and no errors popped up. I'm not sure what the cause is. I'll purchase a new power supply and replace my current one, as that would be the most likely cause I suppose (350W PSU, the system is running just shy of that amount)

friedtofu · 06-19-2007, 09:55 AM

I am experiencing a similar problem. Did you find out what the cause was? Bad PS?

My logs looks exactly the same. I was able to log on though and start rtorrent client. Does anyone know if a bad disk block or something would cause an unexpected reboot? The system will run for about an hour or 2 before it reboots. I grep the logs and it actually reboots about every 8 hours if not logged on after it reboots.

I ran memtest no long ago but I will give that a try again too to see if it reboots.

thanks