From owner-freebsd-stable@FreeBSD.ORG Sun Apr 13 08:01:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A068157F; Sun, 13 Apr 2014 08:01:51 +0000 (UTC) Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01C1E13E5; Sun, 13 Apr 2014 08:01:50 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id e53so5484859eek.30 for ; Sun, 13 Apr 2014 01:01:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3eiVuY0TBe4VZq0AtRFNaiJlgBMdbeS4ALXi1pX347U=; b=Kqd3wMh894PTOwZyUoyxoq64wHIli0wNpv0Me7qQtZp2l+hvkXpMzj7eEneDziFCca Xk6iGUK2wx1RIkRKkPzQFsmyeARG+1QhkPjLtEzWpnzJyQp0zNF29SyLw1d3eZqdsjUm GbH3/GNNOQ9uYzied3yHOLSNrSCxff7BxNsRLjL/ub2/oPZVsWWurVr2aWlqHS1mxXKz XqJYWNzCcDGyxg+h9J822LOT+MDrDIses9Hrad9YaWtpsJ4jn6efZ2vLfSr4e4VSzxCJ At2B/rGacPXqdwHP3JfNTjuUPHQqYhOKm2Dy7ToJTaxapYb3M6YQaHqHJ1XSqGIsGB75 Ektg== X-Received: by 10.14.87.7 with SMTP id x7mr42057359eee.44.1397376108208; Sun, 13 Apr 2014 01:01:48 -0700 (PDT) Received: from hollewijn.internal (8d690a59.ftth.concepts.nl. [141.105.10.89]) by mx.google.com with ESMTPSA id g3sm31232370eet.35.2014.04.13.01.01.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 01:01:47 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: 9.2 Boot Problem From: Alban Hertroys In-Reply-To: <1D50A38D-8919-4034-A4E5-EEF8E78E638D@lafn.org> Date: Sun, 13 Apr 2014 10:02:19 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <12D44EED-29C6-4EC2-90CE-59A8246CEB57@gmail.com> References: <175D3755-BB9B-4EAD-BDAD-06E9670E06AB@lafn.org> <186472F9-A97B-4863-81BC-67BE788D5E9A@lafn.org> <791C8200-023A-4ACB-9B6F-F5A8B0E170F4@lafn.org> <5bfb4fb619954c3dfbd3499aafa98917.authenticated@ultimatedns.net> <4F983E6A-0A7D-403C-AFAA-9CCCCB05716F@lafn.org> <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> To: Doug Hardie X-Mailer: Apple Mail (2.1874) Cc: "dteske@FreeBSD.org Teske" , freebsd-stable , Chris H X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Apr 2014 08:01:51 -0000 On 13 Apr 2014, at 4:07, Doug Hardie 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.