Date: Mon, 7 Jan 2008 12:19:30 +0100
From: Ingo Molnar <mingo@elte.hu>
To: jplatte@naasa.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: regression: 100% io-wait with 2.6.24-rcX
Message-ID: <20080107111930.GB29973@elte.hu>
References: <200801071151.11200.lists@naasa.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200801071151.11200.lists@naasa.net>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1080
Lines: 31


* Joerg Platte <lists@naasa.net> wrote:

> 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...

do:

  echo t > /proc/sysrq-trigger

and send us the dmesg output. If the dmesg output does not include the 
bootup bits then increase CONFIG_LOG_BUF_SHIFT to 20 or so:

  CONFIG_LOG_BUF_SHIFT=20

to have a large enough kernel messages buffer.

	Ingo
--
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/