Re: shutdown -r doesn't execute rc.d sequence
> On Mar 28, 2017, at 14:27, Andrey Chernov wrote: … >> Using rc_debug=yes I see that it is the kernel problem, not rc problem. >> Sometimes rc backward sequence executed even fully, sometimes only >> partly, but in unpredictable moment inside rc sequence the kernel decide >> to reboot quickly (or even deadly hang in rare cases). Always without >> any "Syncing buffers..." leaving FS dirty. No zfs etc. just normal UFS, >> no EFI, no GPT. >> I change GELI swap to normal one, but it does not help. The same >> untouched config works for years, I see this bug for the first time in >> FreeBSD. >> > > I forget to mention that typescript and dmesg does not survive after > this reboot (or rare hang). Good to note. The simple explanation to the problem might be r307755, depending on when you last synced/built ^/head. I have a few more questions (if reverting that doesn't pan out): - What make/model of x86_64 are you running AMD (Bulldozer, etc) or Intel (Conroe/Nehalem/Westmere/Sandybridge/Haswell)? - Is this a custom built machine? If so, what is your motherboard? If not, who’s the vendor? - Is your system firmware up to date? - What does your make.conf/src.conf look like? - Are you running GENERIC or a custom kernel? If custom, could you please include the config somewhere? - Are you loading any drivers in loader.conf? - Are you using Linux emulation? - Are you running any blob drivers, like nvidia? Thanks! -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
Re: shutdown -r doesn't execute rc.d sequence
On 29.03.2017 0:15, Andrey Chernov wrote: > On 28.03.2017 22:33, Ngie Cooper (yaneurabeya) wrote: >> >>> On Mar 28, 2017, at 12:30, Andrey Chernov wrote: >>> >>> With latest -current amd64, reboot happens almost immediately, leaving >>> FS dirty. No proper backward rc.d or /usr/local/etc/rc.d sequence >>> execution is shown. No deactivating GELI swap too. >> >> Hi Andrey, >> Do you have a typescript demonstrating this? Adding rc_debug=yes to >> /etc/rc.conf would be super helpful, along with `boot -v`, to see whether >> the issue is in userspace or rc(5). >> I’ll double check my amd64/i386 VMs too (if possible, redirect the >> output over serial to a typescript for analysis). >> Are you using vanilla FreeBSD, a fork, or a packaged variant (mfsbsd, >> nanobsd, etc)? >> Thanks! >> -Ngie >> > > Using rc_debug=yes I see that it is the kernel problem, not rc problem. > Sometimes rc backward sequence executed even fully, sometimes only > partly, but in unpredictable moment inside rc sequence the kernel decide > to reboot quickly (or even deadly hang in rare cases). Always without > any "Syncing buffers..." leaving FS dirty. No zfs etc. just normal UFS, > no EFI, no GPT. > I change GELI swap to normal one, but it does not help. The same > untouched config works for years, I see this bug for the first time in > FreeBSD. > I forget to mention that typescript and dmesg does not survive after this reboot (or rare hang). signature.asc Description: OpenPGP digital signature
Re: shutdown -r doesn't execute rc.d sequence
On 28.03.2017 22:33, Ngie Cooper (yaneurabeya) wrote: > >> On Mar 28, 2017, at 12:30, Andrey Chernov wrote: >> >> With latest -current amd64, reboot happens almost immediately, leaving >> FS dirty. No proper backward rc.d or /usr/local/etc/rc.d sequence >> execution is shown. No deactivating GELI swap too. > > Hi Andrey, > Do you have a typescript demonstrating this? Adding rc_debug=yes to > /etc/rc.conf would be super helpful, along with `boot -v`, to see whether the > issue is in userspace or rc(5). > I’ll double check my amd64/i386 VMs too (if possible, redirect the > output over serial to a typescript for analysis). > Are you using vanilla FreeBSD, a fork, or a packaged variant (mfsbsd, > nanobsd, etc)? > Thanks! > -Ngie > Using rc_debug=yes I see that it is the kernel problem, not rc problem. Sometimes rc backward sequence executed even fully, sometimes only partly, but in unpredictable moment inside rc sequence the kernel decide to reboot quickly (or even deadly hang in rare cases). Always without any "Syncing buffers..." leaving FS dirty. No zfs etc. just normal UFS, no EFI, no GPT. I change GELI swap to normal one, but it does not help. The same untouched config works for years, I see this bug for the first time in FreeBSD. signature.asc Description: OpenPGP digital signature
Re: shutdown -r doesn't execute rc.d sequence
On Tue, Mar 28, 2017 at 10:38:53PM +0300, Andrey Chernov wrote: > ... > >> With latest -current amd64, reboot happens almost immediately, leaving > >> FS dirty. No proper backward rc.d or /usr/local/etc/rc.d sequence > >> execution is shown. No deactivating GELI swap too. > > > > Hi Andrey, > > Do you have a typescript demonstrating this? Adding rc_debug=yes to > > /etc/rc.conf would be super helpful, along with `boot -v`, to see whether > > the issue is in userspace or rc(5). > > I’ll double check my amd64/i386 VMs too (if possible, redirect the > > output over serial to a typescript for analysis). > > Are you using vanilla FreeBSD, a fork, or a packaged variant (mfsbsd, > > nanobsd, etc)? > > Thanks! > > -Ngie > > I don't have serial, so typescript may not work treating as dirty, but > I'll try. As I say, it is today's -current, vanilla. It looks like > regression because few weeks ago all things works. > FWIW, I did not see an issue either for my build machine of my laptop at r316082: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #298 r316082M/316093:1200027: Tue Mar 28 06:37:15 PDT 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 Peace, david -- David H. Wolfskill da...@catwhisker.org Who would have thought that a "hotelier" would be so ... unwelcoming? Sad. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: shutdown -r doesn't execute rc.d sequence
On 28.03.2017 22:33, Ngie Cooper (yaneurabeya) wrote: > >> On Mar 28, 2017, at 12:30, Andrey Chernov wrote: >> >> With latest -current amd64, reboot happens almost immediately, leaving >> FS dirty. No proper backward rc.d or /usr/local/etc/rc.d sequence >> execution is shown. No deactivating GELI swap too. > > Hi Andrey, > Do you have a typescript demonstrating this? Adding rc_debug=yes to > /etc/rc.conf would be super helpful, along with `boot -v`, to see whether the > issue is in userspace or rc(5). > I’ll double check my amd64/i386 VMs too (if possible, redirect the > output over serial to a typescript for analysis). > Are you using vanilla FreeBSD, a fork, or a packaged variant (mfsbsd, > nanobsd, etc)? > Thanks! > -Ngie I don't have serial, so typescript may not work treating as dirty, but I'll try. As I say, it is today's -current, vanilla. It looks like regression because few weeks ago all things works. signature.asc Description: OpenPGP digital signature
Re: shutdown -r doesn't execute rc.d sequence
> On Mar 28, 2017, at 12:30, Andrey Chernov wrote: > > With latest -current amd64, reboot happens almost immediately, leaving > FS dirty. No proper backward rc.d or /usr/local/etc/rc.d sequence > execution is shown. No deactivating GELI swap too. Hi Andrey, Do you have a typescript demonstrating this? Adding rc_debug=yes to /etc/rc.conf would be super helpful, along with `boot -v`, to see whether the issue is in userspace or rc(5). I’ll double check my amd64/i386 VMs too (if possible, redirect the output over serial to a typescript for analysis). Are you using vanilla FreeBSD, a fork, or a packaged variant (mfsbsd, nanobsd, etc)? Thanks! -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
