Red Hat Bugzilla – Bug 61900
Kernel DRM errors in log with Radeon 7500
Last modified: 2007-04-18 12:41:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314
Description of problem:
After upgrading from 7.2 to Skipjack I am getting the following error message in
Mar 24 21:28:41 garfield kernel: [drm:radeon_freelist_get] *ERROR* returning NULL!
Mar 24 21:32:00 garfield last message repeated 40 times
Mar 24 21:33:26 garfield last message repeated 15 times
Mar 24 21:36:05 garfield last message repeated 22 times
Mar 24 21:37:13 garfield last message repeated 52 times
Mar 24 21:38:30 garfield last message repeated 50 times
Mar 24 21:39:43 garfield last message repeated 84 times
and so on....
This error. as far as I can tell so far, isn't causing any problems other then
filling up /var/log/messages.
I was running XFree86-4.2.0-6.47 and kernel-2.4.17-0.18 on my 7.2 install, but I
was not getting this error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Upgrade from 7.2
Actual Results: Error messages in /var/log/messages
Expected Results: No error messages in /var/log/messages
Athlon XP 1800+
Ati Radeon 7500
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon 7500 QW (prog-if
Subsystem: ATI Technologies Inc: Unknown device 013a
Flags: bus master, stepping, 66Mhz, medium devsel, latency 32, IRQ 10
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at c000 [size=256]
Memory at e1000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities:  AGP version 2.0
Capabilities:  Power Management version 2
An update to kernel-2.4.18-0.8 seems to have cured this problem. :-) I am
running 2.4.18-0.8 and XFree86-4.2.0-6.48 now.
Ok let me know if this comes back....
Ok, I tried to see if I could reproduce the error and it is still there. It just
doesn't occur as frequently with 2.4.18-0.8. I noticed it doesn't occur with all
3D games. Playing RTCW will produce the error everytime.
Nuked the printk with the error.... doesn't look like a critical error so
printk'ing on it is BAD.