[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510906280728s1d80c417w64ce6985e9ed8f64@mail.gmail.com>
Date: Sun, 28 Jun 2009 16:28:44 +0200
From: Kay Sievers <kay.sievers@...y.org>
To: Alberto Gonzalez <alberto6674@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-hotplug@...r.kernel.org,
Dave Airlie <airlied@...ux.ie>
Subject: Re: Kernel 2.6.30 and udevd problem
On Sun, Jun 28, 2009 at 16:22, Alberto Gonzalez<alberto6674@...il.com> wrote:
> On Sunday 28 June 2009 14:49:52 Kay Sievers wrote:
>> On Sun, Jun 28, 2009 at 14:37, Alberto Gonzalez<alberto6674@...il.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.
>
> 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@...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