From owner-freebsd-hackers  Thu Jun  5 05:31:28 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA10725
          for hackers-outgoing; Thu, 5 Jun 1997 05:31:28 -0700 (PDT)
Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA10720
          for <freebsd-hackers@freebsd.org>; Thu, 5 Jun 1997 05:31:25 -0700 (PDT)
Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA10786
  (5.67b/IDA-1.5 for <freebsd-hackers@freebsd.org>); Thu, 5 Jun 1997 14:31:19 +0200
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id OAA05420; Thu, 5 Jun 1997 14:31:17 +0200 (CEST)
X-Face: "<d]#=8pzx);RzeqSKI86OVa7=!0/(uRa.+B.9Z9\eNUn@UG?!`y7yt2dFNn%k4'.}](uE%
 yCO)$e&Y1%3EO~ifu6Q-#YUM&JZ't,}JkPnAz,8Dj33u%@GBi%[Y#LHz$]h7a<p4)-jKI7~sKjlP-^
 EvA[G;]v&0]W!EL%shs,{7x0|oqN4YVIs5,NI#,V{9"WF):5&RkOhyj*#-IAG}Tnu;YCF,d
Message-Id: <19970605143021.16317@mi.uni-koeln.de>
Date: Thu, 5 Jun 1997 14:30:21 +0200
From: Stefan Esser <se@FreeBSD.ORG>
To: mef@cs.washington.edu
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: pci_map_mem failed: Intel EtherExpress Pro 10/100B Ethernet
References: <199706050546.WAA09090@tweetie-bird.cs.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.74
In-Reply-To: <199706050546.WAA09090@tweetie-bird.cs.washington.edu>; from mef@cs.washington.edu on Wed, Jun 04, 1997 at 10:46:07PM -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Jun 4, mef@cs.washington.edu wrote:
> I get the following message when I boot on a PR440 Intel SMP
> motherboard using a May snapshot of the FreeBSD 3.0 code:
> 
> fxp0 <Intel EtherExpress Pro 10/100B Ethernet> rev 1 int a irq 10 on pci1:10:0
> pci_map_mem failed: device's memrange 0xF98FF000-0xF98FFFFF is incompatible with its bridge's memrange 0xF9A00000-0xFBEFFFFF

Hmmm, the card is working fine, you say ?
Could you please build a kernel with

options PCI_BRIDGE_DEBUG

boot that kernel with "-v", and send me 
the boot messages ?

> The device seems to work just fine, but I have not pushed it hard at
> all.  Just curious whether there is something that I need to do or
> look into.

No, if it works at all, then you don't need 
to worry. There is a PCI to PCI bridgem, that 
does block out accesses to memory mapped regs
that do not fall within 0xF9A00000-0xFBEFFFFF.

Your fxp card got its registers mapped to some
address outside that range by the PCI BIOS, and
thus should not work at all :)

Please send the verbose boot messages with the
above option added to your kernel config file.

But beware: I replaced the PCI code in -current
a few days ago, and you will get different boot
messages from that new code. The PCI_BRIDGE_DEBUG
will not provide any additional information anymore,
so you want to build a kernel from the sources that
came with that SNAP ...

Regards, STefan