[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#233832: marked as done (Radeon DRI MTRR problem)

Your message dated Mon, 26 Feb 2007 18:51:31 +0100
with message-id <45E31E23.6050706@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xlibmesa-dri
Version: 4.3.0-2

Upon upgrading from 4.3.0 pre-release packages to the recently released 
4.3.0-2 packages (thank you for your hard work!), my direct rendering
stopped working, however the problem has identical symptoms to those 
errors already posted here so I am assuming it is the same sse_test_dummy
missing symbol others noted.

While I was digging for this problem however, I found this as the only
fault in my xfree86 log file (radeon mobility 9000 card, 2.6.2 kernel,
kernel radeon driver):

(WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x2000000)
(WW) RADEON(0): Cannot read colourmap from VGA.  Will restore with default

(don't know if the second one is new or old.)  Matching this, the 
following appears in dmesg:

mtrr: 0xe8000000,0x2000000 overlaps existing 0xe8000000,0x1000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0
mtrr: 0xe8000000,0x2000000 overlaps existing 0xe8000000,0x1000000

I included the [drm] message to show the exact context of messages appearing
in dmesg--they appear exact in the order show there, with no other lines
between.

cat /proc/mtrr yields the following:

reg00: base=0x00000000 (   0MB), size= 256MB: write-back, count=1
reg01: base=0x10000000 ( 256MB), size= 128MB: write-back, count=1
reg02: base=0xfeda0000 (4077MB), size= 128KB: write-through, count=1
reg03: base=0xe8000000 (3712MB), size=  16MB: write-combining, count=1
reg04: base=0xf0000000 (3840MB), size=  64MB: write-combining, count=1

I'm attaching the XFree86.0.log file; my XF86Config-4 has nothing
interesting in it so I'm not wasting bits with that.

thanks again for the hard work,
take care

Attachment: XFree86.0.log
Description: Binary data


--- End Message ---
--- Begin Message --- 
Closing this bug since I didn't get any reply from the submitter (or
repliers) after my ping more than a month ago. If anybody ever
reproduces this problem, feel free to reopen.

Brice

--- End Message ---
Reply to: