From: Jiri Slaby <jirislaby@gmail.com>
To: dzickus@redhat.com
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
linux-ide@vger.kernel.org
Subject: hibernation hangs with ATA errors (lockup_detector bug)
Date: Mon, 31 May 2010 16:22:00 +0200 [thread overview]
Message-ID: <4C03C608.1040600@gmail.com> (raw)
Hi,
with -next I get the following errors while trying to hibernate in
qemu-kvm after the image is stored on disk:
sd 0:0:0:0: [sda] Starting disk
sd 0:0:1:0: [sdb] Starting disk
e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
ata1.00: configured for MWDMA2
ata1.01: configured for MWDMA2
PM: thaw of devices complete after 168.017 msecs
ata2.01: qc timeout (cmd 0xec)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
sd 0:0:1:0: [sdb] Stopping disk
sd 0:0:0:0: [sda] Stopping disk
uhci_hcd 0000:00:01.2: PCI INT D disabled
e1000 0000:00:03.0: PCI INT A disabled
ata2.01: qc timeout (cmd 0xec)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2.01: qc timeout (cmd 0xec)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
...
I bisected it down to:
commit 58687acba59266735adb8ccd9b5b9aa2c7cd205b
Author: Don Zickus <dzickus@redhat.com>
Date: Fri May 7 17:11:44 2010 -0400
lockup_detector: Combine nmi_watchdog and softlockup detector
The new nmi_watchdog (which uses the perf event subsystem) is very
similar in structure to the softlockup detector. Using Ingo's
suggestion, I combined the two functionalities into one file:
kernel/watchdog.c.
...
The config difference against 58687acb^:
--- .config.old 2010-05-31 16:01:51.727312636 +0200
+++ .config 2010-05-31 16:11:08.682136175 +0200
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.34-rc7
-# Mon May 31 16:01:51 2010
+# Mon May 31 16:11:08 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
@@ -2133,7 +2133,7 @@
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
-CONFIG_NMI_WATCHDOG=y
+CONFIG_LOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
'nowatchdog' parameter helps.
$ grep PERF .config
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_HAVE_PERF_EVENTS_NMI=y
--
js
next reply other threads:[~2010-05-31 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 14:22 Jiri Slaby [this message]
2010-06-01 13:50 ` hibernation hangs with ATA errors (lockup_detector bug) Don Zickus
2010-06-01 14:46 ` Jiri Slaby
2010-06-01 15:26 ` Don Zickus
2010-06-02 18:44 ` Don Zickus
2010-06-02 19:13 ` Frederic Weisbecker
2010-06-02 19:43 ` Frederic Weisbecker
2010-06-03 8:17 ` Tejun Heo
2010-06-02 21:03 ` Don Zickus
2010-06-06 6:22 ` Jiri Slaby
2010-09-03 8:35 ` Jiri Slaby
2010-09-03 13:56 ` Don Zickus
2010-09-24 15:10 ` Jiri Slaby
2010-09-24 18:24 ` Don Zickus
2010-09-24 19:19 ` Don Zickus
2010-09-25 19:30 ` Jiri Slaby
2010-09-27 14:21 ` Don Zickus
2010-06-01 14:51 ` Jiri Slaby
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=4C03C608.1040600@gmail.com \
--to=jirislaby@gmail.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.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).