From owner-freebsd-bugs Thu Jan 4 15:22:13 2001 From owner-freebsd-bugs@FreeBSD.ORG Thu Jan 4 15:22:11 2001 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from housebsd.org (corona.housebsd.org [207.112.136.202]) by hub.freebsd.org (Postfix) with ESMTP id 609A037B400 for ; Thu, 4 Jan 2001 15:22:11 -0800 (PST) Received: from localhost (localhost [[UNIX: localhost]]) by housebsd.org (8.9.3/8.8.8) with ESMTP id RAA04944 for ; Thu, 4 Jan 2001 17:21:33 -0600 (CST) X-Authentication-Warning: corona.housebsd.org: bauerp owned process doing -bs Date: Thu, 4 Jan 2001 17:21:32 -0600 (CST) From: bauerp X-Sender: bauerp@corona.housebsd.org To: freebsd-bugs@FreeBSD.org Subject: serial port problems 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 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. Thanks for the airtime. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message