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 03-21-2012, 01:59 PM   #1
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 14.2 running TWM
Posts: 474

Rep: Reputation: 137Reputation: 137
Random restarts Slackware64 13.37


It doesn't reboot, just flicks off in an instant, and then immediately starts up again from the beginning of the boot sequence; so one moment I could be browsing this forum and the next I'm looking at a black screen as it starts to boot.

I've opened it up and cleaned it out, re-seated the memory. I don't think it is overheating as it happened just now after ten minutes uptime and yet another time it could run all day and then do it. It's not even an everyday occurrence but it is about 2-3 times a week maybe.

The box is about a year old, it's an Acer i3 quad core, 4GB RAM, 1TB HD, NVIDIA GeForce 315 running Slackware64 13.37 with the binary NVIDIA driver installed.

I looked at /var/log/messages but there doesn't seem to be much there:

Mar 21 17:33:46 rebelCode kernel: [ 115.271932] newsbeuter[2434]: segfault at 0 ip 00007fc77a281e86 sp 00007fc773ffdfd8 error 4 in libc-2.13.so[7fc77a15d000+19b000]
Mar 21 17:36:49 rebelCode kernel: [ 297.884261] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Mar 21 17:37:49 rebelCode kernel: [ 357.030210] r8169 0000:02:00.0: eth0: link up
Mar 21 17:39:38 rebelCode kernel: [ 465.602739] newsbeuter[2981]: segfault at 0 ip 00007f7f95773e86 sp 00007f7f93795fd8 error 4 in libc-2.13.so[7f7f9564f000+19b000]
Mar 21 17:44:27 rebelCode syslogd 1.5.0: restart.
Mar 21 17:44:27 rebelCode kernel: klogd 1.5.0, log source = /proc/kmsg started.
Mar 21 17:44:27 rebelCode kernel: 0fff]
Mar 21 17:44:27 rebelCode kernel: [ 0.608413] pnp: PnP ACPI: found 16 devices
Mar 21 17:44:27 rebelCode kernel: [ 0.608523] ACPI: ACPI bus type pnp unregistered

is where it happened just now (newsbeuter segfaulted on the 'China Daily' feed, I had to comment it out).

I was wondering what the best way to approach this would be?
 
Old 03-21-2012, 02:31 PM   #2
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292Reputation: 1292
The first thing I would suspect is the proprietary nvidia drivers, they usually leave no trail behind when they crash. Also check /var/log/syslog and Xorg.0.log.
 
Old 03-22-2012, 01:30 PM   #3
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 14.2 running TWM
Posts: 474

Original Poster
Rep: Reputation: 137Reputation: 137
I can't see much in the logs that gives me a pointer towards the problem.

I'll try running with the nouveau driver for a while, see what happens.

Thanks.
 
Old 03-24-2012, 05:19 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2 and Slackware64 -current (AKA Slackware64 15)
Posts: 3,803

Rep: Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166Reputation: 2166
You may want to run memtest overnight to see if one of your ram chips is failing.
 
Old 03-24-2012, 06:29 PM   #5
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 14.2 running TWM
Posts: 474

Original Poster
Rep: Reputation: 137Reputation: 137
I will do. Thank you.
 
Old 03-24-2012, 08:51 PM   #6
kingbeowulf
Senior Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware
Posts: 1,142
Blog Entries: 11

Rep: Reputation: 575Reputation: 575Reputation: 575Reputation: 575Reputation: 575Reputation: 575
It is possible that the heat sink on the CPU is loose.

And no, although the proprietary Nvidia blob can sometime crash X server, it will not reboot Slackware, and I have been running it for years since Geforce256 DDR.
 
  


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
Fedora 10: X restarts on its own on a random basis. Iltbreg Fedora 5 02-09-2009 02:16 PM
Urgent - random restarts on production server ??? Avatar Linux - General 4 06-13-2007 10:37 AM
random restarts? nick623 Ubuntu 10 05-08-2007 04:07 PM
Still X Random restarts redhatnoob Linux - General 2 02-17-2004 05:25 PM
Random X restarts on new install tomser Linux - Hardware 6 09-07-2003 10:32 PM

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

All times are GMT -5. The time now is 05:38 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
Open Source Consulting | Domain Registration