Bug 1813219
| Summary: | systemd-udevd issue with mmc on arm | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nicolas Chauvet (kwizart) <kwizart> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | armhfp | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-246.10-1.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-05 01:58:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Seems like this one works with me: mmcblk[0-9] I don't think there is any issue with the sd or sr cases, but there is probably a need to adapt the others msblk and mspblk cases... THis is the same as #1803500. It should be fixed in rawhide. It would be great if you could check that the fix there works in your case too. I was waiting for the beta freeze before backporting that patch. The effect should be only cosmetic, so it's now very high priority. *** This bug has been marked as a duplicate of bug 1803500 *** Re-opening the same issue for f33
as rebasing to systemd 246 with 55abe5f0ba5c81c4d2e607ca8dd8fb9acb13c797 as overwritten the fix.
See with:
git log use-bfq-scheduler.patch
Now the udev rules is missing the ENV{DEVTYPE}=="disk", \ line again...
Please re-apply for f33+
Sorry for that that. Fix queued in dist-git, will go out in the next rebuild. Thanks for the fix in f33, but the issue isn't forwarded to the rawhide branch. FEDORA-2021-dcc8b357ea has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-dcc8b357ea FEDORA-2021-dcc8b357ea has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-dcc8b357ea` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-dcc8b357ea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-dcc8b357ea has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: When booting on an armv7 device (Toshiba AC100) the following error occurs Version-Release number of selected component (if applicable): systemd-243.7-1.fc31.armv7hl How reproducible: always on boot Steps to Reproduce: 1. Boot on an armv7 device 2. 3. Actual results: journalctl -b -o cat _COMM=systemd-udevd -l Using default interface naming scheme 'v243'. ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. mmcblk0p1: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000000.sdhci/mmc_host/mmc0/mmc0:0007/block/mmcblk0/mmcblk0p1/queue/scheduler}, ignoring:> mmcblk0p2: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000000.sdhci/mmc_host/mmc0/mmc0:0007/block/mmcblk0/mmcblk0p2/queue/scheduler}, ignoring:> mmcblk0p3: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000000.sdhci/mmc_host/mmc0/mmc0:0007/block/mmcblk0/mmcblk0p3/queue/scheduler}, ignoring:> mmcblk1p1: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000600.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p1/queue/scheduler}, ignoring:> mmcblk1p2: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000600.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p2/queue/scheduler}, ignoring:> mmcblk1p3: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000600.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p3/queue/scheduler}, ignoring:> mmcblk1p4: /usr/lib/udev/rules.d/60-block-scheduler.rules:5 Failed to write ATTR{/sys/devices/soc0/c8000600.sdhci/mmc_host/mmc1/mmc1:0001/block/mmcblk1/mmcblk1p4/queue/scheduler}, ignoring:> Using default interface naming scheme 'v243'. ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Using default interface naming scheme 'v243'. ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Expected results: no errors Additional info: Seems like the globling also includes the partitions, removing the "*" seems to help to only consider the main block device. Patch comming...