Ubuntu
linux package

"vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

Bug #1827162 reported by Khaled El Mously
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Won't Fix
Medium
bugproxy
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info)

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1827162

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
Andrew Cloke (andrew-cloke)
Changed in ubuntu-power-systems:
status: New → Incomplete
bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-177390 severity-medium targetmilestone-inin---
Andrew Cloke (andrew-cloke)
Changed in ubuntu-power-systems:
importance: Undecided → Medium
Frank Heimes (fheimes)
Changed in ubuntu-power-systems:
assignee: nobody → bugproxy (bugproxy)
Manoj Iyer (manjo)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Frank Heimes (fheimes)
tags: added: reverse-proxy-bugzilla
Revision history for this message
Manoj Iyer (manjo) wrote :

The kernel propagates the error back if /sys/../uevent file fails to write. /sys/bus/vio/devices/vio/uevent fails in this case because the drivers associated with it are:

ubuntu@tiselius:~$ ls /sys/bus/vio/drivers/
hvc_console tpm_ibmvtpm

On our power systems we do not have the devices associated with the drive. Looks like these messages are expected, since this is the expected behavior by the kernel I don't think this is a bug. Could IBM please confirm that this is indeed the case?

Revision history for this message
Thierry FAUCK (thierry-j) wrote :

Yes, the devices are effectively missing on the systems - the explanation is said that there's a dummy vio (ie, powervm) bus created, but since it's not in use you get this message. The message should be harmless, but ideally we should be able to just get rid of it.... This message has been around for a while.

Revision history for this message
Manoj Iyer (manjo) wrote :

Based on our analysis and comments from IBM confirming that this is an expected behavior, I am marking this as wont fix.

Changed in ubuntu-power-systems:
status: Incomplete → Won't Fix
Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2019-06-18 17:28 EDT-------
*** Bug 157265 has been marked as a duplicate of this bug. ***

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.