18 Oct
2016
18 Oct
'16
8:16 p.m.
Am 18.10.2016 um 21:33 schrieb Alex Theotokatos via arch-general:
Did this problem started after an upgrade? Can you check if it is hardware failure? Any memtest?
it did staret after upgrading the kernel to 4.7.7 Hardware seems ok. After upgrading the kernel to 4.7.8 today the issue did not occur again. So I assume the error was in the kernel, although I would still very much like to know a way to analyse this kind of problem. I imaging there must be some kind of continious loggin tool that shows when exactly the error triggers.