From owner-freebsd-questions Tue Nov 9 3:36:20 1999 Delivered-To: freebsd-questions@freebsd.org Received: from europa.salford.ac.uk (europa.salford.ac.uk [146.87.3.2]) by hub.freebsd.org (Postfix) with SMTP id D08F114D4A for ; Tue, 9 Nov 1999 03:36:16 -0800 (PST) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 21015 invoked by alias); 9 Nov 1999 11:36:13 -0000 Received: (qmail 20251 invoked from network); 9 Nov 1999 11:35:00 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by europa.salford.ac.uk with SMTP; 9 Nov 1999 11:35:00 -0000 Received: (qmail 20632 invoked by uid 141); 9 Nov 1999 11:34:59 -0000 Date: Tue, 9 Nov 1999 11:34:59 +0000 (GMT) From: Mark Powell X-Sender: mark@localhost To: freebsd-questions@freebsd.org Subject: Stress testing a machine with "make world" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We all know "make world" is a good acid test of whether a machine has decent motherboard, RAM and disk subsystem. However, how far does one go? And what is a good stress test of a machine with lots of RAM? I've had a machine forced upon me, which is based on a Micro-Star 6119 motherboard. Never heard of them before, so I decided to test it out. Handles a 3.3R "make world" fine, but will panic the kernel on a "make -j60 world". ----- IdlePTD 2711552 initial pcb at 2310b8 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x29a fault code = supervisor read, page not present instruction pointer = 0x8:0xc0174bef stack pointer = 0x10:0xc78b5f30 frame pointer = 0x10:0xc7be8174 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (pagedaemon) interrupt mask = trap number = 12 panic: page fault syncing disks... 133 133 133 119 93 45 7 1 done .... --- #0 boot (howto=Cannot access memory at address 0x20. ) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); --- These sort of errors are bad hardware? This always happens when the machine has 128MB of RAM. If the RAM is increased to 256MB, I can't get the "make world" to fail, even putting the number of concurrent jobs up into the hundreds. I presume this is due to it swapping less and not encountering the problems with the hardware? How can one test such a machine without resorting to a "make -j100 world" on each and even DIMM in turn? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message