From owner-freebsd-stable@FreeBSD.ORG Thu Oct 5 05:17:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28E1C16A403 for ; Thu, 5 Oct 2006 05:17:00 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6C5D43D45 for ; Thu, 5 Oct 2006 05:16:59 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 04 Oct 2006 22:14:04 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id k955GxBw074362; Wed, 4 Oct 2006 22:16:59 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id k955Gw8b074361; Wed, 4 Oct 2006 22:16:58 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200610050516.k955Gw8b074361@ambrisko.com> In-Reply-To: <20061004192833.GK4945@poupinou.org> To: Bruno Ducrot Date: Wed, 4 Oct 2006 22:16:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: stable@freebsd.org, Bill Moran Subject: Re: Dell 1950 does not properly respond to reboot and shutdown -p X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 05:17:00 -0000 Bruno Ducrot writes: | On Wed, Oct 04, 2006 at 02:07:12PM -0400, Bill Moran wrote: | > In response to Bruno Ducrot : | > > Hi, | > > | > > On Wed, Oct 04, 2006 at 12:28:35PM -0400, Bill Moran wrote: | > > > | > > > A reboot causes the OS to halt, but the hardware just sits there on the | > > > shutdown screen. | > > > | > > > A shutdown -p does the same. | > > | > > What exactly are the last few lines? | > | > (manually copied) | > | > ... | > All buffers synced. | > Uptime: 1m16s | > | | Thanks. Then this happen after print_uptime(). | | I believe one of the drivers register a shutdown_final (or | shutdown_post_sync) event that hang your system. I think (though I | may be wrong) mfi may be that one. | | It would help if you can add some printf in dev/mfi/mfi.c into the | mfi_shutdown() function in order to check if that assumption | is correct. Some what related to this we have a local hack: --- sys/kern/subr_bus.c.orig Tue Jun 27 15:49:39 2006 +++ sys/kern/subr_bus.c Tue Jun 27 15:49:51 2006 @@ -2906,6 +2906,7 @@ bus_generic_shutdown(device_t dev) device_t child; TAILQ_FOREACH(child, &dev->children, link) { + DELAY(1000); device_shutdown(child); } Seems like we were tearing things done to fast and resources stolen away from HW that was totally shutdown yet or something. I think this was worse when things had shared interrupts but I forget the exact details. It's been a lot time when I put in the hack and moved onto the next fire. It seems the more HW we had in the machine the worse the problem was. This is just a hack and not a fix. Doug A.