From nobody@FreeBSD.org  Thu May 21 17:01:33 2009
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AE0AA1065670
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 May 2009 17:01:33 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 9A6B48FC13
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 May 2009 17:01:33 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n4LH1X4s033171
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 May 2009 17:01:33 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id n4LH1XFZ033170;
	Thu, 21 May 2009 17:01:33 GMT
	(envelope-from nobody)
Message-Id: <200905211701.n4LH1XFZ033170@www.freebsd.org>
Date: Thu, 21 May 2009 17:01:33 GMT
From: "Peter J. Blowers" <pblowers@safarivideonetworks.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: failure to set ip address in amd64 if_bce.c, i386 seems OK
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         134788
>Category:       kern
>Synopsis:       [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    delphij
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 21 17:10:00 UTC 2009
>Closed-Date:    Thu Oct 29 00:04:19 UTC 2009
>Last-Modified:  Tue Nov 10 23:40:01 UTC 2009
>Originator:     Peter J. Blowers
>Release:        7.2-RELEASE
>Organization:
Library Video Company
>Environment:
FreeBSD r710_1.ltn.lvc.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May  1 07:18:07 UTC 2009     root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Platform is a new Dell T610.  Error messages from if_bce.c on bootup of FreeBSD 7.2-RELEASE amd64.  Here's the dmesg:

Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-RELEASE #0: Fri May  1 07:18:07 UTC 2009
    root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU           E5520  @ 2.27GHz (2263.27-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x106a5  Stepping = 5
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x9ce3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,<b19>,<b20>,<b23>>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  Cores per package: 8
  Logical CPUs per core: 2
usable memory = 8567054336 (8170 MB)
avail memory  = 8265519104 (7882 MB)
ACPI APIC Table: <DELL   PE_SC3  >
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID: 16
 cpu1 (AP/HT): APIC ID: 17
 cpu2 (AP): APIC ID: 18
 cpu3 (AP/HT): APIC ID: 19
 cpu4 (AP): APIC ID: 20
 cpu5 (AP/HT): APIC ID: 21
 cpu6 (AP): APIC ID: 22
 cpu7 (AP/HT): APIC ID: 23
ioapic1: Changing APIC ID to 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 32-55 on motherboard
kbd1 at kbdmux0
acpi0: <DELL PE_SC3> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0xd6000000-0xd7ffffff irq 36 at device 0.0 on pci1
miibus0: <MII bus> on bce0
ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce0: Ethernet address: 00:24:e8:4d:ba:63
bce0: [ITHREAD]
bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x04060405); Flags( MFW MSI )
bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0xd8000000-0xd9ffffff irq 48 at device 0.1 on pci1
miibus1: <MII bus> on bce1
ukphy1: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce1: Ethernet address: 00:24:e8:4d:ba:65
bce1: [ITHREAD]
bce1: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x04060405); Flags( MFW MSI )
pcib2: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci2: <ACPI PCI bus> on pcib2
bce2: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0xda000000-0xdbffffff irq 32 at device 0.0 on pci2
miibus2: <MII bus> on bce2
ukphy2: <Generic IEEE 802.3u media interface> PHY 1 on miibus2
ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce2: Ethernet address: 00:24:e8:4d:ba:67
bce2: [ITHREAD]
bce2: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x04060405); Flags( MFW MSI )
bce3: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem 0xdc000000-0xddffffff irq 42 at device 0.1 on pci2
miibus3: <MII bus> on bce3
ukphy3: <Generic IEEE 802.3u media interface> PHY 1 on miibus3
ukphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bce3: Ethernet address: 00:24:e8:4d:ba:69
bce3: [ITHREAD]
bce3: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (0x04060405); Flags( MFW MSI )
pcib3: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci3: <ACPI PCI bus> on pcib3
mfi0: <Dell PERC 6> port 0xfc00-0xfcff mem 0xdf180000-0xdf1bffff,0xdf1c0000-0xdf1fffff irq 33 at device 0.0 on pci3
mfi0: Megaraid SAS driver Ver 3.00 
mfi0: 1162 (296219876s/0x0020/info) - Shutdown command received from host
mfi0: 1163 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028)
mfi0: 1164 (boot + 3s/0x0020/info) - Firmware version 1.21.02-0528
mfi0: 1165 (boot + 3s/0x0008/info) - Battery Present
mfi0: 1166 (boot + 3s/0x0020/info) - Controller hardware revision ID (0x0)
mfi0: 1167 (boot + 3s/0x0020/info) - Package version 6.1.1-0047
mfi0: 1168 (boot + 3s/0x0020/info) - Board Revision 
mfi0: 1169 (boot + 10s/0x0004/info) - Enclosure PD 20(c None/p0) communication restored
mfi0: 1170 (boot + 10s/0x0002/info) - Inserted: Encl PD 20
mfi0: 1171 (boot + 10s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5002408051683100,0000000000000000
mfi0: 1172 (boot + 10s/0x0002/info) - Inserted: PD 00(e0x20/s0)
mfi0: 1173 (boot + 10s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=1221000000000000,0000000000000000
mfi0: 1174 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028)
mfi0: 1175 (boot + 3s/0x0020/info) - Firmware version 1.21.02-0528
mfi0: 1176 (boot + 3s/0x0008/info) - Battery Present
mfi0: 1177 (boot + 3s/0x0020/info) - Controller hardware revision ID (0x0)
mfi0: 1178 (boot + 3s/0x0020/info) - Package version 6.1.1-0047
mfi0: 1179 (boot + 3s/0x0020/info) - Board Revision 
mfi0: 1180 (boot + 10s/0x0004/info) - Enclosure PD 20(c None/p0) communication restored
mfi0: 1181 (boot + 10s/0x0002/info) - Inserted: Encl PD 20
mfi0: 1182 (boot + 10s/0x0002/info) - Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5002408051683100,0000000000000000
mfi0: 1183 (boot + 10s/0x0002/info) - Inserted: PD 00(e0x20/s0)
mfi0: 1184 (boot + 10s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=1221000000000000,0000000000000000
mfi0: 1185 (296219937s/0x0020/info) - Time established as 05/21/09 11:18:57; (37 seconds since power on)
mfi0: 1186 (296219968s/0x0008/info) - Battery temperature is normal
mfi0: [ITHREAD]
pcib4: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci6: <ACPI PCI bus> on pcib6
pci0: <base peripheral, interrupt controller> at device 20.0 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.1 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.2 (no driver attached)
uhci0: <UHCI (generic) USB controller> port 0xec40-0xec5f irq 17 at device 26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0xec60-0xec7f irq 18 at device 26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdf0ff800-0xdf0ffbff irq 19 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: waiting for BIOS to give up control
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 4 ports with 4 removable, self powered
umass0: <OEM Mass Storage, class 0/0, rev 2.00/0.00, addr 2> on uhub2
uhub3: <vendor 0x0424 product 0x2514, class 9/0, rev 2.00/0.00, addr 3> on uhub2
uhub3: multiple transaction translators
uhub3: 3 ports with 3 removable, self powered
ukbd0: <Dell Dell USB Keyboard, class 0/0, rev 1.10/3.06, addr 4> on uhub3
kbd2 at ukbd0
uhci2: <UHCI (generic) USB controller> port 0xec80-0xec9f irq 21 at device 29.0 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
uhub4: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
uhub4: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0xeca0-0xecbf irq 20 at device 29.1 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub5: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb4
uhub5: 2 ports with 2 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xdf0ffc00-0xdf0fffff irq 21 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb5: EHCI version 1.0
usb5: companion controllers, 2 ports each: usb3 usb4
usb5: <EHCI (generic) USB 2.0 controller> on ehci1
usb5: USB revision 2.0
uhub6: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb5
uhub6: 4 ports with 4 removable, self powered
pcib7: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci7: <ACPI PCI bus> on pcib7
vgapci0: <VGA-compatible display> mem 0xd5800000-0xd5ffffff,0xde7fc000-0xde7fffff,0xde800000-0xdeffffff irq 19 at device 3.0 on pci7
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH9 SATA300 controller> port 0xec10-0xec17,0xec08-0xec0b,0xec18-0xec1f,0xec0c-0xec0f,0xec20-0xec2f,0xec30-0xec3f irq 23 at device 31.2 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
sio1: [FILTER]
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
cpu4: <ACPI CPU> on acpi0
est4: <Enhanced SpeedStep Frequency Control> on cpu4
p4tcc4: <CPU Frequency Thermal Control> on cpu4
cpu5: <ACPI CPU> on acpi0
est5: <Enhanced SpeedStep Frequency Control> on cpu5
p4tcc5: <CPU Frequency Thermal Control> on cpu5
cpu6: <ACPI CPU> on acpi0
est6: <Enhanced SpeedStep Frequency Control> on cpu6
p4tcc6: <CPU Frequency Thermal Control> on cpu6
cpu7: <ACPI CPU> on acpi0
est7: <Enhanced SpeedStep Frequency Control> on cpu7
p4tcc7: <CPU Frequency Thermal Control> on cpu7
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xd1800-0xd27ff,0xec000-0xeffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ukbd1: <Avocent USB Composite Device-0, class 0/0, rev 1.10/0.00, addr 2> on uhub4
kbd3 at ukbd1
ums0: <Avocent USB Composite Device-0, class 0/0, rev 1.10/0.00, addr 2> on uhub4
ums0: X report 0x0002 not supported
device_attach: ums0 attach returned 6
Timecounters tick every 1.000 msec
acd0: DVDR <PLDS DVD+/-RW DS-8A3S/HD51> at ata2-master SATA150
mfi0: 1187 (296219968s/0x0008/info) - Current capacity of the battery is above threshold
mfid0: <MFI Logical Disk> on mfi0
mfid0: 953344MB (1952448512 sectors) RAID volume '' is optimal
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #7 Launched!
SMP: AP CPU #4 Launched!
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Hitachi HDS721010KLA330 GKAO> Fixed Direct Access SCSI-4 device 
da0: 40.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
GEOM_LABEL: Label for provider mfid0s1a is ufsid/4a12c0da2ef0a762.
GEOM_LABEL: Label for provider mfid0s1d is ufsid/4a12c0efdeaf5581.
GEOM_LABEL: Label for provider mfid0s1e is ufsid/4a12c0daa231eca6.
GEOM_LABEL: Label for provider mfid0s1f is ufsid/4a12c0dacd7f69c8.
GEOM_LABEL: Label for provider da0s1a is ufsid/4a13c43f215ef832.
GEOM_LABEL: Label for provider da0s1d is ufsid/4a13c45a0fa7e195.
GEOM_LABEL: Label for provider da0s1e is ufsid/4a13c43ffdab6db6.
GEOM_LABEL: Label for provider da0s1f is ufsid/4a13c43f85e8be57.
Trying to mount root from ufs:/dev/mfid0s1a
GEOM_LABEL: Label ufsid/4a12c0da2ef0a762 removed.
GEOM_LABEL: Label for provider mfid0s1a is ufsid/4a12c0da2ef0a762.
GEOM_LABEL: Label ufsid/4a12c0daa231eca6 removed.
GEOM_LABEL: Label for provider mfid0s1e is ufsid/4a12c0daa231eca6.
GEOM_LABEL: Label ufsid/4a12c0dacd7f69c8 removed.
GEOM_LABEL: Label for provider mfid0s1f is ufsid/4a12c0dacd7f69c8.
GEOM_LABEL: Label ufsid/4a12c0efdeaf5581 removed.
GEOM_LABEL: Label for provider mfid0s1d is ufsid/4a12c0efdeaf5581.
GEOM_LABEL: Label ufsid/4a12c0da2ef0a762 removed.
GEOM_LABEL: Label ufsid/4a12c0daa231eca6 removed.
GEOM_LABEL: Label ufsid/4a12c0dacd7f69c8 removed.
GEOM_LABEL: Label ufsid/4a12c0efdeaf5581 removed.
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to UP
bce2: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred, resetting!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to DOWN
bce2: link state changed to UP
bce2: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred, resetting!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to DOWN
bce2: link state changed to UP
bce2: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred, resetting!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to DOWN
bce2: link state changed to UP
bce2: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred, resetting!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to DOWN
bce2: link state changed to UP
bce2: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred, resetting!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000000!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000010!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000000, offset = 0x00000014!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000080!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000240!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x00000258!
bce2: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory: cid_addr = 0x00000800, offset = 0x0000025C!
bce2: link state changed to DOWN
bce2: link state changed to UP




>How-To-Repeat:
Roughly 50/50 chance of seeing this on bootup.  Sometimes it will obtain an ip address and work, sometimes not.  If it *does* work, then I see only
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
bce2: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
in messages, and not the other errors.
>Fix:
DHCP is occasionally successful.  Statically assigning an address possibly works better, but no clear fix.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-amd64->freebsd-net 
Responsible-Changed-By: gavin 
Responsible-Changed-When: Fri May 22 20:40:10 UTC 2009 
Responsible-Changed-Why:  
I'm guessing this is a bug in bce(4) rather than in the amd-specific 
code 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 
State-Changed-From-To: open->feedback 
State-Changed-By: delphij 
State-Changed-When: Wed Jun 3 22:35:55 UTC 2009 
State-Changed-Why:  
Dear submitter, 

David has committed a fix 1 day ago which should fixed this issue. 
Could you please give it a test?  (7-STABLE). 

If you can't use 7-STABLE, please obtain the patch here: 

http://svn.freebsd.org/viewvc/base/stable/7/sys/dev/mii/brgphy.c?r1=181897&r2=193358&view=patch 

Please let us know if this has solved your problem, thanks! 


Responsible-Changed-From-To: freebsd-net->delphij 
Responsible-Changed-By: delphij 
Responsible-Changed-When: Wed Jun 3 22:35:55 UTC 2009 
Responsible-Changed-Why:  
Take so I can receive feedbacks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 

From: Jordan Newman <jn@isprime.com>
To: bug-followup@FreeBSD.org,
 pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Wed, 10 Jun 2009 10:23:54 -0400

 Tested with 7-STABLE and seeing the same problem.

From: Jordan Newman <jn@isprime.com>
To: bug-followup@FreeBSD.org,
 pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Sat, 13 Jun 2009 20:25:24 -0400

 --Apple-Mail-1-343951891
 Content-Type: text/plain;
 	charset=US-ASCII;
 	format=flowed;
 	delsp=yes
 Content-Transfer-Encoding: 7bit
 
 We have noticed that a cold reboot seems to fix the problem.  This may  
 be a problem with re-initialization.
 
 
 
 --Apple-Mail-1-343951891
 Content-Type: text/html;
 	charset=US-ASCII
 Content-Transfer-Encoding: quoted-printable
 
 <html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
 -webkit-line-break: after-white-space; ">We have noticed that a cold =
 reboot seems to fix the problem. &nbsp;This may be a problem with =
 re-initialization.<font class=3D"Apple-style-span" size=3D"3"><span =
 class=3D"Apple-style-span" style=3D"font-size: 12px;"><span =
 class=3D"Apple-style-span" style=3D"font-size: =
 medium;"><br></span></span></font><div apple-content-edited=3D"true"><span=
  class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
 rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
 normal; font-variant: normal; font-weight: normal; letter-spacing: =
 normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
 0px; -webkit-border-horizontal-spacing: 0px; =
 -webkit-border-vertical-spacing: 0px; =
 -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
 auto; -webkit-text-stroke-width: 0; "><div style=3D"word-wrap: =
 break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
 after-white-space; "><span class=3D"Apple-style-span" =
 style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
 Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
 font-weight: normal; letter-spacing: normal; line-height: normal; =
 orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; =
 white-space: normal; widows: 2; word-spacing: 0px; =
 -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
 auto; -webkit-text-stroke-width: 0; "><br =
 class=3D"Apple-interchange-newline"></span></div></span> =
 </div><br></body></html>=
 
 --Apple-Mail-1-343951891--

From: Peter Blowers <pblowers@safarivideonetworks.com>
To: bug-followup@FreeBSD.org,
 pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Wed, 1 Jul 2009 08:09:47 -0400

 As of today the problem persists in 7-STABLE after a warm reboot.  No  
 longer get 'PHY write timeout!' error, but the rest of the errors  
 remain, and no IP address is assigned.

From: Jordan Newman <jn@isprime.com>
To: bug-followup@FreeBSD.org,
 pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Tue, 11 Aug 2009 13:13:23 -0400

 This problem still persists, is there any debug information I can get  
 you that would help move this along.
State-Changed-From-To: feedback->open 
State-Changed-By: linimon 
State-Changed-When: Mon Aug 24 11:28:14 UTC 2009 
State-Changed-Why:  
Submitter notes the problem still recurs. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 
State-Changed-From-To: open->feedback 
State-Changed-By: delphij 
State-Changed-When: Mon Sep 28 22:03:29 UTC 2009 
State-Changed-Why:  
Dear submitter, 

davidch@ (the bce(4) author) has pointed out that this might be 
caused by a firmware bug.  Could you please try disabling the 
management firmware? 

- Download Broadcom diagnostic tool from: 

http://www.broadcom.com/support/ethernet_nic/driver-sla.php?driver=NX2-diag  

- Burn into CD-ROM, and boot off it 
- Choose 1 "FreeDOS Setup", English, Run FreeDOS from CDROM  
- Run the following command: 

cd nx2 
uxdiag -c 1 -mfw 0 
uxdiag -c 2 -mfw 0 

Please let us know if this would solve your problem, thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 

From: Adam Jacob Muller <adam@isprime.com>
To: bug-followup@FreeBSD.org, pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Mon, 5 Oct 2009 16:37:23 -0400

 Hi All,
 I've made a test today with a new Dell R610 and confirmed that  
 disabling the management firmware resolves this issue completely.
 
 However, booting into DOS to fix this issue is not ideal, is there any  
 chance of a FreeBSD version of this utility being released and/or  
 having this workaround integrated into the bce driver?
 
 ----
 Adam Jacob Muller
 ISPrime, Inc.
 AS23393
 212-812-9054
 adam@isprime.com
 

From: Tom Judge <tom@tomjudge.com>
To: bug-followup@FreeBSD.org, pblowers@safarivideonetworks.com
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c,
 i386 seems OK
Date: Wed, 28 Oct 2009 22:54:20 +0000

 On the R610 updating the firmware to version 5.0.9 will resolve this issue.
 
 Tom
State-Changed-From-To: feedback->closed 
State-Changed-By: delphij 
State-Changed-When: Thu Oct 29 00:02:21 UTC 2009 
State-Changed-Why:  
This is believed to be a firmware bug, and was confirmed to be 
fixed by a more recent Broadcom firmware update.  A workaround 
is also possible as discussed in the PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 

From: Adam Jacob Muller <adam@isprime.com>
To: bug-followup@FreeBSD.org, pblowers@safarivideonetworks.com
Cc: tom@tomjudge.com, davidch@freebsd.org, delphij@freebsd.org
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Sun, 8 Nov 2009 12:51:48 -0500

 Anyone know of a way to fix this that doesn't involve booting into  
 FreeDOS ?
 
 A FreeBSD version of the uxdiag utility ?
 
 As an aside, anyone know how to "attach" yourself to a pr so you can  
 find out when it gets updated?
 
 ---
 Adam Jacob Muller
 ISPrime, Inc.
 AS23393
 212-812-9054
 adam@isprime.com
 

From: "David Christensen" <davidch@broadcom.com>
To: "Adam Jacob Muller" <adam@isprime.com>,
	"bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org>,
	"pblowers@safarivideonetworks.com" <pblowers@safarivideonetworks.com>
Cc: "tom@tomjudge.com" <tom@tomjudge.com>,
	"delphij@freebsd.org" <delphij@freebsd.org>
Subject: RE: kern/134788: [bce] failure to set ip address in amd64
 if_bce.c, i386 seems OK
Date: Mon, 9 Nov 2009 10:26:54 -0800

 > Anyone know of a way to fix this that doesn't involve booting=20
 > into FreeDOS ?
 
 The dmesg dump indicates the driver is not detecting the correct
 PHY (notice that it attaches to ukphy0 rather than brgphy0).  Do
 you see the same thing on your system?  If you do then this problem
 is unrelated to a different issue that requires updating firmware
 on the adapter.
 
 This shouldn't happen in HEAD but I'd need to go back and look in
 RELENG_7 to see if it's fixed there.
 
 Dave=
 

From: Adam Jacob Muller <adam@isprime.com>
To: David Christensen <davidch@broadcom.com>
Cc: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.org>, "pblowers@safarivideonetworks.com" <pblowers@safarivideonetworks.com>, "tom@tomjudge.com" <tom@tomjudge.com>, "delphij@freebsd.org" <delphij@freebsd.org>
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Mon, 9 Nov 2009 16:24:05 -0500

 Hi David,
 Thanks in advance for your help with this.
 
 In both cases (working and non-working) I see the system attaching to  
 ukphy,
 
 test# grep -e bce -e phy dmesg.working
 bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xd6000000-0xd7ffffff irq 36 at device 0.0 on pci1
 miibus0: <MII bus> on bce0
 ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce0: Ethernet address: 00:21:9b:92:62:bc
 bce0: [ITHREAD]
 bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xd8000000-0xd9ffffff irq 48 at device 0.1 on pci1
 miibus1: <MII bus> on bce1
 ukphy1: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
 ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce1: Ethernet address: 00:21:9b:92:62:be
 bce1: [ITHREAD]
 bce1: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce2: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xda000000-0xdbffffff irq 32 at device 0.0 on pci2
 miibus2: <MII bus> on bce2
 ukphy2: <Generic IEEE 802.3u media interface> PHY 1 on miibus2
 ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce2: Ethernet address: 00:21:9b:92:62:c0
 bce2: [ITHREAD]
 bce2: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce3: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xdc000000-0xddffffff irq 42 at device 0.1 on pci2
 miibus3: <MII bus> on bce3
 ukphy3: <Generic IEEE 802.3u media interface> PHY 1 on miibus3
 ukphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce3: Ethernet address: 00:21:9b:92:62:c2
 bce3: [ITHREAD]
 bce3: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: link state changed to DOWN
 bce0: link state changed to UP
 
 
 
 test# grep -e bce -e phy dmesg.broken
 bce0: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xd6000000-0xd7ffffff irq 36 at device 0.0 on pci1
 miibus0: <MII bus> on bce0
 ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce0: Ethernet address: 00:21:9b:92:62:bc
 bce0: [ITHREAD]
 bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce1: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xd8000000-0xd9ffffff irq 48 at device 0.1 on pci1
 miibus1: <MII bus> on bce1
 ukphy1: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
 ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce1: Ethernet address: 00:21:9b:92:62:be
 bce1: [ITHREAD]
 bce1: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce2: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xda000000-0xdbffffff irq 32 at device 0.0 on pci2
 miibus2: <MII bus> on bce2
 ukphy2: <Generic IEEE 802.3u media interface> PHY 1 on miibus2
 ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce2: Ethernet address: 00:21:9b:92:62:c0
 bce2: [ITHREAD]
 bce2: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce3: <Broadcom NetXtreme II BCM5709 1000Base-T (C0)> mem  
 0xdc000000-0xddffffff irq 42 at device 0.1 on pci2
 miibus3: <MII bus> on bce3
 ukphy3: <Generic IEEE 802.3u media interface> PHY 1 on miibus3
 ukphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,  
 1000baseT-FDX, auto
 bce3: Ethernet address: 00:21:9b:92:62:c2
 bce3: [ITHREAD]
 bce3: ASIC (0x57092003); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C  
 (0x04060405); Flags( MFW MSI )
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000000!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000010!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000014!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000080!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000240!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000258!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x0000025C!
 bce0: link state changed to DOWN
 bce0: link state changed to UP
 bce0: /usr/src/sys/dev/bce/if_bce.c(6970): Watchdog timeout occurred,  
 resetting!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000000!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000010!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000000, offset = 0x00000014!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000080!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000240!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x00000258!
 bce0: /usr/src/sys/dev/bce/if_bce.c(1386); Unable to write CTX memory:  
 cid_addr = 0x00000800, offset = 0x0000025C!
 bce0: link state changed to DOWN
 bce0: link state changed to UP
 
 
 I can test this with HEAD, does it need to be HEAD though or are these  
 changes potentially in RELENG_8 already?
 I'm csup'ing this to HEAD right now and i'll retest.
 
 ----
 Adam Jacob Muller
 ISPrime, Inc.
 AS23393
 212-812-9054
 adam@isprime.com
 
 On Nov 9, 2009, at 1:26 PM, David Christensen wrote:
 
 >> Anyone know of a way to fix this that doesn't involve booting
 >> into FreeDOS ?
 >
 > The dmesg dump indicates the driver is not detecting the correct
 > PHY (notice that it attaches to ukphy0 rather than brgphy0).  Do
 > you see the same thing on your system?  If you do then this problem
 > is unrelated to a different issue that requires updating firmware
 > on the adapter.
 >
 > This shouldn't happen in HEAD but I'd need to go back and look in
 > RELENG_7 to see if it's fixed there.
 >
 > Dave
 

From: Xin LI <delphij@delphij.net>
To: Adam Jacob Muller <adam@isprime.com>
Cc: David Christensen <davidch@broadcom.com>, 
 "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.ORG>,
 "pblowers@safarivideonetworks.com" <pblowers@safarivideonetworks.com>, 
 "tom@tomjudge.com" <tom@tomjudge.com>,
 "delphij@freebsd.org" <delphij@FreeBSD.ORG>
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c,
 i386 seems OK
Date: Mon, 09 Nov 2009 13:47:43 -0800

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Hi, Adam,
 
 Adam Jacob Muller wrote:
 > In both cases (working and non-working) I see the system attaching to
 > ukphy,
 [...]
 > I can test this with HEAD, does it need to be HEAD though or are these
 > changes potentially in RELENG_8 already?
 > I'm csup'ing this to HEAD right now and i'll retest.
 
 Which FreeBSD version are you currently using?  I think 7-STABLE should
 already have the necessary PHY supporting bits for some newer hardware.
  FreeBSD 7.2-RELEASE (not -STABLE) for instance is lacking of some PHY
 changes that is necessary for newer bce(4) NICs to work.
 
 Cheers,
 - --
 Xin LI <delphij@delphij.net>	http://www.delphij.net/
 FreeBSD - The Power to Serve!	       Live free or die
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.13 (FreeBSD)
 
 iEYEARECAAYFAkr4jf8ACgkQi+vbBBjt66ARhACfQgSLvh+2XAn9HjiEnpggw2Us
 bGQAoLQhHzxIDi47EE6P/4s2QEJ2Vgz7
 =Hvjr
 -----END PGP SIGNATURE-----

From: "David Christensen" <davidch@broadcom.com>
To: "d@delphij.net" <d@delphij.net>,
	"Adam Jacob Muller" <adam@isprime.com>
Cc: "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.ORG>,
	"pblowers@safarivideonetworks.com" <pblowers@safarivideonetworks.com>,
	"tom@tomjudge.com" <tom@tomjudge.com>,
	"delphij@freebsd.org" <delphij@FreeBSD.ORG>
Subject: RE: kern/134788: [bce] failure to set ip address in amd64
 if_bce.c, i386 seems OK
Date: Mon, 9 Nov 2009 14:09:06 -0800

 > Adam Jacob Muller wrote:
 > > In both cases (working and non-working) I see the system=20
 > attaching to=20
 > > ukphy,
 > [...]
 > > I can test this with HEAD, does it need to be HEAD though=20
 > or are these=20
 > > changes potentially in RELENG_8 already?
 > > I'm csup'ing this to HEAD right now and i'll retest.
 >=20
 > Which FreeBSD version are you currently using?  I think=20
 > 7-STABLE should already have the necessary PHY supporting=20
 > bits for some newer hardware.
 >  FreeBSD 7.2-RELEASE (not -STABLE) for instance is lacking of=20
 > some PHY changes that is necessary for newer bce(4) NICs to work.
 
 The change you need is was checked into RELENG_7 on June 2nd
 (see v1.46.2.11 of sys/dev/mii/miidevs and v1.70.2.6 of=20
 sys/dev/mii/brgphy.c).
 
 Dave=
 

From: Adam Jacob Muller <adam@isprime.com>
To: "David Christensen" <davidch@broadcom.com>
Cc: "d@delphij.net" <d@delphij.net>, "bug-followup@FreeBSD.org" <bug-followup@FreeBSD.ORG>, "pblowers@safarivideonetworks.com" <pblowers@safarivideonetworks.com>, "tom@tomjudge.com" <tom@tomjudge.com>, "delphij@freebsd.org" <delphij@FreeBSD.ORG>
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c, i386 seems OK
Date: Mon, 9 Nov 2009 17:44:07 -0500

 On Nov 9, 2009, at 5:09 PM, David Christensen wrote:
 
 >> Adam Jacob Muller wrote:
 >>> In both cases (working and non-working) I see the system
 >> attaching to
 >>> ukphy,
 >> [...]
 >>> I can test this with HEAD, does it need to be HEAD though
 >> or are these
 >>> changes potentially in RELENG_8 already?
 >>> I'm csup'ing this to HEAD right now and i'll retest.
 >>
 >> Which FreeBSD version are you currently using?  I think
 >> 7-STABLE should already have the necessary PHY supporting
 >> bits for some newer hardware.
 >> FreeBSD 7.2-RELEASE (not -STABLE) for instance is lacking of
 >> some PHY changes that is necessary for newer bce(4) NICs to work.
 >
 > The change you need is was checked into RELENG_7 on June 2nd
 > (see v1.46.2.11 of sys/dev/mii/miidevs and v1.70.2.6 of
 > sys/dev/mii/brgphy.c).
 >
 > Dave
 
 
 Ok,
 This was 7.2-RELEASE since it was a freshly installed box just for  
 this test I did not bother to update to 7.2-STABLE like we normally do  
 (and still observe the original problem).
 Perhaps with 7.2-STABLE I will see ukrphy when "broken" and brgphy  
 when "working" ?
 
 test# ident /boot/kernel/kernel | grep brgphy
       $FreeBSD: src/sys/dev/mii/brgphy.c,v 1.70.2.5.4.1 2009/04/15  
 03:14:26 kensmith Exp $
 
 Testing 7.2-STABLE now.
 
 ----
 Adam Jacob Muller
 ISPrime, Inc.
 AS23393
 212-812-9054
 adam@isprime.com
 

From: Miroslav Lachman <000.fbsd@quip.cz>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/134788: [bce] failure to set ip address in amd64 if_bce.c,
 i386 seems OK
Date: Wed, 11 Nov 2009 00:36:25 +0100

 I have Dell R610 machines with bce0 - bce3
 
 bce0@pci0:1:0:0:        class=0x020000 card=0x02361028 chip=0x163914e4 
 rev=0x20 hdr=0x00
      vendor     = 'Broadcom Corporation'
      device     = 'NetXtreme II BCM5709 Gigabit Ethernet'
      class      = network
      subclass   = ethernet
 
 System is FreeBSD 7.2-RELEASE-p4 amd64
 
 I am also seeing messages like
 bce0: /usr/src/sys/dev/bce/if_bce.c(1525): PHY write timeout!
 
 But no messages like "Unable to write CTX memory" or anything else 
 related to bce0. My bce0 is attached to
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 
 I didn't tried any high network load, bce0 has IP without problems on 
 reboot.
 Is "PHY write timeout" serious problem for production use on server with 
 expected 300Mbps?
 
 Does it mean I need to upgrade system to 7-STABLE to get bce0 on brgphy?
 
 Miroslav Lachman
>Unformatted:
