LinuxQuestions.org
Review your favorite Linux distribution.
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 05-30-2014, 03:50 PM   #1
kerszi
LQ Newbie
 
Registered: May 2014
Posts: 4

Rep: Reputation: Disabled
Slackware 14.1 64 bit crash


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.

Below are logs from syslog when slack suspend.

Log from first server
----------------
Apr 1 18:30:14 serwer02s kernel: [19577.548007] RIP [<ffffffff81149f44>] kmem_cache_alloc+0x54/0x120
Apr 1 18:30:14 serwer02s kernel: [19577.548007] RSP <ffff8800be227eb0>
Apr 1 18:30:14 serwer02s kernel: [19577.548007] CR2: ffff8801c482ea80
Apr 1 18:30:14 serwer02s kernel: [19577.548007] ---[ end trace 8450b3b6414c2961 ]---
Apr 1 18:30:14 serwer02s kernel: [19577.655954] BUG: unable to handle kernel paging request at ffff8801c482ea80
Apr 1 18:30:14 serwer02s kernel: [19577.656007] IP: [<ffffffff81149d8f>] kmem_cache_alloc_trace+0x5f/0x120
Apr 1 18:30:14 serwer02s kernel: [19577.656007] PGD 236f067 PUD 0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Oops: 0000 [#2] SMP
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Modules linked in: arptable_filter arp_tables cls_fw xt_mark iptable_mangle sch_sfq cls_u32 sch_htb xt_tcpudp xt_nat xt_conntrack iptable_nat nf_nat_ipv4 iptable_filter ip_tables xt_connlimit x_tables nf_nat_irc nf_nat_ftp nf_nat nf_conntrack_irc nf_conntrack_ftp nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipv6 lp fuse i2c_dev mperf gpio_ich processor tg3 lpc_ich thermal_sys radeon ttm drm_kms_helper drm e1000e ppdev agpgart freq_table i2c_algo_bit i2c_core libphy parport_pc parport hwmon wmi evdev psmouse ptp pps_core button serio_raw snd_intel8x0 uhci_hcd ehci_pci ehci_hcd shpchp snd_ac97_codec snd_pcm snd_page_alloc snd_timer snd microcode soundcore ac97_bus loop
Apr 1 18:30:14 serwer02s kernel: [19577.656007] CPU: 0 PID: 32150 Comm: sh Tainted: G D 3.10.17 #2
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Hardware name: Hewlett-Packard hp workstation xw6200/08B8h, BIOS 786B7 v2.10 09/05/2006
Apr 1 18:30:14 serwer02s kernel: [19577.656007] task: ffff8800c4f72a60 ti: ffff8800c7686000 task.ti: ffff8800c7686000
Apr 1 18:30:14 serwer02s kernel: [19577.656007] RIP: 0010:[<ffffffff81149d8f>] [<ffffffff81149d8f>] kmem_cache_alloc_trace+0x5f/0x120
Apr 1 18:30:14 serwer02s kernel: [19577.656007] RSP: 0018:ffff8800c7687e78 EFLAGS: 00010282
Apr 1 18:30:14 serwer02s kernel: [19577.656007] RAX: 0000000000000000 RBX: ffff8800c88865b8 RCX: 00000000000d2bdb
Apr 1 18:30:14 serwer02s kernel: [19577.656007] RDX: 00000000000d2bda RSI: 00000000000080d0 RDI: ffffffff8115e520
Apr 1 18:30:14 serwer02s kernel: [19577.656007] RBP: ffff8800c7687ea8 R08: 0000000000015740 R09: 0000000000000003
Apr 1 18:30:14 serwer02s kernel: [19577.656007] R10: 0000000000000001 R11: 0000000000000246 R12: ffff8801c482ea80
Apr 1 18:30:14 serwer02s kernel: [19577.656007] R13: 00000000000080d0 R14: 0000000000000088 R15: ffff8800db8019c0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] FS: 00007ff474987740(0000) GS:ffff8800dfa00000(0000) knlGS:0000000000000000
Apr 1 18:30:14 serwer02s kernel: [19577.656007] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 1 18:30:14 serwer02s kernel: [19577.656007] CR2: ffff8801c482ea80 CR3: 00000000c0046000 CR4: 00000000000007f0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Apr 1 18:30:14 serwer02s kernel: [19577.656007] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Stack:
Apr 1 18:30:14 serwer02s kernel: [19577.656007] ffffffff8115e520 ffff8800c88865b8 ffff8800c7687f50 0000000000000000
Apr 1 18:30:14 serwer02s kernel: [19577.656007] ffff8800c7687f48 0000000000000000 ffff8800c7687ec0 ffffffff8115e520
Apr 1 18:30:14 serwer02s kernel: [19577.656007] ffff8800c88865b8 ffff8800c7687f00 ffffffff8115eaa6 ffff8800c4f72a60
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Call Trace:
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115e520>] ? alloc_pipe_info+0x20/0xb0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115e520>] alloc_pipe_info+0x20/0xb0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115eaa6>] create_pipe_files+0x46/0x200
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115ec94>] __do_pipe_flags+0x34/0xf0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115edc0>] SyS_pipe2+0x20/0xa0
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff81b6efb2>] ? page_fault+0x22/0x30
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff8115ee50>] SyS_pipe+0x10/0x20
Apr 1 18:30:14 serwer02s kernel: [19577.656007] [<ffffffff81b6f786>] system_call_fastpath+0x1a/0x1f
Apr 1 18:30:14 serwer02s kernel: [19577.656007] Code: f8 36 a2 00 48 8b 7d d0 49 8b 0f 65 48 03 0c 25 08 cd 00 00 48 8b 51 08 4c 8b 21 4d 85 e4 74 57 49 63 47 20 48 8d 4a 01 4d 8b 07 <49> 8b 1c 04 4c 89 e0 65 49 0f c7 08 0f 94 c0 84 c0 74 ca 49 63
-------------
Log from second server

