From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 28402] Kernel 2.6.34 freezes randomly
Date: Tue, 31 Aug 2010 13:04:35 -0700 (PDT)
Message-ID: <20100831200435.4E6521300A0@annarchy.freedesktop.org>
References: <bug-28402-502@http.bugs.freedesktop.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
	[131.252.210.176])
	by gabe.freedesktop.org (Postfix) with ESMTP id 5C1E99E82F
	for <dri-devel@lists.freedesktop.org>;
	Tue, 31 Aug 2010 13:04:35 -0700 (PDT)
In-Reply-To: <bug-28402-502@http.bugs.freedesktop.org/>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=28402

--- Comment #28 from Da Fox <da_fox@mad.scientist.com> 2010-08-31 13:04:34 PDT ---
(In reply to comment #27)
> (In reply to comment #26)

> > Could you possibly see if the following three (consecutive) commits are in 
> > your tree too, and test them?
> I'd like, as soon as I find out, how to checkout these specific versions. ;)

Try something like 'git checkout <sha1>' to checkout a specific revision. It
will complain if the commit does not exist or if there is something else which
prevents the checkout (locally modified files for example).
Incase they have a diffent sha1 id in your tree you can try looking for them
using 'gitk' (the git repository browser). Since the kernel is so big you may
want to limit how far back gitk should show history, try gitk
--since=01-01-2010. You can either try to jump directly to the commit by
entering a sha1 id into the 'SHA1 ID' box, or by typing a commit message into
the 'Find' box. Beware that by default the search is case-sensitive.



> What we need is a damn trigger to this bug. Without reproducibility trying to
> catch the right commit is a pure matter of luck and very frustrating.

I feel your pain, I've also mis-identified an 'unstable' commit as 'stable',
which means the whole rest of the bisecting process (which takes a lot of time)
is wasted. What triggers the freeze for me most of the time though is opening
firefox (with a lot of windows and tabs from my previous browsing session). I
do this as soon as I've logged in and my desktop environment has finished
loading. 



On a side note, for those earlier commits (such as
44ca7478d46aaad488d916f7262253e000ee60f9, which I've been testing again during
the day), do you also find that the system becomes very slow? As in there is a
high CPU usage, but not caused by any running program?
I've seen this again today, where top reports all programs using only a small
amount of cpu (a grand total of 8% or so), and yet my CPU usage was almost 50%.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.