Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751449AbXBEKgf (ORCPT ); Mon, 5 Feb 2007 05:36:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752146AbXBEKgf (ORCPT ); Mon, 5 Feb 2007 05:36:35 -0500 Received: from jdi.jdi-ict.nl ([82.94.239.5]:39142 "EHLO jdi.jdi-ict.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751449AbXBEKge (ORCPT ); Mon, 5 Feb 2007 05:36:34 -0500 X-Greylist: delayed 664 seconds by postgrey-1.27 at vger.kernel.org; Mon, 05 Feb 2007 05:36:34 EST Date: Mon, 5 Feb 2007 11:24:30 +0100 (CET) From: Igmar Palsenberg X-X-Sender: igmar@jdi.jdi-ict.nl To: Andrew Morton cc: linux-kernel@vger.kernel.org, npiggin@suse.de, erich Subject: Re: 2.6.16.32 stuck in generic_file_aio_write() In-Reply-To: <20061214011042.7b279be6.akpm@osdl.org> Message-ID: References: <20061130212248.1b49bd32.akpm@osdl.org> <20061206074008.2f308b2b.akpm@osdl.org> <20061214004213.13149a48.akpm@osdl.org> <20061214011042.7b279be6.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.12 (jdi.jdi-ict.nl [127.0.0.1]); Mon, 05 Feb 2007 11:24:31 +0100 (CET) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1272 Lines: 41 > Does the other machine have the same problems? It does. It seems to depend on the interrupt frequency : Setting KERNEL_HZ=250 makes it ony appear once a month or so, with KERNEL_HZ=1000, it will occur within a week. It does happen a lot less with the other machine, which isn't under disk activity load as much as the other machine. > Are you able to rule out a hardware failure? Well.. It's too much coincidence that 2 (almost identical) machines show the same weard behaviour. What strikes me that only *disk* interrupts after a while don't get handled. The machine itself is alive, just all disk IO is blocked, which makes it pretty much useless. Erich, could this be some sort of hardware problem ? I know it's a PITA to reproduce, but setting CONFIG_HZ to 1000 and bashing the machine with diskactivity seems to help :) Regards, Igmar -- Igmar Palsenberg JDI ICT Zutphensestraatweg 85 6953 CJ Dieren Tel: +31 (0)313 - 496741 Fax: +31 (0)313 - 420996 The Netherlands mailto: i.palsenberg@jdi-ict.nl - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/