From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 28 Jun 2009 14:28:44 +0000 Subject: Re: Kernel 2.6.30 and udevd problem Message-Id: List-Id: References: <200906280821.58631.info@gnebu.es> <200906281437.00329.info@gnebu.es> <200906281622.10072.info@gnebu.es> In-Reply-To: <200906281622.10072.info@gnebu.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Alberto Gonzalez Cc: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org, Dave Airlie On Sun, Jun 28, 2009 at 16:22, Alberto Gonzalez wrot= e: > On Sunday 28 June 2009 14:49:52 Kay Sievers wrote: >> On Sun, Jun 28, 2009 at 14:37, Alberto Gonzalez > 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 hap= pen >> > 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 =C2=A0[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. > > When I kill udevd, the KERNEL messages continue. If there isn't something else running which acts on uevents that trigger drm events, which I wouldn't expect, it seems like a drm kernel problem. Kay