search for: prime95

...irst repeat the test setup: Use Xen 4.1.1 and kernel 2.6.32.36 (commit ae333e9). Configure 2 HVMs called VM1 and VM2 as follows (per HVM): 2 VCPUs, 2 virtual disks, 1024 MB RAM, viridian=1 Install Windows 2008 R2 SP1, do install everything twice - never clone. Install GPLPV, iometer 2006.07.27, prime95 26.6 x64, ActiveState Perl 5.12.4 x64, wget for Windows and the attached perl script. Run iometer with 2 workers on the same but separate second virtual disk, queue depth 4 per worker, access specification "All in one". Run prime95 torture test with "In-place large FFTs". On...

..."Page Fault While In Kernel Mode". My main test was the usual 'make buildworld'. I became worried about the quality of the memory sticks. Therefore, I ran several forms of tests/benchmarks. memtest86 (http://www.memtest86.com/) worked right after running all tests for 16 hours. prime95 (http://www.mersenne.org/) crunch test which used about 900Mb of memory worked fine under Windows after 8 hours or so. Then, I ran Sisandra 2003 burn-in test for about 4 hours. Finally, I ran DocMemory 2.0 for 6 hours. All of them worked without any glitches. No problems were found with the system....

Hi there guys! I want to set up Puppy-Linux to run off a 2GB USB key-drive in native mode (I.e. not as a virtual machine, which I'm finding runs too slow on my system, under XP.) To test it out, I want to run off a 150GB USB HDD. Now this drive is NTFS formatted and way bigger than the 1GB file structure limit that I read about in the Syslinux documentation. There's only one

...rivileged domain. No difference. My setup: - Hardware: Nforce2 motherboard, 2GB ram, 1.8GHz Athlon XP, Hauppauge PVR-150 - Xen: 3.0.2 - Kernel: 2.6.16-xen - ivtv: 0.6.6 What I''ve tried so far: 1. Verified that this is not a hardware problem (I''ve done stability testing, prime95, memtest86, etc. The system works perfectly and the IVTV device is rock-solid on a non-Xen Linux 2.6.16 kernel.) 2. Moved the encoder (IVTV) to its own IRQ 3. Set PCI latency timers to reasonable values for all devices (e.g. 128) 4. Verified that there are *no* errors in dmesg, xm dmesg, syslogs...