This bug was fixed in the package linux-oem-5.10 - 5.10.0-1021.22 --------------- linux-oem-5.10 (5.10.0-1021.22) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1021.22 -proposed tracker (LP: #1922921) * Display abnormal on the TGL+4k panel machines (LP: #1922885) - drm/i915/display: Do not allow DC3CO if PSR SF is enabled - SAUCE: drm/i915/display/psr: Disable DC3CO when the PSR2 is used * Fix mic on P620 after S3 resume (LP: #1921757) - ALSA: usb-audio: Carve out connector value checking into a helper - ALSA: usb-audio: Check connector value on resume -- Timo Aaltonen <timo.aalto...@canonical.com> Wed, 07 Apr 2021 18:07:55 +0300 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1920874 Title: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+ Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] Memory card removal event can not be reflected via uevent on some card readers Ex. Realtek card readers 0bda:0328 and 0bda:0158. Thus the file browser still see the ghost disk even it's already removed. [Fix] Found the commit 6540fbf6b643 in 5.9.0-rc3 introduce this regression. Fix it by making sure the partition scan will never be skipped for each vfs_open until the partition scan is really done [Test] Verified on the Realtek card reader 0bda:0328 on Dell Precision 7820 and the external Realtek usb interface card reader 0bda:0158. Insert the SD card in the card reader $ udevadm monitor Remove the SD card and check the udevadm monitor output KERNEL[188.377042] change /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.383261] remove /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) KERNEL[188.390887] change /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.396012] remove /devices/pci0000:00/0000:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) The remove event should be observed from the output messages. On the affected card reader, only change event would be observed. [Where problem could occur] These kind of card readers doesn't send remove event of scsi_disk and scsi_device like others so they only depend on the block subsystem to detect the media change and relect the removal event by partition scan. The behavior related to media removal is changed after 5.9.0-rc3. The remove event is not able to be correcly reflected since then, the device node of the media will remain there until next card insertion. ========== Original Bug Description ========== Ubuntu version: 20.10 Kernel: 5.10.0-1013-oem Card reader: Realtek Card Reader (0bda:0328 and 0bda:0158) Summary ======= After upgrading to kernel 5.9.0-rc3 or later, the device node for the partitions on the memory cards will not disappear after removing the memory cards. This is confusing to the user level applications like File Browser since the partition label will remain there for a long time. Steps to reproduce ================== 1. Upgrade to kernel later than 5.9.0-rc3 2. Plug the external card reader and insert the formatted memory card 3. Verify if the memory card mounted and visible on File Browser 4. Remove the memory card from the card reader 5. Verify if the mounted memory card removed from the File Browser Expected results ================ The mounted memory card identifier should be disappear after remove the memory card Actual results ============== The partition label of the memory card exists for a long time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: dev 1443 F.... pulseaudio /dev/snd/controlC0: dev 1443 F.... pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_UX434IQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=ac0e9628-3402-4892-84ab-a1dfb21be15a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.190 Tags: groovy Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434IQ_UX434IQ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434IQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434IQ_UX434IQ.203:bd02/26/2020:br5.16:svnASUSTeKCOMPUTERINC.:pnZenBookUX434IQ_UX434IQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434IQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434IQ_UX434IQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1920874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp