From owner-freebsd-bugs Fri Jan 19 16:26:17 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id E57BB37B402 for ; Fri, 19 Jan 2001 16:25:53 -0800 (PST) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.1/8.11.1) with ESMTP id f0K0PQm25365; Sat, 20 Jan 2001 11:25:28 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Sat, 20 Jan 2001 11:25:26 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Bruce Evans 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 Wed, 10 Jan 2001, Bruce Evans wrote: > > I hope this is something that can be addressed. Last night i went to > > attach a console to a switch i was working on. Every time i went to > > attach to the serial port my system locked. cu -l /dev/cuaa0 minicom and > > tip all displayed the same results. > > > > I looked through dmesg to see nothing out of the ordinary. sio0 and sio1 > > found properly, all appeared normal. Fortunately being untrusting of pc > > hardware i checked the bios to find that the serial ports had been > > disabled. After re-enabling them this behavior went away. > > > > Is it possible to have some change in status mentioned in dmesg stating > > that the serial ports are infact not operational? Probing them and > > assigning irq's to the device that isn't enabled is not very intuitive > > when it comes to trouble shooting this. > > 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. > > Bruce 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. -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message