no uevent after ejecting CD-ROM

Bug #1458470 reported by Removed by request
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I'm using Ubuntu 15.10 dev with udev 219-10ubuntu1 and I'm noticing that udev rules are only executed while the system is booting. For example the file "/lib/udev/rules.d/10-test.rules" with the content "KERNEL=="sr0", RUN+="/usr/bin/touch /tmp/test.txt"" does create the file /tmp/test.txt on booting but if I'm then deleting the file and ejecting /dev/sr0 the file isn't created anymore.

Revision history for this message
Martin Pitt (pitti) wrote :

Can you please run

  udevadm monitor -e --udev

then eject sr0 (in a different terminal), then copy&paste the whole output of udevadm monitor here?

Changed in udev (Ubuntu):
status: New → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

Physically ejecting /dev/sr0 results in this output:

root@ubuntu:~# udevadm monitor -e --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

Changed in udev (Ubuntu):
status: Incomplete → New
Revision history for this message
Martin Pitt (pitti) wrote :

Right, so this is (at most) the kernel's fault. I'm not sure whether ejecting a CD is supposed to trigger an uevent, but maybe not in all cases?

affects: udev (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
summary: - udev rules aren't executed anymore after booting
+ no uevent after ejecting CD-ROM
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1458470

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

In the past physically ejecting /dev/sr0 has worked for me. A recent apport-collect (while this report was already made) against "linux (Ubuntu)" was done here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463627

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc8-unstable/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

>Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

I'm using user-defined udev rules which I have noticed stopped working shortly before I have created this ticket. Based on these rules I have created the testcase in the startpost so yes, this was working not much time before I have created this ticket.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.