Date: Wed, 2 Apr 2003 23:34:23 -0600 From: "Cagle, John (ISS-Houston)" <john.cagle@hp.com> To: "Bruce Evans" <bde@zeta.org.au> Cc: freebsd-current@freebsd.org Subject: RE: sio problem in -current (COM1) Message-ID: <C50AB9511EE59B49B2A503CB7AE1ABD10440E47A@cceexc19.americas.cpqcorp.net>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C50AB9511EE59B49B2A503CB7AE1ABD10440E47A>