Date: Thu, 30 Mar 2017 20:14:23 +0300 From: Andrey Chernov <ache@freebsd.org> To: Bruce Evans <brde@optusnet.com.au> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, avg@FreeBSD.org, bde@FreeBSD.org, current@FreeBSD.org Subject: Re: New syscons bugs: shutdown -r doesn't execute rc.d sequence and others Message-ID: <e1830cff-58af-f0b1-bab9-935ba32883f4@freebsd.org> In-Reply-To: <20170331015718.X3330@besplex.bde.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> <e4b3dd02-6dd2-0723-eed1-a3fd0be5b651@freebsd.org> <20170331015718.X3330@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30.03.2017 18:13, Bruce Evans wrote: > On Thu, 30 Mar 2017, Andrey Chernov 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. >> >> Finally I have good news and bad news with today's -current: >> >> 1) It seems your latest commit r316136 fix premature reboot issue. > > Now I need to know how that helped. Do you used a non-default mode? Perhaps it isn't really helped, but just hide the problem, changing some another race time parameters. I use 80x30 text mode on all screens. >> 2) I still can't enter KDB using Ctrl-Alt-ESC, while booting, after >> booting, after login and while shutdown - nothing happens. >> boot -d enters KDB normally, but the keyboard sequence handler is >> broken, not boot -d. > > Try "<newline>~b". What? It just prints \n, new csh prompt and ~b > It is an old bug that Ctrl-Alt-ESC (and Ctrl-PrtScr) Ctrl-PrtScr does nothing too. > But I think the misconfiguration is the > same for vt. No, Ctrl-Alt-ESC works for vt at every phase of the system lifecycle. I use Russian keymap for syscons, but Ctrl, Alt, ESC of course are not remapped. I surely remember it works for syscons long time ago. Just to not forget it, I use PS/2 keyboard and have no vt* lines in the kernel config.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e1830cff-58af-f0b1-bab9-935ba32883f4>