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
Subject: Re: [BISECTED] drm: random hang since 620f378 "drm: prune modes when ..."
Date: Wed, 09 Dec 2009 08:13:52 +1000 [thread overview]
Message-ID: <1260310432.12969.0.camel@t60prh> (raw)
In-Reply-To: <200912082259.48715.arnd@arndb.de>
On Tue, 2009-12-08 at 22:59 +0100, Arnd Bergmann wrote:
> On Monday 07 December 2009, Arnd Bergmann wrote:
> > After upgrading one of my machines to 2.6.32, I saw hangs after one to thirty minutes after
> > booting, with random data written to parts of the frame buffer. I've bisected it down
> > to 620f37811d "drm: prune modes when output is disconnected.", which was merged
> > in 2.6.32-rc1. Connecting a serial console does not reveal any output at the time of
> > the crash.
> >
> > The machine uses an Intel G45 chipset with the i915 kernel mode setting enabled.
> >
> > I have no clue what that patch does or why reverting it fixes the problem but 2.6.32
> > with this revert applied has not shown these hangs yet.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Scratch this, the machine crashed again in the same way, but only after
> a some hours of uptime (normally it took a few minutes). It still looks like
> this commit makes the bug much more likely, but it could also be
> attributed to complete coincedence and bad timing. 2.6.31 certainly never
> showed the problem and the bisection clearly pointed in the general direction
> of i915.
>
> I hate debugging sporadic hangs...
>
> 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.
>
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.
Dave.
next prev parent reply other threads:[~2009-12-08 22:15 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 [this message]
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
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=1260310432.12969.0.camel@t60prh \
--to=airlied@redhat.com \
--cc=ajax@redhat.com \
--cc=arnd@arndb.de \
--cc=dri-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.