Oh great, more issues.

[Red Squirrel]

I had to do some electrical on the same circuit my PC is on so I just shut it down normally and did what had to be done. When I turned it back on, the keyboard did not work. So had to reboot, then it worked. Couple hours later while playing minecraft the whole system just locked right up for no reason. Cursor and all, completely frozen. Had to hit reset. When it came back there was no sound. Rebooted again, it hung on the grub menu, but when I hit enter it went through.

It seems everything is working normal now, but WTF is this about? Any way to diagnose what caused this to ensure it never happens again? Running Kubuntu (whatever is the newest version as of a few months ago, not sure how to check which I have). I have not updated in a while so not an update that caused it. In fact, that's another thing, I keep getting prompted saying there's updates, but no way to actually initiate it.

 

[lxskllr]

Dunno about the logging. maybe poke around in /var/log to see if anything interesting shows up. To update, I'm pretty sure Kubuntu uses Ubuntu Software center. Use that, or one of the apt tools to update.

 

[MrChad]

I'm not a Linux expert, but those sound like hardware issues to me. A bad power supply or motherboard, perhaps?

 

[Red Squirrel]

That's what I'm afraid of... I think I'll just have to bite the bullet and replace everything. (cheaper than trying to replace 1 part at a time and pay for shipping each time). When I look back this system has been nothing but trouble, even when I had windows 7. Though I thought all those issues went away when I switched to ATI. The nvidia drivers were causing tons of issues even in Windows.

I was hoping to save up to build a new server though. My current server is on it's last legs.



Also seeing TONS of random errors in /var/log/syslog. Don't know what time this happened exactly but wonder if it could all be related:

Dec  2 00:33:12 falcon kernel: [    0.669630] ioapic: probe of 0000:00:05.4 failed with error -22
Dec  2 00:33:12 falcon kernel: [    0.669637] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Dec  2 00:33:12 falcon kernel: [    0.669644] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Dec  2 00:33:12 falcon kernel: [    0.669674] intel_idle: MWAIT substates: 0x21120
Dec  2 00:33:12 falcon kernel: [    0.669675] intel_idle: v0.4 model 0x2D
Dec  2 00:33:12 falcon kernel: [    0.669676] intel_idle: lapic_timer_reliable_states 0xffffffff
Dec  2 00:33:12 falcon kernel: [    0.669724] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Dec  2 00:33:12 falcon kernel: [    0.669728] ACPI: Power Button [PWRB]
Dec  2 00:33:12 falcon kernel: [    0.669748] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Dec  2 00:33:12 falcon kernel: [    0.669749] ACPI: Power Button [PWRF]
Dec  2 00:33:12 falcon kernel: [    0.669855] ACPI: Requesting acpi_cpufreq
Dec  2 00:33:12 falcon kernel: [    0.670965] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.670969] ACPI Error: Method parse/execution failed [\_SB_.C000._TPC] (Node ffff88031e483938), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.672061] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.672064] ACPI Error: Method parse/execution failed [\_SB_.C001._TPC] (Node ffff88031e488708), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.673152] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.673154] ACPI Error: Method parse/execution failed [\_SB_.C002._TPC] (Node ffff88031e48c4d8), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.674222] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.674225] ACPI Error: Method parse/execution failed [\_SB_.C003._TPC] (Node ffff88031e4902a8), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.675313] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.675315] ACPI Error: Method parse/execution failed [\_SB_.C004._TPC] (Node ffff88031e494078), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.676412] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.676415] ACPI Error: Method parse/execution failed [\_SB_.C005._TPC] (Node ffff88031e497e38), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.677497] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.677499] ACPI Error: Method parse/execution failed [\_SB_.C006._TPC] (Node ffff88031e49bc08), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.678606] ACPI Error: [\TST0] Namespace lookup failure, AE_NOT_FOUND (20121018/psargs-359)
Dec  2 00:33:12 falcon kernel: [    0.678610] ACPI Error: Method parse/execution failed [\_SB_.C007._TPC] (Node ffff88031e49f9d8), AE_NOT_FOUND (20121018/psparse-537)
Dec  2 00:33:12 falcon kernel: [    0.681331] GHES: HEST is not enabled!

Later on there are TONS of these, about 2000 lines worth:

