From owner-freebsd-current@FreeBSD.ORG Mon Dec 11 19:48:33 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 2FEDA16A40F for ; Mon, 11 Dec 2006 19:48:33 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C743E43EF3 for ; Mon, 11 Dec 2006 19:34:09 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0415146F25; Mon, 11 Dec 2006 14:35:24 -0500 (EST) Date: Mon, 11 Dec 2006 19:35:23 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Maxim Konovalov In-Reply-To: <20061211183048.S20189@mp2.macomnet.net> Message-ID: <20061211193334.W62822@fledge.watson.org> References: <20061211110009.K62822@fledge.watson.org> <20061211183048.S20189@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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:48:33 -0000 On Mon, 11 Dec 2006, Maxim Konovalov wrote: > 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! So, just to confirm: you can now run with default net.isr.direct and debug.mpsafenet settings and without problems? Robert N M Watson Computer Laboratory University of Cambridge