Bug 779146

Summary: YaST2 Kernel Settings doesn't remember Global I/O Scheduler
Product: [openSUSE] openSUSE 12.2 Reporter: Samuel Jones <samuel>
Component: YaST2Assignee: Josef Reidinger <jreidinger>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: forgotten_P9eo8KG-dg, lslezak, samuel
Version: Final   
Target Milestone: RC 2   
Hardware: 64bit   
OS: openSUSE 12.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2log
y2log with Y2DEBUG
/etc/sysconfig/bootloader file
/var/log/pbl.log
/var/log/pbl.log
This should be the log from upgrade

Description Samuel Jones 2012-09-06 20:11:40 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0

YaST2 Kernel Settings doesn't remember Global I/O Scheduler, aways reverts back to 'Not Configured' after applying.

cat /sys/block/sda/queue/scheduler also returns [cfq] after many attempts at setting to deadline

Reproducible: Always

Steps to Reproduce:
1. Change Global I/O Scheduler in YaST2 Kernel Settings to something other 'Not Configured'
2. OK to apply
3. cat /sys/block/*/queue/scheduler or reopen Kernel Settings to see that the setting hasn't been applied.
Actual Results:  
I/O Scheduler remains unchanged from the default, CFQ

Expected Results:  
It should change to what is selected.
Comment 1 Forgotten User P9eo8KG-dg 2013-02-07 22:41:28 UTC
Still the same in 12.3 RC1.
Maybe this one can get fixed?
Nice to configure SSD's with other scheduler.
Comment 2 Ladislav Slezák 2015-01-14 14:46:14 UTC
I have fixed the scheduler activation in https://github.com/yast/yast-tune/pull/12.

The scheduler option should be written to the bootloader options at https://github.com/yast/yast-tune/blob/master/src/modules/SystemSettings.rb#L131.

But it looks like it does not work correctly anymore...

Josef, please look at it, thanks!
Comment 3 Ladislav Slezák 2015-01-14 14:52:24 UTC
Created attachment 619552 [details]
y2log

y2log from openSUSE-13.2
Comment 4 Ladislav Slezák 2015-01-14 14:55:39 UTC
Created attachment 619553 [details]
y2log with Y2DEBUG
Comment 5 Josef Reidinger 2015-01-15 08:16:17 UTC
Lada - do you run it in running system or in installation? For me it looks like running system. If so, can you please attach your /etc/sysconfig/bootloader? It looks like bootloader think you manage bootloader yourself without yast ( bootloader set to NONE ).
Comment 6 Josef Reidinger 2015-01-15 08:20:51 UTC
and if you can please also include /var/log/pbl.log which contain data from perl bootloader
Comment 7 Ladislav Slezák 2015-01-21 14:47:13 UTC
Created attachment 620345 [details]
/etc/sysconfig/bootloader file

Yes, it contains LOADER_TYPE="none" value.

BTW I did an upgrade from 13.1 (via DVD IIRC...).
Comment 8 Ladislav Slezák 2015-01-21 14:49:55 UTC
Created attachment 620347 [details]
/var/log/pbl.log
Comment 9 Ladislav Slezák 2015-01-21 14:52:10 UTC
Created attachment 620349 [details]
/var/log/pbl.log

(Reattaching again, sorry, forgot to compress the log...)
Comment 10 Josef Reidinger 2015-01-22 06:56:12 UTC
Hmm, that is very bad to have this loader type. I will check what is going there, as it mean, that also when you install new kernel you cannot use it.
Comment 11 Josef Reidinger 2015-01-27 16:25:22 UTC
Lada - pbl.log shows that something change settings to none. I worry, that upgrade in 13.2 using DVD can be broken, do you still have yast logs from this upgrade? As initial bootloader was grub and I have similar report.
Comment 12 Ladislav Slezák 2015-01-30 16:31:08 UTC
Created attachment 621483 [details]
This should be the log from upgrade
Comment 13 Josef Reidinger 2015-01-30 16:48:21 UTC
Ah, it shows my suspicious that it is caused by missing proposal, so it read that bootloader is grub and then decide that it is not supported one so switch to none bootloader.

So if you change bootloader type to grub2 it should work for kernel settings.
Bug is fixed for next opensuse release and in TW.