mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Adamushko <dmitry.adamushko@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Ingo Molnar <mingo@elte.hu>, 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: Wed, 15 Apr 2009 16:51:48 +0200	[thread overview]
Message-ID: <b647ffbd0904150751u64e69097q79c511533f949c00@mail.gmail.com> (raw)
In-Reply-To: <49E5EABB.9010402@garzik.org>

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

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).

btw., is the upgrade done with the help of some microcode startup
script? I wonder why it decides to unload the microcode module (what
kind of checks it does to take this decision)...

(non-whitespace-damaged version is enclosed. I appologize for the
inconvenience, don't have a proper e-mail client at hand)


---

Keep sysfs files around for cpus even when we failed to locate
microcode for them at the moment of module loading. The appropriate
microcode firmware can become available later on.


--- arch/x86/kernel/microcode_core-orig.c       2009-04-15
10:34:25.000000000 +0200
+++ arch/x86/kernel/microcode_core.c            2009-04-15
16:27:51.000000000 +0200
@@ -380,8 +380,6 @@ static int mc_sysdev_add(struct sys_devi
                return err;

        err = microcode_init_cpu(cpu);
-       if (err)
-               sysfs_remove_group(&sys_dev->kobj, &mc_attr_group);

        return err;
 }


>
>        Jeff
>

-- 
Best regards,
Dmitry Adamushko

[-- Attachment #2: microcode-fix-warning.patch --]
[-- Type: text/x-patch, Size: 348 bytes --]

--- arch/x86/kernel/microcode_core-orig.c	2009-04-15 10:34:25.000000000 +0200
+++ arch/x86/kernel/microcode_core.c		2009-04-15 16:27:51.000000000 +0200
@@ -380,8 +380,6 @@ static int mc_sysdev_add(struct sys_devi
 		return err;
 
 	err = microcode_init_cpu(cpu);
-	if (err)
-		sysfs_remove_group(&sys_dev->kobj, &mc_attr_group);
 
 	return err;
 }

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 18:23 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 [this message]
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=b647ffbd0904150751u64e69097q79c511533f949c00@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=amd64-microcode@amd64.org \
    --cc=andreas.herrmann3@amd.com \
    --cc=jeff@garzik.org \
    --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

all inboxes | Powered by JetHome®