search for: uevent

...erial support registered for DeLorme Earthmate USB usbserial: USB Serial support registered for HID->COM RS232 Adapter usbserial: USB Serial support registered for Nokia CA-42 V2 Adapter usbcore: registered new interface driver cypress cypress_m8: Cypress USB to Serial Driver v1.09 udevmonitor: UEVENT[1229960645.326958] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3 (usb) UEVENT[1229960645.332895] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3/2-3:1.0 (usb) UDEV [1229960645.341691] add /devices/pci0000:00/0000:00:0b.0/usb2/2-3 (usb) UEVENT[1229960645.344109] add /class/usb (class) UEVENT[122...

...nd and udevinfo > -V reports greater than 059 then you are using udev, so use > udevmonitor to watch the udev events going past. # cat /proc/sys/kernel/hotplug /sbin/udevsend # udevinfo -V udevinfo, version 068 Here is the output from udevmonitor during the xm create when the vif failed: UEVENT[1133877953] add@/devices/xen-backend/vbd-4-2049 UEVENT[1133877953] add@/devices/xen-backend/vif-4-0 UEVENT[1133877953] add@/class/net/vif4.0 UEVENT[1133877953] online@/devices/xen-backend/vif-4-0 UDEV [1133877956] add@/devices/xen-backend/vbd-4-2049 Here is the output when the vbd failed: UEVENT...

On Fri, 11 Oct 2019 16:15:52 +0800 Jason Wang <jasowang at redhat.com> wrote: > This patch adds bus uevent support for mdev bus in order to allow > cooperation with userspace. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > drivers/vfio/mdev/mdev_driver.c | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/drivers/vfio/mdev/mdev_driver.c b/dri...

Provide private field for event handlers exclusive use. Convert nouveau_fence_wait_uevent() and nouveau_fence_wait_uevent_handler(); drop struct nouveau_fence_uevent. Signed-off-by: Peter Hurley <peter at hurleysoftware.com> --- drivers/gpu/drm/nouveau/core/include/core/event.h | 1 + drivers/gpu/drm/nouveau/nouveau_fence.c | 20 +++++++------------- 2 files changed,...

...s and vifs are connecting perfectly fine, just these tap:aio devices that won''t work. I''ve also verified that blktap and xenblk are loaded as modules. I used udevmonitor to track what happens when I start domUs with tap:aio vs. file (loop) disks. Here''s file method: UEVENT[1209507940.668013] add@/block/dm-30 UEVENT[1209507940.668040] offline@/block/dm-30 UEVENT[1209507940.668049] online@/block/dm-30 UEVENT[1209507940.668059] add@/block/dm-31 UEVENT[1209507940.668067] offline@/block/dm-31 UEVENT[1209507940.668074] online@/block/dm-31 UDEV [1209507940.895265] add@/blo...

...nt: Tuesday, December 06, 2005 9:16 AM > To: Dave Thompson (davetho) > Cc: Xen Mailing List > Subject: Re: [Xen-devel] Hotplug scripts not working... > xen/ia64 domU stoppedworking > > On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson > (davetho) wrote: > > > UEVENT[1133877953] add@/devices/xen-backend/vbd-4-2049 > > UEVENT[1133877953] add@/devices/xen-backend/vif-4-0 > UEVENT[1133877953] > > add@/class/net/vif4.0 UEVENT[1133877953] > > online@/devices/xen-backend/vif-4-0 > > UDEV [1133877956] add@/devices/xen-backend/vbd-4-2049...

...configured properly. I think it comes down to the domU not being able to "talk" with udevd. I know udevd is still running and is responsive (if I run udevmonitor and mount/umount a disk I see normal output). When I attempt to start my domU I normally see udevmonitor output like this: UEVENT[1240149226.992189] add /devices/xen-backend/vbd-9-2048 (xen-backend) UDEV [1240149226.993163] add /devices/xen-backend/vbd-9-2048 (xen-backend) UEVENT[1240149227.012202] add /devices/xen-backend/vbd-9-2064 (xen-backend) UDEV [1240149227.013301] add /devices/xen-backend/vbd-9-2...

...> drm_kms_helper_hotplug_event(dev); > > I'm curious if you think there might be an advantage to doing this per- > connector even with multiple connectors? Seems like we could do that if we > stored changed connectors as a bitmask. I believe firing off multiple per-connector uevents would be worse than a single per-device uevent because user-space would see intermediate states instead of an atomic change. Let's say I have 3 connectors connected, and different settings set in my compositor when 1, 2 or 3 screens are connected. Let's say an unplug disconnects 2 monitor...

Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd...

Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd...

On Tue, 06/28 04:45, Christoph Hellwig wrote: > On Tue, Jun 28, 2016 at 10:39:15AM +0800, Fam Zheng wrote: > > Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that > > point we haven't created the serial attribute file, therefore depending > > on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get > > created. > > > > This race condition can be easily reproduced by hot plugg...

On Tue, 06/28 04:45, Christoph Hellwig wrote: > On Tue, Jun 28, 2016 at 10:39:15AM +0800, Fam Zheng wrote: > > Userspace listens to the KOBJ_ADD uevent generated in add_disk. At that > > point we haven't created the serial attribute file, therefore depending > > on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get > > created. > > > > This race condition can be easily reproduced by hot plugg...

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Add information so rproc-serial can be easily recogniced from user space. Add the following information to uevent: DRIVER=virtio_console|virtio_rproc_serial INTERFACE=grand-parent/parent/name Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi, I need some way to identify the major/minor number for the rproc-serial device, given the udev event. Review comments are welcomed. Than...

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Add information so rproc-serial can be easily recogniced from user space. Add the following information to uevent: DRIVER=virtio_console|virtio_rproc_serial INTERFACE=grand-parent/parent/name Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi, I need some way to identify the major/minor number for the rproc-serial device, given the udev event. Review comments are welcomed. Than...

...have been initialized properly, as userspace will instantly start to look > > for them when this call happens. > > Unfortunately it seems impossible to fix this generally without touching the > offending callers. The approach I'm proposing here is adding a flag to > suppress uevent in add_disk(), which is patch 1, then in later patches, convert > any caller to only trigger the uevent when attributes are added. We (or rather Dan) is touching most add_disk callers anyway for the driverfs_dev removal. Let's just pass the array of attributes to a disk_add variant and sol...

...perly, as userspace will instantly start to look > > > for them when this call happens. > > > > Unfortunately it seems impossible to fix this generally without touching the > > offending callers. The approach I'm proposing here is adding a flag to > > suppress uevent in add_disk(), which is patch 1, then in later patches, convert > > any caller to only trigger the uevent when attributes are added. > > We (or rather Dan) is touching most add_disk callers anyway for the > driverfs_dev removal. Let's just pass the array of attributes to > a...

This patch adds bus uevent support for mdev bus in order to allow cooperation with userspace. Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vfio/mdev/mdev_driver.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/vfio/mdev/mdev_driver.c b/drivers/vfio/mdev/mdev_driver.c index b7c40...

...perly, as userspace will instantly start to look > > > for them when this call happens. > > > > Unfortunately it seems impossible to fix this generally without touching the > > offending callers. The approach I'm proposing here is adding a flag to > > suppress uevent in add_disk(), which is patch 1, then in later patches, convert > > any caller to only trigger the uevent when attributes are added. > > We (or rather Dan) is touching most add_disk callers anyway for the > driverfs_dev removal. Let's just pass the array of attributes to > a...

...errors:0 dropped:0 overruns:0 frame:0 TX packets:1824 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1955948 (1.8 MiB) TX bytes:345201 (337.1 KiB) ====== udev monitor output ==== udevmonitor prints the received event from the kernel [UEVENT] and the event which udev sends out after rule processing [UDEV] UEVENT[1182238470.444318] add@/devices/xen-backend/vfb-8-0 UDEV [1182238470.451658] add@/devices/xen-backend/vfb-8-0 UEVENT[1182238470.475845] add@/devices/xen-backend/vbd-8-768 UDEV [1182238470.475845] add@/devices/xen-backend/vbd-...

On Wed, Jun 29, 2016 at 6:59 PM, Fam Zheng <famz at redhat.com> wrote: > It is documented that KOBJ_ADD should be generated after the object's > attributes and children are ready. We can achieve this with the new > disk_gen_uevents interface. > > Signed-off-by: Fam Zheng <famz at redhat.com> > --- > arch/powerpc/sysdev/axonram.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/powerpc/sysdev/axonram.c b/arch/powerpc/sysdev/axonram.c > index 4efd69b..27e7175 100644...