bsdsar Interface Errors
I have 2 interfaces on the machine and only one is showing these errors. BTW, that interface is in promiscuous mode, the other is not. bsdsar -i shows In Errors on the order of 0.05% bsdsar -I shows In Errs/s on the order of 0.05% I am on: FreeBSD 6.2-PRERELEASE bsdsar v1.10 - Eric Anderson Questions: - Are these interface errors or errors the interface is seeing on the wire? - regardless of where the errors are generated, do I need to worry about them since they are only 0.05% of the incoming packets? - Why is there NO information about this utility on the net? -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rsync and trailing '/'
From: Noah [EMAIL PROTECTED] Subject: rsync and trailing '/' To: User Questions freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed rsync version 2.6.9 protocol version 29 I am running rsync, and I wonder if having the trailing '/' at the end of the directory is proper configuration? --- snip --- /usr/local/bin/rsync -avz -e ssh [EMAIL PROTECTED]:/var/cron/ /var/cron/ --- snip --- Cheers, Noah Whoa, Noah duuude! That trailing slash makes mondo difference. Use with caution FBSD dudes! -- Yudhvir Singh Sidhu Mars or Bust ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Decompressing Emulecompressed Packets with Hardware
I am losing kernel and threaded packets when processing emulecompressed p2p packets. This takes up a lot of the CPU and I am wondering if the decompression, and other floating point processing, could be better performed by a card such as a GPU, DSP, or a sound or video graphics cards? I have tried Intel configurations such as 32 bit, 64 bit, dual cpu, dual core, SCSI, SATA - they all bog down when these packets have to be processed. I am running a modified FBSD 6.1 on UFS 1. I guess I am hoping some one can point me in a direction to do more research. I am not looking to re-write my code, I am looking to see if there I can introduce hardware which can take over these math intensive threads. -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Managed Switch Implementation
Is there anyone who has experience in developing port mirroring in FBSD? I am trying to combine 2 devices, a managed switch with a modified firewall. This device wants to see traffic from, say 3 ports. So, 3 ports in and all they do is mirror to 1 port internally. -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Memory test
I need to checkout memory on a remote machine. I see there is memtest and memtest86 out there. Which one is appropriate for my situation?: CPU is a dual cpu, dual core SMP Intel Xeon. Can I run either program while the machine is performing other tasks?** -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot Load FreeBSD 6.2 64 bit and maybe other versions as well
An update for some who may care. I tried loading Live Linux distros: Puppy, DSL and STD. They load fine but don't see a network interface. Also installed Fedora 5 Linux Distro and same - no ethernet interface seen. It has been a while but I recall that Windows XP pro will not boot. Anybody have any ideas on what to try next? I am pretty much spent. This is a new evaluation box and so I have no problems sending it back to the SuperMicro VAR. I want to figure this thing out just for the challenge of it. Know what I mean? Yudhvir = On 12/11/06, Y Sidhu [EMAIL PROTECTED] wrote: I am a newbie and have gone though past posts and have been looking at the last couple of weeks of posts go by. I have not seen anything similar to my problem. I cannot load an OS except under ACPI-Disabled. I can boot into safe mode, but cannot configure a working network interface. Therefore, I cannot send in a dmesg output. Here is some data I have gathered: Details a. SuperMicro X7DBR-8+ / X7DBR-I+ b. Intel 3.2 GHz Xeon dual core dual cpu, K8 class cpu c. BIOS - Phoenix (just upgraded to 1.2A from 1.1C) The upgrade has had no affect on this problem as far as I can tell. d. Dual Ethernet - Intel Pro/1000 Network Connection Version 6.2.9. em0 is IRQ 5 at device 0.0 on pci4. em1 is IRQ 11 at device 0.1 on pci4. Also, when I am booted in safe mode, in dmesg, there is an entry em IRQ 10 at device 2.0 on pci5. e. SCSI - Adaptec version 4.3. AIC 7902 Ultra 320, PCI-X ID=7 f. One 73 GB Seagate Cheetah 10K.7 SCSI hard drive, Model ST3207LC. I have tested this and another drive out without any media errors. The Adaptec adapter sees the drive and capacity fine. g. When I try to boot normally, the messages scroll by and the system freezes at: waiting 5 seconds for SCSI devices to settle h. When I disable ACPI either under the BIOS's settings or select Disable ACPI when loading FreeBSD, the system loads but I cannot get the ethernet interface to come up. ifconfig shows all the right values. I have also used route delete default and route add default ip of gateway - to no avail. There is a message which pops up saying em0: watchdog timeout - resetting Looking into dmesg output, I see: em0 link state changed to UP and em0 link state DOWN repeat over and over again. i. 1 GB ram and have tested it with memtest 86 without any errors. My Gut a. Something is causing a good old fashioned IRQ conflict. I have 1 drive and 1 cdrom on this machine. b. The SCSI ACPI79xx driver is not there or not loading Hoping I am looking for a nudge in the right direction. -- Yudhvir Singh Sidhu -- Yudhvir Singh Sidhu 408 375 3134 cell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cannot Load FreeBSD 6.2 64 bit and maybe other versions as well
I am a newbie and have gone though past posts and have been looking at the last couple of weeks of posts go by. I have not seen anything similar to my problem. I cannot load an OS except under ACPI-Disabled. I can boot into safe mode, but cannot configure a working network interface. Therefore, I cannot send in a dmesg output. Here is some data I have gathered: Details a. SuperMicro X7DBR-8+ / X7DBR-I+ b. Intel 3.2 GHz Xeon dual core dual cpu, K8 class cpu c. BIOS - Phoenix (just upgraded to 1.2A from 1.1C) The upgrade has had no affect on this problem as far as I can tell. d. Dual Ethernet - Intel Pro/1000 Network Connection Version 6.2.9. em0 is IRQ 5 at device 0.0 on pci4. em1 is IRQ 11 at device 0.1 on pci4. Also, when I am booted in safe mode, in dmesg, there is an entry em IRQ 10 at device 2.0 on pci5. e. SCSI - Adaptec version 4.3. AIC 7902 Ultra 320, PCI-X ID=7 f. One 73 GB Seagate Cheetah 10K.7 SCSI hard drive, Model ST3207LC. I have tested this and another drive out without any media errors. The Adaptec adapter sees the drive and capacity fine. g. When I try to boot normally, the messages scroll by and the system freezes at: waiting 5 seconds for SCSI devices to settle h. When I disable ACPI either under the BIOS's settings or select Disable ACPI when loading FreeBSD, the system loads but I cannot get the ethernet interface to come up. ifconfig shows all the right values. I have also used route delete default and route add default ip of gateway - to no avail. There is a message which pops up saying em0: watchdog timeout - resetting Looking into dmesg output, I see: em0 link state changed to UP and em0 link state DOWN repeat over and over again. i. 1 GB ram and have tested it with memtest 86 without any errors. My Gut a. Something is causing a good old fashioned IRQ conflict. I have 1 drive and 1 cdrom on this machine. b. The SCSI ACPI79xx driver is not there or not loading Hoping I am looking for a nudge in the right direction. -- Yudhvir Singh Sidhu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
