All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeff Garzik <jeff@garzik.org>, Peter Oruba <peter.oruba@amd.com>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	amd64-microcode@amd64.org,
	Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: LKML <linux-kernel@vger.kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: microcode driver newly spews warnings
Date: Mon, 13 Apr 2009 20:27:46 +0200	[thread overview]
Message-ID: <20090413182746.GA9954@elte.hu> (raw)
In-Reply-To: <49E38393.8000700@garzik.org>


(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'
>>> Modules linked in: microcode(-) kvm_intel kvm uinput sr_mod i2c_i801  
>>> cdrom i2c_c
>>> ore ata_generic sg firewire_ohci snd_hda_codec_realtek pata_marvell  
>>> snd_hda_inte
>>> l snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc  
>>> e1000e ahci lib
>>> ata sd_mod scsi_mod crc_t10dif ext3 jbd uhci_hcd ehci_hcd [last  
>>> unloaded: scsi_w
>>> ait_scan]
>>> Pid: 2161, comm: rmmod Not tainted 2.6.30-rc1-00306-g8371f87 #1
>>> Call Trace:
>>>  [<ffffffff80241a2f>] warn_slowpath+0xaf/0x110
>>>  [<ffffffff80324046>] ? sysfs_addrm_finish+0x1a6/0x250
>>>  [<ffffffff802294d9>] ? __phys_addr+0x9/0x50
>>>  [<ffffffff802294d9>] ? __phys_addr+0x9/0x50
>>>  [<ffffffff8036c49d>] ? kobject_release+0x5d/0xa0
>>>  [<ffffffff802ba7c2>] ? __vunmap+0x12/0x110
>>>  [<ffffffff80325a8b>] sysfs_remove_group+0xeb/0xf0
>>>  [<ffffffffa0207468>] mc_sysdev_remove+0x38/0x50 [microcode]
>>>  [<ffffffff803fc2f8>] sysdev_driver_unregister+0x68/0xa0
>>>  [<ffffffffa0207eed>] microcode_exit+0x39/0x65 [microcode]
>>>  [<ffffffff8026c511>] sys_delete_module+0x191/0x250
>>>  [<ffffffff8020b5bb>] system_call_fastpath+0x16/0x1b
>>> ---[ end trace 0a72bfd99e89dde6 ]---
>>> ------------[ cut here ]------------
>>
>>
>> Full dmesg and lspci attached.
>
> Whoops, forgot kernel config.  Attached.
>
> 	Jeff
>
>
>



  reply	other threads:[~2009-04-13 18:28 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 [this message]
2009-04-15 14:10     ` Jeff Garzik
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=20090413182746.GA9954@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.