Displaying 7 results from an estimated 7 matches for "3072mb".
Did you mean:
3072m
2013 Jul 01
0
[Fwd: Re: XEN 4.2.2: Windows 2008 R2 server HVM does not start when attempting to use more than 3072MB of RAM]
> On Mon, Jul 01, 2013 at 12:12:31AM +0300, NiX wrote:
>> System:
>>
>> CPU''s: 2 x XEON X5450
>> Motherboard:
>> http://www.intel.com/p/en_US/support/highlights/server/s5000psl/
>> RAM: 16GB DDR2 ECC
>> OS: Debian 7.0 64bit
>>
>> If I attempt to use more than 3GB of RAM to the guest below (Windows
>> 2008
>> server R2
2018 Sep 04
2
[PATCH] PCI: add prefetch quirk to work around Asus/Nvidia suspend issues
...that. It may not be
> related at all but it could be worth a try to dump out MTRR registers of
> one of the affected systems and see if the memory areas are listed there
> (and if the attributes are somehow wrong if found).
>From Asus X542UQ:
# cat /proc/mtrr
reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable
reg02: base=0x090000000 ( 2304MB), size= 256MB, count=1: uncachable
reg03: base=0x08c000000 ( 2240MB), size= 64MB, count=1: uncachable
reg04: base=0x08b800000 ( 2232MB), size= 8MB, count=1...
2018 Sep 04
1
[PATCH] PCI: add prefetch quirk to work around Asus/Nvidia suspend issues
On Tue, Sep 4, 2018 at 2:43 PM, Mika Westerberg
<mika.westerberg at linux.intel.com> wrote:
> Yes, can you check if the failing device BAR is included in any of the
> above entries? If not then it is probably not related.
mtrr again for reference:
reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable
reg02: base=0x090000000 ( 2304MB), size= 256MB, count=1: uncachable
reg03: base=0x08c000000 ( 2240MB), size= 64MB, count=1: uncachable
reg04: base=0x08b800000 ( 2232MB), size= 8MB, count=1...
2013 Jun 30
3
XEN 4.2.2: Windows 2008 R2 server HVM does not start when attempting to use more than 3072MB of RAM
System:
CPU''s: 2 x XEON X5450
Motherboard: http://www.intel.com/p/en_US/support/highlights/server/s5000psl/
RAM: 16GB DDR2 ECC
OS: Debian 7.0 64bit
If I attempt to use more than 3GB of RAM to the guest below (Windows 2008
server R2 64bit) it will end up with the following error message:
xl create win_2008_server_hvm.cfg
Parsing config from win_2008_server_hvm.cfg
xc: info: VIRTUAL
2018 Sep 04
0
[PATCH] PCI: add prefetch quirk to work around Asus/Nvidia suspend issues
On Tue, Sep 04, 2018 at 09:52:02AM +0800, Daniel Drake wrote:
> # cat /proc/mtrr
> reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
> reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable
> reg02: base=0x090000000 ( 2304MB), size= 256MB, count=1: uncachable
> reg03: base=0x08c000000 ( 2240MB), size= 64MB, count=1: uncachable
> reg04: base=0x08b800000 ( 2232MB), s...
2018 Sep 03
2
[PATCH] PCI: add prefetch quirk to work around Asus/Nvidia suspend issues
On Sat, Sep 1, 2018 at 3:12 AM, Bjorn Helgaas <helgaas at kernel.org> wrote:
> If true, this sounds like some sort of erratum, so it would be good to
> get some input from Intel, and I cc'd a few Intel folks.
Yes, it would be great to get their input.
> It's interesting that all the systems below are from Asus. That makes
> me think there's some BIOS or SMM
2012 Apr 12
1
6.2 x86_64 "mtrr_cleanup: can not find optimal value"
...:41 ns2 kernel: gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: 0G
/proc/mtrr (bios memory remap disabled)
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg02: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-back
reg03: base=0x0cf700000 ( 3319MB), size= 1MB, count=1: uncachable
reg04: base=0x0cf800000 ( 3320MB), size= 8MB, count=1: uncachable
reg05: base=0x100000000 ( 4096MB), size= 4096MB, count=1: write-back
reg06: base=0x0d0000000 ( 3328MB), size= 256MB, cou...