Re: re(4) problem

From: Pyun YongHyeon <pyunyh_at_gmail.com>
Date: Mon, 10 Mar 2008 10:48:59 +0900
On Sat, Mar 08, 2008 at 04:36:55PM -0300, JoaoBR wrote:
 > On Saturday 08 March 2008 09:46:13 Abdullah Ibn Hamad Al-Marri wrote:
 > > ----- Original Message ----
 > >
 > > > From: Daniel Gerzo <danger_at_FreeBSD.org>
 > > > To: Pyun YongHyeon <pyunyh_at_gmail.com>
 > > > Cc: Daniel Gerzo <danger_at_FreeBSD.org>; current_at_FreeBSD.org;
 > > > yongari_at_FreeBSD.org Sent: Saturday, March 8, 2008 2:11:03 AM
 > > > Subject: Re[2]: re(4) problem
 > > >
 > > > Hello Pyun,
 > > >
 > > > Friday, March 7, 2008, 5:38:15 AM, you wrote:
 > > > > I guess your issue is not related with bus_dma fixes but improper
 > > > > handling of link state. Try attached patch and let me know how it
 > > > > goes.
 > > >
 > > > The attached patch didn't help, the box is again in the same status.
 > > > Can I provide you with some more detailed debugging info, or do you
 > > > have some other ideas what could be fixed?
 > > >
 > > > I could probably manage a remote access to that box, but no remote
 > > > console is available, and I don't know exactly how to trigger this
 > > > scenario, but I think it depends on the amount of traffic being sent
 > > > over the device.
 > > >
 > > > --
 > > > Best regards,
 > > >  Daniel                            mailto:danger_at_FreeBSD.org
 > >
 > > I'm using RELENG_7 too with pf, and I face the same problem for my mail
 > > server, which only gets new messages, and doesn't send anything since the
 > > outgoing mail runs on another servers.
 > >
 > > To get it working smoothly I have to reboot it every 3 days, otherwise I'll
 > > get packet loss even when I ping it from another server in the same lan.
 > >
 > 
 > 
 > I get actually around the problem by setting  
 > 
 > ifconfig re0 ... -txcsum -rxcsum -lro -tso
 > 
 > which still shows the problem from time to time but seems that additional
 > 
 > sysctl net.inet.tcp.tso=0
 > 
 > seems to help, I am over a week running fine with it
 > 

It seems that you've already disabled TSO on re(4) interface.
Disabling system-wise TSO wouldn't affect re(4)'s TSO operation
anymore. If it helps re(4) stability it would indicate other
problems in kernel.

-- 
Regards,
Pyun YongHyeon
Received on Mon Mar 10 2008 - 00:49:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:28 UTC