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 19:11:31 +0000 [thread overview]
Message-ID: <472781E3.7010103@rncbc.org> (raw)
In-Reply-To: <47239A37.8000401@rncbc.org>
Rui Nuno Capela wrote:
> Steven Rostedt wrote:
>>
>> When things start to freeze, could you capture the output of a sysrq-t.
>>
>
> yes, you can find a complete serial console capture here, where it holds
> the final SysRq-T output:
> http://www.rncbc.org/datahub/console-2.6.23.1-rt4.1-1.log
>
> the corresponding .config is also there:
> http://www.rncbc.org/datahub/config-2.6.23.1-rt4.1
>
> the reason this is a new kernel build, following a shot in the dark from
> nick mainsbridge, which let out the ntfs module build (CONFIG_NTFS_FS is
> not set) suggesting that would mitigate similar freezes.
>
> in deed the general feel is that it seems to run longer and less prone
> to those incidents, but that is just a gut feeling, nothing more.
>
> hope this be any useful.
>
>> I have a P4HT laptop (unfortunately with no serial). I use it as one of my
>> main machines, so it will suck for me when it freezes ;-). I'll take your
>> config and try it out.
>>
>> I'll most likely do this on Monday since process Wife has the highest
>> priority over the weekend ;-)
>>
>
> that is also true here :)
>
> otoh, as reported before, the freezes are not exclusive to P4HT, which
> is the main box I'm been reporting here (the one which has a good old
> serial port anyway), but also applies to my other laptop, an core2 duo
> t7200.
>
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
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 ;)
--
rncbc aka Rui Nuno Capela
rncbc@rncbc.org
next prev parent reply other threads:[~2007-10-30 19:13 UTC|newest]
Thread overview: 13+ 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 ` Rui Nuno Capela [this message]
2007-10-30 19:28 ` 2.6.23.1-rt5 " 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
2007-10-31 8:02 ` Alessio Igor Bogani
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=472781E3.7010103@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.