From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 01:48:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB7B837B401 for ; Mon, 30 Jun 2003 01:48:42 -0700 (PDT) Received: from relay4.mail.uk.psi.net (relay4.mail.uk.psi.net [154.32.111.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 565BA43FD7 for ; Mon, 30 Jun 2003 01:48:39 -0700 (PDT) (envelope-from dmlb@dmlb.org) Received: from gate.ttpcom.com ([193.119.175.2] helo=vader) by relay4.mail.uk.psi.net with smtp (Exim 2.12 #2) id 19WuKz-0005Ju-00 for freebsd-current@freebsd.org; Mon, 30 Jun 2003 09:48:37 +0100 Received: from matrix.ttpcom.com ([193.119.172.14]) by vader; Mon, 30 Jun 2003 09:46:11 +0100 (BST) Received: from matrix [193.119.172.14] by matrix.ttpcom.com (SMTPD32-7.07) id AA56ADB03E0; Mon, 30 Jun 2003 09:52:38 +0100 Received: FROM DJK1Comp BY matrix ; Mon Jun 30 09:52:38 2003 +0100 Message-ID: <005b01c33ee4$455dd9f0$a7ac77c1@DJK1Comp> From: "Duncan Barclay" To: "Kenneth D. Merry" References: <000501c33e6f$e954da10$4bc8a8c0@orac> <20030629162638.A93448@panzer.kdm.org> <001801c33e8e$799ff4b0$4bc8a8c0@orac> <20030629170229.A93754@panzer.kdm.org> Date: Mon, 30 Jun 2003 09:40:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4920.2300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4920.2300 cc: freebsd-current@freebsd.org Subject: PCI help needed - Re: Very alpha BroadCom 4401 driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 08:48:43 -0000 From: "Kenneth D. Merry" > I sent dmesg and pciconf output last week...I've attached it again. Thanks. The penny is starting to drop here. A night's sleep does wonders. When you boot your machine it gets things right: bcm0: mem 0xfaffe000-0xfaffffff irq 11 at device 0.0 on pci2 pcib2: device bcm0 requested decoded memory range 0xfaffe000-0xfaffffff bcm0: Ethernet address: 00:0b:db:94:bf:42 bcm0: core 0x806 revi 0x4 vend 0x4243 match 0x18000058 (type 0x0 base 0x18000000) inst 0x0 bcm0: core 0x804 revi 0x2 vend 0x4243 match 0x18002058 (type 0x0 base 0x18002000) inst 0x0 When loaded as a module, the value for "match" is 0xffffffff, and this is wrong. > I just tried loading it as a module, and got the panic again. One > interesting thing is that is shows the MAC address as ff:ff:ff:ff:ff:ff. > > Another interesting thing is that if I insert a cardbus fxp card (the > Broadcom chip is on board), the whole system locks up hard if the bcm > driver is compiled into the kernel. If the bcm driver isn't there, things > work as expected. All this points to something strange with memory mappings - it may be your machine or the Broadcom chip set. On your machine, the chip is at a very high address 0xfaffe000-0xfaffffff. For some reason, when used as a module, this isn't being correctly mapped to the device driver - I have no idea why not as this is wanderering into PCI voodoo. Can anyone else suggest what's happening here? Ken has dmesg output available. > Ken Duncan