From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: Dave Airlie <airlied@linux.ie>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [drm:radeon_cp_idle] *ERROR* radeon_cp_idle called without lock held
Date: Mon, 02 Jun 2008 01:22:40 +0200 [thread overview]
Message-ID: <1212362560.9513.2.camel@odie.local> (raw)
In-Reply-To: <alpine.DEB.0.82.0806012310440.5760@skynet.skynet.ie>
søn, 01 06 2008 kl. 23:11 +0100, skrev Dave Airlie:
> >
> > Backtrace:
> > 0: X(xf86SigHandler+0x80) [0x80d29f0]
> > 1: [0xb7f54400]
> > 2: /usr/lib/xorg/modules/input//evdev_drv.so [0xb7aab90e]
> > 3: X [0x80d2b87]
> > 4: X [0x80b6065]
> > 5: [0xb7f54400]
> > 6: X(Dispatch+0x81) [0x808d5d1]
> > 7: X(main+0x485) [0x8074bb5]
> > 8: /lib/libc.so.6(__libc_start_main+0xdc) [0xb7c813ec]
> > 9: X(FontFileCompleteXLFD+0x229) [0x8073f21]
> >
> > Fatal server error:
> > Caught signal 11. Server aborting
>
> Looks like X is dying in its input driver, which is causing the video
> driver to do something without the lock, so its an X.org configuration or
> build issues.. best ask on xorg@lists.freedesktop.org
You are right, this was simply freedesktop.org bug #13991 [1] which has
been solved since January [2], but not made it into a release of
xf86-input-evdev yet.
So I still want to do something about the throttling issue of the kernel
messages, but that's gonna wait as I'm off to bed now.
Thanks Dave.
Simon Holm Thøgersen
[1] http://bugs.freedesktop.org/show_bug.cgi?id=13991
[2]
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-input-evdev.git;a=commit;h=5adbc6b98ca1da9a426528ce0df64a992feff3bd
prev parent reply other threads:[~2008-06-01 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 19:16 Simon Holm Thøgersen
2008-06-01 21:19 ` Dave Airlie
[not found] ` <1212358046.6296.12.camel@odie.local>
2008-06-01 22:11 ` Dave Airlie
2008-06-01 23:22 ` Simon Holm Thøgersen [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=1212362560.9513.2.camel@odie.local \
--to=odie@cs.aau.dk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®