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 |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
03-19-2014, 06:57 PM
|
#1
|
Senior Member
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151
Rep:
|
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.
|
|
|
03-19-2014, 09:42 PM
|
#2
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
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).
|
|
|
03-19-2014, 10:31 PM
|
#3
|
Senior Member
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151
Original Poster
Rep:
|
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.
|
|
|
03-19-2014, 10:57 PM
|
#4
|
Senior Member
Registered: Jan 2002
Location: Nanjing, China
Distribution: Ubuntu 22.04
Posts: 2,151
Original Poster
Rep:
|
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.
|
|
|
All times are GMT -5. The time now is 06:29 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|