SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use Slackware 14.1 64 bit version with kernel 3.10.17 on 3 machines and sometimes suspend, crashed. On first machine crashed after 2 days, other machines can good working with 17-18 days (or more), and unfortunelly crashed. Mostly programs are killing, but ping sometimes is working. I don't know why system is down? Is fault of kernel or memory or mainboard? On slackware 14.0 64 bit (Linux 3.2.45) works perfect more than 100 days. Now I update kernel to kernel 3.14.4 and I hope that will help me.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
The first question would be what are you running (that's not part of the Slackware 14.1 release); what add-on software, versions, stuff like that. Too, did you rebuild any 14.0 packages that you had installed (or did you just leave them there)?
What hardware do you have? What configurations have you fiddled with?
Right now, your kernel version should look like this:
Code:
ls -al /var/log/packages/kernel*
-rw-r--r-- 1 root root 27047 Nov 24 2013 /var/log/packages/kernel-firmware-20131008git-noarch-1
-rw-r--r-- 1 root root 978 Feb 20 10:53 /var/log/packages/kernel-generic-3.10.17-x86_64-2
-rw-r--r-- 1 root root 23137 Feb 20 10:53 /var/log/packages/kernel-headers-3.10.17-x86-2
-rw-r--r-- 1 root root 975 Feb 20 10:53 /var/log/packages/kernel-huge-3.10.17-x86_64-2
-rw-r--r-- 1 root root 222468 Feb 20 10:54 /var/log/packages/kernel-modules-3.10.17-x86_64-2
-rw-r--r-- 1 root root 2812317 Feb 20 10:54 /var/log/packages/kernel-source-3.10.17-noarch-2
Note the ...noarch-2; that's the updated kernel that should be installed (if you haven't done that, it would be your first step -- see your favorite mirror and get all the patches, including the kernel patches and apply them). You probably don't want to mess with building and installing 3.14.4 yet.
A few months back, a race that could cause pipe info to be read from memory already freed, was identified and fixed. I believe this
is what you're triggering.
On the 3.10.x branch, this was corrected in 3.10.24 (also 3.12.5 and 3.13 in the mainline). I've placed upstream's fix here (sig) which
applies cleanly to Slackware 14.1's 3.10.17.
--mancha
Last edited by mancha; 05-31-2014 at 07:04 PM.
Reason: mention other versions
>The first question would be what are you running (that's not part of the Slackware 14.1 release); what add-on software, versions, stuff like that. Too, did you >rebuild any 14.0 packages that you had installed (or did you just leave them there)?
>What hardware do you have? What configurations have you fiddled with?
Hardware name is Hewlett-Packard hp workstation xw6200/08B8h
Hardware name: /SE7230NH1LX
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Quote:
Originally Posted by kerszi
Now Server working 6 days without crash and I hope that new kernel helps me.
Probably was the kernel (3.14.4 includes the fixes that were in 3.10.17-2, the patched kernel).
Are you using the Lustre distributed file system? I'd be interested in knowing how it works for you, the good, the bad and the ugly (if there is anything bad or ugly, that is).
I finally gave up on ReiserFS (when he went to jail and wasn't going to be doing any work on the file system for quite a while) and switched to ext4 (the Slackware default). I've been thinking about a distributed file system and wonder how you like it.
I working on ReiserFS many years and is good. 8 years ago I used ext3, but after 4-5 reboot server didn't start. I didn't use ext4. I use
Slackwares system from 2000 year.
ext3 did not have a journal... so sudden power loss could cause hard drive corruption... ext4 solved this and has been stable for many years. Not sure, but guessing by 'reboot' you mean 'lost power'.
ext3 did not have a journal... so sudden power loss could cause hard drive corruption... ext4 solved this and has been stable for many years. Not sure, but guessing by 'reboot' you mean 'lost power'.
Small correction: the ext3 filesystem does have a journal! And ext4 adds checksumming to the journal, to make rollbacks safer after a crash.
ext3 did not have a journal... so sudden power loss could cause hard drive corruption... ext4 solved this and has been stable for many years. Not sure, but guessing by 'reboot' you mean 'lost power'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
