Date: Wed, 10 Jan 2001 16:58:39 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: bauerp <bauerp@bigfoot.com> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: serial port problems Message-ID: <Pine.BSF.4.21.0101101647440.25177-100000@besplex.bde.org> In-Reply-To: <Pine.NEB.4.10.10101041716430.1789-100000@corona.housebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 4 Jan 2001, bauerp 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101101647440.25177-100000>