From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 27 00:40:52 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B65BF16A4BF; Wed, 27 Aug 2003 00:40:52 -0700 (PDT) Received: from dmlb.org (pc2-cmbg4-6-cust36.cmbg.cable.ntl.com [81.96.76.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9698B4401A; Wed, 27 Aug 2003 00:40:45 -0700 (PDT) (envelope-from dmlb@dmlb.org) Received: from orac.my.domain ([192.168.200.75] helo=orac) by dmlb.org with smtp (Exim 3.36 #1) id 19ruul-000Obb-00; Wed, 27 Aug 2003 08:40:23 +0100 Message-ID: <009c01c36c6e$7a882150$4bc8a8c0@orac> From: "Duncan Barclay" To: "James Nobis" , "Kenneth D. Merry" References: Date: Wed, 27 Aug 2003 08:40:25 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-hackers@freebsd.org cc: freebsd-mobile@freebsd.org cc: dcswest@gmx.net Subject: Re: bcm4400 driver and Dell 8500 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2003 07:40:52 -0000 Hello James and Ken, Both of you are having real problems with the bcm driver and both of you have a Dell 8500. This is James' dmesg output, which from memory looks very similar to your Ken? > bcm0: mem 0xfaffe000-0xfaffffff irq 11 > at device 0.0 on pci2 > bcm0: Ethernet address: ff:ff:ff:ff:ff:ff > panic: bcm0: Strange type for core 0xffffffff > I'm running 5.1-current from august 22nd. I can try pulling down the > latest 5.1 tommorow if you think this might help. This is the same result > as when I tried the driver from over a month ago. We think that the problem is something to do with the PCI configuration of the machine. The ethernet address being ff:ff:ff:ff:ff:ff indicates that the memory map is not right. > Before sending this email I was going to obtain a backtrace. I recompiled > with the symbol table and kernel debugger and now the driver appears to > work fine. Should it work this way? Hmm interesting. Ken can you try this and see if the driver then works? Duncan