search for: 4095m

Hi guys, Having a weird issue with a Dom0. When we were running 2.6.18.8 kernel the server would lock up every 2 weeks for no reason. Its been a difficult one to resolve as there are no errors. We have now upgraded to 2.6.32.13 and the lock ups are more often. For example today it crashed in the morning, then it was rebooted and it crashed again about 5 hours later, no logs. The

Hi all, This is today''s nightly testing report; no new issue found, bug #1259 got fixed. Some vt-d cases failed in first round testing, but can get pass in retesting. Fixed issue: ============================================== 1. booting windows guest causes Xen HV crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259 Old issues:

...located early at first and then try to initialize iommu, if iommu for intel or AMD could setup properly, swiotlb buffer will be freed. The early allocating is with bootmem, and could panic when we try to use kdump with buffer above 4G only, or with memmap to limit mem under 4G. for example: memmap=4095M$1M to remove memory under 4G. According to Eric, add _nopanic version and no_iotlb_memory to fail map single later if swiotlb is still needed. -v2: don't pass nopanic, and use -ENOMEM return value according to Eric. panic early instead of using swiotlb_full to panic...according to Eric/K...

...located early at first and then try to initialize iommu, if iommu for intel or AMD could setup properly, swiotlb buffer will be freed. The early allocating is with bootmem, and could panic when we try to use kdump with buffer above 4G only, or with memmap to limit mem under 4G. for example: memmap=4095M$1M to remove memory under 4G. According to Eric, add _nopanic version and no_iotlb_memory to fail map single later if swiotlb is still needed. -v2: don't pass nopanic, and use -ENOMEM return value according to Eric. panic early instead of using swiotlb_full to panic...according to Eric/K...

...10600070106 [ 0.000000] original 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: 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]...