Have you been able to reproduce this on other shutdowns? This just looks like a normal watchdog (NIC) timeout that got mixed in with shutdown. --Peter Mike Jakubik wrote: >On Sun, August 7, 2005 9:05 pm, jason henson said: > > >>Mike Jakubik wrote: >> >> >> >>>FreeBSD 7.0-CURRENT #0: Fri Jul 29 22:26:55 EDT 2005 >>> >>> >>># shutdown -p now >>>... >>>Stopping cron. >>>Shutting down local daemons:. >>>Stopping named. >>>Waiting for PIDS: 39130 second watchdog timeout expired. Shutdown >>>terminated. Sun Aug 7 15:32:10 EDT 2005 >>>Aug 7 15:32:10 fbsd init: /bin/sh on /etc/rc.shutdown terminated >>>abnormally, going to single user mode Aug 7 15:32:10 fbsd syslogd: >>>exiting on signal 15 pflog0: promiscuous mode disabled >>>Waiting (max 60 seconds) for system process `vnlru' to stop...done >>>Waiting (max 60 seconds) for system process `bufdaemon' to stop...done >>>Waiting (max 60 seconds) for system process `syncer' to stop... >>>Syncing disks, vnodes remaining...1 1 1 0 0 0 done >>>All buffers synced. >>>unmount of /dev failed (BUSY) Uptime: 6d15h13m2s >>>Powering system off using ACPI >>> >>> >>> >>> >>I just got the /dev failed message on the snap shot of 6 from July02. I >>installed it a few days ago. >> >> > >Thats not what i was referring to, that is a known issue. The watchdog >timeout, etc, is what i was trying to point out. > > >_______________________________________________ >freebsd-current_at_freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > > >Received on Mon Aug 08 2005 - 02:11:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:40 UTC