From owner-freebsd-current Wed Jul 15 06:47:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19325 for freebsd-current-outgoing; Wed, 15 Jul 1998 06:47:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19316 for ; Wed, 15 Jul 1998 06:47:38 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id JAA00375 for ; Wed, 15 Jul 1998 09:47:44 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 09:47:43 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: repeatable crash with softupdates Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently enabled softupdates on every filesystem but root. i can cause a crash by running the x11 version of cvsup to download the source tree. this happens just about every time. i enabled crashdumps to my swap device and ran savecore, but my limited cluefullness hasn't figured me out a way to actually examine what happened, all i saw was that the kernel had panic'd from a page fault. the kernel i'm running is from ~noon yesterday. what can i do to provide more info about this to the developers? what information would be useful? (i didn't want to just randomly attach my config file, dmesg and whatnot without asking first) also, it seems i have had a bunch of crashes before the softupdates went into my kernel but these were few and far between ( well every 3-6 days ) although it might been the punks at the office rebooting me for other stuff. :) these new crashes are produceable right after a reboot though. thank you, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message