linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <udev@dervishd.net>
To: Udev/Hotplug <linux-hotplug-devel@lists.sourceforge.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: udev rule makes the system hang: revisited
Date: Thu, 01 Mar 2007 15:39:18 +0000	[thread overview]
Message-ID: <20070301153918.GA2420@DervishD> (raw)

    Hi all :))

    I'm CC'ing this message to LKML because I don't know if this is some
weird (and known) interaction between modules.

    I'm using vanilla 2.6.19.5.

    I was having a problem using this rule:

ACTION="add", ENV{MODALIAS}="?*", RUN+="/sbin/modprobe $env{MODALIAS}"

    and I finally found the module that was hanging the system:
something with alias "serio:alotofnumbersanddigits".

    I've replaced the rule above by this one:

ACTION="add", ENV{MODALIAS}="?*", ENV{MODALIAS}!="serio*",
    RUN+="/sbin/modprobe $env{MODALIAS}"

    But the question is: why?. And: who is causing the request?. As far
as I know, the only serio things I have are my keyboard and my PS/2
mouse connector (which *doesn't* have a mouse connected), and of course
my keyboard support is not a module (although psaux is).

    Anyone has any idea about what the problem may be? The aliases for
the modules when the event is handled by udev are those:

    serio:ty06pr00id00ex00
    serio:ty01pr00id00ex00

    If I filter out THOSE TWO aliases and only those, the system doesn't
hang. Otherwise, the system appears dead, not even sysrq works (I can't
check ping because right now there aren't other machines in the network,
so probably the machine is not *that* dead, and only the keyboard has
dead :??).

    Thanks a lot in advance. If anyone needs more information or tests,
just ask.

    Kay, I followed your advice, booted without udev and make some tests
until I found the culprit. Hard, but fruitful ;)) Thanks :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2007-03-01 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070301153918.GA2420@DervishD \
    --to=udev@dervishd.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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 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).