Strange complete system freeze with no log messages

samjh · 2009-12-11 12:41:16

After the latest pacman -Syu, I've been having problems with hard freezes which leave no error messages on any of the log files in /var/log.

I have checked /var/log/everything.log, errors.log, Xorg.0.log, dmesg.log, kernel.log, and messages.log, but none of them indicate any problems.

In the three occasions when the system has frozen, it has occurred when I press the "enter" key (twice while browsing the web, and once in gnome-terminal), but pressing the "enter" key does not always freeze the system. In particular, it has not been a problem when logging in via GDM.

...

OK, the system crashed twice again after pressing enter while typing this post. Now, I'm resorting to copying and pasting new lines.

As I've already said, log files show no errors or any messages which indicate this sort of problem. The screen simply freezes, there is no hard-drive activity, there is no response to keyboard or mouse inputs, I cannot switch to other tty screens. Unfortunately, my keyboard doesn't have lights for numlock, etc., so I cannot do the keyboard lights trick to check for kernel panic.

This all happened just after the most recent package upgrade, so I'll post which packages were upgraded here:
[2009-12-11 10:47] synchronizing package lists
[2009-12-11 10:47] starting full system upgrade
[2009-12-11 10:59] upgraded heimdal (1.2.1-7 -> 1.3.1-2)
[2009-12-11 10:59] upgraded libcups (1.4.2-1 -> 1.4.2-2)
[2009-12-11 10:59] upgraded cups (1.4.2-1 -> 1.4.2-2)
[2009-12-11 10:59] upgraded enchant (1.5.0-1 -> 1.5.0-2)
[2009-12-11 10:59] upgraded evolution-data-server (2.28.1-1 -> 2.28.1-2)
[2009-12-11 10:59] upgraded gen-init-cpio (2.6.17-3 -> 2.6.32-1)
[2009-12-11 10:59] upgraded ghostscript (8.70-2 -> 8.70-3)
[2009-12-11 10:59] upgraded tdb (3.4.3-3 -> 3.4.3-4)
[2009-12-11 10:59] upgraded smbclient (3.4.3-3 -> 3.4.3-4)
[2009-12-11 10:59] upgraded gnome-vfs (2.24.2-1 -> 2.24.2-2)
[2009-12-11 10:59] upgraded gstreamer0.10-bad (0.10.17-2 -> 0.10.17-3)
[2009-12-11 10:59] upgraded neon (0.28.6-1 -> 0.28.6-2)
[2009-12-11 10:59] upgraded gstreamer0.10-bad-plugins (0.10.17-2 -> 0.10.17-3)
[2009-12-11 10:59] upgraded gtk2 (2.18.3-2 -> 2.18.4-1)
[2009-12-11 10:59] >>please run /usr/sbin/cups-genppdupdate
[2009-12-11 10:59] >>and restart cups deamon
[2009-12-11 10:59] upgraded gutenprint (5.2.4-1 -> 5.2.4-2)
[2009-12-11 10:59] upgraded kbd (1.15-2 -> 1.15.1-1)
[2009-12-11 10:59] upgraded libburn (0.7.2.pl01-1 -> 0.7.4.pl00-1)
[2009-12-11 10:59] upgraded libcddb (1.3.2-1 -> 1.3.2-1.1)
[2009-12-11 10:59] upgraded libv4l (0.6.3-1 -> 0.6.3-2)
[2009-12-11 10:59] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2009-12-11 10:59] upgraded pacman-mirrorlist (20090616-1 -> 20091206-1)
[2009-12-11 10:59] upgraded pm-utils (1.2.6.1-1 -> 1.2.6.1-2)
[2009-12-11 10:59] upgraded subversion (1.6.6-1 -> 1.6.6-2)
[2009-12-11 10:59] upgraded telepathy-glib (0.9.1-1 -> 0.9.2-1)
[2009-12-11 10:59] upgraded xorg-server (1.7.2-2 -> 1.7.3-1)

Any ideas?

Last edited by samjh (2009-12-11 12:41:49)

MadTux · 2009-12-11 16:37:15

There was an upgrade of xorg-server, which may (or may not) cause the problems. Can you give some more details about your system?

samjh · 2009-12-12 00:08:47

I've just force-reinstalled xorg-server 1.7.2 (couldn't remove 1.7.3, due to nvidia dependency) from /var/cache/pacman/pkg. It seems to have solved the freeze, so the issue definitely seems to be with the 1.7.3 upgrade.

My system specs:
Arch x86_64
NVidia 9600GT (running the proprietary driver)
Gnome 2.28

There is no compiz-fusion or other fancy things running on my Gnome setup. It's very vanilla.

Last edited by samjh (2009-12-12 07:12:37)

samjh · 2009-12-12 07:24:12

I've found a work-around to this issue: place gdm as the last daemon in the DAEMONS list in /etc/rc.conf

Interestingly, that is the same work-around for when X crashed and sent users back to GDM in xorg-server 1.7.1 and 1.7.2. That crash used to also happen when the enter key was pressed.

See here: http://bbs.archlinux.org/viewtopic.php?id=84374

Bug reported: http://bugs.archlinux.org/task/17472

Last edited by samjh (2009-12-12 07:41:50)

Schnaaki · 2009-12-16 08:36:22

I have exactly the same problem on my notebook...

Pressing "enter" in xorg-server 1.7.3 sometimes causes a hard system freeze.

Using xorg-server 1.7.1 sends me back to GDM - but only once. After relogging this bug doesn't reappear.
The workaround using gdm as last daemon in rc.conf doesn't solve this problem.

Any other suggestions?

Velophile · 2009-12-18 13:42:49

Hi, I was getting a similar issue; intermittent lockups/freezes always preceded by hitting the enter key and with nothing (I could find) in the log files. I got round the problem by switching to the -ck kernel (2.6.32) from AUR. It's been in use for a day now and no lockups.

Last edited by Velophile (2009-12-18 13:43:45)

vimex · 2009-12-20 21:25:42

Velophile wrote:

Hi, I was getting a similar issue; intermittent lockups/freezes always preceded by hitting the enter key and with nothing (I could find) in the log files. I got round the problem by switching to the -ck kernel (2.6.32) from AUR. It's been in use for a day now and no lockups.

I am still suffering from the issue. Even I install the kernel26-ck

It should be the problem of xorg. I did not encounter this problem when I was in the console

Last edited by vimex (2009-12-20 21:27:16)

Velophile · 2009-12-21 09:55:47

Seems I was a be premature in thinking it was fixed, it locked up a couple of times last night so I've shifted GDM to the end of the DAEMONS list in rc.conf, see if that helps.

saka · 2009-12-21 11:04:04

hmm. i got a same problem .. sometime when i press enter, the system return to gdm, i've shifted the GDM to the end of DAEMONS array, but the problem still exist.

so i just remove gdm.. login from console and start the gnome using startx.. until now there is no more problem when i hit enter.

Last edited by saka (2009-12-21 11:04:51)

vimex · 2009-12-21 18:43:41

really? I will try to remove the gdm daemon

Velophile · 2009-12-22 09:03:23

Turns out it *could* be because of KMS, which I have enabled so if (re)moving GDM doesn't do the trick I guess trying without KMS is worth a shot.

fyi: http://bbs.archlinux.org/viewtopic.php?id=85983

libmcCain · 2009-12-22 13:54:45

I have same problem, total system freeze, I have to hard reboot. Since finding this thread I noticed it might also happen after pressing Enter.

Happened after system upgrade, but then again I didn't upgrade for 6month so I wouldn't know the incriminated package.
I tried the gdm at last but didn't work, I will test starttx from console to see.

thieveshonor · 2009-12-23 07:16:46

I am also having this problem. At first I thought it might have been a flash issue since it seemed to happen whenever I was on a webpage. Lately I've noticed that it happens when I hit the enter button. It also doesn't seem to matter what applications I have open. It also appears to happen randomly. Maybe twice in an hour, but then it won't happen again for a few days. I've tried removing gdm from /etc/rc.conf. I'll monitor it for a few days and see if anything happens. I would be glad to hear if someone can come up with a solid solution.

graysky · 2009-12-23 10:12:22

Either of you guys try running memtest86+?

Velophile · 2009-12-23 10:23:31

I have, when I first started getting the problem, it didn't throw anything up though I can try again later just to make sure.

TBH, I'd kind of assumed it's not a problem with that as the Ubuntu install I've had on there for a year has never had this problem, arch has done it pretty much from install day, which was only a week or so ago. I'll try memtest86+ and I'll try running without KMS as I suspect the problem started during the initial setup when I turned KMS on and installed Plymouth.

thieveshonor · 2009-12-23 22:14:38

@graysky: I ran memtest over night on my system. When I checked it in the morning there were no errors. I also checked the hardrives. Again, no errors.

vimex · 2009-12-29 08:09:03

I downgrade the kernel26 kernel26-firmware kernel-headers, glibc and its dependents, xf86-input-evdev, xf86-video-vesa, xorg-server to the versions before 30 NOV....

and the gdm should be the last one in the DAEMON line ...

it seems ok now....Jesus Christ..

I will never upgrade the system any more.....

It does not freeze any more, but.. it will go back to the gdm screen..maybe I have to downgrade more...faint

Last edited by vimex (2009-12-29 08:18:48)

Sojek · 2009-12-29 20:10:47

What if I don't use gdm? Shall I put it at the end anyway?

libmcCain · 2009-12-31 08:53:06

What do you mean? If you don't use GDM, you don't put it at all!

Anyway, I removed GDM from rc.conf and startx from console. So far so good, no hard freeze in one week.

Edit: Sojek you also have hard system freeze yet you don't use GDM? Does your hard freeze occurs when you hit enter?

