UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Peter Kirk
Hi there, first of, this is my first posting to this list, hopfully it is the right place, if not please direct me, I was not being thick intentionally. I have a fresh installation of FreeBSD7 on x86, with no big changes to the system. Situation: Two PCs, one running linux and my own programs

Re: UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Andrey V. Elsukov
Peter Kirk wrote: first of, this is my first posting to this list, hopfully it is the right place, if not please direct me, I was not being thick intentionally. I have a fresh installation of FreeBSD7 on x86, with no big changes to the system. Can you show `ifconfig -u` output? -- WBR, Andr

Re: UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Peter Kirk
On Friday 20 June 2008 11:10:06 Andrey V. Elsukov wrote: > > I have a fresh installation of FreeBSD7 on x86, with no big changes to > > the system. > > Can you show `ifconfig -u` output? re0: flags=8843 metric 0 mtu 1500 options=9b ether 00:19:66:59:85:7f inet6 fe80::219:66

Re: UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Andrey V. Elsukov
Peter Kirk wrote: On Friday 20 June 2008 11:10:06 Andrey V. Elsukov wrote: I have a fresh installation of FreeBSD7 on x86, with no big changes to the system. Can you show `ifconfig -u` output? re0: flags=8843 metric 0 mtu 1500 options=9b It's problem in re(4) driver. Try to use `ifc

Re: UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Peter Kirk
On Friday 20 June 2008 11:38:16 Andrey V. Elsukov wrote: > Peter Kirk wrote: > >> Can you show `ifconfig -u` output? > > > > re0: flags=8843 metric 0 mtu 1500 > > options=9b > > It's problem in re(4) driver. > Try to use `ifconfig re0 -rxcsum -txcsum`. You can add these > parameters to your

[Queueing Packets with ALTQ on Gigabit Fiber Optic and Gigabit Ethernet]

2008-06-20 Thread Diego Salvador
Hi, Is there any difference in handling packet queues with ALTQ if the network card is a Gigabit fiber network interface and a Gigabit Ethernet network interface with the same driver? For example (em) driver for Intel-based cards. I'm currently having a system configured with FreeBSD-6.2 RELEAS

Re: Network Instability when upgrading to 4GB of RAM

2008-06-20 Thread Alexander Sack
Pyun YongHyeon wrote: > > On Thu, Jun 19, 2008 at 11:41:32AM -0700, Alexander Sack wrote: > > > > > > > > Paul Haddad wrote: > > > > > > All, > > > As a follow up to myself I installed an Intel PCIe NIC and disabled > the on > > > board RTL based one and all my problems went away.

Re: kern/114714: commit references a PR

2008-06-20 Thread dfilter service
The following reply was made to PR kern/114714; it has been noted by GNATS. From: [EMAIL PROTECTED] (dfilter service) To: [EMAIL PROTECTED] Cc: Subject: Re: kern/114714: commit references a PR Date: Fri, 20 Jun 2008 17:30:14 + (UTC) thompsa 2008-06-20 17:26:34 UTC FreeBSD src repo

Re: kern/123961: [vr] [patch] Allow vr interface to handle vlans

2008-06-20 Thread thompsa
Synopsis: [vr] [patch] Allow vr interface to handle vlans State-Changed-From-To: open->patched State-Changed-By: thompsa State-Changed-When: Fri Jun 20 17:47:20 UTC 2008 State-Changed-Why: This has been handled by the bus_dma megaupdate to vr(4), thanks to Pyun. Not merged to RELENG_6 yet. http:

Re: Seeking help understanding my "emX: watchdog timeout" messages

2008-06-20 Thread Rudy
Jack Vogel wrote: Watchdog reset is an indication that the TX completion did not happen within a reasonable time, it can the symptom of a variety of problems. You list a bunch of settings for polling, is this interface in POLLING mode? Yes, DEVICE_POLLING is in the kernel and kern.polling.ena

Re: Seeking help understanding my "emX: watchdog timeout" messages

2008-06-20 Thread Jack Vogel
On the 573 get me an eeprom dump: sysctl dev.em.4.debug=2 If you have having TX timeouts using polling, perhaps your system is so busy that its not running the cleanup routine in time, can you switch and run the interface in non-polled, in fact if possible using MSI?? Jack On Fri, Jun 20, 2008

Re: Seeking help understanding my "emX: watchdog timeout" messages

2008-06-20 Thread Support (Rudy)
Jack Vogel wrote: On the 573 get me an eeprom dump: sysctl dev.em.4.debug=2 here are the dumps: em4: Jun 20 16:30:01 mango kernel: Jun 20 16:30:01 mango kernel: Interface EEPROM Dump: Jun 20 16:30:01 mango kernel: Offset Jun 20 16:30:01 mango kernel: 0x 3000 6748 5014 0d30 f746 00f4

Re: Seeking help understanding my "emX: watchdog timeout" messages

2008-06-20 Thread Support (Rudy)
Jack Vogel wrote: ... can you switch and run the interface in non-polled, in fact if possible using MSI?? Do I have to do anything special for MSI? I see this in my dmesg: # dmesg | grep MSI em0: Using MSI interrupt em1: Using MSI interrupt em2: Using MSI interrupt em3: Using MSI interrupt e

Re: Seeking help understanding my "emX: watchdog timeout" messages

2008-06-20 Thread Jack Vogel
On Fri, Jun 20, 2008 at 4:48 PM, Support (Rudy) <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote: >> >> ... can you switch and run the interface in non-polled, in fact if >> possible using >> MSI?? > > Do I have to do anything special for MSI? I see this in my dmesg: > > # dmesg | grep MSI > em0: Usi

Re: UDP checksum invalid on FreeBSD7/x86

2008-06-20 Thread Pyun YongHyeon
On Fri, Jun 20, 2008 at 11:54:55AM +0200, Peter Kirk wrote: > On Friday 20 June 2008 11:38:16 Andrey V. Elsukov wrote: > > Peter Kirk wrote: > > >> Can you show `ifconfig -u` output? > > > > > > re0: flags=8843 metric 0 mtu 1500 > > > options=9b > > > > It's problem in re(4) driver.