Uploaded image for project: 'GENIVI Development Platform'
  1. GENIVI Development Platform
  2. GDP-607

Sometimes Weston 1.11 fails to start

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Low
    • GDP 13
    • None
    • GDP Master
    • None
    • Raspberry Pi 3

    • 2930_Fabools, 3031_Galoomps

    Description

      Sometimes weston fails to start. As this not always happens it is either a timing issue or related to shutdown abrupt shutdowns in which cases the system is not properly cleaned up.
      Following is the error log produced when it fails:

      Jul 21 07:43:49 intel-corei7-64 systemd[1]: Started Weston reference Wayland compositor.
      Jul 21 07:43:49 intel-corei7-64 weston-launch[238]: [[0;1;39mpam_lastlog(login:session): file /var/log/lastlog created[[0m
      Jul 21 07:43:49 intel-corei7-64 weston-launch[238]: pam_unix(login:session): session opened for user root by (uid=0)
      Jul 21 07:43:51 intel-corei7-64 weston-launch[238]: failed to restore keyboard mode: Bad file descriptor
      Jul 21 07:43:51 intel-corei7-64 weston-launch[238]: failed to set KD_TEXT mode on tty: Bad file descriptor
      Jul 21 07:43:51 intel-corei7-64 weston-launch[238]: could not reset vt handling
      Jul 21 07:43:51 intel-corei7-64 systemd[1]: [[0;1;39mweston.service: Main process exited, code=exited, status=1/FAILURE[[0m
      Jul 21 07:43:51 intel-corei7-64 killall[357]: killall: weston: no process killed
      Jul 21 07:43:51 intel-corei7-64 systemd[1]: [[0;1;39mweston.service: Control process exited, code=exited status=1[[0m
      Jul 21 07:43:51 intel-corei7-64 systemd[1]: [[0;1;39mweston.service: Unit entered failed state.[[0m
      Jul 21 07:43:51 intel-corei7-64 systemd[1]: [[0;1;39mweston.service: Failed with result 'exit-code'.[[0m
      

      Workaround: Add restart parameters to weston.service makes it start on second attempt

      Original message by Leon Anavi:
      Hi,

      I have noticed that from time to time Weston 1.11 fails to start on GDP on Raspberry Pi 3. I am using the latest version from the repositories in GitHub. Initially I though it is again GDP-525 because there are no input devices but the patch for fixing this issue is still there and furthermore I cannot reproduce the issue in 100% of the cases.

      I started a discussion in the mailing list a few days ago and now I am creating the issue for further investigation.

      Attachments

        Issue Links

          Activity

            People

              dunderroffe Viktor Sjölind (Inactive)
              Leonanavi Leon Anavi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: