similar to: FreeBSD 6.3-stable and if_re - stability problems?

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:

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

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

There is an error in the chmod(1) man page. tingo at kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 root at kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo at kg-v2$ apropos ^sticky sticky(7) - sticky text and append-only directories tingo at kg-v2$ man 1 chmod | grep sticky 1000 (the sticky bit). See chmod(2)

Hello, I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu. tingo at kg-quiet$ uname -a FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013 root at kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo at kg-quiet$ dmesg | grep CPU | head -1 CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics (3618.02-MHz K8-class CPU)

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

Hello One one of my stable machines I see these messages in /var/log/messages: Mar 3 18:37:41 kg-i82 kernel: 16.011e9e3975b3aa06 too long Mar 3 21:41:42 kg-i82 kernel: 16.016a24cf0742715c too long Mar 3 21:41:58 kg-i82 kernel: 15.feb784aee196608c too short Does anyone know hwat the messages mean, or which part of the kernel they are from? Googling didn't help me. The machine runs FreeBSD

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, 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, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many

Hi, Is there any reason why uchcom[1] hasn't been MFC'ed to RELENG_7 yet? I see discussion[2] about this subject as far back as around 7.0-release, but I can't find any uchcom.c files in my src, not even for latest RELENG_7. References: 1) http://www.freebsd.org/cgi/man.cgi?query=uchcom&apropos=0&sektion=0&manpath=FreeBSD+8-current&format=html 2)

> On Fri, Aug 3, 2012 at 3:09 PM, Torfinn Ingolfsen > <torfinn.ingolfsen@getmail.no> wrote: > > Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation. > > Today I set up another partition, EFI system partition. The partyitions now looks like this: > > root@kg-vm2# gpart show ada0 > > => 34 250069613 ada0 GPT (119G)

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, Somehow[TM] an installation of 4.11 to ad0s3 managed to wipe out my existing disklabel for 7.0 on ad0s4. I now need to recover the disklabel to get my system to boot! There were three labels - ad0s4a: UFS, exact size unknown. Is it possible to infer this from the UFS partition size? I can mount this already, as I simply wrote an 'a' label of maximum size to the disklabel - ad0s4b:

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

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

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

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