[Kernel-packages] [Bug 2021962] Re: F/xilinx and J/xilinx uses different keyword in /proc/device-tree/compatible
** Description changed: While testing J/xilinx, I noticed that the keyword we use to grep from /proc/device-tree/compatible has to be changed into kv26 instead of k26 that we used for F/xilinx J/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp F/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)". But it's better to let the kernel maintainer (Portia) to answer that if this difference is expected. Related change for tests: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543 + + --- + External link: https://warthogs.atlassian.net/browse/PEL-439 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2021962 Title: F/xilinx and J/xilinx uses different keyword in /proc/device- tree/compatible Status in ubuntu-kernel-tests: New Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: While testing J/xilinx, I noticed that the keyword we use to grep from /proc/device-tree/compatible has to be changed into kv26 instead of k26 that we used for F/xilinx J/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp F/xilinx: $ cat /proc/device-tree/compatible xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)". But it's better to let the kernel maintainer (Portia) to answer that if this difference is expected. Related change for tests: https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/443543 --- External link: https://warthogs.atlassian.net/browse/PEL-439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2021962/+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
[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
Here is the log that reproduce the hang. ** Attachment added: "papat.log" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5630877/+files/papat.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+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
[Kernel-packages] [Bug 2078763] Re: [uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service loaded failed during cold boot stress test
** Changed in: linux-mtk (Ubuntu)
Status: In Progress => Fix Released
--
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:
Fix Released
Status in linux-mtk source package in Jammy:
Fix Released
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 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
[Kernel-packages] [Bug 2078762] Re: [g510][g700] add fsource device tree node
** Changed in: linux-mtk (Ubuntu) Status: New => Fix Released -- 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/2078762 Title: [g510][g700] add fsource device tree node Status in linux-mtk package in Ubuntu: Fix Released Status in linux-mtk source package in Jammy: Fix Released Bug description: [Impact] to enable efuse operation, the device node is required. [Fix] add device node in both g510 and g700. [Test] to test the function, we also need the downstream fsource driver. in this case, we only add the device node. [Where problems could occur] none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078762/+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
[Kernel-packages] [Bug 2082868] Re: [g1200] regulators not enabled after sru d2024.08.12
** Changed in: linux-mtk (Ubuntu) Status: In Progress => Fix Released -- 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/2082868 Title: [g1200] regulators not enabled after sru d2024.08.12 Status in linux-mtk package in Ubuntu: Fix Released Status in linux-mtk source package in Jammy: Fix Released Bug description: [Impact] the following two upstream patches break mediatek downstream regulator device tree setup: d3cf8a17498d regulator: mt6360: De-capitalize devicetree regulator subnodes 1e0fb1136461 power: supply: mt6360_charger: Fix of_match for usb-otg-vbus regulator [Fix] in order to maintain the device tree compatibility, the kernel has to support both upstream and downstream device tree compatible strings. [Test] check if the downstream device tree nodes are still able to be probed. [Where problems could occur] the default behavior is to use upstream device tree compatibility strings, so the issue might arise if the downstream device tree nodes are not probed correctly. however, this is unlikely unless the user mixes the upper and lower case of nodes. LP: #2081960 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2082868/+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
