Re: dc still reporting collisions
On Sat, 15 Nov 2003, Jos Backus wrote: If its a real hub, hubs aren't full duplex. Yeah, I know (believe it or not, but my job description says Network Engineer :-). I don't make assumptions about titles and knowledge levels. :-) If its a switch, the switch and PC might not have negoatiated full duplex properly. Try unplug/replug the cable, or switch to autoselect. Thanks for the advice, but this setup has been working unchanged for years now. All that's really changed is FreeBSD on this machine. It could be broken hardware though. I'm going to try booting 4.9-RELEASE and see if I can get FTP to work (5.1-RELEASE just hangs during root mount). Just because it's been working forever doesn't mean it can't fail. Ever heard of power surges? Static discharge? I've seen a tx on a Compaq motherboard go kaput with no intervention whatsoever. It happens. Thankfully collisions are fairly deterministic. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Mon, Nov 17, 2003 at 09:14:05AM -0800, Doug White wrote: On Sat, 15 Nov 2003, Jos Backus wrote: Just because it's been working forever doesn't mean it can't fail. Of course. Ever heard of power surges? Static discharge? I've seen a tx on a Compaq motherboard go kaput with no intervention whatsoever. It happens. Yeah (I have ESD equipment at home, for fiddling with mobo's etc.). But it turns out I lied, because I did change something a while back: I added a new soundcard to my wife's PC. As it turns out, after I moved it to a different PCI slot the problem went away. Whoever designed PCI ought to be shot :-) My apologies for wasting everybody's time. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 12:47:45PM -0600, Dan Nelson wrote: Are you sure your kernel, /usr/include/sys, and netstat are all up-to-date? I know mine are. What's odd in my case is that FreeBSD - Windows works but generates many collisions (11 MB file xfer results in roughly 8000 collisions) but Windows - FreeBSD doesn't work at all. It does smell like broken hardware but nothing has changed in this setup in a while. Hm. Guess I'll have to run that test with 4.9. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 11:44:35PM -0800, Jos Backus wrote: On Sat, Nov 15, 2003 at 12:47:45PM -0600, Dan Nelson wrote: Are you sure your kernel, /usr/include/sys, and netstat are all up-to-date? I know mine are. What's odd in my case is that FreeBSD - Windows works but generates many collisions (11 MB file xfer results in roughly 8000 collisions) but Windows - FreeBSD doesn't work at all. It does smell like broken hardware but nothing has changed in this setup in a while. Hm. Guess I'll have to run that test with 4.9. I tried this today with 4.9, and the problem is still there (Windows - FreeBSD: 6 KB/sec, FreeBSD - Windows 330 KB/sec). At this point I'm assuming some kind of hardware-related problem. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote: The dc(4) driver is still reporting collisions on 100 Mbit full-duplex links: [snip] netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 Link#1 00:00:e8:89:b9:6626463 026737 13253 225301 Fwiw, I'm seeing the same with tx(4): lizzy:~% ifconfig tx0 tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 inet 10.0.0.10 netmask 0x broadcast 10.0.0.10 ether 00:e0:29:09:e4:1a media: Ethernet autoselect (10baseT/UTP) status: active lizzy:~% netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253 tx01500 10/24 lizzy 159162 - 122841 - - tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - - lo0 16384 Link#25347 0 5347 0 0 lo0 16384 your-net localhost 442 - 442 - - lizzy:~% It's gotten so bad that I can no longer transfer files from a Windows system to this FreeBSD system (both are on the same 10BaseT hub). I only rarely used to see collisions before, and filetransfers have always worked just fine. Last time I know for sure this worked was October 17th. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
lizzy:~% ifconfig tx0
tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
inet 10.0.0.10 netmask 0x broadcast 10.0.0.10
ether 00:e0:29:09:e4:1a
media: Ethernet autoselect (10baseT/UTP)
status: active
lizzy:~% netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253
tx01500 10/24 lizzy 159162 - 122841 - -
tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - -
lo0 16384 Link#25347 0 5347 0 0
lo0 16384 your-net localhost 442 - 442 - -
lizzy:~%
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Seishi Hiragushi [EMAIL PROTECTED] reported this 1.5 months ago:
Message-Id: [EMAIL PROTECTED]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
Andy Farkas replies to himself:
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Ack! I can't count. Or my numerical recognition system is failing
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
dc01500 Link#1 00:00:e8:89:b9:6626463 026737 13253 225301
Ipkts + Opkts collisions :(
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
In the last episode (Nov 15), Andy Farkas said: The dc(4) driver is still reporting collisions on 100 Mbit full-duplex links: ifconfig -a dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 172.22.2.12 netmask 0xfff0 broadcast 172.22.2.15 ether 00:00:e8:89:b9:66 media: Ethernet autoselect (100baseTX full-duplex) status: active netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 Link#1 00:00:e8:89:b9:6626463 026737 13253 225301 dc01500 172.22.2/28 team226044 -26636 - - lo0 16384 Link#2 73 0 73 0 0 lo0 16384 your-net localhost 73 - 73 - - Are you sure your kernel, /usr/include/sys, and netstat are all up-to-date? -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Fri, Nov 14, 2003 at 11:14:36PM -0800, Jos Backus wrote: On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote: The dc(4) driver is still reporting collisions on 100 Mbit full-duplex links: [snip] netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll dc01500 Link#1 00:00:e8:89:b9:6626463 026737 13253 225301 Fwiw, I'm seeing the same with tx(4): lizzy:~% ifconfig tx0 tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 inet 10.0.0.10 netmask 0x broadcast 10.0.0.10 ether 00:e0:29:09:e4:1a media: Ethernet autoselect (10baseT/UTP) status: active lizzy:~% netstat -i NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253 tx01500 10/24 lizzy 159162 - 122841 - - tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - - lo0 16384 Link#25347 0 5347 0 0 lo0 16384 your-net localhost 442 - 442 - - lizzy:~% It's gotten so bad that I can no longer transfer files from a Windows system to this FreeBSD system (both are on the same 10BaseT hub). I only rarely used to see collisions before, and filetransfers have always worked just fine. Last time I know for sure this worked was October 17th. These probably are actual collisions though. The OP's point is that collisions are supposed to be impossible on a full duplex link, whereas in your situation they aren't. Ceri -- pgp0.pgp Description: PGP signature
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was commenting on the (relatively) high collision count I'm
seeing. This is a hub (DSL router) with 2 PC's on it. I have never seen this
many collisions happening before. Plus I can no longer transfer files from the
Windows system to the FreeBSD system (even using FTP), something that worked
flawlessly at least until October 17th. So something is broken. You think it
could be hardware?
Thanks,
Jos
lizzy:~% ifconfig tx0
tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
inet 10.0.0.10 netmask 0x broadcast 10.0.0.10
ether 00:e0:29:09:e4:1a
media: Ethernet autoselect (10baseT/UTP)
status: active
lizzy:~% netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253
tx01500 10/24 lizzy 159162 - 122841 - -
tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - -
lo0 16384 Link#25347 0 5347 0 0
lo0 16384 your-net localhost 442 - 442 - -
lizzy:~%
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Seishi Hiragushi [EMAIL PROTECTED] reported this 1.5 months ago:
Message-Id: [EMAIL PROTECTED]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
!DSPAM:3fb5d46c649171139613270!
--
Jos Backus _/ _/_/_/ Sunnyvale, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/_/
jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer'
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, 15 Nov 2003, Jos Backus wrote:
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was commenting on the (relatively) high collision count I'm
seeing. This is a hub (DSL router) with 2 PC's on it. I have never seen this
many collisions happening before. Plus I can no longer transfer files from the
Windows system to the FreeBSD system (even using FTP), something that worked
flawlessly at least until October 17th. So something is broken. You think it
could be hardware?
If its a real hub, hubs aren't full duplex.
If its a switch, the switch and PC might not have negoatiated full duplex
properly. Try unplug/replug the cable, or switch to autoselect.
Thanks,
Jos
lizzy:~% ifconfig tx0
tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
inet 10.0.0.10 netmask 0x broadcast 10.0.0.10
ether 00:e0:29:09:e4:1a
media: Ethernet autoselect (10baseT/UTP)
status: active
lizzy:~% netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253
tx01500 10/24 lizzy 159162 - 122841 - -
tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - -
lo0 16384 Link#25347 0 5347 0 0
lo0 16384 your-net localhost 442 - 442 - -
lizzy:~%
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Seishi Hiragushi [EMAIL PROTECTED] reported this 1.5 months ago:
Message-Id: [EMAIL PROTECTED]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
!DSPAM:3fb5d46c649171139613270!
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 03:09:27PM -0800, Doug White wrote:
On Sat, 15 Nov 2003, Jos Backus wrote:
On Sat, Nov 15, 2003 at 05:23:08PM +1000, Andy Farkas wrote:
Jos Backus wrote:
Fwiw, I'm seeing the same with tx(4):
Looks like a different problem.
Probably. I was commenting on the (relatively) high collision count I'm
seeing. This is a hub (DSL router) with 2 PC's on it. I have never seen this
many collisions happening before. Plus I can no longer transfer files from the
Windows system to the FreeBSD system (even using FTP), something that worked
flawlessly at least until October 17th. So something is broken. You think it
could be hardware?
If its a real hub, hubs aren't full duplex.
Yeah, I know (believe it or not, but my job description says Network
Engineer :-).
If its a switch, the switch and PC might not have negoatiated full duplex
properly. Try unplug/replug the cable, or switch to autoselect.
Thanks for the advice, but this setup has been working unchanged for years
now. All that's really changed is FreeBSD on this machine. It could be broken
hardware though. I'm going to try booting 4.9-RELEASE and see if I can get FTP
to work (5.1-RELEASE just hangs during root mount).
Cheers,
Jos
Thanks,
Jos
lizzy:~% ifconfig tx0
tx0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255
inet 10.0.0.10 netmask 0x broadcast 10.0.0.10
ether 00:e0:29:09:e4:1a
media: Ethernet autoselect (10baseT/UTP)
status: active
lizzy:~% netstat -i
NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll
tx01500 Link#1 00:e0:29:09:e4:1a 154423 1 118093 0 253
tx01500 10/24 lizzy 159162 - 122841 - -
tx01500 10.0.0.10/32 lizzy-proxy 28 - 28 - -
lo0 16384 Link#25347 0 5347 0 0
lo0 16384 your-net localhost 442 - 442 - -
lizzy:~%
The dc(4) driver currently has an almost 1:1 ratio of packets:collisions.
Your tx0 is quite low.
Seishi Hiragushi [EMAIL PROTECTED] reported this 1.5 months ago:
Message-Id: [EMAIL PROTECTED]
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
--
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
--
Jos Backus _/ _/_/_/ Sunnyvale, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/_/
jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer'
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dc still reporting collisions
On Sat, Nov 15, 2003 at 08:27:44PM +, Ceri Davies wrote: These probably are actual collisions though. The OP's point is that collisions are supposed to be impossible on a full duplex link, whereas in your situation they aren't. The collision mechanism is used for flow control on full-duplex links. A very high collision rate would normally indicate a half/full duplex mismatch. A low collision rate would normally indicate that the switch can't handle the load and is throttling back your system. (Other options are broken NICs and/or cables). Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
