Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261626AbVCUH3i (ORCPT ); Mon, 21 Mar 2005 02:29:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261635AbVCUH3h (ORCPT ); Mon, 21 Mar 2005 02:29:37 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:9879 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261626AbVCUH3c (ORCPT ); Mon, 21 Mar 2005 02:29:32 -0500 Date: Mon, 21 Mar 2005 08:29:27 +0100 (MET) From: Jan Engelhardt To: viking cc: linux-kernel@vger.kernel.org Subject: Re: Kernel hiccups (was USB Mouse Hiccups) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 828 Lines: 21 >-meat- >> I've also noted .10 is quicker off the blocks than 2.6.11 seems to be. > >Namely seems to happen around the times when I'm doing something like >mounting devfs (takes nearly 30 secs), and when I'm accessing files from >disc (bash$ less some-random-file.txt) - this can take about two seconds >for Linux to actually notice I've done something. I've no idea where the >error is here, either. i.e. is bash waiting around for me? is the >filesystem code waiting for some reason? Is the kernel in a tailspin? >[shrug] Use sysrq+t and see where it "hangs". Jan Engelhardt -- - 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/