Dec  2 00:33:23 falcon udevd[632]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [837]
Dec  2 00:33:23 falcon udevd[632]: '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [837] terminated by signal 9 (Killed)
Dec  2 00:33:23 falcon udevd[627]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [846]
Dec  2 00:33:23 falcon udevd[627]: '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [846] terminated by signal 9 (Killed)
Dec  2 00:33:23 falcon udevd[621]: timeout '/sbin/blkid -o udev -p /dev/ram2'
Dec  2 00:33:23 falcon udevd[668]: timeout: killing '/sbin/modprobe -bv dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:' [900]
Dec  2 00:33:23 falcon udevd[662]: timeout '/sbin/blkid -o udev -p /dev/ram7'
Dec  2 00:33:23 falcon udevd[783]: timeout: killing 'console-setup-tty /dev/tty3' [906]
Dec  2 00:33:23 falcon udevd[630]: timeout '/sbin/blkid -o udev -p /dev/sda'
Dec  2 00:33:23 falcon udevd[617]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [836]
Dec  2 00:33:23 falcon udevd[624]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [840]
Dec  2 00:33:23 falcon udevd[624]: '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [840] terminated by signal 9 (Killed)

Dec  2 00:33:23 falcon udevd[613]: timeout '/sbin/blkid -o udev -p /dev/ram11'
Dec  2 00:33:23 falcon udevd[773]: timeout: killing 'console-setup-tty /dev/tty4' [908]
Dec  2 00:33:23 falcon udevd[778]: timeout: killing 'console-setup-tty /dev/tty5' [909]
Dec  2 00:33:24 falcon udevd[662]: timeout: killing '/sbin/blkid -o udev -p /dev/ram7' [902]
Dec  2 00:33:24 falcon udevd[668]: timeout: killing '/sbin/modprobe -bv dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:' [900]
Dec  2 00:33:24 falcon udevd[621]: timeout: killing '/sbin/blkid -o udev -p /dev/ram2' [893]
Dec  2 00:33:24 falcon udevd[783]: timeout: killing 'console-setup-tty /dev/tty3' [906]
Dec  2 00:33:24 falcon udevd[630]: timeout: killing '/sbin/blkid -o udev -p /dev/sda' [911]
Dec  2 00:33:24 falcon udevd[617]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [836]
Dec  2 00:33:24 falcon udevd[613]: timeout: killing '/sbin/blkid -o udev -p /dev/ram11' [912]
Dec  2 00:33:24 falcon udevd[773]: timeout: killing 'console-setup-tty /dev/tty4' [908]
Dec  2 00:33:24 falcon udevd[778]: timeout: killing 'console-setup-tty /dev/tty5' [909]
Dec  2 00:33:24 falcon sm-notify[1076]: nsm_parse_reply: [0x529a895d] RPC status 1
Dec  2 00:33:25 falcon udevd[621]: timeout: killing '/sbin/blkid -o udev -p /dev/ram2' [893]
Dec  2 00:33:25 falcon udevd[668]: timeout: killing '/sbin/modprobe -bv dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:' [900]
Dec  2 00:33:25 falcon udevd[662]: timeout: killing '/sbin/blkid -o udev -p /dev/ram7' [902]
Dec  2 00:33:25 falcon udevd[783]: timeout: killing 'console-setup-tty /dev/tty3' [906]
Dec  2 00:33:25 falcon udevd[630]: timeout: killing '/sbin/blkid -o udev -p /dev/sda' [911]
Dec  2 00:33:25 falcon udevd[617]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [836]
Dec  2 00:33:25 falcon udevd[613]: timeout: killing '/sbin/blkid -o udev -p /dev/ram11' [912]
Dec  2 00:33:25 falcon udevd[773]: timeout: killing 'console-setup-tty /dev/tty4' [908]
Dec  2 00:33:25 falcon udevd[778]: timeout: killing 'console-setup-tty /dev/tty5' [909]
Dec  2 00:33:26 falcon udevd[621]: timeout: killing '/sbin/blkid -o udev -p /dev/ram2' [893]
Dec  2 00:33:26 falcon udevd[668]: timeout: killing '/sbin/modprobe -bv dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:' [900]
Dec  2 00:33:26 falcon udevd[662]: timeout: killing '/sbin/blkid -o udev -p /dev/ram7' [902]
Dec  2 00:33:26 falcon udevd[783]: timeout: killing 'console-setup-tty /dev/tty3' [906]
Dec  2 00:33:26 falcon udevd[630]: timeout: killing '/sbin/blkid -o udev -p /dev/sda' [911]
Dec  2 00:33:26 falcon udevd[617]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0000:family:0006:model:002D:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0087,0088,0089,008D,008E,008F,0091,0092,0093,0094,0095,0097,0098,0099,009A,009B,009C,00C0,00E0,00E1,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104#012' [836]
Dec  2 00:33:26 falcon udevd[613]: timeout: killing '/sbin/blkid -o udev -p /dev/ram11' [912]

