public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Jonas Oreland <jonas@mysql.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs?
Date: Mon, 28 Nov 2005 07:59:40 -0500	[thread overview]
Message-ID: <1133182780.5625.4.camel@localhost.localdomain> (raw)
In-Reply-To: <438AF860.7050905@mysql.com>

On Mon, 2005-11-28 at 13:30 +0100, Jonas Oreland wrote: 
> Steven Rostedt wrote:
> > Hi Ingo,
> > 
> > With -rt20 on the AMD64 x2, I'm getting a crap load of these:
> > 
> > read_tsc: ACK! TSC went backward! Unsynced TSCs?
> > 
> > So bad that the system wont even boot (at least I won't wait long enough
> > to let it finish).
> > 
> > config at: http://www.kihontech.com/tests/rt/config
> 
> Check this: http://bugzilla.kernel.org/show_bug.cgi?id=5105
> 
> Booting with idle=poll, fixes that.
> 
> Hope it help

I forgot to mention that I tried that too.  But thank you for sending
this, because, just to make sure, I tried it again, and now it booted.
I think I might have had a typo when adding idle=poll the first time.  I
think of this as a temporary solution, and I won't be adding that to
grub anytime soon.  Manually typing it in at boot time will keep me
remembering that it is there.  As long as I make sure that I type it
right ;-)

OK, this means that I don't want to stay in the -RT kernel too long
(electric prices are up you know).

-- Steve



  reply	other threads:[~2005-11-28 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28 12:05 [RT] read_tsc: ACK! TSC went backward! Unsynced TSCs? Steven Rostedt
2005-11-28 12:30 ` Jonas Oreland
2005-11-28 12:59   ` Steven Rostedt [this message]
2005-11-28 14:21     ` Ingo Molnar
2005-11-28 15:38   ` Lee Revell
2005-11-28 17:30 ` thockin
2005-11-28 17:39   ` Lee Revell
2005-11-28 18:30     ` Dave Jones
2005-11-28 18:35     ` thockin
2005-11-29 14:06       ` Andi Kleen
2005-11-29 16:52         ` thockin
2005-11-29 16:48           ` Andi Kleen

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=1133182780.5625.4.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=johnstul@us.ibm.com \
    --cc=jonas@mysql.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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