[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1311222322480.30673@ionos.tec.linutronix.de>
Date: Fri, 22 Nov 2013 23:27:50 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
cc: Francis Moreau <francis.moro@...il.com>,
Jingoo Han <jg1.han@...sung.com>,
'Borislav Petkov' <bp@...en8.de>,
'Wei WANG' <wei_wang@...lsil.com.cn>,
'LKML' <linux-kernel@...r.kernel.org>,
'Samuel Ortiz' <sameo@...ux.intel.com>,
'Chris Ball' <cjb@...top.org>
Subject: Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64)
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
> > Ok, I've finally managed to find out the bad commit:
> > ad07277e82dedabacc52c82746633680a3187d25: ACPI / PM: Hold acpi_scan_lock
> > over system PM transitions
> >
> > I verified that the parent commit doesn't have the problem.
>
> Interesting.
>
> > Rafael, you're the man now ;)
>
> I kind of don't see how that commit may result in behavior that you
> described earlier in the thread.
>
> You get a memory corruption that seems to have started to happen because
> we're holding an additional lock over suspend resume now. Something's fishy
> on that machine and we need to figure out what it is.
The hickup happens in the timer softirq.
@Francis: Did you try to enable DEBUG_OBJECTS.*. If not please give it
a try.
Thanks,
tglx
--
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