From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 15:36:30 2004 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 E309316A4ED; Tue, 17 Aug 2004 15:36:30 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79D7943D48; Tue, 17 Aug 2004 15:36:29 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from dual (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with SMTP id i7HFaREg063026; Tue, 17 Aug 2004 17:36:27 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <083a01c4846f$f6271810$471b3dd4@digiware.nl> From: "Willem Jan Withagen" To: "Greg 'groggy' Lehey" , "Radek Kozlowski" References: <20040812215859.GM19643@wantadilla.lemis.com><20040812230741.GC10869@werd> <20040817013525.GF81257@wantadilla.lemis.com> Date: Tue, 17 Aug 2004 17:36:27 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: FreeBSD current users Subject: Re: Current method of dumping a processor? 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, 17 Aug 2004 15:36:31 -0000 From: "Greg 'groggy' Lehey" To: "Radek Kozlowski" > On Friday, 13 August 2004 at 1:07:41 +0200, Radek Kozlowski wrote: > > On Fri, Aug 13, 2004 at 07:28:59AM +0930, Greg 'groggy' Lehey wrote: > >> I've tried it on kernels built in January, May and yesterday. In each > >> case, I did: > >> > >> dumpon /dev/ad0s2b > >> > >> (for appropriate values of ad0s2b). All kernels include ddb. I > >> entered the debugger with ctrl-alt-esc and entered "panic". The > >> kernel from January dumps just fine. The kernels from May and August > >> hang. > >> > >> Am I doing something wrong? Has something else changed? Does anybody > >> else have this problem? > > > > I also had this problem back in June when I was trying to get a crash > > dump, but nobody replied (see > > http://lists.freebsd.org/pipermail/freebsd-current/2004-June/029434.html). > > I then learnt that I can use call doadump in ddb and have been using > > that since then. > > Thanks. Yes, this seems to work. Are we agreed that it's a bug that > the 'panic' command just hangs? This was a problem on amd64 with large amounts of memory due to 32bit overflow until I fixed it in a very crude way (after good suggestions where to look) and after a short while it got really fixed in an upper layer by someone who knew what he was doing. But that was when even 'call doadump' did not even work. So if call doadump does work for you big chance it is in the boot() code before it calls doadump. Since that is more or less what panic calls. Since then I've not seen kernels where this problem returned. BTW I'm running amd64 with dual processor. --WjW