Bug#700513: linux-base: Cannot resume after suspending (laptop model HP CQ61 410SH)

On Sat, Feb 16, 2013 at 5:30 PM, Ben Hutchings <ben@decadent.org.uk> wrote:

On Sat, 2013-02-16 at 12:40 -0600, Daniel wrote:
> Not sure if I'm doing this right, but I'm reporting the results here.
>
>
> On Thu, Feb 14, 2013 at 9:25 PM, Ben Hutchings <ben@decadent.org.uk>
> wrote:
> On Thu, 2013-02-14 at 08:27 -0600, Daniel wrote:
> >
> >
> >
> > On Wed, Feb 13, 2013 at 11:28 PM, Ben Hutchings
> <ben@decadent.org.uk>
> > wrote:
> > Control: tag -1 moreinfo
> >
> > On Wed, 2013-02-13 at 11:59 -0600, ddshore wrote:
> > > Package: linux-base
> > > Version: 3.4~bpo60+1
> > > Severity: normal
> > >
> > > After suspending the laptop, and attempting to
> resume, I get
> > a black screen
> > > with the power and wifi icons turned on. I have
> tried using
> > different versions
> > > of the Linux Kernel,
> >
> >
> > Which versions?
> >
> >
> > 2.6.32-5-686 and 3.2.0.0.bpo.4-rt-686-pae
>
>
> Could you also try 3.7-trunk-686-pae, from the experimental
> suite?
>
>
> Done, I just installed it without doing anything else (it mentioned
> that it may be missing some drivers).
> I still have the same error. Should I try anything else? The dmesg,
> or something like that?

dmesg from after boot would be helpful.

Attached, dmesg after a regular reboot.

Maybe the DSDT would also provide useful information. Install acpidump,
run 'acpidump -t DSDT > dsdt.dump' (as root), and attach dsdt.dump.

[...]

Now that you mention it, the guys at #linux had noticed something wrong with my dsdt tables, but I cannot remember what it was.

Im not attaching a dmesg after a suspend (unless you want me to). The first dmesgs from my bug report where after a suspend, but not with the newest kernel.

From what you have seen now, where do we stand? Do you think this is something that is fixable through some changes in configuration, or a more complex problem?

> OK, so I tried:
> echo freezer > /sys/power/pm_test
> echo mem > /sys/power/state
>
>
> echo devices > /sys/power/pm_test
> echo mem > /sys/power/state
>
>
> echo platform > /sys/power/pm_test
> echo mem > /sys/power/state
>
>
> echo processors > /sys/power/pm_test
> echo mem > /sys/power/state
>
>
> echo core > /sys/power/pm_test
>
>
> echo mem > /sys/power/state
>
>
> For all of them, I get this:
> ata1: softreset failed (device not ready)
> ata2: softreset failed (device not ready)
>
>
>
> But it always comes back to live. Am I doing it right?
> I can't find if there is a log file that contains the results of these
> tests.

There's no special log. This suggests that the kernel is mostly doing
the right thing, but something goes wrong with the last stage where the
kernel calls the BIOS to power-off most of the system.

Ben.

--
Ben Hutchings
Computers are not intelligent. They only think they are.