[Kernel-packages] [Bug 2042999] [NEW] BT/WiFi coexit stability issue on RTL8851BE/RTL8852BE
Public bug reported:
1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
Proposed firmware upstreamed as:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
("rtw89: 8852b: update fw to v0.29.29.5")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8852b: update fw to v0.29.29.4")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8851b: update fw to v0.29.41.3")
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2042999
Title:
BT/WiFi coexit stability issue on RTL8851BE/RTL8852BE
Status in linux-firmware package in Ubuntu:
New
Bug description:
1.Install Ubuntu 22.04 on SUT with RTL8851BE / 8852BE Wlan card
2.Connected BT KB/MS,and then connected WIFI, select an AP to connect
3.Check BT mouse/keyboard, mouse movement, keyboard key pressing not respond
smoothly.
Proposed firmware upstreamed as:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2afd1423e4765eb691711ea5e78a19853cb2f6eb
("rtw89: 8852b: update fw to v0.29.29.5")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8852b: update fw to v0.29.29.4")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=02df6e4f03c08fe95c8967a69b86d2c1165400d6
("rtw89: 8851b: update fw to v0.29.41.3")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2042999/+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 2042998] [NEW] After upgrading to 23.10 the system does not resume after suspend
Public bug reported:
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 5102 F wireplumber
/dev/snd/controlC1: jarl 5102 F wireplumber
/dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2042998
Title:
After upgrading to 23.10 the system does not resume after suspend
Status in linux package in Ubuntu:
New
Bug description:
This problem occurs when using nvidia proprietary binary driver. A
different problem occurs when I run the system without the nvidia
proprietary binary driver. See Bug #2042996
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 5102 F wireplumber
/dev/snd/controlC1: jarl 5102 F wireplumber
/dev/snd/seq:jarl 5099 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 08:19:03 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672
[Kernel-packages] [Bug 2042955] Re: kdump tools X dracut doesn't work
** Also affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2042955 Title: kdump tools X dracut doesn't work Status in dracut package in Ubuntu: New Status in kdump-tools package in Ubuntu: New Bug description: supposedly ubuntu kdump & ubuntu dracut do not work together. like at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2042955/+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 2042996] [NEW] After upgrading to 23.10 the system does not suspend when lid is taken down
Public bug reported:
Normally I use the nvidia-driver but to take proprietary binary drivers
out of the equation. I have now uninstalled that and is reporting this
bug without the proprietary binary driver.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 7560 F wireplumber
/dev/snd/controlC1: jarl 7560 F wireplumber
/dev/snd/seq:jarl 7557 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 07:58:08 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
nvidia.NVreg_EnableBacklightHandler=1 quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-04 (4 days ago)
dmi.bios.date: 02/02/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: orxp1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13RSA1:bd02/02/2016:br5.11:svnSystem76,Inc.:pnOryxPro:pvrorxp1:rvnSystem76,Inc.:rnOryxPro:rvrorxp1:cvnSystem76,Inc.:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.sku: Not Applicable
dmi.product.version: orxp1
dmi.sys.vendor: System76, Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2042996
Title:
After upgrading to 23.10 the system does not suspend when lid is taken
down
Status in linux package in Ubuntu:
New
Bug description:
Normally I use the nvidia-driver but to take proprietary binary
drivers out of the equation. I have now uninstalled that and is
reporting this bug without the proprietary binary driver.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarl 7560 F wireplumber
/dev/snd/controlC1: jarl 7560 F wireplumber
/dev/snd/seq:jarl 7557 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Nov 8 07:58:08 2023
HibernationDevice: RESUME=UUID=62c8a911-b76d-4691-9ffe-019c5aef1c88
InstallationDate: Installed on 2016-01-08 (2861 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. ES603 Swipe
Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=77b926b9-e936-4d48-a883-a4690b36dac0 ro
nvidia.NVreg_EnableBacklightHandler=1 quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5
[Kernel-packages] [Bug 2031367] Re: Archive races can cause nvidia driver / kernel version ABI mismatch
** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2031367 Title: Archive races can cause nvidia driver / kernel version ABI mismatch Status in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Bug description: [Summary] after selecting ubuntu from bios boot menu, it lost video output from the discrete GPU * build-in VGA port works fine, can output the display to monitor and boot into OS only the discrete GPU has issue [Steps to reproduce] It is not currently reproducible but, at some point in the past, these steps resulted in the problem: 1. install 22.04 2. install linux-nvidia 3. install linux-modules-nvidia-535-server-nvidia [Actual result] linux-nvidia w/ a 1030 ABI got installed with a linux-modules-nvidia-535-server-nvidia with a 1029 ABI. [Additional information] CID: 202307-31886 SKU: DGX station A100 system-manufacturer: NVIDIA system-product-name: DGX Station A100 920-23487-2531-000 bios-version: L9.28C CPU: AMD EPYC 7742 64-Core Processor (128x) GPU: 01:00.0 3D controller [0302]: NVIDIA Corporation GA100 [A100 SXM4 80GB] [10de:20b2] (rev a1) 46:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) 47:00.0 3D controller [0302]: NVIDIA Corporation GA100 [A100 SXM4 80GB] [10de:20b2] (rev a1) 81:00.0 3D controller [0302]: NVIDIA Corporation GA100 [A100 SXM4 80GB] [10de:20b2] (rev a1) c1:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) c2:00.0 3D controller [0302]: NVIDIA Corporation GA100 [A100 SXM4 80GB] [10de:20b2] (rev a1) Nvidia Driver: 535.54.03 kernel-version: 5.15.0-1030-nvidia [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2031367/+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 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
I'm hoping I'm experiencing the same bug and the fix could be updated to work on Mantic, and committed. ThinkPad P16s, Hybrid dock 40AF, inbuilt ether port works fine, dock ether port works fine in normal mode. If I enable MAC pass-through in BIOS, only a carrier signal is detected, connection fails at DHCP step, and no Internet connection can be established. WiFi is unaffected. -- 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/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Lenovo dock doesn't support MAC passthrough. [Fix] Add support to Lenovo Dock MAC passthrough. [Test] MAC passthrough works once the patch is applied. [Regression Potential] Low. Apart from adding support to Lenovo Dock, this patch only did minor refactoring to existing behavior, no functional change to current code. === Original Bug Report === Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top- tech/Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+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 2039755] Re: lernel crashes in CIFS code
I've got another of these: Nov 8 11:13:52 dsdk8y2u kernel: [435899.335507] [ cut here ] Nov 8 11:13:52 dsdk8y2u kernel: [435899.335509] WARNING: CPU: 2 PID: 218227 at fs/smb/client/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Nov 8 11:13:52 dsdk8y2u kernel: [435899.335563] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs snd_usb_audio snd_usbmidi_lib st ccm rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc cmac algif_hash algif_skcipher af_alg snd_hda_codec_hdmi overlay bnep zram snd_sof_pci_intel_cnl snd_sof_intel_hda_com mon soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd _compress ac97_bus snd_ctl_led snd_pcm_dmaengine snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec binfmt_misc snd_hda_core snd_hwdep intel_tcc_cooling snd_pcm mei_hdcp mei_pxp x86_p kg_temp_thermal intel_powerclamp dell_rbtn intel_rapl_msr snd_seq_midi Nov 8 11:13:52 dsdk8y2u kernel: [435899.335604] coretemp snd_seq_midi_event dell_laptop nls_iso8859_1 kvm_intel dell_smm_hwmon snd_rawmidi dell_wmi kvm snd_seq irqbypass snd_seq_device rapl dell_smbios iwlmvm dcdbas intel_cstate typec_dis playport ledtrig_audio dell_wmi_sysman serio_raw dell_wmi_descriptor mac80211 firmware_attributes_class wmi_bmof libarc4 uvcvideo snd_timer videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 btrtl intel_wmi_thunderbolt snd btbcm btinte l btmtk soundcore videodev iwlwifi bluetooth videobuf2_common input_leds joydev ecdh_generic hid_multitouch mc cfg80211 ecc mei_me mei processor_thermal_device_pci_legacy processor_thermal_device hid_sensor_als hid_sensor_incl_3d hid_sensor _accel_3d hid_sensor_rotation hid_sensor_gyro_3d hid_sensor_magn_3d hid_sensor_custom_intel_hinge hid_sensor_prox processor_thermal_rfim hid_sensor_trigger processor_thermal_mbox industrialio_triggered_buffer processor_thermal_rapl kfifo_bu f intel_rapl_common hid_sensor_iio_common industrialio intel_soc_dts_iosf Nov 8 11:13:52 dsdk8y2u kernel: [435899.335642] intel_pch_thermal int3403_thermal mac_hid intel_hid int3400_thermal int340x_thermal_zone sparse_keymap acpi_thermal_rel soc_button_array acpi_pad sch_fq_codel msr parport_pc ppdev lp efi_pst ore parport ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt r8153_ecm cdc_ether usbnet hid_sensor_custom hid_sensor_hub intel_ishtp_hid r8152 mii i915 drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_ pclmul cec wacom crc32_pclmul usbhid rc_core polyval_clmulni hid_generic polyval_generic drm_kms_helper nvme ghash_clmulni_intel sha512_ssse3 syscopyarea rtsx_pci_sdmmc sysfillrect intel_lpss_pci ucsi_acpi aesni_intel i2c_i801 sysimgb lt thunderbolt intel_lpss crypto_simd i2c_hid_acpi psmouse i2c_hid i2c_smbus cryptd nvme_core typec_ucsi drm intel_ish_ipc nvme_common idma64 xhci_pci xhci_pci_renesas rtsx_pci typec hid intel_ishtp video pinctrl_cannonlake wmi z3fold zstd Nov 8 11:13:52 dsdk8y2u kernel: [435899.335687] CPU: 2 PID: 218227 Comm: kworker/2:0 Tainted: GW 6.2.0-36-generic #37~22.04.1-Ubuntu Nov 8 11:13:52 dsdk8y2u kernel: [435899.335689] Hardware name: Dell Inc. Latitude 7400 2-in-1/0HCNR3, BIOS 1.8.0 06/16/2020 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335691] Workqueue: events delayed_mntput Nov 8 11:13:52 dsdk8y2u kernel: [435899.335695] RIP: 0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Nov 8 11:13:52 dsdk8y2u kernel: [435899.335736] Code: e8 48 c7 c1 70 42 0a c2 48 c7 c2 0a f5 0c c2 41 89 c1 48 c7 c6 78 8f 0b c2 48 c7 c7 d0 67 11 c2 e8 e8 b2 63 df e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 40 55 e8 df 48 c7 c6 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335737] RSP: 0018:bb0483557d00 EFLAGS: 00010286 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335739] RAX: RBX: 91bc54422ee8 RCX: Nov 8 11:13:52 dsdk8y2u kernel: [435899.335740] RDX: RSI: RDI: Nov 8 11:13:52 dsdk8y2u kernel: [435899.335741] RBP: bb0483557d30 R08: R09: Nov 8 11:13:52 dsdk8y2u kernel: [435899.335742] R10: R11: R12: 91bf29020800 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335743] R13: 91bf29020838 R14: R15: 91bf29020800 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335744] FS: () GS:91bfdc50() knlGS: Nov 8 11:13:52 dsdk8y2u kernel: [435899.335745] CS: 0010 DS: ES: CR0: 80050033 Nov 8 11:13:52 dsdk8y2u kernel: [435899.335746] CR2: 7
[Kernel-packages] [Bug 2042357] Re: Merge crash 8.0.3+ds1-3 into Noble
The package built successfully in all architectures (amd64, arm64, armhf, ppc64el, s390x). The PPA does not have riscv64 enabled, but it crash/riscv64 FTBFS in mantic-release, which is in noble now, so even if it fails, it is not a regression from latest state. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2042357 Title: Merge crash 8.0.3+ds1-3 into Noble Status in crash package in Ubuntu: In Progress Status in crash package in Debian: Fix Released Bug description: Work in progress; rebasing on 8.0.3+ds1-3, and testing. ... $ rmadison -a source crash | grep noble crash | 8.0.2-1ubuntu1 | noble | source $ rmadison -a source crash -u debian | grep 'unstable ' crash | 8.0.2-1 | unstable | source crash | 8.0.3+ds1-3 | unstable | source ... Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz ... Docs: https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2028186] Re: zfs with encryption: sluggish resume from suspend, intermittent freezes
FWIW, I switched back to ext4 and am no longer experiencing the same issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2028186 Title: zfs with encryption: sluggish resume from suspend, intermittent freezes Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I had been using Jammy on a Thinkpad T470 for months without problems. I decided to try a fresh Ubuntu Desktop install using ZFS, using the install-time option for full-disk encryption. After using the fresh install for a little while, I noticed that the system was "more sluggish" in the ZFS configuration (which was disappointing, but tolerable). The "sluggishness" is especially noticeable when resuming from suspend. Typically, I'll look at the system clock and notice that it does not change for ~tens of seconds. On some occasions, it will freeze completely (even after waiting many minutes) and require a reboot. Given that this the only difference between a "perfectly working system" and "problematic system" was the filesystem change, I strongly suspect ZFS as the cause (and/or perhaps enabling the full-disk encryption option for it during the install). Any advice on how to further triage this and narrow down the issue would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 19 10:03:03 2023 InstallationDate: Installed on 2023-03-22 (119 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2028186/+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 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
I have the same issue. Thanks for providing instructions to fix it. I
was able to resolve the Bluetooth problem with your fix, but WiFI still
doesn't work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0NG7N9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5560
dmi.product.sku: 0A62
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2040106/+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 2042075] Re: Black screen at login after updating to this kernel
OK thanks. Nothing was obvious in the log differences. We need to narrow down intermediate kernel releases to identify what's changed to cause this regression. Can you please test these binaries from those. Capture the journals for each and note if they worked or didn't. Hopefully we'll get closer. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/26313281 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26398561 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/26405786 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26504338 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26504338 -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+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 2042868] Re: Kernel 6.2.0-36 broke RTW88 solution
Juerg, Thank you for your reaction. I made two 'journalctl -b -1' files, one after rebooting into the 'not working' kernel, the other after rebooting into the 'does work' kernel. It seems I can only attach one file in this comment, so I added the 'not working' version. As to not using the kernel provided rtw88 driver: I did try, long time ago. But the effect is the same as I have now in the 6.2.0-36 kernel: the Wifi driver is not recognised, and I have no network. (I remember the first time having to do something like: attach a cable to a Wifi repeater so that the laptop had internet through the cable, and THEN solve the rtw88 problem by - essentially - using lwfingers solution. For some reason I have NOT been able to configure it such that dsmod works correctly on my laptop, while I got it working on the laptop my parents use [and I administrate]). Any help is appreciated. As for now I can live with the current situation: the kernel I do use is relatively current, although it is officially 'superseded'. Kind regards, Roel [Edit: added a much needed 'NOT' in the post] ** Attachment added: "kernel_not_working" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042868/+attachment/5716997/+files/kernel_not_working -- 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/2042868 Title: Kernel 6.2.0-36 broke RTW88 solution Status in linux package in Ubuntu: New Bug description: On my Linux Mint (derived from Ubuntu) system, I relied on the excellent rtw88 solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my Realtek Wifi Driver whenever a new kernel comes out. As I understand it, the github repository normally is 'ahead' of any kernels, so if and when I do a 'git pull' of his repository before installing the new rtw88, it should work. And this has worked for quite some time, until the 6.2.0-36 kernel came along. As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can cause build issues. You'll need to manually adjust the source code or look for solutions specific to your distribution. We cannot support these types of issues.", so asking him is not an option. Help? Result from version: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 (Well, this the kernel version in which I have Wifi and thus internet, the 'does not work' kernel is 6.2.0-36, supported till February 2024) Result from lscpi-vnvn (also when running the version that still has internet) as an attachment. Kind regards, Roel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042868/+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 2042357] Re: Merge crash 8.0.3+ds1-3 into Noble
Merged with Debian (8.0.3+ds1-3), now building (ppa:mfo/crash-noble). ** Summary changed: - Merge crash 8.0.3 into Noble + Merge crash 8.0.3+ds1-3 into Noble ** Description changed: - Work in progress; rebasing on 8.0.3+ds1-3, and testing. + Work in progress; rebased on 8.0.3+ds1-3, now building (ppa:mfo/crash- + noble), and testing. Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz ** Description changed: - Work in progress; rebased on 8.0.3+ds1-3, now building (ppa:mfo/crash- - noble), and testing. + Work in progress; rebasing on 8.0.3+ds1-3, and testing. + + ... + + $ rmadison -a source crash | grep noble + crash | 8.0.2-1ubuntu1 | noble | source + + $ rmadison -a source crash -u debian | grep 'unstable ' + crash | 8.0.2-1 | unstable | source + crash | 8.0.3+ds1-3 | unstable | source + + ... Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz ** Description changed: Work in progress; rebasing on 8.0.3+ds1-3, and testing. ... $ rmadison -a source crash | grep noble - crash | 8.0.2-1ubuntu1 | noble | source + crash | 8.0.2-1ubuntu1 | noble | source $ rmadison -a source crash -u debian | grep 'unstable ' crash | 8.0.2-1 | unstable | source crash | 8.0.3+ds1-3 | unstable | source ... Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz + + ... + + Docs: + https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/2042357 Title: Merge crash 8.0.3+ds1-3 into Noble Status in crash package in Ubuntu: In Progress Status in crash package in Debian: Fix Released Bug description: Work in progress; rebasing on 8.0.3+ds1-3, and testing. ... $ rmadison -a source crash | grep noble crash | 8.0.2-1ubuntu1 | noble | source $ rmadison -a source crash -u debian | grep 'unstable ' crash | 8.0.2-1 | unstable | source crash | 8.0.3+ds1-3 | unstable | source ... Debian bugs: https://bugs.debian.org/1054805 Please update crash to 8.0.3 https://bugs.debian.org/1055117 FTBFS: crash 8.0.3-1 is missing gdb-10.2.tar.gz ... Docs: https://github.com/canonical/ubuntu-maintainers-handbook/blob/main/PackageMerging.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/2042357/+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 2036988] Re: Unable to boot on Lenovo L590 Laptop
Hello, I also updated my ThinkPad L590 from 20.04 LTS to 22.04.03 LTS (Kenel Version 6.2.0-36-generic) and encountered the same bug. The system was also hanging after "Loading initial ramdisk". I was able to resolve the issue by disableing the "Security Chip"/TPM 2.0 module in BIOS. I remember that I usually got the following message when I booted Ubuntu 20.04 (before the update with "Security chip" enabled) "[Firmware Bug]: TPM interrupt not working, polling instead" Hope that helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036988 Title: Unable to boot on Lenovo L590 Laptop Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen. With advanced boot options and selecting the current kernel, it hangs immediately after "Loading initial ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behavior, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/4072/fd/1023: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: bernd 3561 F pulseaudio /dev/snd/pcmC0D7p: bernd 3561 F...m pulseaudio /dev/snd/controlC1: bernd 3561 F pulseaudio CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-24 (1276 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20Q70019GE Package: linux-hwe-6.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9-generic N/A linux-backports-modules-6.5.0-9-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.21 Tags: jammy Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-20 (336 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/11/2019 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET37W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q70019GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR0ZET37W(1.15):bd12/11/2019:br1.15:efr1.12:svnLENOVO:pn20Q70019GE:pvrThinkPadL590:rvnLENOVO:rn20Q70019GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q7_BU_SMB_FM_ThinkPadL590: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q70019GE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036988/+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 2036988] Re: Unable to boot on Lenovo L590 Laptop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036988 Title: Unable to boot on Lenovo L590 Laptop Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: With Kernel images 6.2.0-32 and 6.2.0-33, I can no longer boot ubuntu on my laptop. On regular graphic boot it just hangs on a black screen. With advanced boot options and selecting the current kernel, it hangs immediately after "Loading initial ramdisk" without any error message. I have to select an older kernel release to boot. 6.2.0-26 is the latest I know to work. We have another identical laptop of type Lenovo L590 also installed with Ubuntu and it shows the same behavior, so it's likely not a hardware problem on my device. The CPU type is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 16:51:07 2023 InstallationDate: Installed on 2020-04-24 (1245 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-20 (304 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/4072/fd/1023: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: bernd 3561 F pulseaudio /dev/snd/pcmC0D7p: bernd 3561 F...m pulseaudio /dev/snd/controlC1: bernd 3561 F pulseaudio CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-24 (1276 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20Q70019GE Package: linux-hwe-6.2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9-generic N/A linux-backports-modules-6.5.0-9-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.21 Tags: jammy Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-20 (336 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/11/2019 dmi.bios.release: 1.15 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET37W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q70019GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR0ZET37W(1.15):bd12/11/2019:br1.15:efr1.12:svnLENOVO:pn20Q70019GE:pvrThinkPadL590:rvnLENOVO:rn20Q70019GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Q7_BU_SMB_FM_ThinkPadL590: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q70019GE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036988/+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 2041853] Re: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)
*** This bug is a duplicate of bug 2009952 *** https://bugs.launchpad.net/bugs/2009952 Think this is actually a duplicate of 2009952. I haven't tested 6.x with the kernel parameter suggested, but everything else described matches. So nothing to do with gnome-shell. https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952 ** This bug has been marked a duplicate of bug 2009952 [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2041853 Title: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works) Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I'm tracking down the multiple causes of screen flashes and audio interruption on my ubuntu 22.04 laptop. Issue open with Lenovo : https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298 This bug is one of the causes (log reversed : journalctl -r) oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac8bfbc10] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd416dc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996b860] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878ac50] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb009cc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a610] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9f6a480] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd404df0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a2f0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb16d9a0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca446320] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acdf86f70] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996a4e0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6fd0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9e94de0] i
[Kernel-packages] [Bug 1988966] Re: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
The ubuntu delta should be applicable to debian too. But it is done in a way that is not upstreamable to Debian. Please change debian/control to have arch specific depends on kexec- tools, for all Debian arches where it exists, and please contribute it to debian. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1988966 Title: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency Status in kexec-tools package in Ubuntu: New Status in kiwi package in Ubuntu: Fix Released Status in kexec-tools package in Debian: New Bug description: kiwi-dracut-oem-dump has a dependency on kexec-tools which is not built for riscv64. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 contains a patch from openSUSE https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec- tools/riscv.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1988966/+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 1709612] Re: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127
if I'm reading the log correctly, you're somehow missing the 'sha1sum' tool, which shouldn't be possible. I suspect other issues with the system, so it's not a bug in the package ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1709612 Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 Status in linux-firmware package in Ubuntu: Invalid Bug description: Iniciando el sistema operativo ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.11 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 02:53:28 2017 Dependencies: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2017-01-06 (215 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1709612/+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 1713230] Re: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127
*** This bug is a duplicate of bug 1709612 *** https://bugs.launchpad.net/bugs/1709612 ** This bug has been marked a duplicate of bug 1709612 package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1713230 Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 Status in linux-firmware package in Ubuntu: New Bug description: Starting graph system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.11 ProcVersionSignature: Ubuntu 4.4.0-75.96-lowlatency 4.4.59 Uname: Linux 4.4.0-75-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 18 12:30:49 2017 Dependencies: ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 127 InstallationDate: Installed on 2017-01-06 (232 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.15ubuntu0.2 SourcePackage: linux-firmware Title: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1713230/+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 1728174] Re: Wrong version of liquidio firmware images is in linux-firmware package of Artful Aardvark
And how would a newer firmware break the driver? AA is EOL anyway, so closing ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1728174 Title: Wrong version of liquidio firmware images is in linux-firmware package of Artful Aardvark Status in linux-firmware package in Ubuntu: Invalid Bug description: The wrong version of liquidio firmware images (v1.6.1) is there. The right version is v1.5.1 which matches the version of the liquidio PF and VF drivers that are part of Linux kernel version 4.13 which Artful has. Please get the v1.5.1 liquidio firmware images from upstream: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=5e68cab0976c0efc13b769791ade3e9747807f35 and put them in Artful's linux-firmware package. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1728174/+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 2042946] [NEW] sound poping and cracking
Public bug reported: since installing kernel 5.15.0-88, my sound is popping and cracking very loudly, I had to deactivate my sound card. No issue with XX.0-87. Realtek ALC255, on hda intel PCH ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2042946 Title: sound poping and cracking Status in linux package in Ubuntu: New Bug description: since installing kernel 5.15.0-88, my sound is popping and cracking very loudly, I had to deactivate my sound card. No issue with XX.0-87. Realtek ALC255, on hda intel PCH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042946/+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 2042945] [NEW] Ubuntu should expose EFI_TLS_CONFIGURATION_PROTOCOL_GUID to cloud-init, userspace and all the things
Public bug reported: Ubuntu should expose EFI_TLS_CONFIGURATION_PROTOCOL_GUID to cloud-init, userspace and all the things https://uefi.org/specs/UEFI/2.10/28_Network_Protocols_TCP_IP_and_Configuration.html#efi- tls-configuration-protocol ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2042945 Title: Ubuntu should expose EFI_TLS_CONFIGURATION_PROTOCOL_GUID to cloud- init, userspace and all the things Status in linux package in Ubuntu: New Bug description: Ubuntu should expose EFI_TLS_CONFIGURATION_PROTOCOL_GUID to cloud- init, userspace and all the things https://uefi.org/specs/UEFI/2.10/28_Network_Protocols_TCP_IP_and_Configuration.html#efi- tls-configuration-protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042945/+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 1718708] Re: Support mpeg4 - dvb-usb-dib0700-1.20.fw
the hardware doesn't support DVB-T2, you need solo/dualHD model for that ** Changed in: linux-firmware (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1718708 Title: Support mpeg4 - dvb-usb-dib0700-1.20.fw Status in linux-firmware package in Ubuntu: Won't Fix Bug description: Hello since 04/05/2016 the french channels (dvb-T) change for mpeg4 , and a scan (with w-scan) return : "674498: (time: 04:20.518) signal ok:QAM_AUTO f = 674498 kHz I999B8C999D999T999G999Y999 (0:0:0) QAM_AUTO f = 674498 kHz I999B8C999D999T999G999Y999 (0:0:0) : updating transport_stream_id: -> (0:0:10) QAM_AUTO f = 674498 kHz I999B8C999D999T999G999Y999 (0:0:10) : updating network_id -> (0:8442:10) undefined coderate HP undefined coderate HP already known: (QAM_64 f = 4294967 kHz I999B8C999D0T8G8Y0 (8442:8442:2)), but not found by pids undefined coderate HP undefined coderate HP undefined coderate HP undefined coderate HP already known: (QAM_64 f = 4294967 kHz I999B8C999D0T8G32Y0 (8442:8442:8)), but not found by pids undefined coderate HP" "ERROR: Sorry - i couldn't get any working frequency/transponder Nothing to scan!!" With "dmesg" "[34150.910121] usb 2-1.2: Product: NovaT 500Stick [34150.910125] usb 2-1.2: Manufacturer: Hauppauge [34150.910129] usb 2-1.2: SerialNumber: 4035677631 [34152.447292] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in cold state, will try to load a firmware [34152.472171] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [34152.673657] dib0700: firmware started successfully. [34153.176663] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in warm state. [34153.177528] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [34153.177743] DVB: registering new adapter (Hauppauge Nova-TD Stick (52009)) [34153.707111] usb 2-1.2: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)... [34153.940615] DiB0070: successfully identified [34153.940628] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [34153.940776] DVB: registering new adapter (Hauppauge Nova-TD Stick (52009)) [34154.127845] usb 2-1.2: DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)... [34154.352614] DiB0070: successfully identified [34154.416501] Registered IR keymap rc-dib0700-rc5 [34154.416811] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/rc/rc0/input17 [34154.419727] rc0: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/rc/rc0 [34154.419915] dvb-usb: schedule remote query interval to 50 msecs. [34154.419922] dvb-usb: Hauppauge Nova-TD Stick (52009) successfully initialized and connected. [34154.422126] usbcore: registered new interface driver dvb_usb_dib0700 fred@fred-W250HUQ:~$ " I don't know if you need some more informations , but do not hesitate to ask me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1718708/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices
** Attachment added: "dm_fake_dev.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+attachment/5716855/+files/dm_fake_dev.sh -- 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/1829563 Title: bcache: risk of data loss on I/O errors in backing or caching devices Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] * The bcache code in Bionic lacks several fixes to handle I/O errors in both backing devices and caching devices. * Partial or permanent errors in backing or caching devices, specially in writeback mode, can lead to data loss and/or the application is not notified about failed I/O requests. * The bcache device might remain available for I/O requests even if backing device is offline, so writes are undefined. [Test Case] * Detailed test cases/steps for the behavior of many patches with code logic changes are provided in bug comments. * The patchset has been tested for regressions on each cache mode (writethrough, writeback, writearound, none) with the xfstests test suite (on ext4) and fio (sequential + random read-write). [Regression Potential] * The patchset is relatively large and touches several areas in bcache code, however, synthetic testing of the patches has been performed, and extensive regression/stress tests were run (as mentioned in Test Case section). * Many patches in the patchset are 'Fixes' patches to other patches, and no further 'Fixes' currently exist upstream. [Other Info] * Canonical Field Eng. deploys bcache+writeback extensively (e.g., BootStack, UA cloud, except rare all-flash cases). [Original Bug Description] This is a request for a backport of the following upstream patch from 4.18: "bcache: stop bcache device when backing device is offline" https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee Field engineering uses bcache quite extensively and it would be good to have this in the GA/bionic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829563/+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 2041219] Re: GUI Freezes Randomly
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2041219 Title: GUI Freezes Randomly Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Hi, So everything would be working normally and then all of a sudden the laptop would freeze and nothing works. There's nothing in /var/crash. This has been run: cd ~/.local/share/gnome-shell/ rm -rf extensions output of journalctl -b-1 > prevboot.txt is attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darian 2556 F pulseaudio /dev/snd/pcmC0D0p: darian 2556 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-21 (66 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: PC Specialist Limited W94_95_97JU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-35-generic N/A linux-backports-modules-6.2.0-35-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.21 Tags: jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W94_95_97JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: W94_95_97JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2041690] Re: [nvidia] After using the secondary screen, the primary screen stops working
** Summary changed:
- Cannot open internal or screen laptop
+ [nvidia] After using the secondary screen, the primary screen stops working
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Tags added: nvidia
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2041690
Title:
[nvidia] After using the secondary screen, the primary screen stops
working
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Bug description:
After I use the secondary screen, the primary screen stops working,
and the problem is nvidia
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12
19:41:24 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:58:39 2023
DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics]
[1025:153b]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f9d] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile /
Max-Q] [1025:1544]
InstallationDate: Installed on 2023-05-20 (160 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=8806d2d2-440c-4fb8-bfae-fce3d6fc0f20 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-14 (13 days ago)
XorgConf:
dmi.bios.date: 06/22/2022
dmi.bios.release: 1.18
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Kamiq_TLS
dmi.board.vendor: TGL
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.18
dmi.ec.firmware.release: 1.10
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.18:bd06/22/2022:br1.18:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.18:rvnTGL:rnKamiq_TLS:rvrV1.18:cvnAcer:ct10:cvrV1.18:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN517-54
dmi.product.sku:
dmi.product.version: V1.18
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2041690/+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 2041690] [NEW] [nvidia] After using the secondary screen, the primary screen stops working
You have been subscribed to a public bug:
After I use the secondary screen, the primary screen stops working, and
the problem is nvidia
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12
19:41:24 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 27 23:58:39 2023
DistUpgraded: 2023-10-14 21:42:04,522 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if
00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f9d] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / Max-Q]
[1025:1544]
InstallationDate: Installed on 2023-05-20 (160 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=8806d2d2-440c-4fb8-bfae-fce3d6fc0f20 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-10-14 (13 days ago)
XorgConf:
dmi.bios.date: 06/22/2022
dmi.bios.release: 1.18
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Kamiq_TLS
dmi.board.vendor: TGL
dmi.board.version: V1.18
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.18
dmi.ec.firmware.release: 1.10
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.18:bd06/22/2022:br1.18:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.18:rvnTGL:rnKamiq_TLS:rvrV1.18:cvnAcer:ct10:cvrV1.18:sku:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN517-54
dmi.product.sku:
dmi.product.version: V1.18
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
[nvidia] After using the secondary screen, the primary screen stops working
https://bugs.launchpad.net/bugs/2041690
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
--
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 2038922] Re: Sudden screen crash
*** This bug is a duplicate of bug 2037325 *** https://bugs.launchpad.net/bugs/2037325 ** This bug has been marked a duplicate of bug 2037325 [Lubuntu] Sudden screen freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038922 Title: Sudden screen crash Status in linux-hwe-6.2 package in Ubuntu: New Bug description: All of the sudden screen started flickering and showing artifacts and after a few seconds got frozen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Date: Tue Oct 10 15:46:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:5062] InstallationDate: Installed on 2023-04-20 (172 days ago) InstallationMedia: Lubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HMS6XX00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=63da9f00-db9b-478f-91b2-b370baa48314 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2022 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET69W (1.47 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HMS6XX00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270: dmi.product.family: ThinkPad X270 dmi.product.name: 20HMS6XX00 dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2038922/+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 2041853] Re: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)
** Summary changed: - screen goes blank, audio cuts out + screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works) ** Package changed: gnome-shell (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Changed in: linux-hwe-6.2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2041853 Title: screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works) Status in linux-hwe-6.2 package in Ubuntu: New Bug description: I'm tracking down the multiple causes of screen flashes and audio interruption on my ubuntu 22.04 laptop. Issue open with Lenovo : https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298 This bug is one of the causes (log reversed : journalctl -r) oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac8bfbc10] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd416dc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996b860] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878ac50] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb009cc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a610] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9f6a480] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd404df0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a2f0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb16d9a0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca446320] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acdf86f70] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996a4e0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6fd0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9e94de0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6350] is on because it needs an allocation. oct. 30 15:17:13 hostn
[Kernel-packages] [Bug 2041853] [NEW] screen goes blank, audio cuts out with kernel 6.2 (but 5.15 works)
You have been subscribed to a public bug: I'm tracking down the multiple causes of screen flashes and audio interruption on my ubuntu 22.04 laptop. Issue open with Lenovo : https://forums.lenovo.com/t5/Ubuntu/ThinkPad-T14s-Gen-3-AMD-Ryzen-Screen-flickers-randomly-and-becomes-black-for-4-5-seconds/m-p/525298 This bug is one of the causes (log reversed : journalctl -r) oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). oct. 30 15:17:13 hostname gnome-shell[22615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertion 'clutter_actor_has_allocation (actor)' failed oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac8bfbc10] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd416dc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996b860] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878ac50] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb009cc0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a610] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9f6a480] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd404df0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac878a2f0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb16d9a0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca446320] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acdf86f70] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996a4e0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6fd0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac9e94de0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6350] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acb121e80] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558ac996ab60] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558aca9a6670] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: Can't update stage views actor [:0x558acd3dada0] is on because it needs an allocation. oct. 30 15:17:13 hostname gnome-shell[22615]: _st_create_shadow_pipeline_from_actor: assertio
[Kernel-packages] [Bug 2039603] Re: NVIDIA pull requests 1018-001v1
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2039603 Title: NVIDIA pull requests 1018-001v1 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Bug description: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2039603/+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 2042929] Re: kernel ring buffer prints UBSAN: array-index-out-of-bounds
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- 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/2042929 Title: kernel ring buffer prints UBSAN: array-index-out-of-bounds Status in linux package in Ubuntu: New Bug description: Context: $ lsb_release -a 2>/dev/null Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic $ uname -rm 6.5.0-10-generic x86_64 $ lshw -short 2>/dev/null | grep display /0/100/1/0 /dev/fb0displayVenus XT [Radeon HD 8870M / R9 M270X/M370X] Errors: --- fifix@fifix-Precision-M4800:~$ sudo dmesg | grep UBSAN [0.809092] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34 [0.809863] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2715:55 [0.810629] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2705:39 [0.811416] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6831:39 [0.812119] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6868:32 [ 49.054671] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/include/linux/ieee80211.h:4304:28 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Nov 7 12:15:43 2023 InstallationDate: Installed on 2023-11-04 (3 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042929/+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 2042935] [NEW] NVIDIA pull request 1018-002v1
Public bug reported: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2042935/+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 2042929] [NEW] kernel ring buffer prints UBSAN: array-index-out-of-bounds
You have been subscribed to a public bug: Context: $ lsb_release -a 2>/dev/null Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic $ uname -rm 6.5.0-10-generic x86_64 $ lshw -short 2>/dev/null | grep display /0/100/1/0 /dev/fb0displayVenus XT [Radeon HD 8870M / R9 M270X/M370X] Errors: --- fifix@fifix-Precision-M4800:~$ sudo dmesg | grep UBSAN [0.809092] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34 [0.809863] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2715:55 [0.810629] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2705:39 [0.811416] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6831:39 [0.812119] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/drivers/gpu/drm/radeon/si_dpm.c:6868:32 [ 49.054671] UBSAN: array-index-out-of-bounds in /build/linux-UiLXaH/linux-6.5.0/include/linux/ieee80211.h:4304:28 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Nov 7 12:15:43 2023 InstallationDate: Installed on 2023-11-04 (3 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic -- kernel ring buffer prints UBSAN: array-index-out-of-bounds https://bugs.launchpad.net/bugs/2042929 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 2039786] Re: Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic
** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2039786 Title: Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic Status in linux-raspi package in Ubuntu: New Bug description: Hello all, I upgraded my Raspberry Pi 3B+ from 22.04 to 23.10. The storage device where the OS resides is a USB hdd. It is connected to the Pi via a ASMedia Technology Inc. X820. After the upgrade to 23.10, Ubuntu crashes during boot. To eliminate the X820 as a variable: - I created a Ubuntu server 23.10 directly on a USB stick -> The pi doesn't boot - I created a Ubuntu server 23.04 the same way -> the pi boots After investigation, I found that if I copy the /boot/firmware folder from an old 22.04 image and replace the content of the Fat32 boot partition of the HDD with its content, Ubuntu boots again. From the error I get during boot time, it looks like after booting, the USB HDD is not found or the root partition is not mounted properly. Booting with an SD card and mounting the HDD, I see that no logs in /var/log folder are being updated What should be my next step to get proper error messages and investigate further? Thanks in advance, Aurélien To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039786/+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 2039786] [NEW] Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic
You have been subscribed to a public bug: Hello all, I upgraded my Raspberry Pi 3B+ from 22.04 to 23.10. The storage device where the OS resides is a USB hdd. It is connected to the Pi via a ASMedia Technology Inc. X820. After the upgrade to 23.10, Ubuntu crashes during boot. To eliminate the X820 as a variable: - I created a Ubuntu server 23.10 directly on a USB stick -> The pi doesn't boot - I created a Ubuntu server 23.04 the same way -> the pi boots After investigation, I found that if I copy the /boot/firmware folder from an old 22.04 image and replace the content of the Fat32 boot partition of the HDD with its content, Ubuntu boots again. From the error I get during boot time, it looks like after booting, the USB HDD is not found or the root partition is not mounted properly. Booting with an SD card and mounting the HDD, I see that no logs in /var/log folder are being updated What should be my next step to get proper error messages and investigate further? Thanks in advance, Aurélien ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Raspberry Pi 3B+ doesnt boot from USB on 23.10 Mantic https://bugs.launchpad.net/bugs/2039786 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. -- 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 2042713] Re: Pale Green blank screen after login
-84? I don't see a tag for that on the jammy kernel repo, so where is that from? -- 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/2042713 Title: Pale Green blank screen after login Status in linux package in Ubuntu: Incomplete Bug description: Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84. N.B. I'm using a Graphic AMD processor with unconventional screens resolutions (1280x1025 (5/4) & 1360x768 (16:9)) inxi : CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-) speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256 Shell: Bash inxi: 3.3.13 inxi -S : System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042713/+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 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
Google have provided a non synthetic `fio` impact > Performance was severally degraded when accessing Persistent Volumes provided by Portworx/PureStorage. -- 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/2042564 Title: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: We in the Canonical Public Cloud team have received report from our colleagues in Google regarding a potential performance regression with the 5.15 kernel vs the 5.4 kernel on ubuntu 20.04. Their test were performed using the linux-gkeop and linux-gkeop-5.15 kernels. I have verified with the generic Ubuntu 20.04 5.4 linux-generic and the Ubuntu 20.04 5.15 linux-generic-hwe-20.04 kernels. The tests were run using `fio` fio commands: * 4k initwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` * 4k overwrite: `fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sdc` My reproducer was to launch an Ubuntu 20.04 cloud image locally with qemu the results are below: Using 5.4 kernel ``` ubuntu@cloudimg:~$ uname --kernel-release 5.4.0-164-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 8 (f=8): [W(8)][99.6%][w=925MiB/s][w=237k IOPS][eta 00m:01s] fiojob1: (groupid=0, jobs=8): err= 0: pid=2443: Thu Nov 2 09:15:22 2023 write: IOPS=317k, BW=1237MiB/s (1297MB/s)(320GiB/264837msec); 0 zone resets slat (nsec): min=628, max=37820k, avg=7207.71, stdev=101058.61 clat (nsec): min=457, max=56099k, avg=340.45, stdev=1707823.38 lat (usec): min=23, max=56100, avg=3229.78, stdev=1705.80 clat percentiles (usec): | 1.00th=[ 775], 5.00th=[ 1352], 10.00th=[ 1647], 20.00th=[ 2024], | 30.00th=[ 2343], 40.00th=[ 2638], 50.00th=[ 2933], 60.00th=[ 3261], | 70.00th=[ 3654], 80.00th=[ 4146], 90.00th=[ 5014], 95.00th=[ 5932], | 99.00th=[ 8979], 99.50th=[10945], 99.90th=[18220], 99.95th=[22676], | 99.99th=[32113] bw ( MiB/s): min= 524, max= 1665, per=100.00%, avg=1237.72, stdev=20.42, samples=4232 iops: min=134308, max=426326, avg=316855.16, stdev=5227.36, samples=4232 lat (nsec) : 500=0.01%, 750=0.01%, 1000=0.01% lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=0.01% lat (usec) : 250=0.05%, 500=0.54%, 750=0.37%, 1000=0.93% lat (msec) : 2=17.40%, 4=58.02%, 10=22.01%, 20=0.60%, 50=0.07% lat (msec) : 100=0.01% cpu : usr=3.29%, sys=7.45%, ctx=1262621, majf=0, minf=103 IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0% submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0% complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.1% issued rwts: total=0,83886080,0,8 short=0,0,0,0 dropped=0,0,0,0 latency : target=0, window=0, percentile=100.00%, depth=128 Run status group 0 (all jobs): WRITE: bw=1237MiB/s (1297MB/s), 1237MiB/s-1237MiB/s (1297MB/s-1297MB/s), io=320GiB (344GB), run=264837-264837msec Disk stats (read/write): sda: ios=36/32868891, merge=0/50979424, ticks=5/27498602, in_queue=1183124, util=100.00% ``` After upgrading to linux-generic-hwe-20.04 kernel and rebooting ``` ubuntu@cloudimg:~$ uname --kernel-release 5.15.0-88-generic ubuntu@cloudimg:~$ sudo fio --ioengine=libaio --blocksize=4k --readwrite=write --filesize=40G --end_fsync=1 --iodepth=128 --direct=1 --group_reporting --numjobs=8 --name=fiojob1 --filename=/dev/sda fiojob1: (g=0): rw=write, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 ... fio-3.16 Starting 8 processes Jobs: 1 (f=1): [_(7),W(1)][100.0%][w=410MiB/s][w=105k IOPS][eta 00m:00s] fiojob1: (groupid=0, jobs=8): err= 0: pid=1438: Thu Nov 2 09:46:49 2023 write: IOPS=155k, BW=605MiB/s (634MB/s)(320GiB/541949msec); 0 zone resets slat (nsec): min=660, max=325426k, avg=10351.04, stdev=232438.50 clat (nsec): min=1100, max=782743k, avg=6595008.67, stdev=6290570.04 lat (usec): min=86, max=782748, avg=6606.08, stdev=6294.03 clat percentiles (usec): | 1.00th=[ 914], 5.00th=[ 2180], 10.00th=[ 2802], 20.00th=[ 3556], | 30.00th=[ 4178]
[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error
I have tried switching to 23.10/beta and installed the pc-kernel snap rev 1506 but the problem is still there -- 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/2034688 Title: installation of kernel headers fail with "Read-only file system" error Status in ubuntu-desktop-installer: Triaged Status in linux package in Ubuntu: In Progress Bug description: Mantic 20230907 Installation of packages that ship files in /lib/modules or /lib/firmware are expected to fail, so their installation must be prevented. For instance: $ apt install linux-headers-generic-6.3.0-7 Reading package lists... Building dependency tree... Reading state information... linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7). The following packages will be upgraded: linux-headers-6.3.0-7-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 51 not fully installed or removed. Need to get 0 B/3,667 kB of archives. After this operation, 27.9 MB of additional disk space will be used. (Reading database ... 132615 files and directories currently installed.) Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ... Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb (--unpack): error creating symbolic link './lib/modules/6.3.0-7-generic/build': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of '/lib/modules/6.3.0-7-generic/build': Read-only file system Errors were encountered while processing: /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+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 2041736] Re: dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2 works)
** Summary changed:
- dm crypt unlock prompt doesn't respond to key presses
+ dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2
works)
** Summary changed:
- dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2
works)
+ [MacbookPro 14,1] dm crypt unlock prompt doesn't respond to key presses in
kernel 6.5 (but 6.2 works)
** Package changed: plymouth (Ubuntu) => linux (Ubuntu)
** Tags added: regression-release
--
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/2041736
Title:
[MacbookPro 14,1] dm crypt unlock prompt doesn't respond to key
presses in kernel 6.5 (but 6.2 works)
Status in linux package in Ubuntu:
New
Bug description:
After upgrading my MacbookPro 14,1 from 23.04 to 23.10 dm-crypt unlock prompt
doesn't respond to key presses and I'm not able to type in my password to
unlock the disk.
The only option that works now is to boot with the kernel left from 23.04
(6.2.0-35-generic).
Any tips to troubleshoot the issue would be much appreciated.
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: plymouth 22.02.122-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 10:25:26 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-04-22 (190 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to mantic on 2023-10-27 (2 days ago)
dmi.bios.date: 08/22/2022
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 499.40.2.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias:
dmi:bvnAppleInc.:bvr499.40.2.0.0:bd08/22/2022:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041736/+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 2041736] [NEW] [MacbookPro 14, 1] dm crypt unlock prompt doesn't respond to key presses in kernel 6.5 (but 6.2 works)
You have been subscribed to a public bug:
After upgrading my MacbookPro 14,1 from 23.04 to 23.10 dm-crypt unlock prompt
doesn't respond to key presses and I'm not able to type in my password to
unlock the disk.
The only option that works now is to boot with the kernel left from 23.04
(6.2.0-35-generic).
Any tips to troubleshoot the issue would be much appreciated.
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename: mantic
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: plymouth 22.02.122-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 10:25:26 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-04-22 (190 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to mantic on 2023-10-27 (2 days ago)
dmi.bios.date: 08/22/2022
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 499.40.2.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias:
dmi:bvnAppleInc.:bvr499.40.2.0.0:bd08/22/2022:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
[MacbookPro 14,1] dm crypt unlock prompt doesn't respond to key presses in
kernel 6.5 (but 6.2 works)
https://bugs.launchpad.net/bugs/2041736
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
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 2019493] Re: Display failure after plugging into thunderbolt dock
I got similar symptom, but with NVIDIA driver and Lenovo Thunderbolt 4 dock. Looks like for it happens after connecting dock back, but screen goes black already when disconnecting from the dock. System info: Linux mopo 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Backtrace: marras 01 14:03:15 mopo kernel: BUG: kernel NULL pointer dereference, address: marras 01 14:03:15 mopo kernel: #PF: supervisor read access in kernel mode marras 01 14:03:15 mopo kernel: #PF: error_code(0x) - not-present page marras 01 14:03:15 mopo kernel: PGD 0 P4D 0 marras 01 14:03:15 mopo kernel: Oops: [#1] PREEMPT SMP NOPTI marras 01 14:03:15 mopo kernel: CPU: 11 PID: 1589 Comm: kworker/u32:11 Tainted: P O 6.2.0-33-generic #33~22.04.1-Ubuntu marras 01 14:03:15 mopo kernel: Hardware name: LENOVO 20YRS21300/20YRS21300, BIOS N37ET46W (1.27 ) 07/12/2023 marras 01 14:03:15 mopo kernel: Workqueue: USBC000:00-con1 ucsi_poll_worker [typec_ucsi] marras 01 14:03:15 mopo kernel: RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] marras 01 14:03:15 mopo kernel: Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54 53 89 f3 e8 73 8b 2a 00 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 7f 3c cc d8 <49> 8b 45 00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 b9 fc ff ff marras 01 14:03:15 mopo kernel: RSP: 0018:b685c2a37d10 EFLAGS: 00010282 marras 01 14:03:15 mopo kernel: RAX: b685c00f5002 RBX: 0002 RCX: marras 01 14:03:15 mopo kernel: RDX: RSI: RDI: b685c00f5002 marras 01 14:03:15 mopo kernel: RBP: b685c2a37d30 R08: R09: marras 01 14:03:15 mopo kernel: R10: R11: R12: a096c33074a8 marras 01 14:03:15 mopo kernel: R13: R14: R15: 000c marras 01 14:03:15 mopo kernel: FS: () GS:a0a1ef6c() knlGS: marras 01 14:03:15 mopo kernel: CS: 0010 DS: ES: CR0: 80050033 marras 01 14:03:15 mopo kernel: CR2: CR3: 000a80410005 CR4: 00770ee0 marras 01 14:03:15 mopo kernel: PKRU: 5554 marras 01 14:03:15 mopo kernel: Call Trace: marras 01 14:03:15 mopo kernel: marras 01 14:03:15 mopo kernel: ? show_regs+0x72/0x90 marras 01 14:03:15 mopo kernel: ? __die+0x25/0x80 marras 01 14:03:15 mopo kernel: ? page_fault_oops+0x79/0x190 marras 01 14:03:15 mopo kernel: ? do_user_addr_fault+0x30c/0x640 marras 01 14:03:15 mopo kernel: ? exc_page_fault+0x81/0x1b0 marras 01 14:03:15 mopo kernel: ? asm_exc_page_fault+0x27/0x30 marras 01 14:03:15 mopo kernel: ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] marras 01 14:03:15 mopo kernel: ucsi_exec_command+0xd9/0xf0 [typec_ucsi] marras 01 14:03:15 mopo kernel: ucsi_send_command+0x4b/0xf0 [typec_ucsi] marras 01 14:03:15 mopo kernel: ucsi_register_altmodes+0xd7/0x210 [typec_ucsi] marras 01 14:03:15 mopo kernel: ucsi_check_altmodes+0x1c/0xb0 [typec_ucsi] marras 01 14:03:15 mopo kernel: ? mutex_lock+0x13/0x50 marras 01 14:03:15 mopo kernel: ucsi_poll_worker+0x3c/0x100 [typec_ucsi] marras 01 14:03:15 mopo kernel: process_one_work+0x21c/0x440 marras 01 14:03:15 mopo kernel: worker_thread+0x50/0x3f0 marras 01 14:03:15 mopo kernel: ? __pfx_worker_thread+0x10/0x10 marras 01 14:03:15 mopo kernel: kthread+0xeb/0x120 marras 01 14:03:15 mopo kernel: ? __pfx_kthread+0x10/0x10 marras 01 14:03:15 mopo kernel: ret_from_fork+0x29/0x50 marras 01 14:03:15 mopo kernel: marras 01 14:03:15 mopo kernel: Modules linked in: ccm rfcomm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_comment nft_compat nf_tables nfnetlink cmac algif_hash overlay algif_skcipher af_alg bnep binfmt_misc dm_crypt nvidia_uvm(PO) snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes nvidia_drm(PO) intel_tcc_cooling nvidia_modeset(PO) snd_hda_codec_realtek x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp coretemp snd_soc_dmic snd_sof_pci_intel_tgl kvm_intel snd_sof_intel_hda_common soundwire_intel kvm soundwire_generic_allocation nvidia(PO) soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp irqbypass snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_compress snd_hda_codec_hdmi ac97_bus marras 01 14:03:15 mopo kernel: snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi iwlmvm snd_usb_audio snd_hda_codec btusb btrtl uvcvideo snd_hda_core snd_usbmidi_lib btbcm mac80211 videobuf2_vmalloc snd_hwdep btintel videobuf2_memops snd_seq_midi processor_thermal_device_pci_legacy libarc4 btmtk intel_rapl_msr videobuf2_v4l2 mei_hdcp me
[Kernel-packages] [Bug 2042868] Re: Kernel 6.2.0-36 broke RTW88 solution
First, you're using an unsupported out-of-tree module, so no promises. Second, we need logs from the failure. Try 'journalctrl -b -1' or something. Adjust the '-1' until you find a log from the 'bad' kernel. Third, is there any reason why you don't use the kernel provided rtw88_8821ce driver? -- 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/2042868 Title: Kernel 6.2.0-36 broke RTW88 solution Status in linux package in Ubuntu: New Bug description: On my Linux Mint (derived from Ubuntu) system, I relied on the excellent rtw88 solution from lwfinger (https://github.com/lwfinger/rtw88) to 'fix' my Realtek Wifi Driver whenever a new kernel comes out. As I understand it, the github repository normally is 'ahead' of any kernels, so if and when I do a 'git pull' of his repository before installing the new rtw88, it should work. And this has worked for quite some time, until the 6.2.0-36 kernel came along. As lwfinger himself (?) states, "Ubuntu often modifies kernel APIs, which can cause build issues. You'll need to manually adjust the source code or look for solutions specific to your distribution. We cannot support these types of issues.", so asking him is not an option. Help? Result from version: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 (Well, this the kernel version in which I have Wifi and thus internet, the 'does not work' kernel is 6.2.0-36, supported till February 2024) Result from lscpi-vnvn (also when running the version that still has internet) as an attachment. Kind regards, Roel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042868/+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 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
Upstream following-up: https://lore.kernel.org/all/20231026123506.26453-1-puliang...@fibocom.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2038259 Title: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: Required fix: https://lore.kernel.org/linux- usb/20230901093610.67438-1-puliang...@fibocom.com To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2038259/+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 2042867] Re: Changing display resolution leads into black screen
It will show up as part of one of our upcoming stable updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042867
Title:
Changing display resolution leads into black screen
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Since updating into 23.10, when I change my build-in display from
2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
black and unable to use.
The only resolution that works is the predefined one.
This bug wasn't present on the previous release, 23.04.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 6 19:37:48 2023
InstallationDate: Installed on 2023-05-05 (185 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
dmi.bios.date: 04/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM5401QAB_UM5401QA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM5401QAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UM5401QAB_UM5401QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042867/+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 2042899] Re: Ubuntu 23.10 Nvidia 535.129.03 external monitor puple tint colour!!
** Package changed: ubuntu => nvidia-graphics-drivers-535 (Ubuntu) ** Tags added: mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042899 Title: Ubuntu 23.10 Nvidia 535.129.03 external monitor puple tint colour!! Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Upgraded Ubuntu to 23.10 to a bad surprise! The external monitor is showing purple tint colour! ``` $ nvidia-smi Tue Nov 7 13:48:08 2023 +---+ | NVIDIA-SMI 535.129.03 Driver Version: 535.129.03 CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA RTX A2000 Laptop GPUOff | :01:00.0 On | N/A | | N/A 57CP5 10W / 60W |815MiB / 4096MiB | 31% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 26704 G /usr/lib/xorg/Xorg 437MiB | |0 N/A N/A 28908C+G ...416580964,443157025533222934,262144 366MiB | +---+ $ dpkg -l |grep -i nvidia ii libaccinj64-12.0:amd6412.0.146~12.0.1-2 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.9.0-3 all NVIDIA C++ Standard Library ii libcublas12:amd64 12.0.2.224~12.0.1-2 amd64NVIDIA cuBLAS Library ii libcublaslt12:amd64 12.0.2.224~12.0.1-2 amd64NVIDIA cuBLASLt Library ii libcudart12:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUDA Runtime Library ii libcufft11:amd64 11.0.1.95~12.0.1-2 amd64NVIDIA cuFFT Library ii libcufftw11:amd64 11.0.1.95~12.0.1-2 amd64NVIDIA cuFFTW Library ii libcuinj64-12.0:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6412.0.146~12.0.1-2 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 12.0.146~12.0.1-2 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti12:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.1.124~12.0.1-2 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.3.1~12.0.1-2 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.3.1~12.0.1-2 amd64NVIDIA cuSOLVERmg Library ii libcusparse12:amd64 12.0.1.140~12.0.1-2 amd64NVIDIA cuSPARSE Library ii libnppc12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives core runtime library ii libnppial12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib
[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
SRU: * https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/90 (oem-6.5) * https://lists.ubuntu.com/archives/kernel-team/2023-November/146756.html (mantic, lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041495 Title: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 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-oem-6.5 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 Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2041495 [Impact] NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: ``` kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ``` [Fix] Proposed fix in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as stable kernels v6.1.55 and v6.5.5. [Test Case] Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. ``` kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues kernel: [2.136735] nvme0n1: p1 p2 p3 ``` [Where problems could occur] This patch tries to set an appropriate CRTO (Controller Ready Timeouts) that may be reported incorrectly by some devices. There should be little (a bit longer CRTO) to no effect on devices performing normally before hands. [Other Info] While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1 will be nominated. == original bug report == NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2042851] Re: kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
5.15.0-60.66-generic is old. Can you try the latest 5.15.0-88.98? -- 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/2042851 Title: kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 Status in linux package in Ubuntu: New Bug description: Laptop may or may not wake up after resume. 2 out of 10 times it will display an error message and become unresponsive: nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type '_Bool Attaching dmesg log file for analysis. === At a minimum every hibernate/resume report should contain responses to each item in this section before being considered Triaged. 1. Is this really a failure? Yes, as machine hangs and becomes unresponsive. 2. Is it reproducible? If not, how often would it be reproducible? I'd say it happens 20% of the time. 3. Did it work before on a prior kernel in the same release, or prior release? Not really sure. I started using the suspend functionality quite recently. 4. Do the symptoms vary at all between hibernation attempts? For example, one time WiFi didn't work, but another a kernel error shows on the screen. It is the same symptoms each time. 5. Do you end up with a flashing Caps Lock light? No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn light on. Only solution is to press power off key. 6. Please advise on how the computer hibernated, and resumed specifically. I suspended it by clicking on the word 'Suspend' in the Gui and then closed the lid. When I opened the lid the computer showed the error. 7. Did the machine break while going into hibernation or waking up? According to the log it broke when suspending. 8. Did you see any error messages leading up to the failure? Nope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+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 2042858] Re: No newer mainline kernel builds
They will be back but mainline builds are not officially supported so closing as '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/2042858 Title: No newer mainline kernel builds Status in linux package in Ubuntu: Invalid Bug description: Hi, no mainline kernel builds have been published since a while, and available builds are a few versions old. Can you do something about this problem ? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042858/+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 2042858] Re: No newer mainline kernel builds
Yes, known issue due to internal infrastructure reshuffling. -- 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/2042858 Title: No newer mainline kernel builds Status in linux package in Ubuntu: Invalid Bug description: Hi, no mainline kernel builds have been published since a while, and available builds are a few versions old. Can you do something about this problem ? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042858/+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 2042899] [NEW] Ubuntu 23.10 Nvidia 535.129.03 external monitor puple tint colour!!
You have been subscribed to a public bug: Upgraded Ubuntu to 23.10 to a bad surprise! The external monitor is showing purple tint colour! ``` $ nvidia-smi Tue Nov 7 13:48:08 2023 +---+ | NVIDIA-SMI 535.129.03 Driver Version: 535.129.03 CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA RTX A2000 Laptop GPUOff | :01:00.0 On | N/A | | N/A 57CP5 10W / 60W |815MiB / 4096MiB | 31% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 26704 G /usr/lib/xorg/Xorg 437MiB | |0 N/A N/A 28908C+G ...416580964,443157025533222934,262144 366MiB | +---+ $ dpkg -l |grep -i nvidia ii libaccinj64-12.0:amd6412.0.146~12.0.1-2 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.9.0-3 all NVIDIA C++ Standard Library ii libcublas12:amd64 12.0.2.224~12.0.1-2 amd64NVIDIA cuBLAS Library ii libcublaslt12:amd64 12.0.2.224~12.0.1-2 amd64NVIDIA cuBLASLt Library ii libcudart12:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUDA Runtime Library ii libcufft11:amd64 11.0.1.95~12.0.1-2 amd64NVIDIA cuFFT Library ii libcufftw11:amd64 11.0.1.95~12.0.1-2 amd64NVIDIA cuFFTW Library ii libcuinj64-12.0:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6412.0.146~12.0.1-2 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 12.0.146~12.0.1-2 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti12:amd64 12.0.146~12.0.1-2 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.1.124~12.0.1-2 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.3.1~12.0.1-2 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.3.1~12.0.1-2 amd64NVIDIA cuSOLVERmg Library ii libcusparse12:amd64 12.0.1.140~12.0.1-2 amd64NVIDIA cuSPARSE Library ii libnppc12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives core runtime library ii libnppial12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei12:amd6412.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig12:amd64 12.0.1.104~12.0.1-2 amd64NVIDIA Performan
[Kernel-packages] [Bug 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041495 Title: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 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-oem-6.5 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 Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2041495 [Impact] NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: ``` kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ``` [Fix] Proposed fix in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as stable kernels v6.1.55 and v6.5.5. [Test Case] Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. ``` kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues kernel: [2.136735] nvme0n1: p1 p2 p3 ``` [Where problems could occur] This patch tries to set an appropriate CRTO (Controller Ready Timeouts) that may be reported incorrectly by some devices. There should be little (a bit longer CRTO) to no effect on devices performing normally before hands. [Other Info] While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1 will be nominated. == original bug report == NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2041495/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Description changed: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] + The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card 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-oem-6.5 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-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
** Description changed: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] - On the device with rt713 codecs: + Device with the soundwire card - !!---Mixer controls for card sofsoundwire - - Card sysdefault:1 'sofsoundwire'/'Intel Soundwire SOF' - Mixer name: 'Intel Meteorlake HDMI' - Components: 'HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic' - Controls : 59 - Simple ctrls : 36 + $ cat /proc/asound/cards + 0 [sofsoundwire ]: sof-soundwire - sof-soundwire + Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' - ; type=BOOLEAN,access=rw--,values=1 - : values=off + ; type=BOOLEAN,access=rw--,values=1 + : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' - ; type=BOOLEAN,access=rw--,values=1 - : values=off - + ; type=BOOLEAN,access=rw--,values=1 + : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' - ; type=BOOLEAN,access=rw--,values=1 - : values=on + ; type=BOOLEAN,access=rw--,values=1 + : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' - ; type=BOOLEAN,access=rw--,values=1 - : values=on + ; type=BOOLEAN,access=rw--,values=1 + : values=on [Where problems could occur] - * This change adds new hardware support. + * This change adds new hardware support. - * The change only adds new hardware support, -it will not affect other codec device. + * The change only adds new hardware support, + it will not affect other codec device. [ Other Info ] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + In progress... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory
[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Tags added: oem-priority originate-from-2033343 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card 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-oem-6.5 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-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (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-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) 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-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) 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 Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Noble) Status: New => Incomplete ** Changed in: linux-oem-6.1 (Ubuntu Noble) Status: Incomplete => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) 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/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 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-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042912/+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 2042888] Re: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.
I suffered same issue after upgrade kernel. When system boots up with SMT enabled, all good in default kernel (5.15.0-43-generic). But error message occurred after upgrade kernel to 6.2.0. core 192 reported as disabled Attempt to enable it fails, resulting the following messages in dmesg: [ 342.156946] smpboot: Booting Node 0 Processor 192 APIC 0x1 [ 352.156658] smpboot: do_boot_cpu failed(-1) to wakeup CPU#192 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2042888 Title: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic. Status in linux-hwe package in Ubuntu: Confirmed Bug description: OS: Ubuntu 22.04.3 LTS Release: 22.04 Kernel: 6.2.0-060200-generic CPU: 1x EPYC 9654 DIMM: 2x Samsung DDR5 16G 1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also tried on kernel 6.5.7-060507) 2.Reboot system and enable SMT-Control from BIOS. 3.Boot to system to read lscpu.txt and dmesg.txt, lscpu log show Off-line CPU(s) info as below: CPU(s): 192 On-line CPU(s) list: 0-95,97-191 Off-line CPU(s) list:96 Vendor ID: AuthenticAMD Model name: AMD EPYC 9654 96-Core Processor CPU family: 25 Model: 17 Thread(s) per core: 2 Core(s) per socket: 96 Socket(s): 1 Stepping:1 Frequency boost: enabled dmesg log show CPU fail info as below, [0.360560] smp: Bringing up secondary CPUs ... [0.360708] x86: Booting SMP configuration: [0.360711] node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 #48 #49 #50 #51 #52 #53 #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 #64 #65 #66 #67 #68 #69 #70 #71 #72 #73 #74 #75 #76 #77 #78 #79 #80 #81 #82 #83 #84 #85 #86 #87 #88 #89 #90 #91 #92 #93 #94 #95 #96 [ 10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96 [ 10.631842] #97 BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2042888/+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 2042912] [NEW] System hang after unplug/plug DP monitor with AMD W7500 card
Public bug reported: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** 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-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New -- 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/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: New Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042912/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel
I don't think that is sufficient for all possible source, meta and binary kernel package incarnations. I need to do some testing. -- 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/2018128 Title: Apport does not collect all logs when the package is HWE kernel Status in apport package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 22.04 LTS with kernel 5.19.0-41-generic When filing bugs against the package 'linux' apport collects all the logs needed to the kernel But in case the user is not on stock kernel anymore and has the HWE kernel apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my case) would it be possible to make apport collect all the logs needed in all kernel cases? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.4 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Apr 29 05:25:30 2023 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
This came indeed in via a cherry-pick made by Ubuntu [0], that was an
early attempt to fix a bug that was actually present in the ceph layer,
as confirmed by the original patch author[1], and fixed actually there
now [2].
[0]: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/commit/?h=master-
prep&id=a53dba9297be9597eac7b17738723bd44bac97ea
[1]:
https://lore.kernel.org/all/8443166a-7182--a489-14b5dab20...@redhat.com/
[2]: https://patchwork.kernel.org/project/ceph-
devel/patch/20221221093031.132792-1-xiu...@redhat.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2041495] Re: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0
oem-6.1 fixed through stable fix in v6.1.55 ** Description changed: + [SRU Justification] + + BugLink: https://bugs.launchpad.net/bugs/2041495 + + [Impact] + + NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: + ``` + kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 + kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A + kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI + kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 + ``` + + [Fix] + + Proposed fix in + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec + "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as + stable kernels v6.1.55 and v6.5.5. + + [Test Case] + + Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. + ``` + kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 + kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A + kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI + kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff + kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds + kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. + kernel: [1.794966] nvme nvme0: 16/0/0 default/read/poll queues + kernel: [2.136735] nvme0n1: p1 p2 p3 + ``` + + [Where problems could occur] + + This patch tries to set an appropriate CRTO (Controller Ready Timeouts) + that may be reported incorrectly by some devices. There should be little + (a bit longer CRTO) to no effect on devices performing normally before + hands. + + [Other Info] + + While this has been in Linus' tree, Mantic/Lunar/oem-6.5 and oem-6.1 + will be nominated. + + == original bug report == + NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041495 Title: Could not probe Samsung P44 30S3 PM9C1a SSD correctly: nvme nvme0: Device not ready: aborting installation, CSTS=0x0 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-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2041495 [Impact] NVME module left unready, therefore not recognized by the installation process, and/or after installation with following error messages: ``` kernel: [ 1.754585] nvme nvme0: pci function 1:e1:00.0 kernel: [ 1.754595] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [ 1.754599] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [ 1.756743] nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 ``` [Fix] Proposed fix in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/core.c?h=v6.5&id=6cc834ba62998c65c42d0c63499bdd35067151ec "nvme: avoid bogus CRTO values", in Linus' tree v6.6 already, as well as stable kernels v6.1.55 and v6.5.5. [Test Case] Apply to kernel and boot with the nvme module installed. Now the device should be probed with success. ``` kernel: [1.731760] nvme nvme0: pci function 1:e1:00.0 kernel: [1.731778] pcieport 1:e0:06.0: can't derive routing for PCI INT A kernel: [1.731780] nvme 1:e1:00.0: PCI INT A: no GSI kernel: [1.731919] nvme nvme0: bad crto:0 cap:800203028033fff kernel: [1.735550] nvme nvme0: Shutdown timeout set to 10 seconds kernel: [1.753865] nvme nvme0: allocated 64 MiB host memory buffer. kernel: [
[Kernel-packages] [Bug 2042888] Re: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2042888 Title: It shows 'smpboot: do_boot_cpu failed(-1) to wakeup CPU#96' in system dmesg log with kernel version 6.2.0-060200-generic. Status in linux-hwe package in Ubuntu: Confirmed Bug description: OS: Ubuntu 22.04.3 LTS Release: 22.04 Kernel: 6.2.0-060200-generic CPU: 1x EPYC 9654 DIMM: 2x Samsung DDR5 16G 1.Install Ubuntu 22.04.3 and upgrade its kernel to 6.2.0-060200-generic (also tried on kernel 6.5.7-060507) 2.Reboot system and enable SMT-Control from BIOS. 3.Boot to system to read lscpu.txt and dmesg.txt, lscpu log show Off-line CPU(s) info as below: CPU(s): 192 On-line CPU(s) list: 0-95,97-191 Off-line CPU(s) list:96 Vendor ID: AuthenticAMD Model name: AMD EPYC 9654 96-Core Processor CPU family: 25 Model: 17 Thread(s) per core: 2 Core(s) per socket: 96 Socket(s): 1 Stepping:1 Frequency boost: enabled dmesg log show CPU fail info as below, [0.360560] smp: Bringing up secondary CPUs ... [0.360708] x86: Booting SMP configuration: [0.360711] node #0, CPUs: #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 #16 #17 #18 #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 #36 #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 #48 #49 #50 #51 #52 #53 #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 #64 #65 #66 #67 #68 #69 #70 #71 #72 #73 #74 #75 #76 #77 #78 #79 #80 #81 #82 #83 #84 #85 #86 #87 #88 #89 #90 #91 #92 #93 #94 #95 #96 [ 10.631524] smpboot: do_boot_cpu failed(-1) to wakeup CPU#96 [ 10.631842] #97 BTW, we also find the same bug on AMD EPYC 9534 64-Core CPU with Ubuntu 22.04.3-kernel 6.2.0 and 6.5.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2042888/+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 2042902] Re: ucm2: soundwire: add rt713 SDCA device
** Description changed: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. + Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] - In progress + On the device with rt713 codecs: + + !!---Mixer controls for card sofsoundwire + + Card sysdefault:1 'sofsoundwire'/'Intel Soundwire SOF' + Mixer name: 'Intel Meteorlake HDMI' + Components: 'HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic' + Controls : 59 + Simple ctrls : 36 + + Before fix: + + 1. $ alsactl init + alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf + alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 + alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 + Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" + Hardware is initialized using a generic method + + 2. $ amixer contents + ... + numid=24,iface=MIXER,name='Headphone Switch' + ; type=BOOLEAN,access=rw--,values=1 + : values=off + ... + numid=33,iface=MIXER,name='IEC958 Playback Switch' + ; type=BOOLEAN,access=rw--,values=1 + : values=off + + + After fix: after adding patch files + + 1. $ alsactl init + alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) + + (note: assuming that failed to remove the empty directory is not a + critical problem) + + 2. $ amixer contents + ... + numid=24,iface=MIXER,name='Headphone Switch' + ; type=BOOLEAN,access=rw--,values=1 + : values=on + ... + numid=33,iface=MIXER,name='IEC958 Playback Switch' + ; type=BOOLEAN,access=rw--,values=1 + : values=on + + [Where problems could occur] + + * This change adds new hardware support. + + * The change only adds new hardware support, +it will not affect other codec device. + + [ Other Info ] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] On the device with rt713 codecs: !!---Mixer controls for card sofsoundwire Card sysdefault:1 'sofsoundwire'/'Intel Soundwire SOF' Mixer name: 'Intel Meteorlake HDMI' Components: 'HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic' Controls : 59 Simple ctrls : 36 Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware s
