Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2932 - kernel26 2.6.12.2-1 "mtrr: type mismatch"

Attached to Project: Arch Linux
Opened by ozar (ozar) - Saturday, 09 July 2005, 02:48 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 30 December 2005, 21:17 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading to kernel26 2.6.12.2-1 I'm getting the messages below at system boot, whereas I didn't get them with any of the previous kernels. Nothing else has changed on the computer system. Is this a bug, or am I incorrect in assuming it is? Thanks for any help...

[code]
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
This task depends upon

Closed by  Judd Vinet (judd)
Sunday, 08 January 2006, 22:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Magic
Comment by ozar (ozar) - Tuesday, 12 July 2005, 23:27 GMT
Some additional info:

I've gone back to the previous kernel and the mtrr messages went away. My /proc/mtrr file in the new 2.6.12.2-1 kernel had code "something like this" in it:

reg00: base=0x00000000 ( 0MB), size=9804620MB: write-back, count=1



Whereas the same file in the 2.6.11.x kernel looks like this:

reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1

Hope this helps... :)
Comment by arjan timmerman (blaasvis) - Wednesday, 02 November 2005, 10:16 GMT
is this resolved in newer versions of the kernel ?
Comment by ozar (ozar) - Wednesday, 02 November 2005, 15:26 GMT
No, it hasn't been fixed yet in the 2.6.12 or 2.6.13 kernels, but I'm not sure about the 2.6.14 kernel that was recently put into testing. I read elsewhere that this is an upstream kernel bug that will eventually be patched, but I can't say for certain.
Comment by ozar (ozar) - Sunday, 08 January 2006, 16:46 GMT
Just an update on this... after upgrading to the latest udev, hwdetect, and initrd, I'm no longer getting the above-mentioned errors. I'm not really sure which one caused the errors to go away, but I relatively certain it was one of them.

oz

Loading...