From owner-freebsd-current@FreeBSD.ORG Mon Dec 11 19:12:08 2006 Return-Path: X-Original-To: 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 340F716A530; Mon, 11 Dec 2006 19:12:08 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B29C643D6A; Mon, 11 Dec 2006 19:09:44 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id kBBJAjek057515; Mon, 11 Dec 2006 22:10:45 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 11 Dec 2006 22:10:41 +0300 (MSK) From: Maxim Konovalov To: Robert Watson In-Reply-To: <20061211110009.K62822@fledge.watson.org> Message-ID: <20061211183048.S20189@mp2.macomnet.net> References: <20061211110009.K62822@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: current@freebsd.org Subject: Re: CURRENT freezes on Laitude D520 (fwd) 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: Mon, 11 Dec 2006 19:12:08 -0000 On Mon, 11 Dec 2006, 11:00-0000, Robert Watson wrote: > On Sun, 10 Dec 2006, yal wrote: > > On Sun, December 10, 2006 13:57, Robert Watson wrote: > > > > > - Try setting net.isr.direct=0 and see if the problem goes away. > > > > > > > > This indeed help. LOR has gone and wireless works. > > > > > result in a deadlock under other circumstances, net.isr.direct makes the > > > chances of that deadlock much greater. > > > > It helped on Latutide D520 as well. No freeze or anything anymore. Top shows > > now 100% idle most of the time. The debug.mpsafent="0" has been deleted, as > > suggested. Thanks to Robert N. M. Watson. > > Sam has committed changes to if_wi in the last 24 hours that may fix > this problem with the default net.isr.direct setting. Could you try > updating to these changes, removing net.isr.direct=0, and seeing > what happens? It works for me. Thanks Sam and Robert! -- Maxim Konovalov