[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091217092523.755ecf29@jbarnes-piketon>
Date: Thu, 17 Dec 2009 09:25:23 -0800
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: keithp@...thp.com, Daniel Vetter <daniel.vetter@...ll.ch>,
linux-kernel@...r.kernel.org, Dave Airlie <airlied@...hat.com>,
dri-devel@...ts.sourceforge.net
Subject: Re: [BISECTED] drm: random hang since 620f378 "drm: prune modes
when ..."
On Wed, 16 Dec 2009 22:41:27 +0000
Arnd Bergmann <arnd@...db.de> wrote:
> On Wednesday 16 December 2009 21:36:36 Arnd Bergmann wrote:
> > On Wednesday 16 December 2009 21:30:05 Jesse Barnes wrote:
> > > But you're sure powersave=0 was solid? Hmm...
> >
> > It's hard to be sure when it sometimes takes a day before a
> > broken version crashes. I can keep running this kernel with and
> > without powersave=0 some more and tell you if it stays reproducible.
>
> Now it has crashed with i915.powersave=0 plus your patch as well
> (latest 2.6.32 git), indicating that there is something else wrong
> with the original 652c393a33 patch.
It does very little else that should affect things. You're sure
reverting the commit makes things ok?
Other potential problems:
- clock gating (the call to intel_init_clock_gating)
- the actual mark_busy stuff itself (calls to intel_mark_busy)
- intel_idle_update (but powersave=0 should prevent that)
If you want to keep testing you could try removing those calls...
--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists