Date: Mon, 11 Dec 2006 11:00:27 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: current@FreeBSD.org Subject: Re: CURRENT freezes on Laitude D520 (fwd) Message-ID: <20061211110009.K62822@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
Retransmit due to bad CC. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Mon, 11 Dec 2006 09:27:56 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: yal <yal@yal.hopto.org> Cc: freebsd-current-request@FreeBSD.org Subject: Re: CURRENT freezes on Laitude D520 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? Thanks, Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061211110009.K62822>