Bug 18312 - radeon RS880 kernel output spam.
Summary: radeon RS880 kernel output spam.
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-12 11:12 UTC by david b
Modified: 2010-10-21 14:17 UTC (History)
0 users

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description david b 2010-09-12 11:12:59 UTC
This may have already been fixed but I have a RS880 ATI graphics card and 
dmesg is being filled with:
"[88799.602783] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88802.135375] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88809.575335] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88809.752431] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88810.380865] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88817.266426] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88817.907848] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88827.752082] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88829.038167] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88831.984730] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88832.807269] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88833.100465] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88834.200435] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88837.028771] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88847.448529] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[88847.916908] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[89080.083880] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[91364.175732] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[91371.600820] radeon 0000:01:05.0: ffff880110f43600 reserve failed for wait
[94230.267064] radeon 0000:01:05.0: ffff880104cb0000 reserve failed for wait
[97792.173935] radeon 0000:01:05.0: ffff880044629200 reserve failed for wait
"
kind of messages. I do not have debugging on for the radeon module. So maybe it is CONFIG_SLUB_DEBUG=y 

(It isn't a continual flood - it just occurs often enough to be rather annoying :/ ).


glxheads 
glxheads: exercise multiple GLX connections (any key = exit)
Usage:
  glxheads xdisplayname ...
Example:
  glxheads :0 mars:0 venus:1
Name: :0.0
  Display:     0x1669010
  Window:      0x4000002
  Context:     0x1676420
  GL_VERSION:  1.5 Mesa 7.7.1
  GL_VENDOR:   Advanced Micro Devices, Inc.
  GL_RENDERER: Mesa DRI R600 (RS880 9715) 20090101  TCL DRI2


(II) Primary Device is: PCI 01@00:05:0
(II) [KMS] Kernel modesetting enabled.
(II) RADEON(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 24/32
(==) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(--) RADEON(0): Chipset: "ATI Radeon HD 4290" (ChipID = 0x9715)
(II) RADEON(0): PCI card detected
(WW) RADEON(0): Color tiling is not yet supported on R600/R700
(II) RADEON(0): KMS Color Tiling: disabled
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:01:05.0
Comment 1 david b 2010-10-08 12:28:50 UTC
diff -Nurp  radeon_object.h radeon_object.h.orig
--- radeon_object.h	2010-10-08 23:27:44.000000000 +1100
+++ radeon_object.h.orig	2010-10-08 23:28:10.000000000 +1100
@@ -125,9 +125,9 @@ static inline int radeon_bo_wait(struct 
 
 	r = ttm_bo_reserve(&bo->tbo, true, no_wait, false, 0);
 	if (unlikely(r != 0)) {
-		/*if (r != -ERESTARTSYS)
+		if (r != -ERESTARTSYS)
 			dev_err(bo->rdev->dev, "%p reserve failed for wait\n", bo);
-		*/
+
 		return r;
 	}
 	spin_lock(&bo->tbo.lock);

Just commenting it out removes the dmesg spam. imho the output isn't useful to end users like my self :)

Note You need to log in before you can comment on or make changes to this bug.