From owner-freebsd-hackers Mon Jul 7 00:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29744 for hackers-outgoing; Mon, 7 Jul 1997 00:16:49 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29739 for ; Mon, 7 Jul 1997 00:16:42 -0700 (PDT) Received: (qmail 9379 invoked by uid 1000); 7 Jul 1997 07:16:52 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707070056.RAA18675@implode.root.com> Date: Mon, 07 Jul 1997 00:16:52 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: PCI Bridge Question Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 07-Jul-97 you wrote: ... > >fxp1 rev 2 int a irq 10 on > pci1:0 > >pci_map_mem failed: device's memrange 0xff9ff000-0xff9fffff is > incompatible > >with > > its bridge's memrange 0xfd200000-0xfd6fffff > >fxp1: Ethernet address 00:a0:c9:6b:8e:b6 > > > > What can I do to make this work? > > Did you verify that it actually doesn't work? From the above, the > device appears to have been mapped and attached okay. Yup. Dead as a dead horse. The other card is very alive. This problem does not exist under 3.0-current 9as of today). BTW, under SMP, this driver panics. This happens under NFS load. What one sees is: Page fault on cpuid = 0; It blows on fxp_add_rfabuf + 0xc7. We get there via: fxp_add_rfabuf fxp_intr smp_idleloop fork_trampoline (wish had a clue what a trampoline is - other than the Kmart type :-) Simon