Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!howland.reston.ans.net!xlink.net!rz.uni-karlsruhe.de!news.uni-stuttgart.de!news.rhrz.uni-bonn.de!RRZ.Uni-Koeln.DE!se From: se@MI.Uni-Koeln.DE (Stefan Esser) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: de0 fails - Can't fix iomem with UserConfig - Why? Date: 11 Jul 1995 09:19:36 GMT Organization: Institute for Mathematics, University of Cologne, Germany Lines: 38 Message-ID: <3ttfn8$78s@news.rrz.uni-koeln.de> References: <DB87I5.MKy@ncrcae.ColumbiaSC.ATTGIS.COM> <3thd4q$qe4@news.rrz.uni-koeln.de> <DBExyu.GJn@ncrcae.ColumbiaSC.ATTGIS.COM> NNTP-Posting-Host: fileserv1.mi.uni-koeln.de To: Jeff.McElroy@ColumbiaSC.ATTGIS.COM Bcc: se In article <DBExyu.GJn@ncrcae.ColumbiaSC.ATTGIS.COM>, Jeff.McElroy@ColumbiaSC.NCR.COM (Jeff McElroy (x6065)) writes: |> The system is an EISA motherboard with the Mercury (Intel) PCI chipset. |> |> Messages from boot... |> |> de0 <Digital DC21040 Ethernet> rev 35 inta irq5 on pci0:7 |> pci_map_mem failed: device's memrange 0x3900000-0x390007C is |> incompatible with its bridge's memrange 0x4000000 - 0xffffffff Yes, that is what I expected you to see ... There is some consistency check, that ought to make sure that all PCI devices behind a PCI to PCI bridge are mapped within the bridges memory window to that PCI bus. The patches I asked you to try ought to help in your case. The message will still be printed, but considered a warning, not a fatal error. |> There is no PCI-PCI bridge involved. There is a PCEB (PCI-Eisa Bridge). |> |> The adapter is a SMC EtherPower (SMC 8432T) |> |> Thanks for the help. I'll forward a bootlog and results of new build. The bootlog will help to fully understand, why the consistency test gives a false warning. STefan -- Stefan Esser Internet: <se@ZPR.Uni-Koeln.DE> Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln