HELP: Konqueror 3.2 hangs SuSE 2.4.21-202-smp4G in 'ps uax'

From: Bob Smith
Date: Sat Apr 17 2004 - 14:49:45 EST

I'm not quite sure where to target this, redirects welcome.

I'm cross-posting because SuSE 2.4.21-202-smp4G is quasi-hanging when accessing process information, particularly noticeable in Konquer sessions. I'm asking now instead of researching further because I'm not sure where to go from here, and because it's happening sooner and sooner after reboot.

The problem initially manifests as a Konqueror freeze. New process creation continues normally (i.e you can start more Konquerors, BASHs, etc. The application does not respond, but KDE can kill the PID after it fails to respond. (I have seen cases where KDE can't influence the program, but when a File | Exit works. This was after a failed KDE 'Logoff' that trashed keyboard functionality(no LED response), but retained mouse input)

ls /proc/[0-9]* does not hang, and does not show dramatic increase of entries, even after creating and killing 20-40 more processes during diagnosis.

ps uax, top and the "KDE System Guard Process Table" all consistently hang. ps consistently shows PIDs into the 2000's, but then hangs. 'for i in /proc/[0-9]* ; do echo $i ; ls $i ; done' hangs on a apparently random process. Further, gdb hangs when you try to 'attach' to the $i-th process in a new bash.

dmesg and /var/log/messages both look innocuous, as does the console. After a failed KDE Logoff and a failed 'telinit 6' from tty4, a Ctrl-Alt-Del on tty1 resulted in:

INIT: Switching to runlevel 6
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
followed by a hang requiring a cold boot.

The system is configured through YaST pointed to:

Is your PC infected? Get a FREE online computer virus scan from McAfee® Security.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at