LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-28-2018, 11:48 AM   #1
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Rep: Reputation: Disabled
two problems: problem 1 - slackware current crashing randomly


Hello,
Slackware current (last update today) 64bit, Plasma5, kernel 4.15.13 (Kernel: 4.15.13 x86_64 bits: 64 Desktop: KDE Plasma 5.12.3)

issue:
System randomly became unresponsive with HD LED on (disk access). No log errors.

The issue is not caused by the latest kernel version as tested with older kernels that worked before (til the end of February).

I wonder if I am the only one with this issue?

thank you

edited to correct error description.

Last edited by Aeterna; 03-28-2018 at 02:30 PM.
 
Old 03-28-2018, 02:18 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
So far, VBox worked fine with the current kernel (4.14.30).
 
Old 03-28-2018, 02:27 PM   #3
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by willysr View Post
So far, VBox worked fine with the current kernel (4.14.30).
Thank you so much,
Unfortunately I was to quick with the accusations. Each time when Slackware froze, I was running vbox.
However for the first time my laptop froze without anything extra running, so this seems to be a problem with my installation (as nobody else is complaining about similar issue).
 
Old 03-28-2018, 02:42 PM   #4
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
Be sure to check your system logs as it might be a hardware problem

/var/log/syslog and /var/log/messages.
 
Old 03-28-2018, 03:00 PM   #5
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by aaazen View Post
Be sure to check your system logs as it might be a hardware problem

/var/log/syslog and /var/log/messages.
Thank you very much but as I mentioned in my first post, unfortunately I don't see any errors in the log files.
 
Old 03-28-2018, 05:34 PM   #6
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,950

Rep: Reputation: Disabled
Try sshing in from a second system and then use 'dmesg -w'. Next time your system goes down hopefully dmesg will give you some useful errors.
 
Old 03-29-2018, 10:46 AM   #7
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by orbea View Post
Try sshing in from a second system and then use 'dmesg -w'. Next time your system goes down hopefully dmesg will give you some useful errors.
Thank you,

I think that I have found the culprit. Since I removed intel-ucode from lilo, I did not experienced system freeze. Before deciding if this is real solution to the problem, I want to wait a bit and see what will happen.

ok: looks like unicode is not to blame as system freezes anyway.

It seems that I will have to reinstall slackware. My /home is on different partition so I will survive.

Last edited by Aeterna; 03-29-2018 at 12:43 PM. Reason: further development
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Virtualbox for Slackware Current 64 Gordie Slackware 6 02-29-2016 01:06 PM
Dota 2 Crashing on Slackware Current (AMD Open Source Drivers) Sylvester Ink Slackware 7 08-02-2014 02:24 PM
Xorg ATI Radeon Driver Crashing Slackware Current 3.8.8 Kernel SlackStephen Slackware 2 05-04-2013 12:51 AM
[SOLVED] Kmail crashing in Slackware current with KDE 4.7.3 saivnoba Slackware 2 11-12-2011 07:05 PM
KDE sound system crashing with SIGSEGV, slackware-current, 2.6.17.13 StarsAndBars14 Linux - Desktop 0 03-09-2007 07:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:44 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration