[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510810091158x3b677959j480c554b86c1ee26@mail.gmail.com>
Date: Thu, 9 Oct 2008 20:58:44 +0200
From: "Kay Sievers" <kay.sievers@...y.org>
To: "Arkadiusz Miskiewicz" <a.miskiewicz@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: loading ipmi_watchdog causes tons of other watchdog modules to be loaded
On Thu, Oct 9, 2008 at 7:22 PM, Arkadiusz Miskiewicz
<a.miskiewicz@...il.com> wrote:
> On Thursday 09 October 2008, Kay Sievers wrote:
>> On Thu, Oct 9, 2008 at 1:48 PM, Arkadiusz Miskiewicz
>>
>> <a.miskiewicz@...il.com> wrote:
>> > No udev on the system. kernel 2.6.25.18-1.
>> >
>> > After loading ipmi_watchdog and doing "cat /dev/watchdog" tons of other,
>> > useles, watchdog modules is loaded. Any idea what introduced such weird
>> > behaviour?
>>
>> I guess the /proc/sys/kernel/modprobe, which lets the kernel fork a
>> modprobe process when you touch a "dangling" device node, which does
>> not have corresponding driver.
>
> ... 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?
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists