From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc5 possible regression: KDE processes die silently [fixed]
Date: Sun, 15 Apr 2007 03:57:10 +0100 [thread overview]
Message-ID: <46219486.3030102@blueyonder.co.uk> (raw)
Am 03.04.2007 00:50 schrieb Adrian Bunk:
>>/ We also have one bug kwin ran into that got fixed after -rc5:/
>>/ /
>>/ Subject : kwin dies silently/
>>/ References : http://lkml.org/lkml/2007/2/28/112/
>>/ Submitter : Sid Boyce <g3vbv@xxxxxxxxxxxxxxxx>/
>>/ Boris Mogwitz <boris@xxxxxxxxxxxxxxxx>/
>>/ Michael Wu <aluminum.tape@xxxxxxxxx>/
>>/ Caused-By : Eric W. Biederman <ebiederm@xxxxxxxxxxxx>/
>>/ commit 0475ac0845f9295bc5f69af45f58dff2c104c8d1/
>>/ Fixed-By : Eric W. Biederman <ebiederm@xxxxxxxxxxxx>/
>>/ Commit : 14e9d5730adfca26452b3a2838a80af6950556f5/
>>/ Status : fixed in -rc6/
>>
> The machine has been running -rc5-git12, then -rc6 for a total
> of four days now, and the problem hasn't reoccurred. Looks like
> it was indeed the same bug.
>
> Thanks,
> Tilman
No further problems since the patch was applied. Currently running
2.6.21-rc6-git7.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next reply other threads:[~2007-04-15 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 2:57 Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
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-02 22:50 ` Adrian Bunk
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=46219486.3030102@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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