[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070803110614.9c06fe45.akpm@linux-foundation.org>
Date: Fri, 3 Aug 2007 11:06:14 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Rafał Bilski <rafalbilski@...eria.pl>
Cc: linux-mtd@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Problem with udev and block2mtd
On Wed, 01 Aug 2007 21:05:59 +0200
Rafał Bilski <rafalbilski@...eria.pl> wrote:
> Hi!
>
> I have changed static /dev to udev on my machine. It has
> a lot of RAM (94MB) so I was expecting that udev will not make
> things worse. Unfortunately udev isn't noticing that new mtd
> device was born.
<tap, tap> Is this thing turned on?
> I was suspecting that this is my fault, but
> udev's /dev is populated and:
> UEVENT[1185991604.930847] add@...dule/mtdcore
> UEVENT[1185991604.969089] add@...dule/mtdpart
> UEVENT[1185991605.005954] add@...dule/block2mtd
> UEVENT[1185991647.726551] add@...dule/mtdsuper
> UEVENT[1185991647.783396] add@...dule/jffs2
> UEVENT[1185991647.801242] add@...ab/jffs2_i
> UDEV [1185991647.815670] add@...ab/jffs2_i
> UEVENT[1185991647.827608] add@...ab/:0000072
> UDEV [1185991647.842338] add@...ab/:0000072
> I don't see nothing about new device.
>
> Is this situation known? Or this is 2.6.23-rc1-git3 regression?
> Or is my udev misconfigured?
>
Did 2.6.22 work OK with the same setup? If so, yes, it's a regression!
-
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