https://bugs.kde.org/show_bug.cgi?id=372991
--- Comment #17 from Peter Wu <pe...@lekensteyn.nl> --- Created attachment 104751 --> https://bugs.kde.org/attachment.cgi?id=104751&action=edit smaller kernel config that is able to boot archiso (In reply to Martin Sandsmark from comment #15) > Well, it wasn't that commit, managed to reproduce it with that reverted. What about testing the previous commit? Simply reverting might not work as there can be other patches that cause this issue. > Running an arch install pretty similar to your setup but with virtualbox. > Also made an unholy mess of shell scripts that seems to trigger it more > consistently, only problem is that it takes forever to build the kernel (I'm > too lazy to modify the config to trim it down). I am attaching a kernel config from which I based my test kernels (the kernel config I used for bisection got lost). It also has ACPI debugging features enabled (remainder of some other bughunt), you could disable that if you want. What do you use for "quickly" triggering the issue? Something automated would be awesome :) (In reply to Martin Sandsmark from comment #16) > also, I'm not sure if I'm somehow triggering this bug instead sometimes (or > if these are related): https://bugs.kde.org/show_bug.cgi?id=230184 It looks unrelated, that seems to be an issue with firing the timer, the issue in this bug is caused by a watcher that is removed. -- You are receiving this mail because: You are watching all bug changes.
