From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 15:51:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E07BF16A4BF for ; Tue, 26 Aug 2003 15:51:38 -0700 (PDT) Received: from mail.speakeasy.net (mail10.speakeasy.net [216.254.0.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B6FF43FDD for ; Tue, 26 Aug 2003 15:51:38 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 31149 invoked from network); 26 Aug 2003 22:51:34 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 26 Aug 2003 22:51:34 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h7QMpA9s025862; Tue, 26 Aug 2003 18:51:11 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20030826182524.M499@gravy.homeunix.net> Date: Tue, 26 Aug 2003 18:51:34 -0400 (EDT) From: John Baldwin To: Bryan Liesner cc: freebsd-current@freebsd.org Subject: RE: Question: should I even bother? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2003 22:51:39 -0000 On 26-Aug-2003 Bryan Liesner wrote: > > > Over the past few weeks, I have posted messages about panics > that I've been having. No answers at all. > > Yesterday, I posted about a repeatable problem where dumps just > destroy my IDE drive. No answers. Pretty serious problem. No, my > swap partition doesn't start at sector 0. > > Have I offended some or all of you somehow? I'd like to contribute in > some way... No, I doubt you've offended anyone. However, most people working on FreeBSD have a steady state of being really busy and unfortunately some bug reports don't always get followed up on. Including stack traces with panic reports can greatly aid in getting the panics resolved. Note that the panic in specfs that a lot of folks were seeing has been recently fixed and I saw many unanswered reports of that panic as reports were coming in well after the problem had been identified and even fixed. The ata(4) driver was just rewritten and is a bit rocky apparently. I haven't dared to upgrade to it yet, so if it's trashing your disks you might want to keep an old kernel around to get work done with. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/