From: Arnd Bergmann <arnd@arndb.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Dave Airlie <airlied@redhat.com>, Adam Jackson <ajax@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net,
keithp@keithp.com, eric@anholt.net, jbarnes@virtuousgeek.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..."
Date: Sun, 13 Dec 2009 21:31:07 +0000 [thread overview]
Message-ID: <200912132131.07100.arnd@arndb.de> (raw)
In-Reply-To: <20091213200017.GA3522@viiv.ffwll.ch>
On Sunday 13 December 2009 20:00:18 Daniel Vetter wrote:
> On Sun, Dec 13, 2009 at 12:30:25PM +0000, Arnd Bergmann wrote:
> > And now it's obvious that my computer hates me. 12 hours of uptime, one reboot
> > to check the old other version is broken, it crashes. I reboot into the
> > good version, send out the above email and the next minute it crashes again.
> > c05422d52ee6b is not the culprit. Sorry Daniel for blaming your patch.
>
> No problem. Looks like your hunting a pretty ugly Heisenbug. There's quite
> a interesting blog post by Paul McKenney, esp. the solution to "Quick Quiz 1"
> might be usefull in your case:
>
> http://paulmck.livejournal.com/14639.html
Thanks! In fact I've actually read that post on the kernel planet and decided
to do basically a linear search through the i915 patches merged into 2.6.32.
The current result is 67cf781bea5 "drm/i915: Make the downclocking debug code
be under DRM_DEBUG not DRM_ERROR." is known bad, while 043029655 "drm/i915:
Support IGD EOS" is probably good, pointing to Jesses 652c393a33 "drm/i915:
add dynamic clock frequency control" as the next best guess. Unfortunately,
that is a rather large change that is not easy to revert on current kernels.
I'll keep running my machine on the 043029655 level and tell you if it keeps
working a few more days.
Arnd
next prev parent reply other threads:[~2009-12-13 21:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:30 [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..." Arnd Bergmann
2009-12-08 21:59 ` Arnd Bergmann
2009-12-08 22:13 ` Dave Airlie
2009-12-08 23:07 ` Arnd Bergmann
2009-12-09 5:38 ` Dave Airlie
2009-12-13 12:18 ` Arnd Bergmann
2009-12-13 12:30 ` Arnd Bergmann
2009-12-13 20:00 ` Daniel Vetter
2009-12-13 21:31 ` Arnd Bergmann [this message]
2009-12-13 21:54 ` Dave Airlie
2009-12-14 18:20 ` Jesse Barnes
2009-12-14 20:38 ` Arnd Bergmann
2009-12-14 20:50 ` Jesse Barnes
2009-12-15 9:51 ` Arnd Bergmann
2009-12-16 13:53 ` Arnd Bergmann
2009-12-16 20:18 ` Jesse Barnes
2009-12-16 21:20 ` Arnd Bergmann
2009-12-16 21:30 ` Jesse Barnes
2009-12-16 21:36 ` Arnd Bergmann
2009-12-16 22:41 ` Arnd Bergmann
2009-12-17 17:25 ` Jesse Barnes
2009-12-17 17:52 ` Arnd Bergmann
2009-12-17 19:13 ` Jesse Barnes
2009-12-19 13:16 ` Arnd Bergmann
2009-12-21 16:06 ` Arnd Bergmann
2009-12-21 17:57 ` Arnd Bergmann
2009-12-28 18:47 ` Jesse Barnes
2009-12-30 22:00 ` Arnd Bergmann
2009-12-16 12:19 ` Mathieu Taillefumier
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=200912132131.07100.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=airlied@redhat.com \
--cc=ajax@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox