From owner-freebsd-hackers Tue Sep 19 16:40:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 03FC937B422 for ; Tue, 19 Sep 2000 16:40:31 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA00943; Tue, 19 Sep 2000 16:41:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009192341.QAA00943@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: Serial port locks up 4.1 In-reply-to: Your message of "Tue, 19 Sep 2000 11:39:50 EDT." <200009191541.LAA18323@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Sep 2000 16:41:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. The correct solution, of course, is "don't do that". -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message