public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bob Smith" <bobsmith401@hotmail.com>
To: linux-kernel@vger.kernel.org, suse-linux-e@suse.com,
	kde-linux@mail.kde.org
Subject: HELP: Konqueror 3.2 hangs SuSE 2.4.21-202-smp4G in 'ps uax'
Date: Sat, 17 Apr 2004 15:48:41 -0400	[thread overview]
Message-ID: <BAY16-F57FTS0aWrz4e0001940c@hotmail.com> (raw)

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:

tricia.cc.gatech.edu/pub/suse/suse/i386/current
and
ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee® 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963


                 reply	other threads:[~2004-04-17 19:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY16-F57FTS0aWrz4e0001940c@hotmail.com \
    --to=bobsmith401@hotmail.com \
    --cc=kde-linux@mail.kde.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suse-linux-e@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox