From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 10:08:38 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD38B16A404 for ; Fri, 13 Jul 2007 10:08:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.234]) by mx1.freebsd.org (Postfix) with ESMTP id CAF0B13C441 for ; Fri, 13 Jul 2007 10:08:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so365066nzf for ; Fri, 13 Jul 2007 03:08:37 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=eta7gQXQkAqn5Cl8IFjPsF1cBxMeMlxnskMp/2YCJAHNETC5u6Hn4kmmdmU0+qQlxWevuKvps2gmXEi9rbbAmPt3tXbStcSoIgwbAi+GYiIMbiguM34cRoL++uKUTJct+akitkyo4Nz+01ISdHGaYWjyyCYfRc+2Y1b9sjUDJ4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=SO+YcEw/LPaMbqN7XHjM17JsR5Ozhvr1cHx6fYZMhfmNDYBglMLyLCpgsjKVIGPgITMkxmijewjmKpddZVqQWaMcStn8A/1TZuzu/0UWJTlEku0P3Mm+A0AUGXtr4/bRTVA43CNXAJXob3sLMNt/cNBIXQwuT578GIt+R8SH/XI= Received: by 10.115.95.1 with SMTP id x1mr1486520wal.1184321316512; Fri, 13 Jul 2007 03:08:36 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id j6sm36199926wah.2007.07.13.03.08.34 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 Jul 2007 03:08:35 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l6DA8Uw2019931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jul 2007 19:08:30 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l6DA8TuH019930; Fri, 13 Jul 2007 19:08:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 13 Jul 2007 19:08:29 +0900 From: Pyun YongHyeon To: "Li-Lun Wang (Leland Wang)" Message-ID: <20070713100829.GC17801@cdnetworks.co.kr> References: <20070713084325.GA47351@Athena.infor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070713084325.GA47351@Athena.infor.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: threadlock and msk watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2007 10:08:38 -0000 On Fri, Jul 13, 2007 at 04:43:25PM +0800, Li-Lun Wang (Leland Wang) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > After making world a couple of days ago, my msk(4) became very > unstable. Under moderate network load, the interface hung and I > received > > kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering > > at least once every several minutes and > > kernel: msk0: Rx FIFO overrun! > > occasionally. > > It was so annoying that I took the trouble of binary searching the > kernel version to find the one destabilized my msk(4). > > The outcome of the search turned out te be strange. Instead of > finding a date after which msk(4) became so very unstable, it *seemed* > that the older the kernel version the stabler msk(4) I got, and the > newer the kernel version the easier and more often msk(4) hung. > > I managed to pin down that with the kernel as of 2007.06.04.12.00.00, > it seemed not to give me any msk watchdog timeout at all, and that > with the kernel as of 2007.06.05.12.00.00, msk(4) began to hang and > the watchdog began to timeout once in a while. There may be a latter > commit that made my msk(4) even more unstable, but I am not sure about > this part as it is not easy to measure the level of "unstableness" of > the network. > > It seems that the most significant commit between 2007.06.04.12.00.00 > and 2007.06.05.12.00.00 was threadlock by jeff@. I don't know why or > how it would affect msk(4), though. I was using SCHED_SMP on a C2D, > but switched back to SCHED_ULE when I did the search. > > I discovered a couple other funny phenomena during the search that may > also suggest this be related to threadlock. One is that msk(4) seemed > to hang less frequently when the system was busy building world or > kernel. The other thing is that I seemed to be able to help unhang > the interface by switching the input focus in X Window by move my > mouse cursor to another window. > > My result might not be accurate, though, as I only rebuilt the kernel, > not the whole world, when I did the search. > Does msk(4) use shared interrupt? Show me the output of "vmstat -i". -- Regards, Pyun YongHyeon