This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1845319
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
--
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/1845319
Title:
writing 'add' to /sys/devices/vio/uevent fails with ENODEV
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
[impact]
The systemd-udev-trigger service calls 'udevadm trigger --type=devices
--action=add', which writes 'add' to all /sys/devices/ uevent nodes,
to re-generate their uevents sent to udev. Until systemd commit
97afc0351a96e0daa83964df33937967c75c644f, any errors during this
process were simply logged to debug and ignored, but now udevadm will
log errors and return failure.
On ppc64el, the /sys/devices/vio device returns ENODEV when writing
'add' to its uevent, which causes the udevadm command to return
failure, which causes the systemd-udev-trigger system service to fail.
The kernel vio driver should be fixed to not return ENODEV.
[test case]
On a ppc64el system, with any systemd containing commit
97afc0351a96e0daa83964df33937967c75c644f, check the status of the
systemd-udev-trigger service, to see that it's failed.
Alternately, again on a ppc64el system, run as root:
# echo add > /sys/devices/vio/uevent
-bash: echo: write error: No such device
[regression potential]
the potential should be low, as this appears to have always behaved
this way, at least for a while now.
[other info]
the systemd commit that changes udevadm to start failing for this
error isn't included in any Ubuntu release yet, this is found from
systemd upstream testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845319/+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
