Comment 9 for bug 224404

Revision history for this message
Kurt Peterschmidt (kurtpete) wrote : Re: MTRR is not properly setup on Intel Northbridge Chipset (P35) and Asus Motherboard with Memory Remapping Enabled

I'm having a similar issue with a Dell Optiplex 755 with 4gb and an amd64 install of Hardy. The installed video card is an ATI hd2400xt with 256mb. Using the fglrx driver results in an immediate crash at the start of X with 4gb in the machine. Remove 1 stick of ram (leaving 3gb) and all is well.

cat /proc/mtrr with 4gb in the machine gives:

reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1
reg02: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg03: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1

...and with 3gb gives:

reg00: base=0x00000000 ( 0MB), size=65536MB: write-back, count=1
reg01: base=0xbef00000 (3055MB), size= 1MB: uncachable, count=1
reg02: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1

very little in the Xorg log file, when the crash occurs except for:

(EE) fglrx(0): [drm] failed to remove DRM signal handler
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x2000 at 0x7f4a97a13000
(II) fglrx(0): [drm] Closed DRM master.

I have the most recent BIOS update available from Dell, and I've also tried the kernel in hardy-proposed (2.6.24-17-generic). The issue has persisted. I also have the most recent fglrx driver (8.4) installed through envyNG.

A similarly spec'd machine with the 32-bit install of Hardy does not experience this issue.

This appears to either be a bios or a kernel issue, I'm not sure which...