Displaying 20 results from an estimated 5000 matches similar to: "fxp: stalled transfers"
2009 Jun 24
0
FreeBSD Errata Notice FreeBSD-EN-09:03.fxp
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-EN-09:03.fxp Errata Notice
The FreeBSD Project
Topic: Poor TCP performance of fxp(4)
Category: core
Module: sys/dev
Announced: 2009-06-24
Credits: Bjoern Koenig <bkoenig@alpha-tierchen.de>
Pyun YongHyeon <yongari@FreeBSD.org>
Affects:
2008 Sep 23
1
fxp multicast forwarding problems
Hi,
Whilst doing some QA work on XORP on my desktop, which has fxp0 and
msk0, fxp0 got totally hosed.
I was running PIM-SM and IGMPv2 router-mode on the box at the time.
I wonder if this is related to the problems with fxp multicast
transmission I saw back in April.
I'm a bit concerned about this as fxp is still a very widespread and
useful network chip.
I am running
2003 Sep 12
2
recent stability problems with fxp driver
I've spent the past four days or so updating machines here to 4.8/9-stable via
cvsup, and have done a complete make buildworld/kernel on each machine (some
SMP, some single processor). It seems something is broken with the latest fxp
driver, on each machine (different mobos and hardware configs) heavy network
traffic with fxp NICs causes timeouts and random kernel panics.
First machine to
2008 Oct 03
4
fxp performance with POLLING
Hello again :)
With POLLING enabled I experience about 10%-25% performance drop when
copying files over network. Tested with both SAMBA and NFS. Is it normal?
FreeBSD 7.1-PRERELEASE #0: Sat Sep 6 01:52:12 CEST 2008
fxp0: <Intel 82801DB (ICH4) Pro/100 Ethernet> port 0xc800-0xc83f mem
0xe1021000-0xe1021fff irq 20 at device 8.0 on pci1
# ifconfig fxp0
fxp0:
2003 Sep 12
2
fxp damages dmesg?
Motherboard ASUS CUSL2-C with 815EP chipset and
two Intel 82559 Pro/100 Ethernet cards
exibits the following.
dmesg reports usual text only a few seconds after reboot.
Later it displays a single line with a fragment of ipfw log, e.g.
167 213.131.11.152 in via fxp0
which seems to change with each new activity of ipfw.
Files /var/log/dmesg.today and /var/log/dmesg.yesterday
rotate daily as usual
2008 Oct 29
2
Problem with Bridging ... and bge devices under FreeBSD 7.x?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm trying to run a QEMU VM on top of a FreeBSD 7.x server ... I've tried the
exact same setup on my desktop, using 192.168.1.x and an fxp device, and it all
works perfectly, but as soon as I do this on another machine on a public IP,
I'm not getting any routing, I can't even ping it from the same machine ...
My first thought was
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
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
2004 Oct 09
9
fxp initiated behind shorewall
Okay, no one had any idea concerning my Radmin question, which I still
haven''t figured out. However, I am now trying to figure out an FXP problem.
All of the needed details are listed below the description problem.
Problem:
I have a local windows XP pro computer running FlashFXP behind shorewall
2.0.9 (unpatched) with only two interfaces (ppp0 and eth1) as
loc:192.168.1.5. The server
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
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
2003 Jun 05
1
fxp0: device timeout | SCB already complete (me too)
On Thu, 5 Jun 2003, Shaun Jurrens wrote:
> On Wed, Jun 04, 2003 at 06:32:46PM +0200, Palle Girgensohn wrote:
> #> Hi Shaun,
> #>
> #> Thanks for the input! Glad to hear I'm not the only one
> #>
> #> In my case, both the SCSI and NIC are integrated on the motherboard, so I
> #> cannot really move them around... :)
> #>
> #> Also, as I
2004 Jun 10
1
multiple connections
Hello,
I have an issue with multiple connections to the Internet. I tried
following the steps described in [1] but things are not working
properly. I would like the network setup as follows:
______
| |- ppp0 -- Dynamic IP (PPPoE on eth2)
Internal---- eth0 | GW |
|____|- eth1 -- Static IP -> Static''s GW
From [1], the
2006 Mar 20
1
FreeBSD box dropping packets
Dear All,
I have a FreeBSD box running 5.4-RELEASE-p8.
Two interfaces:
fxp0 - internet, SKA4 internal interface
fxp0: <Intel 82559 Pro/100 Ethernet>
bge0 - internal with 30 vlans on it, old bge Gigabit 64/32 PCI-2.1 adapter.
bge0: <Altima AC1002 Gigabit Ethernet, ASIC rev. 0x105>
Firewall is pf with about 5000 rules.
A week ago it was working just properly, but after adding more RAM
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
2013 Jun 12
2
[PATCH 0/2] fix kernel crash with macvtap on top of LRO
On Wed, Jun 12, 2013 at 03:56:36PM +0100, Ben Hutchings wrote:
> On Mon, 2013-06-10 at 10:07 +0300, Michael S. Tsirkin wrote:
> > On Thu, Feb 07, 2013 at 01:14:20PM -0500, David Miller wrote:
> > > From: Ben Hutchings <bhutchings at solarflare.com>
> > > Date: Thu, 7 Feb 2013 16:20:46 +0000
> > >
> > > > If the consensus is still that we must
2013 Jun 12
2
[PATCH 0/2] fix kernel crash with macvtap on top of LRO
On Wed, Jun 12, 2013 at 03:56:36PM +0100, Ben Hutchings wrote:
> On Mon, 2013-06-10 at 10:07 +0300, Michael S. Tsirkin wrote:
> > On Thu, Feb 07, 2013 at 01:14:20PM -0500, David Miller wrote:
> > > From: Ben Hutchings <bhutchings at solarflare.com>
> > > Date: Thu, 7 Feb 2013 16:20:46 +0000
> > >
> > > > If the consensus is still that we must
2009 Apr 14
6
problem with if_re on RELENG_7
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
2003 Aug 13
6
5.1-R-p2 crashes on SMP with AMI RAID and Intel 1000/Pro
Dear Sirs.
It seems to me a never ending story. We run a box with a TYAN Thunder
2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise
1600 RAID adapter and additional Intel 1000/Pro server type (64 bit)
GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this
state was really hard! It is a story similar to that what happend when
we changed towards FreeBSD
2014 Dec 18
1
[PATCH 09/10] macvtap: Re-enable UFO support
On Wed, Dec 17, 2014 at 09:43:51PM -0500, Vlad Yasevich wrote:
> On 12/17/2014 05:41 PM, Michael S. Tsirkin wrote:
> > On Wed, Dec 17, 2014 at 01:20:54PM -0500, Vladislav Yasevich wrote:
> >> Now that UFO is split into v4 and v6 parts, we can bring
> >> back v4 support. Continue to handle legacy applications
> >> by selecting the ipv6 fagment id but do not