linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: Dave Airlie <airlied@linux.ie>,
	Alex Deucher <alexander.deucher@amd.com>,
	Jerome Glisse <jglisse@redhat.com>
Cc: torvalds@linux-foundation.org,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm merge for 3.9-rc1
Date: Wed, 27 Feb 2013 19:01:38 -0500	[thread overview]
Message-ID: <CA+5PVA5za2stXYxQ_Tu3D6Lbif94cqK_5wvPXFhUpvsh_DOXVg@mail.gmail.com> (raw)
In-Reply-To: <CA+5PVA5vvw-JyODTtRwVhQSEiGrt=3wzDoCmeButEMTZxWAhbA@mail.gmail.com>

On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer <jwboyer@gmail.com> wrote:
> On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer <jwboyer@gmail.com> wrote:
>> On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie <airlied@linux.ie> wrote:
>>> Alex Deucher (29):
>>>       drm/radeon: halt engines before disabling MC (6xx/7xx)
>>>       drm/radeon: halt engines before disabling MC (evergreen)
>>>       drm/radeon: halt engines before disabling MC (cayman/TN)
>>>       drm/radeon: halt engines before disabling MC (si)
>>>       drm/radeon: use the reset mask to determine if rings are hung
>>
>> Something in this series of commits is causing the GPU to hang on reboot
>> on my Dell XPS 8300 machine.  That has a:
>>
>> 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee
>> ATI Caicos [Radeon HD 6450]
>>
>> card in it.  After reboots, I get a screen that looks like this:
>>
>> http://t.co/tPnT6xQZUK
>>
>> I can hit it fairly consistently after a few reboots, so I tried doing a
>> git bisect on the radeon driver and it came down to:
>>
>> ca57802e521de54341efc8a56f70571f79ffac72 is the first bad commit
>
> So I don't think that's actually the cause of the problem.  Or at least
> not that alone.  I reverted it on top of Linus' latest tree and I still
> get the lockups.

Actually, git bisect does seem to have gotten it correct.  Once I
actually tested the revert of just that on top of Linus' tree (commit
d895cb1af1), things seem to be working much better.  I've rebooted a
dozen times without a lockup.  The most I've seen it take on a kernel
with that commit included is 3 reboots, so that's definitely at least an
improvement.

Now that I seem to have narrowed down which commit is broken, I'd be
happy to test fixes, etc.  Sorry for the noise from earlier today.


josh

  parent reply	other threads:[~2013-02-28  0:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  0:05 [git pull] drm merge for 3.9-rc1 Dave Airlie
2013-02-26  1:22 ` Linus Torvalds
2013-02-26  1:59   ` Dave Airlie
2013-02-27  1:39 ` Linus Torvalds
2013-02-27  2:25   ` Linus Torvalds
2013-02-27  3:30   ` Dave Airlie
2013-02-27  3:38     ` Linus Torvalds
2013-02-27 10:04   ` Chris Wilson
2013-03-03 15:39   ` Azat Khuzhin
2013-03-05 19:18   ` Daniel Vetter
2013-02-27 16:34 ` Josh Boyer
2013-02-27 20:20   ` Josh Boyer
2013-02-27 20:24     ` Josh Boyer
2013-02-28  0:01     ` Josh Boyer [this message]
2013-02-28  1:14       ` Josh Boyer
2013-02-28 13:38         ` Alex Deucher
2013-02-28 13:44           ` Josh Boyer
2013-02-28 15:09             ` Alex Deucher
2013-02-28 15:15               ` Josh Boyer
2013-02-28 18:59                 ` Josh Boyer
2013-03-05 15:21                   ` Josh Boyer
2013-03-05 15:48                     ` Alex Deucher
2013-02-27 22:36 Sedat Dilek
2013-02-27 23:06 ` Sedat Dilek
2013-02-28 11:18   ` Chris Wilson
2013-02-28 17:07     ` Sedat Dilek

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=CA+5PVA5za2stXYxQ_Tu3D6Lbif94cqK_5wvPXFhUpvsh_DOXVg@mail.gmail.com \
    --to=jwboyer@gmail.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).