Date: Thu, 30 Mar 2017 16:26:08 +0300 From: Andrey Chernov <ache@freebsd.org> To: Andriy Gapon <avg@FreeBSD.org>, Bruce Evans <brde@optusnet.com.au> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, bde@FreeBSD.org, current@FreeBSD.org Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others Message-ID: <365b1846-ee24-00f5-9498-63b3a290483a@freebsd.org> In-Reply-To: <f2e5e8c4-f380-01d0-e87e-c401894de4d9@FreeBSD.org> References: <7d5bbbf0-6908-185c-2ee0-29e0a4f60591@freebsd.org> <D9EAB41D-CE19-4225-8868-F4AFE461F903@gmail.com> <5587c798-d36c-9074-1060-30e206db5571@freebsd.org> <69af07a7-ec8f-9b7f-8b93-9ba148f30fec@freebsd.org> <8C24D1BA-1607-4C19-BA38-39256E82C7AF@gmail.com> <51045bee-a626-efb3-4b1e-0c3d36abb1ab@freebsd.org> <20170329132927.U882@besplex.bde.org> <f35b6ae1-c668-0649-e327-f57811b1d71a@freebsd.org> <20170330150449.R1061@besplex.bde.org> <3534bbeb-9f73-4e37-8f89-c05dd9f89f8c@freebsd.org> <20170330183716.W1655@besplex.bde.org> <4085b441-74ee-796f-adc0-713dfc198b03@freebsd.org> <1772f54a-4268-577a-8e7f-abce929d39c8@freebsd.org> <f2e5e8c4-f380-01d0-e87e-c401894de4d9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30.03.2017 14:23, Andriy Gapon wrote: > On 30/03/2017 12:34, Andrey Chernov wrote: >> On 30.03.2017 12:23, Andrey Chernov wrote: >>> Yes, only for reboot/shutdown. The system does not do anythings wrong >>> even under high load. On reboot or hang those lines are never printed: >>> >>> kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done >>> kernel: Waiting (max 60 seconds) for system process `bufdaemon' to >>> stop...done >>> kernel: Waiting (max 60 seconds) for system process `syncer' to stop... >>> kernel: Syncing disks, vnodes remaining...5 3 0 1 0 0 done >>> kernel: All buffers synced. >>> (it is from 10-stable sample, old -current samples are lost) >>> >>> Moreover, GELI swap deactivation lines are never printed too (I already >>> mention that I change swap to normal, but nothing is changed). >> >> I start to have raw guess that _any_ kernel printf in shutdown mode >> cause not printf but premature reboot. > > This sounds somewhat familiar... > I vaguely recall an opposite issue that happened in the past. After one of my > changes the reboot started hanging for one user. Turned out that the actual bug > was always there, but previously the system rebooted because of a printf that > caused a LOR (between spinlocks, AFAIR), witness tried to report it... using > printf, and that recursed and there was a triple fault in the end. > > Let me try to dig some details, maybe the current issue is related in some ways. > > By chance, do you have WITNESS but not WITNESS_SKIPSPIN in your kernel config? No, I don't have WITNESS* I think removing all vt* lines from the kernel confing (and leaving sc) will be enough to reproduce it, but I am not sure.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?365b1846-ee24-00f5-9498-63b3a290483a>