Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755380AbYAGLK1 (ORCPT ); Mon, 7 Jan 2008 06:10:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753986AbYAGLKR (ORCPT ); Mon, 7 Jan 2008 06:10:17 -0500 Received: from rosi.naasa.net ([212.8.0.13]:53985 "EHLO rosi.naasa.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753395AbYAGLKQ (ORCPT ); Mon, 7 Jan 2008 06:10:16 -0500 X-Greylist: delayed 1142 seconds by postgrey-1.27 at vger.kernel.org; Mon, 07 Jan 2008 06:10:16 EST From: Joerg Platte Reply-To: jplatte@naasa.net To: linux-kernel@vger.kernel.org Subject: regression: 100% io-wait with 2.6.24-rcX Date: Mon, 7 Jan 2008 11:51:10 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200801071151.11200.lists@naasa.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 18 Hi, when booting kernel 2.6.24-rc{4,5,6,7} top reports up to 100% iowait, even if no program accesses the disc on my Thinkpad T40p. Kernel 2.6.23.12 does not suffer from this. Is there anything I can do to find out which process or which part of the kernel is responsible for this? I can try to bisect it, but maybe there are other possibilities to debug this, since I cannot boot this computer frequently. I discovered, that there is no iowait within the first few seconds after waking up from suspend to ram... regards, Jörg -- 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/