From owner-freebsd-bugs Mon Jan 22 2: 1:21 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B934037B401 for ; Mon, 22 Jan 2001 02:01:03 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA25883; Mon, 22 Jan 2001 21:00:47 +1100 Date: Mon, 22 Jan 2001 21:00:41 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Andy Farkas Cc: bauerp , freebsd-bugs@FreeBSD.ORG Subject: Re: serial port problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 20 Jan 2001, Andy Farkas wrote: > On Wed, 10 Jan 2001, Bruce Evans wrote: > > The driver already does an unreasonable amount of checking at probe > > time that the ports work. It even checks that interrupts work. > > Non-working interrupts caused the probe to fail in FreeBSD-2, but now > > certain types of broken interrupts only result in a boot message like > > "configured irq 4 not in bitmap of probed irqs 0". I don't know how > > this particular failure would cause a lockup. > Well, I think something is wrong with the probe, 'cause this machine does > not have any serial ports (it used to) yet says: > > ... > FreeBSD 4.1.1-STABLE #0: Sat Oct 14 19:20:47 EST 2000 > ... > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 > ... > > The probe did not pick up the fact that there is no serial port. > > This is an old dual P90 MB with no onboard coms or lpt. I don't see how it can get that far without there being something very much like an 8250 at port 0x3f8, unless the undocumented no-probe flag (0x40000) somehow gets set. The flag is only supposed to be set internally for pccards. It's interesting that only an 8250 is found. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message