Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755494Ab0GIXIO (ORCPT ); Fri, 9 Jul 2010 19:08:14 -0400 Received: from smtp4.Stanford.EDU ([171.67.219.84]:52337 "EHLO smtp.stanford.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754928Ab0GIXIL (ORCPT ); Fri, 9 Jul 2010 19:08:11 -0400 Subject: Re: 2.6.33.5 rt23: machine lockup (nfs/autofs related?) From: Fernando Lopez-Lezcano To: john stultz Cc: nando@ccrma.Stanford.EDU, Thomas Gleixner , LKML , rt-users , Steven Rostedt , Nick Piggin In-Reply-To: <1278714680.2349.15.camel@localhost.localdomain> References: <1278609590.7527.11.camel@localhost.localdomain> <1278628386.3008.11.camel@localhost.localdomain> <1278629044.12059.6.camel@localhost.localdomain> <1278630050.3008.18.camel@localhost.localdomain> <1278702134.5102.9.camel@localhost.localdomain> <1278705254.2349.14.camel@localhost.localdomain> <1278713600.7122.22.camel@localhost.localdomain> <1278714680.2349.15.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Fri, 09 Jul 2010 16:07:40 -0700 Message-ID: <1278716860.7122.72.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 35 On Fri, 2010-07-09 at 15:31 -0700, john stultz wrote: > On Fri, 2010-07-09 at 15:13 -0700, Fernando Lopez-Lezcano wrote: > > On Fri, 2010-07-09 at 12:54 -0700, john stultz wrote: > > > On Fri, 2010-07-09 at 12:02 -0700, Fernando Lopez-Lezcano wrote: > > > > Ok, I got one! (had to go buy a null modem cable, I thought I had one > > > > but it has disappeared since the last time I did this :-) > > > > > > Great! Sorry to make you go shopping! But this points out the problem > > > nicely. > > > > No problem at all, I was sure I had one... anyway, I still need it :-< > > > > > > Find it below... it keeps spewing stuff every once in a while. Hopefully > > > > this will be enough. No response from the network or the keyboard or > > > > mouse at this point, reset is the only way out. > > > > > > > > I can retest if somebody comes up with a patch... > > > > Sorry, it looks like the patch patched correctly and this is the new > > kernel, but I still get a hang as before. > > Huh. Exact same backtrace? Maybe there's more then one issue with that > function... Hmmm, most likely I made some mistake - I'll double check and report back. -- Fernando -- 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/