From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ming Lei <tom.leiming@gmail.com>,
Djalal Harouni <tixxdz@opendz.org>,
Borislav Petkov <borislav.petkov@amd.com>,
Tony Luck <tony.luck@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
gouders@et.bocholt.fh-gelsenkirchen.de,
Marcos Souza <marcos.mage@gmail.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"tglx@linutronix.de" <tglx@linutronix.de>,
prasad@linux.vnet.ibm.com, Jeff Chua <jeff.chua.linux@gmail.com>,
Tejun Heo <tj@kernel.org>, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: x86/mce: machine check warning during poweroff
Date: Sat, 14 Jan 2012 03:48:27 +0530 [thread overview]
Message-ID: <4F10ADB3.7080409@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F10AB02.1010305@linux.vnet.ibm.com>
On 01/14/2012 03:36 AM, Srivatsa S. Bhat wrote:
> On 01/14/2012 03:08 AM, Justin P. Mattock wrote:
>
>>>
>>
>> this showed up using no_console_suspend
>>
>>
>> 131.875143] usb 5-1: device descriptor read/64, error -110
>> [ 140.599340] PM: Syncing filesystems ... done.
>> [ 140.815981] PM: Preparing system for mem sleep
>> [ 140.829117] Freezing user space processes ... (elapsed 0.01 seconds)
>> done.
>> [ 140.840150] Freezing remaining freezable tasks ...
>> [ 147.079160] usb 5-1: device descriptor read/64, error -110
>> [ 147.282166] usb 5-1: new full-speed USB device number 6 using uhci_hcd
>> [ 157.686165] usb 5-1: device not accepting address 6, error -110
>> [ 157.788183] usb 5-1: new full-speed USB device number 7 using uhci_hcd
>> [ 160.849310]
>> [ 160.849320] Freezing of tasks failed after 20.00 seconds (1 tasks
>> refusing to freeze, wq_busy=0):
>
>> [ 160.849460] khubd D f5d90020 0 20 2 0x00000000
>> [ 160.849471] f5d95d50 00000046 f5d095d0 f5d90020 00000000 c16ec3c0
>> bce8e78a 00000024
>> [ 160.849488] c16ec3c0 bce7b7f6 00000024 f60063c0 f5d09170 f5d95d20
>> c120490b c1039aa6
>> [ 160.849505] 00000000 00000046 c1721180 00000296 f5d95d70 f5d95d40
>> c1465208 00000000
>> [ 160.849521] Call Trace:
>> [ 160.849538] [<c120490b>] ? do_raw_spin_lock+0x3b/0xf0
>> [ 160.849548] [<c1039aa6>] ? lock_timer_base.isra.24+0x26/0x50
>> [ 160.849558] [<c1465208>] ? _raw_spin_lock_irqsave+0x58/0x70
>> [ 160.849567] [<c1204a4e>] ? do_raw_spin_unlock+0x4e/0x90
>> [ 160.849574] [<c1463c30>] schedule+0x30/0x50
>> [ 160.849582] [<c1461b7f>] schedule_timeout+0x10f/0x1f0
>> [ 160.849589] [<c10396f0>] ? usleep_range+0x40/0x40
>> [ 160.849597] [<c1463ae0>] wait_for_common+0xb0/0x120
>> [ 160.849605] [<c1053bb0>] ? try_to_wake_up+0x260/0x260
>> [ 160.849614] [<c1463bdd>] wait_for_completion_timeout+0xd/0x10
>> [ 160.849624] [<c13250e1>] usb_start_wait_urb+0xb1/0xe0
>> [ 160.849632] [<c10e0101>] ? sys_swapon+0xab1/0xc50
>> [ 160.849640] [<c1325308>] usb_control_msg+0xb8/0xf0
>> [ 160.849648] [<c12ad1e8>] ? _dev_info+0x28/0x30
>> [ 160.849656] [<c131e627>] hub_port_init+0x627/0x710
>> [ 160.849664] [<c131d396>] ? usb_set_device_state+0x76/0x130
>> [ 160.849672] [<c1320906>] hub_thread+0x626/0x1080
>> [ 160.849681] [<c10515a1>] ? finish_task_switch+0x31/0xf0
>> [ 160.849688] [<c14635c0>] ? __schedule+0x3b0/0x7b0
>> [ 160.849698] [<c10490c0>] ? __init_waitqueue_head+0x50/0x50
>> [ 160.849705] [<c1050ef9>] ? complete+0x49/0x60
>> [ 160.849713] [<c13202e0>] ? usb_remote_wakeup+0x40/0x40
>> [ 160.849720] [<c1048928>] kthread+0x78/0x80
>> [ 160.849728] [<c10488b0>] ? __init_kthread_worker+0x60/0x60
>> [ 160.849736] [<c146b0fe>] kernel_thread_helper+0x6/0xd
>> [ 160.849755]
>> [ 160.849759] Restarting tasks ... done.
>> [ 160.865733] power_supply BAT0: uevent
>> [ 160.865737] power_supply BAT0: POWER_SUPPLY_NAME=BAT0
>> [ 160.886551] power_supply BAT0: prop STATUS=Full
>> [ 160.886562] power_supply BAT0: prop PRESENT=1
>> [ 160.886570] power_supply BAT0: prop TECHNOLOGY=Unknown
>> [ 160.886577] power_supply BAT0: prop CYCLE_COUNT=0
>>
>> I can supply full dmesg if needed.
>> a bisect on this should not take too long, just need the time to do so.
>>
>> last good kernel I have here is: 3.2.0-06541-gf33180c
>>
>
> Freezing failure is a totally different problem. Freezing happens much
> before CPUs are taken offline and even before devices are suspended.
> But yes, if freezing fails, suspend fails too (it is aborted rather).
> And freezing failures are typically a bit harder to trigger since they
> occur due to some race conditions. But the suspend failure problem
> discussed earlier in this thread (while discussing the MCE warnings) is a
> deterministic thing and very easily reproducible.
>
So, looks like we have got 2 problems: a)freezing failure apparently due to
usb related code b) suspend failure due to MCE overhaul.
Adding Tejun and Alan Stern to Cc.
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2012-01-13 22:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 0:00 x86/mce: machine check warning during poweroff Djalal Harouni
2012-01-12 14:22 ` 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 [this message]
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=4F10ADB3.7080409@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=borislav.petkov@amd.com \
--cc=gouders@et.bocholt.fh-gelsenkirchen.de \
--cc=gregkh@suse.de \
--cc=jeff.chua.linux@gmail.com \
--cc=justinmattock@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcos.mage@gmail.com \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=tixxdz@opendz.org \
--cc=tj@kernel.org \
--cc=tom.leiming@gmail.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).