From nobody@FreeBSD.org  Wed Oct 26 18:44:22 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 61F8F16A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 Oct 2005 18:44:22 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1780743D4C
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 Oct 2005 18:44:22 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j9QIiMvA053214
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 26 Oct 2005 18:44:22 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j9QIiMGX053213;
	Wed, 26 Oct 2005 18:44:22 GMT
	(envelope-from nobody)
Message-Id: <200510261844.j9QIiMGX053213@www.freebsd.org>
Date: Wed, 26 Oct 2005 18:44:22 GMT
From: Andreas Klemm <bits_@web.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: 6.0rc1: nve0: device timeout (51)
X-Send-Pr-Version: www-2.3

>Number:         88045
>Category:       kern
>Synopsis:       [nve] [patch] 6.0rc1: nve0: device timeout (51)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 26 18:50:16 GMT 2005
>Closed-Date:    Tue Oct 06 07:50:37 UTC 2009
>Last-Modified:  Tue Oct 06 07:50:37 UTC 2009
>Originator:     Andreas Klemm
>Release:        6.0 rc1
>Organization:
home
>Environment:
FreeBSD titan.klemm.apsfilter.org 6.0-RC1 FreeBSD 6.0-RC1 #9: Wed Oct 26 16:00:02 CEST 2005     root@titan.klemm.apsfilter.org:/usr/obj/usr/src/sys/TITANi386  i386       
>Description:
My board has 2 Ethernet ports on board: re and nve.
Mainboard is a MCI K8N Neo2 with nForce 3 Ultra Chipset.
http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=607

The re interface works great since months.
Now with FreeBSD 6.0 I read about the nve driver and wanted to try
that ethernet port, that should/could have best performance, since
its directly connected to the nForce3 chipset whereas the other 
network port goes via additional PCI bridge which should eat up
performance/throughput (at least "theoretically", not that I was
unsatisfied with performance).

When using the nve interface with same cable and switchport (Draytek
Vigor 2600GI WLAN Router) then I get repeatedly console messages
Oct 26 19:47:45 titan kernel: nve0: device timeout (51)
Oct 26 19:47:45 titan kernel: nve0: link state changed to DOWN
Oct 26 19:47:48 titan kernel: nve0: link state changed to UP
Oct 26 19:48:45 titan kernel: nve0: device timeout (51)
Oct 26 19:48:45 titan kernel: nve0: link state changed to DOWN
Oct 26 19:48:48 titan kernel: nve0: link state changed to UP
Oct 26 19:49:45 titan kernel: nve0: device timeout (51)
Oct 26 19:49:45 titan kernel: nve0: link state changed to DOWN
Oct 26 19:49:48 titan kernel: nve0: link state changed to UP
Oct 26 19:50:11 titan kernel: nve0: device timeout (51)
Oct 26 19:50:11 titan kernel: nve0: link state changed to DOWN
Oct 26 19:50:14 titan kernel: nve0: link state changed to UP
Oct 26 19:51:04 titan kernel: nve0: device timeout (51)
Oct 26 19:51:04 titan kernel: nve0: link state changed to DOWN
Oct 26 19:51:07 titan kernel: nve0: link state changed to UP
Oct 26 19:51:56 titan kernel: nve0: device timeout (51)
Oct 26 19:51:56 titan kernel: nve0: link state changed to DOWN
Oct 26 19:51:59 titan kernel: nve0: link state changed to UP
Oct 26 19:52:14 titan kernel: nve0: device timeout (51)
Oct 26 19:52:14 titan kernel: nve0: link state changed to DOWN
Oct 26 19:52:17 titan kernel: nve0: link state changed to UP
Oct 26 19:53:14 titan kernel: nve0: device timeout (51)
Oct 26 19:53:14 titan kernel: nve0: link state changed to DOWN
Oct 26 19:53:17 titan kernel: nve0: link state changed to UP
Oct 26 19:54:15 titan kernel: nve0: device timeout (51)
Oct 26 19:54:15 titan kernel: nve0: link state changed to DOWN
Oct 26 19:54:17 titan kernel: nve0: link state changed to UP
Oct 26 19:56:16 titan kernel: nve0: device timeout (57)
Oct 26 19:56:16 titan kernel: nve0: link state changed to DOWN
Oct 26 19:56:18 titan kernel: nve0: link state changed to UP
Oct 26 19:56:29 titan kernel: nve0: device timeout (58)
Oct 26 19:56:29 titan kernel: nve0: link state changed to DOWN
Oct 26 19:56:31 titan kernel: nve0: link state changed to UP
Oct 26 19:56:45 titan kernel: nve0: device timeout (58)
Oct 26 19:56:45 titan kernel: nve0: link state changed to DOWN
Oct 26 19:56:47 titan kernel: nve0: link state changed to UP
Oct 26 19:57:37 titan kernel: nve0: device timeout (58)
Oct 26 19:57:37 titan kernel: nve0: link state changed to DOWN
Oct 26 19:57:39 titan kernel: nve0: link state changed to UP
Oct 26 19:58:34 titan kernel: nve0: device timeout (58)
Oct 26 19:58:34 titan kernel: nve0: link state changed to DOWN
Oct 26 19:58:37 titan kernel: nve0: link state changed to UP
Oct 26 19:59:34 titan kernel: nve0: device timeout (58)
Oct 26 19:59:34 titan kernel: nve0: link state changed to DOWN
Oct 26 19:59:36 titan kernel: nve0: link state changed to UP
Oct 26 20:01:06 titan kernel: nve0: device timeout (64)
Oct 26 20:01:06 titan kernel: nve0: link state changed to DOWN
Oct 26 20:01:08 titan kernel: nve0: link state changed to UP

Finally the whole port seems unusable since I cannot ping anything


root@titan[ttyp2]{226} ~ ping www.sun.de
PING www.sun.de (212.125.100.80): 56 data bytes
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available

mbuf statistic (netstat -m):

197/193/390 mbufs in use (current/cache/total)
94/78/172/25600 mbuf clusters in use (current/cache/total/max)
0/8/6656 sfbufs in use (current/peak/max)
237K/204K/441K bytes allocated to network (current/cache/total)
0 requests for sfbufs denied
0 requests for sfbufs delayed
0 requests for I/O initiated by sendfile
11 calls to protocol drain routines
real memory  = 1073676288 (1023 MB)
avail memory = 1041788928 (993 MB)

root@titan[ttyp3]{217} ~ pciconf -lv
agp0@pci0:0:0:  class=0x060000 card=0x02501462 chip=0x00e110de rev=0xa1 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nforce3 CPU to PCI Bridge'
    class    = bridge
    subclass = HOST-PCI
isab0@pci0:1:0: class=0x060100 card=0x02501462 chip=0x00e010de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce3 CPU to ISA Bridge'
    class    = bridge
    subclass = PCI-ISA
none0@pci0:1:1: class=0x0c0500 card=0x02501462 chip=0x00e410de rev=0xa1 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce PCI SMB Controller'
    class    = serial bus
    subclass = SMBus
ohci0@pci0:2:0: class=0x0c0310 card=0x02501462 chip=0x00e710de rev=0xa1 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce OHCI USB Controller'
    class    = serial bus
    subclass = USB
ohci1@pci0:2:1: class=0x0c0310 card=0x02501462 chip=0x00e710de rev=0xa1 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce OHCI USB Controller'
    class    = serial bus
    subclass = USB
ehci0@pci0:2:2: class=0x0c0320 card=0x02501462 chip=0x00e810de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce EHCI USB 2.0 Controller'
    class    = serial bus
    subclass = USB
nve0@pci0:5:0:  class=0x068000 card=0x02501462 chip=0x00df10de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'Network Bus Enumerator'
    class    = bridge
pcm0@pci0:6:0:  class=0x040100 card=0x75851462 chip=0x00ea10de rev=0xa1 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce AC'97 Audio Codec Interface'
    class    = multimedia
    subclass = audio
atapci0@pci0:8:0:       class=0x01018a card=0x02501462 chip=0x00e510de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce ATA Controller'
    class    = mass storage
    subclass = ATA
atapci1@pci0:9:0:       class=0x010185 card=0x02501462 chip=0x00ee10de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'CK8S Serial ATA Controller'
    class    = mass storage
    subclass = ATA
atapci2@pci0:10:0:      class=0x010185 card=0x02501462 chip=0x00e310de rev=0xa2 hdr=0x00
    vendor   = 'NVIDIA Corporation'
    device   = 'nforce SATA Controller'
    class    = mass storage
    subclass = ATA
pcib1@pci0:11:0:        class=0x060400 card=0x00000000 chip=0x00e210de rev=0xa2 hdr=0x01
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce3 PCI to AGP Bridge'
    class    = bridge
    subclass = PCI-PCI
pcib2@pci0:14:0:        class=0x060400 card=0x00000000 chip=0x00ed10de rev=0xa2 hdr=0x01
    vendor   = 'NVIDIA Corporation'
    device   = 'nForce PCI to PCI Bridge'
    class    = bridge
    subclass = PCI-PCI
hostb0@pci0:24:0:       class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00
    vendor   = 'Advanced Micro Devices (AMD)'
    device   = 'Athlon 64 / Opteron HyperTransport Technology Configuration'
    class    = bridge
    subclass = HOST-PCI
hostb1@pci0:24:1:       class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00
    vendor   = 'Advanced Micro Devices (AMD)'
    device   = 'Athlon 64 / Opteron Address Map'
    class    = bridge
    subclass = HOST-PCI
hostb2@pci0:24:2:       class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00
    vendor   = 'Advanced Micro Devices (AMD)'
    device   = 'Athlon 64 / Opteron DRAM Controller'
    class    = bridge
    subclass = HOST-PCI
hostb3@pci0:24:3:       class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00
    vendor   = 'Advanced Micro Devices (AMD)'
    device   = 'Athlon 64 / Opteron Miscellaneous Control'
    class    = bridge
    subclass = HOST-PCI
none1@pci1:0:0: class=0x030000 card=0x00021002 chip=0x4e481002 rev=0x00 hdr=0x00
    vendor   = 'ATI Technologies Inc'
    device   = 'Radeon 9800 Pro (R350)'
    class    = display
    subclass = VGA
none2@pci1:0:1: class=0x038000 card=0x00031002 chip=0x4e681002 rev=0x00 hdr=0x00
    vendor   = 'ATI Technologies Inc'
    device   = 'Radeon 9800 Pro (R350) - Secondary'
    class    = display
