From owner-freebsd-hackers  Sun Jul 13 22:03:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA29246
          for hackers-outgoing; Sun, 13 Jul 1997 22:03:02 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29241
          for <hackers@freebsd.org>; Sun, 13 Jul 1997 22:02:59 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA18892; Sun, 13 Jul 1997 22:58:35 -0600 (MDT)
Date: Sun, 13 Jul 1997 22:58:35 -0600 (MDT)
Message-Id: <199707140458.WAA18892@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Drew Derbyshire <ahd@kew.com>
Cc: hackers@freebsd.org
Subject: Re: access to SIO port freezes FreeBSD 2.2.1
In-Reply-To: <199707132321.TAA01158@pandora.hh.kew.com>
References: <199707132321.TAA01158@pandora.hh.kew.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Due to a "little" accident with athena (why in hell I give myself
> root password, I don't know, but it's another story anyway), I
> needed to put the modems into pandora.  So I disable the internal
> dumb ports, move the FIFO UART's to COM1/COM2, and put the modems
> in at COM3/COM4, IRQ 5 and regen the kernel, and system comes up
> fine.

You have both UART's sharing the same IRQ?  This is *bad* news, and can
cause all sorts of problems.  Also, some 'internal' serial ports claim
to allow themselves to be disabled, but in reality the electronics are
still hooked up. 


Nate