linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom <tomgparchaur@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Question about debugging the source of uevents
Date: Mon, 30 Mar 2009 14:43:13 +0000	[thread overview]
Message-ID: <49D0DA81.1020804@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi,

  I have a spare hard disk I don't touch the most of the time. Due to a
strange reason, a change uevent is triggered some random time of the day
(like 4 or more times) and then, of course, udev apply the rules, being
one of them a rule which runs vol_id which then wakes up my spinned-down
hard disk (debugged with echoing a 1 to /proc/sys/vm/block_dump and
udevadm monitor).

  Well, what i want to know is if it's possible to know why the kernel
is triggering the uevent in the first place. Grepping the documentation
of the kernel I don't see anything about it. I know I can just comment
the watch line in /lib/udev/rules.d/60-persistent-storage.rules but I
wanted to know more.

  I'm using Archlinux which currently uses kernel 2.6.28.8 and udev 140.

Thanks in advance.




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-30 14:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 14:43 Tom [this message]
2009-03-30 14:59 ` Question about debugging the source of uevents Kay Sievers
2009-03-30 15:27 ` Tom
2009-03-30 15:33 ` Kay Sievers
2009-03-30 15:34 ` Tom
2009-03-30 15:35 ` Kay Sievers
2009-03-30 15:54 ` Jim Paris
2009-03-30 16:08 ` Tom

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=49D0DA81.1020804@gmail.com \
    --to=tomgparchaur@gmail.com \
    --cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).