[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-stable
Subject:    Shutdown/halt operation ordering
From:       Peter Jeremy <peter.jeremy () alcatel ! com ! au>
Date:       2004-02-26 3:00:16
Message-ID: 20040226030016.GT10121 () gsmx07 ! alcatel ! com ! au
[Download RAW message or body]

The low-level shutdown handling (in kern/kern_shutdown.c:boot()) does
things in the following order:
- shutdown_pre_sync events
- sync disks (unless RB_NOSYNC)
- shutdown_post_sync events
- crashdump (if RB_DUMP)
- shutdown_final events (which includes the final halt/reboot/...)

shutdown_post_sync includes invoking the shutdown handler on all
devices.  Can someone please explain why this is invoked before
dumpsys(), rather than after it?  It would seem reasonable to want
to do things like flush disk caches after the crashdump, rather than
before.  Also, this shutdown processing may disturb state information
that is relevant to the problem that made the system panic.

What is the impact of moving 
        EVENTHANDLER_INVOKE(shutdown_post_sync, howto);
to after the dumpsys() call?

-- 
Peter Jeremy
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]