This bug is awaiting verification that the linux-mtk/5.15.0-1034.39
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-mtk-v2 
verification-needed-jammy-linux-mtk

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mtk in Ubuntu.
https://bugs.launchpad.net/bugs/2078763

Title:
   [uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service
  loaded failed during cold boot stress test

Status in linux-mtk package in Ubuntu:
  In Progress
Status in linux-mtk source package in Jammy:
  In Progress

Bug description:
  [Impact]
  During the cold-boot stress test, DUT did cold boot 30 times successfully, 
however, Checkbox found a System service, 
systemd-backlight@backlight:1c008000.dsi0.0.service, loaded failed once at the 
iteration 9th.

  Panel: DSI panel
  DTBO: default

  [Fix]
  (DSI + eDP) is fine because dsi and edp drivers are built-in. when panel 
driver is probed, it would try to wake up the parent and since dsi and edp are 
already built-in, the brightness function will work without any time gap.
  (DSI + HDMI) has the probability to fail because when panel driver is probed, 
it would try to wake up the parent, but hdmi driver is modularized, it will 
need to wait the hdmi driver to be loaded. the time gap would cause 
systemd-backlight service fails.
  the workaround fix would be to make the hdmi module built-in.

  [Test]
  1. Flash genio-core-22-20240802-124.img image
  2. Install Checkbox
     ```
     sudo snap install checkbox22 --beta
     sudo snap install checkbox-baoshan --edge --devmode
     sudo snap install checkbox-ce-oem --channel="uc22/edge" --devmode
     sudo snap stop --disable checkbox-ce-oem.remote-slave

     sudo snap install bluez
     sudo snap install genio-test-tool --devmode
     sudo snap install bugit --devmode
     ```
  3. Run cold-boot stress testing via Checkbox Control (Need another device as 
Host to run checkbox remotely)
     On Host, install and run the following command to test DUT via checkbox 
control
       ```
       # Install checkbox on host (suppose your host is jammy)
       $ sudo snap install checkbox22 --beta
       $ sudo snap install checkbox --channel="22.04/beta" --classic
       # test-runner-G350 is a launcher file [1]
       $ checkbox.checkbox-cli control <IP of DUT> test-runner-G700

       # Choose "genio-baoshan - Stress tests for Ubuntu Core 22" plan

       # Choose "Warm-boot Stress Test" plan
       ```

  Checkbox Script [2]
    ```
    sleep "${{STRESS_BOOT_WAIT_DELAY:-120}}"
    reboot
    ```

  [1]: 
https://git.launchpad.net/~baoshan-team/baoshan/+git/checkbox-baoshan/tree/launchers/test-runner-G700
  [2]: 
https://github.com/canonical/checkbox/blob/6f1685379562d7076f233112f125478185dcb029/providers/base/units/stress/boot.pxu#L145

  [Where problems could occur]
  making the module to be built-in should be no harm for the system.

  
  LP: #2076054

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078763/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to