You are not logged in.
Have we solved this (it's not solved for everyone by the looks of it)?
It solves the original issue you've posted - so I'd vote yes. I'll need to do my own git bisect process -- but it will take many days on that old laptop. Will see - may be over coming holidays.
Offline
@romstor have you checked the contents of /proc/cmdline for init_on_alloc=0
Offline
Same here. LTS kernel sleeps like a baby, normal doesn't sleep at all and refuses to wake. init_on_alloc=0 makes no difference. HP Elitebook 840 G6
Offline
@romstor have you checked the contents of /proc/cmdline for init_on_alloc=0
Yes, it was properly picked up. I even tried to add both init_on_alloc=0 and init_on_free=0 (and combinations thereof) - no luck. May be my issue is different.
Offline
I forgot to turn off automatic suspend after a time and strangely enough the PC was successfully suspended when I came to it. I have troubleshooted audio problems before that. So maybe snd_hda_intel might interfere here? Possibly snd_hda_intel.dmic_detect=0 might have made it work?
Maybe the PC have enough time to finish the suspend procedure? I have 32GB of RAM. So if it should be dumped to disk it could take a while.
I have no time to debug it tho. I am just sharing my experience. Suspend now works as expected for me.
Offline
@bambooCZ was your issue triggered by the 5.3.12 kernel update?
Offline
@loqs Not exactly. My issue was on new installation. I have tried LTS kernel when I was troubleshooting it. The system was about 5 hours old.
Sound was also working with the LTS kernel, but not with the normal one.
Last edited by bambooCZ (2019-12-10 22:47:35)
Offline
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
I had a version of same problem, see separate thread if interested: https://bbs.archlinux.org/viewtopic.php … 3#p1877773
Thanks to everyone who worked towards this fix
Offline
lschu wrote:I plan to give those a go this weekend if I have time to get around to it.
I would suggest running the first two builds overnight as they can take a long time.
Just curious to know, but the OP stated the build took longer than 6 hours, how much would you benefit if you used parallel builds ? I know OP does not have this option, just asking for myself because in my case I'm not always in the possibility to run things overnight....
Would it also be required to run overnight?
Failure is success in progress.
A.E.
Offline
Getting OT (and old-ish thread), sorry about this...
Just curious to know, but the OP stated the build took longer than 6 hours, how much would you benefit if you used parallel builds ? I know OP does not have this option, just asking for myself because in my case I'm not always in the possibility to run things overnight....
Would it also be required to run overnight?
... but as this is the newbie corner I believe a few pieces of information is in order
Parallel builds means to use all / most cores of a CPU (depends on configuration). It will make a massive difference on modern systems, of course depending on the number of cores the CPU/system has. Even the least efficient CPUs have at least two cores -> compilation time will be at least halved on almost any computer these days! It is not uncommon to have 4, 6 or even 8 cores, however for a single compilation it might not scale that well to N cores (there's a limit to how well the compilation can parallelize, as some parts depend on others). By my gut feeling (*rumble*) I say it is possible to get a reduction of 80% (with >4 cores) for large compile tasks like the Kernel, but probably not much more than that.
Of course running overnight is just an suggestion (instead of overnight you might run it during a lunch break, while going to the GYM or, while browsing Reddit or Arch Forums .... YMMV!) :-D
(also having hibernate / suspend issues, but not at all sure if this thread is relevant to my problem; will post elsewhere once I'm sure where to post / if I have the time...)
Last edited by Wild Penguin (2020-01-20 16:08:32)
Offline
I'm also experiencing the same issue, and init_on_alloc=0 does not fix it. I did confirm it is present in /proc/cmdline.
PC is an old HP Elitebook 6930p from 2010ish. Intel graphics. Journalctl has nothing in it between a successful suspend, and then the hard reboot.
I will try to get my hands on an older kernel. Is this bug being tracked somewhere?
Edit: words are hard
Last edited by auxym (2020-01-23 23:36:45)
Offline
@auxym old packages are available in the ALA. No one has mentioned reporting the issue upstream.
Offline
Alright, I installed kernel v5.3.18-1 and suspend works fine. It does appear to be an issue with v5.4, and init_on_alloc=0 does not fix it for me.
Offline
@auxym I would start a new thread as your issue is not triggered by 5.3.12 or fixed by init_on_alloc=0
https://bbs.archlinux.org/viewtopic.php … 6#p1877006 contains step by step instructions to bisect between 5.3 and 5.4 to find the causal commit.
Offline