From: Marcel Holtmann <marcel@holtmann.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with the default IOSCHED
Date: Sun, 06 Nov 2005 19:57:38 +0100 [thread overview]
Message-ID: <1131303458.5824.1.camel@blade> (raw)
In-Reply-To: <20051102115542.GN26049@suse.de>
Hi Jens,
> > 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
prev parent reply other threads:[~2005-11-06 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 0:28 Problem with the default IOSCHED Marcel Holtmann
2005-11-02 0:32 ` Randy.Dunlap
2005-11-02 0:50 ` Marcel Holtmann
2005-11-02 11:55 ` Jens Axboe
2005-11-06 18:57 ` Marcel Holtmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1131303458.5824.1.camel@blade \
--to=marcel@holtmann.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.