From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757933Ab2ARPl5 (ORCPT ); Wed, 18 Jan 2012 10:41:57 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:54656 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755445Ab2ARPl4 (ORCPT ); Wed, 18 Jan 2012 10:41:56 -0500 X-Authority-Analysis: v=2.0 cv=I83ntacg c=1 sm=0 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=w8ftPpTke-cA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=ieqZB9EfK4cV3iOLFHQA:9 a=PUjeQqilurYA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Message-ID: <1326901314.17534.81.camel@gandalf.stny.rr.com> Subject: Re: [PATCH RT 0/4] [ANNOUNCE] 3.0.14-rt32-rc1 From: Steven Rostedt To: Tim Sander Cc: linux-kernel@vger.kernel.org, linux-rt-users , Thomas Gleixner , Carsten Emde , John Kacur Date: Wed, 18 Jan 2012 10:41:54 -0500 In-Reply-To: <201201181450.17680.tim.sander@hbm.com> References: <20120118034531.335521323@goodmis.org> <201201181450.17680.tim.sander@hbm.com> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.2-1 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2012-01-18 at 14:50 +0100, Tim Sander wrote: > Hi Steve > > This is the RT stable review cycle of patch 3.0.14-rt32-rc1. > > > > Please scream at me if I messed something up. Please test the patches too. > Well the error i described in other mails to this list are still persistent: > * ksoftirq running wild due to fec ethernet tx interrupt. > I would be surprised if it went away, as none of these patches would have touched that code. > Does patch nr 2 possibly fix the error reboot fails with "Unable to execute > shutdown: Bad address". The error occurs not to often so it is hard to say if > this 3.0.14-rt32 is still showing this error. Honestly I don't know about that error. But wait queues have been a thorn in -rt for a while, and this patch fixes a few areas I'm sure. That being one of them, I guess you'll find out if you see the bug again ;-) -- Steve