From owner-freebsd-emulation@FreeBSD.ORG Wed Jun 10 13:21:35 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C344C106568B; Wed, 10 Jun 2009 13:21:35 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9CA838FC26; Wed, 10 Jun 2009 13:21:34 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA06970; Wed, 10 Jun 2009 16:21:31 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4A2FB35A.8070300@icyb.net.ua> Date: Wed, 10 Jun 2009 16:21:30 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: ajtiM References: <200906071217.46779.lumiwa@gmail.com> In-Reply-To: <200906071217.46779.lumiwa@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, freebsd-emulation@freebsd.org, re@freebsd.org, Chagin Dmitry Subject: Re: skype-out calls disconnect after 5 minute X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2009 13:21:36 -0000 on 07/06/2009 20:17 ajtiM said the following: > My system: FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 > root@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > Skype-out calls disconnect after about 5 minutes. I red that was problem with > beta or pre release but looks like that is the problem here still. Version of > Skype is 2.9.9.72. > Do I need to put kern.hz=100 in loader.conf, please? > > Thanks in advace, I am not entirely sure but I think that the behavior that you see was caused by r190893 (on Apr 10) and was fixed by r192987 (on May 28). I think that your best bet is to upgrade to stable/7 that includes the aforementioned commit. I have been experiencing the same problem myself and tracked it to linux_times, but very fortunately Dmitry committed the proper fix before I could finish my investigation. I think that this may be a good candidate for 7.2 errata. -- Andriy Gapon