From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261319AbVGGQKO (ORCPT ); Thu, 7 Jul 2005 12:10:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261324AbVGGQKO (ORCPT ); Thu, 7 Jul 2005 12:10:14 -0400 Received: from ms-smtp-03.nyroc.rr.com ([24.24.2.57]:42668 "EHLO ms-smtp-03.nyroc.rr.com") by vger.kernel.org with ESMTP id S261319AbVGGQKM (ORCPT ); Thu, 7 Jul 2005 12:10:12 -0400 Date: Thu, 7 Jul 2005 12:10:05 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@localhost.localdomain Reply-To: rostedt@goodmis.org To: Ingo Molnar cc: linux-kernel@vger.kernel.org Subject: Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45 In-Reply-To: Message-ID: References: <200506301952.22022.annabellesgarden@yahoo.de> <20050630205029.GB1824@elte.hu> <200507010027.33079.annabellesgarden@yahoo.de> <20050701071850.GA18926@elte.hu> <20050703140432.GA19074@elte.hu> <20050703181229.GA32741@elte.hu> <20050706100451.GA7336@elte.hu> <20050707153103.GA22782@elte.hu> 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 On Thu, 7 Jul 2005, Steven Rostedt wrote: > > Darn subversion! I just started a massive commit, and I can't leave work > till it's done. So you still got me here ;-) That commit is still going. I can see why subversion was not used for kernel development. > > On Thu, 7 Jul 2005, Ingo Molnar wrote: > > > > > Anyway, I also want to let you know that the e100 does not work. It's > > > detected, but it wont bring up DHCP, and when I manually configued it, > > > it just froze (the process not the machine). But when I did a sysrq-t, > > > the machine froze up after it completed with some RT yeilding bug. > > > Here's what was last to spit out: > > > > is PCI_MSI enabled by any chance? That is known to break level-triggered > > IOAPIC irqs and devices. > > > > As a matter of fact it is... I'll turn it off now and try it out. > If the commit is still going, I'll get you a response about the result. > It did the trick. I got a network. But I also got a hell of a lot of 'enqueued dead tasks'. But stupid me forgot to turn on capture in minicom, and haven't been able to reproduce the problem. I rebooted the machine which blew away all evidence of what occured, and it's now fine. I'll reboot a few more times to see if I can get it to break again. -- Steve