[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200906301448.55209.rjw@sisk.pl>
Date: Tue, 30 Jun 2009 14:48:54 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Johannes Stezenbach <js@...21.net>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13644] hibernation/swsusp lockup due to acpi-cpufreq
On Tuesday 30 June 2009, Johannes Stezenbach wrote:
> On Mon, Jun 29, 2009 at 02:31:01AM +0200, Rafael J. Wysocki wrote:
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13644
> > Subject : hibernation/swsusp lockup due to acpi-cpufreq
> > Submitter : Johannes Stezenbach <js@...21.net>
> > Date : 2009-06-16 01:27 (13 days old)
> > References : http://lkml.org/lkml/2009/6/15/630
> > Handled-By : Rafael J. Wysocki <rjw@...k.pl>
>
> I tested v2.6.31-rc1-228-g2bfdd79 and the bug is still there.
> It actually got worse, the local_irq_save/restore workaround
> in kernel/up-c (http://lkml.org/lkml/2009/6/16/333) doesn't fix it
> anymore, it hangs at suspend before writing out the image.
>
> With the up.c workaround (including a
> WARN_ON_ONCE(irqs_disabled() && !oops_in_progress);)
> applied and no_console_suspend I captured the attached
> output using a crappy webcam. (Without the workaround
> there is a huge spew of warnings about irqs enabled
> unexpectedly.) I guess the interesting part is
>
> pm_op(): pci_pm_thaw returns -16
> PM: Device 0000:00:00.0 failed to thaw: error -16
Hmm, it looks like we fail to thaw the host bridge.
> (PCI info is in http://lkml.org/lkml/2009/6/15/630)
Well, thanks for the update. I'll do my best to fix the cpufreq suspend
before 2.6.31 final.
Best,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists