All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Gesler <rgesler@pacificnet.net>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Strange shutdown problem with KDE2.2.2.
Date: Mon, 15 Apr 2002 13:42:16 -0700	[thread overview]
Message-ID: <3CBB3B28.74AA68F0@pacificnet.net> (raw)
In-Reply-To: 2.2.32.20020414192256.00ca4358@[192.168.1.23]

Ray Olszewski wrote:
> 
> At 07:13 PM 4/14/02 +0000, Richard Adams wrote:
> >On Sunday 14 April 2002 13:02, Ola Theander wrote:
> >> Dear subscribers.
> >>
> >> I'm running a SuSE 7.3 Professional Linux installation with KDE 2.2.2 on my
> >> Dell Inspiron 8000. Unfortunately I have a problem when I'm shutting down
> >> KDE somtimes the shutdown result in some very strange graphical effect, it
> >> looks pretty much like a sheet of papper burning into ashes. After that the
> >> computer locks and I have to turn of the power. The problem occurs pretty
> >> unprovoked, I could have runned a normal KDE session and when I turn of the
> >> KDE the problem occurs.
> >>
> >> Any help on this matter would be greatly appciciated.
> >
> >You say locks, have you tryed ctrl-alt-backspace to escape from X.??
> >If you have a network, can you ping the (locked)-machine from another host.?
> >And forall what kernel do you have running.??
> 
> The symption as described doesn't suggest anything to me, but, like Richard,
> I wonder how thoroughly "locked" the computer is. Beyond his question:
> 
>         can you CRTL-ALT-F* to a command-line vt (assuming
>                 you have some running)?
> 
>         can you establish a telnet or ssh connection (assuming
>                 you have the relevant servers running)? [This may
>                 be the most important one, since if you can do a
>                 remote connection, you can find out all the usual
>                 things about the state of the host.]
> 
>         can you still connect to any other services you have running
>                 (e.g., SMTP, DNS, HTTP, ident ... I don't really know
>                 what you use the host for so these are wild guesses)?
> 
>         does the host still respond to pings (I guess Richard already
>                 asked this one)?
> 
> After you reboot, do the logs contain any useful information from KDE or
> from X itself?
> 
> How much memory does the system have? (Actual RAM and swap)
> 
I have no answer to this problem (it has happened to me several time),
but I can provide some additional information. Hopefully someone will be
able to suggest where to look the next time this occurs.  I am running
SuSE 7.2 with a 2.4.4 kernel and KDE 2.2.1.  Note that as I rember I
also saw this happen a couple of times with a 2.2.x kernel and an
earlier version of KDE. 

* When this event occurs the local keyboard and mouse is locked.
Therefore       X can not be terminated by cont+alt+backspace nor can a
switch to              another terminal.

* I can login via ssh from another syster and execute commands.
Before           anyone asks, I have killed all processes, I think,
associated with KDE         and X. However, the keyboard, mouse and
screen on the effected system          remain locked.  After su to root
I have tried halting the system, but          only a partial halt is
made.  By this I mean a system going down               message is
received at the log in terminal and network connection is           lost
and the locked system never reaches run level 0.  After a          
manual reset of the system fschk is run on all partitions during
reboot        so that it appears the shutdown process occurs prion to
unmounting.

I have not been able to find anything in the logs indicating any problem
detected by KDE, X or the kernel. My guess at this time is some locking
process has occured, but I have no idea where to start looking..Therfore
it is not clear where this problem lies .ie kernel, X or KDE.

Hopefully someone will have some suggestions of where to look, what
debug funtions to use, or ? that I can do the next time this occurs so
that a meaningful bug report can be made to the developers.  Since this
happens  rarely, it may be awhile before I can provide any further
information other than what I have forgotten to mention.

Ralph Gesler
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-04-15 20:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14 19:22 Strange shutdown problem with KDE2.2.2 Ray Olszewski
2002-04-15 20:42 ` Ralph Gesler [this message]
2002-04-15 21:56   ` JD
2002-04-16 15:26     ` Ralph Gesler
2002-04-16 15:30       ` Strange shutdown problem JD
2002-04-16 15:47       ` Strange shutdown problem with KDE2.2.2 Richard Adams
2002-04-16 17:44         ` Ralph Gesler
2002-04-16 19:41           ` Richard Adams
2002-04-16 22:58             ` Ralph Gesler
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 19:43 Ola Theander
2002-04-16 20:10 ` JD
2002-04-16 16:34 Ola Theander
2002-04-16 16:48 ` JD
2002-04-15 14:13 Ola Theander
2002-04-14 13:02 Ola Theander
2002-04-14 19:13 ` Richard Adams

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=3CBB3B28.74AA68F0@pacificnet.net \
    --to=rgesler@pacificnet.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.