Smart system shutdown

This proposal has been accepted as a session.


One Line Summary

How systemd inhibitors can be used to handle system shutdown in eCall and telephony scenarios.


A cars infotainment system is not necessarily shutdown once the car is stoppend and the key is removed. There are certain scenarios where the system has to remain active.

With a regular phone call, when the car is turned off, the system should only shutdown if the call is ended or the battery level reaches a point where ignition of the car would be impossible.

In case of an accident, modern cars use an eCall to automatically contact emergency services and transmit relevant data. Since the electronic system itself is an additional cause for injuries, it needs to be shutdown once the eCall is finished.

An eCall can also be started manually, e.g. in case of a medical emergency. In these cases the system must stay active even if the battery level is getting low.

In this session we would like to discuss if systemd inhibitors are capable of dealing with these scenarios and should limitations exist, how they can be fixed.


systemd, automotive, telephony, ecall

Presentation Materials



  • Me-selfie-waverly-bridge

    Colin Guthrie



    I have been an avid user of Linux for the last twenty or so years and in that time have built up a wealth of experience and connections.

    Initially involved in Mandrake Linux as a packager/contributor and then through the renaming process to Mandriva. When the commerical company behind Mandriva hit financial troubles, I, along with several other former employees, was one of the founding members of the Mageia distribution which is still going strong.

    Over the years my areas of focus have shifted somewhat. Originally I was maintainer of stack and helped push the eyecandy related Compiz packages. I moved on to caring about audio and was responsible for pushing PulseAudio as the default audio option in Mandriva which received very good writeups for the way in which it was introduced and it’s stability there compared to other distributions. I was heavily involved in the upstream PulseAudio project.

    Laterly, focus has shifted again but remains in the Plumbing layers. I have been responsible for pushing systemd and dracut as the boot+init solutions in Mageia and adapting various tools as well as contributing back to upstream dracut and systemd (albeit minimally in the case of the latter).

    I remain very interested in Audio and the other Plumbing layers although my day job is unrelated and invovles web development and a little sysadmin at my own company Tribalogic Ltd


  • Timo-1

    Timo Müller

    BMW Car IT GmbH


    No Biography Provided