Bug 22428 - After last update all my drives go into suspend mode too frequently
Summary: After last update all my drives go into suspend mode too frequently
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-20 12:11 CET by Pavel Roschin
Modified: 2020-08-16 15:59 CEST (History)
2 users (show)

See Also:
Source RPM: kernel?, microcode?
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pavel Roschin 2018-01-20 12:11:34 CET 
Description of problem:
I disabled suspend mode for all disks long time ago. But after recent update I noticed that both my disks spin-up too frequently (seems that disk suspends after 10 seconds of inactivity). I tried to disable suspend mode using hdparm -S0 but that didn't help.

I did nothing with my system except update. I don't know which component caused that bug. Is it possible that microcode update for Meltdown/Spectre causes that bug?

Here is full package list of that update:
  cpupower.x86_64 4.14.13-1.mga6                      dkms-nvidia-current.x86_64 384.111-1.mga6.nonfree             
  dracut.x86_64 044-11.1.mga6                         dumpcap.x86_64 2.2.12-1.mga6                                  
  kernel-desktop-devel-latest.x86_64 4.14.13-1.mga6   kernel-desktop-latest.x86_64 4.14.13-1.mga6                   
  kernel-userspace-headers.x86_64 4.14.13-1.mga6      ldetect-lst.x86_64 0.3.7.5-1.mga6                             
  lib64gd3.x86_64 2.2.5-2.mga6                        lib64javascriptcore-gir4.0.x86_64 2.18.5-1.mga6               
  lib64javascriptcoregtk4.0_18.x86_64 2.18.5-1.mga6   lib64poppler-glib8.x86_64 0.52.0-3.6.mga6                     
  lib64poppler66.x86_64 0.52.0-3.6.mga6               lib64vorbis-devel.x86_64 1.3.5-2.1.mga6                       
  lib64vorbis0.x86_64 1.3.5-2.1.mga6                  lib64vorbisenc2.x86_64 1.3.5-2.1.mga6                         
  lib64vorbisfile3.x86_64 1.3.5-2.1.mga6              lib64webkit2-devel.x86_64 2.18.5-1.mga6                       
  lib64webkit2gtk-gir4.0.x86_64 2.18.5-1.mga6         lib64webkit2gtk4.0_37.x86_64 2.18.5-1.mga6                    
  lib64wireshark8.x86_64 2.2.12-1.mga6                lib64wiretap6.x86_64 2.2.12-1.mga6                            
  lib64wscodecs1.x86_64 2.2.12-1.mga6                 lib64wsutil7.x86_64 2.2.12-1.mga6                             
  libvorbis0.i586 1.3.5-2.1.mga6                      libvorbisenc2.i586 1.3.5-2.1.mga6                             
  microcode.noarch 0.20180108-1.mga6.nonfree          nvidia-current-cuda-opencl.x86_64 384.111-1.mga6.nonfree      
  nvidia-current-devel.x86_64 384.111-1.mga6.nonfree  nvidia-current-doc-html.x86_64 384.111-1.mga6.nonfree         
  perf.x86_64 4.14.13-1.mga6                          poppler.x86_64 0.52.0-3.6.mga6                                
  skypeforlinux.x86_64 8.13.0.2-1                     virtualbox-kernel-desktop-latest.x86_64 5.2.2-7.mga6          
  webkit2.x86_64 2.18.5-1.mga6                        webkit2-jsc.x86_64 2.18.5-1.mga6                              
  wireshark.x86_64 2.2.12-1.mga6                      x11-driver-video-nvidia-current.x86_64 384.111-1.mga6.nonfree 



# uname -a
Linux rpg.home 4.14.13-desktop-1.mga6 #1 SMP Wed Jan 10 12:48:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:
Always
Comment 1 Marja Van Waes 2018-01-20 13:01:03 CET 
(In reply to Pavel Roschin from comment #0)

> 
> I did nothing with my system except update. I don't know which component
> caused that bug. Is it possible that microcode update for Meltdown/Spectre
> causes that bug?
> 

Or a kernel update... I think tmb was expecting some problems.

Assignee: bugsquad => tmb
Source RPM: kernel? => kernel?, microcode?
CC: (none) => marja11

Comment 2 Pavel Roschin 2018-01-22 23:32:47 CET 
Switched back to 4.14.10-1. This is definitely kernel bug that led to 300 (!!!) HDD power switches.

I also noticed that gnome-disks under 4.14.13-1 outputs errors concerned with power management in terminal. Probably kernel power management interface was broken?
Comment 3 Pavel Roschin 2018-01-25 22:00:18 CET 
Looks I was wrong. Booting previous kernel didn't solve the problem. I'll try to downgrade microcode.
Comment 4 Aurelien Oudelet 2020-08-16 15:59:32 CEST 
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien
Note You need to log in before you can comment on or make changes to this bug.