From: Dave Airlie <airlied@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Adam Jackson <ajax@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net,
keithp@keithp.com, eric@anholt.net, jbarnes@virtuousgeek.org
Subject: Re: [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..."
Date: Wed, 09 Dec 2009 15:38:07 +1000 [thread overview]
Message-ID: <1260337087.3658.1.camel@t60prh> (raw)
In-Reply-To: <200912090007.45545.arnd@arndb.de>
On Wed, 2009-12-09 at 00:07 +0100, Arnd Bergmann wrote:
> On Tuesday 08 December 2009, Dave Airlie wrote:
> > >
> > > Sorry for blaming the wrong patch, especially if it already caused a lot
> > > of work. I'll try blaming ec2a4c3fdc8 "drm/i915: get the bridge device
> > > once" now, that is the next-best candidate that my bisection pointed to,
> > > but I'll do more rigorous testing.
>
> It just crashed again with both 620f378 and ec2a4c3fdc8 reverted as well,
> after about an hour of uptime.
>
> > Btw is this just a laptop with no monitor plugged in?
> >
> > just want to rule out the patch you mentioned for any sort of memory
> > corruption.
>
> It's a desktop machine with three outputs, Asus P5Q-EM mainboard.
> VGA is not connected at all, DVI has an open-ended cable on it, i.e. no
> screen on it. HDMI is connected through a cheap passive HDMI multiswitch
> to the DVI-D input of a Lenovo screen.
CC'ed the Intel ppl,
regression since 2.6.31 by the looks of it, bisection has found two
false positives so far.
Dave.
next prev parent reply other threads:[~2009-12-09 5:40 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 [this message]
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
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=1260337087.3658.1.camel@t60prh \
--to=airlied@redhat.com \
--cc=ajax@redhat.com \
--cc=arnd@arndb.de \
--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