Hey there,
My system froze up today and I’m a little concerned that there is something wrong with my hardware. What logs should i check if it happens again?
Got openSUSE 12.2
On 11/27/2012 05:46 PM, illusi0n wrote:
>
> Hey there,
>
> My system froze up today and I’m a little concerned that there is
> something wrong with my hardware. What logs should i check if it happens
> again?
> Got openSUSE 12.2
>
>
you don’t have to wait, some of the logs from the freeze are probably
still available…
view /var/log/messages
each line begins with a date/time stamp…just look around the time of
the freeze…
and, please if you post again on this describe what you mean when you
say “froze up”…that is, could you move the mouse but clicking on
stuff didn’t work…or, did the keyboard LEDs flash…or, did the
screen turn black…or did the screen just remain totally constant
including the mouse pointer or or or or or
and, while ‘frozen’ did you try to press and hold Ctrl+Alt and then
momentary press F2? if so, what happened–if you see a log in prompt log
in as your self and type in ‘top’ and come back and tell us what was at
the top of top consuming all your cpu cycles…
and, when you say ‘frozen’ how long did you wait to see if it thawed out
(we can’t see you machine, and can’t assess what “frozen” means to you.
oh, and tell us why you suspect hardware? have you been having other
problems?
oh2, did this freeze issue begin after a kernel change? or other
update/upgrade?
–
dd
Hey dd,
helpful as always 
I just had a fixed frame of my desktop, mouse movements were not recognized. I didn’t think about ctrl+alt+f2 but I tried ctrl+alt+backspace isn’t it similar?
I just had a nasty hardware failure a year ago and it took me awhile to find the cause so that’s why I was a little bit concerned and thought please not again.
As far as software goes, it might have been an ati driver problem since i recently installed catalyst 12.11 beta, now i downgraded to 12.10 via atiupgrade again, so hopefully no more problems.
On 11/27/2012 07:26 PM, illusi0n wrote:
> hopefully no more problems
right! let us know if it comes up again…
–
dd
On 2012-11-27 19:26, illusi0n wrote:
> I didn’t think about ctrl+alt+f2 but I tried
> ctrl+alt+backspace isn’t it similar?
No. The first switches to one of the virtual terminals, and you can go
back to the graphical session by typing ctrl-alt-f7. Try all Fs, all work.
The second kills and restarts the graphical session.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Thanks man, will try ctrl+alt+f2 in case it happens again.
On 2012-11-28 20:46, illusi0n wrote:
> Thanks man, will try ctrl+alt+f2 in case it happens again.
Try it just now to find out how it works. It doesn’t kill anything. Just
remember that …F7 returns. Also, if you switch to another user, you
can go back and forth on both users on F7 and F8.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I tried it robin it works, thanks
Unfortunately the machine stopped wroking in the night again, when i tried ctrl+alt+f7 nothing happened. The clock on the computer showed ~23:30 so here is the content of messages in this time period up to the reboot
Nov 28 21:25:38 linux-rtmu dbus-daemon[778]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 21:27:11 linux-rtmu su: (to root) micha on /dev/pts/6
Nov 28 21:55:38 linux-rtmu dbus-daemon[778]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 21:55:38 linux-rtmu dbus-daemon[778]: helper(pid 23637): launched job udisks-helper-ata-smart-collect on /dev/sda
Nov 28 21:55:38 linux-rtmu dbus-daemon[778]: helper(pid 23637): completed with exit code 0
Nov 28 21:55:38 linux-rtmu dbus-daemon[778]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 22:25:38 linux-rtmu dbus-daemon[778]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 22:25:38 linux-rtmu dbus-daemon[778]: helper(pid 23717): launched job udisks-helper-ata-smart-collect on /dev/sda
Nov 28 22:25:38 linux-rtmu dbus-daemon[778]: helper(pid 23717): completed with exit code 0
Nov 28 22:25:38 linux-rtmu dbus-daemon[778]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 22:41:35 linux-rtmu su: (to root) micha on /dev/pts/6
Nov 28 22:41:35 linux-rtmu su: (to root) micha on /dev/pts/6
Nov 28 22:55:38 linux-rtmu dbus-daemon[778]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 22:55:38 linux-rtmu dbus-daemon[778]: helper(pid 24101): launched job udisks-helper-ata-smart-collect on /dev/sda
Nov 28 22:55:38 linux-rtmu dbus-daemon[778]: helper(pid 24101): completed with exit code 0
Nov 28 22:55:38 linux-rtmu dbus-daemon[778]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 23:25:38 linux-rtmu dbus-daemon[778]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 28 23:25:38 linux-rtmu dbus-daemon[778]: helper(pid 24417): launched job udisks-helper-ata-smart-collect on /dev/sda
Nov 28 23:25:38 linux-rtmu dbus-daemon[778]: helper(pid 24417): completed with exit code 0
Nov 28 23:25:38 linux-rtmu dbus-daemon[778]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1c.7/0000:05:00.0/0000:06:06.0/0000:0a:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sda
Nov 29 06:56:08 linux-rtmu rsyslogd: [origin software="rsyslogd" swVersion="5.10.1" x-pid="834" x-info="http://www.rsyslog.com"] start
On 2012-11-29 07:06, illusi0n wrote:
> Unfortunately the machine stopped wroking in the night again, when i
> tried ctrl+alt+f7 nothing happened. The clock on the computer showed
> ~23:30 so here is the content of messages in this time period up to the
> reboot
Nothing interesting there, I think. 
If you leave the computer running while you away and it hangs, leave it
at VT10 (type ctrl-alt-f10).
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Thanks for the suggestion robin, will keep it in mind for the future but I hope I’ve found the problem.
It was probably a cpu cooling issue.