From: Jiri Slaby <jirislaby@gmail.com>
To: Don Zickus <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: Re: hibernation hangs with ATA errors (lockup_detector bug)
Date: Fri, 03 Sep 2010 10:35:04 +0200 [thread overview]
Message-ID: <4C80B338.6020701@gmail.com> (raw)
In-Reply-To: <4C0B3E94.6020506@gmail.com>
On 06/06/2010 08:22 AM, Jiri Slaby wrote:
> On 06/02/2010 08:44 PM, Don Zickus wrote:
>> --- a/kernel/watchdog.c
>> +++ b/kernel/watchdog.c
>> @@ -550,8 +550,7 @@ cpu_callback(struct notifier_block *nfb, unsigned long action, void *hcpu)
>> break;
>> case CPU_ONLINE:
>> case CPU_ONLINE_FROZEN:
>> - if (watchdog_enable(hotcpu))
>> - return NOTIFY_BAD;
>> + watchdog_enable(hotcpu)
>
> This fixes the problem indeed.
Hi, was this fixed somehow? I still use this hunk and don't know if it
is needed:
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -524,7 +524,7 @@ cpu_callback(struct notifier_block *nfb, unsigned
long action, void *hcpu)
break;
case CPU_ONLINE:
case CPU_ONLINE_FROZEN:
- err = watchdog_enable(hotcpu);
+ watchdog_enable(hotcpu);
break;
#ifdef CONFIG_HOTPLUG_CPU
case CPU_UP_CANCELED:
thanks,
--
js
next prev parent reply other threads:[~2010-09-03 8:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 14:22 hibernation hangs with ATA errors (lockup_detector bug) Jiri Slaby
2010-06-01 13:50 ` 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 [this message]
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=4C80B338.6020701@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).