From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Eric Anholt <eric@anholt.net>,
Sitsofe Wheeler <sitsofe@yahoo.com>,
airlied@linux.ie, keithp@keithp.com,
dri-devel@lists.sourceforge.net,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: i915 X lockup
Date: Sat, 28 Feb 2009 00:47:51 -0800 [thread overview]
Message-ID: <20090228004751.96d1ea8d.akpm@linux-foundation.org> (raw)
In-Reply-To: <49A8F660.10604@gmail.com>
On Sat, 28 Feb 2009 09:31:28 +0100 Jiri Slaby <jirislaby@gmail.com> wrote:
> On 28.2.2009 01:20, Eric Anholt wrote:
> > KMS support is not a feature of the server but of your 2D driver. You
> > want 2.6.2, or things will be bad.
>
> I have 2.5.0. After turning KMS off, problem seems to be solved.
>
> Anyway, I would appreciate a version of the intel driver being in the
> Kconfig text, otherwise it looks like: don't use this on machines with
> installation from stone age. If one has latest stable release of a
> distro, he doesn't even think he doesn't have "new enough userspace".
>
> For reference, the text is:
> Choose this option if you want kernel modesetting enabled by default,
> and you have a new enough userspace to support this. Running old
> userspaces with this enabled will cause pain.
Hang on.
The kernel deadlocked on struct_mutex, did it not? That's a kernel bug
regardless of what userspace you're running.
Do we know why this happened?
next prev parent reply other threads:[~2009-02-28 8:48 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 [this message]
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
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=20090228004751.96d1ea8d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=jirislaby@gmail.com \
--cc=keithp@keithp.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 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.