none3@pci2:8:0: class=0x040100 card=0x1115153b chip=0x17121412 rev=0x02 hdr=0x00
    vendor   = 'VIA Technologies Inc (Was: IC Ensemble Inc)'
    device   = 'ICE1712 Envy24 Multichannel Audio Controller'
    class    = multimedia
    subclass = audio
none4@pci2:12:0:        class=0x0c0010 card=0x086c0574 chip=0x30441106 rev=0x46 hdr=0x00
    vendor   = 'VIA Technologies Inc'
    device   = 'VT6306 VIA Fire II IEEE-1394 OHCI Link Layer Controller'
    class    = serial bus
    subclass = FireWire
re0@pci2:13:0:  class=0x020000 card=0x025c1462 chip=0x816910ec rev=0x10 hdr=0x00
    vendor   = 'Realtek Semiconductor'
    device   = 'RTL8169 Gigabit Ethernet Adapter'
    class    = network
    subclass = ethernet

Copyright (c) 1992-2005 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 6.0-RC1 #9: Wed Oct 26 16:00:02 CEST 2005
    root@titan.klemm.apsfilter.org:/usr/obj/usr/src/sys/TITANi386
ACPI APIC Table: <Nvidia AWRDACPI>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3000+ (1808.81-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x10ff0  Stepping = 0
  Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
  AMD Features=0xe2500800<SYSCALL,NX,MMX+,<b25>,LM,3DNow+,3DNow>
real memory  = 1073676288 (1023 MB)
avail memory = 1041788928 (993 MB)
ioapic0 <Version 1.1> irqs 0-23 on motherboard
acpi0: <Nvidia AWRDACPI> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNK1> irq 3 on acpi0
pci_link1: <ACPI PCI Link LNK2> on acpi0
pci_link2: <ACPI PCI Link LNK3> irq 10 on acpi0
pci_link3: <ACPI PCI Link LNK4> irq 5 on acpi0
pci_link4: <ACPI PCI Link LNK5> irq 5 on acpi0
pci_link5: <ACPI PCI Link LUBA> irq 7 on acpi0
pci_link6: <ACPI PCI Link LUBB> irq 7 on acpi0
pci_link7: <ACPI PCI Link LMAC> irq 7 on acpi0
pci_link8: <ACPI PCI Link LAPU> on acpi0
pci_link9: <ACPI PCI Link LACI> irq 11 on acpi0
pci_link10: <ACPI PCI Link LMCI> on acpi0
pci_link11: <ACPI PCI Link LSMB> irq 7 on acpi0
pci_link12: <ACPI PCI Link LUB2> irq 7 on acpi0
pci_link13: <ACPI PCI Link LFIR> on acpi0
pci_link14: <ACPI PCI Link L3CM> on acpi0
pci_link15: <ACPI PCI Link LIDE> on acpi0
pci_link16: <ACPI PCI Link LSID> irq 10 on acpi0
pci_link17: <ACPI PCI Link LFID> irq 11 on acpi0
pci_link18: <ACPI PCI Link APC1> irq 0 on acpi0
pci_link19: <ACPI PCI Link APC2> irq 0 on acpi0
pci_link20: <ACPI PCI Link APC3> irq 0 on acpi0
pci_link21: <ACPI PCI Link APC4> irq 0 on acpi0
pci_link22: <ACPI PCI Link APC5> irq 16 on acpi0
pci_link23: <ACPI PCI Link APCF> irq 0 on acpi0
pci_link24: <ACPI PCI Link APCG> irq 0 on acpi0
pci_link25: <ACPI PCI Link APCH> irq 0 on acpi0
pci_link26: <ACPI PCI Link APCI> irq 0 on acpi0
pci_link27: <ACPI PCI Link APCJ> irq 0 on acpi0
pci_link28: <ACPI PCI Link APCK> irq 0 on acpi0
pci_link29: <ACPI PCI Link APCS> irq 0 on acpi0
pci_link30: <ACPI PCI Link APCL> irq 0 on acpi0
pci_link31: <ACPI PCI Link APCM> irq 0 on acpi0
pci_link32: <ACPI PCI Link AP3C> irq 0 on acpi0
pci_link33: <ACPI PCI Link APCZ> irq 0 on acpi0
pci_link34: <ACPI PCI Link APSI> irq 0 on acpi0
pci_link35: <ACPI PCI Link APSJ> irq 0 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <NVIDIA nForce3-250 AGP Controller> mem 0xf0000000-0xf7ffffff at device 0.0 on pci0
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfc003000-0xfc003fff irq 21 at device 2.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xfc004000-0xfc004fff irq 22 at device 2.1 on pci0
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 4 ports with 4 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfc005000-0xfc0050ff irq 23 at device 2.2 on pci0
ehci0: [GIANT-LOCKED]
usb2: EHCI version 1.0
usb2: companion controllers, 4 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 8 ports with 8 removable, self powered
nve0: <NVIDIA nForce MCP7 Networking Adapter> port 0xa400-0xa407 mem 0xfc000000-0xfc000fff irq 21 at device 5.0 on pci0
nve0: Ethernet address 00:11:09:cd:3d:ec
miibus0: <MII bus> on nve0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
nve0: Ethernet address: 00:11:09:cd:3d:ec
nve0: [GIANT-LOCKED]
pcm0: <nVidia nForce3 250> port 0xa800-0xa8ff,0xac00-0xac7f mem 0xfc001000-0xfc001fff irq 22 at device 6.0 on pci0
pcm0: [GIANT-LOCKED]
pcm0: <Avance Logic ALC850 AC97 Codec>
atapci0: <nVidia nForce3 Pro UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 8.0 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <nVidia nForce3 Pro SATA150 controller> port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc800-0xc80f,0xcc00-0xcc7f irq 23 at device 9.0 on pci0
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
atapci2: <nVidia nForce3 Pro SATA150 controller> port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f,0xe400-0xe47f irq 20 at device 10.0 on pci0
ata4: <ATA channel 0> on atapci2
ata5: <ATA channel 1> on atapci2
pcib1: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
pci1: <display> at device 0.1 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 14.0 on pci0
pci_link18: BIOS IRQ 22 for 0.6.INTA is invalid
pci_link21: BIOS IRQ 23 for 0.9.INTA is invalid
pci_link19: BIOS IRQ 20 for 0.10.INTA is invalid
pci2: <ACPI PCI bus> on pcib2
pci2: <multimedia, audio> at device 8.0 (no driver attached)
pci2: <serial bus, FireWire> at device 12.0 (no driver attached)
re0: <RealTek 8169S Single-chip Gigabit Ethernet> port 0x9400-0x94ff mem 0xfb000000-0xfb0000ff irq 16 at device 13.0 on pci2
miibus1: <MII bus> on re0
rgephy0: <RTL8169S/8110S media interface> on miibus1
rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
re0: Ethernet address: 00:11:09:cd:3e:59
speaker0: <PC speaker> port 0x61 on acpi0
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xccfff,0xd0000-0xd3fff,0xd4000-0xd57ff,0xd6000-0xd6fff on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 1808812986 Hz quality 800
Timecounters tick every 1.000 msec
acd0: DVDROM <LITEON DVD-ROM LTD122/IHNC> at ata1-master UDMA33
acd1: DVDR <HL-DT-ST DVDRAM GSA-4082B/A201> at ata1-slave UDMA33
ad4: 152627MB <Seagate ST3160827AS 3.42> at ata2-master SATA150
ad6: 152627MB <Seagate ST3160827AS 3.42> at ata3-master SATA150
Trying to mount root from ufs:/dev/ad6s1a
cd0 at ata1 bus 0 target 0 lun 0
cd0: <LITEON DVD-ROM LTD122 IHNC> Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
cd1 at ata1 bus 0 target 1 lun 0
cd1: <HL-DT-ST DVDRAM GSA-4082B A201> Removable CD-ROM SCSI-0 device
cd1: 33.000MB/s transfers
cd1: Attempt to query device size failed: NOT READY, Medium not present
re0: link state changed to UP
re0: promiscuous mode enabled
re0: link state changed to DOWN
re0: link state changed to UP

# general options
machine         i386
cpu             I686_CPU
ident           TITANi386
maxusers        0
options         CPU_SUSP_HLT
options         INCLUDE_CONFIG_FILE

#makeoptions    DEBUG=-g
#options        KDB
#options        DDB

# kernel/vm options
options         SCHED_4BSD
options         PREEMPTION
options         COMPAT_43               # Compatible with BSD 4.3 [KEEP THIS!]
options         COMPAT_FREEBSD4         # Compatible with FreeBSD4
options         COMPAT_FREEBSD5         # Compatible with FreeBSD5
options         KTRACE
options         _KPOSIX_PRIORITY_SCHEDULING
options         ADAPTIVE_GIANT          # Giant mutex is adaptive.
options         BLKDEV_IOSIZE=8192
options         DFLDSIZ="(128*1024*1024)"
options         MAXDSIZ="(384*1024*1024)"
options         MAXSSIZ="(384*1024*1024)"
# Postgresql 180 clients
options         SYSVSHM                 # SYSV-style shared memory
options         SYSVMSG                 # SYSV-style message queues
options         SYSVSEM                 # SYSV-style semaphores
#options        SHMMAXPGS=4096
options         SHMMAXPGS=65536
options         SHMMAX="(SHMMAXPGS*PAGE_SIZE)+1"
options         SHMALL="(SHMMAXPGS*PAGE_SIZE)+1"
options         SEMMNI=40
options         SEMMNS=240
options         SEMUME=40
options         SEMMNU=120

# Firewall options
#options        IPFIREWALL
#options        IPFIREWALL_VERBOSE
#options        IPFIREWALL_VERBOSE_LIMIT=10
#options        ICMP_BANDLIM
#options        DUMMYNET

# IP stack options
options         INET
options         INET6
options         ZERO_COPY_SOCKETS
#options        IPSTEALTH       # don't touch ttl, hides fw from traceroute
#options        TCP_DROP_SYNFIN # ignore TCP packets with SYN+FIN set
                                # Prevent nmap identifying TCP/IP stack.
                                # Not recommended for web servers,
                                # it breaks RFC1644 extensions.
#options        TCP_RESTRICT_RST        # block emmision of TCP RST packets
                                # helpful in preventing TCP/IP stack
                                # identification.
#options        ACCEPT_FILTER_DATA
#options        ACCEPT_FILTER_HTTP
options         LIBMCHAIN
options         ALTQ
options         ALTQ_CBQ
options         ALTQ_RED
options         ALTQ_RIO
options         ALTQ_HFSC
options         ALTQ_PRIQ
options         NETGRAPH                        # netgraph(4) system
options         NETGRAPH_BLUETOOTH              # ng_bluetooth(4)
options         NETGRAPH_BLUETOOTH_BT3C         # ng_bt3c(4)
options         NETGRAPH_BLUETOOTH_HCI          # ng_hci(4)
options         NETGRAPH_BLUETOOTH_L2CAP        # ng_l2cap(4)
options         NETGRAPH_BLUETOOTH_SOCKET       # ng_btsocket(4)
options         NETGRAPH_BLUETOOTH_UBT          # ng_ubt(4)
options         NETGRAPH_BLUETOOTH_UBTBCMFW     # ubtbcmfw(4)
options         NETGRAPH_BPF
# needs giant
#options        NETGRAPH_BLUETOOTH_H4           # ng_h4(4)

# filesystems
options         GEOM_GPT
options         GEOM_BDE
options         FFS
options         SOFTUPDATES
options         UFS_ACL
options         UFS_DIRHASH
#options                UFS_EXTATTR
#options                UFS_EXTATTR_AUTOSTART
options         CD9660
options         CD9660_ICONV
options         UDF
options         PSEUDOFS
options         PROCFS
options         FDESCFS
options         QUOTA
options         MD_ROOT
options         NFSCLIENT
options         NFSSERVER
options         NTFS
options         NTFS_ICONV
options         MSDOSFS
options         MSDOSFS_ICONV
options         MSDOSFS_LARGE
options         LIBICONV
options         NULLFS

# MAC framework
#options                MAC
#options                MAC_BIBA
#options                MAC_BSDEXTENDED
#options                MAC_LOMAC
#options                MAC_MLS
#options                MAC_PARTITION
#options                MAC_PORTACL
#options                MAC_SEEOTHERUIDS

# hardware (&options)
options         SCSI_DELAY=5000         # Delay (in ms) before probing SCSI
options         KBD_INSTALL_CDEV        # install a CDEV entry in /dev

# northbridge
device          npx
device          apic
device          acpi
device          pmtimer
device          atkbdc
device          atkbd
device          psm
device          vga
device          sc
device          sio
device          speaker
device          fdc

# southbridge
device          isa
device          pci
device          agp
#device         cbb
#device         pccard
#device         cardbus
device          ata
device          atadisk
device          atapicd
options         ATA_STATIC_ID
device          scbus
device          pass
device          ses             # SCSI Environmental Services (and SAF-TE)
device          atapicam
device          cd
device          miibus
#device         bge
device          re
device          nve
#device         wlan
#device         ipw
#device         iwi
#device         sound
#device         snd_ich
device          usb
device          uhci
device          ohci
device          ehci
device          uhid
device          ukbd
device          ums
device          umass
device          ucom
device          uplcom
device          ppc
device          ppbus
device          lpt

# pseudo devices
device          md
device          loop
device          mem
device          io
device          random
device          ether
device          vlan
device          gif
#device         faith           # IPv6-to-IPv4 relaying (translation)
device          gre
device          tun
device          tap
device          bpf
#device         pf
#device         pflog
#device         pfsync
device          carp
device          pty
device          snp
options         VESA
device          splash






>How-To-Repeat:
simply use nve interface, the kernel messages appear automatically here...

>Fix:
no sorry
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: andreas 
State-Changed-When: Thu Oct 27 11:00:01 GMT 2005 
State-Changed-Why:  
Answer from Quinton Dolan q (at) OntheNet (dot) com (dot) au: 
+--------------------- 
I am not currently tracking FreeBSD development, but I have a good 
idea what may be contributing to the number of timeout errors you are 
seeing. 
Check around line 730 of if_nv.c (or whatever it's called in 6.0) 
sc->linkup = 0; 
sc->cur_rx = 0; 
sc->pending_rxs = 0; 
+       sc->pending_txs = 0; 
This should mostly eliminate the problem. 
+--------------------- 

I added this fix which entirely solves the problem in FreeBSD 6.0rc1: 
Index: if_nve.c 
=================================================================== 
RCS file: /data/ncvs/src/sys/dev/nve/if_nve.c,v 
retrieving revision 1.7.2.4 
diff -u -r1.7.2.4 if_nve.c 
--- if_nve.c    9 Oct 2005 04:18:17 -0000       1.7.2.4 
+++ if_nve.c    27 Oct 2005 09:58:45 -0000 
@@ -727,7 +727,7 @@ 

DEBUGOUT(NVE_DEBUG_INIT, "nve: nve_init_rings - entryn"); 

-       sc->cur_rx = sc->cur_tx = sc->pending_rxs = sc->pending_txs = 0; 
+       sc->cur_rx = sc->cur_tx = sc->pending_rxs = 0; 
/* Initialise RX ring */ 
for (i = 0; i < RX_RING_SIZE; i++) { 
struct nve_rx_desc *desc = sc->rx_desc + i; 

This should could/should solve these PRs from 6.0 Beta 3 and Beta 1 as well: 
- http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/84027 
if_nve gets stuck 
- http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85583 
[nve] [timeout] send errors ("device timeout") 
with nVidia Ethernet nve(4) in 6.0-BETA3 


Responsible-Changed-From-To: freebsd-bugs->obrien 
Responsible-Changed-By: andreas 
Responsible-Changed-When: Thu Oct 27 11:00:01 GMT 2005 
Responsible-Changed-Why:  
Answer from Quinton Dolan q (at) OntheNet (dot) com (dot) au: 
+--------------------- 
I am not currently tracking FreeBSD development, but I have a good 
idea what may be contributing to the number of timeout errors you are 
seeing. 
Check around line 730 of if_nv.c (or whatever it's called in 6.0) 
sc->linkup = 0; 
sc->cur_rx = 0; 
sc->pending_rxs = 0; 
+       sc->pending_txs = 0; 
This should mostly eliminate the problem. 
+--------------------- 

I added this fix which entirely solves the problem in FreeBSD 6.0rc1: 
Index: if_nve.c 
=================================================================== 
RCS file: /data/ncvs/src/sys/dev/nve/if_nve.c,v 
retrieving revision 1.7.2.4 
diff -u -r1.7.2.4 if_nve.c 
--- if_nve.c    9 Oct 2005 04:18:17 -0000       1.7.2.4 
+++ if_nve.c    27 Oct 2005 09:58:45 -0000 
@@ -727,7 +727,7 @@ 

DEBUGOUT(NVE_DEBUG_INIT, "nve: nve_init_rings - entryn"); 

-       sc->cur_rx = sc->cur_tx = sc->pending_rxs = sc->pending_txs = 0; 
+       sc->cur_rx = sc->cur_tx = sc->pending_rxs = 0; 
/* Initialise RX ring */ 
for (i = 0; i < RX_RING_SIZE; i++) { 
struct nve_rx_desc *desc = sc->rx_desc + i; 

This should could/should solve these PRs from 6.0 Beta 3 and Beta 1 as well: 
- http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/84027 
if_nve gets stuck 
- http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85583 
[nve] [timeout] send errors ("device timeout") 
with nVidia Ethernet nve(4) in 6.0-BETA3 

http://www.freebsd.org/cgi/query-pr.cgi?pr=88045 
State-Changed-From-To: analyzed->open 
State-Changed-By: andreas 
State-Changed-When: Thu Oct 27 16:28:57 GMT 2005 
State-Changed-Why:  
Q referred to fix something in nv_stop() 
But this already is fixed. 
My wrong understanding from his patch suggestion lead to a bogus patch. 
I found the variable in the wrogn function as well and changed something 
in the ringbuffer initialization which was not intended by Q. 
Forget about my patch. It didn't work anyway. 
So the issue is still open. 
Thanks David for pointing that out. 

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

From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Andreas Klemm <andreas@FreeBSD.org>
Cc: bits_@web.de, obrien@FreeBSD.org, bug-followup@FreeBSD.org
Subject: Re: kern/88045: [nve] [timeout] 6.0rc1: nve0: device timeout (51)
Date: Thu, 27 Oct 2005 17:39:20 +0000 (UTC)

 On Thu, 27 Oct 2005, Andreas Klemm wrote:
 
 > Answer from Quinton Dolan q (at) OntheNet (dot) com (dot) au:
 > +---------------------
 > I am not currently tracking FreeBSD development, but I have a good
 > idea what may be contributing to the number of timeout errors you are
 > seeing.
 > Check around line 730 of if_nv.c (or whatever it's called in 6.0)
 >         sc->linkup = 0;
 >         sc->cur_rx = 0;
 >         sc->pending_rxs = 0;
 > +       sc->pending_txs = 0;
 > This should mostly eliminate the problem.
 > +---------------------
 
 
 this got already committed but doesn't help here with an nf4:
 
 nve0: <NVIDIA nForce MCP9 Networking Adapter> port 0xe400-0xe407 mem 0xfc003000-0xfc003fff irq 3 at device 10.0 on pci0
 
 nve0: link state changed to UP
 nve0: device timeout (2)
 nve0: link state changed to DOWN
 nve0: link state changed to UP
 nve0: device timeout (4)
 nve0: link state changed to DOWN
 nve0: link state changed to UP
 
 no way to use the interface.
 
 
 > I added this fix which entirely solves the problem in FreeBSD 6.0rc1:
 > Index: if_nve.c
 > ===================================================================
 > RCS file: /data/ncvs/src/sys/dev/nve/if_nve.c,v
 > retrieving revision 1.7.2.4
 > diff -u -r1.7.2.4 if_nve.c
 > --- if_nve.c    9 Oct 2005 04:18:17 -0000       1.7.2.4
 > +++ if_nve.c    27 Oct 2005 09:58:45 -0000
 > @@ -727,7 +727,7 @@
 >
 >         DEBUGOUT(NVE_DEBUG_INIT, "nve: nve_init_rings - entry\n");
 >
 > -       sc->cur_rx = sc->cur_tx = sc->pending_rxs = sc->pending_txs = 0;
 > +       sc->cur_rx = sc->cur_tx = sc->pending_rxs = 0;
 >         /* Initialise RX ring */
 >         for (i = 0; i < RX_RING_SIZE; i++) {
 >                 struct nve_rx_desc *desc = sc->rx_desc + i;
 
 
 This change is a NOP from my understanding of the code. The function
 this is in is called from attach and sc->* , the softc should already
 got zeroed if I remember correctly.
 
 -- 
 Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT

From: <lucasvr@lsi.usp.br>
To: <bug-followup@FreeBSD.org>, <bits_@web.de>
Cc: <lima@catho.com.br>
Subject: Re: kern/88045 : [nve] [patch] 6.0rc1: nve0: device timeout (51)
Date: Sun, 27 Nov 2005 15:07:01 -0000

 This is a multi-part message in MIME format.
 
 ----------part4389cb9586226
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Hi,
 
 This is just a quick fix for the nve timeout problem.
 It seems to be related to the watchdog. The patch just
 defines a constant where it's possible to enable or disable
 it.
 
 The patch is not meant to be integrated, but maybe it serves
 as a workaround for many out there. Sorry for not looking deeper
 into the problem, but as I don't use BSD I can't work better on
 it at home :-)
 
 Cheers,
 Lucas
 
 ----------part4389cb9586226
 Content-Type: application/octet-stream; name="nve-watchdog.patch"
 Content-Transfer-Encoding: base64
 
 LS0tIHN5cy9kZXYvbnZlL2lmX252ZS5jLm9yaWcJU3VuIE9jdCAgOSAwMToxODoxNyAyMDA1Cisr
 KyBzeXMvZGV2L252ZS9pZl9udmUuYwlTdW4gTm92IDI3IDEyOjQwOjEwIDIwMDUKQEAgLTEyMiw2
 ICsxMjIsMTAgQEAgX19GQlNESUQoIiRGcmVlQlNEOiBzcmMvc3lzL2Rldi9udmUvaWZfbgogCiAj
 aW5jbHVkZSA8ZGV2L252ZS9pZl9udmVyZWcuaD4KIAorLyogd2F0Y2hkb2cgaXMga25vd24gdG8g
 YmUgYnJva2VuLiB0aGlzIGlzIGp1c3QgYW4gdWdseSBoYWNrLCAKKyAqIGJ1dCB3b3JrcyBmb3Ig
 bm93ICovCisjZGVmaW5lIEVOQUJMRV9XQVRDSERPRyAwCisKIE1PRFVMRV9ERVBFTkQobnZlLCBw
 Y2ksIDEsIDEsIDEpOwogTU9EVUxFX0RFUEVORChudmUsIGV0aGVyLCAxLCAxLCAxKTsKIE1PRFVM
 RV9ERVBFTkQobnZlLCBtaWlidXMsIDEsIDEsIDEpOwpAQCAtMTI0NCw4ICsxMjQ4LDggQEAgbnZl
 X21paWJ1c193cml0ZXJlZyhkZXZpY2VfdCBkZXYsIGludCBwaAogc3RhdGljIHZvaWQKIG52ZV93
 YXRjaGRvZyhzdHJ1Y3QgaWZuZXQgKmlmcCkKIHsKKyNpZiBFTkFCTEVfV0FUQ0hET0cKIAlzdHJ1
 Y3QgbnZlX3NvZnRjICpzYyA9IGlmcC0+aWZfc29mdGM7Ci0KIAlkZXZpY2VfcHJpbnRmKHNjLT5k
 ZXYsICJkZXZpY2UgdGltZW91dCAoJWQpXG4iLCBzYy0+cGVuZGluZ190eHMpOwogCiAJc2MtPnR4
 X2Vycm9ycysrOwpAQCAtMTI1Niw3ICsxMjYwLDcgQEAgbnZlX3dhdGNoZG9nKHN0cnVjdCBpZm5l
 dCAqaWZwKQogCiAJaWYgKGlmcC0+aWZfc25kLmlmcV9oZWFkICE9IE5VTEwpCiAJCW52ZV9pZnN0
 YXJ0KGlmcCk7Ci0KKyNlbmRpZgogCXJldHVybjsKIH0KIAo=
 
 ----------part4389cb9586226--
 

From: "Bjoern A. Zeeb" <bz@FreeBSD.org>
To: bug-followup@FreeBSD.org, bits_@web.de
Cc:  
Subject: Re: kern/88045 : [nve] [patch] 6.0rc1: nve0: device timeout (51)
Date: Mon, 12 Dec 2005 06:28:18 +0000 (UTC)

 Could you please try the patch at [1] which I just committed to HEAD[2].
 
 [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051211-01.diff
 [2] http://docs.freebsd.org/cgi/mid.cgi?200512120623.jBC6Nilf000427
 
 -- 
 Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT

From: Andras Got <andras@webmedia.hu>
To: bug-followup@FreeBSD.org,  bits_@web.de
Cc:  
Subject: Re: kern/88045: [nve] [patch] 6.0rc1: nve0: device timeout (51)
Date: Thu, 16 Feb 2006 20:51:56 +0100

 Hi,
 
 I'm installing a SUN Fire X2100 and having the same error with nve. I cannot really submit any debug 
 msg, because i couldn't boot fbsd to comconsole. The dmesg says totally the as mentioned above.
 
 There may be an error with bge also, but I hope there is none.
 
 OS Versions: 6.0-RELEASE and 6.1-BETA1 so far.
 
 The HW is an nVidia nforce pro chipset with nothing unusual imho. The nve iface (with Marvell 
 88EE1111 PHY) is in the factory default "Pin strap" mode in the bios. The Broadcom iface (type 5721) 
 looks good, but when nve starts to fail, then all the network goes wrong. :(
 
 Regards,
 Andrej
Responsible-Changed-From-To: obrien->jhb 
Responsible-Changed-By: jhb 
Responsible-Changed-When: Mon Jun 12 20:52:44 UTC 2006 
Responsible-Changed-Why:  
Take this one to make sure i don't lose it if it times out. 

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

From: John Baldwin <john@baldwin.cx>
To: bug-followup@freebsd.org, bits_@web.de
Cc:  
Subject: Re: kern/88045: [nve] [patch] 6.0rc1: nve0: device timeout (51)
Date: Mon, 12 Jun 2006 16:50:29 -0400

 This should be fixed in recent RELENG_6 (post 6.1 I'm afraid).  Can you please 
 test a very recent 6.x snapshot from snapshots.se.freebsd.org or a kernel 
 from a very recent RELENG_6 and report back?
 
 -- 
 John Baldwin

From: Dan Rich <drich@employees.org>
To: bug-followup@FreeBSD.org, bits_@web.de, jhb@FreeBSD.org
Cc:  
Subject: Re: kern/88045: [nve] [patch] 6.0rc1: nve0: device timeout (51)
Date: Thu, 25 Jan 2007 14:55:35 -0800

 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
 --------------enig06D2D4A36A71CD2D162BF065
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 I just picked up an ASUS M2NPV-VM motherboard that has an nve0 interface
 and I wanted to give you some feedback.  I'm running 6.2 RELEASE on it,
 and am running into the timeout issue.  My logs are full of entries like:=
 
 
 Jan 22 13:37:14 morpheus nve0: device timeout (64)
 Jan 22 13:37:14 morpheus nve0: link state changed to DOWN
 Jan 22 13:37:14 morpheus nve0: link state changed to DOWN
 Jan 22 13:37:15 morpheus nve0: link state changed to UP
 Jan 22 13:37:15 morpheus nve0: link state changed to UP
 Jan 22 13:39:43 morpheus nve0: device timeout (64)
 Jan 22 13:39:43 morpheus nve0: link state changed to DOWN
 Jan 22 13:39:43 morpheus nve0: link state changed to DOWN
 Jan 22 13:39:45 morpheus nve0: link state changed to UP
 Jan 22 13:39:45 morpheus nve0: link state changed to UP
 
 However, I did run into one interesting way of keeping the interface
 up.  I am running ntop on the machine, and it looks like as long as the
 interface is in promiscuous mode the timeouts go away and the interface
 is stable!  Is that any help in tracking down what might be going on?
 
 My machine: ASUS M2NPV-VM motherboard with an AMD Athlon 64 X2 dual core
 4600+.
 Here is some of the useful info from dmesg:
 
 FreeBSD 6.2-RELEASE #5: Mon Jan 22 11:38:03 PST 2007
     root@morpheus.lapseofthought.com:/usr/src/sys/amd64/compile/MORPHEUS
 Timecounter "i8254" frequency 1193182 Hz quality 0
 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (2405.03-MHz K8-class=
  CPU)
   Origin =3D "AuthenticAMD"  Id =3D 0x40fb2  Stepping =3D 2
   Features=3D0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,=
 PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
   Features2=3D0x2001<SSE3,CX16>
   AMD Features=3D0xea500800<SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow+,3DNow>=
 
   AMD Features2=3D0x1f<LAHF,CMP,<b2>,<b3>,CR8>
   Cores per package: 2
 real memory  =3D 2112815104 (2014 MB)
 avail memory =3D 2031714304 (1937 MB)
 ACPI APIC Table: <Nvidia AWRDACPI>
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
 =2E..
 nve0: <NVIDIA nForce MCP13 Networking Adapter> port 0xc800-0xc807 mem 0xf=
 e02b000-0xfe02bfff irq 21 at device 20.0 on pci0
 nve0: Ethernet address 00:17:31:6f:99:20
 miibus0: <MII bus> on nve0
 ukphy0: <Generic IEEE 802.3u media interface> on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000b=
 aseT-FDX, auto
 nve0: Ethernet address: 00:17:31:6f:99:20
 
 
 --=20
 Dan Rich <drich@employees.org> |   http://www.employees.org/~drich/
                                |  "Step up to red alert!"  "Are you sure,=
  sir?
                                |   It means changing the bulb in the sign=
 =2E.."
                                |          - Red Dwarf (BBC)
 
 
 
 --------------enig06D2D4A36A71CD2D162BF065
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: OpenPGP digital signature
 Content-Disposition: attachment; filename="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.6 (GNU/Linux)
 
 iD8DBQFFuTVnIYJ5xMxu09kRAtC/AJ9hFzgVSZo+Bj/pouPQjACCaq7z9gCfbK5x
 0E77PcW8avLAySJ/vDb9ge4=
 =t6zU
 -----END PGP SIGNATURE-----
 
 --------------enig06D2D4A36A71CD2D162BF065--
Responsible-Changed-From-To: jhb->freebsd-bugs 
Responsible-Changed-By: jhb 
Responsible-Changed-When: Mon Oct 5 14:22:11 UTC 2009 
Responsible-Changed-Why:  
Toss this one back into the pool.  It should probably be closed as nfe(4) 
has effectively replaced nve(4) at this point. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=88045 
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Tue Oct 6 07:50:35 UTC 2009 
State-Changed-Why:  
if_nfe(4) had replaced if_nve(4) some while ago. Please consider using 
that instead! Thanks for submitting the PR and for trying to make 
FreeBSD better! It's appreciated.. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=88045 
>Unformatted:
