On Tue, Oct 18, 2016 at 10:16:26PM +0200, sivmu wrote:
> After upgrading the kernel to 4.7.8 today the issue did not occur again.
What repo did you find that kernel in?
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
Did this problem started after an upgrade?
Can you check if it is hardware failure?
Any memtest?
Am 18.10.2016 um 00:53 schrieb Ralf Mardorf:
> On Mon, 17 Oct 2016 23:50:14 +0200, sivmu wrote:
>> The result of the trigger is a full system crash, showing the current
>> screen.
>
>> I have no idea how to analyse the issue further.
>
> You didn't mention what WM or DE, what kind of network, w
On Mon, 17 Oct 2016 23:50:14 +0200, sivmu wrote:
>The result of the trigger is a full system crash, showing the current
>screen.
>I have no idea how to analyse the issue further.
You didn't mention what WM or DE, what kind of network, what tool to
access the network and what graphics is used.
A
5 matches
Mail list logo