I'm wondering if that's when it locked up. Seems about right.

 

[SOFTengCOMPelec]

I had to do some electrical on the same circuit my PC is on so I just shut it down normally and did what had to be done.

The power supply does not fully shut down (the standby voltage continues, I think), so that if you leave the PC plugged in, it could get hit with whatever you were doing to the electrics.
So it could be that your motherboard and/or power supply are now damaged/faulty (educated guess).

If it was me, I would be tempted to try a Linux boot Live CD/DVD, such as Ubuntu, and either leave it running and/or surf the internet with it, and see if it still plays up. (To differentiate between the existing Linux on the HDD issues, and actual hardware problems).

(Obviously this reply is guess work, and could easily be wrong).

 

[Red Squirrel]

The power supply does not fully shut down (the standby voltage continues, I think), so that if you leave the PC plugged in, it could get hit with whatever you were doing to the electrics.
So it could be that your motherboard and/or power supply are now damaged/faulty (educated guess).

If it was me, I would be tempted to try a Linux boot Live CD/DVD, such as Ubuntu, and either leave it running and/or surf the internet with it, and see if it still plays up. (To differentiate between the existing Linux on the HDD issues, and actual hardware problems).

(Obviously this reply is guess work, and could easily be wrong).

How would that work? I turned off the breaker, the PC but not the UPS, so the UPS was constantly supplying power to the PSU, and all I was doing with electrical was removing a string of lights from a junction box that's on the same circuit, that would not do anything electrically on the line given the power is off.

I guess if this starts happening a lot I can do the live CD route, but this is the first time in months that I have an issue so I can't imagine running off a live CD for that long.

 

[SOFTengCOMPelec]

How would that work? I turned off the breaker, the PC but not the UPS, so the UPS was constantly supplying power to the PSU, and all I was doing with electrical was removing a string of lights from a junction box that's on the same circuit, that would not do anything electrically on the line given the power is off.

I guess if this starts happening a lot I can do the live CD route, but this is the first time in months that I have an issue so I can't imagine running off a live CD for that long.

Sorry if I misunderstood what you were saying. I did not notice/know that you were using an UPS for this computer.

Linux installs can easily/sometimes break (in my experience), which usually causes a problem(s), which remain until it is either sorted out, or Linux has been re-installed again.
In my experience the problem(s) are usually specific (e.g. It refuses to print), rather than effecting many different things, at different times, like you are experiencing.
Hence the worry that it may be hardware related.

Are you overclocking at all, on the problematic machine ?

 

[Red Squirrel]

Sorry if I misunderstood what you were saying. I did not notice/know that you were using an UPS for this computer.

Linux installs can easily/sometimes break (in my experience), which usually causes a problem(s), which remain until it is either sorted out, or Linux has been re-installed again.
In my experience the problem(s) are usually specific (e.g. It refuses to print), rather than effecting many different things, at different times, like you are experiencing.
Hence the worry that it may be hardware related.

Are you overclocking at all, on the problematic machine ?

Nope no overclock. Though now that I think about it think I did increase voltage to the ram a tad a while back while troubleshooting all my issues.

 

[SOFTengCOMPelec]

Nope no overclock. Though now that I think about it think I did increase voltage to the ram a tad a while back while troubleshooting all my issues.

Usually Linux is very good at NOT crashing so badly that you need to reset/re-boot. If it does crash that badly, it is often a hardware problem.
It might be worth checking your ram overnight, with memtest86 or similar.
Ram tends to be relatively unreliable, compared to some other things, such as your cpu failing.

 

[scoob8000]

Usually Linux is very good at NOT crashing so badly that you need to reset/re-boot. If it does crash that badly, it is often a hardware problem.
It might be worth checking your ram overnight, with memtest86 or similar.
Ram tends to be relatively unreliable, compared to some other things, such as your cpu failing.

