From: lists@sapience.com
To: linux-kernel@vger.kernel.org
Subject: [drm:radeon_freelist_get] *ERROR* returning NULL!
Date: Fri, 16 Nov 2001 23:25:13 -0500 [thread overview]
Message-ID: <20011117042513.GA8133@sapience.com> (raw)
I have a radeon card - when I turn on dri the machine later livelocks
with X spinning its wheels generating loads of messages like
these:
[drm:radeon_freelist_get] *ERROR* returning NULL!
last message repeated 2209 times
This is triggered by trying to run (a) wolfenstein, or (b) Xconfigurator
doing a probe or (c) possibly by some screen save but I'm not 100%
certain which screensaver.
Kernel is 2.4.15-pre5 - I also changed the agp id (i860) in agp.h as per
recent patch of Nicolas Aspert (from 2532 to 2531). Without
this AGP was off and DRI was off. No problems crashes in this case.
Distro is 7.2 fully updated. Machine is Dell 530 2 x 1.7Ghx P4.
This may or may not be related but dpms doesn't work either,
XFree86 log has:
(II) Loading extension DPMS
(II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
while xset q shows
DPMS (Energy Star):
Display is not capable of DPMS
What information can I provide that might help or is this a known
problem with radeon?
Regards
Gene/
reply other threads:[~2001-11-17 4:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011117042513.GA8133@sapience.com \
--to=lists@sapience.com \
--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