Mailinglist Archive: opensuse (2271 mails)

< Previous Next >
Re: [SLE] HELP: Konqueror 3.2 hangs SuSE 2.4.21-202-smp4G in 'ps uax'
  • From: "Neil Schneider" <pacneil@xxxxxxxxxxxxx>
  • Date: Sat, 17 Apr 2004 20:55:35 -0700 (PDT)
  • Message-id: <39165.>
First thing I would check is memory. Run memtest86 for several hours if
any errors appear remove or replace the offending memory. Then look for
other problems. Every time I've had this kind of unreproduceable random
error it's been a bad memory module.


Bob Smith said:
> 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:
> and
> _________________________________________________________________
> Is your PC infected? Get a FREE online computer virus scan from McAfee®
> Security.
> --
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Neil Schneider pacneil_at_linuxgeek_dot_net
Key fingerprint = 67F0 E493 FCC0 0A8C 769B 8209 32D7 1DB1 8460 C47D

Fires can't be made with dead embers, nor can enthusiasm be stirred by
spiritless men. Enthusiasm in our daily work lightens effort and turns
even labor into pleasant tasks. --James Baldwin

< Previous Next >