From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753154Ab2DWAF7 (ORCPT ); Sun, 22 Apr 2012 20:05:59 -0400 Received: from mx.scalarmail.ca ([98.158.95.75]:30013 "EHLO ironport-01.sms.scalar.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752895Ab2DWAF6 (ORCPT ); Sun, 22 Apr 2012 20:05:58 -0400 Date: Sun, 22 Apr 2012 20:05:54 -0400 From: Nick Bowler To: Linus Torvalds Cc: David Airlie , Ben Skeggs , Martin Peres , dri-devel@lists.freedesktop.org, Linux Kernel Mailing List Subject: Re: Linux 3.4-rc4 Message-ID: <20120423000554.GA893@elliptictech.com> References: <20120422040715.GA30689@elliptictech.com> <20120422164023.GA32342@elliptictech.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120422164023.GA32342@elliptictech.com> Organization: Elliptic Technologies Inc. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2012-04-22 12:40 -0400, Nick Bowler wrote: > On 2012-04-21 21:51 -0700, Linus Torvalds wrote: > > Nick, I realize you had trouble with a bisection already, but it might > > really be worth trying again. Do a > > > > git bisect visualize > > > > and try to pick a good commit (avoding the problems you hit) when you > > hit a problem, and then do > > > > git reset --hard > > > > to force bisection to try another place. That way you can sometimes > > avoid the problem spots, and continue the bisection. > > Unfortunately, I think the whole swath of commits bisect wants to test > are broken (as in, they panic before I get to see whether or not the VGA > is working), because the commit from which most of the drm trees were > based appears to be broken. Nevertheless, I've included the new bisect > log (four new commits marked skip as opposed to last time). I've also > included the boot log from a crashing kernel, in case someone recognizes > how I can avoid this during bisection. Note that this crash is *not* a > regression that exists in current mainline -- bisecting this issue was > the first time I had ever seen it. Following up on the above, the commit which introduces the panics during boot is this one: commit 8e7e70522d760c4ccd4cd370ebfa0ba69e006c6e Author: Jerome Glisse Date: Wed Nov 9 17:15:26 2011 -0500 drm/ttm: isolate dma data from ttm_tt V4 Move dma data to a superset ttm_dma_tt structure which herit from ttm_tt. This allow driver that don't use dma functionalities to not have to waste memory for it. V2 Rebase on top of no memory account changes (where/when is my delorean when i need it ?) V3 Make sure page list is initialized empty V4 typo/syntax fixes Signed-off-by: Jerome Glisse Reviewed-by: Thomas Hellstrom and the previous commit (3230cfc34fca: "drm/nouveau: enable the ttm dma pool when swiotlb is active V3") works properly. Sometime this week I suppose I'll try to track down the commit which fixed the crashes... Cheers, -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)