LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sid Boyce <g3vbv@blueyonder.co.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, auxsvr@gmail.com
Subject: Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently
Date: Wed, 21 Mar 2007 20:34:20 +0100 [thread overview]
Message-ID: <20070321193420.GP752@stusta.de> (raw)
In-Reply-To: <46016EAF.6010801@blueyonder.co.uk>
On Wed, Mar 21, 2007 at 05:43:11PM +0000, Sid Boyce wrote:
> Sid Boyce wrote:
> >Andrew Morton wrote:
> >>(cc restored. Please always do reply-to-all)
> >>
> >>
> >>>On Wed, 28 Feb 2007 18:05:13 +0200 auxsvr@gmail.com wrote:
> >>>On Wednesday 28 February 2007 17:19, Sid Boyce wrote:
> >>>
> >>>>openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to
> >>>>require a password to unlock, but it asks for password. When the screen
> >>>>unlocks, kwin is gone with no errors logged in /var/log/kdm or
> >>>>/var/log/messages. No problems with 2.6.20.
> >>>>
> >>>>Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 and 2.6.21-rc2.
> >>>>Regards
> >>>>Sid.
> >>>>
> >>>This is the linux kernel mailing list. Perhaps you should post your
> >>>problem to the opensuse mailing list.
> >>>
> >>
> >>2.6.20 worked.
> >>
> >>2.6.20-rc2 did not.
> >>
> >>Working theory: the kernel broke.
> >>
> >>Sid, the chances that anyone can work out what caused this are pretty
> >>low. It would be great if you could perform a git bisection search
> >>sometime in
> >>the next few weeks, work out which commit caused this.
> >>
> >>Thanks.
> >>
> >>
> >>
> >>
> >I shall go back to 2.6.20-git3 and work forward. Up to 2.6.20-git2 was OK.
> >Regards
> >Sid.
> >
>
> I tracked the problem down to 2.6.20-git11. Up to 2.6.20-git10 is OK,
> but from 2.6.20-git11 up to current 2.6.21-rc4-git2 all exhibit the problem.
Thanks for this search.
Looking at the changes between 2.6.20-git10 and 2.6.20-git11, the only
suspicious changes are the 60 sysctl patches by Eric.
Eric, can you look at this issue?
> Regards
> Sid.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-03-21 19:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 15:19 Sid Boyce
2007-02-28 16:05 ` auxsvr
2007-03-08 5:47 ` Andrew Morton
2007-03-08 7:34 ` Sid Boyce
2007-03-21 17:43 ` Sid Boyce
2007-03-21 19:34 ` Adrian Bunk [this message]
2007-03-21 20:17 ` Eric W. Biederman
2007-03-22 1:32 ` Sid Boyce
2007-03-22 1:42 ` Randy Dunlap
2007-03-22 10:59 ` Adrian Bunk
2007-03-22 19:49 ` Sid Boyce
2007-03-26 12:02 ` boris
2007-03-27 3:38 ` Sid Boyce
2007-03-27 13:48 ` Eric W. Biederman
2007-03-28 3:26 ` Sid Boyce
2007-03-28 4:14 ` Adrian Bunk
2007-03-28 13:17 ` Eric W. Biederman
2007-03-29 11:35 ` Sid Boyce
2007-03-30 18:00 ` Adrian Bunk
2007-03-29 4:04 ` Eric W. Biederman
2007-03-29 11:37 ` Sid Boyce
2007-03-29 16:16 ` Sid Boyce
2007-02-28 16:24 Sid Boyce
[not found] <45E5DE32.2070902@argo.co.il>
2007-03-01 13:52 ` Sid Boyce
2007-03-01 15:11 ` Avi Kivity
2007-03-02 4:22 ` Sid Boyce
[not found] <45E939E1.8050501@argo.co.il>
2007-03-03 20:30 ` Sid Boyce
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=20070321193420.GP752@stusta.de \
--to=bunk@stusta.de \
--cc=auxsvr@gmail.com \
--cc=ebiederm@xmission.com \
--cc=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: 2.6.21-rc1 and 2.6.21-rc2 kwin dies silently' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).