Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266744AbUKAQmx (ORCPT ); Mon, 1 Nov 2004 11:42:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270616AbUKAQmw (ORCPT ); Mon, 1 Nov 2004 11:42:52 -0500 Received: from dfw-gate3.raytheon.com ([199.46.199.232]:52421 "EHLO dfw-gate3.raytheon.com") by vger.kernel.org with ESMTP id S266744AbUKAQiq (ORCPT ); Mon, 1 Nov 2004 11:38:46 -0500 Subject: Re: [Fwd: Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.4] To: Ingo Molnar Cc: Karsten Wiese , Bill Huey , Adam Heath , jackit-devel , "K.R. Foley" , LKML , Florian Schmidt , Fernando Pablo Lopez-Lezcano , Paul Davis , Lee Revell , Rui Nuno Capela , Thomas Gleixner , Michal Schmidt X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Mark_H_Johnson@raytheon.com Date: Mon, 1 Nov 2004 10:34:22 -0600 X-MIMETrack: Serialize by Router on RTSHOU-DS01/RTS/Raytheon/US(Release 6.5.2|June 01, 2004) at 11/01/2004 10:35:40 AM 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: 1852 Lines: 52 >I've uploaded -V0.6.5 to the usual place: > > http://redhat.com/~mingo/realtime-preempt/ I built with this patch and had some problems with the system locking up. First attempt: - booted to single user without problem - telinit 5 was OK as well - logged in. After first window popped up, I did su - to get root access and the system locked up. No display updates nor any mouse movement. Entering Alt-SysRq-L displayed SysRq : Show Regs On All CPUs and no other messages appeared on the serial console. Attempts to use other Alt-SysRq keys were ignored, hard reset to reboot. Second attempt: - booted to single user without problem - telinit 5 failed after kudzu timed out (had "detected" a change due to the serial console) No messages on serial console after the kudzu timeout. This time Alt-SysRq-L did work. Also did Alt-SysRq-T and -D and will send the all the serial console messages separately. Did notice an odd message during the dump of tasks... Losing too many ticks! TSC cannot be used as a timesource. Possible reasons for this are: You're running with Speedstep. [almost surely not] You don't have DMA enabled for your hard disk (see hdparm), [udma4 should be set at this point] Incorrect TSC synchronization on an SMP system (see dmesg). [can't look at that, system is hung] Falling back to a sane timesource now. Alas, this "sane timesource" didn't help either, system still not responding right. Alt-SysRq-S said SysRq : Emergency Sync [without any complete messages] and Alt-SysRq-B did reboot the system. --Mark H Johnson - 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/