[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49DC51C6.1090103@cn.fujitsu.com>
Date: Wed, 08 Apr 2009 15:27:02 +0800
From: Wang Chen <wangchen@...fujitsu.com>
To: Alessandro Suardi <alessandro.suardi@...il.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Ingo Molnar <mingo@...e.hu>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Microcode driver causing WARNING in 2.6.29-git13/14 on Dell E6400
Alessandro Suardi said the following on 2009-4-7 19:07:
> Dell Latitude E6400, F10-uptodate as of yesterday, 2.6.29-git14 plus
> Vegard Nossum's fix to acpi/battery.c to allow booting (this specific
> WARNING was also printed during -git13 boot, which would eventually
> hang prior to Vegard's patch).
>
> dmesg excerpt:
>
>
>
> Adding 4096532k swap on /dev/sda5. Priority:-1 extents:1 across:4096532k
> SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
> platform microcode: firmware: requesting intel-ucode/06-17-06
> platform microcode: firmware: requesting intel-ucode/06-17-06
> Microcode Update Driver: v2.00 <tigran@...azian.fsnet.co.uk>, Peter Oruba
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/group.c:138 sysfs_remove_group+0x60/0xef()
> Hardware name: Latitude E6400
> sysfs group ffffffffa0136850 not found for kobject 'cpu0'
> Modules linked in: microcode(-) snd_hda_codec_intelhdmi snd_hda_intel
> snd_hda_codec snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event
> snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd
> battery pcspkr video dell_laptop firewire_ohci rfkill i2c_i801 ac
> firewire_core dcdbas soundcore usb_storage crc_itu_t output i2c_core
> joydev snd_page_alloc [last unloaded: scsi_wait_scan]
> Pid: 2570, comm: rmmod Not tainted 2.6.29-git14 #1
> Call Trace:
> [<ffffffff81047c2e>] warn_slowpath+0xcc/0x11c
> [<ffffffff811b4fd5>] ? kobject_release+0x6d/0x8c
> [<ffffffff811b4f68>] ? kobject_release+0x0/0x8c
> [<ffffffff8113f208>] sysfs_remove_group+0x60/0xef
> [<ffffffffa01344b4>] mc_sysdev_remove+0x42/0x5f [microcode]
> [<ffffffff8125970b>] sysdev_driver_unregister+0x6c/0xb8
> [<ffffffffa0134f9a>] microcode_exit+0x47/0x87 [microcode]
> [<ffffffff81075317>] sys_delete_module+0x1cb/0x246
> [<ffffffff813c2b09>] ? trace_hardirqs_on_thunk+0x3a/0x3c
> [<ffffffff8100bf6b>] system_call_fastpath+0x16/0x1b
> ---[ end trace 13427fb4ef873fae ]---
> ------------[ cut here ]------------
> WARNING: at fs/sysfs/group.c:138 sysfs_remove_group+0x60/0xef()
> Hardware name: Latitude E6400
> sysfs group ffffffffa0136850 not found for kobject 'cpu1'
> Modules linked in: microcode(-) snd_hda_codec_intelhdmi snd_hda_intel
> snd_hda_codec snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event
> snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd
> battery pcspkr video dell_laptop firewire_ohci rfkill i2c_i801 ac
> firewire_core dcdbas soundcore usb_storage crc_itu_t output i2c_core
> joydev snd_page_alloc [last unloaded: scsi_wait_scan]
> Pid: 2570, comm: rmmod Tainted: G W 2.6.29-git14 #1
> Call Trace:
> [<ffffffff81047c2e>] warn_slowpath+0xcc/0x11c
> [<ffffffff811b4fd5>] ? kobject_release+0x6d/0x8c
> [<ffffffff811b4f68>] ? kobject_release+0x0/0x8c
> [<ffffffff8113f208>] sysfs_remove_group+0x60/0xef
> [<ffffffffa01344b4>] mc_sysdev_remove+0x42/0x5f [microcode]
> [<ffffffff8125970b>] sysdev_driver_unregister+0x6c/0xb8
> [<ffffffffa0134f9a>] microcode_exit+0x47/0x87 [microcode]
> [<ffffffff81075317>] sys_delete_module+0x1cb/0x246
> [<ffffffff813c2b09>] ? trace_hardirqs_on_thunk+0x3a/0x3c
> [<ffffffff8100bf6b>] system_call_fastpath+0x16/0x1b
> ---[ end trace 13427fb4ef873faf ]---
> Microcode Update Driver: v2.00 removed.
>
>
> System seems to work at the moment (apart from unrelated X/VT
> issues I plan to report in a detailed fashion by the end of this week).
>
I encounter this warning too.
Seems commit af5c820a3169e81af869c113e18ec7588836cd50 intends to hunt
this warning when microcode_init_cpu() failed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists