search for: re0

...e there any problems with the if_re ? After upgrade RELENG_7 on my laptop NIC stopped to work:( uname -a: FreeBSD notebook.minsk.domain 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #3: Fri Apr 10 20:38:55 EEST 2009 root@notebook.minsk.domain:/usr/obj/usr/src/sys/tiger-asus-a6m i386 notebook# dhclient re0 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 9 DHCPDISC...

Hi, I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after booting, re0 works for only a short time, then gives "re0: PHY read failed" over and over. Does anyone have a suggestion on how to debug? Thanks, Steve

Hello, I need some advice how to debug this issue ... Recently I got a new mainboard for a router, it's a Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. The problem is that re0 works fine and re1 doesn't: It doesn't receive any packets. Tcpdump displays all outgoing packets, but no incoming ones on re1. Ifconfig shows the link correctly (100 or 1000 Mbit, depending on where I plug the cable in). I also swapped cables just to be sure, but it made no difference. I...

...e re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most annoying fact is that we non-autonegotiating mode with our re and D-Link gigabit switches: fixing media at 1000BaseTX leads to link down regardless of master/slave settings on both sides; on re side it is even undocumented. Any clues? Thanks in advance. Sincerely, D.Marc...

I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's are not being detected. No Kernel modifications as this is a fresh install. pciconf -lv : re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet re1@pci0:2:0:0: class=0x020000 card=0x82c61043 ch...

...ter shut down there is active link. Here is some information after last update: [root@backup ~]# uname -a FreeBSD backup.pulsar.bg 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Mon Oct 6 17:01:26 EEST 2008 root@backup.pulsar.bg:/usr/obj/usr/src/sys/MYCONF amd64 [root@backup ~]# pciconf -lv ... re0@pci0:3:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet ... em0@pci0:1:0:0: class=0x020000 card=0x10838086 chip...

Hi, After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC refuses to handle large file transfers. pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' class = network subclass = ethernet Log messages: re: watchdog timeout...

...tered GENSEC backend 'sasl-DIGEST-MD5' registered GENSEC backend 'schannel' registered GENSEC backend 'spnego' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered added interface re0 ip=10.0.10.10 bcast=10.0.255.255 netmask=255.255.0.0 added interface re0 ip=10.0.10.10 bcast=10.0.255.255 netmask=255.255.0.0 added interface re0 ip=10.0.10.10 bcast=10.0.255.255 netmask=255.255.0.0 added interface re0 ip=10.0.10.10 bcast=10.0.255.255 netmask=255.255.0.0 finddcs: searching for a DC...

Hi all I've very big problem with my nfsd server. I'm running FreeBSD-stable and sometime (one time/week) i've this kind of message on the console : bge0 watchdog timeout problems fxp1 watchdog timeout problems and all my network card is down. Nothing can make the network card work again (only reboot working). There are only one service I need on this server and

...at device 1.1 on pci0 ata0: <ATA channel 0> on atapci0 ata0: [ITHREAD] ata1: <ATA channel 1> on atapci0 ata1: [ITHREAD] vgapci0: <VGA-compatible display> mem 0xf0000000-0xf1ffffff,0xf2000000-0xf2000fff at device 2.0 on pci0 pci0: <unknown> at device 3.0 (no driver attached) re0: <RealTek 8139C+ 10/100BaseTX> port 0xc200-0xc2ff mem 0xf4000000-0xf40000ff irq 5 at device 4.0 on pci0 miibus0: <MII bus> on re0 rlphy0: <RealTek internal media interface> PHY 0 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re0: Ethernet address: 00:16...

...tches ?(offset = 0) re str = + eprintf "PCRE.matches %s, %d ->%!" str offset; + let r = PCRE.matches ~offset re str in eprintf " %b\n%!" r; r @@ -103,6 +103,11 @@ let () = assert (subi 1 = (2, 3)); assert (subi 2 = (3, 3)); + assert (matches ~offset:5 re0 "aaabcabc" = true); + assert (sub 0 = "ab"); + + assert (matches ~offset:5 re0 "aaabcbaac" = false); + assert (replace re0 "dd" "abcabcaabccca" = "ddcabcaabccca"); assert (replace ~global:true re0 "dd" "abcab...

...?offset re str = + eprintf "PCRE.matches %s, %d ->%!" str (optget 0 offset); + let r = PCRE.matches ?offset re str in eprintf " %b\n%!" r; r @@ -103,6 +107,11 @@ let () = assert (subi 1 = (2, 3)); assert (subi 2 = (3, 3)); + assert (matches ~offset:5 re0 "aaabcabc" = true); + assert (sub 0 = "ab"); + + assert (matches ~offset:5 re0 "aaabcbaac" = false); + assert (replace re0 "dd" "abcabcaabccca" = "ddcabcaabccca"); assert (replace ~global:true re0 "dd" "abcab...

...gt; ata0: [ITHREAD] > ata1: <ATA channel 1> on atapci0 > ata1: [ITHREAD] > vgapci0: <VGA-compatible display> mem > 0xf0000000-0xf1ffffff,0xf2000000-0xf2000fff at device 2.0 on pci0 > pci0: <unknown> at device 3.0 (no driver attached) > re0: <RealTek 8139C+ 10/100BaseTX> port 0xc200-0xc2ff mem > 0xf4000000-0xf40000ff irq 5 at device 4.0 on pci0 > miibus0: <MII bus> on re0 > rlphy0: <RealTek internal media interface> PHY 0 on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,...

...NICs work while the onboard NIC does not? none2@pci0:1:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet re0@pci0:2:4:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169/8110 Family Gigabit Ethernet NIC' class = network subclass = ethernet re1@pci0:2:6:0: class=0x020000 card=0x10ec16f3 chip=0x...

...Message ---- > From: Pyun YongHyeon <pyunyh@gmail.com> > To: Ian FREISLICH <ianf@clue.co.za> > Cc: FreeBSD Current <freebsd-current@freebsd.org>; Robert Backhaus <robbak@robbak.com> > Sent: Monday, March 17, 2008 8:12:03 AM > Subject: Re: Packet corruption in re0 > > On Fri, Feb 22, 2008 at 10:43:22AM +0200, Ian FREISLICH wrote: > > Pyun YongHyeon wrote: > > > On Thu, Feb 21, 2008 at 01:18:18PM +0200, Ian FREISLICH wrote: > > > > Pyun YongHyeon wrote: > > > > > On Thu, Feb 21, 2008 at 02:47:43PM +1000,...

Str is a pretty ugly regexp module. Let's try to replace it with PCRE. This series of commits goes some small way towards that eventual goal. - - - I wonder if there was a deep reason why we had this? let unix2dos s = String.concat "\r\n" (Str.split_delim (Str.regexp_string "\n") s) I replaced it with what I think should be (nearly) equivalent: let unix2dos s =

...ne[2] runs FreeBSD 6.3-stable / amd64: root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 6.3-STABLE FreeBSD 6.3-STABLE #1: Sun Jan 27 02:10:15 CET 2008 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/SMP amd64 The machine has an if_re interface: root@kg-vm# pciconf -lv | grep -B 4 network subclass = VGA re0@pci2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network It looks like the interface works, because it gets the ip address and other dhcp...

This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with

This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with

...0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb0 at pci0 dev 28 function 0 "Intel 3400 PCIE" rev 0x06: apic 0 int 17 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 "Intel 3400 PCIE" rev 0x06: apic 0 int 17 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), apic 0 int 16, address 00:18:7d:2a:f1:1c rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4 ppb2 at pci0 dev 28 function 5 "Intel 3400 PCIE" rev 0x06: apic 0 int 16 pci3 at ppb2 bus 3 re1 at pci3 dev 0 func...