[Kernel-packages] [Bug 2020295] [NEW] Include the MAC address pass through function on RTL8153DD-CG
Public bug reported:
[Impact]
[Fix]
Commit in v6.3-rc1 fixes the issue.
ec51fbd1b8a2 r8152: add USB device driver for config selection
[Test]
[Where problems could occur]
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: Fix Released
** Affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Kinetic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: Fix Released
** Affects: linux-oem-6.1 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Tags: oem-priority originate-from-1974429 somerville
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Tags added: oem-priority originate-from-1974429 somerville
** Description changed:
[Impact]
[Fix]
+ Commit in v6.3-rc1 fixes the issue.
+ ec51fbd1b8a2 r8152: add USB device driver for config selection
[Test]
[Where problems could occur]
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2020295
Title:
Include the MAC address pass through function on RTL8153DD-CG
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
[Fix]
Commit in v6.3-rc1 fixes the issue.
ec51fbd1b8a2 r8152: add USB device driver for config selection
[Test]
[Where problems could occur]
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020295/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020062] [NEW] No HDMI/DP audio output on dock(Nvidia GPU)
Public bug reported:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.0 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.0 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.1 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.0 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.1 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Tags: oem-priority originate-from-2018485 somerville
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-6.0 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu Mantic)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: New => Invalid
** Description changed:
[Impact]
+ When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
+ Nvidia provides a patch to fix it
+
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
[Test]
+ Verified on the target machine.
{Where problems could occur]
+ The patch just adds IDs, and won't lead to any regression.
** Tags added: oem-priority originate-from-2018485 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Inva
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
Verified with 6.1.0-1012-oem ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Mantic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008157 Title: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002842] Re: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32
*** This bug is a duplicate of bug 2008157 *** https://bugs.launchpad.net/bugs/2008157 ** This bug has been marked a duplicate of bug 2008157 [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002842 Title: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: I'm getting UBSAN complains every boot, this issue exists for years, but I was lazy to report it as everything works. However, not sure if it is security issue: [1.866789] [1.866992] [1.867187] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 [1.867454] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [1.867608] CPU: 0 PID: 203 Comm: kworker/0:1H Tainted: G I 5.15.0-58-generic #64-Ubuntu [1.867612] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4/X299 UD4-CF, BIOS F6p 12/06/2021 [1.867614] Workqueue: kblockd blk_mq_run_work_fn [1.867620] Call Trace: [1.867621] [1.867623] show_stack+0x52/0x5c [1.867628] dump_stack_lvl+0x4a/0x63 [1.867635] dump_stack+0x10/0x16 [1.867641] ubsan_epilogue+0x9/0x49 [1.867647] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.867653] ? _printk+0x58/0x73 [1.867658] MR_GetPhyParams+0x487/0x700 [megaraid_sas] [1.867675] MR_BuildRaidContext+0x402/0xb50 [megaraid_sas] [1.867693] megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] [1.867710] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] [1.867725] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] [1.867739] megasas_queue_command+0x1be/0x200 [megaraid_sas] [1.867753] ? ktime_get+0x43/0xc0 [1.867759] scsi_dispatch_cmd+0x93/0x200 [1.867764] scsi_queue_rq+0x2d5/0x690 [1.867771] blk_mq_dispatch_rq_list+0x13c/0x680 [1.867779] ? sbitmap_get+0x1/0xe0 [1.867786] __blk_mq_do_dispatch_sched+0xba/0x2e0 [1.867792] blk_mq_do_dispatch_sched+0x40/0x70 [1.867797] __blk_mq_sched_dispatch_requests+0x105/0x150 [1.867802] blk_mq_sched_dispatch_requests+0x35/0x70 [1.867806] __blk_mq_run_hw_queue+0x34/0xc0 [1.867812] blk_mq_run_work_fn+0x1f/0x30 [1.867818] process_one_work+0x228/0x3d0 [1.867823] worker_thread+0x53/0x420 [1.867826] ? process_one_work+0x3d0/0x3d0 [1.867830] kthread+0x127/0x150 [1.867836] ? set_kthread_struct+0x50/0x50 [1.867843] ret_from_fork+0x1f/0x30 [1.867852] [1.867853] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: vsukhoml 2725 F pulseaudio /dev/snd/controlC0: vsukhoml 2725 F pulseaudio /dev/snd/controlC1: vsukhoml 2725 F pulseaudio /dev/snd/controlC2: vsukhoml 2725 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jan 13 11:12:10 2023 InstallationDate: Installed on 2020-05-03 (985 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X299 UD4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=UUID=9f617cba-f115-4ee3-ad8e-de95fcd2ca03 ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-15 (182 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6p dmi.board.asset.tag: Default string dmi.board.name: X299 UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmerican
[Kernel-packages] [Bug 2017774] Re: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
The issue has been fix in 6.0.0-1016.16 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. [Fix] The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded Below commits are all from v6.1-rc1 fb1836c91317 ACPI: video: Prefer native over vendor a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper [Test] Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018566] [NEW] A deadlock issue in scsi rescan task while resuming from S3
Public bug reported: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1999593 somerville ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Tags added: oem-priority originate-from-1999593 somerville ** Summary changed: - A race condiction issue in scsi rescan task while resuming from S3 + A deadlock issue in scsi rescan task while resuming from S3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/2023
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which were in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ In v6.3-rc1 4c0eb35fc103 drm/i915: Improve PPS debugs ed5509d1d451 drm/i915: Fix whitespace 1e47e035bb73 drm/i915: Print the PPS registers using consistent format ba21bb24810f drm/i915: Reject unusable power sequencers d83804f22d85 drm/i915: Extend dual PPS handlind for ICP+ bf38bba3e7d6 drm/i915: Try to use the correct power sequencer intiially on bxt/glk 209074fd5a82 drm/i915: Generalize the PPS vlv_pipe_check() stuff 3f9ffce5765d drm/i915: Do panel VBT init early if the VBT declares an explicit panel type f70f8153e364 drm/i915: Introduce intel_panel_init_alloc() [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Description changed: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] - The series of patches which are in drp-tip fix the isue + The series of patches which were in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ + + In v6.3-rc1 + 4c0eb35fc103 drm/i915: Improve PPS debugs + ed5509d1d451 drm/i915: Fix whitespace + 1e47e035bb73 drm/i915: Print the PPS registers using consistent format + ba21bb24810f drm/i915: Reject unusable power sequencers + d83804f22d85 drm/i915: Extend dual PPS handlind for ICP+ + bf38bba3e7d6 drm/i915: Try to use the correct power sequencer intiially on bxt/glk + 209074fd5a82 drm/i915: Generalize the PPS vlv_pipe_check() stuff + 3f9ffce5765d drm/i915: Do panel VBT init early if the VBT declares an explicit panel type + f70f8153e364 drm/i915: Introduce intel_panel_init_alloc() [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which were in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ In v6.3-rc1 4c0eb35fc103 drm/i915: Improve PPS debugs ed5509d1d451 drm/i915: Fix whitespace 1e47e035bb73 drm/i915: Print the PPS registers using consistent format ba21bb24810f drm/i915: Reject unusable power sequencers d83804f22d85 drm/i915: Extend dual PPS handlind for ICP+ bf38bba3e7d6 drm/i915: Try to use the correct power sequencer intiially on bxt/glk 209074fd5a82 drm/i915: Generalize the PPS vlv_pipe_check() stuff 3f9ffce5765d drm/i915: Do panel VBT init early if the VBT declares an explicit panel type f70f8153e364 drm/i915: Introduce intel_panel_init_alloc() [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017774] Re: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
** Description changed: [Impact] + When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. + [Fix] + The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded + + Below commits are all from v6.1-rc1 + fb1836c91317 ACPI: video: Prefer native over vendor + a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true + b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit + a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() + 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper + [Test] + Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] + All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] When switched to discrete mode in the BIOS, nvidia driver will create its own backlight interface(nvidia_0) to control the backlight, but at the same time dell-laptop creates its own backlight interface(dell_backlight), too. In discrete mode, dell_backlight interface doesn't work, and it leads to gnome chooses the wrong interface(dell_backlight) to control the backlight and then leads to the issue. [Fix] The acpi_video_backlight_use_native() helper function is introduced after v6.1 and nvidia driver will call this function if kernel provides it. This helper tells video_detect module that nvidia controls the backlight, so that dell-laptop won't create another backlight interface when it's loaded Below commits are all from v6.1-rc1 fb1836c91317 ACPI: video: Prefer native over vendor a5df42521f32 ACPI: video: Simplify __acpi_video_get_backlight_type()454d61a56d5e ACPI: video: Make acpi_video_backlight_use_native() always return true b39be9f441f9 ACPI: video: Refactor acpi_video_get_backlight_type() a bit a2fc3c899bb0 ACPI: video: Drop backlight_device_get_by_type() call from acpi_video_get_backlight_type() 2600bfa3df99 ACPI: video: Add acpi_video_backlight_use_native() helper [Test] Verified on the target machine and confirmed dell_backlight interface is not generated. [Where problem could occur] All changes are in __acpi_video_get_backlight_type() function and to make it smarter to decide which type of backlight interface should be created. The final result is pretty similar to the latest mainline version, if it introduce any regression we can add quirk to list those misjudged machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017774] [NEW] both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness
Public bug reported: [Impact] [Fix] [Test] [Where problem could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-2013207 somerville ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-2013207 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2017774 Title: both dell_backlight and nvidia_0 backlight interface appear, and can't adjust the display brightness Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] [Fix] [Test] [Where problem could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2017774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Downgraded bluez from 5.64-0ubuntu1 to 5.53-0ubuntu3.6
2. forgot the bt device on my phone and power cycle the machine
ii bluez 5.53-0ubuntu3.6
amd64Bluetooth tools and daemons
Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17
17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
3. Ran setup again, and then ran demo, the move command still works, I
can see cursor move.
BTW, the commit Dilyn found shoule not be relavent, I see the same warning
message with 5.15 kernel + 5.64 bluez
09572fca7223 Bluetooth: hci_sock: Add support for BT_{SND,RCV}BUF
2023-03-31T05:00:02.985301Z WARN ble::sys::mgmt: Failed to set
BT_SNDMTU: Protocol not available (os error 92)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2006517
Title:
Bluetooth works on desktop but not on ubuntu core
Status in bluez package in Ubuntu:
Confirmed
Bug description:
We have built a snap that uses some bluetooth functionality.
The snap runs well when using Ubuntu desktop 22.04 (all updates applied end
of Jan 2022).
We have tried using this same snap on Ubuntu Core 22 running on X86_64.
On some hardware platforms (thinkpad E15 and x86 Mac) everything works as
expected.
We can install the snap on Jammy 22.04 or Core 22 on these platforms and get
expected functionality regardless of OS.
On our targeted platform (a Dell 5570) things are not working. When running
22.04 Jammy, everything works. When running Core 22, some advanced bluetooth
functionality is not available.
Since the Core 22 image installs and runs on other X86_64 hardware we suspect
a device driver issue.
Attached are several files taken from the Dell 5570
1) dmesg from Core 22.
2) dmesg from Jammy 22.04
3) output of lspci from Jammy 22.04
4) Output of lsusb from Jammy 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Fresh installed ubuntu-22.04.2-desktop 2. Installed 5.15 kernel ii bluez 5.64-0ubuntu1 amd64Bluetooth tools and daemons Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux 3. Installed customer's 2 snaps and run the setup and connect the bt device from my phone 4. The move command works, I can see cursor on my phone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine
The patch doesn't work. ** Changed in: hwe-next Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008860 Title: The external monitor is blank if plug in the dock cable to power up the machine Status in HWE Next: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Invalid Bug description: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] Actually, there is no functional changes with default RR sched policy, but it accidentially fixes the blank screen issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
The BT adv feature 1. works with 5.15 + bluez (20/stable) 5.53-7 2. doesn't work with 5.15 + bluez (22/beta) 5.64-3 3. (from Dilyn and Wendell) works with 5.19 + bluez (22/beta) It's still unclear why bluez requires specific version of kernel. Do we have a bluez expert to consult what kind of features the 5.15 kernel are missing? Or could our customer stick with bluez (20/stable)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
From Dilyn's steps, he install the beta version of the bluez, and here is what I found. 1. power cycle the machine 2. install beta bluez, the advinfo doesn't work acelankao@ubuntu:~$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ snap install --channel=22/beta bluez bluez (22/beta) 5.64-3 from Canonical✓ installed acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Reading adv features failed with status 0x0c (Not Supported) 1. removed the beta bluez, and install stable bluez acelankao@ubuntu:~$ sudo snap remove bluez bluez removed acelankao@ubuntu:~$ sudo snap install bluez bluez (20/stable) 5.53-7 from Canonical✓ installed 2. power cycle the machine, and then advinfo works acelankao@ubuntu:~$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes bluez 5.53-7 33420/stable canonical✓ - checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Supported flags: connectable general-discoverable limited-discoverable managed-flags tx-power scan-rsp-appearance scan-rsp-local-name Secondary-channel-1M Secondary-channel-2M Secondary-channel-CODED Max advertising data len: 31 Max scan response data len: 31 Max instances: 8 Instances list with 0 items BTW, the BT firmware is intel/ibt-0040-0041.sfi [ 15.452255] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 15.452260] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 15.453014] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi [ 16.965744] Bluetooth: hci0: Waiting for firmware download to complete [ 16.966269] Bluetooth: hci0: Firmware loaded in 1477780 usecs [ 16.966446] Bluetooth: hci0: Waiting for device to boot [ 16.985279] Bluetooth: hci0: Device booted in 18524 usecs [ 16.987502] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc [ 16.990290] Bluetooth: hci0: Applying Intel DDC parameters completed [ 16.994174] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Tried many different ways to recover the status(advinfo should work), but in vain, so I removed customer's snaps, removed the beta bluez, installed the stable bluez and then power cycle the machine. The advinfo works again. acelankao@ubuntu:~$ snap list NameVersion RevTracking PublisherNotes bluez 5.53-7 33420/stable canonical✓ - checkbox20 2.1 1152 latest/stable ce-certification-qa - core16-2.58.3 14946 latest/stable canonical✓ core core20 202303081852 latest/stable canonical✓ base core22 20230304547latest/stable canonical✓ base pc 22-0.3 12722/stable canonical✓ gadget pc-kernel 5.15.0-66.73.1 x1 - -kernel snapd 2.5918745 latest/betacanonical✓ snapd toolbox 0.8.4 2811 20/stable ondra- acelankao@ubuntu:~$ snap connections bluez Interface Plug Slot Notes bluetooth-control bluez:bluetooth-control - - bluez bluez:client bluez:service - home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control- - uhid bluez:uhid :uhid - uinput bluez:uinput - - acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Unable to open mgmt_socket acelankao@ubuntu:~$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo bluez.btmgmt advinfo Supported flags: connectable general-discoverable limited-discoverable managed-flags tx-power scan-rsp-appearance scan-rsp-local-name Secondary-channel-1M Secondary-channel-2M Secondary-channel-CODED Max advertising data len: 31 Max scan response data len: 31 Max instances: 8 Instances list with 0 items -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
** Attachment added: "lsusb_vvv.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656717/+files/lsusb_vvv.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
acelankao@ubuntu:~/bci-snaps$ snap connections bluez Interface PlugSlot Notes bluetooth-control bluez:bluetooth-control - - bluez blackrock-bci-moveagain:bluez bluez:service manual bluez bluez:clientbluez:service - dbus blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez manual home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control - - uhid bluez:uhid :uhid - uinput bluez:uinput- - acelankao@ubuntu:~/bci-snaps$ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~/bci-snaps$ snap connections bluez Interface PlugSlotNotes bluetooth-control bluez:bluetooth-control :bluetooth-control manual bluez blackrock-bci-moveagain:bluez bluez:service manual bluez bluez:clientbluez:service - dbus blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez manual home bluez:home - - kernel-crypto-api bluez:kernel-crypto-api - - network-controlbluez:network-control - - uhid bluez:uhid :uhid - uinput bluez:uinput- - acelankao@ubuntu:~/bci-snaps$ sudo blackrock-bci-moveagain.bledemo Error: NotSupported acelankao@ubuntu:~/bci-snaps$ sudo bluez.btmgmt advinfo Reading adv features failed with status 0x0c (Not Supported) ** Attachment added: "lspci_nnvvk.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656716/+files/lspci_nnvvk.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
I followed the steps Dilyn provides, and the bt adv feature is gone, even if I connected the bluez:bluetooth-control manually. acelankao@ubuntu:~/bci-snaps$ uname -a Linux ubuntu 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux acelankao@ubuntu:~/bci-snaps$ snap install --dangerous blackrock-bci-libtorch.snap blackrock-bci-libtorch 1.11.0-cuda113 installed acelankao@ubuntu:~/bci-snaps$ snap install --dangerous blackrock-bci-moveagain.snap blackrock-bci-moveagain 0+git.3f19fe7 installed acelankao@ubuntu:~/bci-snaps$ snap install --channel=22/beta bluez bluez (22/beta) 5.64-3 from Canonical✓ installed acelankao@ubuntu:~/bci-snaps$ /snap/blackrock-bci-moveagain/current/bin/setup.sh Warning: Failed to connect 'bluez'. Please connect manually, available providers are: - bluez:service Added: - blackrock-bci-moveagain as moveagain acelankao@ubuntu:~/bci-snaps$ snap connect blackrock-bci-moveagain:bluez bluez:service acelankao@ubuntu:~/bci-snaps$ snap connect blackrock-bci-moveagain:dbus-bluez bluez:dbus-bluez acelankao@ubuntu:~/bci-snaps$ sudo blackrock-bci-moveagain.bledemo Error: NotSupported ** Attachment added: "pc-kernel.info.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+attachment/5656715/+files/pc-kernel.info.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Should work well now acelankao@ubuntu:~$ sudo bluez.btmgmt [mgmt]# info Index list with 1 item hci0: Primary controller addr 60:E3:2B:67:3E:CC version 12 manufacturer 2 class 0x10010c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr current settings: powered ssp br/edr le advertising secure-conn name BlueZ 5.53 short name hci0: Configuration options supported options: public-address missing options: hci0 type 7 discovering off [mgmt]# advinfo Supported flags: connectable general-discoverable limited-discoverable managed-flags tx-power scan-rsp-appearance scan-rsp-local-name Secondary-channel-1M Secondary-channel-2M Secondary-channel-CODED Max advertising data len: 31 Max scan response data len: 31 Max instances: 8 Instances list with 0 items [mgmt]# power on hci0 Set Powered complete, settings: powered ssp br/edr le advertising secure-conn [mgmt]# find Discovery started hci0 type 7 discovering on hci0 dev_found: 24:5A:4C:13:CF:27 type LE Public rssi -68 flags 0x0004 AD flags 0x00 name U6-LITE hci0 dev_found: 00:91:9E:32:09:5F type BR/EDR rssi -57 flags 0x0001 eir_len 5 confirm_name succeeded for 00:91:9E:32:09:5F hci0 dev_found: 60:E3:2B:81:A4:15 type BR/EDR rssi -68 flags 0x name u-HP-EliteBook-830-13-inch-G10-Notebook-PC hci0 dev_found: 7A:FC:87:61:33:B9 type LE Random rssi -63 flags 0x AD flags 0x1a eir_len 19 hci0 dev_found: 00:91:9E:32:09:5F type BR/EDR rssi -59 flags 0x name u-HP-Elite-x360-830-13-inch-G10-2-in-1-Notebook- hci0 dev_found: FC:F6:E0:56:87:8D type LE Random rssi -62 flags 0x0004 AD flags 0x00 eir_len 8 hci0 dev_found: 34:6F:24:A8:93:EE type LE Public rssi -70 flags 0x AD flags 0x1a eir_len 21 hci0 dev_found: 94:53:30:A9:DA:A4 type BR/EDR rssi -72 flags 0x name ubuntu-Vostro-5581 hci0 dev_found: 4C:80:93:CC:AC:21 type BR/EDR rssi -67 flags 0x0001 eir_len 5 confirm_name succeeded for 4C:80:93:CC:AC:21 hci0 dev_found: 4C:80:93:CC:AC:21 type BR/EDR rssi -59 flags 0x name u hci0 dev_found: 01:AA:A3:26:D9:92 type LE Random rssi -61 flags 0x0004 AD flags 0x00 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
>From Jesse, the interface is not connected, could you try below connect command and try your app again? $ sudo snap connect bluez:bluetooth-control acelankao@ubuntu:~$ sudo btmgmt version Version 5.53 acelankao@ubuntu:~$ sudo btmgmt revision Invalid command in menu main: revision Use "help" for a list of available commands in a menu. Use "menu " if you want to enter any submenu. Use "back" if you want to return to menu main. acelankao@ubuntu:~$ sudo btmgmt monitor.features Invalid command in menu main: monitor Use "help" for a list of available commands in a menu. Use "menu " if you want to enter any submenu. Use "back" if you want to return to menu main. acelankao@ubuntu:~$ sudo btmon --mgmt sudo: btmon: command not found acelankao@ubuntu:~$ sudo bluez.btmon --mgmt /snap/bluez/334/usr/bin/btmon: unrecognized option '--mgmt' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002842] Re: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32
Here is the test kernel and the patches applied on top of 5.15.0-68 https://people.canonical.com/~acelan/bugs/lp2002842/ I'll find a machine to verify it later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002842 Title: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: I'm getting UBSAN complains every boot, this issue exists for years, but I was lazy to report it as everything works. However, not sure if it is security issue: [1.866789] [1.866992] [1.867187] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 [1.867454] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [1.867608] CPU: 0 PID: 203 Comm: kworker/0:1H Tainted: G I 5.15.0-58-generic #64-Ubuntu [1.867612] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4/X299 UD4-CF, BIOS F6p 12/06/2021 [1.867614] Workqueue: kblockd blk_mq_run_work_fn [1.867620] Call Trace: [1.867621] [1.867623] show_stack+0x52/0x5c [1.867628] dump_stack_lvl+0x4a/0x63 [1.867635] dump_stack+0x10/0x16 [1.867641] ubsan_epilogue+0x9/0x49 [1.867647] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.867653] ? _printk+0x58/0x73 [1.867658] MR_GetPhyParams+0x487/0x700 [megaraid_sas] [1.867675] MR_BuildRaidContext+0x402/0xb50 [megaraid_sas] [1.867693] megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] [1.867710] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] [1.867725] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] [1.867739] megasas_queue_command+0x1be/0x200 [megaraid_sas] [1.867753] ? ktime_get+0x43/0xc0 [1.867759] scsi_dispatch_cmd+0x93/0x200 [1.867764] scsi_queue_rq+0x2d5/0x690 [1.867771] blk_mq_dispatch_rq_list+0x13c/0x680 [1.867779] ? sbitmap_get+0x1/0xe0 [1.867786] __blk_mq_do_dispatch_sched+0xba/0x2e0 [1.867792] blk_mq_do_dispatch_sched+0x40/0x70 [1.867797] __blk_mq_sched_dispatch_requests+0x105/0x150 [1.867802] blk_mq_sched_dispatch_requests+0x35/0x70 [1.867806] __blk_mq_run_hw_queue+0x34/0xc0 [1.867812] blk_mq_run_work_fn+0x1f/0x30 [1.867818] process_one_work+0x228/0x3d0 [1.867823] worker_thread+0x53/0x420 [1.867826] ? process_one_work+0x3d0/0x3d0 [1.867830] kthread+0x127/0x150 [1.867836] ? set_kthread_struct+0x50/0x50 [1.867843] ret_from_fork+0x1f/0x30 [1.867852] [1.867853] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: vsukhoml 2725 F pulseaudio /dev/snd/controlC0: vsukhoml 2725 F pulseaudio /dev/snd/controlC1: vsukhoml 2725 F pulseaudio /dev/snd/controlC2: vsukhoml 2725 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jan 13 11:12:10 2023 InstallationDate: Installed on 2020-05-03 (985 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X299 UD4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=UUID=9f617cba-f115-4ee3-ad8e-de95fcd2ca03 ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-15 (182 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6p dmi.board.asset.tag: Default string dmi.board.name: X299 UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6p:bd12/06/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnX299UD4:pvrDefaultstring:rvnGigaby
[Kernel-packages] [Bug 2002842] Re: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1992670 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002842 Title: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: I'm getting UBSAN complains every boot, this issue exists for years, but I was lazy to report it as everything works. However, not sure if it is security issue: [1.866789] [1.866992] [1.867187] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 [1.867454] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [1.867608] CPU: 0 PID: 203 Comm: kworker/0:1H Tainted: G I 5.15.0-58-generic #64-Ubuntu [1.867612] Hardware name: Gigabyte Technology Co., Ltd. X299 UD4/X299 UD4-CF, BIOS F6p 12/06/2021 [1.867614] Workqueue: kblockd blk_mq_run_work_fn [1.867620] Call Trace: [1.867621] [1.867623] show_stack+0x52/0x5c [1.867628] dump_stack_lvl+0x4a/0x63 [1.867635] dump_stack+0x10/0x16 [1.867641] ubsan_epilogue+0x9/0x49 [1.867647] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.867653] ? _printk+0x58/0x73 [1.867658] MR_GetPhyParams+0x487/0x700 [megaraid_sas] [1.867675] MR_BuildRaidContext+0x402/0xb50 [megaraid_sas] [1.867693] megasas_build_ldio_fusion+0x5b9/0x9a0 [megaraid_sas] [1.867710] megasas_build_io_fusion+0x412/0x450 [megaraid_sas] [1.867725] megasas_build_and_issue_cmd_fusion+0xa5/0x380 [megaraid_sas] [1.867739] megasas_queue_command+0x1be/0x200 [megaraid_sas] [1.867753] ? ktime_get+0x43/0xc0 [1.867759] scsi_dispatch_cmd+0x93/0x200 [1.867764] scsi_queue_rq+0x2d5/0x690 [1.867771] blk_mq_dispatch_rq_list+0x13c/0x680 [1.867779] ? sbitmap_get+0x1/0xe0 [1.867786] __blk_mq_do_dispatch_sched+0xba/0x2e0 [1.867792] blk_mq_do_dispatch_sched+0x40/0x70 [1.867797] __blk_mq_sched_dispatch_requests+0x105/0x150 [1.867802] blk_mq_sched_dispatch_requests+0x35/0x70 [1.867806] __blk_mq_run_hw_queue+0x34/0xc0 [1.867812] blk_mq_run_work_fn+0x1f/0x30 [1.867818] process_one_work+0x228/0x3d0 [1.867823] worker_thread+0x53/0x420 [1.867826] ? process_one_work+0x3d0/0x3d0 [1.867830] kthread+0x127/0x150 [1.867836] ? set_kthread_struct+0x50/0x50 [1.867843] ret_from_fork+0x1f/0x30 [1.867852] [1.867853] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: vsukhoml 2725 F pulseaudio /dev/snd/controlC0: vsukhoml 2725 F pulseaudio /dev/snd/controlC1: vsukhoml 2725 F pulseaudio /dev/snd/controlC2: vsukhoml 2725 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jan 13 11:12:10 2023 InstallationDate: Installed on 2020-05-03 (985 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X299 UD4 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=UUID=9f617cba-f115-4ee3-ad8e-de95fcd2ca03 ro quiet splash nomodeset RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-15 (182 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.versio
[Kernel-packages] [Bug 2007530] Re: Built-in camera device dies after runtime suspended
Fixed in BIOS. ** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007530 Title: Built-in camera device dies after runtime suspended Status in HWE Next: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] Add the xHC ID to an existing quirk fixes the issue https://www.spinics.net/lists/kernel/msg4689370.html [Test] Verified by me and QA. [Where problems could occur] It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
Verified the backlight interface is correct with 6.1.0-1008-oem.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
Confirmed there is only one backlight interface amdgpu_bl0 in the system with 6.1.0-1008-oem ** Tags removed: oem-priority originate-from-2007527 somerville verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
** Tags added: oem-priority originate-from-2007527 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
Hi Larry,
You have to wait the new kernel for Lunar, should be available soon.
The OEM kernel is in -proposed(6.1.0-1008.8-oem) now which contains the fix if
you want to try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
** Description changed: [Impact] Sometimes the system boots up with a acpi_backlight0 sysfs interface which doesn't work. The real backlight interface is amdgpu_bl0 which is provided by the amdgpu [Fix] Add this machine to the video_detect_dmi_table [Verify] + Verified by our QA and ODM. [Where problems could occur] + Pretty safe to add the DMI quirk, won't affect other platforms. ** Description changed: [Impact] - Sometimes the system boots up with a acpi_backlight0 sysfs interface which doesn't work. The real backlight interface is amdgpu_bl0 which is provided by the amdgpu + Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] - Add this machine to the video_detect_dmi_table + Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. ** Description changed: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. + https://lkml.org/lkml/2023/3/2/187 + [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
** Description changed:
[Impact]
+ There are acpi_video* sysfs backlight interface in the system which are not
working.
+ For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
+ The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
+ 77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
+ The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
+ I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
+ Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
+ There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] [NEW] Remove all other acpi_video backlight interface on Dell AIO platforms
Public bug reported:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method in
video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which should
do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.1 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Tags: oem-priority originate-from-2003317 somerville
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Tags added: oem-priority originate-from-2003317 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] [NEW] Screen backlight keeps in minimized and can't change it with amdgpu
Public bug reported: [Impact] Sometimes the system boots up with a acpi_backlight0 sysfs interface which doesn't work. The real backlight interface is amdgpu_bl0 which is provided by the amdgpu [Fix] Add this machine to the video_detect_dmi_table [Verify] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with a acpi_backlight0 sysfs interface which doesn't work. The real backlight interface is amdgpu_bl0 which is provided by the amdgpu [Fix] Add this machine to the video_detect_dmi_table [Verify] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine
** Description changed: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] - Actually, there is no functional changes with default RR sched policy, but it accidentialy fixes the blank screen issue. + Actually, there is no functional changes with default RR sched policy, but it accidentially fixes the blank screen issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008860 Title: The external monitor is blank if plug in the dock cable to power up the machine Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] Actually, there is no functional changes with default RR sched policy, but it accidentially fixes the blank screen issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine
** Description changed: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] + Actually, there is no functional changes with default RR sched policy, but it accidentialy fixes the blank screen issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008860 Title: The external monitor is blank if plug in the dock cable to power up the machine Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] Actually, there is no functional changes with default RR sched policy, but it accidentially fixes the blank screen issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine
** Tags added: civet-cat oem-priority originate-from-2000198 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008860 Title: The external monitor is blank if plug in the dock cable to power up the machine Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008860] [NEW] The external monitor is blank if plug in the dock cable to power up the machine
Public bug reported: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Description changed: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] - Verified with the WD22TB + 2 DP monitors. + Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2008860 Title: The external monitor is blank if plug in the dock cable to power up the machine Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] There are one or more monitors connect to the dock and then plug the dock cable to power up the Dell machine, the external monitors keeps blank. [Fix] The issue has been fixed in v6.2-rc1 and the first bad commit is 08fb97de03aa drm/sched: Add FIFO sched policy to run queue [Test] Verified with the WD22TB + 2 4k DP monitors. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2008860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
>From the dmesg logs, the kernel you use on desktop(5.15.0-56) and on core(5.15.0-58) are not the same, but I've checked the kernel logs, there is no update on bt driver part between the 2 kernel versions. It'd be good if you can help me to update the kernel to make sure the kernel versions are identical and check the issue again.(I feel the result won't change) The snap package works on desktop, but not on core, this doesn't look like a kernel/driver issue. Could you provide more info about which function call failed? or provide a simple program that we could try on our side? BTW, the difference between the dmesg logs is that rfcomm is loaded on the desktop, but not on the core system, could you also try to load it on the core system to see if it makes any difference, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007530] Re: Built-in camera device dies after runtime suspended
** Tags added: oem-priority originate-from-2006707 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007530 Title: Built-in camera device dies after runtime suspended Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] Add the xHC ID to an existing quirk fixes the issue https://www.spinics.net/lists/kernel/msg4689370.html [Test] Verified by me and QA. [Where problems could occur] It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007530] Re: Built-in camera device dies after runtime suspended
** Description changed: [Impact] + When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] + Add the xHC ID to an existing quirk fixes the issue + https://www.spinics.net/lists/kernel/msg4689370.html [Test] + Verified by me and QA. [Where problems could occur] + It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007530 Title: Built-in camera device dies after runtime suspended Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When the xHC host controller[1022:1505] is runtime suspended, it can't be waken up and the devices connect to it will be lost. [Fix] Add the xHC ID to an existing quirk fixes the issue https://www.spinics.net/lists/kernel/msg4689370.html [Test] Verified by me and QA. [Where problems could occur] It disables disable a bit which is enable in sparse controller and do reset on resume. The impact should be minimun. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007530] [NEW] Built-in camera device dies after runtime suspended
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007530 Title: Built-in camera device dies after runtime suspended Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
Are you sure the function is lost? Looks like the Adv Monitor is running even the features callback returns an invalid value. Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) Feb 07 23:50:34 ubuntu bluetoothd[1562]: Adv Monitor Manager created with supported features:0x0001, enabled features:0x0001, max number of supported monitors:32, max number of supported patterns:16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
+
+ cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
+ 50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to di
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] + These 3 commits fix the issue + a8671493d207 drm/amdgpu: make sure to init common IP before gmc + e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega + dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega + + == + V1. AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] These 3 commits fix the issue a8671493d207 drm/amdgpu: make sure to init common IP before gmc e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega == V1. AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : ht
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
The fix should contain below 3 commits and confirmed that doesn't introduce
regressions on Dell Inspiron 3585 with AMD GPU.
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
Kinetic(5.19) already contains those commits since 5.19.0-27.28.
BTW, I can reproduce the regression with only applied commit
a8671493d207 ("drm/amdgpu: make sure to init common IP before gmc").
With all the 3 commits, the issue is gone and the display works
normally.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Commit a8671493d207 ("drm/amdgpu: make sure to init common IP before
gmc") intorduce a regression in 5.17-oem kernel and has been reverted
since 5.17.0-1027.28
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
** Description changed: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ - The patch is not finalized, so submit SRU to OEM kernels only, and will - submit to other series kernels once the patch is accepted by upstream. + Included in v6.2-rc1 + d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ Included in v6.2-rc1 d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
SRU submitted, thanks https://lists.ubuntu.com/archives/kernel-team/2023-January/136392.html ** Description changed: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] - Verified by Aaron Ma. + Verified by Aaron Ma and the bug reporter. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] Verified by Aaron Ma and the bug reporter. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
** Description changed: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 + + BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with + this commit, so no need to revert it. [Test] Verified by Aaron Ma. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] Verified by Aaron Ma. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
** Description changed: + [Impact] + The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup + 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc + + [Fix] + Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. + https://gitlab.freedesktop.org/drm/amd/-/issues/2216 + + [Test] + Verified by Aaron Ma. + + [Where problems could occur] + Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. + + + When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 [Test] Verified by Aaron Ma. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
Hi Paul, Aaron has found the bad commit which is 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc I've updated the test kernel at the same location which reverted the commit. https://people.canonical.com/~acelan/bugs/lp2002467/ I'm going to submit SRU to revert this one, please help to verify it, thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
This commit is required for bug 2000110, and I can't figure out any good solution for this. "drm/amdgpu: make sure to init common IP before gmc" introduces regression which could be found here https://gitlab.freedesktop.org/drm/amd/-/issues/2216 and has been reverted from 5.10 stable kernel. Anyway, I'll submit SRU to revert this commit, and try to provide better solution for bug 2000110 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2216 https://gitlab.freedesktop.org/drm/amd/-/issues/2216 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Triaged Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2
** Tags added: originate-from-2002824 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002968 Title: Fix flicker display problem on some panels which support PSR2 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Bug description: [Impact] On some PSR2 supported panels, which connects to Intel Graphics has flicker symptom. It gets normal after booting the kernel with parameter `i915. enable_psr=0` [Fix] Backport one patch from upstream. https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87 [Test] Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if the display has abnormal flickering problem on graphics interfaces. [Where problems could occur] The risk of regression is low. It only fixes problem on panels which support PSR2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Tags added: originate-from-2000192 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
Similar to the issue on upstream
https://gitlab.freedesktop.org/drm/amd/-/issues/2220
Compare what we backported and the kernel versions reported on the
upstream bug, I feel like it's below commit introduce the regression
Could you try this test kernel to see if it helps, it only reverts the below
commit.
https://people.canonical.com/~acelan/bugs/lp2002467/
commit d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
Author: Lijo Lazar
Date: Fri Sep 30 10:43:08 2022 +0530
drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
MMHUB 2.1.x versions don't have ATCL2. Remove accesses to ATCL2 registers.
Since they are non-existing registers, read access will cause a
'Completer Abort' and gets reported when AER is enabled with the below
patch.
Tagging with the patch so that this is backported along with it.
v2: squash in uninitialized warning fix (Nathan Chancellor)
Fixes: 8795e182b02d ("PCI/portdrv: Don't disable AER reporting in
get_port_device_capability()")
Signed-off-by: Lijo Lazar
Reviewed-by: Guchun Chen
Signed-off-by: Alex Deucher
Cc: sta...@vger.kernel.org
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2220
https://gitlab.freedesktop.org/drm/amd/-/issues/2220
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen 3 blank laptop screen on bootup
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Incomplete
Bug description:
When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a
Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes
blank shortly after bootup.
As far as I can tell (the screen blanks pretty quickly, so I'm not
100% sure), the last message before the screen disappears is this one:
Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu
from EFI VGA
Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine,
so this appears to be a regression in whatever changes there were in
the framebuffer/amdgpu drivers between 5.17.0.1025.26 and
5.17.0.1026.27.
I think this should be high priority, because it gives the impression
that the system is completely borked, when in actuality it's probably
just waiting for me to enter my drive encryption password.
If I type the encryption password, it seems to progress to starting
the system (the microphone mute LED comes on as expected), but even X
starting does not turn the screen back on. Switching to the frame
buffer console with Ctrl-Alt-Fx does nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
Hi Paul, Could you upload the result of "lspci -vvnn" command here? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Incomplete Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Tags added: originate-from-2000236 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Description changed: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] - Verified on the machine which can reproduce the issue. + ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] + This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Description changed: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] - The series of patches fixed the isue + The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] Verified on the machine which can reproduce the issue. [Where problems may occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] Verified on the machine which can reproduce the issue. [Where problems may occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: AceLan Kao (acelankao) => (unassigned) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches fixed the isue https://patchwork.freedesktop.org/series/110693/ [Test] Verified on the machine which can reproduce the issue. [Where problems may occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
Lunar has been merged to v6.1, so patches have been included. ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
** Description changed: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ - The patch has been accepted but still not shown in the upstream tree, so - submit this patch to oem kernels first, and will submit it to other - generic ubuntu kernels. + The patch is included in v6.2-rc1 + 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. + [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] Re: Lost display on bulit-in monitor after suspend
** Description changed: [Impact] + On some laptops, the eDP blinking slowly after resuming from S3 [Fix] + The series of patches fixed the isue + https://patchwork.freedesktop.org/series/110693/ [Test] + Verified on the machine which can reproduce the issue. [Where problems may occur] ** Tags added: oem-priority originate-from-2000383 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on bulit-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches fixed the isue https://patchwork.freedesktop.org/series/110693/ [Test] Verified on the machine which can reproduce the issue. [Where problems may occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001599] [NEW] Lost display on bulit-in monitor after suspend
Public bug reported: [Impact] [Fix] [Test] [Where problems may occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on bulit-in monitor after suspend Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] [Fix] [Test] [Where problems may occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
** Tags added: originate-from-1988823 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] + The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] - AMD provides a commit to fix this issue + AMD provides a list of commits to fix this issue + 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a + 2. drm/amdgpu: Don't enable LTR if not supported + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 + 3. Patch series: fix PCI AER issues + drm/amdgpu: make sure to init common IP before gmc + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 + drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 + drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 + 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ - For older version of the kernels, we need some other commits to fix the - conflicts - - a8671493d207 drm/amdgpu: make sure to init common IP before gmc - 7bb91228291a drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid cards - - [Test] + Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed: [Impact] + With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] + AMD provides a commit to fix this issue + https://patchwork.freedesktop.org/patch/507366/ + + For older version of the kernels, we need some other commits to fix the + conflicts + + a8671493d207 drm/amdgpu: make sure to init common IP before gmc + 7bb91228291a drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid cards + [Test] [Where problems could occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a commit to fix this issue https://patchwork.freedesktop.org/patch/507366/ For older version of the kernels, we need some other commits to fix the conflicts a8671493d207 drm/amdgpu: make sure to init common IP before gmc 7bb91228291a drm/amd/pm: disable BACO entry/exit completely on several sienna cichlid cards [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] [NEW] Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1989125 somerville ** Tags added: oem-priority originate-from-1989125 somerville ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => Won't Fix ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
Verified with 5.17.0-1025-oem and 6.0.0-1009, tried reboot 3 times with each kernel, the audio output is normal. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch has been accepted but still not shown in the upstream tree, so submit this patch to oem kernels first, and will submit it to other generic ubuntu kernels. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
Verified with 5.17.0-1025-oem and 5.19.0-27 kernel, confirmed the issue could not be reproduced on the reported machine. ** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
** Description changed: [Impact] + On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] + Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ + The patch has been accepted but still not shown in the upstream tree, so + submit this patch to oem kernels first, and will submit it to other + generic ubuntu kernels. + [Test] + Verified by our QA and ODM. [Where problems could occur] + It extends the delay time, should be no harm for existing platforms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch has been accepted but still not shown in the upstream tree, so submit this patch to oem kernels first, and will submit it to other generic ubuntu kernels. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] [NEW] Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
Public bug reported: [Impact] [Fix] https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1998062 somerville ** Description changed: [Impact] [Fix] + https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] ** Tags added: oem-priority originate-from-1998062 somerville ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] [Fix] https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
** Tags added: oem-priority originate-from-1997768 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
** Description changed: [Impact] + Micron NVME storage fails to init with below error messages + [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting + [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] + The patch from v5.19 add a quirk for Micron NVME fixes this issue +41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] + Verified with 5.17 OEM kernel on the reported machine. + Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. - [Where problems could occcur] + [Where problems could occur] + The impact should be low as it adds one device ID into a quirk. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] [NEW] Micron NVME storage failure [1344, 5407]
Public bug reported: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
The final an accepted patch https://patchwork.kernel.org/project/linux-pci/patch/20221109142652.450998-1-nirmal.pa...@linux.intel.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998419] [NEW] Gnome doesn't run smooth when performing normal usage with RPL-P CPU
Public bug reported: [Impact] Gnome desktop doesn't run smooth when performing normal usage, the cursor usually stops working and stuck, and then becomes back to normal. [Fix] Can't reproduce this issue with drm-tip kernel, so found below commit after bisected dc73ac63e63a drm/i915/rpl-p: Add stepping info [Test] Verified on the RPL-P machine and the cursor/window move smoothly. [Where problems could occur] Adding info for new RPL-P chipset should be pretty safe. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1997745 somerville ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1997745 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998419 Title: Gnome doesn't run smooth when performing normal usage with RPL-P CPU Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Gnome desktop doesn't run smooth when performing normal usage, the cursor usually stops working and stuck, and then becomes back to normal. [Fix] Can't reproduce this issue with drm-tip kernel, so found below commit after bisected dc73ac63e63a drm/i915/rpl-p: Add stepping info [Test] Verified on the RPL-P machine and the cursor/window move smoothly. [Where problems could occur] Adding info for new RPL-P chipset should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
6.0.0-1008.8 has been verified by ODM with different platforms. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
Verified that with the both proposed kernel(-1008) and the proposed sof firmware, the audio works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic ** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
The audio works with the 6.0-oem kernel built from the latest git tree which includes -1007 and stable update 6.0.4, 6.0.5, 6.0.6, and 6.0.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
Tried mainline kernel v6.1-rc1 ~ rc4, all of them work. Also applied required patches on top of mainline v6.0 kernel, and it works, too. So, the issue might be from 6.0-oem kernel, will check it soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
** Attachment added: "dmesg_6.1.0-060100rc4-generic.log" https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1992714/+attachment/5630718/+files/dmesg_6.1.0-060100rc4-generic.log ** Tags removed: verification-failed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
The firmware should be fine, verified with 6.0.0-1007-oem and mainline 6.1-rc4, the mainline kernel works, but oem kernel doesn't. Will check what is missing in the kernel and set the firmware verification to done. ** Attachment added: "dmesg_6.0.0-1007-oem.log" https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1992714/+attachment/5630717/+files/dmesg_6.0.0-1007-oem.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in firmware-sof source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
** Description changed: [Impact] + The system hangs after S3 with VMD mode is on. [Fix] + Intel provides a fix and still under discussion + https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ [Test] + Verified by us and ODM. [Where problems could occur] + The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. ** Description changed: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ + The patch is not finalized, so submit SRU to OEM kernels only, and will + submit to other series kernels once the patch is accepted by upstream. + [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. ** Tags added: oem-priority originate-from-1978453 somerville ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] [NEW] Screen freeze after resuming from suspend (nvme0: I/O timeout)
Public bug reported: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-1978453 somerville ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ The patch is not finalized, so submit SRU to OEM kernels only, and will submit to other series kernels once the patch is accepted by upstream. [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
** Description changed: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update + And applied some other commits to fix the conflicts + c48a36301634 drm/mgag200: Optimize damage clips + 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support + 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID + 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock + e13f13e039dc drm: Add DRM-managed mutex_init() + [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] + The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** Tags added: originate-from-1993325 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
