Re: [BUG?] mtrr sanitizer fails on Latitude E6230
Yinghai Lu writes: > On Thu, Nov 7, 2013 at 12:25 AM, Mikael Pettersson > wrote: > > Yinghai Lu writes: > > > On Wed, Nov 6, 2013 at 1:16 AM, Mikael Pettersson > > wrote: > > > > I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and > > noticed that > > > > the mtrr sanitizer failed on it: > > > > > > > > === snip === > > > > Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 > > (prerelease) (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013 > > > > Command line: ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM > > rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > > KEYTABLE=sv-latin1 > > > ... > > > gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: > > 6M > > > ... > > > > mtrr_cleanup: can not find optimal value > > > > please specify mtrr_gran_size/mtrr_chunk_size > > > > === snip === > > > > > > > > For now I'm disabling the mtrr sanitizer in this machine's kernel. > > > > > > Can you try to boot with "mtrr_gran_size=8m mtrr_chunk_size=64m" ? > > > > That results in: > > > > reg 0, base: 0GB, range: 8GB, type WB > > reg 1, base: 8GB, range: 512MB, type WB > > reg 2, base: 3584MB, range: 512MB, type UC > > reg 3, base: 3520MB, range: 64MB, type UC > > reg 4, base: 3512MB, range: 8MB, type UC > > reg 5, base: 8688MB, range: 16MB, type UC > > reg 6, base: 8680MB, range: 8MB, type UC > > reg 7, base: 8678MB, range: 2MB, type UC > > total RAM covered: 8094M > > gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M > > New variable MTRRs > > reg 0, base: 0GB, range: 2GB, type WB > > reg 1, base: 2GB, range: 1GB, type WB > > reg 2, base: 3GB, range: 256MB, type WB > > reg 3, base: 3328MB, range: 128MB, type WB > > reg 4, base: 3456MB, range: 64MB, type WB > > reg 5, base: 3512MB, range: 8MB, type UC > > reg 6, base: 4GB, range: 4GB, type WB > > reg 7, base: 8GB, range: 512MB, type WB > > reg 8, base: 8672MB, range: 32MB, type UC > > e820: update [mem 0xdb80-0x] usable ==> reserved > > e820: update [mem 0x21e00-0x21e5f] usable ==> reserved > ... > >> modified: [mem 0x00021e00-0x00021e5f] reserved > > that is right, it throw 6M away. > > Did you notice any slowness or speeding for x window? I'm not noticing any change. i915 kernel driver + xorg's intel driver. > What does /proc/mtrr look like after xwindow is started? reg00: base=0x0 (0MB), size= 2048MB, count=1: write-back reg01: base=0x08000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x0c000 ( 3072MB), size= 256MB, count=1: write-back reg03: base=0x0d000 ( 3328MB), size= 128MB, count=1: write-back reg04: base=0x0d800 ( 3456MB), size= 64MB, count=1: write-back reg05: base=0x0db80 ( 3512MB), size=8MB, count=1: uncachable reg06: base=0x1 ( 4096MB), size= 4096MB, count=1: write-back reg07: base=0x2 ( 8192MB), size= 512MB, count=1: write-back reg08: base=0x21e00 ( 8672MB), size= 32MB, count=1: uncachable /Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] mtrr sanitizer fails on Latitude E6230
On Thu, Nov 7, 2013 at 12:25 AM, Mikael Pettersson wrote: > Yinghai Lu writes: > > On Wed, Nov 6, 2013 at 1:16 AM, Mikael Pettersson > wrote: > > > I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and noticed > that > > > the mtrr sanitizer failed on it: > > > > > > === snip === > > > Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 > (prerelease) (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013 > > > Command line: ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM > rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > KEYTABLE=sv-latin1 > > ... > > gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M > > ... > > > mtrr_cleanup: can not find optimal value > > > please specify mtrr_gran_size/mtrr_chunk_size > > > === snip === > > > > > > For now I'm disabling the mtrr sanitizer in this machine's kernel. > > > > Can you try to boot with "mtrr_gran_size=8m mtrr_chunk_size=64m" ? > > That results in: > > reg 0, base: 0GB, range: 8GB, type WB > reg 1, base: 8GB, range: 512MB, type WB > reg 2, base: 3584MB, range: 512MB, type UC > reg 3, base: 3520MB, range: 64MB, type UC > reg 4, base: 3512MB, range: 8MB, type UC > reg 5, base: 8688MB, range: 16MB, type UC > reg 6, base: 8680MB, range: 8MB, type UC > reg 7, base: 8678MB, range: 2MB, type UC > total RAM covered: 8094M > gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M > New variable MTRRs > reg 0, base: 0GB, range: 2GB, type WB > reg 1, base: 2GB, range: 1GB, type WB > reg 2, base: 3GB, range: 256MB, type WB > reg 3, base: 3328MB, range: 128MB, type WB > reg 4, base: 3456MB, range: 64MB, type WB > reg 5, base: 3512MB, range: 8MB, type UC > reg 6, base: 4GB, range: 4GB, type WB > reg 7, base: 8GB, range: 512MB, type WB > reg 8, base: 8672MB, range: 32MB, type UC > e820: update [mem 0xdb80-0x] usable ==> reserved > e820: update [mem 0x21e00-0x21e5f] usable ==> reserved ... >> modified: [mem 0x00021e00-0x00021e5f] reserved that is right, it throw 6M away. Did you notice any slowness or speeding for x window? What does /proc/mtrr look like after xwindow is started? Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [BUG?] mtrr sanitizer fails on Latitude E6230
Yinghai Lu writes: > On Wed, Nov 6, 2013 at 1:16 AM, Mikael Pettersson > wrote: > > I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and noticed that > > the mtrr sanitizer failed on it: > > > > === snip === > > Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 > > (prerelease) (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013 > > Command line: ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM > > rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 > > KEYTABLE=sv-latin1 > ... > gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M > ... > > mtrr_cleanup: can not find optimal value > > please specify mtrr_gran_size/mtrr_chunk_size > > === snip === > > > > For now I'm disabling the mtrr sanitizer in this machine's kernel. > > Can you try to boot with "mtrr_gran_size=8m mtrr_chunk_size=64m" ? That results in: Linux version 3.12.0-test (mikpe@barley) (gcc version 4.8.3 20131017 (prerelease) (GCC) ) #1 SMP Thu Nov 7 09:12:14 CET 2013 Command line: mtrr_gran_size=8m mtrr_chunk_size=64m ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=sv-latin1 KERNEL supported cpus: Intel GenuineIntel e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x-0x0009d3ff] usable BIOS-e820: [mem 0x0009d400-0x0009] reserved BIOS-e820: [mem 0x000e-0x000f] reserved BIOS-e820: [mem 0x0010-0x1fff] usable BIOS-e820: [mem 0x2000-0x201f] reserved BIOS-e820: [mem 0x2020-0x40003fff] usable BIOS-e820: [mem 0x40004000-0x40004fff] reserved BIOS-e820: [mem 0x40005000-0xd5f09fff] usable BIOS-e820: [mem 0xd5f0a000-0xd5ff] reserved BIOS-e820: [mem 0xd600-0xd6751fff] usable BIOS-e820: [mem 0xd6752000-0xd67f] reserved BIOS-e820: [mem 0xd680-0xd6fb2fff] usable BIOS-e820: [mem 0xd6fb3000-0xd6ff] ACPI data BIOS-e820: [mem 0xd700-0xd86fbfff] usable BIOS-e820: [mem 0xd86fc000-0xd87f] ACPI NVS BIOS-e820: [mem 0xd880-0xd96d4fff] usable BIOS-e820: [mem 0xd96d5000-0xda054fff] reserved BIOS-e820: [mem 0xda055000-0xda097fff] ACPI NVS BIOS-e820: [mem 0xda098000-0xdaadcfff] usable BIOS-e820: [mem 0xdaadd000-0xdafe] reserved BIOS-e820: [mem 0xdaff-0xdaff] usable BIOS-e820: [mem 0xdb80-0xdf9f] reserved BIOS-e820: [mem 0xf800-0xfbff] reserved BIOS-e820: [mem 0xfec0-0xfec00fff] reserved BIOS-e820: [mem 0xfed0-0xfed03fff] reserved BIOS-e820: [mem 0xfed1c000-0xfed1] reserved BIOS-e820: [mem 0xfee0-0xfee00fff] reserved BIOS-e820: [mem 0xff00-0x] reserved BIOS-e820: [mem 0x0001-0x00021e5f] usable NX (Execute Disable) protection: active SMBIOS 2.7 present. DMI: Dell Inc. Latitude E6230/0Y47PX, BIOS A11 08/27/2013 e820: update [mem 0x-0x0fff] usable ==> reserved e820: remove [mem 0x000a-0x000f] usable e820: last_pfn = 0x21e600 max_arch_pfn = 0x4 MTRR default type: uncachable MTRR fixed ranges enabled: 0-9 write-back A-B uncachable C-C write-protect D-E7FFF uncachable E8000-F write-protect MTRR variable ranges enabled: 0 base 0 mask E write-back 1 base 2 mask FE000 write-back 2 base 0E000 mask FE000 uncachable 3 base 0DC00 mask FFC00 uncachable 4 base 0DB80 mask FFF80 uncachable 5 base 21F00 mask FFF00 uncachable 6 base 21E80 mask FFF80 uncachable 7 base 21E60 mask FFFE0 uncachable 8 disabled 9 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 original variable MTRRs reg 0, base: 0GB, range: 8GB, type WB reg 1, base: 8GB, range: 512MB, type WB reg 2, base: 3584MB, range: 512MB, type UC reg 3, base: 3520MB, range: 64MB, type UC reg 4, base: 3512MB, range: 8MB, type UC reg 5, base: 8688MB, range: 16MB, type UC reg 6, base: 8680MB, range: 8MB, type UC reg 7, base: 8678MB, range: 2MB, type UC total RAM covered: 8094M gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M New variable MTRRs reg 0, base: 0GB, range: 2GB, type WB reg 1, base: 2GB, range: 1GB, type WB reg 2, base: 3GB, range: 256MB, type WB reg 3, base: 3328MB, range: 128MB, type WB reg 4, base: 3456MB, range: 64MB, type WB reg 5, base: 3512MB, range: 8MB, type UC reg 6, base: 4GB, range: 4GB, type WB reg 7, base: 8GB, range: 512MB, type WB reg 8, base: 8672MB, range: 32MB, type UC e820: update [mem 0xdb80-0x] usable ==> reserved e820: update [mem 0x21e
Re: [BUG?] mtrr sanitizer fails on Latitude E6230
On Wed, Nov 6, 2013 at 1:16 AM, Mikael Pettersson wrote: > I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and noticed that > the mtrr sanitizer failed on it: > > === snip === > Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 (prerelease) > (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013 > Command line: ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD > rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=sv-latin1 ... gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M ... > mtrr_cleanup: can not find optimal value > please specify mtrr_gran_size/mtrr_chunk_size > === snip === > > For now I'm disabling the mtrr sanitizer in this machine's kernel. Can you try to boot with "mtrr_gran_size=8m mtrr_chunk_size=64m" ? Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
