From: Keith Packard <keith.packard@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Keith Packard <keith.packard@intel.com>,
Jiri Slaby <jirislaby@gmail.com>, Eric Anholt <eric@anholt.net>,
Sitsofe Wheeler <sitsofe@yahoo.com>,
airlied@linux.ie, dri-devel@lists.sourceforge.net,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: i915 X lockup
Date: Sat, 28 Feb 2009 09:11:58 -0800 [thread overview]
Message-ID: <1235841119.4162.5.camel@aiko.keithp.com> (raw)
In-Reply-To: <20090228004751.96d1ea8d.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
> The kernel deadlocked on struct_mutex, did it not? That's a kernel bug
> regardless of what userspace you're running.
No, it didn't deadlock on struct_mutex, it deadlocked because the
hardware got wedged, and we still don't know how to unwedge the hardware
and get it working again other than turning it off and back on again.
> Do we know why this happened?
Yes, the hardware will happily lock up when user space maps the PCI BAR
covering the device registers and the application pokes various internal
device registers directly.
That's the fundamental contract KMS requires -- if the kernel is going
to manage the device, then user space isn't supposed to manipulate it
directly anymore.
I suspect most any other device in the machine could be made to do 'bad
things' if userspace went and poked it directly.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2009-02-28 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 9:28 i915 X lockup Jiri Slaby
2009-02-27 10:01 ` Peter Zijlstra
2009-02-27 10:12 ` Jiri Slaby
2009-02-27 10:14 ` Jiri Slaby
2009-02-27 10:32 ` Andrew Morton
2009-02-27 13:04 ` Sitsofe Wheeler
2009-02-27 13:49 ` Jiri Slaby
2009-02-27 23:12 ` Sitsofe Wheeler
2009-02-28 0:20 ` Eric Anholt
2009-02-28 8:31 ` Jiri Slaby
2009-02-28 8:47 ` Andrew Morton
2009-02-28 9:00 ` Eric Anholt
2009-02-28 18:24 ` Bruno Prémont
2009-02-28 19:57 ` Eric Anholt
2009-02-28 17:11 ` Keith Packard [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=1235841119.4162.5.camel@aiko.keithp.com \
--to=keith.packard@intel.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.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