[SOLVED] System freezes in Mageia 5 and 6

[maxperl]

Hello all,

I suffer from frequent system freezes. The system freezes in Mageia 5, but also in Mageia 6. I don't know, what is the reason for this. The last freeze in Mageia 5 occurs today at 10:52 hour. Enclosed you will find the output of the commands journalctl -r --since today > today_r.txt and journalctl --since today > today.txt. I will also enclose the Xorg.0.log.old file.

I don't know which informations additionally could be help.

PS.: Whereas I wrote this forum post, the system freezes again (at 11:17 hours, bizzarely after restart the clock showed 11:16, but after a minute again 11:19). The files of this freeze has the prefix today2...

PSS.: Again a freeze at 11:22 hours. You see, I really suffer

[maxperl]

the other files

Again a freeze at 11:30 h

[maxperl]

Please let me give a last suspicion: Perhaps it has something to do with my SSD harddrive. I have 2 harddrives. My main drive in the touchscreen is a SSD, until yesterday I have installed Mageia 6 there (with the system freezes), but yesterday I deleted Mageia 6 and installed Mageia 5 on the SDD.

The second harddrive is a normal HDD. There was until yesterday Mageia 5 (and until yesterday system freezes was not a very big problem there, but I worked mainly on the Mageia 6 system). Now there is Mageia 6.

At my first installation of Mageia 6 on the SDD I had the following bug: https://bugs.mageia.org/show_bug.cgi?id=17796

But at reinstalling Mageia 5 on the SDD I deleted all partitions. Only the first EFI partition I transfered to the new Mageia 5 system.

So sorry for so much informations Hopefully some of them are helpful. If you need additional informations, please let me know...

Please note: The freezes occur also at the HDD installation although there the system freezes not so often as the SSD installation. I have opened a bug report...

[petedan10]

Did you check SMART status just to rule out any hardware problem?

[maxperl]

No I didn't.. How do I do that? Perhaps the freezes come from my wlan problem (see https://bugs.mageia.org/show_bug.cgi?id=18843) I have bought an usb stick and blacklisted the iwlwifi module. Perhaps this solves the problems (I am testing it...).

[petedan10]

I think GSmartControl is the best there is.

[maxperl]

Dear petedan,
Thank you for your answer.
Here the details of gsmartcontrol:

/dev/sda: (This is the SSD)

smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.4.13-desktop-1.mga5] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HCG8e82022bcfbd199805
Serial Number: P026 2G06
Firmware Version: 90014a
User Capacity: 62,545,461,248 bytes [62.5 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA/ATAPI-7 T13/1532D revision 1
Local Time is: Thu Jul 7 18:10:55 2016 CEST
SMART support is: Unavailable - device lacks SMART capability.

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

/dev/sdb

smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.4.13-desktop-1.mga5] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, http://www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HGST HTS545050A7E680
Serial Number: TM85133J0SGK9M
LU WWN Device Id: 5 000cca 7decaab2f
Firmware Version: GG2OAE00
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Jul 7 18:11:38 2016 CEST
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: (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: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 118) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control 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 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 253 253 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1438
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 1068
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 908
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 57
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 8295
194 Temperature_Celsius 0x0002 176 176 000 Old_age Always - 34 (Min/Max 7/39)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0

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 Short offline Completed without error 00% 521 -

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.

[maxperl]

PS: The freezes don't come from the WLAN problem. At 16.49 h my Mageia5 system freezes again. I booted into Mageia 6 and saw after the /var/log directory. The only files where modification was made after (or better at) 16.49 were:
/var/log/messages
/var/log/user.log
/var/log/journal/****/system.journal and /var/log/journal/****/user-1000.journal (both I could not open)

Here are the last lines of messages and user.log. But I don't know whether this was some seconds before the freeze, just before or at the freeze or after. Perhaps it is helpful:
/var/log/messages

Jul 7 16:49:22 localhost systemd-logind[789]: Power key pressed.
Jul 7 16:49:30 localhost systemd-logind[789]: Power key pressed.
Jul 7 16:49:39 localhost org.gnome.Shell.CalendarServer[2014]: (gnome-shell-calendar-server:3781): ShellCalendarServer-WARNING **: Failed to start evolution-source-registry: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.evolution.dataserver.Sources3 was not provided by any .service files

/var/log/user.log

Jul 7 16:49:39 localhost org.gnome.Shell.CalendarServer[2014]: (gnome-shell-calendar-server:3781): ShellCalendarServer-WARNING **: Failed to start evolution-source-registry: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.evolution.dataserver.Sources3 was not provided by any .service files

[maxperl]

Hello, me again
I have just installed Linux Mint 18 for test purposes. And the freezes occur also there. Therefore I think it is a hardware defect... But which hardware could be affected? Any ideas, how I can figure out this (and then repair it)?

[jiml8]

If you are satisfied that it is a hardware fault, I would start with the hard drive or SSD as a candidate. Should I eliminate them, I would look at RAM and finally at the power supply. Normally I would expect a freeze from bad RAM to be permanent until a reboot, but not necessarily. Similarly, I would expect a freeze caused by the power supply to be permanent pending reboot, but not necessarily.

