From owner-freebsd-hackers Wed Sep 20 9: 8:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C0DF637B42C; Wed, 20 Sep 2000 09:08:54 -0700 (PDT) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id MAA21433; Wed, 20 Sep 2000 12:10:18 -0400 (EDT) Message-Id: <200009201610.MAA21433@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 20 Sep 2000 12:08:45 -0400 To: Mike Smith From: Dennis Subject: Re: Serial port locks up 4.1 Cc: hackers@freebsd.org In-Reply-To: <200009192341.QAA00943@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:41 PM 09/19/2000 -0700, you wrote: >> >> FYI: It seems that if you try to access the serial port on a MB with the >> port disabled, freebsd 4.1 will freeze up solid. Enabling the serial >> console will cause a lock up on boot, and any access to the port will do it >> as well. > >This is probably a feature of the board/super-IO chipset in question. > >In particular, the port should never have probed successfully if the port >was really "disabled", so you should never have been able to access it in >the first place. Its displays an error, but installs it anyway, so it seems that the driver is at least partially at fault. It happens on several very different MBs (both SBCs and ATX MBs), so its not an isolated issue. > >The correct solution, of course, is "don't do that". Easy to say , but it might be very hard to find if you have a serial console enabled and the machine just wont boot. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message