29 Oct
2018
29 Oct
'18
10:22
http://bugzilla.suse.com/show_bug.cgi?id=1109425
http://bugzilla.suse.com/show_bug.cgi?id=1109425#c5
--- Comment #5 from Stefan Priebe
Is there a possibility to bisect the (upstream!) kernel and check which commit introduced the regression?
This would really help us in root causing the problem.
Sadly not. As this bug is triggered on a random basis. It happens once a week out of 40 machines. I'm not able to reproduce. -- You are receiving this mail because: You are on the CC list for the bug.