search for: gran_siz

...nge: 1GB, type WB reg 2, base: 3256MB, range: 8MB, type UC reg 3, base: 3264MB, range: 64MB, type UC reg 4, base: 3328MB, range: 256MB, type UC reg 5, base: 3584MB, range: 512MB, type UC reg 6, base: 17150MB, range: 2MB, type UC reg 7, base: 17152MB, range: 256MB, type UC total RAM covered: 16310M gran_size: 64K chunk_size: 64K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 128K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 256K num_reg: 10 lose cover RAM: 126M gran_size: 64K chunk_size: 512K num...

Good Day All, Today I looked at the dmesg log and I notice that the following messages regarding mtrr_gran_size/mtrr_chunk_size. I am currently running CentOS 6.3 and I installed CentOS 6.2 and 6.1 and I was seeing the same errors. When I installed CentOS 5.8 on the same laptop I do not see these errors. $ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:p...

...have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs but are bit lost on the impact. The system CPU is a q6600 so it supports mtrr. It has 8gb of RAM and a G33 intel chipset (maximum memory is 8gb), 256mb onboard Intel video. Problem exists with DVD 6.2 kernel and lat...

CentOS 6.4, current, Dell PE R720. Had an issue today with a bus error, and googling only found two year old references to problems with non-Dell drives (we just added two WD Reds, and mdadm raided them). So, looking through dmesg and /var/log/messages, I ran into a *lot* of G gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 512K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 1M num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size: 2M num_reg: 10 lose cover R...

...ase: 0GB, range: 16GB, type WB reg 1, base: 16GB, range: 1GB, type WB reg 2, base: 3000MB, range: 8MB, type UC reg 3, base: 3008MB, range: 64MB, type UC reg 4, base: 3GB, range: 1GB, type UC reg 5, base: 17406MB, range: 2MB, type UC total RAM covered: 16310M Found optimal setting for mtrr clean up gran_size: 64K chunk_size: 128M num_reg: 8 lose cover RAM: 0G New variable MTRRs reg 0, base: 0GB, range: 2GB, type WB reg 1, base: 2GB, range: 1GB, type WB reg 2, base: 3000MB, range: 8MB, type UC reg 3, base: 3008MB, range: 64MB, type UC reg 4, base: 4GB, range: 4GB, type WB reg 5, bas...

...d 6 disabled 7 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 original variable MTRRs reg 0, base: 0GB, range: 16GB, type WB reg 1, base: 16GB, range: 1GB, type WB reg 2, base: 3GB, range: 1GB, type UC total RAM covered: 16384M Found optimal setting for mtrr clean up gran_size: 64K chunk_size: 64K num_reg: 5 lose cover RAM: 0G New variable MTRRs reg 0, base: 0GB, range: 2GB, type WB reg 1, base: 2GB, range: 1GB, type WB reg 2, base: 4GB, range: 4GB, type WB reg 3, base: 8GB, range: 8GB, type WB reg 4, base: 16GB, range: 1GB, type WB e820 update range: 00000000c00000...

...ase: 0GB, range: 32GB, type WB reg 1, base: 32GB, range: 1GB, type WB reg 2, base: 3000MB, range: 8MB, type UC reg 3, base: 3008MB, range: 64MB, type UC reg 4, base: 3GB, range: 1GB, type UC reg 5, base: 33790MB, range: 2MB, type UC total RAM covered: 32694M Found optimal setting for mtrr clean up gran_size: 64K chunk_size: 128M num_reg: 9 lose cover RAM: 0G New variable MTRRs reg 0, base: 0GB, range: 2GB, type WB reg 1, base: 2GB, range: 1GB, type WB reg 2, base: 3000MB, range: 8MB, type UC reg 3, base: 3008MB, range: 64MB, type UC reg 4, base: 4GB, range: 4GB, type WB reg 5, bas...

https://bugs.freedesktop.org/show_bug.cgi?id=109681 Bug ID: 109681 Summary: Nvidia GT710 => nouveau + wayland + swayWM => crash when use acceleration (open Firefox) Product: Mesa Version: 18.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz <marcin.slusarz at gmail.com> wrote: > [ 326.168487] ====================================================== > [ 326.168491] [ INFO: possible circular locking dependency detected ] > [ 326.168496] 3.13.6 #1270 Not tainted > [ 326.168500] ------------------------------------------------------- > [ 326.168504] ldconfig/22297 is

...: 0GB, range: 2GB, type WB [ 0.000000] reg 1, base: 2GB, range: 1GB, type WB [ 0.000000] reg 2, base: 4GB, range: 1GB, type WB [ 0.000000] reg 3, base: 3071MB, range: 1MB, type UC [ 0.000000] total RAM covered: 4095M [ 0.000000] Found optimal setting for mtrr clean up [ 0.000000] gran_size: 64K chunk_size: 2M num_reg: 4 lose cover RAM: 0G [ 0.000000] New variable MTRRs [ 0.000000] reg 0, base: 0GB, range: 2GB, type WB [ 0.000000] reg 1, base: 2GB, range: 1GB, type WB [ 0.000000] reg 2, base: 3071MB, range: 1MB, type UC [ 0.000000] reg 3, base: 4GB, range:...

...ange: 256MB, type UC [ 0.000000] reg 4, base: 3320MB, range: 8MB, type UC [ 0.000000] reg 5, base: 8696MB, range: 8MB, type UC [ 0.000000] reg 6, base: 8694MB, range: 2MB, type UC [ 0.000000] total RAM covered: 7918M [ 0.000000] Found optimal setting for mtrr clean up [ 0.000000] gran_size: 64K chunk_size: 16M num_reg: 8 lose cover RAM: 0G [ 0.000000] New variable MTRRs [ 0.000000] reg 0, base: 0GB, range: 2GB, type WB [ 0.000000] reg 1, base: 2GB, range: 1GB, type WB [ 0.000000] reg 2, base: 3GB, range: 256MB, type WB [ 0.000000] reg 3, base: 3320MB, range: 8MB,...

...0.002941] 5 base 230000000 mask FF0000000 uncachable [ 0.002942] 6 disabled [ 0.002942] 7 disabled [ 0.003537] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.003690] total RAM covered: 8192M [ 0.004410] Found optimal setting for mtrr clean up [ 0.004412] gran_size: 64K chunk_size: 64K num_reg: 6 lose cover RAM: 0G [ 0.004861] e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved [ 0.004867] last_pfn = 0xcf65f max_arch_pfn = 0x400000000 [ 0.007191] found SMP MP-table at [mem 0x000f22d0-0x000f22df] [ 0.007279] check: Scanning 1 areas...

...0.003936] 5 base 0CFF00000 mask FFFF00000 uncachable [ 0.003937] 6 disabled [ 0.003938] 7 disabled [ 0.004864] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.005025] total RAM covered: 4607M [ 0.005436] Found optimal setting for mtrr clean up [ 0.005438] gran_size: 64K chunk_size: 2M num_reg: 6 lose cover RAM: 0G [ 0.006325] e820: update [mem 0xcff00000-0xffffffff] usable ==> reserved [ 0.006331] last_pfn = 0xcfe90 max_arch_pfn = 0x400000000 [ 0.011041] found SMP MP-table at [mem 0x000f3e50-0x000f3e5f] [ 0.034915] check: Scanning 1 areas...

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001