From: Aras Vaichas <arasv@magtech.com.au>
To: linux-hotplug@vger.kernel.org
Subject: udev-126 error: delete_path: rmdir(//dev) failed: Device or resource
Date: Thu, 28 Aug 2008 05:49:00 +0000 [thread overview]
Message-ID: <48B63C4C.9000503@magtech.com.au> (raw)
Hi, I just upgraded from 124 to 126 and I now get this error when I
disconnect my USB Bluetooth device.
udev-124: No udevd messages
Jan 1 01:06:47 user.info kernel: usb 1-1: USB disconnect, address 9
Jan 1 01:06:47 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep81
Jan 1 01:06:47 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep02
Jan 1 01:06:47 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep82
Jan 1 01:06:47 user.debug kernel: PM: Removing info for bluetooth:hci0
Jan 1 01:06:47 daemon.info hcid[504]: HCI dev 0 down
Jan 1 01:06:47 daemon.info hcid[504]: Stoping security manager 0
Jan 1 01:06:48 daemon.info hcid[504]: HCI dev 0 unregistered
Jan 1 01:06:48 user.debug kernel: PM: Removing info for usb:1-1:1.0
Jan 1 01:06:48 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep03
Jan 1 01:06:48 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep83
Jan 1 01:06:48 user.debug kernel: PM: Removing info for usb:1-1:1.1
Jan 1 01:06:48 user.debug kernel: PM: Removing info for usb:1-1:1.2
Jan 1 01:06:48 user.debug kernel: PM: Removing info for No
Bus:usbdev1.9_ep00
Jan 1 01:06:48 user.debug kernel: PM: Removing info for usb:1-1
udev-126: udevd errors
Jan 1 01:04:04 user.info kernel: usb 1-1: USB disconnect, address 8
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep81
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep02
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep82
Jan 1 01:04:04 user.debug kernel: PM: Removing info for bluetooth:hci0
Jan 1 01:04:04 daemon.info hcid[504]: HCI dev 0 down
Jan 1 01:04:04 daemon.info hcid[504]: Stoping security manager 0
Jan 1 01:04:04 daemon.err udevd-event[808]: delete_path: rmdir(//dev)
failed: Device or resource busy
Jan 1 01:04:04 daemon.err udevd-event[810]: delete_path: rmdir(//dev)
failed: Device or resource busy
Jan 1 01:04:04 daemon.err udevd-event[809]: delete_path: rmdir(//dev)
failed: Device or resource busy
Jan 1 01:04:04 daemon.info hcid[504]: HCI dev 0 unregistered
Jan 1 01:04:04 user.debug kernel: PM: Removing info for usb:1-1:1.0
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep03
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep83
Jan 1 01:04:04 user.debug kernel: PM: Removing info for usb:1-1:1.1
Jan 1 01:04:04 user.debug kernel: PM: Removing info for usb:1-1:1.2
Jan 1 01:04:04 user.debug kernel: PM: Removing info for No
Bus:usbdev1.8_ep00
Jan 1 01:04:04 user.debug kernel: PM: Removing info for usb:1-1
Jan 1 01:04:04 daemon.err udevd-event[811]: delete_path: rmdir(//dev)
failed: Device or resource busy
Jan 1 01:04:04 daemon.err udevd-event[812]: delete_path: rmdir(//dev)
failed: Device or resource busy
Jan 1 01:04:04 daemon.err udevd-event[814]: delete_path: rmdir(//dev)
failed: Device or resource busy
I can post the output of "udevd --debug" if it will help.
My configuration of udevd is:
./configure --prefix=/
Aras
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next reply other threads:[~2008-08-28 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 5:49 Aras Vaichas [this message]
2008-08-28 7:30 ` udev-126 error: delete_path: rmdir(//dev) failed: Device or resource busy Kay Sievers
2008-08-28 9:20 ` udev-126 error: delete_path: rmdir(//dev) failed: Device or arasv
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=48B63C4C.9000503@magtech.com.au \
--to=arasv@magtech.com.au \
--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 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.