linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Jiri Slaby <jirislaby@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: Wed, 2 Jun 2010 21:13:40 +0200	[thread overview]
Message-ID: <20100602191336.GA5164@nowhere> (raw)
In-Reply-To: <20100602184459.GA15159@redhat.com>

On Wed, Jun 02, 2010 at 02:44:59PM -0400, Don Zickus wrote:
> On Tue, Jun 01, 2010 at 04:46:28PM +0200, Jiri Slaby wrote:
> > On 06/01/2010 03:50 PM, Don Zickus wrote:
> > > On Mon, May 31, 2010 at 04:22:00PM +0200, Jiri Slaby wrote:
> > >> Hi,
> > >>
> > >> with -next I get the following errors while trying to hibernate in
> > >> qemu-kvm after the image is stored on disk:
> > > 
> > > Is this the host that is hibernating or the guest?
> > 
> > Guest.
> > 
> > > KVM guests don't emulate the performance counters, so the nmi piece
> > > shouldn't be functioning and the soft lockup piece just sits on top of an
> > > hrtimer, so off the top of my head it is hard to imagine it intefering
> > > with a sata driver.
> > > 
> > > I'll need your whole boot up log to see how the lockup detector
> > > initialized itself.
> 
> Ok, so I found out what is causing the problem, not entirely sure why or
> what the right fix is, but this patch should do the trick.
> 
> This is probably one of those fixing the symptoms but not the problem patch,
> but I don't know enough about suspend/resume to understand what the real
> problem is.


So the problem is that we stop the cpu hotplug notifying, I guess this prevents
some ata callbacks to execute in the cpu hotplug notifier and then provoke this
crash.

The patch looks ok, but I think you should at least print a message in such
case of watchdog failure.

Thanks.



> 
> ---->SNIP<---------------------
> [lockup detector] don't return NOTIFY_BAD when cpu goes online for suspend
> 
> KVM guests do not support performance counter emulation, so if the nmi
> watchdog piece is compiled in, it will always fail during boot.  The
> failure returns NOTIFY_BAD when the cpu goes online in the cpu notifier
> callback.  Returning NOTIFY_BAD causes hibernation to do really bad
> things, so avoid doing that.
> 
> The cpu failure shouldn't be a critical failure anyway, so returning
> NOTIFY_BAD was probably overstating things.
> 
> Signed-off-by: Don Zickus <dzickus@redhat.com>
> 
> 
> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> index 6b7fad8..fda9770 100644
> --- 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)
>  		break;
>  #ifdef CONFIG_HOTPLUG_CPU
>  	case CPU_UP_CANCELED:


  reply	other threads:[~2010-06-02 19:13 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 [this message]
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=20100602191336.GA5164@nowhere \
    --to=fweisbec@gmail.com \
    --cc=dzickus@redhat.com \
    --cc=jirislaby@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).