RE: Dropped Packets
Hi all, I have done some more investigation and stumbled into something odd. If I use ping currently I am getting about 3% packet loss (it gets worse) but with hping (to the exact same ip) I get no loss? As I understand hping and ping use different methods of sending packets, could this be an indication to where my problem might be (buffering or something) ? Ping -- 290 packets transmitted, 281 packets received, 3% packet loss Hping -- 289 packets tramitted, 289 packets received, 0% packet loss I'm using icmp mode in hping, and sending to the same ip... Thanks again for the help Dave -Original Message- From: Dave Raven [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 6:25 PM To: 'Simon Chang' Cc: 'freebsd-questions@freebsd.org' Subject: RE: Dropped Packets Hi, Its interesting you'd say that I'd virtually ruled it out given that it takes over a day to start? What I do see sometimes is a message warning me that its limiting open port RST responses - the unit is under a reasonable amount of load though (but not overloaded). The strange thing is that its open port (not closed). Even if I up the limit though (the messages do stop) it doesn't stop the dropping... I've rebooted it recently, but here is the dmesg -- CPU: Intel(R) Xeon(R) CPU5150 @ 2.66GHz (2666.68-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 3489005568 (3407232K bytes) avail memory = 3395510272 (3315928K bytes) Preloaded elf kernel kernel at 0xc0378000. Preloaded elf module splash_bmp.ko at 0xc037809c. Preloaded splash_image_data /boot/optec.bmp at 0xc0378140. Preloaded elf module if_em.ko at 0xc037818c. Preloaded elf module if_silbpi.ko at 0xc037822c. Preloaded elf module hptmv.ko at 0xc03782d0. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 31 entries at 0xc00fddd0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib8: PCI to PCI bridge (vendor=8086 device=25f7) irq 0 at device 2.0 on pci0 pci1: PCI bus on pcib8 pcib9: PCI to PCI bridge (vendor=8086 device=3500) irq 11 at device 0.0 on pci1 pci2: PCI bus on pcib9 pcib10: PCI to PCI bridge (vendor=8086 device=3510) irq 11 at device 0.0 on pci2 pci3: PCI bus on pcib10 pcib11: PCI to PCI bridge (vendor=8086 device=0329) at device 0.0 on pci3 pci4: PCI bus on pcib11 pcib12: PCI to PCI bridge (vendor=8086 device=032a) at device 0.2 on pci3 pci5: PCI bus on pcib12 hptmv0: RocketRAID 182x SATA Controller mem 0xd800-0xd807 irq 11 at device 1.0 on pci5 RocketRAID 182x SATA Controller driver Version 1.12 RR182x [0,0]: channel started successfully RR182x [0,1]: channel started successfully RR182x [0,2]: channel started successfully RR182x [0,3]: channel started successfully RR182x [0,4]: channel started successfully RR182x [0,5]: channel started successfully RR182x [0,6]: channel started successfully RR182x [0,7]: channel started successfully RR182x: RAID5 write-back enabled pcib13: PCI to PCI bridge (vendor=8086 device=3518) irq 5 at device 2.0 on pci2 pci6: PCI bus on pcib13 pci6: unknown card (vendor=0x8086, dev=0x1096) at 0.0 irq 5 pci6: unknown card (vendor=0x8086, dev=0x1096) at 0.1 irq 10 pcib14: PCI to PCI bridge (vendor=8086 device=350c) at device 0.3 on pci1 pci7: PCI bus on pcib14 silbpi0: PXG2BPIG port 0x3000-0x303f mem 0xd820-0xd821 irq 11 at device 1.0 on pci7 silbpi0: Speed:N/A Duplex:N/A silbpi1: PXG2BPIG port 0x3040-0x307f mem 0xd822-0xd823 irq 7 at device 1.1 on pci7 silbpi1: Speed:N/A Duplex:N/A pcib15: PCI to PCI bridge (vendor=8086 device=25f8) irq 0 at device 4.0 on pci0 pci8: PCI bus on pcib15 pcib16: PCI to PCI bridge (vendor=8086 device=25f9) irq 0 at device 6.0 on pci0 pci9: PCI bus on pcib16 pcib17: PCI to PCI bridge (vendor=8086 device=2690) irq 7 at device 28.0 on pci0 pci10: PCI bus on pcib17 pcib18: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci11: PCI bus on pcib18 pci11: ATI model 515e graphics accelerator at 1.0 irq 5 isab0: PCI to ISA bridge (vendor=8086 device=2670) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Generic PCI ATA controller port 0x1800-0x180f,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: unknown card (vendor=0x8086, dev=0x269b) at 31.3 irq 10 pcib1: Host to PCI bridge on motherboard pci12: PCI bus on pcib1 pcib2: Host to PCI bridge on motherboard pci13: PCI bus on pcib2 pcib3: Host to PCI bridge on motherboard pci14: PCI bus on pcib3 pcib4: Host to PCI bridge on motherboard pci15: PCI bus on pcib4 pcib5: Host to PCI bridge on motherboard pci16: PCI bus on pcib5 pcib6: Host to PCI bridge on motherboard pci17: PCI bus on pcib6 pcib7: Host to PCI bridge
Dropped Packets
Hi all, I have a FreeBSD 4.11 (I know its outdated but I don't have an option) box which is behaving very weirdly. After about a day and a half it starts to drop packets - about 6-10% of pings at least, and tcp traffic becomes unreliable etc. I have swapped out the network cards, the cables etc and I don't have any mbuf problems and all seems fine. For the first day the box works fine - pinging, doing tcp traffic etc; and then suddenly it just stops. Rebooting brings it all back to normal. Any ideas what could be causing this, and how I could go about diagnosing it? As far as I know there are no known bugs for this. I'm using the em driver, but not with SMP. There are no errors on the interface, and the em debug_info and stats sysctl's don't show any problems - there is no indication on the box itself that its dropping packets.. My thinking is that it must be box specific as a reboot solves the problem? Thanks in advance Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dropped Packets
Hardware issues come to mind. Do you have a dmesg? SC On Sun, Feb 24, 2008 at 9:27 AM, Dave Raven [EMAIL PROTECTED] wrote: Hi all, I have a FreeBSD 4.11 (I know its outdated but I don't have an option) box which is behaving very weirdly. After about a day and a half it starts to drop packets - about 6-10% of pings at least, and tcp traffic becomes unreliable etc. I have swapped out the network cards, the cables etc and I don't have any mbuf problems and all seems fine. For the first day the box works fine - pinging, doing tcp traffic etc; and then suddenly it just stops. Rebooting brings it all back to normal. Any ideas what could be causing this, and how I could go about diagnosing it? As far as I know there are no known bugs for this. I'm using the em driver, but not with SMP. There are no errors on the interface, and the em debug_info and stats sysctl's don't show any problems - there is no indication on the box itself that its dropping packets.. My thinking is that it must be box specific as a reboot solves the problem? Thanks in advance Dave ___ 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: Dropped Packets
ad0: 76319MB ST380215A [155061/16/63] at ata0-master BIOSDMA da0 at hptmv0 bus 0 target 0 lun 0 da0: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da0: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da1 at hptmv0 bus 0 target 1 lun 0 da1: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da1: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da2 at hptmv0 bus 0 target 2 lun 0 da2: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da2: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da3 at hptmv0 bus 0 target 3 lun 0 da3: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da3: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da4 at hptmv0 bus 0 target 4 lun 0 da4: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da4: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da5 at hptmv0 bus 0 target 5 lun 0 da5: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da5: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da6 at hptmv0 bus 0 target 6 lun 0 da6: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da6: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) da7 at hptmv0 bus 0 target 7 lun 0 da7: ST380815 AS 3.AA Fixed Direct Access SCSI-0 device da7: 76319MB (156301477 512 byte sectors: 255H 63S/T 9729C) Mounting root from ufs:/dev/ad0s1a Thanks for the help Dave -Original Message- From: Simon Chang [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 5:57 PM To: Dave Raven Cc: freebsd-questions@freebsd.org Subject: Re: Dropped Packets Hardware issues come to mind. Do you have a dmesg? SC On Sun, Feb 24, 2008 at 9:27 AM, Dave Raven [EMAIL PROTECTED] wrote: Hi all, I have a FreeBSD 4.11 (I know its outdated but I don't have an option) box which is behaving very weirdly. After about a day and a half it starts to drop packets - about 6-10% of pings at least, and tcp traffic becomes unreliable etc. I have swapped out the network cards, the cables etc and I don't have any mbuf problems and all seems fine. For the first day the box works fine - pinging, doing tcp traffic etc; and then suddenly it just stops. Rebooting brings it all back to normal. Any ideas what could be causing this, and how I could go about diagnosing it? As far as I know there are no known bugs for this. I'm using the em driver, but not with SMP. There are no errors on the interface, and the em debug_info and stats sysctl's don't show any problems - there is no indication on the box itself that its dropping packets.. My thinking is that it must be box specific as a reboot solves the problem? Thanks in advance Dave ___ 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]
