mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirco Tischler <mt-ml@gmx.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [BUG]:WARNING: at arch/x86/kernel/rtc.c:122 in 2.6.26-rc1
Date: Wed, 07 May 2008 23:46:17 +0200	[thread overview]
Message-ID: <1210196777.26103.8.camel@mtlp.tischlernetz> (raw)
In-Reply-To: <alpine.LFD.1.10.0805072253480.3318@apollo.tec.linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

On Mi, 2008-05-07 at 22:58 +0200, Thomas Gleixner wrote:
> On Wed, 7 May 2008, Mirco Tischler wrote:
> 
> > On Mi, 2008-05-07 at 21:06 +0200, Thomas Gleixner wrote:
> > > > [11677.490019] CPU1 is down
> > > > [11677.490149] Extended CMOS year: 2000
> > > > [11677.490149] x86 PAT enabled: cpu 0, old 0x7040600070406, new
> > > > 0x7010600070106
> > > > [11677.490747] Back to C!
> > > > [11677.490952] microcode: CPU0 updated from revision 0x92 to 0x92, date
> > > > = 03132007 
> 
> That's an odd one: updated from revision 0x92 to 0x92
> 
> It's right before the warning triggers. Is this microcode message in
> all your boot/resume logs ?
Yes, wondered about that too. It's defintely not on all resumes. But it
is on more than that single one triggering the warning:
May  7 19:53:21 kernel: [4307505.090195] Extended CMOS year: 2000
May  7 19:53:21 kernel: [4307505.090195] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 19:53:21 kernel: [4307505.090195] Back to C!
May  7 19:53:21 kernel: [4307505.090195] microcode: CPU0 updated from revision 0x92 to 0x92, date = 03132007 
May  7 19:53:21 kernel: [4307505.090195] Extended CMOS year: 2000

May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000
May  7 21:52:04 kernel: [4294896.091827] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
May  7 21:52:04 kernel: [4294896.091827] Back to C!
May  7 21:52:04 kernel: [4294896.091827] Extended CMOS year: 2000

Thanks
Mirco

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-07 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 18:05 Mirco Tischler
2008-05-07 18:11 ` Mirco Tischler
2008-05-07 19:06 ` Thomas Gleixner
2008-05-07 19:32   ` Mirco Tischler
2008-05-07 20:58     ` Thomas Gleixner
2008-05-07 21:46       ` Mirco Tischler [this message]
2008-05-07 22:03         ` Andi Kleen
2008-05-08 10:12           ` Thomas Gleixner
2008-05-08 10:52             ` 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=1210196777.26103.8.camel@mtlp.tischlernetz \
    --to=mt-ml@gmx.de \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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

all inboxes | Powered by JetHome®