From: Stefan Biereigel <security@biereigel-wb.de>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Stefan Biereigel <stefan@biereigel.de>,
lenb@kernel.org, rjw@rjwysocki.net,
Lan Tianyu <lantianyu1986@gmail.com>
Subject: Re: [REGRESSION 3.14-rc6] Samsung N150 lid does not "open" after suspend to RAM.
Date: Mon, 24 Mar 2014 12:19:13 +0100 [thread overview]
Message-ID: <533014B1.4030307@biereigel-wb.de> (raw)
In-Reply-To: <CAOLK0pxh4b3uzjD4jaPssD66K8g33uqahV1SzOAJAmQmnY4XqQ@mail.gmail.com>
Hi,
thank you for the suggestion. The patch resolves the issue on my N150
when applied to a clean 3.14-rc7. Anyways I'm wondering if similar
problems to mine now exist on the Samsung Series 7/9 notebooks?
Is any further action from my part required?
Regards,
Stefan
Am 24.03.2014 10:30, schrieb Lan Tianyu:
> Please try the following patch.
>
> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
> index d7d32c2..9239527 100644
> --- a/drivers/acpi/ec.c
> +++ b/drivers/acpi/ec.c
> @@ -1027,8 +1027,13 @@ static struct dmi_system_id ec_dmi_table[] __initdata = {
> DMI_MATCH(DMI_SYS_VENDOR, "ASUSTek Computer Inc."),
> DMI_MATCH(DMI_PRODUCT_NAME, "L4R"),}, NULL},
> {
> - ec_clear_on_resume, "Samsung hardware", {
> - DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD.")}, NULL},
> + ec_clear_on_resume, "Samsung NP530U3B", {
> + DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "530U3BI/530U4BI/530U4BH"),}, NULL},
> + {
> + ec_clear_on_resume, "Samsung NP530U3C", {
> + DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "530U3C/530U4C/532U3C"),}, NULL},
> {},
> };
>
>
>
>
> 2014-03-24 15:50 GMT+08:00 Stefan Biereigel <security@biereigel-wb.de>:
>> Hi,
>>
>> starting with 3.14-rc6, the lid on my Samsung N150 behaves weird: My
>> system is set up, so that it should suspend to RAM as soon as the lid is
>> closed. Beginning with 3.14-rc6, the lid goes from "open" to "closed"
>> correctly the first time (and the system suspends), but after resuming
>> from standby (by opening the lid), the lid does not change to "open" again.
>> Of course, closing the lid again does not induce suspend to RAM then.
>> Opening the lid now (while not sleeping), makes ACPI notify the opening,
>> so I guess ACPI "misses" or discards the lid open event from the EC when
>> coming from sleep.
>> Now, closing the lid again does induce suspend to RAM. This behaviour is
>> reproducible: every other time, suspending works.
>>
>> This behaviour seems to be introduced by commit ad332c8a: ACPI / EC:
>> Clear stale EC events on Samsung systems.
>> Which was introduced after 3.14-rc5.
>>
>> When opening the lid to resume from standby, i see in dmesg:
>> Mar 23 22:12:04 little1 kernel: [ 7630.932074] ACPI : EC: 1 stale EC
>> events cleared
>> (which comes from drivers/acpi/ec.c)
>>
>> Seems to me, that the "open" event is cleared from the EC, but also
>> discarded instead of passed on. Shouldn't the correct behaviour be to
>> report all the pending events, read from the EC, as ACPI events? Can you
>> point me in a direction for fixing the issue cleanly, then I will try to
>> find a solution and prepare a patch for this issue.
>>
>> Best regards,
>> Stefan
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2014-03-24 11:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 7:50 [REGRESSION 3.14-rc6] Samsung N150 lid does not "open" after suspend to RAM Stefan Biereigel
2014-03-24 9:30 ` Lan Tianyu
2014-03-24 11:19 ` Stefan Biereigel [this message]
2014-03-25 9:34 ` Lan Tianyu
2014-03-25 9:43 ` Stefan Biereigel
2014-03-25 13:23 ` Kieran Clancy
2014-03-25 13:53 ` Juan Manuel Cabo
2014-03-25 16:07 ` Stefan Biereigel
2014-03-25 16:38 ` Stefan Biereigel
2014-03-25 20:24 ` Stefan Biereigel
2014-03-25 20:41 ` Juan Manuel Cabo
2014-03-25 22:56 ` Juan Manuel Cabo
2014-03-26 10:42 ` Stefan Biereigel
2014-03-26 14:38 ` Kieran Clancy
2014-03-26 15:01 ` Rafael J. Wysocki
2014-03-26 19:56 ` Stefan Biereigel
2014-03-26 22:36 ` Kieran Clancy
2014-03-26 22:41 ` Stefan Biereigel
[not found] ` <CAM6oVw2v9ptr0c08uPiB_3z3e41VO+Vp3OhoHXiBxagAOfPBZA@mail.gmail.com>
2014-04-01 9:53 ` Kieran Clancy
2014-04-01 11:36 ` Nicolas Porcel
2014-04-01 11:58 ` Kieran Clancy
2014-04-01 12:18 ` Nicolas Porcel
2014-04-01 18:02 ` Nicolas Porcel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533014B1.4030307@biereigel-wb.de \
--to=security@biereigel-wb.de \
--cc=lantianyu1986@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stefan@biereigel.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox