You are not logged in.
Anyone know why I'm getting the following "mtrr: type mismatch" comments at system boot after upgrading to the newly released kernel?
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,8000000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,4000000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,2000000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,1000000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,800000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,400000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,200000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,100000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,80000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,40000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,20000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,10000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,8000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,4000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,2000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: type mismatch for e0000000,1000 old: write-back new: write-combining
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x800 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x400 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x200 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x100 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x80 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x40 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x20 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x10 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x8 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x4 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x2 base: 0xe0000000
Jul 8 20:34:53 compuser mtrr: size and base must be multiples of 4 kiB
Jul 8 20:34:53 compuser mtrr: size: 0x1 base: 0xe0000000
I never had this with any of the previous kernels.
Thanks in advance for any help!
Edit: Okay, I've gone ahead and opened a bug report on this because I haven't changed anything on the system other than upgrading to the new kernel.
oz
Offline
hmmm - grep mtrr /etc/sysctrl.conf ? does that return anything? if so, I'd say comment it out - otherwise, do nothing, heh 8)
Offline
Hi, phrakture - - thanks for the suggestion but I've already returned to the previous kernel and the long series of mtrr messages went away. I didn't run across any other problems with the kernel.
The default Archlinux kernels usually work well for me so I might wait for the next kernel upgrade, or perhaps go ahead and compile a custom kernel.
Thanks again!
oz
Offline
Update in case anyone else is experiencing this...
I've still been getting these errors on all the updated stock kernels ever since 2.6.12 was released. It appears to be a kernel bug, and hopefully will be patched soon.
In the interim, the only two ways I've found to stop these errors are to add video=vesafb:nomtrr to the kernel line in my menu.lst file, or add video=vesafb:mtrr:2 to the same line.
oz
Offline