From owner-freebsd-current@FreeBSD.ORG  Wed Apr  2 19:17:11 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3E89937B401
	for <freebsd-current@freebsd.org>;
	Wed,  2 Apr 2003 19:17:11 -0800 (PST)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C906C43F85
	for <freebsd-current@freebsd.org>;
	Wed,  2 Apr 2003 19:17:09 -0800 (PST)	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id NAA20785;
	Thu, 3 Apr 2003 13:16:49 +1000
Date: Thu, 3 Apr 2003 13:16:48 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: "Cagle, John (ISS-Houston)" <john.cagle@hp.com>
In-Reply-To: <C50AB9511EE59B49B2A503CB7AE1ABD10476C1A5@cceexc19.americas.cpqcorp.net>
Message-ID: <20030403130503.T28990@gamplex.bde.org>
References: <C50AB9511EE59B49B2A503CB7AE1ABD10476C1A5@cceexc19.americas.cpqcorp.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: sio problem in -current (COM1)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2003 03:17:11 -0000

On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote:

> I'm having a problem with -current on a ProLiant BL10e blade server.  On
> the blade server, we use a serial console on sio0/COM1.  This works
> perfectly with 4.8, but for some reason, the sio driver doesn't see COM1
> at all, and assigns COM2 resources to sio0.  Any pointers to where I
> should look would be greatly appreciated.
>
> I've attached dmesg output for 4.8 and -current on this blade.

4.8:
> ...
> config> di sio2

Maybe this helps.  sio2's irq is often the same as sio0's, and this can
sometimes cause problems.  Workarounds for some of these problems have
been broken and turned off since FreeBSD-2.

> ...
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A, console
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A

-current:
> ...
> sio0 port 0x2f8-0x2ff irq 3 on acpi0
> sio0: type 16550A, console

acpi sometimes does this for reasons that no one understands AFAIK.
Booting with -v should show the usual sio0 being probed and something
about why the probe failed, provided sio0 is in hints.  The probe order
may be relevant.

Bruce