May 24 17:55:03 serwer02n kernel: [2081001.425024] BUG: unable to handle kernel paging request at ffff8801a4dbc0c0
May 24 17:55:03 serwer02n kernel: [2081001.425212] IP: [<ffffffff81149f44>] kmem_cache_alloc+0x54/0x120
May 24 17:55:03 serwer02n kernel: [2081001.425365] PGD 236f067 PUD 0
May 24 17:55:03 serwer02n kernel: [2081001.425443] Oops: 0000 [#1] SMP
May 24 17:55:03 serwer02n kernel: [2081001.425528] Modules linked in: nf_conntrack_netlink nfnetlink hid_generic usbhid hid arptable_filter arp_tables cls_fw xt_mark iptable_ma
ngle sch_sfq cls_u32 sch_htb xt_tcpudp xt_nat xt_conntrack iptable_nat nf_nat_ipv4 iptable_filter ip_tables xt_connlimit x_tables nf_nat_irc nf_nat_ftp nf_nat nf_conntrack_irc
nf_conntrack_ftp nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipv6 lp ppdev parport_pc parport fuse acpi_cpufreq mperf processor gpio_ich radeon thermal_sys i2c_dev lpc_ich fr
eq_table ttm drm_kms_helper drm psmouse agpgart i2c_i801 e1000e i2c_algo_bit serio_raw hwmon evdev ipmi_si e1000 i2c_core uhci_hcd ipmi_msghandler shpchp ehci_pci ehci_hcd ptp
pps_core microcode button loop
May 24 17:55:03 serwer02n kernel: [2081001.425647] CPU: 1 PID: 19913 Comm: sh Not tainted 3.10.17 #2
May 24 17:55:03 serwer02n kernel: [2081001.425647] Hardware name: /SE7230NH1LX, BIOS NH72310J.86B.1179.2006.0508.2328 05/08/2006
May 24 17:55:03 serwer02n kernel: [2081001.425647] task: ffff880091239530 ti: ffff8800a7ede000 task.ti: ffff8800a7ede000
May 24 17:55:03 serwer02n kernel: [2081001.425647] RIP: 0010:[<ffffffff81149f44>] [<ffffffff81149f44>] kmem_cache_alloc+0x54/0x120
May 24 17:55:03 serwer02n kernel: [2081001.425647] RSP: 0018:ffff8800a7edfdd8 EFLAGS: 00010286
May 24 17:55:03 serwer02n kernel: [2081001.425647] RAX: 0000000000000000 RBX: 0000000001200011 RCX: 00000000048692d6
May 24 17:55:03 serwer02n kernel: [2081001.425647] RDX: 00000000048692d5 RSI: 00000000000000d0 RDI: ffff8800bc0019c0
May 24 17:55:03 serwer02n kernel: [2081001.425647] RBP: ffff8800a7edfe08 R08: 0000000000015740 R09: 0000000000000000
May 24 17:55:03 serwer02n kernel: [2081001.425647] R10: 0000000000000000 R11: ffffffffffffffe8 R12: ffff8801a4dbc0c0
May 24 17:55:03 serwer02n kernel: [2081001.425647] R13: 00000000000000d0 R14: ffff8800bc0019c0 R15: ffffffff81080de6
May 24 17:55:03 serwer02n kernel: [2081001.425647] FS: 00007f244da3d740(0000) GS:ffff8800bfa80000(0000) knlGS:0000000000000000
May 24 17:55:03 serwer02n kernel: [2081001.425647] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 24 17:55:03 serwer02n kernel: [2081001.425647] CR2: ffff8801a4dbc0c0 CR3: 00000000a52a1000 CR4: 00000000000007e0
May 24 17:55:03 serwer02n kernel: [2081001.425647] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 24 17:55:03 serwer02n kernel: [2081001.425647] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 24 17:55:03 serwer02n kernel: [2081001.425647] Stack:
May 24 17:55:03 serwer02n kernel: [2081001.425647] ffff880091239530 0000000001200011 ffff880091239530 0000000001200011
May 24 17:55:03 serwer02n kernel: [2081001.425647] ffff88009bde62e0 ffff8800a81a4000 ffff8800a7edfe28 ffffffff81080de6
May 24 17:55:03 serwer02n kernel: [2081001.425647] 0000000001200011 ffff88009bde62e0 ffff8800a7edfe58 ffffffff810813df
May 24 17:55:03 serwer02n kernel: [2081001.425647] Call Trace:
May 24 17:55:03 serwer02n kernel: [2081001.425647] [<ffffffff81080de6>] prepare_creds+0x26/0x1a0
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff810813df>] copy_creds+0x2f/0x140
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff81055001>] copy_process.part.44+0x2b1/0x1380
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff811572c0>] ? get_empty_filp+0x90/0x1b0
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff810561ad>] do_fork+0xad/0x350
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff810564d6>] SyS_clone+0x16/0x20
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff81b6faa9>] stub_clone+0x69/0x90
May 24 17:55:03 serwer02n kernel: [2081001.476834] [<ffffffff81b6f786>] ? system_call_fastpath+0x1a/0x1f
 
