mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	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: Sat, 03 Nov 2007 19:22:18 +0100	[thread overview]
Message-ID: <472CBC5A.5080104@googlemail.com> (raw)
In-Reply-To: <472781E3.7010103@rncbc.org>

>> Steven Rostedt wrote:
>>> When things start to freeze, could you capture the output of a sysrq-t.
>>>

Hi ,

I have also the same problem on my SMP box[1] ( i686 ), random hard freeze I can just hard reset the box.

I'm not able to capture any output :/ keyboard does not work , netconsole does not have any output when freeze occurs,
nor I have any 'BUG:' , 'Oops:' or the like messages in any logs.
The only thing I noticed is :

...

Clocksource tsc unstable (delta = 4686944957 ns)
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ <-- may be some sort data corruption :/

...

as latest kernel message before most freeze. 

Booting with different clocksource does not make any difference.

I do not use nvidia , in fact I don't use any external kernel module on that box.

Anyway it seems to work fine on non-SMP also my laptops does not have that problem with the same kernel.

If needed I can post the config but I tested a lot different configs with the same result.

Is there any rt-git tree I can test ?


Regards,

Gabriel


[1] http://194.231.229.228/lara/lara.html
    http://194.231.229.228/lara/lara.lspci


      parent reply	other threads:[~2007-11-03 18:22 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
2007-11-03 18:22             ` Gabriel C [this message]

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=472CBC5A.5080104@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rncbc@rncbc.org \
    --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