From owner-freebsd-hackers Fri Oct 12 11:50:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9DD6E37B405 for ; Fri, 12 Oct 2001 11:50:17 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id f9CIoGG29403 for ; Fri, 12 Oct 2001 14:50:16 -0400 (EDT) Date: Fri, 12 Oct 2001 14:50:15 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: Page fault and bad memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am writing a program that stresses memory a lot. The program accepts a parameter to indicate how long it runs. For several big values, the program runs OK. But when I give a even bigger one, the system panics at generic_bcopy(). I am wondering whether this has something to do with bad memory chip or some other hardware problem. I do not believe that the program logic will change when given a bigger input. Although I am still studying the code, the chances of a software bug is small. How can I tell if this is due to bad memory? The system is running 4.3-Release and the program runs for about 2 hours. It is a kernel module doing a lot of I/O. Thanks for you advice. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message