LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Maxim <maximlevitsky@gmail.com>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far
Date: Sun, 18 Mar 2007 01:01:44 +0200	[thread overview]
Message-ID: <200703180101.44668.maximlevitsky@gmail.com> (raw)
In-Reply-To: <1174088342.13341.340.camel@localhost.localdomain>

On Saturday 17 March 2007 01:39:01 Thomas Gleixner wrote:
> On Fri, 2007-03-16 at 12:30 +0200, Maxim Levitsky wrote:
> > Mar 14 00:22:23 MAIN kernel: [    2.072875] caller is check_tsc_sync_source+0x1d/0x100
> > Mar 14 00:22:23 MAIN kernel: [    2.072878]  [show_trace_log_lvl+26/48] show_trace_log_lvl+0x1a/0x30
> > Mar 14 00:22:23 MAIN kernel: [    2.072931] checking TSC synchronization [CPU#0 -> CPU#1]:
> > Mar 14 00:22:23 MAIN kernel: [    2.092922] Measured 72051818872 cycles TSC warp between CPUs, turning off
> > 
> > It looks clear that preempt is enabled all the way in second cpu initialization, ( I think that at least in check_tsc_sync_source, it should be disabled,
> > shouldn't it ? )
> 
> This should be fixed by commit d04f41e35343f1d788551fd3f753f51794f4afcf
> 
> 	tglx
> 
> 
> 
> 

Hi,

Yes, it is fixed, thanks

Regards,
	Maxim Levitsky

  reply	other threads:[~2007-03-17 23:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 10:30 [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Maxim Levitsky
2007-03-16 23:19 ` Len Brown
2007-03-17 23:00   ` Maxim
2007-03-17 23:32     ` Thomas Gleixner
2007-12-30  7:50       ` Mike Galbraith
2007-12-30 14:53         ` Ingo Molnar
2007-03-20 11:54     ` sysfs ugly timer interface (was Re: [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far) Pavel Machek
2007-03-22 15:28       ` Greg KH
2007-03-22 15:41         ` Thomas Gleixner
2007-03-23  1:24         ` sysfs q [was: sysfs ugly timer interface] Jan Engelhardt
2007-03-23  4:48           ` Greg KH
2007-03-23  6:05             ` Jan Engelhardt
2007-03-16 23:39 ` [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Thomas Gleixner
2007-03-17 23:01   ` Maxim [this message]
2007-03-16 23:44 ` Thomas Gleixner
2007-03-17  0:04   ` [PATCH] i386: trust the PM-Timer calibration of the local APIC timer Thomas Gleixner
2007-03-17  7:22     ` Ingo Molnar
2007-03-17 13:24     ` Andi Kleen
2007-03-18  8:12     ` Andrew Morton
2007-03-18  8:45       ` Thomas Gleixner
2007-03-17  1:32   ` [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Len Brown
2007-03-17  9:56     ` Thomas Gleixner
2007-03-17 11:05       ` Thomas Gleixner
2007-03-17 16:52       ` Thomas Gleixner
2007-03-17 10:32     ` Arjan van de Ven
2007-03-17 13:26       ` Andi Kleen
2007-03-20  4:27         ` Greg KH
2007-03-20  6:30           ` Thomas Gleixner
2007-03-20  9:14           ` Arjan van de Ven
2007-03-20 11:36           ` Andi Kleen
2007-03-20 11:41             ` Oliver Neukum
2007-03-17 22:45     ` Maxim
2007-03-20  5:04   ` Lee Revell
2007-03-20  5:36     ` Eric St-Laurent
2007-03-20  9:15       ` Arjan van de Ven
2007-03-20 18:04         ` Andy Lutomirski
2007-03-20 22:58         ` Eric St-Laurent

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=200703180101.44668.maximlevitsky@gmail.com \
    --to=maximlevitsky@gmail.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).