From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 02:00:16 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 11CF316A4CE for ; Wed, 27 Oct 2004 02:00:16 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D72843D2F for ; Wed, 27 Oct 2004 02:00:15 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i9R20DHv010457; Tue, 26 Oct 2004 22:00:15 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Tue, 26 Oct 2004 22:00:12 -0400 To: "David Boyd" , From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Panic on shutdown -r now 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: Wed, 27 Oct 2004 02:00:16 -0000 At 7:53 PM -0400 10/25/04, David Boyd wrote: >I am resubmitting this (see 10/7/2004) because it persists >in 5.3-RELEASE. > >System is very recent (last night) cvsup of RELENG_5. > >Motherboard is Intel D865PERL. > >The system is setup to collect a dump after a panic, but none is >ever found. Also, the corrupted output after "Shutting down ACPI" >is about as good as it gets... sometimes the console (vga or >serial) displays just one or two "random" letters (usually an "s"). Earlier this year, I had seen similar garbage output on some of my systems at shutdown. I don't remember the details, except that I was not getting any panics, and that the garbage went away at some point. Are you sure the system is set up correctly for collecting coredumps? When you are using a serial console, can you do a serial-break, and force a coredump? (just type in "call doadump()"). See if that gives you a core dump after you reboot. The contents won't be important, but it would tell you if coredumps themselves are working. The main reason I ask is that I thought coredumps were not working for me either, but it turned out that I had forgotten to add options KDB, DDB, and BREAK_TO_DEBUGGER in my kernel config. Once I added them, coredumps worked fine for me. (but then, this is on a single CPU system, and I notice you have multiple CPU's) >It doesn't appear that disabling ACPI has any effect on this >problem. When you disable ACPI, then when does the garbage output occur? I assume you do *not* see the "Shutting down ACPI" message when you have ACPI turned off. >Shutdown -p now always performs a power off. > >The system is temporarily a spare, so I can do anything that you >think may help. In your kernel config, do you have hyperthreading (HTT) turned on? (I notice your CPU's support it) I do not know enough about kernel debugging to be of any help, but those are a few questions which came to mind. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu