From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 21:34:25 2003 Return-Path: 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 E96CA37B404 for ; Wed, 2 Apr 2003 21:34:25 -0800 (PST) Received: from ztxmail03.ztx.compaq.com (ztxmail03.ztx.compaq.com [161.114.1.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F1543FAF for ; Wed, 2 Apr 2003 21:34:24 -0800 (PST) (envelope-from john.cagle@hp.com) Received: from cceexg13.americas.cpqcorp.net (cceexg13.americas.cpqcorp.net [16.110.250.119]) by ztxmail03.ztx.compaq.com (Postfix) with ESMTP id 64C1C83E1; Wed, 2 Apr 2003 23:34:24 -0600 (CST) Received: from cceexc19.americas.cpqcorp.net ([16.110.250.85]) by cceexg13.americas.cpqcorp.net with Microsoft SMTPSVC(5.0.2195.2966); Wed, 2 Apr 2003 23:34:24 -0600 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 2 Apr 2003 23:34:23 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: sio problem in -current (COM1) Thread-Index: AcL5j4YgUfOE1PwtRWKfVLafkgddAwAEYVyw From: "Cagle, John (ISS-Houston)" To: "Bruce Evans" X-OriginalArrivalTime: 03 Apr 2003 05:34:24.0201 (UTC) FILETIME=[AF5E5B90:01C2F9A2] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2003 05:34:26 -0000 Thanks! It was an ACPI-related problem. I disabled ACPI (hint.acpi.0.disabled=3D"1" in /boot/device.hints) and rebooted and now both com ports show up properly as they did with FreeBSD 4.8. (These are just standard com ports, btw.) I didn't realize ACPI was involved in legacy com port detection. That's weird. Thanks, John > -----Original Message----- > From: Bruce Evans [mailto:bde@zeta.org.au]=20 > Sent: Wednesday, April 02, 2003 9:17 PM > To: Cagle, John (ISS-Houston) > Cc: freebsd-current@freebsd.org > Subject: Re: sio problem in -current (COM1) >=20 >=20 > On Wed, 2 Apr 2003, Cagle, John (ISS-Houston) wrote: >=20 > > I'm having a problem with -current on a ProLiant BL10e=20 > blade server. =20 > > On the blade server, we use a serial console on sio0/COM1. =20 > This works=20 > > perfectly with 4.8, but for some reason, the sio driver doesn't see=20 > > COM1 at all, and assigns COM2 resources to sio0. Any pointers to=20 > > where I should look would be greatly appreciated. > > > > I've attached dmesg output for 4.8 and -current on this blade. >=20 > 4.8: > > ... > > config> di sio2 >=20 > Maybe this helps. sio2's irq is often the same as sio0's,=20 > and this can sometimes cause problems. Workarounds for some=20 > of these problems have been broken and turned off since FreeBSD-2. >=20 > > ... > > 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 >=20 > -current: > > ... > > sio0 port 0x2f8-0x2ff irq 3 on acpi0 > > sio0: type 16550A, console >=20 > acpi sometimes does this for reasons that no one understands=20 > AFAIK. Booting with -v should show the usual sio0 being=20 > probed and something about why the probe failed, provided=20 > sio0 is in hints. The probe order may be relevant. >=20 > Bruce