You are not logged in.
I am a noob at Linux. I reverted the Linux kernel back to 4.17.3 and have been waiting for a solution. Can I pacman -Syu now? The lastest package is 4.18.8.arch1-1 or am I suppose to wait for 4.18.9?
Offline
Wait for 4.18.9.arch1-1. Congratulations to everyone involved in the fix process.
Offline
I tested kernel 4.18.9 a couple of times (5/5) and the kernel boots just fine.
[Edited]: A thorough "reboot session" later - 4.18.9 is still rock solid! \o/
Last edited by NiceGuy (2018-09-24 06:12:25)
Offline
I also wanted to add: If you have any issue whatsoever, then do not hesitate to report it either in the forum, upstream to the developers and open a new bug report.
Intel Core 2 hardware is only getting older and most kernel developers tend to use more modern hardware by now. That is why our issue as well, only got fixed until we reported it upstream. It takes time and patience, as we all experienced, but it's worth it, isn't it?
Offline
Just upgraded to 4.18.9 and it works, well done everyone.
Thx
Offline
Time to remove "TEMPORARY" from the title?
Offline
Just upgraded. Works great now....no stall on boot. Thanks to everyone who helped with this....
_________________________
Asus X200CA Notebook
Offline
Time to remove "TEMPORARY" from the title?
I'm gonna wait til it hits the repos.
EDIT I am a dumbass lol, it did!
Last edited by benoliver999 (2018-09-21 07:35:13)
Offline
I have a similar issue on a Ryzen 7 based system since updating kernel to 4.18.1-arch. I get the systemd-udevd blocked for 120 seconds thing constantly when in terminal. Additionally I'm intermittently left with a hung boot just as the GUI should be loading. Powering down or rebooting requires endless patience or a hard shutdown because systemd-udevd [370] gives up waiting for workers to finish after which its event loop fails with "Connection timed out". Had none of these issues prior to last kernel update so it's nothing to do with old hardware or confined to Intel or AMD, but more likely recent kernel bug(s).
Strangely my old Asus z87I-PRO board which has had a rolling update of Arch for many years now without ever being rebuilt does not present the same issues even though it's running the same kernel.
I have the same issue with a newly build machine on a Ryzen 2700. However, the kernel update did not fix the problem (booting from the LTS kernel works fine). Does this mean the problem is unrelated or are there still unpatched parts in linux 4.18.9.arch1-1?
Offline
audiomuze wrote:I have a similar issue on a Ryzen 7 based system since updating kernel to 4.18.1-arch. I get the systemd-udevd blocked for 120 seconds thing constantly when in terminal. Additionally I'm intermittently left with a hung boot just as the GUI should be loading. Powering down or rebooting requires endless patience or a hard shutdown because systemd-udevd [370] gives up waiting for workers to finish after which its event loop fails with "Connection timed out". Had none of these issues prior to last kernel update so it's nothing to do with old hardware or confined to Intel or AMD, but more likely recent kernel bug(s).
Strangely my old Asus z87I-PRO board which has had a rolling update of Arch for many years now without ever being rebuilt does not present the same issues even though it's running the same kernel.
I have the same issue with a newly build machine on a Ryzen 2700. However, the kernel update did not fix the problem (booting from the LTS kernel works fine). Does this mean the problem is unrelated or are there still unpatched parts in linux 4.18.9.arch1-1?
This does not sound like the same issue. Here the boot hangs immediately and you get a warning about a CPU stall, it's not a systemd-udevd issue. You can't even get to the terminal.
I would open another thread.
Last edited by benoliver999 (2018-09-21 11:40:24)
Offline
Magic -- removed clocksource and the system always boots ok now with 4.18.9. Thank you everyone! It is amazing to see how it starts in a forum thread and ends up being a change upstream, in the kernel. Now if I could only get a hang of this bisecting thing... I will! :-)
Offline
Hello, I think I am having the same (or similar) issue with the latest kernel (4.18.16.arch1-1), I captured the here. Would those be useful to somebody?
Last edited by juanfgs (2018-11-02 23:32:55)
Offline