From: Rui Nuno Capela <rncbc@rncbc.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Gregory Haskins <ghaskins@novell.com>
Subject: Re: 2.6.23.1-rt5 (was 2.6.23-rt1 trouble)
Date: Tue, 30 Oct 2007 21:02:44 +0000 [thread overview]
Message-ID: <47279BF4.4060207@rncbc.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0710301605100.31349@gandalf.stny.rr.com>
Steven Rostedt wrote:
> --
>> 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 ;)
>>
>
> hmm, it could also be a separate issue. This other laptop is the one that
> took a while to freeze. Correct?
>
yes, it seems that was the case, but not sure if still applies. the
moment of the freezes are rather random, sometimes in the (tainted)
desktop one it takes a while too before it starts to hiccup.
> Was it only on X apps? Or could it possible be something we could do via a
> command line and then we could see vga output (if any).
>
most of the time, yes, it's on X applications. if I get into a tty (eg.
via Alt-Ctrl-F1) it seems to eventually recover from the intermitent
frozen state easier, but its just a matter of time to have it also dead
on the console, sooner or later. once it starts freezing the first time
I know the whole system is, how should i say? doomed ...
never saw a bug, oops or panik message. it just drops dead, until
SysRq-B gets hit in despair :)
cheers
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
next prev parent reply other threads:[~2007-10-30 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 2:04 2.6.23-rt1 Steven Rostedt
2007-10-15 10:49 ` 2.6.23-rt1 trouble Rui Nuno Capela
2007-10-17 17:39 ` Rui Nuno Capela
2007-10-27 14:43 ` 2.6.23-rt4 (was 2.6.23-rt1 trouble) Rui Nuno Capela
2007-10-27 16:05 ` Steven Rostedt
2007-10-27 20:06 ` Rui Nuno Capela
2007-10-30 19:11 ` 2.6.23.1-rt5 " Rui Nuno Capela
2007-10-30 19:28 ` Steven Rostedt
2007-10-30 19:54 ` Rui Nuno Capela
2007-10-30 20:06 ` Steven Rostedt
2007-10-30 21:02 ` Rui Nuno Capela [this message]
2007-11-03 18:22 ` Gabriel C
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47279BF4.4060207@rncbc.org \
--to=rncbc@rncbc.org \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome