similar to: 7.1-R to RELENG_7 upgrade breaks re nic

Hi list, Are 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

----- Original 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: >

With FreeBSD 6.3-RELEASE, I'm finding significant packet loss (sometimes 85%). If I insert an Intel nic (fxp), there is nil packet loss with similar tests (ping -c 100). re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xc800-0xc8ff mem 0xf9fff000-0xf9ffffff irq 17 at device 0.0 on pci1 I have seen a thread on current mentioning similar problems:

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

Hello! Is anybody having stability problems with if_re under FreeBSD 6.3-stable? I know about PR kern/118719[1] but it doesn't look like the problem I'm having - at least my machine doesn't panic. My machine[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

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

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

1. I have a realtek network card and am using a cable modem router. Does anyone know if fixes for problems with these (see below) have been backported from HEAD to RELENG_7? 2. Is this a good time to upgrade to RELENG_7? 3. I read a post last week that advised that 7.1 is a long way off. Appreciate any advice on use of ULE 3.0 and ZFS prior to 7.1 and a comment on what is holding up 7.1. Thanks

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

Hi I installed the following driver. http://www.f.csce.kyushu-u.ac.jp/~shigeaki//software/freebsd-nfe.html Before I had the nve driver which was unstable on this server and on a prior server in both cases causing either spontaneous reboot or just a crash when under load. So far touchwood the nfe driver has stayed up and running at almost 3 days uptime and has had some stress. I know the driver

Hi all, Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac Minis via the memstick image; they seem to be pretty good little boxes for things like offsite secondary nameservers, for example, and they're easily replaced in case of problems. However, the newest minis have slightly different hardware, and FreeBSD can't find the built-in NIC. pciconf -lv on the

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

Hi, I noticed that network connection of one of my boxes got significantly slow just after upgrading it to 8.0R. The box has an em0 (82547EI) and worked fine with 7.2R. The symptoms are: - A ping to a host on the same LAN takes 990ms RTT, it reduces gradually to around 1ms, and then it returns to around 1s. The rate was about 2ms/ping. - The response is quite slow, but no packet

Greetings, I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving the realpath security advisory. The machine is remote and the NIC uses the rl driver. After booting the machine I had no network connectivity. The person at the remote site says the boot was normal and he could see that the NIC was properly configured but he could not ping it and I could not login. We booted

Dear colleagues, experimenting with new amd64-based router we found strange 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

Hi, tuning my network fixing nic's speed and duplex (both on server and switch) i got this error with bce driver: # ifconfig bce0 bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4> ether 00:15:c5:fe:11:01 inet 192.168.1.13 netmask 0xffffff00 broadcast

Hi Yonghyeon and All, >From time to time I use a notebook and boot FreeBSD from USB stick. FreeBSD 9.2-i386 works OK. So I tried to use FreeBSD 10.0-i386 BETA2 and the network adapter works for some 10-15 seconds and then stops with diagnostic message "msk0:watchdog timeout". I've found similar case at freebsd-current@ with no workaround. Yes, there is an interrupt storm as well.

I'm having problems getting PF + ALTQ to work on em(4) interfaces under 8.0-RELEASE. Kernel was rebuilt with the additional options necessary for ALTQ and what not. Same basic configuration works fine under 7.2-RELEASE. Basically, the queues create successfully but running a pfctl -vsq shows a zero packet/byte count for all queues, even the interface's root queues. This same problem is

Hi! Revisions 1.38.2.17/1.38.2.18 of src/sys/pci/if_rl.c (and corresponding 1.14.2.6 of src/sys/pci/if_rlreg.h) broke rl(4) at least for D-Link DFE 530TX+ 10/100BaseTX. I've sent PR an hour ago but still did not get its number. Meantime I've rolled back these revisions, rebuilt kernel and my NICs work again. Eugene Grosbein

Hello, recently I've installed 7.0 and now I'm observing strange thing with my Internet connection. Access to some sites may be VERY slow or doesn't work at all with different kinds of timeout messages or without messages at all (but other sites works fine). For example, firefox may say "Transferring data from..." message and then "The connection to the server was reset