Date: Mon, 06 Jan 2003 08:16:48 -0800 From: Peter Wemm <peter@wemm.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 23251 for review Message-ID: <20030106161648.52ACD2A89E@canning.wemm.org> In-Reply-To: <20030106082032.GF2184@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote: > On Sun, Jan 05, 2003 at 11:50:47PM -0800, Peter Wemm wrote: > > > > I'm really puzzled as to why mpt_shutdown has an effect. Adding some > > printfs has shown me that it completes and gets past it. As far as sc0 > > shutdown actually. > > I once did a "shutdown -p", walked away and when I returned hours > later I found the machine powered off. Something must have kicked > in eventually. Boredom maybe :-) > > Anyway: it doesn't look like a hard lock, so multiple invocations > of the same shutdown handler with a lot of timeouts seems like a > possible explanation. Doesn't sound ia64 specific either... Thinking more about it.. I did notice timeout messages from the mpt driver if I left it long enough. I guess da gave up eventually. Anyway, moving the dashutdown calls to before the device tree is shot down solved the problem. It now cleanly reboots with mpt and acpica. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-projects" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030106161648.52ACD2A89E>