On Thu, Mar 29, 2007 at 12:35:42PM +0100, Sid Boyce wrote:
>...
> 1) Ran the commands as above,cg-clone; git start; git bisect bad
> ;git bisect good I presume.
> 2) 2.6.20-git10 is the last good kernel.
> 3) 2.6.20-git11 and later are all bad.
> 4) I do cg-clone which gives a kernel whose
On Thu, Mar 29, 2007 at 12:35:42PM +0100, Sid Boyce wrote:
...
1) Ran the commands as above,cg-clone; git start; git bisect bad
checksum;git bisect good checksum of 2.6.20-git10 I presume.
2) 2.6.20-git10 is the last good kernel.
3) 2.6.20-git11 and later are all bad.
4) I do cg-clone which
Sid Boyce wrote:
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following
patch. I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following patch.
I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@
Adrian Bunk wrote:
On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote:
Eric W. Biederman wrote:
Sid Boyce <[EMAIL PROTECTED]> writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything
Adrian Bunk wrote:
On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote:
Eric W. Biederman wrote:
Sid Boyce [EMAIL PROTECTED] writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following patch.
I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@
Sid Boyce wrote:
Eric W. Biederman wrote:
Sid I think I have found the problem. Could you try the following
patch. I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@
Sid I think I have found the problem. Could you try the following patch.
I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@ static void exit_notify(struct
Adrian Bunk <[EMAIL PROTECTED]> writes:
> I think I got your problem:
>
> After rebooting, you do "git bisect [bad|good]" *once*.
>
> Then recompile the kernel from the current tree, reboot, and again
> *once* "git bisect [bad|good]".
>
> etc.
Sounds right.
Someone else doing the bisect
Adrian Bunk [EMAIL PROTECTED] writes:
I think I got your problem:
After rebooting, you do git bisect [bad|good] *once*.
Then recompile the kernel from the current tree, reboot, and again
*once* git bisect [bad|good].
etc.
Sounds right.
Someone else doing the bisect suggested that
Sid I think I have found the problem. Could you try the following patch.
I believe I accidentally switched the sense of a test
diff --git a/kernel/exit.c b/kernel/exit.c
index f132349..b55ed4c 100644
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -790,7 +790,7 @@ static void exit_notify(struct
On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote:
> Eric W. Biederman wrote:
> >Sid Boyce <[EMAIL PROTECTED]> writes:
> >
> >
> >>This is what I've got so far on the first boot, I shall have to check the
> >>manpage for git-bisect again to see if there is anything else to be added,
>
Eric W. Biederman wrote:
Sid Boyce <[EMAIL PROTECTED]> writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else to be added,
nothing enlightening seen so far - further reboots to be done.
I'm a
Sid Boyce <[EMAIL PROTECTED]> writes:
> This is what I've got so far on the first boot, I shall have to check the
> manpage for git-bisect again to see if there is anything else to be added,
> nothing enlightening seen so far - further reboots to be done.
I'm a little confused at what I am
Sid Boyce [EMAIL PROTECTED] writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else to be added,
nothing enlightening seen so far - further reboots to be done.
I'm a little confused at what I am seeing
Eric W. Biederman wrote:
Sid Boyce [EMAIL PROTECTED] writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else to be added,
nothing enlightening seen so far - further reboots to be done.
I'm a
On Wed, Mar 28, 2007 at 04:26:05AM +0100, Sid Boyce wrote:
Eric W. Biederman wrote:
Sid Boyce [EMAIL PROTECTED] writes:
This is what I've got so far on the first boot, I shall have to check the
manpage for git-bisect again to see if there is anything else to be added,
nothing
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
On Thu, Mar 22, 2007 at 07:49:16PM +, Sid Boyce wrote:
> Kernel built and installed, so I shall have something to report in the
> next couple of days.
I see this kwin bug too
on a Thinkpad (x86_64) as well as on a Pmac (powerpc64).
It is only triggerd when the screen is locked AND! set
to
On Thu, Mar 22, 2007 at 07:49:16PM +, Sid Boyce wrote:
Kernel built and installed, so I shall have something to report in the
next couple of days.
I see this kwin bug too
on a Thinkpad (x86_64) as well as on a Pmac (powerpc64).
It is only triggerd when the screen is locked AND! set
to
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
> On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
>
> >...
> There's not a lot of docs out there.
>
> The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
>
> Linus's email doc:
>
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
Adrian Bunk wrote:
On Wed, Mar 21, 2007 at 06:42:58PM -0700, Randy Dunlap wrote:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
...
There's not a lot of docs out there.
The man-page: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Linus's email doc:
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
> Eric W. Biederman wrote:
> > Adrian Bunk <[EMAIL PROTECTED]> writes:
> >
> >
> >> On Wed, Mar 21, 2007 at 05:43:11PM +, Sid Boyce wrote:
> >>
> >>> Sid Boyce wrote:
> >>>
> Andrew Morton wrote:
>
> >
Eric W. Biederman wrote:
Adrian Bunk <[EMAIL PROTECTED]> writes:
On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL
Adrian Bunk <[EMAIL PROTECTED]> writes:
> On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL PROTECTED] wrote:
>> >>>On Wednesday 28
On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL PROTECTED] wrote:
> >>>On Wednesday 28 February 2007 17:19, 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 [EMAIL PROTECTED] 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
Sid Boyce wrote:
Andrew Morton wrote:
(cc restored. Please always do reply-to-all)
On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] 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
On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL PROTECTED] wrote:
On Wednesday 28 February 2007 17:19, Sid Boyce wrote:
openSUSE 10.3 Alpha and
Adrian Bunk [EMAIL PROTECTED] writes:
On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL PROTECTED] wrote:
On Wednesday 28 February 2007 17:19, Sid
Eric W. Biederman wrote:
Adrian Bunk [EMAIL PROTECTED] writes:
On Wed, Mar 21, 2007 at 05:43:11PM +, 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 [EMAIL
On Thu, 22 Mar 2007 01:32:36 + Sid Boyce wrote:
Eric W. Biederman wrote:
Adrian Bunk [EMAIL PROTECTED] writes:
On Wed, Mar 21, 2007 at 05:43:11PM +, Sid Boyce wrote:
Sid Boyce wrote:
Andrew Morton wrote:
(cc restored. Please always do
Andrew Morton wrote:
(cc restored. Please always do reply-to-all)
On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] 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
(cc restored. Please always do reply-to-all)
> On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] 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.
(cc restored. Please always do reply-to-all)
On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] 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
Andrew Morton wrote:
(cc restored. Please always do reply-to-all)
On Wed, 28 Feb 2007 18:05:13 +0200 [EMAIL PROTECTED] 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
Avi Kivity wrote:
Sid Boyce wrote:
> Avi Kivity wrote:
>> Sid Boyce wrote:
> That's very much appreciated. The point is that all vanilla
kernels up
> to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
> 2.6.20-rc2 and like other problems reported, sic
Avi Kivity wrote:
Sid Boyce wrote:
Avi Kivity wrote:
Sid Boyce wrote:
That's very much appreciated. The point is that all vanilla
kernels up
to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
2.6.20-rc2 and like other problems reported, sic framebuffer,
etc.,
there is
Avi Kivity wrote:
Sid Boyce wrote:
> That's very much appreciated. The point is that all vanilla
kernels up
> to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
> 2.6.20-rc2 and like other problems reported, sic framebuffer, etc.,
> there is a distinct likelihood that it's related
Sid Boyce wrote:
> That's very much appreciated. The point is that all vanilla kernels up
> to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
> 2.6.20-rc2 and like other problems reported, sic framebuffer, etc.,
> there is a distinct likelihood that it's related to those kernels
Avi Kivity wrote:
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
Avi Kivity wrote:
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
Sid Boyce wrote:
That's very much appreciated. The point is that all vanilla kernels up
to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
2.6.20-rc2 and like other problems reported, sic framebuffer, etc.,
there is a distinct likelihood that it's related to those kernels and
Avi Kivity wrote:
Sid Boyce wrote:
That's very much appreciated. The point is that all vanilla
kernels up
to 2.6.20+ have not had the problems now seen on 2.6.20-rc1 and
2.6.20-rc2 and like other problems reported, sic framebuffer, etc.,
there is a distinct likelihood that it's related to
>>/ 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
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
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
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
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
/ 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
54 matches
Mail list logo
