From owner-freebsd-stable@FreeBSD.ORG Fri Apr 15 20:34:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ABCF1065672 for ; Fri, 15 Apr 2011 20:34:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E14018FC0C for ; Fri, 15 Apr 2011 20:34:44 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7838D46B23; Fri, 15 Apr 2011 16:34:44 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E8DA08A01B; Fri, 15 Apr 2011 16:34:43 -0400 (EDT) From: John Baldwin To: Przemyslaw Frasunek Date: Fri, 15 Apr 2011 16:34:43 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DA4A96F.9000507@frasunek.com> <201104151440.48349.jhb@freebsd.org> <4DA896D1.6050600@frasunek.com> In-Reply-To: <4DA896D1.6050600@frasunek.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104151634.43336.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 15 Apr 2011 16:34:44 -0400 (EDT) Cc: freebsd-stable@freebsd.org Subject: Re: Missing serial port after enabling serial console in loader.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2011 20:34:45 -0000 On Friday, April 15, 2011 3:04:49 pm Przemyslaw Frasunek wrote: > > Hmm, that unknown device is your COM1. Do you have a copy of your current > > dmesg available? I'm curious if sio0 failed to probe the UAR1 device and then > > later attached to UAR2. > > Sure, this is my non-verbose dmesg: http://www.frasunek.com/tmp/dmesg.txt > > It's from 7.3-RELEASE, but on 7.4 I get the same behaviour. Hmm, I don't see it even trying to probe the COM1 device. I'll have to wait until you get a verbose dmesg to investigate further I'm afraid. :( -- John Baldwin