Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760332AbYJITTl (ORCPT ); Thu, 9 Oct 2008 15:19:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755275AbYJITTc (ORCPT ); Thu, 9 Oct 2008 15:19:32 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]:24524 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755196AbYJITTb (ORCPT ); Thu, 9 Oct 2008 15:19:31 -0400 Message-ID: Date: Thu, 9 Oct 2008 21:09:26 +0200 From: "Kay Sievers" To: "Arkadiusz Miskiewicz" Subject: Re: loading ipmi_watchdog causes tons of other watchdog modules to be loaded Cc: linux-kernel@vger.kernel.org In-Reply-To: <200810092102.16110.a.miskiewicz@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200810091348.19828.a.miskiewicz@gmail.com> <200810091922.24108.a.miskiewicz@gmail.com> <200810092102.16110.a.miskiewicz@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1546 Lines: 44 On Thu, Oct 9, 2008 at 9:02 PM, Arkadiusz Miskiewicz wrote: > On Thursday 09 October 2008, Kay Sievers wrote: >> On Thu, Oct 9, 2008 at 7:22 PM, Arkadiusz Miskiewicz >> > >> > ... but that ipmi_watchdog is the correct driver that handles >> > /dev/watchdog, so this shouldn't be happening, correct? >> >> While the driver you expect to work is loaded, what does: >> ls -l /dev/watchdog >> print? >> >> If the devno of this node is 10:130, what does: >> find /sys/class /sys/devices/ -name dev | xargs grep 10:130 >> print? > > # ls -l /dev/watchdog > crw------- 1 root root 10, 130 sie 8 17:00 /dev/watchdog > # find /sys/class /sys/devices/ -name dev | xargs grep 10:130 > /sys/class/misc/watchdog/dev:10:130 Ok, so you actually have a driver bound to that device number, and it should not trigger the usual module autoloading mechanism. What does: ls -l /sys/class/misc/watchdog/ and ls -l /sys/class/misc/watchdog/device/ print? Does the /sys/class/misc/watchdog/ directory exist, before you load the module you expect to be the driver behind /dev/watchdog? To clarify, the other modules get loaded, after you loaded but module, the above /sys/class/misc/watchdog/ directory exists, and only if you read from the device, all the other modules get loaded? Kay -- 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/