[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1174485863.10840.80.camel@localhost.localdomain>
Date: Wed, 21 Mar 2007 15:04:22 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Marcus Better <marcus@...ter.se>
Cc: linux-kernel@...r.kernel.org, Andi Kleen <ak@...e.de>
Subject: Re: [PATCH] clockevents: Fix suspend/resume to disk hangs
On Tue, 2007-03-20 at 10:35 +0100, Marcus Better wrote:
> Thomas Gleixner wrote:
>
> > I finally found a dual core box, which survives suspend/resume without
> > crashing in the middle of nowhere. Sigh, I never figured out from the
> > code and the bug reports what's going on.
> >
> > The observed hangs are caused by a stale state transition of the clock
> > event devices, which keeps the RCU synchronization away from completion,
> > when the non boot CPU is brought back up.
>
> This didn't fix the suspend problems on my Thinkpad R60. (Sorry for
> nagging - please let me know if I can assist in debugging this...)
I did not expect that it fixes your problem. clockevents are only used
in arch/i386 right now. You are running a 64 bit kernel, so a change of
your problem would have been very surprising.
You said, that the breakage came between 2.6.20 and rc2. Can you bisect
it ?
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