Random freezes - Intel

Purgator · 2017-01-09 17:08:20

I got many times freeze during an update (pacman -Syu)

seth · 2017-01-09 19:12:09

"smartctl -a /dev/sda" - this might not be "intel" at all by "dying disk"? It *is* a disk and not some usb key on usb 1.0, is it ;-)

Purgator · 2017-01-10 10:10:23

I don't understand what you mean. Do you mean it may not be related to intel graphics ? It would be an issue on my SSD. I agree that a possibility.
I could upgrade the firmware but it doesn't seems to help http://www.crucial.com/usa/en/support-ssd-firmware

Maybe my SSD is a deficient product, but that appear only under Arch Linux, not Windows 7 dunno really why. I have not tryed with other windows.

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.13-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron MX100/MX200/M5x0/M600 Client SSDs
Device Model:     Crucial_CT256MX100SSD1
Serial Number:    14310CD506E8
LU WWN Device Id: 5 00a075 10cd506e8
Firmware Version: MU01
User Capacity:    256 060 514 304 bytes [256 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Jan 10 10:46:20 2017 CET
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

General SMART Values:
Offline data collection status:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
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: 		( 1190) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					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: 	 (   3) minutes.
Conveyance self-test routine
recommended polling time: 	 (   3) minutes.
SCT capabilities: 	       (0x0035)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocate_NAND_Blk_Cnt 0x0033   100   100   000    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3455
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2022
171 Program_Fail_Count      0x0032   100   100   000    Old_age   Always       -       0
172 Erase_Fail_Count        0x0032   100   100   000    Old_age   Always       -       0
173 Ave_Block-Erase_Count   0x0032   099   099   000    Old_age   Always       -       34
174 Unexpect_Power_Loss_Ct  0x0032   100   100   000    Old_age   Always       -       109
180 Unused_Reserve_NAND_Blk 0x0033   000   000   000    Pre-fail  Always       -       2159
183 SATA_Interfac_Downshift 0x0032   100   100   000    Old_age   Always       -       0
184 Error_Correction_Count  0x0032   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0022   070   049   000    Old_age   Always       -       30 (Min/Max 14/51)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
202 Percent_Lifetime_Used   0x0031   099   099   000    Pre-fail  Offline      -       1
206 Write_Error_Rate        0x000e   100   100   000    Old_age   Always       -       0
210 Success_RAIN_Recov_Cnt  0x0032   100   100   000    Old_age   Always       -       0
246 Total_Host_Sector_Write 0x0032   100   100   000    Old_age   Always       -       7150218838
247 Host_Program_Page_Count 0x0032   100   100   000    Old_age   Always       -       226646112
248 Bckgnd_Program_Page_Cnt 0x0032   100   100   000    Old_age   Always       -       328793680

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Vendor (0xff)       Completed without error       00%      3370         -

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.

seth · 2017-01-10 21:05:52

"pacman -Syu" notably does two things:
1. write a lot on disk ;-)
2. write many lines into the terminal

The smart output does't look crtical - where did/do you run pacman? (linux console, desktop enviroment, session type, terminal emulator, ssh?) - does it also happen on VT1?

ugjka · 2017-01-10 21:28:44

If this is intel graphics problem you could try this which is a kernel with latest intel stuff. But make sure you have backups, the code is untested.

Purgator · 2017-01-11 09:06:16

@Seth
I run pacman into a terminal emulator on my local xfce desktop environment.
I can try update in VT1 in the future. In this case, may I stop every graphical environment ?

Note if I write big files on my disk, nothing goes wrong.

@ugjka
I may try if all the rest doesnt work, I was pretty sure it was intel graphics but today i doubt about it.

seth · 2017-01-11 11:54:33

You may, but most likely would not even have to.
The problem may be the terminal emulator (which one), the (xface?) compositor or really just X11 - something would stumble on the "massive" buffer updates.
So redirecting the pacman output somewhere else (off-screen or by using VT1) might prove being more robust, hinting the path to track.

Purgator · 2017-01-11 13:18:54

I'm not sure we are going to the correct way. Just as a reminder the freeze can occur in every situation, even without any terminal opened. Also, when I run pacman -Syu under my terminal emulator, that may freeze or not freeze, it's not every time.
I'm gonna update thru VT1, but I can't be sure that the test is reliable, because update in terminal emulator can work without any issue.

I will let you know

Terminal emulator : xfce terminal
Compositor : xfce compositor (or idk).

cirrus · 2017-01-11 15:34:53

OP consider running

journalctl -f

in a terminal emulator and during next freeze it *might* output something more to go on.

Last edited by cirrus (2017-01-11 15:35:27)

Purgator · 2017-01-11 16:12:30

If it record in journactl, I should be able to see it after the freeze, right ?

I'm gonna open this during a pacman update but I can't do more while freeze is random and can happen everytime. I can't let on foreground a terminal emulator while working xD

cirrus · 2017-01-11 19:06:42

Purgator wrote:

If it record in journactl, I should be able to see it after the freeze, right ?

Sadly it's not a given, it depends on some factors, one of which is if the buffers get written to disk, in my experience usually not, but you will be able to see the output, maybe use tmux or one of them emulators which allows split panes. Then you can both work and keep eye on it.

helmholtze · 2017-01-12 07:03:58

There are also freezes occured in my laptop which has a i5 CPU and intel graphics since the kernel 4.7 .
Maybe that's the problem "Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips"

Add the following kernel parameter to your boot loader (e.g GRUB2) :

i915.enable_execlists=0

or maybe you can install the kernel 'linux-lts' instead.

See also
https://wiki.archlinux.org/index.php/in … re-M_chips
https://bbs.archlinux.org/viewtopic.php?id=213495
https://bbs.archlinuxcn.org/viewtopic.php?id=4519 (Chinese)

Last edited by helmholtze (2017-01-12 10:31:45)

Purgator · 2017-01-12 09:31:31

@cirrus : I just open a terminal emulator on a corner of the screen and that ok (read only, no border etc).

@helmholtze : I'm on bay trail my cpu is a pentium N3540.
I doesn't have any log then it's not related to "Kernel crashing w/kernels 4.0+ on Broadwell/Core-M chips"

Then i don't think i can solve my issue with that. I may try in the future.

EDIT : I think it may be related to this bug : https://bugzilla.kernel.org/show_bug.cgi?id=109051
I tryed the intel_idle.max_cstate=1 flag since the beginning but there are some patch related in this bug reported which could help. I may try using those patch but at the moment i have no idea how to use them.

EDIT : I see sometimes in logs :

janv. 16 12:40:49 legendance kernel: perf: interrupt took too long (2551 > 2500), lowering kernel.perf_event_max_sample_rate to 78300
janv. 16 12:46:17 legendance kernel: perf: interrupt took too long (3204 > 3188), lowering kernel.perf_event_max_sample_rate to 62400
janv. 16 12:53:47 legendance kernel: perf: interrupt took too long (4012 > 4005), lowering kernel.perf_event_max_sample_rate to 49800

janv. 16 14:08:10 legendance kernel: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
janv. 16 14:08:10 legendance kernel: mce: [Hardware Error]: Machine check events logged
janv. 16 14:08:10 legendance kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1)
janv. 16 14:08:10 legendance kernel: mce: [Hardware Error]: Machine check events logged
janv. 16 14:08:10 legendance kernel: CPU2: Core temperature above threshold, cpu clock throttled (total events = 1)
janv. 16 14:08:10 legendance kernel: CPU3: Core temperature above threshold, cpu clock throttled (total events = 1)
janv. 16 14:08:10 legendance kernel: CPU1: Core temperature/speed normal
janv. 16 14:08:10 legendance kernel: CPU0: Core temperature/speed normal
janv. 16 14:08:10 legendance kernel: CPU2: Core temperature/speed normal
janv. 16 14:08:10 legendance kernel: CPU3: Core temperature/speed normal

I'm always having a terminal displaying journalctl -f on a second screen

Last edited by Purgator (2017-01-16 13:13:25)

Purgator · 2017-01-25 10:09:47

Hello, I was having no freeze recently and I was happy but today I got one more freeze.
As always, I got a "journalctl -f" as root on second screen and I was able to see what happened => Nothing, here are my last lines :

dbus-daemon[1364]: Activating service name='ca.desrt.dconf'
dbus-daemon[1364]: Successfully activated service 'ca.desrt.dconf'

I don't really know why this is here but I don't think it's related.

I loaded a video some minutes before the freeze. Again, I'm not sure it's related.

joaki97 · 2017-01-26 16:51:33

i also had problem like you. I have acer aspire 5750 without nvidia/amd graphics card. Problem was in motherboard. Actually, my intel wouldn't came back when fell in low power mode, so i flashed hacked bios and I turned off c-states completely. Now is everything ok.

Purgator · 2017-01-27 15:39:21

Hum why not, I'm gonna check an update for the bios.
It seems the c-states was the issue here, i got only rare freeze with it disabled.

Sadly this bug will not get fixed now, it's too old imo. Without that power managment my battery is getting low very fast

Purgator · 2017-02-06 15:59:56

