mtrr: type mismatch for e8000000,8000000 old: write-back new: write-combining <arjan> X vs mtrr driver disagreement <arjan> then bug the X team for sure 00:00.0 Host bridge: Intel Corp. E7505 Memory Controller Hub (rev 03) 00:00.1 Class ff00: Intel Corp. E7505/E7205 Series RAS Controller (rev 03) 00:01.0 PCI bridge: Intel Corp. E7505/E7205 PCI-to-AGP Bridge (rev 03) 00:02.0 PCI bridge: Intel Corp. E7505 Hub Interface B PCI-to-PCI Bridge (rev 03)00:02.1 Class ff00: Intel Corp. E7505 Hub Interface B PCI-to-PCI Bridge RAS Controller (rev 03) 00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82) 00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801DB (ICH4) IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation NV34GL [Quadro FX 500/600 PCI] (rev a1) 02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04) 02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04) 03:03.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01) (using stock nv driver)
Created attachment 106435 [details] config file
Created attachment 106436 [details] xorg log
Configure the system to boot into runlevel 3, so that X does not start after a clean system reboot. Then capture the output of /proc/mtrr so we know what MTRRs are set prior to X starting up. Also check if /var/log/messages contains any MTRR related errors or messages prior to starting X. Then start up X using "startx", and attach the /proc/mtrr results from the X session, and /var/log/messages MTRR entries, as well as the X log if it differs from the attached one. TIA
Created attachment 106437 [details] /proc/mtrr before X
Created attachment 106438 [details] /proc/mtrr after starting X
Created attachment 106439 [details] dmesg before X
Created attachment 106440 [details] dmesg after starting X
Please read this thread â http://www.ussg.iu.edu/hypermail/linux/kernel/0411.3/0314.html - it seems that this bug was fixed in kernel 2.6.10 (this was the main reason why MPlayer was slower on 2.6 kernels; unfortunately it's still faster on 2.4 ones). There is still one question - does it need to be fixed in X.org X11 as it says Alan Cox (http://www.ussg.iu.edu/hypermail/linux/kernel/0411.3/1244.html)?
Carbon copying Alan to find out. Setting status to "NEEDINFO"
Was this ever resolved? I am seeing this issue on RHEL4 and it is seriously hurting X performance.
Red Hat Enterprise Linux customers who are experiencing issues of this nature, should contact Red Hat Global Support Services at 1-888-RED-HAT1 and discuss the issue with one of our associates. Once GSS has been contacted, they will work with the customer, engineering and other parties on finding a solution for Red Hat Enterprise Linux. Hope this helps.
This problem seems to be isolated to very few systems using Intel integrated video hardware. It isn't clear if anyone is still experiencing this problem or not in Fedora Core 4. At this point, the best advice I can give anyone who can still reproduce this, is to file a bug report in X.Org bugzilla at http://bugs.freedesktop.org, and include as many details as possible, including all of the above file attachments and any other data that might help narrow the problem down. Once you have filed a bug report in X.Org bugzilla, the upstream i810 driver maintainer (Alan Hourihane) and other developers who frequently contribute to the i810 driver codebase will see your bug report and may be able to directly troubleshoot it locally with hardware they have on hand. Once the report is filed upstream, paste the URL here and we will track the issue in the X.org bugzilla going forward.
Setting status to "NEEDINFO_REPORTER" and awaiting upstream bug report URL and status update.
https://bugs.freedesktop.org/show_bug.cgi?id=4310