Description of problem: On f36+ and later (at least) Version-Release number of selected component (if applicable): systemd-250.8-1.fc36.aarch64 How reproducible: always on appropriate hardware. Steps to Reproduce: 1. boot on jetson-tx1 with mmc partitions 2. 3. Actual results: mmcblk0p1: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p1/queue/scheduler}, ignorin> tegra-vi 54080000.vi: failed to allocate vi channels: -19 tegra-video tegra-video: failed to initialize 54080000.vi: -19 mmcblk0p12: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p12/queue/scheduler}, ignor> mmcblk1p3: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0000.mmc/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p3/queue/scheduler}, ignorin> mmcblk0p11: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p11/queue/scheduler}, ignor> mmcblk1p2: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0000.mmc/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p2/queue/scheduler}, ignorin> mmcblk0p13: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p13/queue/scheduler}, ignor> mmcblk0p14: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p14/queue/scheduler}, ignor> mmcblk0p18: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p18/queue/scheduler}, ignor> mmcblk0p19: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p19/queue/scheduler}, ignor> mmcblk0p17: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p17/queue/scheduler}, ignor> mmcblk0p2: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p2/queue/scheduler}, ignorin> mmcblk0p10: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p10/queue/scheduler}, ignor> mmcblk1p1: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0000.mmc/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p1/queue/scheduler}, ignorin> mmcblk0p22: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p22/queue/scheduler}, ignor> mmcblk0p15: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p15/queue/scheduler}, ignor> mmcblk0p4: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p4/queue/scheduler}, ignorin> mmcblk0p16: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p16/queue/scheduler}, ignor> mmcblk0p3: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p3/queue/scheduler}, ignorin> mmcblk0p21: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p21/queue/scheduler}, ignor> mmcblk0p20: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p20/queue/scheduler}, ignor> Condition check resulted in dev-block-8:4.device - KINGSTON_SA400S37240G 4 being skipped. Created slice system-lvm2\x2dpvscan.slice - Slice /system/lvm2-pvscan. mmcblk0p5: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p5/queue/scheduler}, ignorin> Starting lvm2-pvscan@8:4.service - LVM event activation on device 8:4... mmcblk0p9: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p9/queue/scheduler}, ignorin> mmcblk0p6: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p6/queue/scheduler}, ignorin> mmcblk0p8: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p8/queue/scheduler}, ignorin> mmcblk0p7: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/platform/700b0600.mmc/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p7/queue/scheduler}, ignorin> Expected results: No errors Additional info: Looking at the fedora distgit, the module has regressed with the commit-id d906ff02 "Rebase the bfq patch" that removes the "ENV{DEVTYPE}=="disk", \" condition. Adding the condition again discard the error. Can you provide more information about why this rule has regressed again in your setup ? This is not the first time I'm reporting this issue and there is a need to clear it for good. Thanks in advance.
Ouch. Fix is waiting in https://src.fedoraproject.org/rpms/systemd/pull-request/93
This bug is NOT fixed !
What do you mean exactly? Fixed where.
FEDORA-2022-a3bf337a61 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a3bf337a61
FEDORA-2022-a3bf337a61 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-7cf1869073 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7cf1869073
FEDORA-2022-7cf1869073 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-7cf1869073` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7cf1869073 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-7cf1869073 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.