From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 16 22:39:23 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0746C16A401 for ; Mon, 16 Jul 2007 22:39:23 +0000 (UTC) (envelope-from james.shank@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id B745613C4BD for ; Mon, 16 Jul 2007 22:39:22 +0000 (UTC) (envelope-from james.shank@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so311725anc for ; Mon, 16 Jul 2007 15:39:21 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eJ3uNDsD0o4wo4FdyKc8rWu9jDdUkK/vXzyA+ZLAP2JNfY484YJj6l1zbMpCcK6aJ+nOJ04KTpZAM8mgKqZOfDKtEXqBl+O4yp3vZHGHXaG4Ht0aQqMY0SwGS7BAhnpzWtbrh9WhFd2dNw/f83qo9U9GfAGGO8imFgbjl3UEjsA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WhPlxGcjngMkolWcGjj1btEGNdKObZkdiCbk37fioyEjvUt5D9XnFfe0AtyOS+T67s7Trv+3JEbgH5nlnPy4weJYKRbcSG7suqHf6HCPAZLOrF66Xz12/im3Im1PVmVpZKMs41B0ltOtNTRq8dCP6mrPHyYhXB6v+04NKJi9Xqg= Received: by 10.100.9.19 with SMTP id 19mr2571514ani.1184625561533; Mon, 16 Jul 2007 15:39:21 -0700 (PDT) Received: by 10.100.198.5 with HTTP; Mon, 16 Jul 2007 15:39:21 -0700 (PDT) Message-ID: Date: Mon, 16 Jul 2007 17:39:21 -0500 From: "James Shank" To: "Stefan Esser" , freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <469B2DB9.3090202@FreeBSD.org> Cc: Subject: Re: Problem with Broadcom 5704 B1 on amd64 6.2 release X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2007 22:39:23 -0000 Stefan, Another thing that might be helpful: When I last looked at the motherboard, I remember seeing the chip identified as a BCM 5704 B1. The BGE driver seems to think it is a B0. I don't know if this is significant, but I thought the more information I gave, the more you and the other smart people on here would have to work with. Thanks again, JAmes On 7/16/07, James Shank wrote: > Dear Stefan, > > Thanks for your help. I've attached the information you requested. > In particular, here are the relevant sections of the dmesg output: > > pcib5: at device 11.0 on pci8 > pcib5: secondary bus 10 > pcib5: subordinate bus 10 > pcib5: I/O decode 0xf000-0xfff > pcib5: memory decode 0xde100000-0xde1fffff > pcib5: prefetched decode 0xfff00000-0xfffff > pci10: on pcib5 > pci10: physical bus=10 > found-> vendor=0x14e4, dev=0x1648, revid=0x10 > bus=10, slot=9, func=0 > class=02-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0116, statreg=0x02b0, cachelnsz=16 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) > intpin=a, irq=10 > powerspec 2 supports D0 D3 current D0 > MSI supports 8 messages, 64 bit > map[10]: type 1, range 64, base de100000, size 16, enabled > pcib5: memory: end (de1fffff) < start (49dbdf2de100000) > pcib5: (null) requested unsupported memory range 0x0-0x0 (decoding > 0xde100000-0xde1fffff, 0xfff00000-0xfffff) > pcib5: matched entry for 10.9.INTA > pcib5: slot 9 INTA hardwired to IRQ 28 > found-> vendor=0x14e4, dev=0x1648, revid=0x10 > bus=10, slot=9, func=1 > class=02-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0116, statreg=0x02b0, cachelnsz=16 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x40 (16000 ns), maxlat=0x00 (0 ns) > intpin=b, irq=11 > powerspec 2 supports D0 D3 current D0 > MSI supports 8 messages, 64 bit > map[10]: type 1, range 64, base de110000, size 16, enabled > pcib5: memory: end (de1fffff) < start (dbfa72fdde110000) > pcib5: (null) requested unsupported memory range 0x0-0x0 (decoding > 0xde100000-0xde1fffff, 0xfff00000-0xfffff) > pcib5: matched entry for 10.9.INTB > pcib5: slot 9 INTB hardwired to IRQ 29 > bge0: mem > 0x49dbdf2de100000-0x49dbdf2de10ffff irq 28 at device 9.0 on pci10 > pcib5: memory: end (de1fffff) < start (49dbdf2de100000) > pcib5: bge0 requested unsupported memory range 0x0-0x0 (decoding > 0xde100000-0xde1fffff, 0xfff00000-0xfffff) > bge0: couldn't map memory > device_attach: bge0 attach returned 6 > bge1: mem > 0xdbfa72fdde110000-0xdbfa72fdde11ffff irq 29 at device 9.1 on pci10 > pcib5: memory: end (de1fffff) < start (dbfa72fdde110000) > pcib5: bge1 requested unsupported memory range 0x0-0x0 (decoding > 0xde100000-0xde1fffff, 0xfff00000-0xfffff) > bge1: couldn't map memory > device_attach: bge1 attach returned 6 > pci8: at device 11.1 (no > driver attached) > > > Any help you could provide would be greatly appreciated! > > Thanks again, > > James > > > On 7/16/07, Stefan Esser wrote: > > James Shank schrieb: > > > Greetings, > > > > > > I've run into a problem with the onboard Broadcom 5704 NetXtreme nics > > > on a Tyan S2891 Thunder K8SRE motherboard. > > > > > > Here is the relevant dmesg output to show the error: > > > > > > pcib5: at device 11.0 on pci8 > > > pci10: on pcib5 > > > pcib5: memory: end (de1fffff) < start (48739b2de100000) > > > pcib5: memory: end (de1fffff) < start (dbca73fdde110000) > > > bge0: mem > > > 0x48739b2de100000-0x48739b2de10ffff irq 28 at device 9.0 on pci10 > > > pcib5: memory: end (de1fffff) < start (48739b2de100000) > > > > Hi James, > > > > the information that you provided is not sufficient to diagnose > > this problem. You should post a *verbose* boot message log (via > > the boot loader menu or the loader command "boot -v"). > > > > Please do also provide a dump of the config registers of the > > PCI bridge for which the error condition is reported: > > > > # pciconf -r pci8:11:0 0:0x3f // device 11.0 on pci8 > > > > Not sure that I'll have time to look into this right today, but > > others on the list will want the same information so you may > > want to post it there ... > > > > This looks like a problem with the PCI bridge code, not the > > device init code, actually. But just in case it is not, you > > could also provide a register dump of the Ethernet chip: > > > > # pciconf -r pci10:9:0 0:0x3f > > > > Regards, STefan > > > >