I note that your SSD apparently does not have SMART capability. The SSDs that I myself am familiar with all have SMART capability; you did not specify the make and model of your device, but this could be an indicator of an SSD problem. Or, it might just need to be TRIMmed.

[maxperl]

Dear jumi8,
Thanks for your answer.
I did a memtest86 yesterday. All 48 tests passed. Unfortunately I have accidentally deleted the HTML result logs. Sorry. If these are important, I will do a memtest again tonight (it lasted all the night).

The model name of the SSD is "HCG8e 82022bcfbd"
Trim doesn't work, too:

maximilian@maximilian-P2212T ~ $ sudo fstrim /
fstrim: /: the discard operation is not supported

I remebered, that earlierly trim etc. worked. I had to repair the notebook, and perhaps there the sdd was changed?
Perhaps the problem is that the command of "hdparm -I /dev/sda" returns under the item "Model Number" a curious sign (here unfortunately not visible, in the terminal just before the second "8" is a box with four numbers (0004)) and there is not recognized by the commands fstrim etc?

/dev/sda:

ATA device, with non-removable media
Model Number: HCG8e82022bcfbd199805
Serial Number: P026 2G06
Firmware Revision: 90014a
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 1
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 0
heads 16 0
sectors/track 63 0
--
LBA user addressable sectors: 122159104
LBA48 user addressable sectors: 122159104
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 59648 MBytes
device size with M = 1000*1000: 62545 MBytes (62 GB)
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Vendor, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: udma4 udma5 *udma6 udma7
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* Power Management feature set
* Removable Media Status Notification feature set
* 48-bit Address feature set
Mandatory FLUSH_CACHE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Host-initiated interface power management
Removable Media Status Notification feature set supported
Checksum: correct

But I don't think that the SSD is the problem because also the Mageia System on /dev/sdb (the normal HDD) freezes from time to time. All partitions (except the /boot/efi) are in this installation located on the HDD /dev/sdb!

But actual suspicion is that the processor is too hot. Sometimes I got a warning that the temperature is too high... How can I test this?

[ozky]

Can you please give more information of your system hardware ?.

[ozky]

If you are satisfied that it is a hardware fault, I would start with the hard drive or SSD as a candidate. Should I eliminate them, I would look at RAM and finally at the power supply. Normally I would expect a freeze from bad RAM to be permanent until a reboot, but not necessarily. Similarly, I would expect a freeze caused by the power supply to be permanent pending reboot, but not necessarily.

I note that your SSD apparently does not have SMART capability. The SSDs that I myself am familiar with all have SMART capability; you did not specify the make and model of your device, but this could be an indicator of an SSD problem. Or, it might just need to be TRIMmed.

This sounds more kernel side problem can be this same problem what my laptop suffers.

https://bugzilla.kernel.org/show_bug.cgi?id=109051
https://wiki.archlinux.org/index.php/in ... tel_driver
https://bugs.mageia.org/show_bug.cgi?id=17387

[maxperl]

Dear ozky,
Thank you very much for your answers. Enclosed you will find the output of the commands of lspcidrake -v, lsusb and cat /proc/cpuinfo.
If you need further informations, please let me know.

The things with the kernel side problem I will read and proove later because this evening I am not on my laptop... But thanks also for this advices!

[ozky]

Found it Intel(R) Celeron(R) CPU N2920 @ 1.86GHz is baytrail prosessor,my laptop have 2840 model.
So you need to add to grub line intel_idle.max_cstate=1 until bug is fixed by kernel devs.
Then answer if it helps.

https://bugzilla.kernel.org/show_bug.cgi?id=109051

[jiml8]

This sounds more kernel side problem can be this same problem what my laptop suffers.

My first thought was also kernel, but OP has tried Mint as well. Mint is sufficiently different that I was willing to go along with OP's determination that it was probably hardware. However, Mint 18 uses the 4.4 kernel which is the same basic kernel the latest release of Mageia 5 uses.

Should you wish to look at the kernel, you probably ought to look at these tunables:

vm.dirty_background_ratio
vm.dirty_ratio
vm.overcommit_ratio
vm.overcommit_memory

The dirty tunables will lead to long pauses due to I/O waits if they are not set appropriately for the running system. The overcommit settings have to do with memory management.

[ozky]

That c state bug jiml8 affects to all kernels not only 4.4 all from 4.2.x to 4.7,kernel don't need to match with version number if bug is not fixed.
If you look this bug report it's huge and affects like i said many kernels i doupt those your ratio things would do nothing.
https://bugzilla.kernel.org/show_bug.cgi?id=109051

[maxperl]

Dear ozky,
You are great!!!! Since adding the kernel options I had no freeze any more and also my wlan problem (see https://bugs.mageia.org/show_bug.cgi?id=18843) went away!
Only after hibernation and standby ( I hope this is the right word in English; in German it is "Ruhezustand" and "Bereitschaft") the laptop doesn't wake up. But this is for me a minor problem because I always shut the notebook down. But if someone has an idea, you are welcome...

Again thank you all very much for your help!

[ozky]

Awesome i did have that clue that looks same problem i have had with my laptop....good it's now fixed.