From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-kernel@vger.kernel.org
Subject: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
Date: Tue, 31 Aug 2010 21:53:43 +0200 [thread overview]
Message-ID: <201008312153.45792.Martin@lichtvoll.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Hi!
I am seeking help with encircling the cause of:
[Bug 16376] random - possibly Radeon DRM KMS related - freezes
https://bugzilla.kernel.org/show_bug.cgi?id=16376
I started a bisection as described in which has been painful for me - at
least for a first time bisection -, but after the second skip of a non-
booting kernel git points me to a kernel that is outside of the initial
range between good and back.
good is: [60b341b778cc2929df16c0a504c91621b3c6a4ad] Linux 2.6.33
bad is: bad: [64ba9926759792cf7b95f823402e2781edd1b5d4] Merge branch 'for-
linus' of git://git.open-osd.org/linux-open-osd
After skipping the last non booting kernel, git bisect put me to
5be796f0b842c5852d7397a82f8ebd6be8451872 which is just 300 lines after
2.6.33-rc2.
Obviously I am not interested in kernels prior 2.6.33. Should I just do a
"git bisect good" without trying the kernel or is there some other remedy?
its 11 cycles already without testing anything outside the initial
good/bad range and it takes about half a day to be somewhat sure that a
kernel is good, so I'd like to avoid testing versions outside this range.
My bug comment #35 contains a log of the bisection[1].
[1] https://bugzilla.kernel.org/show_bug.cgi?id=16376#c35
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-08-31 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:53 Martin Steigerwald [this message]
2010-08-31 22:39 ` help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes Ken Moffat
2010-09-01 16:10 ` Martin Steigerwald
2010-09-01 18:13 ` Ken Moffat
2010-09-01 18:47 ` Paolo Ornati
2010-09-01 19:26 ` Martin Steigerwald
2010-09-05 7:53 ` Martin Steigerwald
2010-09-05 12:20 ` Paolo Ornati
2010-09-05 13:25 ` Martin Steigerwald
2010-09-07 2:51 ` Ted Ts'o
2010-09-09 14:18 ` Martin Steigerwald
2010-09-10 11:55 ` Florian Mickler
2010-09-10 13:49 ` Martin Steigerwald
2010-09-10 15:53 ` Theodore Tso
2010-09-10 16:18 ` Martin Steigerwald
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=201008312153.45792.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--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