From owner-freebsd-current@FreeBSD.ORG  Wed Aug  8 01:32:45 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id ABB2016A417
	for <freebsd-current@freebsd.org>; Wed,  8 Aug 2007 01:32:45 +0000 (UTC)
	(envelope-from peo@intersonic.se)
Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com
	[212.247.8.98])
	by mx1.freebsd.org (Postfix) with ESMTP id 6CFDA13C45E
	for <freebsd-current@freebsd.org>; Wed,  8 Aug 2007 01:32:45 +0000 (UTC)
	(envelope-from peo@intersonic.se)
X-Virus-Scanned: amavisd-new at inter-sonic.com
Message-ID: <46B91964.5080102@intersonic.se>
Date: Wed, 08 Aug 2007 03:16:20 +0200
From: Per olof Ljungmark <peo@intersonic.se>
Organization: Intersonic AB
User-Agent: Thunderbird 2.0.0.4 (X11/20070703)
MIME-Version: 1.0
To: Danny Braniss <danny@cs.huji.ac.il>
References: <E1I5htx-000N1N-LS@cs1.cs.huji.ac.il>
In-Reply-To: <E1I5htx-000N1N-LS@cs1.cs.huji.ac.il>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: bge/BCM5704 crashes current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2007 01:32:45 -0000

Danny Braniss wrote:
> Hi,
> 	I trying out an IBM X3455 which has 2 Broadcom BCM5704.
> they work ok under -stable, but -current just reboots without a trace,
> no panic, no nothing - actually some garbage on the serial port.
> I tried wit/and without msi.
> 
> this is what i get under -stable:
> bge0@pci2:1:0:  class=0x020000 card=0x02a61014 chip=0x164814e4 rev=0x10 
> hdr=0x00
>     vendor     = 'Broadcom Corporation'
>     device     = 'BCM5704 NetXtreme Dual Gigabit Adapter'
>     class      = network
>     subclass   = ethernet
>     cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split 
> transaction
>     cap 01[48] = powerspec 2  supports D0 D3  current D0
>     cap 03[50] = VPD
>     cap 05[58] = MSI supports 8 messages, 64 bit 
> bge1@pci2:1:1:  class=0x020000 card=0x02a61014 chip=0x164814e4 rev=0x10 
> hdr=0x00
>     vendor     = 'Broadcom Corporation'
>     device     = 'BCM5704 NetXtreme Dual Gigabit Adapter'
>     class      = network
>     subclass   = ethernet
>     cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split 
> transaction
>     cap 01[48] = powerspec 2  supports D0 D3  current D0
>     cap 03[50] = VPD
>     cap 05[58] = MSI supports 8 messages, 64 bit 
> 

Same here, system is HP Proliant DL380G4. System will lock hard at 
network start.

bge0: <Broadcom BCM5704 B0, ASIC rev. 0x2100> mem 0xfdef0000-0xfdefffff 
irq 25 at device 1.0 on pci3
miibus0: <MII bus> on bge0
brgphy0: <BCM5704 10/100/1000baseTX PHY> on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto
bge1: <Broadcom BCM5704 B0, ASIC rev. 0x2100> mem 0xfdee0000-0xfdeeffff 
irq 26 at device 1.1 on pci3
miibus1: <MII bus> on bge1
brgphy1: <BCM5704 10/100/1000baseTX PHY> on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 
1000baseTX-FDX, auto