From owner-freebsd-current Fri Feb 14 12:40:48 2003 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 5C88937B401 for ; Fri, 14 Feb 2003 12:40:47 -0800 (PST) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E54F43FB1 for ; Fri, 14 Feb 2003 12:40:46 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.12.7/8.12.7) with ESMTP id h1EKei71017058; Fri, 14 Feb 2003 15:40:45 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20030214110403.GF93252@elvis.mu.org> References: <20030214103808.GE93252@elvis.mu.org> <20030214110403.GF93252@elvis.mu.org> Date: Fri, 14 Feb 2003 15:40:43 -0500 To: Alfred Perlstein , Dag-Erling Smorgrav From: Garance A Drosihn Subject: Re: fix: lock order reversal proc/filedesc. Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-RPI-Spam-Score: -3 () IN_REP_TO,ORDER_STATUS,QUOTED_EMAIL_TEXT,REFERENCES,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01 X-Scanned-By: MIMEDefang 2.28 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 3:04 AM -0800 2/14/03, Alfred Perlstein wrote: >* Dag-Erling Smorgrav [030214 02:52] wrote: >> Alfred Perlstein writes: > > > Thanks to Paul Saab's work on fixing twe(4) I was able to > > > get a crash dump from my box > > > > How? I can't get a crash dump in -CURRENT, even on a plain > > jane ata disk, and it's been months since I last managed to > > get one. > >I dunno, it just works for me. Get a twe? :) > >What exactly is broken about dumps for you on ata? It's upsetting >to hear this, don't people realize that this is a VERY important >feature for allowing people to get things done in FreeBSD? When I was getting a panic on current a few weeks ago, I tried several times to generate a dump, and never got one. In my bug reports here, I mentioned that I couldn't get a panic, but since no one replied to that I assumed it must have been something I was doing wrong, or it was directly related to the same problem which was causing the panic. (the bug seemed to be something in softupdates, so it was plausible to me that maybe the disk had been put into a weird state by the bug). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message