This. It does sound hardware related.

Do you have a good UPS that does voltage regulation? If not get one with the next build.

 

[Red Squirrel]

I'm pretty sure my UPS has AVR, it's older though, it's an Ultra.

What hardware would you look at replacing first? Motherboard? I may as well just brute force this and fix this computer once and for all. Though I really don't have the money right now...

The other day anything I typed felt like it was on a 1200 baud terminal, rebooted, now it's ok. Just seems I get so many weird random issues.

 

[jae]

I would put my money on bad motherboard. When a motherboard goes, a lot times you get random issues that point to different hardware. Unplug all components except PSU, 1stick of RAM and video card ( unless you integrated video). Boot up a Live CD and see how it performs.

Also you should test your RAM

 

[scoob8000]

Run memtest86 overnight on the memory first to rule that out. If it checks out okay, then I'd go with motherboard.

 

[Red Squirrel]

Yeah did memtest before. though this motherboard is really weird, it will lock up all the time, but if I disable legacy USB support, then it works and passes with flying colours. I can't explain that, makes no sense to me. I think it probably really is the motherboard. Now that I'm not trying to do SLI I will also have more choice of motherboards (I only had like two choices at the time as most LGA2011 NCIX had did not have enough slots). Though if I buy a new motherboard that means I have to buy new ram too... motherboards are more picky about ram these days and you have to check the compatibility list. Almost tempting to just buy a prebuilt system. For the price of a new motherboard and ram I can practically get a full working prebuilt system, especially if I wait till boxing day.

 

[theevilsharpie]

It looks like you have a piece of hardware that is locking up and causing your kernel to hang.

In my experience, most hardware hangs that didn't result in a complete hard-lock (i.e., the system is incredibly slow but still somewhat interactive) have been storage-related.

 

[Red Squirrel]

It looks like you have a piece of hardware that is locking up and causing your kernel to hang.

In my experience, most hardware hangs that didn't result in a complete hard-lock (i.e., the system is incredibly slow but still somewhat interactive) have been storage-related.

Hmm, I do have an OCZ vertex 3, I know those are hit and miss... Could it be that? That would be cheaper and easier than the motherboard, maybe I should replace that first. I already have a secondary drive in there with Windows on it, so even if I just do a swap. Think I will start with that. Since I swapped the video cards my issues have been 1% of what I had before, so it's going to be hard to tell right away if it fixes it or not so may as well start with the cheapest/easiest option first. Though deep down I am really starting to think it is in fact the motherboard.

 

[jae]

Hmm, I do have an OCZ vertex 3, I know those are hit and miss... Could it be that? That would be cheaper and easier than the motherboard, maybe I should replace that first. I already have a secondary drive in there with Windows on it, so even if I just do a swap. Think I will start with that. Since I swapped the video cards my issues have been 1% of what I had before, so it's going to be hard to tell right away if it fixes it or not so may as well start with the cheapest/easiest option first. Though deep down I am really starting to think it is in fact the motherboard.

Instead of just flat out replacing it, why don't you just unplug the SSD and run Windows to see if it locks up?

Also, did you unplug all the unnecessary component and try to boot with an live flash drive/cd? This would include unplugging your hard drives.

 

[Red Squirrel]

Instead of just flat out replacing it, why don't you just unplug the SSD and run Windows to see if it locks up?

Also, did you unplug all the unnecessary component and try to boot with an live flash drive/cd? This would include unplugging your hard drives.

The issues don't happen often enough to do that, this is the first time in maybe 6 months that I have any issues. Though, before I switched to ATI I did have issues in Windows too. The Nvidia driver would randomly crash and all the monitors would turn off and then back on and I'd get an error that the driver crashed and recovered. Though now days I only go in Windows to game and have not had any issues since. Live CDs don't work very well on this system, the screen constantly flickers and it's enough to drive any sane person mad, and if there is a way to catch epilepsy, it's probably this way. Though that was also solved when I switched to ATI as when I installed Kubuntu with the live CD I did not have that issue.

As of now this was a one time issue since all the changes I made, so I'm wondering if maybe it was isolated, though, it's still pretty serious for it to outright lock up like that. Never had lockups in windows during the time I have used it though, but I'm not in there often, as it's not setup for anything but a few games.

