public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Oruba <peter.oruba@amd.com>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	amd64-microcode@amd64.org,
	Andreas Herrmann <andreas.herrmann3@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: microcode driver newly spews warnings
Date: Wed, 15 Apr 2009 10:10:03 -0400	[thread overview]
Message-ID: <49E5EABB.9010402@garzik.org> (raw)
In-Reply-To: <20090413182746.GA9954@elte.hu>

Ingo Molnar wrote:
> (added Cc:s)
> 
> * Jeff Garzik <jeff@garzik.org> wrote:
> 
>> Jeff Garzik wrote:
>>> Kernel: 2.6.30-rc1-00306-g8371f87
>>> Hardware: ICH10 x86-64
>>>
>>> This is a regression from 2.6.29.  Microcode spews the following 
>>> WARNING multiple times during boot:
>>>
>>>> ------------[ cut here ]------------
>>>> WARNING: at fs/sysfs/group.c:138 sysfs_remove_group+0xeb/0xf0()
>>>> Hardware name:         sysfs group ffffffffa0209700 not found for  
>>>> kobject 'cpu0'


Update:  Regression occurs in 2.6.30-rc2.

I've now reproduced this on ICH9/Core2 as well as ICH10/Nahelem.

	Jeff




  reply	other threads:[~2009-04-15 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 18:23 microcode driver newly spews warnings Jeff Garzik
2009-04-13 18:25 ` Jeff Garzik
2009-04-13 18:27   ` Ingo Molnar
2009-04-15 14:10     ` Jeff Garzik [this message]
2009-04-15 14:51       ` Dmitry Adamushko
2009-04-16 23:07         ` Ingo Molnar
2009-04-16 23:21           ` Jeff Garzik
2009-04-16 23:28             ` H. Peter Anvin
2009-04-17  6:58               ` Dmitry Adamushko

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=49E5EABB.9010402@garzik.org \
    --to=jeff@garzik.org \
    --cc=amd64-microcode@amd64.org \
    --cc=andreas.herrmann3@amd.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peter.oruba@amd.com \
    --cc=rjw@sisk.pl \
    /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