From: Tilman Schmidt <tilman@imap.cc>
To: Adrian Bunk <bunk@stusta.de>
Cc: Tilman Schmidt <tilman@imap.cc>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
reiserfs-dev@namesys.com, Oliver Pinter <oliver.pntr@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: 2.6.21-rc5 possible regression: KDE processes die silently
Date: Wed, 04 Apr 2007 22:33:28 +0200 [thread overview]
Message-ID: <46140B98.1080004@imap.cc> (raw)
In-Reply-To: <20070402225006.GI14134@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]
Am 03.04.2007 00:50 schrieb Adrian Bunk:
> On Sun, Apr 01, 2007 at 05:21:06PM +0200, Tilman Schmidt wrote:
>> I'm sorry to say this has now happened with kernel 2.6.21-rc5, too.
>> [...] it's not reproducible and invariably
>> happens when I'm away from the machine.
I have now finally once seen it happen while I was watching, again
on 2.6.21-rc5. The X display was idle and blanked because I hadn't
touched the keyboard and mouse in a while (it seems to happen only
in that state) but I had "top" running in an ssh session from another
machine so I could see what the machine was doing.
Just before the KDE crash, an "online_update" process appeared. The
KDE processes vanished from "top" more or less together with that
process. Before, the system had been idle except for the screensaver.
"online_update" was most probably started by SuSE's "susewatcher"
applet, and according to its log found some new updates, so perhaps
it did try to emit a sound as Rafael suspects. (The machine doesn't
have speakers connected, so I can't tell.)
> We also have another report of crashes under KDE:
>
> Subject : crashes in KDE
> References : http://bugzilla.kernel.org/show_bug.cgi?id=8157
> Submitter : Oliver Pinter <oliver.pntr@gmail.com>
Could be the same. The report is not detailed enough to say.
Oliver provokes his crash with amarok which would fit in with
the sound hypothesis.
> We also have one bug kwin ran into that got fixed after -rc5:
>
> Subject : kwin dies silently
[...]
> Fixed-By : Eric W. Biederman <ebiederm@xmission.com>
> Commit : 14e9d5730adfca26452b3a2838a80af6950556f5
Looks promising. Building -rc5-git12 now. Will test that until
-rc6 arrives.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
In theory, there is no difference between theory and practice.
In practice, there is.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-04-04 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 22:38 2.6.21-rc3-mm2: KDE processes die while system is idle Tilman Schmidt
2007-04-01 15:21 ` 2.6.21-rc5 possible regression: KDE processes die silently (was: 2.6.21-rc3-mm2: KDE processes die while system is idle) Tilman Schmidt
2007-04-01 16:48 ` Rafael J. Wysocki
2007-04-02 23:06 ` Adrian Bunk
2007-04-03 21:09 ` Rafael J. Wysocki
2007-04-06 0:06 ` Rafael J. Wysocki
2007-04-02 22:50 ` Adrian Bunk
2007-04-03 1:25 ` Eric W. Biederman
2007-04-04 20:33 ` Tilman Schmidt [this message]
2007-04-04 22:30 ` 2.6.21-rc5 possible regression: KDE processes die silently Eric W. Biederman
2007-04-09 12:56 ` 2.6.21-rc5 possible regression: KDE processes die silently [fixed] Tilman Schmidt
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=46140B98.1080004@imap.cc \
--to=tilman@imap.cc \
--cc=bunk@stusta.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=reiserfs-dev@namesys.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.