From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 16 22:36:45 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 94FE816A403 for ; Mon, 16 Jul 2007 22:36:45 +0000 (UTC) (envelope-from james.shank@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 50B5713C4B6 for ; Mon, 16 Jul 2007 22:36:45 +0000 (UTC) (envelope-from james.shank@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so311574anc for ; Mon, 16 Jul 2007 15:36:44 -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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JjIWp23EQxG99N5X2/e0CrhRFq8yiJWgmv/+x3wmAX0CSZV0UCxCTVqxa4VOW4sRgBdIafjpKiDFI/hJHOI1WlIraP2zkHGb5PdMHEJRU83JDqOe5QzgcEu0tF6BHlb25QLqnY7UaFCfAbzNgGCUIxGRV9/SI3xWmIHkwfpLOTA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=T4frd7CIz/Er3jgSZOUj/DyxjnM0pRs3WkJyEdGXs6I5+EnETPIeO0hKxDgWqKrNEwcrPegI5a3zQ34Vy1FkPA+i0+k7koOyDALl7KXHcA4PfmWz+RH/ygPlQpsxNIq/wS8IgHMKxtdW6YeL0EgAj3oNBocctMOA91nZfz9JPQ4= Received: by 10.100.8.18 with SMTP id 18mr2572723anh.1184625404625; Mon, 16 Jul 2007 15:36:44 -0700 (PDT) Received: by 10.100.198.5 with HTTP; Mon, 16 Jul 2007 15:36:44 -0700 (PDT) Message-ID: Date: Mon, 16 Jul 2007 17:36:44 -0500 From: "James Shank" To: "John Baldwin" In-Reply-To: <200707160754.01330.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200707160754.01330.jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org 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:36:45 -0000 Dear John, Thanks for the suggestion. I tried the 7.0 livefs snapshot and had the same results as with the 6.2 release; identical errors on both. Thanks, James On 7/16/07, John Baldwin wrote: > On Monday 16 July 2007 01:37:40 am James Shank wrote: > > 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) > > bge0: couldn't map memory > > device_attach: bge0 attach returned 6 > > bge1: mem > > 0xdbca73fdde110000-0xdbca73fdde11ffff irq 29 at device 9.1 on pci10 > > pcib5: memory: end (de1fffff) < start (dbca73fdde110000) > > bge1: couldn't map memory > > device_attach: bge1 attach returned 6 > > > > It appears to me that the problem might be due to using a 32-bit int > > for end addresses where it looks like the start address uses 64-bit > > int. > > > > Any input on how to proceed would be greatly appreciated. > > > > I've also attached full dmesg output as well as pciconf -l -v output. > > > > Thanks! > > Can you try a 7.0 snapshot? It has different handling of 64-bit BARs. If 7 > works then we can look at backporting those changes to 6.x. > > -- > John Baldwin >