From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86, microcode: Conversion from sysdev class caused regression
Date: Wed, 11 Apr 2012 13:06:01 -0700 [thread overview]
Message-ID: <20120411200601.GC12288@kroah.com> (raw)
In-Reply-To: <20120411163849.GE4794@alberich.amd.com>
On Wed, Apr 11, 2012 at 06:38:50PM +0200, Andreas Herrmann wrote:
> Hi,
>
> commit 8a25a2fd126c621f44f3aeaef80d51f00fc11639 (cpu: convert 'cpu'
> and 'machinecheck' sysdev_class to a regular subsystem) causes a
> regression in the CPU microcode loader.
>
> Previous behaviour was that module loading failed if no appropriate
> CPU was found. Now we get
>
> [ 131.717212] WARNING: at fs/sysfs/group.c:138 mc_device_remove+0x5f/0x70 [microcode]()
> [ 131.717218] Hardware name: 01972NG
> [ 131.717223] sysfs group ffffffffa00013d0 not found for kobject 'cpu0'
> [ 131.717228] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel
> btusb snd_hda_codec bluetooth thinkpad_acpi rfkill microcode(-) [last unloaded: cfg80211]
> [ 131.717254] Pid: 4560, comm: modprobe Not tainted 3.4.0-rc2-00002-g258f742 #5
> [ 131.717260] Call Trace:
> [ 131.717277] [<ffffffff8103113b>] ? warn_slowpath_common+0x7b/0xc0
> [ 131.717287] [<ffffffff81031235>] ? warn_slowpath_fmt+0x45/0x50
> [ 131.717300] [<ffffffff81120e74>] ? sysfs_remove_group+0x34/0x120
> [ 131.717311] [<ffffffffa00000ef>] ? mc_device_remove+0x5f/0x70 [microcode]
> [ 131.717325] [<ffffffff81331eb9>] ? subsys_interface_unregister+0x69/0xa0
> [ 131.717336] [<ffffffff81563526>] ? mutex_lock+0x16/0x40
> [ 131.717346] [<ffffffffa0000c3e>] ? microcode_exit+0x50/0x92 [microcode]
> [ 131.717357] [<ffffffff8107051d>] ? sys_delete_module+0x16d/0x260
> [ 131.717369] [<ffffffff810a0065>] ? wait_iff_congested+0x45/0x110
> [ 131.717379] [<ffffffff815656af>] ? page_fault+0x1f/0x30
> [ 131.717389] [<ffffffff81565ba2>] ? system_call_fastpath+0x16/0x1b
>
>
> after loading the driver on an unsupported CPU and the subsequent
> attempt to unload the driver.
That's not nice, but why is the driver getting loaded for a CPU that it
doesn't control? Startup scripts?
It's just a "warning", everything else still works properly, right?
Patches to fix this up are always gladly accepted :)
thanks,
greg k-h
next prev parent reply other threads:[~2012-04-11 20:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 16:38 Andreas Herrmann
2012-04-11 17:06 ` Kay Sievers
2012-04-11 20:04 ` Borislav Petkov
2012-04-11 20:06 ` Greg Kroah-Hartman [this message]
2012-04-11 20:10 ` Borislav Petkov
2012-04-12 16:23 ` Borislav Petkov
2012-04-12 16:30 ` [PATCH 1/2] x86, microcode: Fix sysfs warning during module unload Borislav Petkov
2012-04-12 22:45 ` Greg Kroah-Hartman
2012-04-12 16:34 ` [PATCH 2/2] x86, microcode: Ensure that module is only loaded for Borislav Petkov
2012-04-12 22:45 ` Greg Kroah-Hartman
2012-04-16 8:42 ` Srivatsa S. Bhat
2012-04-16 13:43 ` Borislav Petkov
2012-04-17 14:11 ` Srivatsa S. Bhat
2012-04-17 14:50 ` Borislav Petkov
2012-04-17 15:53 ` Gene Heskett
2012-04-17 16:02 ` Kay Sievers
2012-04-17 17:30 ` Gene Heskett
2012-04-17 18:07 ` Borislav Petkov
2012-04-22 2:55 ` Henrique de Moraes Holschuh
2012-04-25 23:36 ` Kay Sievers
2012-04-17 17:35 ` Srivatsa S. Bhat
2012-05-08 4:28 ` [tip:x86/urgent] x86/microcode: Ensure that module is only loaded on supported Intel CPUs tip-bot for Srivatsa S. Bhat
2012-04-14 18:23 ` [tip:x86/urgent] x86, microcode: Fix sysfs warning during module unload on unsupported CPUs tip-bot for Andreas Herrmann
2012-04-14 18:24 ` [tip:x86/urgent] x86, microcode: Ensure that module is only loaded on supported AMD CPUs tip-bot for Andreas Herrmann
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=20120411200601.GC12288@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Borislav.Petkov@amd.com \
--cc=andreas.herrmann3@amd.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome