Bug 484682
| Summary: | drm: X: "reserve_memtype failed/conflicting memory types d0000000-e0000000 uncached-minus<->write-combining" messages | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom London <selinux> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | airlied, jglisse, kernel-maint, kmcmartin, notting, zkabelac |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-14 14:47:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Tom London
2009-02-09 14:58:08 UTC
I don't get these booting kernel-2.6.29-0.96.rc3.git12.fc11.x86_64 with xorg-x11-server-Xorg-1.5.99.902-5.fc11.x86_64. Two subsequent boots with kernel-2.6.29-0.99.rc4.git1.fc11.x86_64 did not produce the above errors ..... I'm "... Dazed and confused ..." ;) I'll continue to monitor. 11 subsequent boots and this has not repeated..... Created attachment 331894 [details]
/var/log/messages from boot with lots of 'kernel: Xorg:2805 conflicting memory types'/'reserve_memtype failed' messages
Got these again.....
Feb 13 17:26:13 tlondon gdm-simple-slave[2804]: DEBUG(+): GdmServer: Got USR1 from X server - emitting READY
Feb 13 17:26:13 tlondon kernel: Xorg:2805 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining
Feb 13 17:26:13 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus
Feb 13 17:26:13 tlondon kernel: Xorg:2805 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining
Feb 13 17:26:13 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus
Feb 13 17:26:14 tlondon kernel: Xorg:2805 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining
Feb 13 17:26:14 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus
I attach a complete /var/log/messages from this run.
system appeared to function ok....
Continue to get these (not every boot): Feb 19 07:16:14 tlondon avahi-daemon[3806]: Registering new address record for 192.168.1.105 on eth1.IPv4. Feb 19 07:16:14 tlondon dhclient: bound to 192.168.1.105 -- renewal in 36568 seconds. Feb 19 07:16:15 tlondon kernel: Xorg:3926 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining Feb 19 07:16:15 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Feb 19 07:16:15 tlondon nscd: 4038 Access Vector Cache (AVC) started Feb 19 07:16:15 tlondon NetworkManager: <info> (eth1): device state change: 7 -> 8 Feb 19 07:16:15 tlondon nscd: 4059 Access Vector Cache (AVC) started and Feb 19 07:16:16 tlondon gdm-simple-slave[3923]: DEBUG(+): GdmServer: Got USR1 from X server - emitting READY Feb 19 07:16:16 tlondon kernel: Xorg:3926 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining Feb 19 07:16:16 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Feb 19 07:16:16 tlondon kernel: Xorg:3926 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining Feb 19 07:16:16 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Feb 19 07:16:16 tlondon kernel: Xorg:3926 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining Feb 19 07:16:16 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Feb 19 07:16:16 tlondon kernel: Xorg:4160 freeing invalid memtype d0000000-e0000000 Feb 19 07:16:16 tlondon gdm-simple-slave[3923]: DEBUG(+): GdmSlave: Server is ready - opening display :0 Feb 19 07:16:16 tlondon kernel: Xorg:3926 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining Feb 19 07:16:16 tlondon kernel: reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Here's the boot line for this run: Feb 19 07:15:52 tlondon kernel: Linux version 2.6.29-0.134.rc5.git2.fc11.x86_64 (mockbuild.phx.redhat.com) (gcc version 4.4.0 20090217 (Red Hat 4.4.0-0.20) (GCC) ) #1 SMP Thu Feb 19 03:35:39 EST 2009 I'm not 100% sure, but it appears from the "timestamps" that I only get these messages when I boot with an old LCD external monitor (system is Thinkpad X200) that "doesn't work" with KMS. I have to boot with "nomodeset" to get the system up. Could there be a connection? *** Bug 486499 has been marked as a duplicate of this bug. *** Possibly? Try booting with enable_mtrr_cleanup mtrr_spare_reg_nr=2? Otoh, I think I saw a clean up to use ioremap_wc in the DRM for this... adding airlied to CC. cheers, Kyle I tried booting with "enable_mtrr_cleanup mtrr_spare_reg_nr=2" and I still get spew: Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.29-0.153.rc6.git2.fc11.x86_64 (mockbuild.phx.redhat.com) (gcc version 4.4.0 20090219 (Red Hat 4.4.0-0.21) (GCC) ) #1 SMP Tue Feb 24 23:43:31 EST 2009 Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet init=/sbin/bootchartd enable_mtrr_cleanup mtrr_spare_reg_nr=2 nomodeset KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009ec00 (usable) <<<<<SNIP>>>>>> Xorg:3831 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Xorg:3831 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Xorg:3984 freeing invalid memtype d0000000-e0000000 Xorg:3831 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Xorg:3987 freeing invalid memtype d0000000-e0000000 Xorg:3831 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Xorg:3992 freeing invalid memtype d0000000-e0000000 Xorg:3831 conflicting memory types d0000000-e0000000 uncached-minus<->write-combining reserve_memtype failed 0xd0000000-0xe0000000, track uncached-minus, req uncached-minus Xorg:3995 freeing invalid memtype d0000000-e0000000 Booting without "nomodeset": X does not detect my (old) Mitsubishi LCD monitor, only laptop screen. I'll few more comments about this problem. I'm noticing this on my laptop T61 - I'm running vanilla kernel build from Linus tree (some post 2.6.29-rc6 atm.) I've tried to use both UXA & EXA acceleration - also git build for drm libs and intel driver - and still getting the same problem. It might help that my friend with similar hw configuration - but just running Ubuntu xserver 1.5.99.902, again with similar vanilla kernel and git versions for drm (1c381092a310af9b1b39b3a983ad5760b71a9025) and intel driver (668b2352a47bcfba75fe0492a5805726222755eb) doesn't show such problem. My mtrr looks like this: reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x0bf700000 ( 3063MB), size= 1MB, count=1: uncachable reg03: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable reg04: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back reg05: base=0x13c000000 ( 5056MB), size= 64MB, count=1: uncachable reg06: base=0x0e0000000 ( 3584MB), size= 256MB, count=2: write-combining Does booting with the 'nopat' kernel option make this go away? Just to be clear: I currently have to boot with "nomodeset" with this monitor. You want me to try "nomodeset nopat"? Or just "nopat"? Both? [I'll try tonight when I get home....] Created attachment 333606 [details]
dmesg output booting kernel-2.6.29-0.172.rc6.git4.fc11.x86_64 with "nomodeset nopat"
Booting with both "nomodeset" and "nopat" makes the "reserve_memtype" type messages "go away".
Attached is dmesg output from booting that way.....
"nopat" also seems to "fix" the problem of compiz "white screening" on this monitor: https://bugzilla.redhat.com/show_bug.cgi?id=486375 This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping There was few bugs in kernel PAT support, testing newer kernel will likely fix your issues. Can you test with fedora 12 livecd and report if it works with it. I've been running Rawhide, and haven't seen this in ages.... So yes, works with F12/Rawhide. Ok closing. |