Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #228357 > unrolled thread

Sid random crash with no clue in log files

Started bySébastien Kalt <skalt@throka.org>
First post2020-10-28 16:20 +0100
Last post2020-10-28 18:10 +0100
Articles 4 — 4 participants

Back to article view | Back to linux.debian.user


Contents

  Sid random crash with no clue in log files Sébastien Kalt <skalt@throka.org> - 2020-10-28 16:20 +0100
    Re: Sid random crash with no clue in log files Linux-Fan <Ma_Sys.ma@web.de> - 2020-10-28 16:40 +0100
    Re: Sid random crash with no clue in log files Charles Curley <charlescurley@charlescurley.com> - 2020-10-28 17:00 +0100
    Re: Sid random crash with no clue in log files <tomas@tuxteam.de> - 2020-10-28 18:10 +0100

#228357 — Sid random crash with no clue in log files

FromSébastien Kalt <skalt@throka.org>
Date2020-10-28 16:20 +0100
SubjectSid random crash with no clue in log files
Message-ID<B4VoZ-2uA-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,

I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while
copying large files through network, sometimes when watching a youtube
video, sometimes juste using LibreOffice, or going nothing ...

I can't manage to have a pattern for thoses craches. Today it craches 4
times, the last week it didn't crash.

I encoded a video with 100 % CPU charge during one hour and it didn't crash.

When I look at the log files, I see nothing : syslog, messages, daemon.log,
kern.log, Xorg.0.log.old, dmesg

When it crashes, the system seems to be not responding, I can move the
mouse, but it doesn't click, and then the screen becomes blank. I need to
shut down the mini PC pushing the power button for a long time.

When I restart it, I don't see anything during the reboot (well, it's quite
fast, so I might miss something).

Do you have any suggestions to find what might be causing this ?

Regards,

Sébastien

[toc] | [next] | [standalone]


#228359

FromLinux-Fan <Ma_Sys.ma@web.de>
Date2020-10-28 16:40 +0100
Message-ID<B4VIl-2AF-13@gated-at.bofh.it>
In reply to#228357

[Multipart message — attachments visible in raw view] — view raw

Sébastien Kalt writes:

> Hello,
>
> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while  

[...]

> When it crashes, the system seems to be not responding, I can move the mouse,  
> but it doesn't click, and then the screen becomes blank. I need to shut down  
> the mini PC pushing the power button for a long time.

[...]

Hello,

common things to test in case of random crashes are hardware-related issues  
like cooling (CPU temperatures?), power supply and RAM (memtest86+).

Another thing to debug is: While the system is in the described crash state,  
you can still move the mouse -- this means some software on the system  
remains running despite not being accessible through GUI. An interesting  
step could be to attempt a login through SSH (install openssh-server if not  
already there to enable SSH access). From that SSH login you might be able  
to call a tool like `htop` to check the state of the system and stop any  
rouge processes etc.

I used to have similar types of crashes (the screen never went black, but  
the mouse cursor would move with any further inputs like klicks and key  
presses ignored) on a system with VirtualBox and the NVidia proprietary GPU  
driver (must have been Debian 7 or 8 IIRC). If either VirtualBox or NVidia  
graphics driver were uninstalled, it would never crash that way... In any  
case, logging in through SSH, I could see that the Xorg process was at 100%  
CPU. Killing it caused the screen to go black. Attempting to re-start would  
fail in some way, but afterwards a login from the local system would again  
be possible and the hard reset could be avoided...

HTH
Linux-Fan

öö

[toc] | [prev] | [next] | [standalone]


#228360

FromCharles Curley <charlescurley@charlescurley.com>
Date2020-10-28 17:00 +0100
Message-ID<B4W1I-2H7-9@gated-at.bofh.it>
In reply to#228357
On Wed, 28 Oct 2020 16:09:33 +0100
Sébastien Kalt <skalt@throka.org> wrote:

> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's
> while copying large files through network, sometimes when watching a
> youtube video, sometimes juste using LibreOffice, or going nothing ...

> Do you have any suggestions to find what might be causing this ?

I suspect something, likely RAM, isn't properly seated. I would: remove
and re-seat any socketed ICs, and any daughter boards. Replug all
cables.

Install and run memtest86 for several hours.

If you have played with hardware settings in the BIOS, set them back to
factory values.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]


#228361

From<tomas@tuxteam.de>
Date2020-10-28 18:10 +0100
Message-ID<B4X7s-3y2-3@gated-at.bofh.it>
In reply to#228357

[Multipart message — attachments visible in raw view] — view raw

On Wed, Oct 28, 2020 at 04:09:33PM +0100, Sébastien Kalt wrote:
> Hello,
> 
> I'm having random crashes on my ASUS PN50 mini PC : sometimes it's while
> copying large files through network, sometimes when watching a youtube
> video, sometimes juste using LibreOffice, or going nothing ...
> 
> I can't manage to have a pattern for thoses craches. Today it craches 4
> times, the last week it didn't crash.
> 
> I encoded a video with 100 % CPU charge during one hour and it didn't crash.
> 
> When I look at the log files, I see nothing : syslog, messages, daemon.log,
> kern.log, Xorg.0.log.old, dmesg
> 
> When it crashes, the system seems to be not responding, I can move the
> mouse, but it doesn't click, and then the screen becomes blank. I need to
> shut down the mini PC pushing the power button for a long time.
> 
> When I restart it, I don't see anything during the reboot (well, it's quite
> fast, so I might miss something).
> 
> Do you have any suggestions to find what might be causing this ?

If the mouse still moves, I'd look first into software. Try to log
into your machine either with a Linux console (CTRL-ALT+F1 or some
other function key) or via ssh, as linux fan suggests.

Try to locate some central gui program which might be misbehaving
and kill it (gnome-panel or some such).

If it were a hardware problem, the machine would most probably
freeze completely or at least show non-repeatable symptoms.

Cheers
 - t

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web