From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian May Subject: Re: open sleeps Date: Thu, 26 Jun 2008 16:30:10 +1000 Message-ID: <48633772.50806@vpac.org> References: <485AE866.6070206@vpac.org> <20080620095813.22fb518e.sfr@canb.auug.org.au> <485AF4BE.6090409@vpac.org> <20080620102003.8dd1270c.sfr@canb.auug.org.au> <485AFEE7.5010703@vpac.org> <485B03DA.5070501@vpac.org> <20080620064529.GA29319@disturbed> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: Brian May , Stephen Rothwell , linux-fsdevel@vger.kernel.org Return-path: Received: from zimbra.vpac.org ([202.158.218.6]:58252 "EHLO zimbra.vpac.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752397AbYFZGaO (ORCPT ); Thu, 26 Jun 2008 02:30:14 -0400 In-Reply-To: <20080620064529.GA29319@disturbed> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Dave Chinner wrote: > This is just the stupid (broken) ia32 stack tracing - it outputs every > single object it sees in the stack that may be function call. Hence > you see some stuff that is from past stack traversals. I'd say this > is sleeping in a select() call, not doing anything related to > xfs or networking.... > Hello, Thanks for your help. Just a followup: Every indication seems to be that it is the firewall in the virus scanner we use, F-Secure, that prevents Windows from releasing oplocks properly. After turning off the firewall, the oplocks get released and there is no problem. Possibly related to the timing of wpkg being invoked before system logons too. Might be time to consider another virus scanner/firewall solution. Brian May