From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Peter Oruba <peter.oruba@amd.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: Fri, 17 Apr 2009 01:07:31 +0200 [thread overview]
Message-ID: <20090416230731.GA19553@elte.hu> (raw)
In-Reply-To: <b647ffbd0904150751u64e69097q79c511533f949c00@mail.gmail.com>
* Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> 2009/4/15 Jeff Garzik <jeff@garzik.org>:
> > 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.
>
> Hi,
>
>
> the following patch should eliminate the problem (and revert to
> the old behavior that was altered by Rusty's patch).
Jeff, did this do the trick for you?
Ingo
next prev parent reply other threads:[~2009-04-16 23:08 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
2009-04-15 14:51 ` Dmitry Adamushko
2009-04-16 23:07 ` Ingo Molnar [this message]
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=20090416230731.GA19553@elte.hu \
--to=mingo@elte.hu \
--cc=amd64-microcode@amd64.org \
--cc=andreas.herrmann3@amd.com \
--cc=dmitry.adamushko@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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