From: Djalal Harouni <tixxdz@opendz.org>
To: Borislav Petkov <borislav.petkov@amd.com>,
Tony Luck <tony.luck@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: x86/mce: machine check warning during poweroff
Date: Wed, 11 Jan 2012 01:00:51 +0100 [thread overview]
Message-ID: <20120111000051.GA28874@dztty> (raw)
Today's pull from Linus' tree shows a warning during poweroff, the
message is related to the machinecheck.
The drivers/base/core.c:device_release() did not find the registred
release() function.
This kernel is used for development and it's running under KVM/Qemu, so
if you need further information or tests let me know.
Qemu is simulating 2 CPUs.
Thanks.
[ 1879.944193] ------------[ cut here ]------------
[ 1879.950488] WARNING: at drivers/base/core.c:194 device_release+0x82/0x90()
[ 1879.959424] Hardware name: Bochs
[ 1879.964714] Device 'machinecheck1' does not have a release() function, it is broken and must be fixed.
[ 1879.977354] Modules linked in:
[ 1879.979704] Pid: 1738, comm: halt Not tainted 3.2.0-minimal-kvm-05692-g1c81065-dirty #41
[ 1879.989093] Call Trace:
[ 1879.992729] [<ffffffff8103952a>] warn_slowpath_common+0x7a/0xb0
[ 1879.999308] [<ffffffff81039601>] warn_slowpath_fmt+0x41/0x50
[ 1880.005463] [<ffffffff8172b022>] device_release+0x82/0x90
[ 1880.012915] [<ffffffff81601667>] kobject_release+0x47/0x90
[ 1880.019107] [<ffffffff8160152c>] kobject_put+0x2c/0x60
[ 1880.024269] [<ffffffff8172acc2>] put_device+0x12/0x20
[ 1880.031254] [<ffffffff8172ba19>] device_unregister+0x19/0x20
[ 1880.038594] [<ffffffff81afb49d>] mce_cpu_callback+0xea/0x18b
[ 1880.043389] [<ffffffff81b08924>] notifier_call_chain+0x64/0xf0
[ 1880.051928] [<ffffffff81066c89>] __raw_notifier_call_chain+0x9/0x10
[ 1880.059077] [<ffffffff8103b50b>] __cpu_notify+0x1b/0x30
[ 1880.063894] [<ffffffff8103b530>] cpu_notify_nofail+0x10/0x20
[ 1880.071952] [<ffffffff81ae27dd>] _cpu_down+0x11d/0x2c0
[ 1880.078534] [<ffffffff81b01235>] ? printk+0x3c/0x3e
[ 1880.082662] [<ffffffff8103b7cb>] disable_nonboot_cpus+0x8b/0x110
[ 1880.091129] [<ffffffff81053f21>] kernel_power_off+0x21/0x50
[ 1880.098420] [<ffffffff81054220>] sys_reboot+0x110/0x220
[ 1880.104098] [<ffffffff8108efdd>] ? trace_hardirqs_on+0xd/0x10
[ 1880.112006] [<ffffffff81b04deb>] ? _raw_spin_unlock_irq+0x2b/0x50
[ 1880.119181] [<ffffffff8106dc0d>] ? finish_task_switch+0x8d/0x1a0
[ 1880.126741] [<ffffffff8106dbce>] ? finish_task_switch+0x4e/0x1a0
[ 1880.134793] [<ffffffff81b02f0b>] ? __schedule+0x3db/0x890
[ 1880.140510] [<ffffffff81b0cfc7>] ? sysret_check+0x1b/0x56
[ 1880.148101] [<ffffffff8160d33e>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[ 1880.156706] [<ffffffff81b0cfa2>] system_call_fastpath+0x16/0x1b
[ 1880.162885] ---[ end trace d8faf9d3af9f23e8 ]---
[ 1880.171148] Power down.
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 2
model name : QEMU Virtual CPU version 0.12.5
stepping : 3
microcode : 0x1
cpu MHz : 2800.047
cache size : 4096 KB
fpu : yes
fpu_exception : yes
cpuid level : 4
wp : yes
flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl pni cx16
tsc_deadlin _timer hypervisor lahf_lm
bogomips : 5600.09
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
--
tixxdz
http://opendz.org
next reply other threads:[~2012-01-10 23:57 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:00 Djalal Harouni [this message]
2012-01-12 14:22 ` x86/mce: machine check warning during poweroff Ming Lei
2012-01-13 20:22 ` Srivatsa S. Bhat
2012-01-13 20:34 ` Justin P. Mattock
2012-01-13 20:37 ` Linus Torvalds
2012-01-13 20:53 ` Srivatsa S. Bhat
2012-01-13 21:08 ` Linus Torvalds
2012-01-13 21:24 ` Andi Kleen
2012-01-13 21:38 ` Justin P. Mattock
2012-01-13 22:06 ` Srivatsa S. Bhat
2012-01-13 22:17 ` Alan Stern
2012-01-13 22:18 ` Srivatsa S. Bhat
2012-01-13 23:13 ` Andi Kleen
2012-01-14 0:44 ` Dirk Gouders
2012-01-13 23:02 ` Linus Torvalds
2012-01-13 23:27 ` Srivatsa S. Bhat
2012-01-14 0:05 ` Linus Torvalds
2012-01-14 2:41 ` Srivatsa S. Bhat
2012-01-14 2:53 ` Linus Torvalds
2012-01-14 3:05 ` Srivatsa S. Bhat
2012-01-14 3:10 ` Linus Torvalds
2012-01-14 3:18 ` Srivatsa S. Bhat
2012-01-14 3:41 ` Linus Torvalds
2012-01-14 5:15 ` Tony Luck
2012-01-14 14:49 ` Greg KH
2012-01-14 16:30 ` Alan Stern
2012-01-14 20:45 ` Jeff Chua
2012-01-15 2:05 ` Tony Luck
2012-01-15 2:34 ` Greg KH
2012-01-15 3:36 ` Alan Stern
2012-01-16 18:15 ` Greg KH
2012-01-16 18:11 ` Greg KH
2012-01-16 18:27 ` Luck, Tony
2012-01-16 18:34 ` Greg KH
2012-01-16 18:42 ` Kay Sievers
2012-01-17 2:21 ` Suresh Siddha
2012-01-17 9:52 ` Srivatsa S. Bhat
2012-01-17 16:15 ` Jeff Chua
2012-01-17 16:36 ` Srivatsa S. Bhat
2012-01-18 3:17 ` Suresh Siddha
2012-01-18 10:19 ` Srivatsa S. Bhat
2012-01-18 13:15 ` Srivatsa S. Bhat
2012-01-18 13:32 ` Sergey Senozhatsky
2012-01-18 22:08 ` Suresh Siddha
2012-01-19 7:50 ` Sergey Senozhatsky
2012-01-19 12:02 ` Srivatsa S. Bhat
2012-01-20 2:28 ` Suresh Siddha
2012-01-23 8:43 ` Peter Zijlstra
2012-01-26 20:27 ` [tip:sched/urgent] sched/nohz: Fix nohz cpu idle load balancing state with cpu hotplug tip-bot for Suresh Siddha
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=20120111000051.GA28874@dztty \
--to=tixxdz@opendz.org \
--cc=ak@linux.intel.com \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tony.luck@intel.com \
/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