From owner-freebsd-hackers Tue Aug 4 09:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29537 for freebsd-hackers-outgoing; Tue, 4 Aug 1998 09:03:38 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lariat.lariat.org ([206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29473 for ; Tue, 4 Aug 1998 09:03:17 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id KAA02474; Tue, 4 Aug 1998 10:03:03 -0600 (MDT) Message-Id: <199808041603.KAA02474@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 10:02:41 -0600 To: hackers@FreeBSD.ORG From: Brett Glass Subject: More on the crashes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's some more info on the spontaneous crashes we're seeing under 2.2.7. They seem to happen during times of heavy CPU and memory loads; the crash this morning occurred when we were doing a backup of the entire disk. We do our daily backups by piping the output of dump through gzip -9 and then through FTP to a hard disk on another machine. Just before our OS upgrade we did several such backups for safety; none of them caused a crash. The reboots leave the file system a bit inconsistent. At one point, with a kernel that was built slightly differently, we got error messages saying "malloc(): recursive call" (or something similar). Once, we saw a panic screen that described a virtual memory error; it flashed just before the reboot. Has anyone else seen these? I'm concerned that there might be a VM problem in 2.2.7. (We can't see any signs of flaky hardware.) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message