FS#12534 - mtrr mismatch on 2 different linux-systems

Attached to Project: Arch Linux
Opened by Christian Galander (igprolin) - Monday, 22 December 2008, 13:31 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 06 April 2009, 17:29 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I can't use my tv card with more than 3 gb of ram.
I found differences between ubuntu and archlinux:

/proc/mtrr under archlinux:
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size= 512MB: write-back, count=1
reg02: base=0xa0000000 (2560MB), size= 256MB: write-back, count=1
reg03: base=0xb0000000 (2816MB), size= 128MB: write-back, count=1
reg04: base=0xb8000000 (2944MB), size= 64MB: write-back, count=1
reg05: base=0xbc000000 (3008MB), size= 16MB: write-back, count=1

/proc/mtrr under ubuntu:
reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size= 512MB: write-back, count=1
reg02: base=0xa0000000 (2560MB), size= 256MB: write-back, count=1
reg03: base=0xb0000000 (2816MB), size= 128MB: write-back, count=1
reg04: base=0xb8000000 (2944MB), size= 64MB: write-back, count=1
reg05: base=0xbc000000 (3008MB), size= 16MB: write-back, count=1
reg06: base=0xc0000000 (3072MB), size= 256MB: write-combining, count=1

under ubuntu i can use my tv card but not under archlinux.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 06 April 2009, 17:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.6.29.1
Comment by Jan de Groot (JGC) - Monday, 22 December 2008, 16:39 GMT
Try booting your system with the "nopat" kernel option.
Comment by Christian Galander (igprolin) - Monday, 22 December 2008, 17:42 GMT
I bootet my system with the nopat kernel option but without any success.
I switched back to ubuntu
Comment by Jan de Groot (JGC) - Monday, 22 December 2008, 22:35 GMT
What kernel does ubuntu use? Can you attach dmesg output of both ubuntu and archlinux kernel?
Comment by Christian Galander (igprolin) - Monday, 22 December 2008, 23:34 GMT
Sorry i remove archlinux from my harddisk but i will install it on a secondary disk in a few days. ubunut is using kernel 2.6.27.9 ( i had installed kernel26 from testing but without any success). ah i forgot .. here the dmesg from archlinux: http://nopaste.unixfreunde.de/905 ... and here from ubuntu: http://nopaste.unixfreunde.de/906
Comment by Jan de Groot (JGC) - Monday, 22 December 2008, 23:48 GMT
The one on archlinux contains "nomtrr". That won't help our debugging mtrr problems I think.
Comment by Christian Galander (igprolin) - Tuesday, 23 December 2008, 12:36 GMT
Today i installed archlinux on a second harddisk and bootet it ...
1.) with the default kernel
dmesg: http://nopaste.unixfreunde.de/907
2.) with the ubuntu kernel
dmesg: http://nopaste.unixfreunde.de/908

with the ubuntu kernel i can use my technisat skystar 2 but with the default kernel (2.6.27.10) i had no luck.
Comment by Christian Galander (igprolin) - Tuesday, 23 December 2008, 12:36 GMT
argh ... default kernel is http://nopaste.unixfreunde.de/908 and ubuntu kernel is http://nopaste.unixfreunde.de/907 .. sorry :-(
Comment by Christian Galander (igprolin) - Tuesday, 23 December 2008, 21:13 GMT
Problem solved. With the kernel config from ubuntu, now i can use my technisat skystar 2. I think it is a config error in arch's kernel config.
Comment by Glenn Matthys (RedShift) - Wednesday, 24 December 2008, 08:12 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Upstream Bugs → Kernel)
  • Task assigned to Tobias Powalowski (tpowa)
Note that write-combining is slower than write-back.
(reg06: base=0xc0000000 (3072MB), size= 256MB: write-combining, count=1 from the ubuntu kernel)
Comment by Jan de Groot (JGC) - Monday, 30 March 2009, 07:46 GMT
The latest kernel from testing should fix this issue. This version has the MTRR sanitizer enabled. If it doesn't work by default, try passing "enable_mtrr_cleanup" on the boot line, the sanitizer should restructure your MTRR setup if possible.

Loading...