LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 03-19-2014, 06:57 PM   #1
Pedroski
Senior Member
 
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151

Rep: Reputation: 73
crash and KDE


I've been having trouble with Ubuntu, nautilus kept crashing, but not fatally, I could just click on files and up it came again. Following this, my laptop began to refuse to boot into Ubuntu, it froze on boot.

So I booted Fedora 20. Fed 20 works fine using xfce or gnome, but if I start KDE, when I start an application, say Dolphin, the system freezes. This must be related to the Ubuntu problems.

If I have a hardware problem, why would it not affect gnome or xfce. I can run compiz with xfce, strange special effects, no problems, everything works fine.

In which log in Fedora should I look for clues? In Ubuntu there is a syslog. There I found nautilus caused a segfault, but Fed doesn't have a syslog file.
 
Old 03-19-2014, 09:42 PM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
I would start with making basic hardware tests: Check the temperatures under load, use Memtest86+ to check the RAM, check the output of
Code:
smartctl -a /dev/sda
for problems with your harddisk (or use the disk manufacturer's diagnosis tools).
 
Old 03-19-2014, 10:31 PM   #3
Pedroski
Senior Member
 
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151

Original Poster
Rep: Reputation: 73
I ran memtest for 9 1/2 hours, 9 passes, no errors. smartctl shows

SMART Error Log Version: 1
ATA Error Count: 12 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 12 occurred at disk power-on lifetime: 967 hours (40 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 02 9e 0d 87 64 Error: UNC at LBA = 0x04870d9e = 75959710

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 00 98 0d 87 40 08 00:21:12.257 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:21:12.257 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:21:12.257 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:21:12.257 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:21:12.256 SET FEATURES [Set transfer mode]

Error 11 occurred at disk power-on lifetime: 967 hours (40 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 02 9e 0d 87 64 Error: UNC at LBA = 0x04870d9e = 75959710

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 00 98 0d 87 40 08 00:21:08.213 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:21:08.213 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:21:08.212 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:21:08.212 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:21:08.212 SET FEATURES [Set transfer mode]

Error 10 occurred at disk power-on lifetime: 967 hours (40 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 02 9e 0d 87 64 Error: UNC at LBA = 0x04870d9e = 75959710

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 00 98 0d 87 40 08 00:21:04.168 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:21:04.168 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:21:04.167 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:21:04.167 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:21:04.167 SET FEATURES [Set transfer mode]

Error 9 occurred at disk power-on lifetime: 967 hours (40 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 02 9e 0d 87 64 Error: UNC at LBA = 0x04870d9e = 75959710

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 00 98 0d 87 40 08 00:21:00.135 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:21:00.134 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:21:00.134 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:21:00.134 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:21:00.134 SET FEATURES [Set transfer mode]

Error 8 occurred at disk power-on lifetime: 967 hours (40 days + 7 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 0a 9e 0d 87 64 Error: WP at LBA = 0x04870d9e = 75959710

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 08 10 38 09 0a 40 08 00:20:56.046 WRITE FPDMA QUEUED
60 08 08 98 0d 87 40 08 00:20:56.046 READ FPDMA QUEUED
61 d0 00 50 4c 63 40 08 00:20:56.046 WRITE FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:20:56.046 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:20:56.046 READ NATIVE MAX ADDRESS EXT

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2 -
# 2 Short offline Completed without error 00% 2 -
# 3 Short offline Completed without error 00% 2 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

pedro@peterpu:~$

There may be a hardware error, but why then do gnome and xfce run fine in Fed. They have never crashed on me.
 
Old 03-19-2014, 10:57 PM   #4
Pedroski
Senior Member
 
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151

Original Poster
Rep: Reputation: 73
Just to mention it: this morning at 6am I switched on, and Ubuntu started without a hitch. It is 11 am now, no problems. But sometimes Ubuntu simply refuses to start, whereas Fed will start. That is at least strange.
 
  


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
[SOLVED] KDE 4.10.3 polkit1-kde crash in slackware 14 pataphysician Slackware 3 05-15-2013 12:21 PM
kde kicker crash while exiting kde but why? towsonu2003 Linux - Software 6 10-04-2005 11:08 PM
kde 3.4 on suse 9.3, kde crash when using xine oily_rags SUSE / openSUSE 1 05-16-2005 10:26 PM
kde crash, then other crash, now weird problems true_atlantis Linux - Laptop and Netbook 1 04-28-2004 01:01 AM
KDE 3.1.3 in Slack9 with AntiAliasing kde crash cHarOn99 Slackware 2 08-31-2003 09:06 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 06:29 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