Sorry for the late answer. The patch that caused only applies to Samsung laptops as the code is only executed on laptops reporting a Samsung brand when using dmidecode. I'll answer you more precisly on your thread.
As for the patch, it has been committed in the stable branch of linux-3.14, so it should be available in the next release. I am still maintaining the patched kernel in the AUR repository, but I will delete it as soon as the patch is available in the archlinux official kernel. I'll let you know when it is done.
Thank you for your patience.
Nicolas
]]>Thanks for the work you put in this.
edit: Contrary to what I had said before, I just installed the kernel and still faced the same problem.
I will open a new thread for the thinkpad (and paste the link here).
The patch will soon be communicated to the upstream, so it should be included soon in the latest kernel.
I created a custom kernel in AUR that include the patch. Here is the link: linux-samsung-netbook.
I hope this will be useful. I will tell you when the patch is released in the archlinux binary kernel using this thread, so that you can switch back to it.
]]>Or use linux-lts.
Actually that is what I do. It takes a lot of time to compile custom kernel on Atom N270 CPU.
]]>@knedlyk:
As you can read above, the patch is not submitted yet, but you can build your own kernel including it if you want to. Or use linux-lts.
Works for me, the patch! :-)
($ uname -a
Linux archie 3.13.8-1-ARCH #2 SMP PREEMPT Sat Apr 5 22:19:19 CEST 2014 i686 GNU/Linux
)
Thanks for submitting it!
How can I know when this patch is included?
Before that, updating the kernel doesn't seem to be useful to me, compiling it by myself just takes too long...
You need to apply the patch in the attachment of the comment (attachment 131151). If you use my PKGBUILD file (the one I sent via pastebin), you need to call it ec_clear_process.patch. Please tell me if it works or not, otherwise I need to prevent the kernel team to modify the patch.
This bug is not due to systemd. We should expect any power manager to behave the same way if they are configured to suspend the laptop after closing the lid.
]]>I tested the patch on linux 3.13.7 and it works just great. I'll try to upload my configuration to AUR (although I don't have much time and I that would be my first time). I can at least send you the PKGBUILD: http://bpaste.net/show/xLBQcAW9Z0vUa5BNlpBE/
Here is a quick (and maybe not that good) explanation of the problem for those interested (skip it if you don't care):
The patch that causes the problem fix a very critical problem on new samsung laptops. Those computers continue to report acpi events when they are in suspend mode but do not send them to the kernel (the processor being off), even after resuming. If too many events are recorded, the acpi controller get stuck (and it looks like it is permanent, because it affects windows too). So the solution is to clear the old acpi events after resuming. The problem is that old samsung laptop that do not have this problem fail to send the lid open event after resuming (this event is reported before resuming, but not after), so it is cleared because of the new patch. The patch I sent will process these evens instead of ignoring them. I hope this is clear.
For the full thread, here are the link, from the linux-acpi mailing list that explain why this happens: http://marc.info/?l=linux-acpi&m=139564741817605&w=2
The fix won't be available in the mainline before a long time because of the very critical status of the previous commit, which fixes a problem a lot worse that the one it creates. So it has to be carefully tested
If you have any problem or questions don't hesitate to contact me. I subscribed to the topic so I should receive the notifications now.
]]>