You are not logged in.
Pages: 1
Topic closed
Hi,
I'm new to the forum, although I've been using Archlinux for quite a while.
My problem is really strange, it all started after my netbook went out of battery while compiling (Octave, if it matters).
Now it's unusable. When I boot it up, it keeps going to sleep state S3 every 10sec. I've to keep on waking it up (by pressing any key), despite this, all seems normal and in the end it reaches desktop (but keeps suspending).
Anybody has any idea as to where to look at?
dmesg only shows that it suddenly goes to S3 state, but it does so cleanly, as if something requests for it.
Thank you very much, sorry I can't give much more information now, will try to get some logs to show you.
EDIT-Unsolved:
While writing the post I had an idea. It turned out that Laptop-mode-tools got bugged (Don't know how/why) and it was issuing the suspend command. I disabled it with:
systemctl disable laptop-mode
and it got fixed.
EDIT2:
I'm really sorry, seems that it was just bad luck, though I had it fixed.
Turns out that when disabling laptop-mode service, the service that gives this random behavior got stopped, but it had nothing to do with Laptop-Mode. I uninstalled it, restarted and I again saw the same erratic behavior, the system keeps suspending.
I can go to run level 3 without problems, so it must be another service causing the anomaly.
Could someone point me where/how to find the service that arises the problem?
Last edited by Trinket (2014-03-05 16:51:35)
Offline
I wanted to add the logs I found in the journal regarding my issue:
Mar 06 17:05:47 netbook systemd[1]: Starting Getty on tty1...
Mar 06 17:05:47 netbook systemd[1]: Started Getty on tty1.
Mar 06 17:05:47 netbook systemd[1]: Starting Login Prompts.
Mar 06 17:05:47 netbook systemd[1]: Reached target Login Prompts.
Mar 06 17:05:47 netbook systemd-logind[214]: New seat seat0.
Mar 06 17:05:47 netbook systemd[1]: Started Login Service.
Mar 06 17:05:47 netbook systemd-logind[214]: Watching system buttons on /dev/input/event3 (Power Button)
Mar 06 17:05:47 netbook systemd-logind[214]: Watching system buttons on /dev/input/event4 (Video Bus)
Mar 06 17:05:47 netbook systemd-logind[214]: Watching system buttons on /dev/input/event0 (Power Button)
Mar 06 17:05:47 netbook systemd-logind[214]: Watching system buttons on /dev/input/event1 (Lid Switch)
Mar 06 17:05:47 netbook systemd-logind[214]: Watching system buttons on /dev/input/event2 (Sleep Button)
Mar 06 17:05:47 netbook systemd-logind[214]: Suspending...
Mar 06 17:05:47 netbook systemd[1]: Started Initialize hardware monitoring sensors.
Mar 06 17:05:47 netbook systemd[1]: Starting Sleep.
Mar 06 17:05:47 netbook systemd[1]: Reached target Sleep.
Mar 06 17:05:47 netbook systemd[1]: Starting Suspend...
Mar 06 17:05:48 netbook systemd-sleep[218]: Suspending system...
I have pasted the full log in pastebin:
http://pastebin.com/saNcdUkg
If it helps, in run level 3 (rescue mode) acpi_listen doesn't output anything, so I assume it's not hardware related.
Offline
Try setting "HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/logind.conf
Online
This was driving me mad too. It all started yesterday. I powered on my netbook and waited for arch too finish loading. Now, I might be saying laughable stuff, but I made a mistake and, thinking that arch had finished loading I pressed some shortcuts I use, namely Alt+f Alt+i Alt+s. But arch hadn't finished loading. It was still fschck'ing. Then, constant suspending started. Having tried many things, I rebooted once more and I pressed again the Alt+s shortcut while arch was booting. After one more suspension, then the laptop managed to stay awake. I searched on the net. I found this thread, I followed Scimmia's advice and rebooted. And bingo! my laptop did me the favor of not suspending. Now, I do not know if this was due to my pressing alt+s during boot or due to Scimmia's advice, but it still is a weird issue.
Offline
Try setting "HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/logind.conf
That fixed it! Thank you a lot! Thought it was going to take a lot to find the error!
I just don't understand why that fixed it. Could you explain it a little bit so that it doesn't happen again?
If what I understand about that options is correct, wouldn't acpi_listen catch those events?
Offline
It's more a workaround/diagnosis than a fix. We now know that systemd/logind is what is causing it to suspend, but we don't know why yet. Try setting just one of them to figure out which one it is causing the problem. Once we know that, we might be able to figure out if it's a bug in logind or if there really is something sending it those acpi signals. I would expect acpi_listen to catch them, but I'm not sure.
Online
It's more a workaround/diagnosis than a fix. We now know that systemd/logind is what is causing it to suspend, but we don't know why yet. Try setting just one of them to figure out which one it is causing the problem. Once we know that, we might be able to figure out if it's a bug in logind or if there really is something sending it those acpi signals. I would expect acpi_listen to catch them, but I'm not sure.
I've narrowed it down to the "HandleLidSwitch=ignore" option. Without that the strange auto-suspend bug returns. Does it give you any clue as to where the problem is?
If I understand it correctly, it seems as if my netbook believes it's lid is closed, I should maybe point out that my netbook (Aspire One D150) never detected whether the lid was closed or opened (acpi_listen never caught anything when closing/opening it).
Offline
If it is of any use, I also use an Aspire One D250
Offline
So both of you are on an Aspire One, there's definitely a bug with how the lid switch is being handled. A quick google turns this up: https://wiki.archlinux.org/index.php/Ac … wer_button
Online
So both of you are on an Aspire One, there's definitely a bug with how the lid switch is being handled. A quick google turns this up: https://wiki.archlinux.org/index.php/Ac … wer_button
I had totally forgotten that! I read that a couple of months ago when I got this netbook. I already used linux-one kernel and it didn't fix it, will try updating the bios!
Thank you a lot!
Offline
I'm also having this problem on an old maxdata laptop.
It suspended after 30 seconds.
I've fixed it by setting HandleLidSwitch=ignore in /etc/systemd/logind.conf
Perhaps the fact that it occurred for me every 30 seconds might be a further clue.
I was born with nothing and I still got most of it
Offline
Just to bump this thread, I want to say that I'm currently experiencing this issue after having updated (pacman -Syu) after quite a long time (~months). I'm not on a netbook, but I am on a laptop (a Toshiba Satellite). I remember there was an issue I had before where I could boot up my laptop, close the lid to suspend it, then every time I wanted to suspend it I would have to close the lid twice (the first time only shut off the display, so I would open it, wait for the display to come back on, then close it again and it would suspend).
Now, having just updated, I closed the lid, it suspended, then when I opened it up again my computer would be running for ~20-30 seconds and suspend again. Key presses wouldn't wake it up, but hitting the power button did. (Interestingly enough, the light on my power button "waved", like it flashed in and out at a certain frequency. If I pressed a bunch of keys or held down a key, it would slow down the frequency of the wave.) Anyway, the only way to fix this was to shut down and start up again. I'm running it now without having closed the lid and it's fine.
I haven't tried the workaround, but I suspect that will "fix" my problem. But this is still an issue and isn't yet solved.
Offline
Same problem here on my Samsung N150 Plus netbook. I am using Gnome-Shell (minimal)
The problem started after I decided to install a display manager (GDM) and closed the lid after rebooting, which when opened again, suspended every few seconds. I have just made the changes to /etc/systemd/logind.conf as said in this post, and will reboot in a bit. I am using the linux-lts kernel which is currently
[will@arch ~]$ uname -r
3.10.40-1-lts
UPDATE: The workaround has taken affect and is working well, but a proper fix from the repositories might be nice sometime.
Last edited by WillM (2014-05-28 14:12:10)
Do. Or do not. There is no try. - Yoda
“If we fight like animals, we die like animals.” - Seventh Doctor, Sylvester McCoy
Offline
Try setting "HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/logind.conf
Great. Same problem to a custom netbook, and this is the solution.
Offline
Sorry for replying to this old topic!
Try setting "HandleSuspendKey" and "HandleLidSwitch" to ignore in /etc/systemd/logind.conf
Thank's for posting this!
I was struggling with my very old Mecer laptop and thinking of doing a BIOS update!
But I "AT LAST FOUND THIS POST" -- I can't tell you how happy I am! Thank you, thank you!
Resolved on my Acer AOD150 by updating the BIOS.
Followed BIOS update instructions from: https://www.youtube.com/watch?v=ZR6paPNebPY
Offline
Offline
Pages: 1
Topic closed