From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [bk tree] DRM add a version check.. for 2.6.12 (distro kernel maintainers + drm users plz read also...)
Date: Thu, 7 Apr 2005 14:49:33 +0300 [thread overview]
Message-ID: <20050407114933.GH3858@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503281236330.27073@skynet>
Dropping Linus off this list...
On Mon, Mar 28, 2005 at 12:40:16PM +0100, Dave Airlie wrote:
> Hi Linus,
>
> In order to stop someone loading a drm driver on a wrong core this patch
> makes the driver pass in the version is was built against, this mainly
> useful for people using the DRI snapshots for cards that aren't their
> normal cards...
>
> Also for anyone who maintains a kernel for distros or builds their own
> please build your kernels with CONFIG_DRM=m not =y, from 2.6.11 onwards..
> as if you build with =y then DRI snapshots will no longer work..
I tried 2.6.12-rc2 which includes this patch, and I get DRM failures
here, which causes application and X to hang. (I got failures with 2.6.11
also.)
When accessing the machine from network, I can see that either application,
or X itself is running as close as possible to 100% CPU utilization.
Symptom is such that the application, or X-server, is executing an ioctl()
on a file-handle that has node: /dev/drm/card0 open in r/w mode.
Following is from memory:
ioctl(5, something, something)
-- Received ALARM(0) --
ioctl(5, something, something)
-- Received ALARM(0) --
that repeats as fast as possible.
I have now Radeon 9200SE card with 128 MB memory (I used to have Matrox
MGA G400 AGP with 8 MB memory - no room for anything but pixel maps), but
then I absolutely needed accelerated 3D, and had to go and get a "modern"
card.
System is running Fedora Core 4 Test-1 application space codes along
with fresh baseline 2.6.11 + 2.6.12-rc2 patchset ( = "2.6.12-rc2" ).
I observed that xscreensaver-demo running "GLForestFire" is reliably
able to hangup the desktop within minutes, IF media-automounter is
snooping around in /dev/cdrom and there is some disk. (I had FC4test1
rescue disk in there. )
With disk taken out, the system ran some 8 hours without a glitch.
Nevertheless, I then tried some fun with TuxRacer, and was able to
get the same drm hangup after an hour or so.
ANY ideas ?
/Matti Aarnio
next prev parent reply other threads:[~2005-04-07 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 11:40 Dave Airlie
2005-04-07 11:49 ` Matti Aarnio [this message]
2005-04-07 12:38 ` Dave Airlie
2005-04-07 12:53 ` Matti Aarnio
2005-04-07 13:00 ` Dave Airlie
2005-04-09 8:50 ` Matti Aarnio
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=20050407114933.GH3858@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--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®