Re: rl0 discard oversize frame
Amer H. Alhabsi a écrit : Philippe Laquet wrote: Hi Amer, Could you send an ifconfig -a ? It may occur if your MTU doesn't match Amer H. Alhabsi a écrit : Hi, The network card that came with the PC (Broadcom NetXtreme Gigabit Ethernet) was not recognized by sysinstall. So I bought a real tek based card that works fine. But when I run dmesg, I get lots of these lines (almost 900): rl0: discard oversize frame (ether type 0 flags 3 len 1532 max 1514) Can someone please advise what can be done to stop that. I'm using FreeBSD 6.2 release. Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for the reply. Here is the output of ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 172.22.15.39 netmask 0x broadcast 172.22.255.255 ether 00:e0:4c:ef:04:87 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 OK, You may try to increase your MTU by using ifconfig rl0 mtu 1580 (for example) - Do not forget to add this option in /etc/rc.conf (for boot settings) If it does not solve the problem, the problem could be due to your network interface and the RL driver itself. In that case, you have to shut down the interface and remount it, I agree that it is not a proper solution but I saw it on a newsgroup. Hope this help! Kind Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rl0 discard oversize frame
Hi, The network card that came with the PC (Broadcom NetXtreme Gigabit Ethernet) was not recognized by sysinstall. So I bought a real tek based card that works fine. But when I run dmesg, I get lots of these lines (almost 900): rl0: discard oversize frame (ether type 0 flags 3 len 1532 max 1514) Can someone please advise what can be done to stop that. I'm using FreeBSD 6.2 release. Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize frame
Hi Amer, Could you send an ifconfig -a ? It may occur if your MTU doesn't match Amer H. Alhabsi a écrit : Hi, The network card that came with the PC (Broadcom NetXtreme Gigabit Ethernet) was not recognized by sysinstall. So I bought a real tek based card that works fine. But when I run dmesg, I get lots of these lines (almost 900): rl0: discard oversize frame (ether type 0 flags 3 len 1532 max 1514) Can someone please advise what can be done to stop that. I'm using FreeBSD 6.2 release. Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize frame
Philippe Laquet wrote: Hi Amer, Could you send an ifconfig -a ? It may occur if your MTU doesn't match Amer H. Alhabsi a écrit : Hi, The network card that came with the PC (Broadcom NetXtreme Gigabit Ethernet) was not recognized by sysinstall. So I bought a real tek based card that works fine. But when I run dmesg, I get lots of these lines (almost 900): rl0: discard oversize frame (ether type 0 flags 3 len 1532 max 1514) Can someone please advise what can be done to stop that. I'm using FreeBSD 6.2 release. Thanks, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for the reply. Here is the output of ifconfig -a rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 172.22.15.39 netmask 0x broadcast 172.22.255.255 ether 00:e0:4c:ef:04:87 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize
On 28/02/06, Igor Robul [EMAIL PROTECTED] wrote: On Tue, Feb 28, 2006 at 01:55:56AM -0500, David Scheidt wrote: The RealTek cards supported by the rl(4) driver are trash. If you want to write a better driver, knock yourself out. I'm sure Bill Paul won't mind. Keep in mind that there are other, better performing NICs available for the about same price. Most RL8139 cards work fine in our company. Most Windows PCs have these cards (slowly replaced by integrated NICs on new motherboards), also some FreeBSD-based routers have these NICs. ___ Likewise fine here, the fact windows outperforms freebsd with realteks should be enough embarrasement to warrant a rewrite. A realtek 8139 can easily do full 100mbit with no packet loss but just uses higher cpu utilisation, also its not always easy to say to a datacentre swap the card for diff brand. I like freebsd a lot, but my most worrying thought is their attitude to low end hardware, alot of 486 and 586 class and low end 686 class machines fail to boot in 6.x and everytime this is brought up the hardware is blamed and advised to replace, great if you loaded with cash. The comparison with linux is they maintain support for old hardware. But I guess telling people their card is trash (when it isnt) is easier then rewriting a driver, I cant rewrite as I have no knowledge of coding. here is a quote from the linux 2.6 driver notes. The 8139too driver is based almost entirely on the on the 8139 driver written by Donald Becker. It has a few operational changes, most of which are flawed or pointless. MMIO vs. PIO operation The 8139 is mapped to both PCI I/O and memory space. Using I/O space is traditional on x86 architectures, and most drivers are written to use this mode. However, using the memory space mapping (MMIO) is more efficient for isolated writes since these are stored in a write buffer and the processor can continue execution without waiting for the PCI operation to complete. An added advantage is the processors without native I/O operations avoid extra address space calculations. A problem with using this MMIO mode is that the 8139 has different access alignment restrictions with memory space, and the write buffer potentially changes the ordering of command writes and subsequent memory reads. The 8139too driver attempts to work around the latter problem by doing a read immediately following a register write. Not only does this completely eliminate the advantage of having a write buffer, it doubles the overhead over just using I/O operations! Added Spin-locks The 8139too adds spin-locks. However, as with so many of the 2.3 spin-locks, it added them without considering if they were actually needed. The only code with a potential conflict is when reading and writing MII registers. But the 8139too driver supports only the 8139, which has an internal transceiver that is directly accessed by registers reads. So no spin-lock is needed! The rx_size patch The 8139too driver adds a patch taken from the BSD driver. This patch claims to fix a bug in the Rx ring: when copying a packet into RAM, the length will be 0xfff0. But the BSD bug is an artifact of that driver trying to avoid PCI bus operations by guessing if a packet has arrived, rather than following the documented method of check the RxBufEmpty status. The BSD method is more efficient. Checking the next entry and guessing can potentially save one or two expensive PCI transactions per Rx packet. But (as they found out) it is prone to races and failure. The Linux driver never encounters this problem, but the BSD bug fix was blindly added anyway. I see they taken something from the bsd drivers but are the other optimisations mentioned in the bsd driver? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize
On Tue, Feb 28, 2006 at 01:55:56AM -0500, David Scheidt wrote: The RealTek cards supported by the rl(4) driver are trash. If you want to write a better driver, knock yourself out. I'm sure Bill Paul won't mind. Keep in mind that there are other, better performing NICs available for the about same price. Most RL8139 cards work fine in our company. Most Windows PCs have these cards (slowly replaced by integrated NICs on new motherboards), also some FreeBSD-based routers have these NICs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize
On Sun, Feb 26, 2006 at 11:20:13PM +, Chris wrote: I wonder if anyone has the time to rewrite the realtek driver because whenever anyone posts about rl0 the advice is always ditch the card, I agree that realtek's are the reliant robin class of lan cards but the problems people see do not happen on other operating systems with the same hardware, eg. I have never seen that mtu problem on debian or windows but I have had The RealTek cards supported by the rl(4) driver are trash. If you want to write a better driver, knock yourself out. I'm sure Bill Paul won't mind. Keep in mind that there are other, better performing NICs available for the about same price. I've got one in a machine that dual-boots FreeBSD and XP. The network preformance in XP is no better than on FreeBSD. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rl0 discard oversize
Hi all :-) I have a fbsd 5.4 today while copy a lot files (several Gb) the network saturation...and don't responding of ping :-( in dmesg i see: rl0 discard oversize frame (ether type 4a82 flags 3 len 38118 1514 ok, i tried ifconfig rl0 mtu 1400 but i have the same problem, i tried 1420, 1450, etc. but while copy the network go down 4 several seconds.. if i wait (20/40 seconds) the network come-back normal.. i tried too change my network card but nothing... where is the problem? this is my main server.. and indispensable 4 my work! sorry 4 my bad english...and thanks! Pol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize
Pol Hallen wrote: Hi all :-) I have a fbsd 5.4 today while copy a lot files (several Gb) the network saturation...and don't responding of ping :-( in dmesg i see: rl0 discard oversize frame (ether type 4a82 flags 3 len 38118 1514 [ ... ] where is the problem? With the rl0 hardware, probably. Realtek NICs aren't very good, and I've seen similar reports from other people which were resolved by getting a dc0 or fxp0 NIC instead. this is my main server.. and indispensable 4 my work! sorry 4 my bad english...and thanks! Your english is OK... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0 discard oversize
On 26/02/06, Chuck Swiger [EMAIL PROTECTED] wrote: Pol Hallen wrote: Hi all :-) I have a fbsd 5.4 today while copy a lot files (several Gb) the network saturation...and don't responding of ping :-( in dmesg i see: rl0 discard oversize frame (ether type 4a82 flags 3 len 38118 1514 [ ... ] where is the problem? With the rl0 hardware, probably. Realtek NICs aren't very good, and I've seen similar reports from other people which were resolved by getting a dc0 or fxp0 NIC instead. this is my main server.. and indispensable 4 my work! sorry 4 my bad english...and thanks! Your english is OK... -- -Chuck ___ I wonder if anyone has the time to rewrite the realtek driver because whenever anyone posts about rl0 the advice is always ditch the card, I agree that realtek's are the reliant robin class of lan cards but the problems people see do not happen on other operating systems with the same hardware, eg. I have never seen that mtu problem on debian or windows but I have had it myself on freebsd, I also get poor realtek performance but when I tried linux with the same hardware it was normal. Datacentre's far too often will supply a realtek card with the machine so its not always possible or affordable to simply ditch for a new brand. If someone does have the time to look at the driver it would be great and I would be available for testing as I use realtek cards at home for my lan. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rl0: discard oversize frame
I'm running FreeBSD 5.4-STABLE. At this moment I'm getting all kind of network losses due to the error rl0: discard oversize frame Google showed that a lot of PC suffers form this, but I didn't fine the cure :-( Can anyone help me with a cure? Met vriendelijke groeten Jack Raats ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rl0: discard oversize frame
I also have the errors showing up in my periodic logs but they dont seem to cause me actual network drops. rl0: discard oversize frame (ether type e14c flags 3 len 1722 max 1514) rl0: discard oversize frame (ether type 1 flags 3 len 36860 max 1514) Chris On 5/23/05, Jack Raats [EMAIL PROTECTED] wrote: I'm running FreeBSD 5.4-STABLE. At this moment I'm getting all kind of network losses due to the error rl0: discard oversize frame Google showed that a lot of PC suffers form this, but I didn't fine the cure :-( Can anyone help me with a cure? Met vriendelijke groeten Jack Raats ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd 5.3, rl0: discard oversize frame
Dear Sirs, I have trouble on the my nootbook Compaq Armada e500 (PIII-700, RAM 256 Mb, HDD 5Gb, Internal LAN Intel 100, and second ethernet adapter d-link dfe-690tx (pcmcia card on realtek 8138 chip) The internal lan adapter work fine (fxp0) But pcmcia dfe-690 permanently go down with error message: rl0: discard oversize frame. (more 10 times per day) please help me to find solution of this trouble -- With best regards, German Shikov mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
rl0: discard oversize frame (ether type 4454 flags 3 len 1516 max 1514)
Hi, Im using FreeBSD 5.1 with firewall enabled. I was just wondering why it suddenly had the error messages below. Do you what could have caused this error? and cna anybody suggest any solution how to fix this. Thank you very much in advance... rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1516 max 1514) rl0: discard oversize frame (ether type 55 flags 3 len 1530 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) rl0: discard oversize frame (ether type 4454 flags 3 len 1524 max 1514) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
