Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755535AbZF1O3R (ORCPT ); Sun, 28 Jun 2009 10:29:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752916AbZF1O3C (ORCPT ); Sun, 28 Jun 2009 10:29:02 -0400 Received: from mail-bw0-f213.google.com ([209.85.218.213]:49316 "EHLO mail-bw0-f213.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752741AbZF1O3B convert rfc822-to-8bit (ORCPT ); Sun, 28 Jun 2009 10:29:01 -0400 MIME-Version: 1.0 In-Reply-To: <200906281622.10072.info@gnebu.es> References: <200906280821.58631.info@gnebu.es> <200906281437.00329.info@gnebu.es> <200906281622.10072.info@gnebu.es> From: Kay Sievers Date: Sun, 28 Jun 2009 16:28:44 +0200 Message-ID: Subject: Re: Kernel 2.6.30 and udevd problem To: Alberto Gonzalez Cc: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org, Dave Airlie Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1391 Lines: 33 On Sun, Jun 28, 2009 at 16:22, Alberto Gonzalez wrote: > 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 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. > > 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 -- 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/