[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070518154507.30ebfdcb.akpm@linux-foundation.org>
Date: Fri, 18 May 2007 15:45:07 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christian Leber <christian@...er.de>
Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [BUG] acpi double resume and fail
On Fri, 18 May 2007 23:37:01 +0200
Christian Leber <christian@...er.de> wrote:
> Hello,
>
> i hit a problem with suspend to ram and especially resume.
> Hardware: Dell Latitude D810 (some Intel 915 with Intel Pentium M)
>
> With 2.6.19.7 suspend to ram works reliable, but with 2.6.20-rc4
> it stopped working reliable.
argh, that sounds like an ACPI regression.
> I still can suspend, but after the first resume it goes back to sleep
> directly again, when resuming again it works.
> After the second suspend it won't resume at all.
>
> The problem is that i can't try out the kernel versions <rc4, because
> rc1, rc2 and rc3 doesn't boot at all, so git-bisect also won't help.
>
> Has somebody an idea what i could try out?
>
> (the distribution is in this case ubuntu feisty)
>
The fact that bisection broke really does make it hard. What you would
need to do is to find the patch which fixed that doesn't-boot problem, then
reapply it each time you perform an iteration. That's all doable, if you
have the time. Use git-bisect for it.
Have you tested 2.6.21 and/or 2.6.22-rc1?
We had one other report earlier today that 2.6.22-rc1 does an immediate
resume after suspend-to-RAM - perhaps that is related.
Of course the alternative way of debugging this is just to debug it, rather
than the difficult bisecting. Perhaps an ACPI developer can help with
that.
-
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