Summary: | mtrr: type mismatch for e8000000,8000000 old: write-back new: write-combining | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bill Nottingham <notting> | ||||||
Component: | Driver/nVidia (open) | Assignee: | Xorg Project Team <xorg-team> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | high | CC: | desrt, erik.andren, gajownik, michael.gaber, perry | ||||||
Version: | 6.8.2 | ||||||||
Hardware: | x86 (IA32) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Bill Nottingham
2005-08-30 10:29:55 UTC
Created attachment 3122 [details]
X config
Created attachment 3123 [details]
X log
X will try to setup the write-combining range for the entire AGP space. It seems you could be using some other process that setups up an MTRR before X, and it's usually an *fbdev driver that can cause this. reassigning this to Driver/nv as Bill is using an NVIDIA card not the i810 driver. Whoops, apoligies for the misfiled component. No framebuffer is in use. "me too". I get this problem with a Radeon 9600 in an Intel-based ASUS P4P800SE board. Some time ago, I filed a bug here -- http://bugzilla.ubuntu.com/show_bug.cgi?id=16122 This bugreport closed in Ubuntu some time ago. It was fixed with a new kernel version and I'm reasonably sure it was a kernel bug. Bill, are you still experiencing this problem using a current version of xorg? Closing. Please reopen if the problem still persits in a current version of xorg. Sorry about the delay. Appears fixed with a 2.6.16.x kernel and the xorg 1.0.1 server code. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.