From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] Revert "drm/i915: disable interrupts earlier in the driver unload code"
Date: Fri, 10 May 2013 09:09:51 -0700 [thread overview]
Message-ID: <20130510090951.28bd616e@jbarnes-desktop> (raw)
In-Reply-To: <20130510072709.GD12292@phenom.ffwll.local>
On Fri, 10 May 2013 09:27:09 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, May 08, 2013 at 10:45:16AM -0700, Jesse Barnes wrote:
> > This reverts commit fd0c06420d39958032655a04cfd194d5a7b38f83.
>
> A bit thin on details about what exactly blows up ... can you please dig a
> bit more?
On unload, we crash trying to queue the VLV work from the
gen6_pm_rps_work function and things fall over pretty hard. At least
that's what the backtrace looked like; it was hard to tell since the
machine was hard hung and I couldn't scroll back.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-05-10 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 17:45 [PATCH 1/4] drm/i915: BIOS and power context stolen mem handling for VLV v7 Jesse Barnes
2013-05-08 17:45 ` [PATCH 2/4] drm/i915: allow stolen, pre-allocated objects to avoid GTT allocation v2 Jesse Barnes
2013-05-09 2:12 ` Ben Widawsky
2013-05-09 19:28 ` Jesse Barnes
2013-05-08 17:45 ` [PATCH 3/4] drm/i915: VLV support is no longer preliminary Jesse Barnes
2013-05-10 7:29 ` Daniel Vetter
2013-05-10 16:10 ` Jesse Barnes
2013-05-10 18:58 ` Daniel Vetter
2013-05-10 19:09 ` Jesse Barnes
2013-05-08 17:45 ` [PATCH 4/4] Revert "drm/i915: disable interrupts earlier in the driver unload code" Jesse Barnes
2013-05-10 7:27 ` Daniel Vetter
2013-05-10 16:09 ` Jesse Barnes [this message]
2013-05-10 16:11 ` Jesse Barnes
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=20130510090951.28bd616e@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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.