From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rui Nuno Capela Subject: Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble) Date: Tue, 30 Oct 2007 19:54:13 +0000 Message-ID: <47278BE5.9070401@rncbc.org> References: <1192154640.15992.10.camel@localhost.localdomain> <38542.213.58.131.130.1192445349.squirrel@www.rncbc.org> <471648B8.1030007@rncbc.org> <47234EA1.4050006@rncbc.org> <47239A37.8000401@rncbc.org> <472781E3.7010103@rncbc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Ingo Molnar , Thomas Gleixner , Gregory Haskins To: Steven Rostedt Return-path: Received: from smtp4.netcabo.pt ([212.113.174.31]:48051 "EHLO exch01smtp09.hdi.tvcabo" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753146AbXJ3T4o (ORCPT ); Tue, 30 Oct 2007 15:56:44 -0400 In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org Steven Rostedt wrote: > -- > On Tue, 30 Oct 2007, Rui Nuno Capela wrote: > >> still in trouble with 2.6.23.1-rt5 :( >> >> .config: >> http://www.rncbc.org/datahub/config-2.6.23.1-rt5.0 >> >> serial console capture: >> http://www.rncbc.org/datahub/console-2.6.23.1-rt5.0-1.log > > "NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 > 14:12:24 PDT 2007" > > Is that the nVidia module? Showing a date of Sept 12th also makes this > look suspicious. > > If this is the case, could you run without that module to see if we get > the same freezes. > yes, running without the *cough* nvidia module is under way. but do you remember that on my other laptop the freezes also happen and on that one there's no single proprietary modules in it? (same .config btw) problem is, like most modern laptops, it doesn't come bundled with a serial port so that can't give you a serial console evidence ... thanks for the reminder, anyway ;) > Thanks, > > -- Steve > >> one thing about SysRq-T: while in the middle of a freeze it just doesn't >> dump anything, just the 'SysRq : Show State' line. you can see that >> several times on the console output above. >> >> only when it is somewhat recovering, as said, by making some last resort >> measures like SysRq-E as in 'SysRq: terminate All Tasks' for instance, >> then SysRq-T will dump something. my guess is that this later dump will >> be moot :/ >> >> back to production with 2.6.22.1-rt9 ;) bye now -- rncbc aka Rui Nuno Capela rncbc@rncbc.org