Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261231AbUKCBD4 (ORCPT ); Tue, 2 Nov 2004 20:03:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261228AbUKCBDz (ORCPT ); Tue, 2 Nov 2004 20:03:55 -0500 Received: from lax-gate6.raytheon.com ([199.46.200.237]:2957 "EHLO lax-gate6.raytheon.com") by vger.kernel.org with ESMTP id S261452AbUKBVkg (ORCPT ); Tue, 2 Nov 2004 16:40:36 -0500 To: Ingo Molnar Cc: Mark_H_Johnson@raytheon.com, Thomas Gleixner , Florian Schmidt , Lee Revell , Paul Davis , LKML , Bill Huey , Adam Heath , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , jackit-devel , Rui Nuno Capela , "K.R. Foley" From: Mark_H_Johnson@raytheon.com Subject: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.6.8 Date: Tue, 2 Nov 2004 15:39:21 -0600 Message-ID: X-MIMETrack: Serialize by Router on RTSHOU-DS01/RTS/Raytheon/US(Release 6.5.2|June 01, 2004) at 11/02/2004 03:39:30 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-SPAM: 0.00 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 819 Lines: 20 >was this already in the default bootup, or only after the crash >happened? Not quite a "crash", but definitely after I noticed the system no longer doing any useful work. As I said before, it was as if anything to do with timers was not working (e.g., sleep 1s). >Does this also happen if you chrt ksoftirqd to FIFO prio 1? >Does the 'LOC' count increase for both cpus in /proc/interrupts? It will be an hour or so before I can try either of these, I have a build in progress. I can check both of these with the new build (or the old one if you want that too). --Mark - 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/