Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751476AbVKBA2B (ORCPT ); Tue, 1 Nov 2005 19:28:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751477AbVKBA2B (ORCPT ); Tue, 1 Nov 2005 19:28:01 -0500 Received: from coyote.holtmann.net ([217.160.111.169]:50828 "EHLO mail.holtmann.net") by vger.kernel.org with ESMTP id S1751476AbVKBA2B (ORCPT ); Tue, 1 Nov 2005 19:28:01 -0500 Subject: Problem with the default IOSCHED From: Marcel Holtmann To: linux-kernel@vger.kernel.org Content-Type: text/plain Date: Wed, 02 Nov 2005 01:28:02 +0100 Message-Id: <1130891282.5048.50.camel@blade> Mime-Version: 1.0 X-Mailer: Evolution 2.5.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 574 Lines: 18 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/