Bug 56451
Summary: | Samsung NP530U3B and NP535U3C: Resume from suspend when lid is open doesn't work | ||
---|---|---|---|
Product: | ACPI | Reporter: | mephisto (mephisto.pheles.nyan) |
Component: | Other | Assignee: | Lan Tianyu (tianyu.lan) |
Status: | CLOSED DUPLICATE | ||
Severity: | normal | CC: | aaron.lu, mephisto.pheles.nyan, tianyu.lan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | No | Bisected commit-id: | |
Attachments: |
acpi_listen
/proc/acpi/wakeup acpidump |
Description
mephisto
2013-04-10 08:55:01 UTC
Created attachment 97961 [details]
acpi_listen
Created attachment 97971 [details]
/proc/acpi/wakeup
acpidump please: # acpidump > acpidump.out Thanks. Hi Aaron: All info in the bug45461 "Samsung NP530U3B and NP535U3C lid close does not suspend". They are sister bugs ... I have found a strange things about the lids state.. I just disassembled this acpidump attached there: https://bugzilla.kernel.org/attachment.cgi?id=82311 And the LID device does not have any _PRW method indicating it is able to wake up the system from a sleeping state, so I think this "problem" is expected. Hi mephisto, Did you used to be able to resume the system on LID open? Or if you have windows, can windows resume from suspend on LID open? Thanks. Aaron, yes, it can. Created attachment 98091 [details]
acpidump
root@mephisto-book:/home/mephisto# acpidump > acpidump.out
Wrong checksum for FADT!
From which kernel you start to have this problem? All kernels. Now, i'm on Ubuntu 13.04 (3.8 kernel). So by "it can", you mean under windows, right? Yes. Under Windows all work perfectly. Then perhaps you can try to enable wakeup for the devices listed in /proc/acpi/wakeup, one by one see if any of them makes a difference. Nothing works. Hi: Sorry for late response. Does this issue happen after following operations? - power off the laptop - press the button at the bottom for 10 seconds - boot in linux - should work Your machine is NP530U3B, right? BTW, we try to fixing all acpi related bugs but for some bios issues, specially some machines' manufacture only care Windows. We really have no good way. Please understand. Thanks. This is fix it, but for a short time. 4-5 days. Ok. So this is as same as bug45461. So close this bug as duplicate. Ok? No problem, I will explain :) *** This bug has been marked as a duplicate of bug 45461 *** |