Mint 13 system locking up, what's the next move?

skunkarific · 08-23-2014, 05:57 PM

Output of dmesg |less:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.2.0-64-generic (buildd@kissel) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #97-Ubuntu SMP Wed Jun 4 22:04:21 UTC 2014 (Ubuntu 3.2.0-64.97-generic 3.2.59)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic root=UUID=b0356e31-e000-4e2b-8686-692f4903ac75 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfdf0000 (usable)
[ 0.000000] BIOS-e820: 00000000cfdf0000 - 00000000cfdf3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000cfdf3000 - 00000000cfe00000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000cfe00000 - 00000000cff00000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 000000082f000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
:

Output of grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.824] (II) Loading extension MIT-SCREEN-SAVER

Output of less /var/log.messages
/var/log.messages: No such file or directory

business_kid · 08-24-2014, 01:37 PM

Bah! didn't spot my typo. That should have been

Code:

less /var/log/messages

you will see stuff from that! usually I hit the "End" key and page back looking for an error.

But we are finding nothing. This could be software, or usb issues - even the $@#£! mouse. See if you can divide and conquer in some way. I am presuming you notice no error in the logs when you try the above command.

Another thing is to update the system, if there are any updates. If there was a bug, they may have fixed it.