Date: Sun, 13 Apr 2014 10:02:19 +0200 From: Alban Hertroys <haramrae@gmail.com> To: Doug Hardie <bc979@lafn.org> Cc: "dteske@FreeBSD.org Teske" <dteske@FreeBSD.org>, freebsd-stable <freebsd-stable@freebsd.org>, Chris H <bsd-lists@bsdforge.com> Subject: Re: 9.2 Boot Problem Message-ID: <12D44EED-29C6-4EC2-90CE-59A8246CEB57@gmail.com> In-Reply-To: <1D50A38D-8919-4034-A4E5-EEF8E78E638D@lafn.org> References: <175D3755-BB9B-4EAD-BDAD-06E9670E06AB@lafn.org> <186472F9-A97B-4863-81BC-67BE788D5E9A@lafn.org> <a865b8f2ccb9ad4918544bad3d49554d.authenticated@ultimatedns.net> <791C8200-023A-4ACB-9B6F-F5A8B0E170F4@lafn.org> <5bfb4fb619954c3dfbd3499aafa98917.authenticated@ultimatedns.net> <4F983E6A-0A7D-403C-AFAA-9CCCCB05716F@lafn.org> <feeca307c8da9ca3b385cf47d75904a7.authenticated@ultimatedns.net> <0f3f01cf5439$13cf8570$3b6e9050$@FreeBSD.org> <981CAA9F-1E67-4E56-A119-BA6D1D29F383@lafn.org> <89290759-E5C2-4991-B644-A82648BEDD52@lafn.org> <1D50A38D-8919-4034-A4E5-EEF8E78E638D@lafn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Apr 2014, at 4:07, Doug Hardie <bc979@lafn.org> wrote: > After much digging, I now know what it going on, but not why. When = getkey is called the first time, menu_timeout_enable is set to one. = However, it is set to zero on every check after that. In getkey after = the comment "Was a key pressed" is a check of key to see if a key was = pressed. It is returning a decimal 7 (BEL). That then clears = menu_timeout_enable and it then sits there waiting for a valid key = input. There is no keyboard plugged into the system. I have no idea = how that BEL is being generated or even how to prevent it. Could it be = possible that it comes from the serial console? I tend to doubt thats = the case since the system hangs during boot when the serial console is = not connected. I suppose that I could put in a test for a key value = that is not a control character, but that would only work until the next = system update. I'd have to remember to put it back in each time. Thats = not likely to happen. My memory is not that good. Whats interesting is = that I have 4 systems (i386) doing this and 1 system (i386) and 2 = systems (amd64) not doing it. The only common thread is the 4 systems = doing it are about 100 miles from me and the working ones are here. I=92m hardly an expert on serial console matters, but reading the above = it seems to me that on the problematic systems you have the serial = console connected to some other remote machine(s) - at least, I doubt = you are using a 100 mile long serial cable. Since the problematic systems all receive a BEL signal and the ones = local to you don=92t, the problem may not be at the receiving end but at = the sending end. Is there a difference between the sending part of the = setup between the systems that do receive that BEL signal and those that = don=92t? Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll find there is no forest.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12D44EED-29C6-4EC2-90CE-59A8246CEB57>