From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>,
akpm@osdl.org
Subject: Re: rc6 keeps hanging and blanking displays where rc4-mm1 works fine.
Date: Mon, 15 Aug 2005 14:37:48 +0200 [thread overview]
Message-ID: <43008C9C.60806@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.58.0508120937140.3295@g5.osdl.org>
Linus Torvalds wrote:
>On Fri, 12 Aug 2005, Helge Hafting wrote:
>
>
>>>at the moment. The setup is fine with 2.6.13-rc4-mm1 x86-64, no
>>>problems there.
>>>
>>>
>>The problem still exists in 2.6.13-rc6. Usually, all I get is a
>>suddenly black display, solveable by resizing.
>>
>>
>
>Is there any chance you could try bisecting the problem? Either just
>binary-searching the patches or by using the git bisect helper scripts?
>
>Obviously the git approach needs a "good" kernel in git, but if
>2.6.13-rc4-mm1 is ok, then I assume that 2.6.13-rc4 is ok too? That's a
>fair number of changes:
>
> git-rev-list v2.6.13-rc4..v2.6.13-rc6 | wc
> 340 340 13940
>
>but if you can tighten it up a bit (you already had trouble at rc5, I
>think), it shouldn't require testing more than a few kernels.
>
>Git has had bisection support for a while, but the helper scripts to use
>it sanely are fairly new, so I think you'd need the git-0.99.4 release for
>those. But then you'd just do
>
> git bisect start
> git bisect bad v2.6.13-rc5
> git bisect good v2.6.13-rc4
>
>and start bisecting (that will check out a mid-way point automatically,
>you build it, and then do "git bisect bad" or "git bisect good" depending
>on whether the result is bad or good - it will continue to try to find
>half-way points until it has found the point that turns from good to
>bad..)
>
> Linus
>
>
Ok, I have downlaoded git and started the first compile.
Git will tell when the correct point is found (assuming I
do the "git bisect bad/good" right), by itself?
Is there any way to make git tell exactly where between rc4 and rc5
each kernel is, so I can name the bzimages accordingly?
It takes some time to trigger the bug, so I could possibly end up with
a falsely ok kernel. Is there a simple way to restart the search from
that point,
or will I have to start over with rc4 and rc5 and say
git bisect good/bad until I reach the point of mistake?
Helge Hafting
next prev parent reply other threads:[~2005-08-15 12:30 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 5:07 Linux 2.6.13-rc5 Linus Torvalds
2005-08-02 6:17 ` Jan De Luyck
2005-08-02 6:43 ` Linux 2.6.13-rc5 - possible acpi regression? Jan De Luyck
2005-08-02 10:50 ` Rafael J. Wysocki
2005-08-03 10:59 ` Jan De Luyck
2005-08-02 7:56 ` Linux 2.6.13-rc5 Olaf Hering
2005-08-05 10:40 ` rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble Helge Hafting
2005-08-05 22:05 ` Andrew Morton
2005-08-07 9:41 ` Helge Hafting
2005-08-07 17:06 ` Danny ter Haar
2005-08-08 11:27 ` Helge Hafting
2005-08-08 12:14 ` Danny ter Haar
2005-08-08 14:59 ` Danny ter Haar
[not found] ` <21d7e99705080503515e3045d5@mail.gmail.com>
2005-08-09 12:20 ` Helge Hafting
2005-08-12 10:01 ` rc6 keeps hanging and blanking displays where rc4-mm1 works fine Helge Hafting
2005-08-12 10:32 ` Alan Cox
2005-08-15 12:53 ` Bartlomiej Zolnierkiewicz
2005-08-15 13:00 ` Bartlomiej Zolnierkiewicz
2005-08-12 16:51 ` Linus Torvalds
2005-08-15 12:37 ` Helge Hafting [this message]
2005-08-15 15:50 ` Linus Torvalds
2005-08-15 17:00 ` Ryan Anderson
2005-08-15 17:45 ` Helge Hafting
2005-08-15 21:48 ` Sanjoy Mahajan
2005-08-15 22:11 ` rc6 keeps hanging and blanking displays - bisection complete Helge Hafting
2005-08-15 22:59 ` Linus Torvalds
2005-08-16 8:46 ` Helge Hafting
2005-08-16 19:29 ` Helge Hafting
2005-08-15 23:18 ` Dave Airlie
2005-08-15 23:24 ` Dave Airlie
2005-08-16 7:34 ` Helge Hafting
2005-08-16 16:52 ` rc6 keeps hanging and blanking displays Helge Hafting
2005-08-16 17:00 ` Linus Torvalds
2005-08-16 21:14 ` Helge Hafting
2005-08-16 23:50 ` Dave Airlie
2005-08-17 11:05 ` Helge Hafting
2005-08-17 11:05 ` Dave Airlie
2005-08-17 15:19 ` Linus Torvalds
2005-08-22 21:44 ` Helge Hafting
2005-08-22 23:07 ` Dave Airlie
2005-08-22 23:40 ` Linus Torvalds
2005-08-23 15:33 ` Alan Cox
2005-08-24 6:04 ` Linus Torvalds
2005-08-24 8:37 ` Helge Hafting
2005-09-08 23:47 ` rc6 keeps hanging and blanking displays where rc4-mm1 works fine Andrew Morton
2005-09-09 0:16 ` Linus Torvalds
2005-08-17 11:26 ` rc5 seemed to kill a disk that rc4-mm1 likes. Also some X trouble Rolf Eike Beer
2005-08-22 8:01 ` Rolf Eike Beer
2005-08-22 17:44 ` Linus Torvalds
2005-08-22 17:45 ` Linus Torvalds
2005-08-22 21:01 ` Benjamin Herrenschmidt
2005-08-23 6:48 ` Rolf Eike Beer
2005-08-30 8:07 ` Rolf Eike Beer
2005-09-05 7:49 ` Rolf Eike Beer
2005-09-05 8:45 ` Linus Torvalds
2005-09-05 19:58 ` Sonny Rao
2005-09-06 7:44 ` Linus Torvalds
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=43008C9C.60806@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.