[Bug 2087507] Re: [SRU] Fix error of resume on rtl8168fp
** Also affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => Fix Committed ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2087507 Title: [SRU] Fix error of resume on rtl8168fp To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2087507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086210] Re: Backport some AppArmor complain-mode profile bugfixes from Oracular
** Summary changed: - Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble + Backport some AppArmor complain-mode profile bugfixes from Oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086210 Title: Backport some AppArmor complain-mode profile bugfixes from Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086660] [NEW] Update notification data is not user request data
Public bug reported: https://github.com/openstack/octavia/blob/df85248493f9f1a94de1f1c36a7b87fc6515a28a/octavia/controller/worker/v2/flows/load_balancer_flows.py#L386 When modifying the loadbalancer, the event data being passed is not appropriate. Compared to other components (nova, manila...), event data for modification conveys data after change. However, the loadbalancer is delivering data before changes, so it is not possible to know which request was delivered through event data. The reason for this is that the data retrieved from the DB before the data change is passed on to the event data object and used, so this part seems to need to be changed. ** Affects: octavia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086660 Title: Update notification data is not user request data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/octavia/+bug/2086660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084626] Re: [g510] ddc failed message when the monitor does not support SCDC
verified on g510 with 5.15.0-1035.41 kernel in proposed. did not see the error messages when plugging in the monitor with 1080p max resolution supported. ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084626 Title: [g510] ddc failed message when the monitor does not support SCDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2084626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086210] Re: Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble
** Description changed:
+ SRU Justification:
+
[Impact]
Backporting two AppArmor bugfixes (2de989ae726b "apparmor: allocate
xmatch for nullpdf inside aa_alloc_null" and 62bd5d5f2149 "apparmor:
properly handle cx/px lookup failure for complain") from the Ubuntu
Oracular kernel will fix incorrect behavior that occurs with the usage
of some complain mode profiles (a kernel oops and an actual denial
occurring in complain mode, respectively).
[Fix]
Apply the two patches 2de989ae726b and 62bd5d5f2149 from the Ubuntu
Oracular kernel, previously applied to the Oracular kernel via LP
#2028253 as #94/99 and #95/99 in the series.
[Test case]
Patch 62bd5d5f2149 can be tested by loading the following profile into
the kernel:
abi ,
include
profile ls_child flags=(complain) {
- include
+ include
- /dev/tty rw,
- /usr/bin/ls cxr,
+ /dev/tty rw,
+ /usr/bin/ls cxr,
}
and exercising the profile's nonexistent transition with `aa-exec -p
ls_child sh -c ls`. With the patch applied, the ls command will succeed
instead of failing.
Patch 2de989ae726b is much harder to test, unfortunately. The reproducer
I have is (deterministically) finicky but goes through a Docker
indirection layer, although at least one other person has encountered
the same kernel oops without using Docker. I have attached the files
needed to construct a reproducer to the LP bug report.
With the patch applied, the run_reproducer.sh script will succeed
instead of generating a kernel oops.
[Regression potential]
This patch set fixes bugs in the handling of complain mode profiles, and
are both very small. A bug caused by patch 2de989ae726b would cause, at
most, a memory leak by preventing deallocation of a reference-counted
profile object. A bug introduced by patch 62bd5d5f2149 would show up in
the handling of complain mode profiles and would not affect enforcement
of enforce mode profiles.
+
+ [Other Info]
+
+ This patchset backports some patches from
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028253 which were
+ applied to Oracular but not to Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086210
Title:
Backport some AppArmor complain-mode profile bugfixes from Oracular to
Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086210/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086210] Re: Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble
** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2086210 Title: Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2086210] [NEW] Backport some AppArmor complain-mode profile bugfixes from Oracular to Noble
Public bug reported:
[Impact]
Backporting two AppArmor bugfixes (2de989ae726b "apparmor: allocate
xmatch for nullpdf inside aa_alloc_null" and 62bd5d5f2149 "apparmor:
properly handle cx/px lookup failure for complain") from the Ubuntu
Oracular kernel will fix incorrect behavior that occurs with the usage
of some complain mode profiles (a kernel oops and an actual denial
occurring in complain mode, respectively).
[Fix]
Apply the two patches 2de989ae726b and 62bd5d5f2149 from the Ubuntu
Oracular kernel, previously applied to the Oracular kernel via LP
#2028253 as #94/99 and #95/99 in the series.
[Test case]
Patch 62bd5d5f2149 can be tested by loading the following profile into
the kernel:
abi ,
include
profile ls_child flags=(complain) {
include
/dev/tty rw,
/usr/bin/ls cxr,
}
and exercising the profile's nonexistent transition with `aa-exec -p
ls_child sh -c ls`. With the patch applied, the ls command will succeed
instead of failing.
Patch 2de989ae726b is much harder to test, unfortunately. The reproducer
I have is (deterministically) finicky but goes through a Docker
indirection layer, although at least one other person has encountered
the same kernel oops without using Docker. I have attached the files
needed to construct a reproducer to the LP bug report.
With the patch applied, the run_reproducer.sh script will succeed
instead of generating a kernel oops.
[Regression potential]
This patch set fixes bugs in the handling of complain mode profiles, and
are both very small. A bug caused by patch 2de989ae726b would cause, at
most, a memory leak by preventing deallocation of a reference-counted
profile object. A bug introduced by patch 62bd5d5f2149 would show up in
the handling of complain mode profiles and would not affect enforcement
of enforce mode profiles.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Attachment added: "Files for reproducing the bug fixed by 2de989ae726b"
https://bugs.launchpad.net/bugs/2086210/+attachment/5833490/+files/docker_reproducer.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086210
Title:
Backport some AppArmor complain-mode profile bugfixes from Oracular to
Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2086210/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085583] [NEW] package linux-image-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Just upgraded, installed another video card and nvidia drivers ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-47-generic 6.8.0-47.47 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:lee2374 F pipewire /dev/snd/controlC0: lee2379 F wireplumber /dev/snd/controlC1: lee2379 F wireplumber /dev/snd/controlC2: lee2379 F wireplumber CRDA: N/A CasperMD5CheckResult: pass Date: Thu Oct 24 20:19:33 2024 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-08-10 (441 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550 GAMING X V2 ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=ffa4de09-8982-4ead-a17c-0de894e0db9f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.12-1ubuntu7 RfKill: SourcePackage: dkms Title: package linux-image-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to noble on 2024-10-24 (0 days ago) dmi.bios.date: 03/22/2024 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FE dmi.board.asset.tag: Default string dmi.board.name: B550 GAMING X V2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFE:bd03/22/2024:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550GAMINGXV2:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnB550GAMINGXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: B550 MB dmi.product.name: B550 GAMING X V2 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-07-22T10:59:07 ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085583 Title: package linux-image-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2085583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084626] Re: [g510] ddc failed message when the monitor does not support SCDC
** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084626 Title: [g510] ddc failed message when the monitor does not support SCDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2084626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085437] Re: BT Switch cannot open under Ubuntu 24.04 on MT7920
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085437 Title: BT Switch cannot open under Ubuntu 24.04 on MT7920 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082225] Re: Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume from suspend
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082225 Title: Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084059] Re: OVTI08F4:00: number of CSI2 data lanes 2 is not supported
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084059 Title: OVTI08F4:00: number of CSI2 data lanes 2 is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2084059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085398] Re: The ASPM is disabled on Realtek NIC which prevents the system from entering s0ix
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085398 Title: The ASPM is disabled on Realtek NIC which prevents the system from entering s0ix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084526] Re: r8169: transmit queue 0 timed out error when re-plugging the Ethernet cable
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084526 Title: r8169: transmit queue 0 timed out error when re-plugging the Ethernet cable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2084526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085410] Re: Fix USB device suspend failure while HCD in S4 wakeup
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085410 Title: Fix USB device suspend failure while HCD in S4 wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077941] Re: AMD ACP7.1 support
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077941 Title: AMD ACP7.1 support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085406] Re: [SRU] add support of QCA BT 0489:e0fc
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085406 Title: [SRU] add support of QCA BT 0489:e0fc To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2085406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085456] Re: Fix phantom monitor on some machines with kernel 6.11
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085456 Title: Fix phantom monitor on some machines with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085485] Re: Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported features (-110)"
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085485 Title: Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported features (-110)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085504] Re: iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085504 Title: iwlwifi :00:14.3: Failed to start RT ucode: -110 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2085504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081699] Re: [g700] support p1v4 hardware
verified on 202409-35342 g700 p1v4 hardware. both dsi and edp works fine. ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081699 Title: [g700] support p1v4 hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081696] Re: [g1200] Call trace appeared when reload mtk_rng module
did not see the call trace on 5.15.0-1035-41 by following commands: $ modprobe -r mtk_rng $ modprobe mtk_rng ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081696 Title: [g1200] Call trace appeared when reload mtk_rng module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081686] Re: [g1200] possible kernel memory leak through CONFIG_DEBUG_KMEMLEAK
after enabling the following options in annotation:
CONFIG_DEBUG_KMEMLEAK policy<{'arm64': 'y'}>
CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN policy<{'arm64': 'y'}>
CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF policy<{'arm64': 'n'}>
CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE policy<{'arm64': '16000'}>
CONFIG_DEBUG_KMEMLEAK_TEST policy<{'arm64': 'm'}>
and boot the device:
root@mtk-genio:/home/ubuntu# uname -r
5.15.0-1035-mtk
root@mtk-genio:/home/ubuntu# cat /sys/kernel/debug/kmemleak
root@mtk-genio:/home/ubuntu#
** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-done-jammy-linux-mtk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081686
Title:
[g1200] possible kernel memory leak through CONFIG_DEBUG_KMEMLEAK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081686/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081810] Re: [SRU] uncore: Add ARL and LNL support on 6.11
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081810 Title: [SRU] uncore: Add ARL and LNL support on 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2081810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079017] Re: Need driver support for Realtek RTL8126A rev.b 5Gbps ethernet [10ec:8126]
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079017 Title: Need driver support for Realtek RTL8126A rev.b 5Gbps ethernet [10ec:8126] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2079017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081785] Re: UBSAN: array-index-out-of-bounds in module mt76
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081785 Title: UBSAN: array-index-out-of-bounds in module mt76 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2081785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083292] Re: Missing device ID for amd_atl driver for AMD Strix platform
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083292 Title: Missing device ID for amd_atl driver for AMD Strix platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2083292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084808] Re: Dell Alienware sysytem reports errors of dell_wmi_sysman and dell_smbios in demsg
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084808 Title: Dell Alienware sysytem reports errors of dell_wmi_sysman and dell_smbios in demsg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078773] Re: Missing devices nodes for AMD Instinct MI300 card when installed along with integrated display
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078773 Title: Missing devices nodes for AMD Instinct MI300 card when installed along with integrated display To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2078773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081130] Re: Intel(R) PRO/1000 I219 ethernet adapter [8086:550c] may block entrance of modern standby
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081130 Title: Intel(R) PRO/1000 I219 ethernet adapter [8086:550c] may block entrance of modern standby To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2081130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081796] Re: Support Qualcomm WCN7851 Dual Bluetooth Adapter 0489:E0F3
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081796 Title: Support Qualcomm WCN7851 Dual Bluetooth Adapter 0489:E0F3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083905] Re: Add Intel Arrow Lake-H LPSS PCI IDs
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083905 Title: Add Intel Arrow Lake-H LPSS PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083800] Re: Dell AIO backlight is not working, dell_uart_backlight module is missing
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083800 Title: Dell AIO backlight is not working, dell_uart_backlight module is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042097] Re: [MIR][jammy] oem-somerville-magmar-meta
** Changed in: oem-priority Status: Fix Committed => Fix Released ** Changed in: oem-somerville-magmar-meta (Ubuntu) Status: New => Won't Fix ** No longer affects: Ubuntu Jammy ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042097 Title: [MIR][jammy] oem-somerville-magmar-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081866] Re: Support ov05c10 camera sensor in Intel ipu-bridge
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081866 Title: Support ov05c10 camera sensor in Intel ipu-bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084759] Re: Fix distorted sound output after suspend more than 30 seconds on Cirrus audio codec
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084759 Title: Fix distorted sound output after suspend more than 30 seconds on Cirrus audio codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
15) We added https://git.launchpad.net/~ubuntu-core- dev/grub/+git/ubuntu/commit/?h=focal&id=2310fddfe741bf77f8721675a679478d0b6a5613 since focal that will order the kernel flavour we specify first in the GRUB boot entries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083129] Re: [Lenovo Ubuntu 24.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip
** Summary changed: - netplan static IP address assignment use NetworkManager as renderer would be lost static ip + [Lenovo Ubuntu 24.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: [Lenovo Ubuntu 24.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084626] Re: [g510] ddc failed message when the monitor does not support SCDC
** Description changed: [Impact] After connectin an external HDMI monitor (ASUS VG23AH) to DUT, the error message is thrown multiple times. + "mediatek-hdmi-mt8195-ddc ddc-i2c: ddc failed! : 0" [Fix] checks the capability of the monitor before sending the SCDC commands. [Test] - connect the monitor does not support SCDC + connect the monitor does not support SCDC [Where problems could occur] - when a SCDC supported monitor is regarded as non-supported. + when a SCDC supported monitor is regarded as non-supported. LP: #2062513 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084626 Title: [g510] ddc failed message when the monitor does not support SCDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2084626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2084626] [NEW] [g510] ddc failed message when the monitor does not support SCDC
Public bug reported: [Impact] After connectin an external HDMI monitor (ASUS VG23AH) to DUT, the error message is thrown multiple times. [Fix] checks the capability of the monitor before sending the SCDC commands. [Test] connect the monitor does not support SCDC [Where problems could occur] when a SCDC supported monitor is regarded as non-supported. LP: #2062513 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084626 Title: [g510] ddc failed message when the monitor does not support SCDC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2084626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931390] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed after successful CPU1 offline
this affects jammy:linux-mtk-5.15-1034.40 http://test-results.kernel/d2024.08.12/jammy/linux- mtk/5.15.0-1034.40/sru-mtk-testflinger-mtk-g1200.arm64-ubuntu_ltp- log.html#cpuhotplug:cpuhotplug03-start 156254 cpuhotplug03 1 TINFO: Onlining CPU 1 1562555 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562560 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562573 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562583 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562597 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562605 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562611 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562622 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562630 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562642 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562653 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562662 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562675 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562686 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562697 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1562705 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 156271 cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1 from the log, after waking up the cpu and 1 second sleep, the required task is running on the cpu1 from the first time ps command, but could not find the required task on the target cpu in the following second ps command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931390 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed after successful CPU1 offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Patch added: "ubuntu-drivers-common_0.9.6.2~0.22.04.9.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2083657/+attachment/5827082/+files/ubuntu-drivers-common_0.9.6.2~0.22.04.9.debdiff ** Description changed: [ Impact ] * This issue affects all Ubuntu OEM preloaded systems that are still utilizing the OEM kernel, particularly those equipped with NVIDIA graphics drivers. - * Systems may fail to boot properly due to an outdated OEM kernel conflicting with newer NVIDIA drivers, leading to a black screen on reboot. + * Systems may fail to boot properly due to an outdated OEM kernel conflicting with newer NVIDIA drivers, leading to a black screen on reboot. [ Test Plan ] - * To verify the fix, ensure that the file `/etc/default/grub.d/oem-flavour.cfg` is successfully removed from the affected system after applying the update. - * Additionally, after the system reboots, check that it boots into the general HWE kernel rather than the OEM kernel. + * To verify the fix, ensure that the file `/etc/default/grub.d/oem-flavour.cfg` is successfully removed from the affected system after applying the update. + * After the system reboots, check that it boots into the general HWE kernel rather than the OEM kernel. + + * Idempotency Testing: + - Perform the upgrade multiple times on the same system to verify that the upgrade process is idempotent, ensuring that repeated upgrades do not result in unexpected behavior or changes. + + * Non-OEM System Testing: + - Test the upgrade on a system without OEM kernels to ensure that the upgrade does not affect systems that are not preloaded with the OEM kernel. + - Confirm that the system continues to function normally and boots into the correct kernel after the update. [ Where problems could occur ] - * Removing `/etc/default/grub.d/oem-flavour.cfg` may cause systems relying on the OEM kernel for specific hardware compatibility to lose access to certain OEM-specific optimizations. - * There is a low risk that after removing the OEM kernel, some hardware features may not function as expected if the general HWE kernel does not fully support them. + * Removing `/etc/default/grub.d/oem-flavour.cfg` may cause systems relying on the OEM kernel for specific hardware compatibility to lose access to certain OEM-specific optimizations. + * There is a low risk that after removing the OEM kernel, some hardware features may not function as expected if the general HWE kernel does not fully support them. [ Other Info ] * This patch is targeted only for Ubuntu 22.04 and its associated OEM kernels. - * The issue is specific to systems using NVIDIA drivers in conjunction with an outdated OEM kernel, which conflicts with updates to the HWE kernel and NVIDIA packages. + * The issue is specific to systems using NVIDIA drivers in conjunction with an outdated OEM kernel, which conflicts with updates to the HWE kernel and NVIDIA packages. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ ubuntu-report show | grep DCD "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.6 Candidate: 1:0.9.6.2~0.22.04.7 Version table: 1:0.9.6.2~0.22.04.7 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 1:0.9.6.2~0.22.04.6 100 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen - * The system should seamlessly upgrade NVIDIA drivers and the HWE + * The system should seamlessly upgrade NVIDIA drivers and the HWE kernel without breaking the boot process. The system should boot into the latest supported HWE kernel without encountering compatibility issues with the NVIDIA drivers. 4) What happened instead - * After unattended-upgrades, the system rebooted into the OEM kernel, + * After unattended-upgrades, the system rebooted into the OEM kernel, which is outdated and incompatible with the new NVIDIA drivers. As a result, the screen remained black upon reboot. We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the system booting from deprecated OEM kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.
[Bug 2078763] Re: [uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service loaded failed during cold boot stress test
verified pass on g700 by checking drm component sequence with kernel linux-mtk/5.15.0-1034.40. qa team will check the issue on core system after kernel snap is released. ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078763 Title: [uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service loaded failed during cold boot stress test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078762] Re: [g510][g700] add fsource device tree node
verified pass by using the following command after updating the device tree: $ dtc -I fs -O dts /proc/device-tree|grep fsource ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078762 Title: [g510][g700] add fsource device tree node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
> 5. Why is a previous debian/changelog entry being changed? If you're correcting a previous mistake then I guess it's subjective as to whether that's OK, but I can't distinguish between that and an inadvertent change. Please could you clarify? I get the Debian source package by `pull-lp-source ubuntu-drivers-common jammy` and then generate the debdiff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
> 4. I think the "&& exit 0" lines are a bug, because they will preclude any #DEBHELPER# snippets from running. It looks like debhelper already has generated code in ubuntu-drivers.postinst so this seems like a real and immediate issue. Probably the easiest is to move this into a function and use `return`, but note that then you'll need to do explicit error checking since `set -e` will no longer work. But also, please add `set -e` anyway as is best practice. I will improve it in the following patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
> 6. Shouldn't you be triggering update-grub after touching /etc/default/grub.d, or is there a mechanism for that already in place? The issue itself is triggered by unattended-upgrades to install the generic hwe kernel and NVIDIA packages so it will execute update-grub for sure, but the order is unknown so we shall make it trigger updata- grub in or after ubuntu-drivers-common postinst. I will improve this in the following patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
> 7. I think some additional testing is warranted: specifically to test idempotency of the upgrade path, as well as correct handling for the common case of a non-OEM install. Please could you add to the Test Plan to test these paths? The patch is designed to activate only when /etc/default/grub.d/oem- flavour.cfg exists. It should be nothing happening if /etc/default/grub.d/oem-flavour.cfg doesn't exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082868] Re: [g1200] regulators not enabled after sru d2024.08.12
verified pass on g1200 with 1034.40 kernel. the required mt6360 is working normally. ** Tags removed: verification-needed-jammy-linux-mtk ** Tags added: verification-done-jammy-linux-mtk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082868 Title: [g1200] regulators not enabled after sru d2024.08.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2082868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
> 8. What happens if reimaging from the OEM image, and then upgrading to the updates pocket all at once, including the update that triggered this bug together with this for it? Which postinst will run first? If not deterministic, and this one runs first, will that cause a problem? Do we need a Breaks clause for ordering purposes? Or is it OK to remove /etc/default/grub.d/oem-flavour.cfg _before_ the bug is triggered? If OEM metapackage postinst runs first, it will create the symbolic link of /etc/default/grub.d/oem-flavour.cfg. And then ubuntu-drivers-common postinst will remove it. If ubuntu-drivers-common postinst first, there is nothing happening. But OEM metapackage postinst will still create the symbolic link of /etc/default/grub.d/oem-flavour.cfg. However the content in /etc/default/grub.d/oem-flavour.cfg for the later OEM images from right now for jammy should only be 'GRUB_FLAVOUR_ORDER=generic' instead of 'GRUB_FLAVOUR_ORDER=oem'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060063] Re: PMU counters for Cortex-A78 not working correctly
i was attempting to use the latest version of userspace program, perf, for my testing. however, i realize that this may not be appropriate as perf should ideally be paired with the corresponding version of the Linux kernel. with newer kernels, we no longer need to specify specific cortex events to retrieve status information. in contrast, with version 5.15, we had to explicitly request the events we were interested in from the perf list to obtain the desired status. to achieve results consistent with the newer kernel, it’s not only necessary to apply the patch mentioned in #2, but the perf tool also needs to be updated. since we can specify events in version 5.15 to retrieve status information, I think no additional changes are required for 5.15. ** Changed in: linux-mtk (Ubuntu) Status: In Progress => Won't Fix ** Changed in: linux-mtk (Ubuntu Jammy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060063 Title: PMU counters for Cortex-A78 not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2060063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062535] zip on ubuntu 24.04 system
I have no idea when the fix will be available. Currently for my systems, I have substituted the zip program which came with Ubuntu 22.04. Lee -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062535 Title: zip fails when filenames contain unicode characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zip/+bug/2062535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Description changed: [ Impact ] - * This affects all Ubuntu OEM preloaded systems which are still using OEM kernel. - * Expecially for those systems which are using NVIDIA graphic driver. + * This issue affects all Ubuntu OEM preloaded systems that are still utilizing the OEM kernel, particularly those equipped with NVIDIA graphics drivers. + * Systems may fail to boot properly due to an outdated OEM kernel conflicting with newer NVIDIA drivers, leading to a black screen on reboot. [ Test Plan ] - * We will check on the problematic system to see if - /etc/default/grub.d/oem-flavour.cfg is removed. + * To verify the fix, ensure that the file `/etc/default/grub.d/oem-flavour.cfg` is successfully removed from the affected system after applying the update. + * Additionally, after the system reboots, check that it boots into the general HWE kernel rather than the OEM kernel. [ Where problems could occur ] - * N/A. + * Removing `/etc/default/grub.d/oem-flavour.cfg` may cause systems relying on the OEM kernel for specific hardware compatibility to lose access to certain OEM-specific optimizations. + * There is a low risk that after removing the OEM kernel, some hardware features may not function as expected if the general HWE kernel does not fully support them. [ Other Info ] - * This patch will be only applied to Ubuntu 22.04. + * This patch is targeted only for Ubuntu 22.04 and its associated OEM kernels. + * The issue is specific to systems using NVIDIA drivers in conjunction with an outdated OEM kernel, which conflicts with updates to the HWE kernel and NVIDIA packages. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ ubuntu-report show | grep DCD "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.6 Candidate: 1:0.9.6.2~0.22.04.7 Version table: 1:0.9.6.2~0.22.04.7 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 1:0.9.6.2~0.22.04.6 100 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen - unattended-upgrades won't break the system. + + * The system should seamlessly upgrade NVIDIA drivers and the HWE + kernel without breaking the boot process. The system should boot into + the latest supported HWE kernel without encountering compatibility + issues with the NVIDIA drivers. 4) What happened instead - unattended-upgrades upgraded the NVIDIA packages and the general HWE kernel that retired the OEM kernel in the background. - After the system reboot, the screen keeps black because it boots the OEM kernel and the OEM kernel is still using the old nvidia prebuilt kernel module that is not met to the NVIDIA packages. + + * After unattended-upgrades, the system rebooted into the OEM kernel, + which is outdated and incompatible with the new NVIDIA drivers. As a + result, the screen remained black upon reboot. We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the system booting from deprecated OEM kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2004592] Re: aalogparse.h cannot be included from C++ code
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Ryan Lee (rlee287) ** Changed in: apparmor (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2004592 Title: aalogparse.h cannot be included from C++ code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2004592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
u@ubuntu:~$ ls -l /etc/default/grub.d/oem-flavour.cfg lrwxrwxrwx 1 root root 47 Sep 27 16:06 /etc/default/grub.d/oem-flavour.cfg -> /usr/share/oem-sutton-bast-meta/oem-flavour.cfg u@ubuntu:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.6 Candidate: 1:0.9.6.2~0.22.04.8 Version table: 1:0.9.6.2~0.22.04.8 500 500 https://ppa.launchpadcontent.net/fourdollars/experimental/ubuntu jammy/main amd64 Packages 1:0.9.6.2~0.22.04.7 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 1:0.9.6.2~0.22.04.6 100 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages u@ubuntu:~$ sudo apt install ubuntu-drivers-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: apt-file dmraid gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 iperf kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16 libopenscap8 libregexp-assemble-perl libtimezonemap-data libtimezonemap1 msr-tools pastebinit python3-icu python3-pam rdate ubiquity-casper ubiquity-ubuntu-artwork xautomation Use 'sudo apt autoremove' to remove them. Suggested packages: python3-aptdaemon.pkcompat The following packages will be upgraded: ubuntu-drivers-common 1 upgraded, 0 newly installed, 0 to remove and 195 not upgraded. Need to get 85.2 kB of archives. After this operation, 1,024 B of additional disk space will be used. Get:1 https://ppa.launchpadcontent.net/fourdollars/experimental/ubuntu jammy/main amd64 ubuntu-drivers-common amd64 1:0.9.6.2~0.22.04.8 [85.2 kB] Fetched 85.2 kB in 2s (48.0 kB/s) Preconfiguring packages ... (Reading database ... 202947 files and directories currently installed.) Preparing to unpack .../ubuntu-drivers-common_1%3a0.9.6.2~0.22.04.8_amd64.deb ... Unpacking ubuntu-drivers-common (1:0.9.6.2~0.22.04.8) over (1:0.9.6.2~0.22.04.6) ... Setting up ubuntu-drivers-common (1:0.9.6.2~0.22.04.8) ... /etc/default/grub.d/oem-flavour.cfg contains oem-sutton-bast-meta and GRUB_FLAVOUR_ORDER=oem. Removing oem-flavour.cfg... u@ubuntu:~$ ls -l /etc/default/grub.d/oem-flavour.cfg ls: cannot access '/etc/default/grub.d/oem-flavour.cfg': No such file or directory ** Patch added: "ubuntu-drivers-common_0.9.6.2~0.22.04.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2083657/+attachment/5824916/+files/ubuntu-drivers-common_0.9.6.2~0.22.04.8.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Description changed: + [ Impact ] + + * This affects all Ubuntu OEM preloaded systems those are still using OEM kernel. + * Expecially for those systems those are using NVIDIA graphic driver. + + [ Test Plan ] + + * We will check on the problematic system to see if + /etc/default/grub.d/oem-flavour.cfg is removed. + + [ Where problems could occur ] + + * N/A. + + [ Other Info ] + + * This patch will be only applied to Ubuntu 22.04. + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ ubuntu-report show | grep DCD - "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" + "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: - Installed: 1:0.9.6.2~0.22.04.6 - Candidate: 1:0.9.6.2~0.22.04.7 - Version table: - 1:0.9.6.2~0.22.04.7 500 - 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages - *** 1:0.9.6.2~0.22.04.6 100 - 100 /var/lib/dpkg/status - 1:0.9.6.1 500 - 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + Installed: 1:0.9.6.2~0.22.04.6 + Candidate: 1:0.9.6.2~0.22.04.7 + Version table: + 1:0.9.6.2~0.22.04.7 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + *** 1:0.9.6.2~0.22.04.6 100 + 100 /var/lib/dpkg/status + 1:0.9.6.1 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen unattended-upgrades won't break the system. 4) What happened instead unattended-upgrades upgraded the NVIDIA packages and the general HWE kernel that retired the OEM kernel in the background. After the system reboot, the screen keeps black because it boots the OEM kernel and the OEM kernel is still using the old nvidia prebuilt kernel module that is not met to the NVIDIA packages. We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the system booting from deprecated OEM kernels. ** Description changed: [ Impact ] - * This affects all Ubuntu OEM preloaded systems those are still using OEM kernel. - * Expecially for those systems those are using NVIDIA graphic driver. + * This affects all Ubuntu OEM preloaded systems which are still using OEM kernel. + * Expecially for those systems which are using NVIDIA graphic driver. [ Test Plan ] - * We will check on the problematic system to see if + * We will check on the problematic system to see if /etc/default/grub.d/oem-flavour.cfg is removed. [ Where problems could occur ] - * N/A. + * N/A. [ Other Info ] - * This patch will be only applied to Ubuntu 22.04. + * This patch will be only applied to Ubuntu 22.04. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ ubuntu-report show | grep DCD "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.6 Candidate: 1:0.9.6.2~0.22.04.7 Version table: 1:0.9.6.2~0.22.04.7 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 1:0.9.6.2~0.22.04.6 100 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen unattended-upgrades won't break the system. 4) What happened instead unattended-upgrades upgraded the NVIDIA packages and the general HWE kernel that retired the OEM kernel in the background. After the system reboot, the screen keeps black because it boots the OEM kernel and the OEM kernel is still using the old nvidia prebuilt kernel module that is not met to the NVIDIA packages. We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the system booting from deprecated OEM kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081785] Re: UBSAN: array-index-out-of-bounds in module mt76
** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081785 Title: UBSAN: array-index-out-of-bounds in module mt76 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2081785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083022] Re: [SRU] Fix AST DP output after resume
** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083022 Title: [SRU] Fix AST DP output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2083022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
** Description changed: - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd + Description: Ubuntu 22.04.4 LTS + Release: 22.04 + $ ubuntu-report show | grep DCD + "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" + 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center + $ apt-cache policy ubuntu-drivers-common + ubuntu-drivers-common: + Installed: 1:0.9.6.2~0.22.04.6 + Candidate: 1:0.9.6.2~0.22.04.7 + Version table: + 1:0.9.6.2~0.22.04.7 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages + *** 1:0.9.6.2~0.22.04.6 100 + 100 /var/lib/dpkg/status + 1:0.9.6.1 500 + 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages + 3) What you expected to happen + unattended-upgrades won't break the system. + 4) What happened instead + unattended-upgrades upgraded the NVIDIA packages and the general HWE kernel that retired the OEM kernel in the background. + After the system reboot, the screen keeps black because it boots the OEM kernel and the OEM kernel is still using the old nvidia prebuilt kernel module that is not met to the NVIDIA packages. + + We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the + system booting from deprecated OEM kernels. ** Tags added: originate-from-2077856 sutton ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083657] [NEW] Remove oem-flavour.cfg for the OEM kernel retirement
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
3) What you expected to happen
4) What happened instead
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: High
Assignee: Shih-Yuan Lee (fourdollars)
Status: In Progress
** Affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: High
Assignee: Shih-Yuan Lee (fourdollars)
Status: In Progress
** Tags: oem-priority
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083657
Title:
Remove oem-flavour.cfg for the OEM kernel retirement
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2083657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042097] Re: [MIR][jammy] oem-somerville-magmar-meta
I have uploaded the package into https://launchpad.net/ubuntu/jammy/+queue. ** Changed in: ubuntu Status: New => In Progress ** Tags removed: oem-needs-upload ** Tags added: oem-done-upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042097 Title: [MIR][jammy] oem-somerville-magmar-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083435] Re: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
After rechecking https://git.launchpad.net/ubuntu/+source/apparmor/tree/debian/patches/ubuntu Alex Murray found that this second patch in comment #4 was already applied in the last upload of the apparmor package, so we don't have to apply the patch again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083435 Title: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083435] Re: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
While we're at it, John Johansen also decided to include this patch, which fixes a critical bug in which the rule priority directives could destroy permissions for some classes. ** Patch added: "Patch for commit 204c0c5a3a34ac2eb47b863aae20bace48e0ad3c downloaded from Gitlab" https://bugs.launchpad.net/apparmor/+bug/2083435/+attachment/5823987/+files/204c0c5a3a34ac2eb47b863aae20bace48e0ad3c.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083435 Title: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083435] Re: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
** Patch added: "Patch of commit c86c87e8868c72e5ab2084b5bf783cd5ca800a9b downloaded from GitLab" https://bugs.launchpad.net/apparmor/+bug/2083435/+attachment/5823945/+files/c86c87e8868c72e5ab2084b5bf783cd5ca800a9b.patch ** Description changed: Commit 3c825eb001d33bb6f2480c4f78df03aee4c40396 in the Gitlab upstream adds a field called `execpath` to the `aa_log_record` struct. This field was added in the middle of the struct instead of the end, causing an ABI break in libapparmor without a corresponding major version number bump. This commit landed between v4.0.3 and v4.1.0-beta1, and unfortunately, Oracular currently packages v4.1.0-beta1. - Thus, we need to land a patch to move the `execpath` field to the end of - the struct ASAP to prevent an ABI break from making it into the Oracular - release. The patch is attached below and is available as commit + Thus, we need to land a bugfix patch to move the `execpath` field to the + end of the struct ASAP to prevent an ABI break from making it into the + Oracular release. The patch is attached below and is available as commit c86c87e8868c72e5ab2084b5bf783cd5ca800a9b in the Gitlab repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083435 Title: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083435] Re: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
Gitlab MR has been merged, with commit c86c87e8868c72e5ab2084b5bf783cd5ca800a9b fixing the ABI break. Patch is attached. ** Description changed: Commit 3c825eb001d33bb6f2480c4f78df03aee4c40396 in the Gitlab upstream adds a field called `execpath` to the `aa_log_record` struct. This field was added in the middle of the struct instead of the end, causing an ABI break in libapparmor without a corresponding major version number bump. This commit landed between v4.0.3 and v4.1.0-beta1, and unfortunately, Oracular currently packages v4.1.0-beta1. Thus, we need to land a patch to move the `execpath` field to the end of the struct ASAP to prevent an ABI break from making it into the Oracular - release. The patch will be attached below [once available] and will be - available as commit [SHA to be filled in once patch is merged upstream]. + release. The patch is attached below and is available as commit + c86c87e8868c72e5ab2084b5bf783cd5ca800a9b in the Gitlab repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083435 Title: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083435] Re: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record
** Tags added: oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083435 Title: AppArmor 4.1.0-beta1 contains an ABI break for aa_log_record To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2083435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083129] Re: netplan static IP address assignment use NetworkManager as renderer would be lost static ip
In the lost static ip loop, the OS log show the relevance errors as following. The netplan did not generate configuration file for some network port before NetworkManager reading them. -->> Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8536] settings: Loaded settings plugin: keyfile (internal) Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8536] ifupdown: management mode: unmanaged Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8538] ifupdown: interfaces file /etc/network/interfaces doesn't exist Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens5f1np1.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens5f0np0.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens4f1np1.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens4f0np0.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens3f1np1.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8548] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens3f0np0.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8549] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens2f1np1.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8549] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens2f0np0.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8549] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens1f1np1.nmconnection": failed to load connection: cannot access file: No such file or directory Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: [1725530140.8549] keyfile: load: "/run/NetworkManager/system-connections/netplan-ens1f0np0.nmconnection": failed to load connection: cannot access file: No such file or directory <<-- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083129] Re: netplan static IP address assignment use NetworkManager as renderer would be lost static ip
sosreport file that includes at least one failed information of NetworkManger find netplan generated configs for NIC ports. ** Attachment added: "sosreport file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+attachment/5822937/+files/ose-5518-sosreport-syslog.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083129] [NEW] netplan static IP address assignment use NetworkManager as renderer would be lost static ip
Public bug reported: On Ubuntu 22.04.4, to configure a system to use static address assignment, create a netplan configuration in the file, like /etc/netplan/00-installer-config.yaml. After assigning the network configuration abstraction renderer to NetworkManager not networkd in /etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the NIC interface lost their static ip in some reboot cycles when the rendered is NetworkManager, but networkd as a renderer is works well, all NIC interfaces can get their corresponding IP that configured in netplan confile file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - To configure a system to use static address assignment, create a netplan configuration in the file, like + On Ubuntu 22.04.4, to configure a system to use static address assignment, create a netplan configuration in the file, like /etc/netplan/00-installer-config.yaml. After assigning the network configuration abstraction renderer to NetworkManager not networkd in /etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the NIC interface lost their static ip in some reboot cycles when the rendered is NetworkManager, but networkd as a renderer is works well, all NIC interfaces can get their corresponding IP that configured in netplan confile file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2083129] Re: netplan static IP address assignment use NetworkManager as renderer would be lost static ip
This is the netplan configuration file that we applied, the renderer item be pointed as NetWorkManager ** Attachment added: "netplan config file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+attachment/5822933/+files/00-installer-config.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: netplan static IP address assignment use NetworkManager as renderer would be lost static ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2083129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036954] Re: Cannot turn Bluetooth on in Ubuntu 22.04.03 LTS
The problem was solved after the kernel was updated. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036954 Title: Cannot turn Bluetooth on in Ubuntu 22.04.03 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2082868] [NEW] [g1200] regulators not enabled after sru d2024.08.12
Public bug reported: [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 ** Affects: linux-mtk (Ubuntu) Importance: Critical Assignee: Jian Hui Lee (jianhuilee) Status: In Progress ** Affects: linux-mtk (Ubuntu Jammy) Importance: Critical Assignee: Jian Hui Lee (jianhuilee) Status: In Progress ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-mtk (Ubuntu) Status: New => In Progress ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux-mtk (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2082868 Title: [g1200] regulators not enabled after sru d2024.08.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2082868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
Hi, Ubuntu Since our UEFI is keeping updating, so we'll test it base our new UEFI version and then post our test results here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2061373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"
@Jeff OK, got it. We will base your comments and share it to our mutual customers! Thanks！ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060924 Title: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2060924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070339] Re: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95"
Sorry for pushing you again. We updated to the proposed 6.10 kernel 6.10.0-15-generic on 24.10, the spi-nor error has gone. so I was just wondering will you backport that patches to the 24.04 kernels? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070339 Title: [Lenovo Ubuntu 24.04 Bug] dmesg show "spi-nor: probe of spi0.0 failed with error -95" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073571] Re: [Lenovo Ubuntu 24.04 Bug] lpfc driver reports failure message
@Jeff Base on your pervious comment, you mentioned Ubuntu would update a new version that has less information of SAN activity. I was just wondering how is the status? Thanks, --Xiaochun -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073571 Title: [Lenovo Ubuntu 24.04 Bug] lpfc driver reports failure message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081699] [NEW] [g700] support p1v4 hardware
Public bug reported: [Impact] the latest g700 hardware p1v4 is with a different dsi panel. [Fix] the panel is upgraded to startek-kd070fhfid078 from startek-kd070fhfid015. [Test] check the content on the dsi panel on p1v3 and p1v4. [Where problems could occur] since the device tree needs to be modified, we have to consider the compatibility issue to make sure there is no regression on p1v3 hardware. LP: #2077953 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Description changed: [Impact] the latest g700 hardware p1v4 is with a different dsi panel. [Fix] - the panel is upgraded to startek-kd070fhfid078 from startek-kd070fhfid015. + the panel is upgraded to startek-kd070fhfid078 from startek-kd070fhfid015. [Test] - check the content on the dsi panel on p1v3 and p1v4. + check the content on the dsi panel on p1v3 and p1v4. [Where problems could occur] since the device tree needs to be modified, we have to consider the compatibility issue to make sure there is no regression on p1v3 hardware. + + LP: #2077953 ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081699 Title: [g700] support p1v4 hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081696] [NEW] [g1200] Call trace appeared when reload mtk_rng module
Public bug reported: [Impact] call trace after unloading mtk_rng module [Fix] https://patchwork.linuxtv.org/project/linux-media/patch/20230515141610.v2.1.I0d1657be3fea5870f797e975a7aa490291e17993@changeid/#147177 [Test] 1. modprobe -r mtk_rng 2. modprobe mtk_rng [Where problems could occur] none. the chance should be low. LP: #2072842 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Description changed: [Impact] call trace after unloading mtk_rng module [Fix] https://patchwork.linuxtv.org/project/linux-media/patch/20230515141610.v2.1.I0d1657be3fea5870f797e975a7aa490291e17993@changeid/#147177 - [Test] 1. modprobe -r mtk_rng 2. modprobe mtk_rng [Where problems could occur] none. the chance should be low. + + LP: #2072842 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081696 Title: [g1200] Call trace appeared when reload mtk_rng module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081686] [NEW] [g1200] possible kernel memory leak through CONFIG_DEBUG_KMEMLEAK
Public bug reported:
[Impact]
After enable CONFIG_DEBUG_KMEMLEAK, Kmemleak detects potential leak.
root@mtk-genio:/home/gjiang# cat /sys/kernel/debug/kmemleak
unreferenced object 0xdad64400 (size 512):
comm "kworker/u16:3", pid 146, jiffies 4294896229 (age 8550.412s)
hex dump (first 32 bytes):
00 40 19 03 00 fc ff ff 00 00 00 00 00 00 10 00 .@..
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
backtrace:
[<ce19c3ae>] __kmalloc+0x260/0x410
[<a3612fef>] sg_alloc_append_table_from_pages+0x324/0x490
[<58fcc8b7>] sg_alloc_table_from_pages_segment+0x3c/0x114
[<a37ae8d3>] iommu_dma_get_sgtable+0xa4/0x110
[<2c697e39>] dma_get_sgtable_attrs+0x28/0x50
[<0872c5af>] mtk_gem_prime_get_sg_table+0x64/0xc0
[<6b9e7591>] mtk_drm_gem_prime_vmap+0x60/0x130
[<b73a0770>] drm_gem_vmap+0x2c/0x90
[<34e08004>] drm_client_buffer_vmap+0x2c/0x4c
[<bff437f7>] drm_fb_helper_generic_probe+0x178/0x230
[<dcd73dff>] drm_fb_helper_single_fb_probe+0x2cc/0x530
[<1980a8a1>] __drm_fb_helper_initial_config_and_unlock+0x48/0x140
[<7b1bea4e>] drm_fbdev_client_hotplug+0x13c/0x18c
[<a7d9a8ba>] drm_client_register+0x64/0xa4
[<106a744f>] drm_fbdev_generic_setup+0xd0/0x19c
[<70423ecc>] mtk_drm_bind+0x11c/0x1a0
[Fix]
https://lore.kernel.org/lkml/68a9a139-922b-93ae-0f4d-ee36b3610...@loongson.cn/T/
https://lore.kernel.org/linux-arm-kernel/20231004083226.1940055-1-we...@chromium.org/
[Test]
1. enable CONFIG_DEBUG_KMEMLEAK
2. cat /sys/kernel/debug/kmemleak
[Where problems could occur]
none. the chance should be low.
LP: #2073823
** Affects: linux-mtk (Ubuntu)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: New
** Affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: New
** Also affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-mtk (Ubuntu)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
** Changed in: linux-mtk (Ubuntu Jammy)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081686
Title:
[g1200] possible kernel memory leak through CONFIG_DEBUG_KMEMLEAK
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081686/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081272] Re: Dell Camera does not work
Dell XPS 13 9320 is not cerified on Ubuntu 24.04. Seeing https://ubuntu.com/certified/202112-29802 for details. You can try ppa:oem-solutions-group/intel-ipu6 first. Seeing https://wiki.ubuntu.com/IntelMIPICamera for details. ** Also affects: oem-priority Importance: Undecided Status: New ** No longer affects: oem-priority ** Changed in: oem-somerville-tentacool-meta (Ubuntu) Status: New => Opinion ** Also affects: oem-somerville-tentacool-meta (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: oem-somerville-tentacool-meta (Ubuntu Noble) Status: New => Opinion ** Summary changed: - Dell Camera does not work + Dell XPS 13 9320 - Intel MIPI IPU6 camera does not work ** Summary changed: - Dell XPS 13 9320 - Intel MIPI IPU6 camera does not work + Dell XPS 13 9320 - Intel MIPI IPU6 camera does not work on noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081272 Title: Dell XPS 13 9320 - Intel MIPI IPU6 camera does not work on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oem-somerville-tentacool-meta/+bug/2081272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078878] Re: Missing Bluetooth device IDs for new Mediatek MT7920/MT7925
** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078878 Title: Missing Bluetooth device IDs for new Mediatek MT7920/MT7925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069408] Re: OOBE has a blue background
** Changed in: gnome-initial-setup (Ubuntu) Status: Incomplete => Confirmed ** Also affects: gnome-initial-setup (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-initial-setup (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069408 Title: OOBE has a blue background To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069408] Re: OOBE has a blue background
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069408 Title: OOBE has a blue background To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079947] Re: [g350][sru] ltp: cve-2019-8912 test result is flaky
** Changed in: linux-mtk (Ubuntu) Status: New => Won't Fix ** Changed in: linux-mtk (Ubuntu Jammy) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079947 Title: [g350][sru] ltp: cve-2019-8912 test result is flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2079947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079947] Re: [g350][sru] ltp: cve-2019-8912 test result is flaky
the race window is small and it's hard to trigger a kernel crash but fchownat() will return ENOENT as it should only when the bug is not present. since g350 is less powerful than the other, it may hit the 3min timeout criteria. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079947 Title: [g350][sru] ltp: cve-2019-8912 test result is flaky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2079947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079947] [NEW] [g350][sru] ltp: cve-2019-8912 test result is flaky
Public bug reported:
[Summary]
ubuntu_ltp: cve-2019-8912 fail
[Steps to reproduce]
on the dut:
1. git clone -b sru https://git.launchpad.net/~canonical-kernel-team/+git/ltp
2. sed -i /ntfs/d lib/tst_supported_fs_types.c
3. make autotools
4. ./configure
5. make -j8
6. make install
7. /opt/ltp/testcases/bin/af_alg07
[Expected result]
test should pass
[Actual result]
Running tests...
tst_test.c:1733: TINFO: LTP version: 20230929-607-g8f21ebba4
tst_test.c:1617: TINFO: Timeout per run is 0h 03m 00s
../../../include/tst_fuzzy_sync.h:484: TINFO: Minimum sampling period ended
../../../include/tst_fuzzy_sync.h:307: TINFO: loop = 1024, delay_bias = 0
../../../include/tst_fuzzy_sync.h:295: TINFO: start_a - start_b: { avg =
60ns, avg_dev = 115ns, dev_ratio = 1.92 }
../../../include/tst_fuzzy_sync.h:295: TINFO: end_a - start_a : { avg =
47966ns, avg_dev = 3376ns, dev_ratio = 0.07 }
../../../include/tst_fuzzy_sync.h:295: TINFO: end_b - start_b : { avg =
20322ns, avg_dev = 1366ns, dev_ratio = 0.07 }
../../../include/tst_fuzzy_sync.h:295: TINFO: end_a - end_b: { avg =
27704ns, avg_dev = 2426ns, dev_ratio = 0.09 }
../../../include/tst_fuzzy_sync.h:295: TINFO: spins: { avg = 456077
, avg_dev = 143140 , dev_ratio = 0.31 }
../../../include/tst_fuzzy_sync.h:648: TINFO: Exceeded execution time,
requesting exit
the timeout was set to 3min. the test result is not stable because the
test could pass sometimes.
** Affects: linux-mtk (Ubuntu)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: New
** Affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: New
** Also affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-mtk (Ubuntu)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
** Changed in: linux-mtk (Ubuntu Jammy)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079947
Title:
[g350][sru] ltp: cve-2019-8912 test result is flaky
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2079947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work with v4l2-relayd/v4l2loopback devices
** Tags added: jira-nantou-467 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work with v4l2-relayd/v4l2loopback devices To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076361] Re: Lenovo X12 Detachable Gen 2 unresponsive under light load
** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076361 Title: Lenovo X12 Detachable Gen 2 unresponsive under light load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work with v4l2-relayd/v4l2loopback devices
The symptom looks like https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/707. I agree that we should focus on the major #2 issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work with v4l2-relayd/v4l2loopback devices To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work on Intel MIPI camera
I can also duplicate the second issue by the Virtual Camera created by v4l2-relayd. https://paste.ubuntu.com/p/xvyNRxSxf5/ So the problem is basically between v4l2-relayd/v4l2loopback and pipewire. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work on Intel MIPI camera To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work on Intel MIPI camera
The error is from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpipewire.so belonged to pipewire. https://paste.ubuntu.com/p/jNRQ8zbkHq/ Should we probably report the second issue to https://gitlab.freedesktop.org/pipewire/pipewire/-/issues instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work on Intel MIPI camera To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work on Intel MIPI camera
I reported https://gitlab.gnome.org/GNOME/snapshot/-/issues/223 for my own Logitech QuickCam Notebook Pro. ** Bug watch added: gitlab.gnome.org/GNOME/snapshot/-/issues #223 https://gitlab.gnome.org/GNOME/snapshot/-/issues/223 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work on Intel MIPI camera To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work on Intel MIPI camera
Another webcam device in an old iMac works fine. https://paste.ubuntu.com/p/m3Mm476SVf/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work on Intel MIPI camera To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076315] Re: Snapshot failed to work on mipi camera
After some rough investigations, there are three different issues. The first issue: the v4l2 video device is not listed from `pw-dump`, but I can make it listed after executing `systemctl --user restart pipewire`. So it could be related to some initialization problem within the pipewire infrastructure. The second issue is a stream error that makes it unable to play camera stream. https://paste.ubuntu.com/p/MYPXTs3K39/ The third issue is only observed by my own USB camera device so far that even there is no problem to initial the device on snapshot, but it can not fetch the camera stream to show or to record. I am not sure if we will encounter the third issue after we solved the previous two issues. https://paste.ubuntu.com/p/dcW4f6ykzs/ FYI, https://gitlab.gnome.org/GNOME/snapshot/-/blob/main/TROUBLESHOOTING.md ** Also affects: oem-priority Importance: Undecided Status: New ** Summary changed: - Snapshot failed to work on mipi camera + Snapshot failed to work on Intel MIPI camera ** Changed in: oem-priority Status: New => Confirmed ** Changed in: gnome-snapshot (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076315 Title: Snapshot failed to work on Intel MIPI camera To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078763] [NEW] [uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service loaded failed during cold boot stress test
Public bug reported:
[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
** Affects: linux-mtk (Ubuntu)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: In Progress
** Affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Assignee: Jian Hui Lee (jianhuilee)
Status: In Progress
** Changed in: linux-mtk (Ubuntu)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
** Also affects: linux-mtk (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-mtk (Ubuntu Jammy)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
** Changed in: linux-mtk (Ubuntu)
Status: New => In Progress
** Changed in: linux-mtk (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078763
Title:
[uc22][g700] systemd-backlight@backlight:1c008000.dsi0.0.service
loaded failed during cold boot stress test
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078763/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078762] [NEW] [g510][g700] add fsource device tree node
Public bug reported: [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. ** Affects: linux-mtk (Ubuntu) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078762 Title: [g510][g700] add fsource device tree node To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2078762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