I don't have any possibility to disable cstate in the bios.

After weeks running with cstate disabled from Linux, i got very less freeze. There is something wrong around this.
Recently i updated xf86-video intel with the Arch package released 3 days ago. I'm now having ton of freezes that make the computer useless.
I did a downgrade but got a freeze right after.

Regarding to this bug report : https://bugzilla.kernel.org/show_bug.cgi?id=109051, I should patch my kernel according to this attachment : https://bugzilla.kernel.org/attachment.cgi?id=251471
I have no idea ATM on how to do that, I just tryed to clone official linux git from github but i always got a freeze before the dl end.

I will let you know what happen.

ewaller · 2017-02-06 16:03:10

I did a quick look over this thread thread and saw no mention of Microcode updates for Intel. Ensure these are installed and configured.,

Awebb · 2017-02-06 17:25:54

ewaller wrote:

I did a quick look over this thread thread and saw no mention of Microcode updates for Intel. Ensure these are installed and configured.,

Well:

Awebb wrote:

Look up "microcode" on the wiki, if you haven't already.

Purgator wrote:

Thank you btw, microcode wasnt installed. I installed it and runned grub-mkconfig. Let's see if something changed

:-)

ewaller · 2017-02-06 17:27:04

I said it was a quick look

Purgator · 2017-02-07 14:20:18

I appreciate anyway

I will try the patch and then i will write a summary on the first post. I hope this patch is the answer. It should be pushed into the official linux git repo one day.

Btw, today i got 0 freeze, i just downgraded xf86-video-intel to the previous version i found in my file system. Dunno if related. version : 1:2.99.917+747+g028c946d-1

I patch the kernel in the week and i come back here.

seth · 2017-02-07 14:21:43

The common sense is to ditch xf86-video-intel and use the modesetting driver anyway.

Purgator · 2017-02-09 12:09:36

I'm getting more freeze with modesetting than xf86-video-intel with c-state disabled and the display is corrupt when i scroll on firefox with modesetting.
My custom kernel is ready. I'm going to try it soon.

Purgator · 2017-02-16 13:14:48

Hey I'm back after like a week running the patched kernel and got 0 freeze without c-states=1

I will update the first post with useful information according to the way to identify and solve the issue. Note that the official kernel may include the patch one day.

EDIT 2mn after posting this i got a freeze -_-

EDIT2 An other one ! It seems that freeze when i watch a lot of videos on youtube

Last edited by Purgator (2017-02-16 14:48:29)

Awebb · 2017-02-16 16:19:04

I get the freeze on my Baytrail when trying to switch a wireless network with netctl or netctl-auto without manually powering down the network first. This cstate 1 seems to delay the freezes for a while, but it introduces a whole set of new problems, given what a c-state is and what limiting it to the "highest" means for a mobile device.

Arch Linux

#26 2017-01-09 17:08:20

Re: Random freezes - Intel

#27 2017-01-09 19:12:09

Re: Random freezes - Intel

#28 2017-01-10 10:10:23

Re: Random freezes - Intel

#29 2017-01-10 21:05:52

Re: Random freezes - Intel

#30 2017-01-10 21:28:44

Re: Random freezes - Intel

#31 2017-01-11 09:06:16

Re: Random freezes - Intel

#32 2017-01-11 11:54:33

Re: Random freezes - Intel

#33 2017-01-11 13:18:54

Re: Random freezes - Intel

#34 2017-01-11 15:34:53

Re: Random freezes - Intel

#35 2017-01-11 16:12:30

Re: Random freezes - Intel

#36 2017-01-11 19:06:42

Re: Random freezes - Intel

#37 2017-01-12 07:03:58

Re: Random freezes - Intel

#38 2017-01-12 09:31:31

Re: Random freezes - Intel

#39 2017-01-25 10:09:47

Re: Random freezes - Intel

#40 2017-01-26 16:51:33

Re: Random freezes - Intel

#41 2017-01-27 15:39:21

Re: Random freezes - Intel

#42 2017-02-06 15:59:56

Re: Random freezes - Intel

#43 2017-02-06 16:03:10

Re: Random freezes - Intel

#44 2017-02-06 17:25:54

Re: Random freezes - Intel

#45 2017-02-06 17:27:04

Re: Random freezes - Intel

#46 2017-02-07 14:20:18

Re: Random freezes - Intel

#47 2017-02-07 14:21:43

Re: Random freezes - Intel

#48 2017-02-09 12:09:36

Re: Random freezes - Intel

#49 2017-02-16 13:14:48

Re: Random freezes - Intel

#50 2017-02-16 16:19:04

Re: Random freezes - Intel

Board footer