From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Zhenyu Wang <zhenyuw@linux.intel.com>,
Nanhai Zou <nanhai.zou@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: 2.6.32.1 i915 KMS rmmod failure
Date: Wed, 16 Dec 2009 11:51:03 -0800 [thread overview]
Message-ID: <20091216115103.042aacdf@jbarnes-piketon> (raw)
In-Reply-To: <m3d42e20v3.fsf@intrepid.localdomain>
On Wed, 16 Dec 2009 20:08:16 +0100
Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Hi,
>
> The following sequence causes the machine to hang hard:
> modprobe drm debug=65535
> modprobe i915 modeset=1
> rmmod i915
>
> Linux 2.6.32.1 x86-64, i915 (the machine is a slimline MSI Hetis 915
> barebone), 2 GB RAM etc. Kernel messages captured with a serial
> console. Only analog VGA output connected (no EDID, using a "pro" 5 *
> BNC cable to connect to an old analog monitor). There is
> (unconnected) digital DVI and a TV encoder. Other details available
> on request.
>
> The IRQ happens in intel_pipe_set_base()
>
> DRM_DEBUG("Writing base %08lX %08lX %d %d\n", Start, Offset,
> x, y); I915_WRITE(dspstride, crtc->fb->pitch);
> if (IS_I965G(dev)) {
> ...
> } else {
> I915_WRITE(dspbase, Start + Offset);
> I915_READ(dspbase);
> >>>>>>> IRQ seems to be triggered at this point <<<<<<<
> }
>
> Any ideas?
Seems like we should be disabling everything at unload time rather than
trying to set a new mode... If the dspbase we program isn't mapped
anymore we'd definitely get into trouble.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-12-16 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 19:08 Krzysztof Halasa
2009-12-16 19:51 ` Jesse Barnes [this message]
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=20091216115103.042aacdf@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=zhenyuw@linux.intel.com \
/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
all inboxes | Powered by JetHome®