linux-kernel - Re: 3.5-rc7 - can no longer wake up from suspend to RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL1RGDU8TVBkZ4yP=kjwqvGUsrnQcBGpLa_x-7c=Gu54piVwyw@mail.gmail.com>
Date:	Sat, 21 Jul 2012 15:11:03 -0700
From:	Roland Dreier <roland@...estorage.com>
To:	Tomasz Chmielewski <tch@...g.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 3.5-rc7 - can no longer wake up from suspend to RAM

On Wed, Jul 18, 2012 at 9:46 PM, Tomasz Chmielewski <tch@...g.org> wrote:
> After upgrading to 3.5-rc7, my laptop no longer wakes up reliable from suspend to RAM. 3.4.x worked fine.

FWIW, I've been having similar problems with 3.5-rc7.  With 3.5-rc6 my
laptop resumed fine, but since updating to -rc7, it often seems to just
sit there after opening the lid -- the moon/sleep LED stays on, and the
power LED smoothly cycles on and off, as if it's fast asleep.  Even pressing
the power button doesn't have any effect (until I hold down the power
button long enough to turn off).

I guess I'll start a bisection, but it's slow going because it takes multiple
tries to know for sure if a kernel is bad.

The only commit between rc6 and rc7 that looks like it might be related
is dc332fdf9f373a87b1e2f423b5b004b2a3c37e1a ("ACPI / PM: Leave
Bus Master Arbitration enabled for suspend/resume"), which apparently
fixes some other laptops.  But perhaps I'll try reverting that and see how
it goes.

 - R.
--
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/