I wonder how hard it would be to setup minecraft to run off a live CD. I suppose I could try playing it through a live CD to see if it still happens, as it was during Minecraft that it locked up. I've been busy with other stuff so I have not been doing much on my PC other than occasional gaming and web browsing so now is probably the best time to experiment before I get back into real work.

 

[slashbinslashbash]

1) memtest86, overnight. You say you did it "before", was that before this problem? If so then do it again. Just because your RAM was good 2 months ago does not mean that it is good today.

2) Flash your BIOS to the latest version. If it's already on the latest version, flash to an older version, then re-flash back to the latest version. Some of those error messages relate to the BIOS. Could be a sign of a bad motherboard or just some fixable corruption in the BIOS.

 

[jae]

I wonder how hard it would be to setup minecraft to run off a live CD. I suppose I could try playing it through a live CD to see if it still happens, as it was during Minecraft that it locked up. I've been busy with other stuff so I have not been doing much on my PC other than occasional gaming and web browsing so now is probably the best time to experiment before I get back into real work.

Install a distro on a external HDD or 16-32GB flash drive, then install minecraft.

 

[scoob8000]

1) memtest86, overnight. You say you did it "before", was that before this problem? If so then do it again. Just because your RAM was good 2 months ago does not mean that it is good today.

That's a good point too. Let it run for more than just a few hours. I've seen a few bad sticks that are okay for one or two passes then begin to fail.

It could still just be a buggy motherboard, I've seen plenty of those.

 

[Red Squirrel]

FUCK. Did it again. Guess it's going to start giving me hell again . I thought I had fixed all my issues. I'm strongly debating on just getting a Dell and calling it a day... I just want a computer that works period. No time to deal with crap like this.

Running off a live CD or other distro for a long period of time is just unrealistic, I have stuff to do. Think I'll just get a Dell or something and call it a day. Maybe try a new motherboard first. But that also means new ram, unless I can get lucky enough that the ram I have is on the HCL for the new motherboard, but the odds are quite slim especially with my luck. I just want a computer that works, so I can move on to actual work instead of running around trying to troubleshoot this crap.


This is the syslog at what I assume is the time it crashed (2:36) as there is a time gap. 4:12 is when I hit reset so I'm guessing that's the startup stuff.

