All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: xen_blk timeout connecting to device
Date: Wed, 5 Oct 2005 19:50:02 +0100	[thread overview]
Message-ID: <623652d50510051150x13a260d6q@mail.gmail.com> (raw)
In-Reply-To: <9e246b4d0510050618m2af7f13cu39e1f4ddbd1a3f2a@mail.gmail.com>

On 05/10/05, Tim Durack <tdurack@gmail.com> wrote:
> I have hotplug and udev installed, but am seeing the same problem.

"cat /proc/sys/kernel/hotplug". /sbin/hotplug seems to work for
everyone (?). /sbin/udevsend needs udev rules. The backward compatible
udev rules should work, but don't.

Some notes on debugging this stuff, in case anyone else has problems

in /etc/udev/udev.conf add:

udev_log="info"

In /etc/hotplug.d/default/default.hotplug:

DEBUG=yes export DEBUG

In /etc/hotplug/xen-backend.agent:

add "set -x" as 2nd line.

You should now get debug info in either /var/log/messages or
/var/log/udev (depends on syslog setup).

I gave up with the hotplug stuff, and used the udev rules I posted a
few days ago. If you go that route comment out this line from
/etc/udev/rules.d/50-udev.rules:

ENV{UDEVD_EVENT}=="1", RUN+="/sbin/udev_run_hotplugd"

That will disable the backward compatible hotplug stuff which seems to
be broken with respect to xen. You will now be able to see the udev
events and rules in your log file, and exactly what is going on in the
scripts you execute (echo to stdout will be syslogged by udev). After
that it's just a matter of tying together the unhandled events with
actions.

  reply	other threads:[~2005-10-05 18:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 13:18 xen_blk timeout connecting to device Tim Durack
2005-10-05 18:50 ` Chris Bainbridge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05  6:38 Himanshu Raj
2005-10-05  9:06 ` Ewan Mellor
2005-10-05  9:34   ` Jacob Gorm Hansen
2005-10-05  9:37     ` Chris Bainbridge
2005-10-05  9:57     ` Ewan Mellor
2005-10-05 13:24       ` Himanshu Raj
2005-10-05 13:55         ` Ewan Mellor
2005-10-06 17:15           ` Ryan Grimm
2005-10-06 18:20             ` Ewan Mellor
2005-10-05 15:07 ` Jeremy Katz
2005-10-05 16:55   ` Himanshu Raj
2005-10-05 17:21     ` Chris Bainbridge
2005-09-17 20:38 xen_blk: Timeout " Bonnell, David

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=623652d50510051150x13a260d6q@mail.gmail.com \
    --to=chris.bainbridge@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.