Skip to contentSkip to conversation

Problem with the default IOSCHED

DISCUSSION Marcel Holtmann 3 participants 5 messages Nov 2, 2005 – Nov 6, 2005 Block layer

lore
Share & tools
lore
#0 lore raw

Hi guys,

by accident I selected the anticipatory IO scheduler as default in my kernel config, but only the CFQ was built in. The anticipatory and deadline were only available as modules. This caused an oops at boot. After selecting CFQ as default schedule and a recompile and reboot everything was fine again.

Regards

Marcel

#1 lore raw
Quoted 7 lines · Marcel Holtmann

Hi guys,

by accident I selected the anticipatory IO scheduler as default in my kernel config, but only the CFQ was built in. The anticipatory and deadline were only available as modules. This caused an oops at boot. After selecting CFQ as default schedule and a recompile and reboot everything was fine again.

What kernel version? There are already some patches in 2.6.14-gitN for this kind of problem. Have you tried the -git updates?

Signature · 1 line
~Randy
#2 lore raw

Hi Randy,

Quoted 9 lines
Quoted 5 lines

by accident I selected the anticipatory IO scheduler as default in my kernel config, but only the CFQ was built in. The anticipatory and deadline were only available as modules. This caused an oops at boot. After selecting CFQ as default schedule and a recompile and reboot everything was fine again.

What kernel version? There are already some patches in 2.6.14-gitN for this kind of problem. Have you tried the -git updates?

sorry, I forgot to mention that. It is the latest vanilla you can get.

Regards

Marcel

#3 lore raw
In reply to Marcel Holtmann
Quoted 7 lines · Marcel Holtmann

Hi guys,

by accident I selected the anticipatory IO scheduler as default in my kernel config, but only the CFQ was built in. The anticipatory and deadline were only available as modules. This caused an oops at boot. After selecting CFQ as default schedule and a recompile and reboot everything was fine again.

Hmm yes, that looks like a bug introduced with the io scheduler selection reorg. There's really no support in place for requesting this module out of initrd, I'd rather just make your selection illegal. Does this work for you?

drivers/block/Kconfig.iosched +3 -3
index 5b90d2f..f3b7753 100644
@@ -46,13 +46,13 @@ choice
 	  block devices.
 
 	config DEFAULT_AS
-		bool "Anticipatory" if IOSCHED_AS
+		bool "Anticipatory" if IOSCHED_AS=y
 
 	config DEFAULT_DEADLINE
-		bool "Deadline" if IOSCHED_DEADLINE
+		bool "Deadline" if IOSCHED_DEADLINE=y
 
 	config DEFAULT_CFQ
-		bool "CFQ" if IOSCHED_CFQ
+		bool "CFQ" if IOSCHED_CFQ=y
 
 	config DEFAULT_NOOP
 		bool "No-op"
Signature · 1 line
Jens Axboe
#4 lore raw

Hi Jens,

Quoted 10 lines
Quoted 5 lines

by accident I selected the anticipatory IO scheduler as default in my kernel config, but only the CFQ was built in. The anticipatory and deadline were only available as modules. This caused an oops at boot. After selecting CFQ as default schedule and a recompile and reboot everything was fine again.

Hmm yes, that looks like a bug introduced with the io scheduler selection reorg. There's really no support in place for requesting this module out of initrd, I'd rather just make your selection illegal. Does this work for you?

the patch looks good and please get this out to Linus, because I just made the same mistake on another machine.

Regards

Marcel