From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Sun, 28 Jun 2009 12:49:52 +0000
Subject: Re: Kernel 2.6.30 and udevd problem
Message-Id: <ac3eb2510906280549w75b4da79i1f38888a9be56c4e@mail.gmail.com>
List-Id: <linux-hotplug.vger.kernel.org>
References: <200906280821.58631.info@gnebu.es> <ac3eb2510906280337s57f5a48kc487a85d259f83dd@mail.gmail.com> 
	<200906281437.00329.info@gnebu.es>
In-Reply-To: <200906281437.00329.info@gnebu.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: Alberto Gonzalez <alberto6674@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org

On Sun, Jun 28, 2009 at 14:37, Alberto Gonzalez<alberto6674@gmail.com> wrote:

> This is what I got wen the problem finally came back (it happens randomly, this
> time I triggered it by running glxgears, but it can happen for other reasons
> and none of them triggers it automatically):
>
> KERNEL[1246192153.094553] change   /devices/pci0000:00/0000:00:02.0/drm/card0
> (drm)

> UDEV  [1246192153.178593] change   /devices/pci0000:00/0000:00:02.0/drm/card0
> (drm)
>
> So just an endless loop of the same message again and again.

If you see this loop and kill the udev daemon, the UDEV events will
stop. But do the KERNEL events continue, or do all events stop? This
should tell us if some udev rules trigger something here, or if it is
a loop in the kernel.

Kay