You are not logged in.
Hello guys,
My laptop often freezes (once a day maybe). The reason can be my hdd, which had some problems once.
Here is the output of "smartctl -a /dev/sda | less"
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.8.0-26-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 5400.6
Device Model: ST9500325AS
Serial Number: 5VES9WBZ
LU WWN Device Id: 5 000c50 049699619
Firmware Version: D005DEM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Fri Aug 2 10:11:08 2013 GST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 134) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 091 006 Pre-fail Always - 155744204
3 Spin_Up_Time 0x0003 099 098 085 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2073
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 71436241
9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2782
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1952
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always -
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 5
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 043 045 Old_age Always In_the_past 39 (0 15 39 38 0)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 110
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 122
193 Load_Cycle_Count 0x0032 091 091 000 Old_age Always - 19330
194 Temperature_Celsius 0x0022 039 057 000 Old_age Always - 39 (0 13 0 0 0)
195 Hardware_ECC_Recovered 0x001a 052 046 000 Old_age Always - 155744204
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 3
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 3
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 1
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 135364484270756
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3830158476
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 40434943
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 1099 (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 1099 occurred at disk power-on lifetime: 2310 hours (96 days + 6 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 00 ff ff ff 4f 00 00:27:54.820 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:54.818 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:54.817 READ FPDMA QUEUED
60 00 30 e0 c5 66 4d 00 00:27:54.767 READ FPDMA QUEUED
60 00 40 a0 c5 66 4d 00 00:27:54.762 READ FPDMA QUEUED
Error 1098 occurred at disk power-on lifetime: 2310 hours (96 days + 6 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 00 ff ff ff 4f 00 00:27:51.953 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:51.953 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:51.953 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:51.951 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00:27:51.918 FLUSH CACHE EXT
Error 1097 occurred at disk power-on lifetime: 2310 hours (96 days + 6 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 00 ff ff ff 4f 00 00:27:40.639 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:40.639 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:40.638 READ FPDMA QUEUED
60 00 58 b0 31 79 4e 00 00:27:40.626 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:27:40.625 READ FPDMA QUEUED
Error 1096 occurred at disk power-on lifetime: 2310 hours (96 days + 6 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 00 ff ff ff 4f 00 00:27:35.968 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:35.968 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:35.967 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:27:35.967 READ FPDMA QUEUED
60 00 20 40 66 7c 4d 00 00:27:35.966 READ FPDMA QUEUED
Error 1095 occurred at disk power-on lifetime: 2310 hours (96 days + 6 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
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 00 00 ff ff ff 4f 00 00:24:10.538 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:24:10.538 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:24:10.538 READ FPDMA QUEUED
61 00 20 ff ff ff 4f 00 00:24:10.537 WRITE FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:24:10.523 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 2499 773820463
# 2 Short offline Completed: read failure 90% 2499 773820463
# 3 Short offline Completed: read failure 90% 2487 773820463
# 4 Extended offline Completed: read failure 90% 2481 773820463
# 5 Short offline Completed: read failure 90% 2481 773820463
# 6 Short offline Completed: read failure 90% 1592 773820463
# 7 Short offline Completed: read failure 90% 1229 753218749
# 8 Short offline Completed: read failure 90% 1229 753218749
# 9 Short offline Completed: read failure 90% 1226 753218749
#10 Short offline Completed: read failure 90% 1226 753218749
#11 Short offline Completed without error 00% 1154 -
#12 Short offline Completed without error 00% 1121 -
#13 Short offline Completed without error 00% 796 -
#14 Short offline Completed without error 00% 773 -
#15 Short offline Completed without error 00% 271 -
#16 Short offline Completed without error 00% 187 -
#17 Short offline Completed without error 00% 53 -
#18 Short offline Completed without error 00% 1 -
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.
I am not running system intensive stuff. Most often I am developing in qt creator and running chrome, rarely exceeds 2gb of ram (My system has 4). I doubt it is because of hdd because most often, it freezes when I am building application.
If this was windows, I wouldn't be surprised but on linux, I shouldn't have those kind of issues.
Last edited by khajvah (2013-09-23 22:16:03)
Offline
Hi Khajvah,
This maybe unrelated, but it could be worth a try.
I had the same problem on my laptop a while ago, that it would just freeze with no apparent reason.
It turned out to be a pulseaudio problem, so try to uninstall (or disable) it, if it is installed, and check if the problem persists.
I am sorry, but I have no experience with hdds, so I do not know how to help you if that is really the problem!
Offline
Tell me, is your hard drive spinning up and down constantly? I had similar problems (not with QtCreator or Komodo, but with games and even sometimes while surfing) which produced system freezing for a few seconds or more because of hard drive spinning.. I fixed that by adding:
ACTION=="add", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1", RUN+="/usr/bin/hdparm -B 254 /dev/$kernel"
to /etc/udev/rules.d/75-hdparm.rules
If that doesn't help, can you tell me which DE are you using and list laptop's hardware?
Using Arch Linux x86-64 (linux-ck-bobcat kernel) on AMD based laptop with HD 7400 series GPU.
dd if=/dev/null of=/dev/everything
Offline
Thanks for answers, I don't have pulseaudio installed, so that's not a problem.
About spinning, it is not freezing for just few seconds. Every time it freezes, I have to reboot to be able to use.
I am running KDE and my specs are:
Intel® Core™ i5-3210M processor
4gb RAM
For graphics, it's Intel® HD Graphics 4000 and geforce gt 630m. (optimus shit)
Offline
Can you move to console (ctrl+alt+F2) when freeze occurs? Does freezes happen with other DE, or when effects are disabled on KDE? Have you checked logs after reboot and found something strange/suspicious?
Using Arch Linux x86-64 (linux-ck-bobcat kernel) on AMD based laptop with HD 7400 series GPU.
dd if=/dev/null of=/dev/everything
Offline
Can you move to console (ctrl+alt+F2) when freeze occurs? Does freezes happen with other DE, or when effects are disabled on KDE? Have you checked logs after reboot and found something strange/suspicious?
I once was able to move to console but it was again too laggy and I couldn't use. I am using only one DE...
Offline
How can I see logs?
Offline
I will use pantheon as DE for some time to see if I have any problems with it
Offline
How can I see logs?
You can view system logs via journalctl, and Xorg logs in /var/log/
Using Arch Linux x86-64 (linux-ck-bobcat kernel) on AMD based laptop with HD 7400 series GPU.
dd if=/dev/null of=/dev/everything
Offline
The SMART logs you posted above appear to show errors. Do those error counts increase after you experience the freezes you describe? I'd make a backup ASAP, BTW.
Offline
Some people with Intel graphics were having freezing issues with the last couple of kernel versions. Do a search of the forums for threads about that.
The freeze you're describing is a hard freeze, right? Like the screen still shows a picture, but you can't interact at all- no Ctrl+Alt+F1, etc., correct?
Offline
Some people with Intel graphics were having freezing issues with the last couple of kernel versions. Do a search of the forums for threads about that.
The freeze you're describing is a hard freeze, right? Like the screen still shows a picture, but you can't interact at all- no Ctrl+Alt+F1, etc., correct?
I'm having similar issues with a Dell XPS L702X. System randomly freezes, keyboard is not responsive (cannot change tty or kill X via Ctrl+Alt+Bkspc) and sometimes there is caps-lock led blinking. Only a power cut can terminate this situation. It's a little bit I'm searching the Internet for a possible solution, I read about the presumed pulseaudio problem, but even reverting to a version known not to have the bug cannot solve the problem. I've tried multiple kernels as well, checking 3.11.x, 3.12 and 3.10-lts, in both x86 and x86 with PAE enabled configuration, but I could not manage to understand if this is relevant and how. I've found that systemd may be involved but no clear clues here neither. Log files do not help that much since I think that maybe relevant informations just can't be written in the logs as the system freezes.
In kernel.log, the only recurrent piece of log that usually (but not always) comes up when this problem happens is this:
[43329.363003] ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
[43329.363006] ata6.00: irq_stat 0x00400000, PHY RDY changed
[43329.363008] ata6: SError: { PHYRdyChg CommWake }
[43329.363011] sr 5:0:0:0: CDB:
[43329.363012] cdb[0]=0x4a: 4a 01 00 00 10 00 00 00 08 00
[43329.363018] ata6.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
[43329.363018] res 50/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error)
[43329.363020] ata6.00: status: { DRDY }
[43329.363023] ata6: hard resetting link
[43330.112721] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[43330.118491] ata6.00: configured for UDMA/100
[43330.132756] ata6: EH complete
Checking disk drive SMART test shows a past over-threshold measure about drive temperature, but so far it would not seem that there is any hardware failure incoming.
Other signs I cannot explain nor relate to the main problem, is that in dmesg some core dumps show up randomly. Usually processes which seem to dump core are sd_festival, pulseaudio, systemd (of course, when systemd dumps core system is unusable as I cannot even properly turn it off if init daemon dies this way...), alsa-sink, chromium and even emacs. I could not find a pattern or clues about what kind of problem may be this on the Internet.
I'm sorry if this post lacks relevant informations but, as told, I've no clue about where to start.
System is a Dell XPS L702X laptop with a 500 GB Seagate Momentus 7200.4 hard drive with /boot (ext2), / and /home (ext4) partitions.
More complete kernel.log files:
kernel.log.0
kernel.log.1
Thanks,
Luca
Last edited by enigmatichus (2013-11-21 14:09:23)
Luca
Arch Linux x86_64 | Dell XPS L702X | Intel core i7 2720QM | 8192MB RAM 1333 Mhz | Nvidia GeForce GT555M | 3D 1920x1080 LED
Offline
exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
That error may not be related to the freezing, but points to a problem with your drive cabling.
check the connectors and cables connecting the hdd with the motherboard
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
That error may not be related to the freezing, but points to a problem with your drive cabling.
check the connectors and cables connecting the hdd with the motherboard
Thanks for the super-fast answer, since this is a laptop system and so the disk drive gets inserted straight on a socket and I don't have access to internal cablings to the laptop motherboard, what should I do? Is this incompatible with a disk failure itself (was already checking for a replacement unit) so I can exclude it? Again, thank you for you patience and your swiftness.
Luca
Luca
Arch Linux x86_64 | Dell XPS L702X | Intel core i7 2720QM | 8192MB RAM 1333 Mhz | Nvidia GeForce GT555M | 3D 1920x1080 LED
Offline
enigmatichus,
first i think you should start a new thread about this problem, or ask mods to split these posts into a new thread.
The cause of that error is a temporary loss of connection between controller and drive.
While i have encountered similar errors caused by a faulty drive, in the majority of cases it's a connector/cabling problem.
You (or a technician) will have to open the laptop case to verify the cabling/connector/sockets.
if that is not doable, try reseating the driver or put another drive known to work well in the socket and test.
You should be able to use a live environment and run some programs that will stress the system, especially the harddrives.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
enigmatichus,
first i think you should start a new thread about this problem, or ask mods to split these posts into a new thread.
The cause of that error is a temporary loss of connection between controller and drive.
While i have encountered similar errors caused by a faulty drive, in the majority of cases it's a connector/cabling problem.
You (or a technician) will have to open the laptop case to verify the cabling/connector/sockets.if that is not doable, try reseating the driver or put another drive known to work well in the socket and test.
You should be able to use a live environment and run some programs that will stress the system, especially the harddrives.
I've created a separate thread here.
I've checked internal hard drive connection in the laptop, and unfortunately there is not much I can do on myself since connector seems soldered on the motherboard. I will check another (working) drive via a live-cd and some hard-disk stressing test suite soon.
Thanks,
Luca
Luca
Arch Linux x86_64 | Dell XPS L702X | Intel core i7 2720QM | 8192MB RAM 1333 Mhz | Nvidia GeForce GT555M | 3D 1920x1080 LED
Offline