From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16376] random - possibly Radeon DRM KMS related - freezes
Date: Sun, 5 Sep 2010 07:36:01 GMT [thread overview]
Message-ID: <201009050736.o857a1MW026260@demeter1.kernel.org> (raw)
In-Reply-To: <bug-16376-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16376
--- Comment #38 from Martin Steigerwald <Martin@Lichtvoll.de> 2010-09-05 07:35:55 ---
Created an attachment (id=29012)
--> (https://bugzilla.kernel.org/attachment.cgi?id=29012)
current state of bisection, please help with selecting next commits to test
If its indeed a Radeon KMS related freeze and upto now everything points at
this, I think it has been introduced in the first quarter of commits that git
bisect visualize shows. I'd like to test just before these KMS/DRM related
commits and just after it to speed up the bisection process, but there are
branches and merges and also there are those unbootable kernels (see previous
commit) not that much before these KMS/DRM related commits, so I am unsure an
which exact commit ids too choose.
Please help me selecting suitable commits - I had more than five unbootable
kernels already and the range of commits to test thus is still above 1800. I
really like to shorten this. In the meanwhile I am just going to compile and
test the next kernel.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
--
next prev parent reply other threads:[~2010-09-05 7:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 9:24 [Bug 16376] New: random - possibly Radeon DRM KMS related - freezes bugzilla-daemon
2010-07-13 10:11 ` [Bug 16376] " bugzilla-daemon
2010-07-13 10:15 ` bugzilla-daemon
2010-07-13 10:24 ` bugzilla-daemon
2010-07-13 12:43 ` bugzilla-daemon
2010-07-13 13:32 ` bugzilla-daemon
2010-07-13 15:12 ` bugzilla-daemon
2010-07-13 15:14 ` bugzilla-daemon
2010-07-15 21:12 ` bugzilla-daemon
2010-07-16 18:15 ` bugzilla-daemon
2010-07-16 19:18 ` bugzilla-daemon
2010-07-16 21:09 ` bugzilla-daemon
2010-07-16 21:15 ` bugzilla-daemon
2010-07-23 14:30 ` bugzilla-daemon
2010-07-23 15:17 ` bugzilla-daemon
2010-07-23 15:19 ` bugzilla-daemon
2010-07-25 18:51 ` bugzilla-daemon
2010-07-26 7:08 ` bugzilla-daemon
2010-07-26 14:59 ` bugzilla-daemon
2010-07-28 12:05 ` bugzilla-daemon
2010-07-28 12:51 ` bugzilla-daemon
2010-07-28 14:32 ` bugzilla-daemon
2010-08-01 14:17 ` bugzilla-daemon
2010-08-14 16:47 ` bugzilla-daemon
2010-08-14 16:54 ` bugzilla-daemon
2010-08-14 17:03 ` bugzilla-daemon
2010-08-23 12:39 ` bugzilla-daemon
2010-08-23 14:20 ` bugzilla-daemon
2010-08-23 14:22 ` bugzilla-daemon
2010-08-23 14:31 ` bugzilla-daemon
2010-08-23 14:37 ` bugzilla-daemon
2010-08-23 14:39 ` bugzilla-daemon
2010-08-23 19:44 ` bugzilla-daemon
2010-08-24 18:30 ` bugzilla-daemon
2010-08-25 10:45 ` bugzilla-daemon
2010-08-26 19:18 ` bugzilla-daemon
2010-08-26 19:28 ` bugzilla-daemon
2010-09-05 7:27 ` bugzilla-daemon
2010-09-05 7:36 ` bugzilla-daemon [this message]
2010-09-05 13:29 ` bugzilla-daemon
2010-09-08 16:36 ` bugzilla-daemon
2010-09-08 16:41 ` bugzilla-daemon
2010-09-08 21:49 ` bugzilla-daemon
2010-09-14 13:30 ` [Bug 16376] random Radeon DRM KMS related freezes bugzilla-daemon
2010-12-07 21:18 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2010-07-23 12:11 2.6.35-rc6: Reported regressions 2.6.33 -> 2.6.34 Rafael J. Wysocki
2010-07-23 12:15 ` [Bug #16376] random - possibly Radeon DRM KMS related - freezes Rafael J. Wysocki
2010-08-01 14:27 2.6.35-rc6-git6: Reported regressions 2.6.33 -> 2.6.34 Rafael J. Wysocki
2010-08-01 14:44 ` [Bug #16376] random - possibly Radeon DRM KMS related - freezes Rafael J. Wysocki
2010-08-01 14:44 ` Rafael J. Wysocki
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=201009050736.o857a1MW026260@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.