Dec 18 13:46:16 falcon dhclient: bound to 10.1.2.10 -- renewal in 3033 seconds.
Dec 18 13:46:16 falcon NetworkManager[1413]: <info> (eth0): DHCPv4 state changed renew -> renew
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   address 10.1.2.10
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   prefix 16 (255.255.0.0)
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   gateway 10.1.1.1
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   hostname 'falcon'
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   nameserver '10.1.1.10'
Dec 18 13:46:16 falcon NetworkManager[1413]: <info>   domain name 'firewall.loc'
Dec 18 13:46:16 falcon dbus[1227]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 18 13:46:16 falcon dbus[1227]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 18 14:05:01 falcon CRON[10607]: (root) CMD (ntpdate borg.loc)
Dec 18 14:05:07 falcon CRON[10606]: (CRON) info (No MTA installed, discarding output)
Dec 18 14:17:01 falcon CRON[11314]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Dec 18 14:36:49 falcon dhclient: DHCPREQUEST of 10.1.2.10 on eth0 to 10.1.1.1 port 67 (xid=0x1e115a25)
Dec 18 14:36:49 falcon dhclient: DHCPACK of 10.1.2.10 from 10.1.1.1
Dec 18 14:36:49 falcon dhclient: bound to 10.1.2.10 -- renewal in 2993 seconds.
Dec 18 14:36:49 falcon NetworkManager[1413]: <info> (eth0): DHCPv4 state changed renew -> renew
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   address 10.1.2.10
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   prefix 16 (255.255.0.0)
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   gateway 10.1.1.1
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   hostname 'falcon'
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   nameserver '10.1.1.10'
Dec 18 14:36:49 falcon NetworkManager[1413]: <info>   domain name 'firewall.loc'
Dec 18 14:36:49 falcon dbus[1227]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 18 14:36:49 falcon dbus[1227]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 18 16:12:39 falcon kernel: imklog 5.8.11, log source = /proc/kmsg started.
Dec 18 16:12:39 falcon rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1025" x-info="http://www.rsyslog.com"] start
Dec 18 16:12:39 falcon rsyslogd: rsyslogd's groupid changed to 103
Dec 18 16:12:39 falcon rsyslogd: rsyslogd's userid changed to 101
Dec 18 16:12:39 falcon rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Dec 18 16:12:39 falcon kernel: [    0.000000] Initializing cgroup subsys cpuset
Dec 18 16:12:39 falcon kernel: [    0.000000] Initializing cgroup subsys cpu
Dec 18 16:12:39 falcon kernel: [    0.000000] Linux version 3.8.0-19-generic (buildd@allspice) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8)
Dec 18 16:12:39 falcon kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=e3887d9d-3649-4da7-9dec-b303b75d16ad ro quiet splash vt.handoff=7
Dec 18 16:12:39 falcon kernel: [    0.000000] KERNEL supported cpus:
Dec 18 16:12:39 falcon kernel: [    0.000000]   Intel GenuineIntel
Dec 18 16:12:39 falcon kernel: [    0.000000]   AMD AuthenticAMD
Dec 18 16:12:39 falcon kernel: [    0.000000]   Centaur CentaurHauls
Dec 18 16:12:39 falcon kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Dec 18 16:12:39 falcon kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
Dec 18 16:12:39 falcon kernel: [    0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
Dec 18 16:12:39 falcon kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

I don't really see anything that looks like an error. This is what makes troubleshooting this crap so hard, it's so random and so spaced out.

Is there some kind of debug mode in Linux that would give me more details on what causes the freezes? At least it could maybe help provide info on if it's the motherboard, or something else. What about CPU, can those go bad? That would be easier to replace than the motherboard so I could maybe start with that if it's likely to be that. Think I'll just have to bite the bullet and do the whole motherboard though. That's basically building a whole new machine at that point though.

Even debating on getting a cheap server from Dell, HP, or IBM etc.... At least it will be ECC ram and server grade so it should be more reliable than consumer crap.

 

[ch33zw1z]

Have you already tried a different hard drive? What have you done so far?

1. Try a different hard drive for the install
2. Memtest86+, at least 24 hours. I recommend more in your case. I've had sticks that won't fail for days...literally days. then you get an error.
3. Have you tried a different PSU? I've had a bad PSU that Windows would BSoD, but linux would lock up.
4. Yes, CPU's can go bad. Rare, but possible.

Buying a server from Dell, HP, IBM puts you in a different ball game.

 

[lxskllr]

You've had almost 3 weeks up time. That's not terrible. It's not like it's crashing several times per day, so you have some breathing space to try things.

Have you updated Kubuntu yet? If not, do that. Then check for BIOS updates for your MB. Install if necessary, then sit tight. If it crashes again, decide what you want to do about it. You seem to be constrained by shipping, but the first thing I'd try is a PS. That can be used in a new build if it isn't the problem, so you aren't really throwing money away. After that, I don't know. depends on how you want to proceed. It feels like a power issue to me. Either the PS, or the way the MB is dealing with it.

What are your exact system specs? Is it getting old, or is some of it worth keeping?

 

[Red Squirrel]

Tried many ram tests and cpu tax tests and all are ok, though that's another thing, this system has a weird issue where the memtest will just lock up if legacy USB is enabled. I don't know why, found this out by trial and error. But if I turn it off or use an older version, it's fine. I have not tried it for more than 12-20h though. Next time I'm on night shifts I will try it for the whole set of shifts, as it's the only time were I go more than one day without using the computer.

The fact that it does not happen often is what makes it hard to troubleshoot, as I can spend a ton of money to replace something, only to find out months down the line that it was spent for nothing, then have to spend more to try something else. Just makes the whole process so discouraging.

I probably spent over 3 grand on this machine since it was built a year or so ago.

The specs are:

cpu: i7-3820 CPU @ 3.60GHz
ram: 12GB of ram (I forget exact brand/specs, is there a way to check?)
OS drive: 1x OCZ vertex 3 for OS drive
GPU: ATI Radeon 7870
Motherboard: X79-UD3
Only one monitor at this point (LG E2442TC)

Fairly basic system. I used to have an nvidia card and had WAY more frequent issues, so I was hoping changing it would eliminate ALL issues, while it did eliminate most, it did not eliminate all as this random freezing just started to happen now.

I keep getting a prompt to update kubuntu, but nothing ever happens when I click on it. In fact I don't think any system updates at all have been applied. When I click on the notice it just makes it go away it does not actually give me any option to do it now or later.