https://bugs.freedesktop.org/show_bug.cgi?id=28402 --- Comment #44 from Da Fox <da_fox@xxxxxxxxxxxxxxxxx> 2010-09-06 08:07:07 PDT --- (In reply to comment #43) > Since I don't know, what's important when calling radeontool, I'll better tell > you what I did: > I booted the new kernel, started X (via kdm), switched to a vt and used > radeontools. I'm sorry for not elaborating more, but I'm no expert myself :) However I don't think it is necessary to switch to a vt, it may in fact not be what is required. My understanding is that radeontool captures the current state of the graphics card (the important bits at least). This is likely different between X and a vt, however we are interested in the state the card has in X (since that is where it freezes). Could please also post the results of running radeontool from within X, just to be sure we capture all relevant information? > (In reply to comment #40) > > if you boot with a bad kernel and run > > radeontool regset 0x130 0x70000000 > > does it stabilise any? > No. > I booted a 2.6.35-r3 kernel with gentoo-patches, which is known for me to > possess a high freeze-frequency and did as you said: > > $ radeontool regset 0x130 0x70000000 > OLD: 0x130 (0130) 0x40800000 (1082130432) > NEW: 0x130 (0130) 0x70000000 (1879048192) > > After a few minutes, the freeze appeared again. I have the same result, using d594e46ace22afa1621254f6f669e65430048153 + 8e36113082821980c60ce89a6c5d45fc9492fc26: # radeontool regset 0x130 0x70000000 OLD: 0x130 (0130) 0x70800000 (1887436800) NEW: 0x130 (0130) 0x70000000 (1879048192) And a freeze soon afterwards. I am currently testing d594e46ace22afa1621254f6f669e65430048153 + 8e36113082821980c60ce89a6c5d45fc9492fc26 and the following patch as suggested by Dave Airlie on IRC: ---8<--------- diff --git a/drivers/gpu/drm/radeon/r300.c b/drivers/gpu/drm/radeon/r300.c index c827738..d1a7803 100644 --- a/drivers/gpu/drm/radeon/r300.c +++ b/drivers/gpu/drm/radeon/r300.c @@ -477,7 +477,7 @@ void r300_mc_init(struct radeon_device *rdev) default: rdev->mc.vram_width = 128; break; } r100_vram_init_sizes(rdev); - base = rdev->mc.aper_base; + base = 0; if (rdev->flags & RADEON_IS_IGP) base = (RREG32(RADEON_NB_TOM) & 0xffff) << 16; radeon_vram_location(rdev, &rdev->mc, base); --->8--------- This seems to help for me, I'm still testing but I've been running for a couple of hours already and so far haven't seen a freeze yet. Could you please test this patch also? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
