*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
Hi Kenneth,
Thank you for taking the time to report the issue. In the future, please
feel free to file a case through the support portal if you find a issue
that needs to be fixed urgently in ESM.
In any case, I did some investigating, and found the below commit was
backported to 4.15.0-155-generic:
commit 7dd753ca59d6c8cc09aa1ed24f7657524803c7f3
Author: ManYi Li <[email protected]>
Date: Fri Jun 11 17:44:02 2021 +0800
Subject: scsi: sr: Return appropriate error code when disk is ejected
Link:
https://github.com/torvalds/linux/commit/7dd753ca59d6c8cc09aa1ed24f7657524803c7f3
It landed in a few other kernels too, the full list is:
Bionic 4.15.0-155-generic
Focal 5.4.0-82-generic
Hirsute 5.11.0-32-generic
Impish 5.13.0-1-generic
I believe this is the root cause, and it lines up with your
4.15.0-154-generic (good) and 4.15.0-156-generic (bad) findings.
This has been fixed upstream, by the below commit:
commit 5c04243a56a7977185b00400e59ca7e108004faf
Author: Li Manyi <[email protected]>
Date: Mon Jul 26 19:49:13 2021 +0800
Subject: scsi: sr: Return correct event when media event code is 3
Link:
https://github.com/torvalds/linux/commit/5c04243a56a7977185b00400e59ca7e108004faf
This commit has already been applied to all the Ubuntu kernels, which
are currently sitting in -proposed:
Bionic 4.15.0-159-generic
Focal 5.4.0-87-generic
Hirsute 5.11.0-37-generic
Impish 5.13.0-16-generic
Looking at https://kernel.ubuntu.com/, the current SRU cycle is
scheduled to come to an end early next week, so we should expect a
release to -updates on ther 27th of September, give or take a few days
if any CVEs turn up.
At the moment, it is not very straightforward to access the -proposed
repo under ESM, but if you can also reproduce the issue under Bionic,
feel free to enable -proposed and try 4.15.0-159-generic to confirm it
fixes the issue.
https://wiki.ubuntu.com/Testing/EnableProposed
I set bug 1942299 to track this issue, so I am going to mark this one as
a duplicate of it.
If you have any questions, feel free to write back, or open a case on
the support portal.
Thanks,
Matthew
** This bug has been marked a duplicate of bug 1942299
CD/DVD tray ejects on boot or waking from suspend
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944642
Title:
Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM
media
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
In Progress
Bug description:
Hello! I'm a programmer employed by VMWare. We're using Ubuntu Xenial,
have an ESM contract, and have run into what we believe to be a nasty
interaction between a kernel change and the `cdrom_id --eject-media`
command. This problem started happening after upgrading from
4.15.0-154 to 4.15.0-156.
I am reporting a kernel "device change" event storm that appears to
not stop on its own and is triggered by both ejecting media from a
DVD-ROM drive AND having a udev rule which contains the following
line:
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode",
GOTO="cdrom_end"
If you eliminate this line from your udev rule file, the storm will
never happen. This strongly suggests that the cdrom_id program is a
key component in the problem. As mentioned before, this problem
happened after we upgraded from kernel 4.15.0-154 to kernel 4.15.0-156
as part of a regular update to the Canonical-included packages that we
use as a base for our system. Based on the evidence, we believe that
this is a regression from kernel version 4.15.0-154.
This storm prevents new media inserted into the drive from being
recognized and mounted. In order for any new media inserted into the
drive to be recognized, one must terminate the storm by do one of two
things:
Either:
Move `/lib/udev/cdrom_id` to some other location, wait for a moment for the
storm to stop, then move it back. Media inserted into the drive will be
immediately recognized.
or:
Insert the media several times until it stays inserted. In testing "several"
has been "three or four", but I have no idea of the upper or lower bounds of
this number. Each time you insert the media, it will be automatically removed
from the VM. On the insertion immediately _before_ the one that actually works,
the event storm will stop, and the media will be -again- automatically removed.
On the next insertion, the media will stay in, and you will be able to actually
mount the media inside the VM.
When you look at the output of `udevadm monitor -u -k` during the
event storm the following event is generated at a rate roughly ten
times per second:
KERNEL[3198.914510] change
/devices/pci0000:00/0000:00:07.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
(block)
UDEV [3199.021261] change
/devices/pci0000:00/0000:00:07.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
(block)
Relevant system information:
OS: Ubuntu Xenial ESM
IAAS: vSphere 7.0
uname -a output: Linux test-machine 4.15.0-156-generic #163~16.04.1-Ubuntu
SMP Mon Aug 23 13:38:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Likely Reproduction Steps:
1) Boot a machine (virtual or otherwise) with an attached DVD-ROM drive with
the 4.15.0-156-generic kernel.
2) Insert media into the drive.
3) Eject the media.
4) Notice that `udevadm monitor -u -k` is showing you an endless stream of
"device change" events.
If you need any additional information or resources from us, please
don't hesitate to ask. I expect that if you folks need a vSphere
environment, we'll be able to provide one.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944642/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
