> Do you use the microcode driver?
No.
I'm in the middle of bisecting. Strange enough the symptoms change as I go.
Some commits manage to suspend to RAM, but hang at resume.
Marcus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Friday, 23 March 2007 10:14, Marcus Better wrote:
> Marcus Better wrote:
> > The XFS workqueue patch [1] fixes my problem [2].
>
> > [1] http://permalink.gmane.org/gmane.linux.kernel/507616
> > [2] http://permalink.gmane.org/gmane.linux.kernel/505570
>
> Unfortunately it only fixed suspend to
On Fri, Mar 23, 2007 at 10:14:11 +0100, Marcus Better wrote:
> Marcus Better wrote:
> > The XFS workqueue patch [1] fixes my problem [2].
>
> > [1] http://permalink.gmane.org/gmane.linux.kernel/507616
> > [2] http://permalink.gmane.org/gmane.linux.kernel/505570
>
> Unfortunately it only fixed
Marcus Better wrote:
> The XFS workqueue patch [1] fixes my problem [2].
> [1] http://permalink.gmane.org/gmane.linux.kernel/507616
> [2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to RAM. Suspend to disk still hangs
at "snapshotting system". Will
Marcus Better wrote:
The XFS workqueue patch [1] fixes my problem [2].
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to RAM. Suspend to disk still hangs
at snapshotting system. Will try to
On Fri, Mar 23, 2007 at 10:14:11 +0100, Marcus Better wrote:
Marcus Better wrote:
The XFS workqueue patch [1] fixes my problem [2].
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to
On Friday, 23 March 2007 10:14, Marcus Better wrote:
Marcus Better wrote:
The XFS workqueue patch [1] fixes my problem [2].
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
Unfortunately it only fixed suspend to RAM.
Do you use the microcode driver?
No.
I'm in the middle of bisecting. Strange enough the symptoms change as I go.
Some commits manage to suspend to RAM, but hang at resume.
Marcus
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Thomas Gleixner wrote:
> You said, that the breakage came between 2.6.20 and rc2. Can you bisect
> it ?
The XFS workqueue patch [1] fixes my problem [2].
Marcus
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
pgpv6EWLbYBMj.pgp
Thomas Gleixner wrote:
You said, that the breakage came between 2.6.20 and rc2. Can you bisect
it ?
The XFS workqueue patch [1] fixes my problem [2].
Marcus
[1] http://permalink.gmane.org/gmane.linux.kernel/507616
[2] http://permalink.gmane.org/gmane.linux.kernel/505570
pgpv6EWLbYBMj.pgp
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
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
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
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
On Sat, Mar 17, 2007 at 10:47:01PM +0100, Rafael J. Wysocki wrote:
> On Saturday, 17 March 2007 11:07, Thomas Meyer wrote:
> >...
> > 2.) The first suspend to disk works with no problems, but the second
> > suspend to disk in a row results in an oops:
> > ->resume_device ->
> >
On Sat, Mar 17, 2007 at 10:47:01PM +0100, Rafael J. Wysocki wrote:
On Saturday, 17 March 2007 11:07, Thomas Meyer wrote:
...
2.) The first suspend to disk works with no problems, but the second
suspend to disk in a row results in an oops:
-resume_device -
On Saturday, 17 March 2007 11:07, Thomas Meyer wrote:
> Thomas Gleixner schrieb:
> > 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
Thomas Gleixner schrieb:
> 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
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
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,
Thomas Gleixner schrieb:
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
On Saturday, 17 March 2007 11:07, Thomas Meyer wrote:
Thomas Gleixner schrieb:
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
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
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
24 matches
Mail list logo
