LinuxQuestions.org - kerassshhhh

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - kerassshhhh (https://www.linuxquestions.org/questions/slackware-14/kerassshhhh-736132/)

Hi, I installed 12.2 about 1 month ago. I have experienced 3 crashes and I am concerned that the last 2 have been this week.

I boot into run level 3, sign in and startx kicks off KDE. I generally shutdown the computer at night. Today I was simply web browsing and the system reverted to a terminal window, locked up and I had to power it down.

I guess there is a crash log somewhere which will point me in the direction of the problem. Can anyone advise where I find this?

Quote:

Originally Posted by timl (Post 3588581)

post the out put of 'dmesg', /var/log/syslog, var/log/messages.

Are you sure your computer doesn't overheat? That's the most usual reason for crashes. Monitor your temperature with the sensors command.
I would also check the memory.

I have attached the output from dmesg. It is quite long though.

Noted about overheating. I can't find the sensors command on any of my redhat systems (which are quite old). Is this slackware specific? I would like to compare to my server which has been up for several weeks now.

I don't see anything interesting in your dmesg, and I don't think I should, 'cause dmesg output doesn't usually survive a crash... :)
/var/log/messages would provide more info.
Look for an lm_sensors (or lm-sensors) package for your redhat system. It should be there, it's not Slackware specific.

here is the messages file (last 250K)

Quote:

Originally Posted by timl (Post 3588663)

here is the messages file (last 250K)

Aha, there is a segfault occurring, this might be part of your problems.

here is the line I am looking at:

Code:

Jun 28 14:15:19 autumn kernel: dvdauthor[5985]: segfault at ffffffc4 ip 08053b9b sp bfbf3690 error 4 in dvdauthor[8048000+1b000]

Try re-installing the dvdauthor package and see what happens.

Link here:

http://slackbuilds.org/repository/12...dia/dvdauthor/

Quote:

Originally Posted by C-Sniper (Post 3588669)

Aha, there is a segfault occurring, this might be part of your problems.

here is the line I am looking at:

Code:

Jun 28 14:15:19 autumn kernel: dvdauthor[5985]: segfault at ffffffc4 ip 08053b9b sp bfbf3690 error 4 in dvdauthor[8048000+1b000]

Doubtful, that same application crashes 3 times over 15 minutes according to the log and then there are more --MARK-- entries afterwards for another 2 hours.

Go back a bit more and there is a shutdown event at 13:52, if the OP can confirm this time as when today's problem occurred then we might know a bit more.

Here is a snippet from the last shutdown. I am still digging through the rest of the messages though

Code:

Jun 28 11:25:42 autumn -- MARK --

Jun 28 11:45:42 autumn -- MARK --

Jun 28 12:05:43 autumn -- MARK --

Jun 28 12:14:12 autumn sshd[3362]: Accepted password for tim from 192.168.1.117 port 35098 ssh2

Jun 28 12:25:43 autumn -- MARK --

Jun 28 12:45:43 autumn -- MARK --

Jun 28 13:05:43 autumn -- MARK --

Jun 28 13:25:44 autumn -- MARK --

Jun 28 13:45:44 autumn -- MARK --

Jun 28 13:49:18 autumn kernel: cdrom: This disc doesn't have any tracks I recognize!

Jun 28 13:52:21 autumn init: Switching to runlevel: 0

Jun 28 13:52:28 autumn /usr/sbin/gpm[3012]: *** info [mice.c(1766)]: 

Jun 28 13:52:28 autumn /usr/sbin/gpm[3012]: imps2: Auto-detected intellimouse PS/2

Jun 28 13:52:31 autumn sshd[2826]: Received signal 15; terminating.

Jun 28 13:52:31 autumn saslauthd[2920]: server_exit    : master exited: 2920

Jun 28 13:52:33 autumn logger: /etc/rc.d/rc.inet1:  /sbin/route del default

Jun 28 13:52:33 autumn logger: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -k -d eth0

Jun 28 13:52:34 autumn logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig lo down

Jun 28 13:52:39 autumn acpid: exiting 

Jun 28 13:52:39 autumn exiting on signal 15

From what I can see in the last couple of shutdowns everything looks normal. What does syslog say?

I'm betting it's the nvidia drivers, looks like you have them installed. Try upgrading, or downgrading. On slackware, I have found that all my machine are rock solid until I install the nvidia drivers, then the crashing starts ... but not with every version.

If you don't find anything in the logs, my bet is 90 % chance nvidia drivers are to blame.

I agree with H_TeXMeX_H, it looks like something crashed X and locked up the system. Video driver is the most likely reason.

okay, I'll give that a go thanks.

Wrote that after c-sniper's post. Noted about the video drivers. I think I went for the latest drivers. I'll review these.