I've been trying to compile X from CVS for some time. Each time the build completes successfully, but I always get a mess of errors like this in my syslogs:
/var/log/sys.log:Dec 7 23:47:37 minerva kernel: mtrr: no more MTRRs available /var/log/sys.log:Dec 7 23:47:37 minerva kernel: mtrr: base(0xe8000000) is not a ligned on a size(0x1f00000) boundary /var/log/sys.log:Dec 7 23:48:34 minerva kernel: mtrr: no MTRR for e9e00000,1000 00 found /var/log/sys.log:Dec 7 23:48:51 minerva kernel: mtrr: no more MTRRs available /var/log/sys.log:Dec 7 23:48:52 minerva kernel: mtrr: base(0xe8000000) is not a ligned on a size(0x1f00000) boundary /var/log/sys.log:Dec 7 23:49:30 minerva kernel: mtrr: no MTRR for e9e00000,1000 00 found /var/log/sys.log:Dec 7 23:58:15 minerva kernel: mtrr: no more MTRRs available /var/log/sys.log:Dec 7 23:58:15 minerva kernel: mtrr: base(0xe8000000) is not a ligned on a size(0x1f00000) boundary I can get into X just fine, usually. twvm has no problems, neither does Window Maker. However, GNOME dies horribly. If I try to start gnome-session from Window Maker, nothing happens. If I have it in .xinitrc, X starts up, runs for about 8 seconds, and right before the GNOME splash screen would come up, X would die from SIGSEGV. The MTRR errors occur indepedently of what window manager I'm using or what's in my startup files. I also have info on what MTRRs are being allocated. Here's what /proc/mtrr looks like when X is functioning normally (ie, I'm running my 4.1.0 release compile from a while back), with lines allocated by the X server denoted with two asterisks: reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x20000000 ( 512MB), size= 1MB: write-back, count=1 reg02: base=0x20000000 ( 512MB), size= 1MB: uncachable, count=1 reg03: base=0xf8000000 (3968MB), size= 64MB: write-combining, count=1 ** reg04: base=0xe8000000 (3712MB), size= 16MB: write-combining, count=1 ** reg05: base=0xe9000000 (3728MB), size= 8MB: write-combining, count=1 ** reg06: base=0xe9800000 (3736MB), size= 4MB: write-combining, count=1 ** reg07: base=0xe9c00000 (3740MB), size= 2MB: write-combining, count=1 Here's what the 4.1.99 CVS allocates since I started trying it around Nov. 29: reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 reg01: base=0x20000000 ( 512MB), size= 1MB: write-back, count=1 reg02: base=0x20000000 ( 512MB), size= 1MB: uncachable, count=1 reg03: base=0xf8000000 (3968MB), size= 64MB: write-combining, count=1 ** reg04: base=0xe9e00000 (3742MB), size= 1MB: write-combining, count=1 ** reg05: base=0xe9d00000 (3741MB), size= 1MB: write-combining, count=1 ** reg06: base=0xe9c00000 (3740MB), size= 1MB: write-combining, count=1 ** reg07: base=0xe9b00000 (3739MB), size= 1MB: write-combining, count=1 This is obviously not correct. I know what's wrong, but I don't know why. I've tried this with two Linux kernels (2.4.14 and 2.4.16) with the same results. This occurs with both the "default" X CVS drivers for my card (ati.2 drivers, AIW Radeon AGP 32mb) and the latest gatos CVS. XFree86 4.1.0 with normal and gatos drivers both work fine, this only occurs with XFree CVS. Any ideas? Matt _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
