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 Message-ID: <19970605143021.16317@mi.uni-koeln.de> 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 References: <199706050546.WAA09090@tweetie-bird.cs.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970605143021.16317>