similar to: problem with if_re on RELENG_7

Displaying 20 results from an estimated 200 matches similar to: "problem with if_re on RELENG_7"

2008 Jan 27
3
FreeBSD 6.3-stable and if_re - stability problems?
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
2008 Mar 31
4
Packet corruption in re0
----- 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: >
2009 Feb 24
4
7.1-R to RELENG_7 upgrade breaks re nic
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
2013 Feb 04
2
re(4) problems with GA-H77N-WIFI
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
2005 Mar 10
4
re driver trobles (RELENG_5)
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
2008 Feb 23
1
packet loss with re(4)
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:
2008 May 12
4
7.0 issues fixed? upgrade timing?
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
2009 Nov 30
2
em interface slow down on 8.0R
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
2008 Oct 06
2
can not wake on lan after halt -p (or shutdown -p now) on releng_7 and releng_7_0
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
2010 Jan 31
6
em(4) + ALTQ broken
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
2008 Aug 01
1
Realtek RTL8110 (SB) watchdog timeout.
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
2007 Sep 23
2
nfe driver 6.2 stable
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
2009 Mar 03
1
bce: unable to fix media
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
2008 Dec 02
2
Freebsd 7 STABLE 200807 amd64 - Realtek 8168 not working
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
2006 Mar 27
1
watchdog network card
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
2009 Apr 08
1
fxp: stalled transfers
Hello, after upgrading my system from 7.1-RELEASE to recent RELENG_7 I noticed stalled network transfers in certain cases. I have an Intel PRO/100 ethernet adapter (card=0x00408086 chip=0x12298086 rev=0x0c). In general networking works fine. I can ping hosts, surf on websites and so on. But if I send large files (>1 MB) to my server the transfer stalls after a few kilobytes. This concerns FTP
2013 Feb 13
3
Unusual TCP/IP Packet Size
Monitoring a tcpdump between two systems, a FreeBSD 9.1 system has the following interface: msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=c011b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE> ether 00:11:2f:2a:c7:03 inet 10.0.1.199 netmask 0xffffff00 broadcast 10.0.1.255 inet6 fe80::211:2fff:fe2a:c703%msk0 prefixlen 64 scopeid
2009 Apr 08
1
watchdog timeout
Hello I have some problems with 3Com nics, after a upgrade from 5.5-STABLE to 6.4-STABLE. This machine has two 3com nics (one is LAN other is WAN) and i see too much "watchdog timeout" on both cards. This on/off up/down on cards, affect the interrupt to clients that are downloading from apache web server, especially on large files. --------------------------------------------
2008 Feb 29
1
FreeBSD 7.0 + Xen 3.1 + HVM: Success!
Just thought I'd pass along that I have successfully installed FreeBSD 7.0 into a Xen 3.1 HVM. ?This one went as smooth as I expected, considering my experience with 6.3. ?Haven't done any benchmarking or stress testing or port installs or anything. ?But so far it's working nicely. Here's all the info. ?If you'd like to see anything else, let me know. Host hardware: ?
2017 Sep 20
4
[PATCH 0/4] Replace some uses of the Str module with PCRE.
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 =