From owner-freebsd-stable Wed Mar 29 10:26:34 2000 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id DDAD237C153 for ; Wed, 29 Mar 2000 10:25:22 -0800 (PST) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.9.3/8.8.8) with ESMTP id KAA25639; Wed, 29 Mar 2000 10:25:18 -0800 (PST) Message-Id: <200003291825.KAA25639@ptavv.es.net> To: nino@inode.at Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4-RELEASE; panic while paging In-reply-to: Your message of "Wed, 29 Mar 2000 17:50:18 +0200." <20000329175018.V15889@TK147108.telekabel.at> Date: Wed, 29 Mar 2000 10:25:17 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marinos, In my experience with these things, such errors are almost invariably hardware problems. In the case you are seeing, I'd bet on a memory problem. The VM system in FreeBSD can really pound memory and bring out bugs. If you have more than one memory board, try moving them around and see if the errors change. Try pulling one and then another to see if things clear up when the bad board is pulled. This is how I isolated the same problem with my new K6-3/450. Power supplies can also cause this, but I'd bet on a flaky DIMM. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message