Last edited by libmcCain (2009-12-31 08:55:10)

TAsn · 2010-01-01 15:49:55

I moved gdm to start last, and for now, it seems to work.
So this workaround seems to work for me as well. I'll update if I find out otherwise.

vimex · 2010-01-02 22:20:58

libmcCain wrote:

What do you mean? If you don't use GDM, you don't put it at all!
Anyway, I removed GDM from rc.conf and startx from console. So far so good, no hard freeze in one week.

Edit: Sojek you also have hard system freeze yet you don't use GDM? Does your hard freeze occurs when you hit enter?

you can also start gdm from the inittab.

# cat /etc/inittab
#
# /etc/inittab
#

# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot

## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:

rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p

# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux

# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 38400 hvc0 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null

# End of file

made_in_nz · 2010-01-04 13:46:16

I have also had intermitent system freeze requiring a hard reboot. My system details:

[nickh] 51-> uname -a
Linux nickh 2.6.32-ARCH #1 SMP PREEMPT Sat Dec 26 09:02:58 CET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz GenuineIntel GNU/Linux

Like many here gdm was running on tty2. I tried setting gdm as the last daemon in rc.conf, and tried other things like commenting out "c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux" in /etc/inittab.

I suspected xorg-server was the culprit as there have been two upgrades in the past 3 weeks - I can confirm the problem exists using xorg-server-1.7.2-2, xorg-server-1.7.3.901-1, and xorg-server-1.7.3.902-1.

As a temporary workaround I have installed slim as the login manager and the system has not frozen since. X is also now running on tty7.
Would this not suggest the issue is with gdm or the process that has it running on tty2?

thieveshonor · 2010-01-09 17:13:21

I went about a week without using gdm. No lockups. As soon as I put gdm back into rc.conf my system locked up within a hour. So, it seems that disabling gdm is a solution. However, this causes some other minor problems. If I have gdm disabled I can no longer shutdown or reboot my system using System-> Shutdown. The other issue that I have noticed is that I can no longer auto mount items. If I plug a USB drive into my system I get an error message saying unable to mount and not authorized. The same thing happens with CDs or DVDs even though I am in the optical group. I can still mount these items using the command line. Anyone know if there are fixes for this, or is this a sacrifice that I have to make to avoid system lock ups?

zukka · 2010-01-09 17:59:52

@thieveshonor
if you're not using any display manager and you just launch X sessions with startx, you should put ck-launch-session in your .xinitrc
example:

exec ck-launch-session gnome-session
#or wichever de you use

In this way console kit should be initialized and you should be able to do all the stuff you can't do now..

thieveshonor · 2010-01-13 00:03:39

@zukka
I have the same issues when I switch to SLIM. Will adding that clear up those issues also?

Arch Linux

#1 2009-12-11 12:41:16

Strange complete system freeze with no log messages

#2 2009-12-11 16:37:15

Re: Strange complete system freeze with no log messages

#3 2009-12-12 00:08:47

Re: Strange complete system freeze with no log messages

#4 2009-12-12 07:24:12

Re: Strange complete system freeze with no log messages

#5 2009-12-16 08:36:22

Re: Strange complete system freeze with no log messages

#6 2009-12-18 13:42:49

Re: Strange complete system freeze with no log messages

#7 2009-12-20 21:25:42

Re: Strange complete system freeze with no log messages

#8 2009-12-21 09:55:47

Re: Strange complete system freeze with no log messages

#9 2009-12-21 11:04:04

Re: Strange complete system freeze with no log messages

#10 2009-12-21 18:43:41

Re: Strange complete system freeze with no log messages

#11 2009-12-22 09:03:23

Re: Strange complete system freeze with no log messages

#12 2009-12-22 13:54:45

Re: Strange complete system freeze with no log messages

#13 2009-12-23 07:16:46

Re: Strange complete system freeze with no log messages

#14 2009-12-23 10:12:22

Re: Strange complete system freeze with no log messages

#15 2009-12-23 10:23:31

Re: Strange complete system freeze with no log messages

#16 2009-12-23 22:14:38

Re: Strange complete system freeze with no log messages

#17 2009-12-29 08:09:03

Re: Strange complete system freeze with no log messages

#18 2009-12-29 20:10:47

Re: Strange complete system freeze with no log messages

#19 2009-12-31 08:53:06

Re: Strange complete system freeze with no log messages

#20 2010-01-01 15:49:55

Re: Strange complete system freeze with no log messages

#21 2010-01-02 22:20:58

Re: Strange complete system freeze with no log messages

#22 2010-01-04 13:46:16

Re: Strange complete system freeze with no log messages

#23 2010-01-09 17:13:21

Re: Strange complete system freeze with no log messages

#24 2010-01-09 17:59:52

Re: Strange complete system freeze with no log messages

#25 2010-01-13 00:03:39

Re: Strange complete system freeze with no log messages

Board footer