From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 16376] random - possibly Radeon DRM KMS related - freezes
Date: Sun, 5 Sep 2010 07:36:01 GMT
Message-ID: <201009050736.o857a1MW026260@demeter1.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.sourceforge.net
To: dri-devel@lists.sourceforge.net
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=16376
--- Comment #38 from Martin Steigerwald 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
--