Date: Wed, 4 Oct 2006 22:16:58 -0700 (PDT) From: Doug Ambrisko <ambrisko@ambrisko.com> To: Bruno Ducrot <ducrot@poupinou.org> Cc: stable@freebsd.org, Bill Moran <wmoran@collaborativefusion.com> Subject: Re: Dell 1950 does not properly respond to reboot and shutdown -p Message-ID: <200610050516.k955Gw8b074361@ambrisko.com> In-Reply-To: <20061004192833.GK4945@poupinou.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruno Ducrot writes:
| On Wed, Oct 04, 2006 at 02:07:12PM -0400, Bill Moran wrote:
| > In response to Bruno Ducrot <ducrot@poupinou.org>:
| > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610050516.k955Gw8b074361>