Old 05-31-2014, 12:17 PM   #2
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
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.

Hope this helps some.
 
1 members found this post helpful.
Old 05-31-2014, 12:25 PM   #3
genss
Member
 
Registered: Nov 2013
Posts: 362

Rep: Reputation: Disabled
lustre file system ?
just asking, think its something with the filesystem

Last edited by genss; 05-31-2014 at 12:27 PM.
 
1 members found this post helpful.
Old 05-31-2014, 01:23 PM   #4
metaschima
Senior Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 1,532

Rep: Reputation: Disabled
It looks like a kernel bug to me. You could try a newer kernel and see if it fixes it.
 
Old 05-31-2014, 03:40 PM   #5
mancha
Member
 
Registered: Aug 2012
Posts: 362

Rep: Reputation: Disabled
Hi.

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 08:04 PM. Reason: mention other versions
 
1 members found this post helpful.
Old 06-01-2014, 02:17 PM   #6
kerszi
LQ Newbie
 
Registered: May 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
Thanx for your help

>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

Now I updated from ftp://ftp.slackware.pl/slackware64-current/ and I have


ls -al /var/log/packages/kernel*

-rw-r--r-- 1 root root 28559 May 26 12:24 /var/log/packages/kernel-firmware-20140506git-noarch-1
-rw-r--r-- 1 root root 973 May 26 12:24 /var/log/packages/kernel-generic-3.14.4-x86_64-1
-rw-r--r-- 1 root root 23746 May 26 12:24 /var/log/packages/kernel-headers-3.14.4-x86-1
-rw-r--r-- 1 root root 970 May 26 12:24 /var/log/packages/kernel-huge-3.14.4-x86_64-1
-rw-r--r-- 1 root root 229836 May 26 12:25 /var/log/packages/kernel-modules-3.14.4-x86_64-1
-rw-r--r-- 1 root root 2966619 May 26 12:30 /var/log/packages/kernel-source-3.14.4-noarch-1

>lustre file system ? just asking, think its something with the filesystem
Many years I use reiserFS and is ok

Now Server working 6 days without crash and I hope that new kernel helps me.
 
Old 06-01-2014, 02:37 PM   #7
tronayne
Senior Member
 
Registered: Oct 2003
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,121

Rep: Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819Reputation: 819
Quote:
Originally Posted by kerszi View Post
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.

Glad you've got it going.
 
Old 06-02-2014, 05:39 AM   #8
kerszi
LQ Newbie
 
Registered: May 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
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.
 
Old 06-02-2014, 07:43 AM   #9
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 232

Rep: Reputation: 56
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'.
 
1 members found this post helpful.
Old 06-02-2014, 09:17 AM   #10
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
Quote:
Originally Posted by WhiteWolf1776 View Post
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.

Eric
 
1 members found this post helpful.
Old 06-02-2014, 10:14 AM   #11
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Pittsburgh, PA
Distribution: Slackware
Posts: 232

Rep: Reputation: 56
And this is what I get for posting before coffee..... coffee.. then post... coffee... then post...
 
Old 06-02-2014, 06:36 PM   #12
kerszi
LQ Newbie
 
Registered: May 2014
Posts: 4

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by WhiteWolf1776 View Post
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'.
Yes, you'r right. I mean "lost power"
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
64 bit JVM crash on RHEL 5.5 64 bit ( JRE 1.6 update 23 ) - strace attached bangarrajuv Red Hat 1 07-14-2011 11:00 AM
[SOLVED] Firefox crash in 13.1 (32 bit) fgcl2k Slackware 12 03-10-2011 05:51 AM
Wine 32 bit on Slackware 13 64 bit problems: configure can't find some libraries ozanbaba Slackware 28 11-26-2010 03:42 PM
Slackware 13 64 bit (+hybrid) server crash LyCC Linux - Server 6 11-12-2010 08:45 AM
[SOLVED] ati driver 32-bit compatibility for Slackware 64-bit multilib? vik Slackware 25 02-16-2010 08:06 PM


All times are GMT -5. The time now is 02:15 AM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration