https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195458
--- Comment #50 from Glen Barber <[email protected]> --- (In reply to Andrew Smith from comment #10) > It seems that this at last effects all Kernels since 10.1-RELEASE through p3. > > If you have one of these Kernels with Softupdates active on the root > filesystem and you replace /sbin/init then you get this behaviour. > > If you either disable file system softupdates on the filesystem or you > disable the softupdates option in a new Kernel build then the issue does not > exist. > > I suspect people that haven't had this issue have some other environmental > difference that nobody has highlighted yet. > > The issue of course hits 10.0-RELEASE to 10.1-RELEASE upgrades since when > freebsd-update install is run, the first thing done is to replace the Kernel > and ask for a reboot then run freebsd-update again. The Kernel exhibiting > the problem is then in place. > > Could this be related to the changes made to ufs for the per FFS-Filesystem > threading around August? (r269457, r269533, r269583). I built and installed GENERIC with these commit reverted (releng/10.1@r270157), and still see this behavior after freebsd-update(8) installs the userland updates, so I'm inclined to think these are not the cause. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
