From owner-freebsd-hackers Thu Oct 2 11:49:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA14908 for hackers-outgoing; Thu, 2 Oct 1997 11:49:03 -0700 (PDT) Received: from vipunen.hut.fi (root@vipunen.hut.fi [130.233.224.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA14903; Thu, 2 Oct 1997 11:48:55 -0700 (PDT) Received: from dol-guldur.hut.fi (will@dol-guldur.hut.fi [130.233.224.39]) by vipunen.hut.fi (8.8.7/8.8.7) with ESMTP id VAA139470; Thu, 2 Oct 1997 21:48:48 +0300 Received: (will@localhost) by dol-guldur.hut.fi (8.8.3/8.6.7) id VAA31187; Thu, 2 Oct 1997 21:48:47 +0300 (EET DST) Date: Thu, 2 Oct 1997 21:48:47 +0300 (EET DST) Message-Id: <199710021848.VAA31187@dol-guldur.hut.fi> From: Ville-Pertti Keinonen To: Stefan Esser Cc: freebsd-hackers@freebsd.org Subject: Re: Conflicting I/O address spaces -- caused by...? In-Reply-To: <19970929084523.37780@mi.uni-koeln.de> References: <199709281110.OAA04780@dol-guldur.hut.fi> <19970929084523.37780@mi.uni-koeln.de> Reply-To: will@iki.fi Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser writes: > You better ask this on a xfree86 list, but I seem to > remember, that the X server *has to* use that port. That's basically the answer I got from there, as well. The question "why?" is still unanswered. > I think your PCI BIOS is at fault. When the PC Thanks. That was the problem, upgrading the BIOS helped. As a bonus, it also provided a new option, MPS version, which could be changed to 1.4, fixing the problem with the IOAPIC interrupt assignments for devices behind the PCI-PCI bridge. Strangely, it didn't change the revision in the floating pointer structure, but provides much more sensible information in the actual table. > (You may want to check bit 18 of the result of > > pciconf -r pci0:14:0 0x3c > > which will read the bridge control and interrupt > pin and line registers. If that bit is a 1, then > ISA MODE is enabled, but I doubt it, you Adaptec It wasn't, as you suspected, but it is now. > Using memory accesses to the Adaptec cards is a > valid fix, though! Wouldn't they still see the I/O ports, as well? > Port addresses in PCI are only present for legacy > device emulations, and for DOS which has no easy > way to access memory mapped registers above 1MB. That doesn't mean they shouldn't be assigned sane, non-conflicting values. ;--) > a fix. Using memory mapped accesses through that > PCI bridge may cause system hangs, but only if one > of several possible scenarios exists on your system. > They cause dead-lock, or even delivery of wrong data, > with a very low probability. It seemed to always hang within less than a minute while accessing a SCSI disk when I had it enabled... Maybe I'll try it again now that everything else seems to be working nicely.