[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090616224431.GA14186@sig21.net>
Date: Wed, 17 Jun 2009 00:44:31 +0200
From: Johannes Stezenbach <js@...21.net>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: venkatesh.pallipadi@...el.com, rjw@...k.pl,
linux-kernel@...r.kernel.org, davej@...hat.com, pavel@....cz,
linux-acpi@...r.kernel.org, lenb@...nel.org, arjan@...radead.org,
tglx@...utronix.de
Subject: Re: 2.6.30: hibernation/swsusp lockup due to acpi-cpufreq
On Tue, Jun 16, 2009 at 02:09:23PM -0700, Andrew Morton wrote:
>
> Right, so it's the suspend-must-disable-local-interrupts thing. Again.
> create_image()'s local_irq_disable().
>
> It was wrong to call work_on_cpu() with lcoal interrupts disabled, and
> it's now wrong to call smp_call_function_single() with local interrupts
> disabled. It's just that smp_call_function_single() warns while
> work_on_cpu() didn't.
>
> That all explains the warning But afaik we still don't know why your
> machine actually failed. Perhaps it is a side-efect of emitting the
> warning when the console is in a weird state?
smp_call_function_single() enables irqs and hibernate doesn't like that?
BTW, I have no other UP machine to test with, but I reported
in another thread that a !SMP kernel (or a SMP kernel
with maxcpus=0 parameter) does not boot at all on
my destop machine, see
http://lkml.org/lkml/2009/6/12/468
No idea if I should be worried about this since the
SMP kernel now works fine, another hibernate problem
was solved in
http://lkml.org/lkml/2009/6/14/156
Johannes
--
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