Hello,
I have been using slackware for more than a year.This is the best linux distribution from my experience.But I am having frequent crash-issues.

I have had more than 30 crashes.My slackware just crashes frequently and I have to shut-down the laptop by pressing the power button deliberately.Sometime I even have two or more crashses in a single day.

What could be the problem?
>>>> Is it a kernel issue?
>>>> Is it a hardware problem?

I can share my syslog and dmesg report if you need.(I am unable (or don't know) to upload them here)

Could this be a cause?
---issue 1---
[ 0.000000] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

should I consider turning off the split_lock_detection?

---issue 2---
[ 5.480365] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210930/nsarguments-61)

can I configure the acpi?

My laptop is Dell-Inspiron 5593,i7-10th Gen

Weird. I'm running Slackware64-15.0 on two desktops and a laptop, and I'm running Slackware64-current on a desktop. Everything running well here.
Your issue may be hardware related. I've experienced an unstable system with bad RAM. Perhaps try running memtest.

From /usr/src/linux/Documentation/kernel-parameters.txt :

A kernel parameter like acpi=off is given by the bootloader at boot. With lilo you add kernel parametrs by adding them to the "append" parameter in lilo.conf.

Maybe there are also some ACPI related settings in your computers CMOS setup.

Disabling acpi might make your system more stable, but it will probably also result in some lost functionality. That functionality might include, but not be limited to things like:

• Having to manually turn off the computer after each shutdown
• Losing function of some special buttons on computer or keyboard
• Not being able to detect wether a charger is connected or battery charge level

regards Henrik

1 members found this post helpful.

With any powerful laptop, especially low profile models, the first thing I look for is temperatures. There is never going to be serious airflow without a LOT of noise on thin laptops. Since "quiet" is a major selling point, airflow is minimal at best. All it takes is a few years running above 70C and the thermal pads (never as good as thermal paste) dry up and stop transferring thermals at spec. Check your temps under full load and if they are above 85C get it serviced or do it yourself if you know how. You might buy some time by seeking fan control and raising rpms.

4 members found this post helpful.

enorbet makes excellent points.

You might also check the log files, particularly /var/log/messages and /var/log/syslog.

Perhaps the easiest way would be to wait until the next time it happens, then use the tail command to look for the most recent entries. It's a bit of a long shot, because, in the case of unexpected freezes and shutdowns, sometimes the messages don't have a chance to get logged, but it's certainly worth a shot.

Slackuj, I want to second what enorbet said.
I'm running Slackware on a 2012 Macbook Pro. I needed to find a separate daemon program to control the fans because the machine would get too warm and throttle the clock. Perhaps the Inspiron needs a third-party daemon program to control the fans, too.

Hello, something similar happened to me many years ago with Debian and it turned out to be the hard disk, they changed the hdd and the problems were over. What do you have hdd or ssd?, have you had them for a long time?, do you have any other hdd or ssd to be able to clone the system and try?

A solution has occurred to me, it is what in my country, Spain, we call cutting to the chase.

First you make a system image with clonezilla or if you are not good at clonezilla, you have rescuezilla, which is the same but in graphical mode:

https://rescuezilla.com/download

As you have a system image, now you can install any distro and automatically, as soon as you finish installing the distro, you know if it is hardware or not, if you install a distro and everything goes well, then it is clear that the problem is not from hardware and if it continues to go wrong, then it is clear that it is hardware and then it is time to look at what component it could be, from what you describe it could be a hard drive or ram.

If you install a distro and it goes well for you, if I were you I would install slackware again, just like you did the other time, you write down everything you install and observe, for example:

You install slackware and once installed you update it and then you start to make it your own, just like you did last time, for example, if you have proprietary drivers, you install them, which suddenly goes wrong, you know what that is, that it continues to go well, you continue configuring and above all you write down everything you are doing and how and so it is possible that you can determine the problem or it is possible that you end up with everything working and you will not have lost anything, only time and when you finish, you make another image with rescuezilla and delete the old one that didn't work for you.

1 members found this post helpful.

A quicker way to try out another distro is to boot some live DVD like knoppix. Such a test will not be as complete as a new installation on disk as it will not test the disk, but it will test most of the hardware in simple way. Many live CD/DVDs (and also the Slackware installation CD/DVD) also has the option to select a memory tester in the boot loader.

When suspecting the disk it might be a good idea to read out smart values to see if the disk itself thinkt that it is going to fail. Maybe you will have to enable smart in cmos setup to be able to do that.

regards Henrik

2 members found this post helpful.

True, but with the cd/dvd/usb you only test the ram, effectively as you say through commands, if you master them and know what they are, you can also know if the hard drive fails, since I don't master them, I do it this way that I have mentioned because that way, as soon as you install the operating system that you install, you automatically know if the problem is hardware or operating system, but as you say, if you have the necessary knowledge it is not necessary with just a few commands you already know.

Greetings.

Assuming OP actually prefers Slackware, even if just for a time, LiveSlak would be a good choice. Why install a completely different distro just to ferret out a hardware or configuration problem? One problem with installing other distros is that kernels matter and different distros have different kernels often. In such cases, comparing Apples to Oranges comes to mind. A further assumption or possibly an implication, is that anyone attracted to even try out Slackware commonly wants the freedom and power that comes with such a distro. Those that don't want to know how their system works, just how to click on the apps they like, will gravitate away from Slackware and more commonly toward Ubuntu, Mint, etc.

I suggest learning Memtest+, lm_sensors, stdout, dmesg, syslog, (GKrellm and Conky help, too if you prefer GUI) and man pages to actually become the owner of "the nuts and bolts" if that's what attracted you in the first place.

1 members found this post helpful.

And the CD/DVD drive, video, keyboard, mouse, with options to check the hard drive(s), WAN, USB, Bluetooth...

I got one, used, in 2004. Before I bought it, I tested it with Knoppix. That clean bill of health made it possible. And it still works, as Dad's toy, running Slackware.

This thread makes me think that there is however a distribution which is famous for its stability. But I can't remember its name

1 members found this post helpful.

I installed a new slackware-current-64bit yesterday.

My slackware crashed once again.

Is it a hardware problem?

I also have battery issues.

My laptop is Dell-Inspiron 5593(genuine).

I bought it two years ago.

As far as I remember :

1.I used to have sudden switching off.After every sudden-switching off, my battery health decreased.

2.I replaced a new battery 6 months ago.

3.After battery replacement I never had sudden-switching off. But my slackware gets crashed.
Before battery replacement,I never had a slackware crash.

4.Currently,My battery is showing alien-behavior.
Sometimes,it doesn't gets charged.Sometimes it charges, but cannot run more than 5 minutes without AC.

5.Is it a battery-issue or circuit-issue?

Is there any way to check it?

Good! That solution was probably quicker and easier than trying to fix the kernel/missing modules problem.

In what way did it crash? The same kernel / missing modules problem? A total shutdown? Still powered on but frozen? If frozen, do you see any error messages?

Hard to say without more information.

If your battery runs out and your machine shuts down unexpected it could cause problems with the file systems. Those problems could later cause lost files or files with wrong contents. At boot, an attempt will be made to run some fsck to fix all logical problems in the file system. However, even if the file system gets fixed, some files might still be broken.

Those sudden switch offs were probably because the battery run out. Most batteries lose some health if they are completely drained.

Those crashes might have been caused by broken files from unclean shutdowns.

Hard to say, but some hardware seems broken. It could be the battery (again) or the charger or the laptop. Something probably decides when the battery is fully charged and should not be charged anymore. Maybe that something decides to stop the charging too early.

Unfortunately I have no better idea than to replace stuff and see when the problem goes away.

Does it help with a new battery? Does it help with a new charger? Does it help with a new laptop? However, this way to search for errors is expensive unless you happen to have some other known working equipment where you can borrow parts from.

regards Henrik