From owner-freebsd-current@FreeBSD.ORG Wed Aug 23 12:40:46 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0886116A4E1 for ; Wed, 23 Aug 2006 12:40:46 +0000 (UTC) (envelope-from oleg@lath.rinet.ru) Received: from lath.rinet.ru (lath.rinet.ru [195.54.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B36043DD1 for ; Wed, 23 Aug 2006 12:40:37 +0000 (GMT) (envelope-from oleg@lath.rinet.ru) Received: from lath.rinet.ru (localhost [127.0.0.1]) by lath.rinet.ru (8.13.6/8.13.6) with ESMTP id k7NCeZ0F018983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Aug 2006 16:40:35 +0400 (MSD) (envelope-from oleg@lath.rinet.ru) Received: (from oleg@localhost) by lath.rinet.ru (8.13.6/8.13.6/Submit) id k7NCeZg3018982; Wed, 23 Aug 2006 16:40:35 +0400 (MSD) (envelope-from oleg) Date: Wed, 23 Aug 2006 16:40:35 +0400 From: Oleg Bulyzhin To: Pyun YongHyeon Message-ID: <20060823124035.GA18628@lath.rinet.ru> References: <20060822042023.GC12848@cdnetworks.co.kr> <20060822091107.A3909@fw.reifenberger.com> <20060822073201.GI12848@cdnetworks.co.kr> <20060822144341.L5561@fw.reifenberger.com> <20060822204342.GA4943@lath.rinet.ru> <20060823005554.GC17902@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060823005554.GC17902@cdnetworks.co.kr> User-Agent: Mutt/1.5.11 Cc: Michael Reifenberger , freebsd-current@freebsd.org Subject: Re: call for bge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2006 12:40:46 -0000 On Wed, Aug 23, 2006 at 09:55:54AM +0900, Pyun YongHyeon wrote: > On Wed, Aug 23, 2006 at 12:43:42AM +0400, Oleg Bulyzhin wrote: > > On Tue, Aug 22, 2006 at 02:44:34PM +0200, Michael Reifenberger wrote: > > > On Tue, 22 Aug 2006, Pyun YongHyeon wrote: > > > ... > > > >I'm not familiar with vge(4) and don't have hardwares supported by > > > >vge(4). Because vge(4) supports a kind of interrupt moderation, there > > > >is a possiblity to have the same issue seen on em(4). > > > >If you want my blind patch I can send a patch for you. > > > > > > > Yes, please! > > > I can test it (on RELENG_6 though). > > > > I have an idea why those timeouts can happen. Could you please test > > attached patch? It may help (or may not). Anyway would be fine > > to know results. > > > > Since vge(4) uses MTX_RECURSE mutex and miibus(4) handler is > protected with the mutex I guess it wouldn't help much. > I guess it needs a seperate mutex to protect miibus(4) handler > and should remove the use of MTX_RECURSE. Hmm. 1) _ifmedia_upd() & _ifmedia_sts() functions are not called from mii layer. 2) As i can see MII layer is not protected by anything, unless you specially acquire driver lock prior to calling mii_ function. Locking ifmedia callbacks should be done (though, it may not help with watchdogs timeout), otherwise we have race on accessing PHY registers. (kern/98738). As i can see, random watchdog timeouts was reported for em, bge, vge, sk (and maybe others, those ones which i remember) drivers. All of them has unlocked _ifmedia_ functions. My idea was: perhaps, under certain condition, concurrent access to PHY could lead to hardware deadlock. > vge(4) also has a bug > if mbuf chain is too long(7 or higher) and defragmentation with > m_defrag(9) fails it would access an invalid mbuf chain. > All these requires lots of work and need a real hardware. > Oleg, if you have hardware, would you fix it? Unfortunately i don't have vge hardware. > > -- > Regards, > Pyun YongHyeon -- Oleg.