On 27.06.25 23:38, Rodrigo Vivi wrote: >>> Or at least print a big warning into the system log? >>> >>> I mean a firmware update is usually something which the system >>> administrator triggers very explicitly because when it fails for some >>> reason (e.g. unexpected reset, power outage or whatever) it can sometimes >>> brick the HW. >>> >>> I think it's rather brave to do this automatically. Are you sure we don't >>> talk past each other on the meaning of the wedge event? >> >> The goal is not to do that automatically, but raise the uevent to the admin >> with enough information that they can decide for the right correctable >> action. > > Christian, Andre, any concerns with this still?
Well, that sounds not quite the correct use case for wedge events. See the wedge event is made for automation. For example to allow a process supervising containers get the device working again and re-start the container which used it or gather crash log etc ..... When you want to notify the system administrator which manual intervention is necessary then I would just write that into the system log and raise a device event with WEDGED=unknown. What we could potentially do is to separate between WEDGED=unknown and WEDGED=manual, e.g. between driver has no idea what to do and driver printed useful info into the system log. But creating an event with WEDGED=firmware-flash just sounds to specific, when we go down that route we might soon have WEDGE=change-bios-setting, WEDGE=.... Regards, Christian. > >> >> Thanks, >> Rodrigo.
