From: Alberto Gonzalez <alberto6674@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alberto Gonzalez <alberto6674@gmail.com>,
linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Kernel 2.6.30 and udevd problem
Date: Sun, 28 Jun 2009 14:22:09 +0000 [thread overview]
Message-ID: <200906281622.10072.info@gnebu.es> (raw)
In-Reply-To: <ac3eb2510906280549w75b4da79i1f38888a9be56c4e@mail.gmail.com>
On Sunday 28 June 2009 14:49:52 Kay Sievers wrote:
> 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.
When I kill udevd, the KERNEL messages continue.
>
> Kay
WARNING: multiple messages have this Message-ID (diff)
From: Alberto Gonzalez <alberto6674@gmail.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alberto Gonzalez <alberto6674@gmail.com>,
linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Kernel 2.6.30 and udevd problem
Date: Sun, 28 Jun 2009 16:22:09 +0200 [thread overview]
Message-ID: <200906281622.10072.info@gnebu.es> (raw)
In-Reply-To: <ac3eb2510906280549w75b4da79i1f38888a9be56c4e@mail.gmail.com>
On Sunday 28 June 2009 14:49:52 Kay Sievers wrote:
> 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.
When I kill udevd, the KERNEL messages continue.
>
> Kay
next prev parent reply other threads:[~2009-06-28 14:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 6:21 Kernel 2.6.30 and udevd problem Alberto Gonzalez
2009-06-28 6:21 ` Alberto Gonzalez
2009-06-28 10:37 ` Kay Sievers
2009-06-28 10:37 ` Kay Sievers
2009-06-28 12:37 ` Alberto Gonzalez
2009-06-28 12:37 ` Alberto Gonzalez
2009-06-28 12:49 ` Kay Sievers
2009-06-28 12:49 ` Kay Sievers
2009-06-28 14:22 ` Alberto Gonzalez [this message]
2009-06-28 14:22 ` Alberto Gonzalez
2009-06-28 14:28 ` Kay Sievers
2009-06-28 14:28 ` Kay Sievers
2009-06-30 3:40 ` Alberto Gonzalez
2009-06-30 3:40 ` Alberto Gonzalez
2009-06-30 3:46 ` Dave Airlie
2009-06-30 3:46 ` Dave Airlie
2009-06-30 16:08 ` Jesse Barnes
2009-06-30 16:08 ` Jesse Barnes
2009-07-01 7:09 ` Alberto Gonzalez
2009-07-01 7:09 ` Alberto Gonzalez
2009-07-01 17:22 ` Jesse Barnes
2009-07-01 17:22 ` Jesse Barnes
2009-07-02 6:18 ` Alberto Gonzalez
2009-07-02 6:18 ` Alberto Gonzalez
2009-07-02 16:35 ` Jesse Barnes
2009-07-02 16:35 ` Jesse Barnes
2009-07-02 19:37 ` Alberto Gonzalez
2009-07-02 19:37 ` Alberto Gonzalez
2009-07-02 22:00 ` Michal Soltys
2009-07-02 22:00 ` Michal Soltys
2009-07-04 22:10 ` Alberto Gonzalez
2009-07-04 22:10 ` Alberto Gonzalez
2009-07-20 18:10 ` Jesse Barnes
2009-07-20 18:10 ` Jesse Barnes
2009-07-20 21:06 ` Alberto Gonzalez
2009-07-20 21:06 ` Alberto Gonzalez
2009-07-20 22:48 ` Alberto Gonzalez
2009-07-22 13:25 ` Alberto Gonzalez
2009-07-22 16:08 ` Jesse Barnes
2009-07-22 16:08 ` Jesse Barnes
2009-07-22 16:51 ` Alberto Gonzalez
2009-07-22 17:12 ` Jesse Barnes
2009-07-22 17:12 ` Jesse Barnes
2009-07-22 18:43 ` Alberto Gonzalez
2009-07-22 18:43 ` Alberto Gonzalez
2009-07-22 19:17 ` Jesse Barnes
2009-07-22 19:17 ` Jesse Barnes
2009-07-22 19:44 ` Jesse Barnes
2009-07-22 19:44 ` Jesse Barnes
2009-07-22 20:00 ` Alberto Gonzalez
2009-07-22 20:00 ` Alberto Gonzalez
2009-07-23 0:06 ` Alberto Gonzalez
2009-07-23 0:06 ` Alberto Gonzalez
2009-08-06 13:53 ` Alberto Gonzalez
2009-08-06 13:53 ` Alberto Gonzalez
2009-08-06 21:30 ` Jesse Barnes
2009-08-06 21:30 ` Jesse Barnes
2009-08-06 22:17 ` Alberto Gonzalez
2009-08-06 22:17 ` Alberto Gonzalez
-- strict thread matches above, loose matches on Subject: below --
2009-06-28 5:53 Alberto Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906281622.10072.info@gnebu.es \
--to=alberto6674@gmail.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.