[Kernel-packages] [Bug 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Description changed: + [Impact] + No modems were found sometimtes after reboot/poweroff + Got below messages when it fails + + [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) + [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) + [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 + [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) + [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 + [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) + [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 + + [Fix] + Fibocom provides a fix for this issue which is included in linux-next now + https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ + + [Test Case] + 1. Boot to OS. + 2. Insert sim card to the system. + 3. Check the gnome-settings with WWAN settings or check with command mmcli -L + 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well + + [Where problems could occur] + + = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1157 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-stella-jammy-amd64-20231228-670 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 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-3011-oem N/A - linux-backports-modules-6.5.0-3011-oem N/A - linux-firmware 20220329.git681281e4-0ubuntu3.24 + linux-restricted-modules-6.5.0-3011-oem N/A + linux-backports-modules-6.5.0-3011-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP -- 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/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status
[Kernel-packages] [Bug 2051846] Re: Mute/mic LEDs no function on HP ZBook Power
Enabled proposed-2, installed linux-oem-6.5/6.5.0-1015.16 and verified on LONHOR-PV-SKU9_202401-33401, the leds work fine. ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- 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/2051846 Title: Mute/mic LEDs no function on HP ZBook Power Status in OEM Priority Project: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ZBook Power [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2051846/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ v9 has been accepted. ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (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.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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid 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.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 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-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1
[Kernel-packages] [Bug 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.28.
** Tags added: verification-done-jammy
--
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/2034103
Title:
Missing firmware for AMD GPU GC 11.0.3
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Won't Fix
Status in linux-firmware source package in Lunar:
Won't Fix
Bug description:
[Impact]
linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for
Navi32 hardware.
Of the original list below, only VCN fw update is missing still.
[Test case]
Install the update
Validate brightness control works.
Validate that PSR works.
Validate that eDP works after suspend/resume.
Validate that external display works.
[Where problems could happen]
This is new hw, where the current fw isn't fresh enough. It can't
regress other hw.
--
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034103/+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 2054362] Re: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4
** Also affects: linux (Ubuntu Jammy) 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/2054362 Title: ftrace:test.d--kprobe--kprobe_non_uniq_symbol.tc from ubuntu_kselftests_ftrace failed on 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Bug description: Issue found on B-hwe-5.4.0-173.191~18.04.1 This kprobe_non_uniq_symbol.tc test case came from stable update (bug 2049024) and landed in our Focal kernel since Ubuntu-5.4.0-173.191 So this is not a regression, but a new test case. Test log: Running './ftracetest -vvv test.d/kprobe/kprobe_non_uniq_symbol.tc' === Ftrace unit tests === + initialize_ftrace + disable_tracing + echo 0 + reset_tracer + echo nop + reset_trigger + [ -d events/synthetic ] ... + read line ... + read line ... + reset_events_filter + read line ... + reset_ftrace_filter + [ ! -f set_ftrace_filter ] + echo + grep -v ^# set_ftrace_filter + read t + disable_events + echo 0 + [ -f set_event_pid ] + echo + [ -f set_ftrace_pid ] + echo + [ -f set_ftrace_notrace ] + echo + [ -f set_graph_function ] [1] Test failure of registering kprobe on non unique symbol + echo + tee set_graph_function set_graph_notrace + [ -f stack_trace_filter ] + echo + [ -f kprobe_events ] + echo + [ -f uprobe_events ] + echo + [ -f synthetic_events ] + echo + [ -f snapshot ] + echo 0 + clear_trace + echo + enable_tracing + echo 1 + . /home/ubuntu/autotest/client/tmp/ubuntu_kselftests_ftrace/src/linux/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc + SYMBOL=name_show + grep -c -E [[:alnum:]]+ t name_show /proc/kallsyms + [ 14 -le 1 ] + echo p:test_non_unique name_show [FAIL] # of passed: 0 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 I think we're probably missing https://github.com/torvalds/linux/commit/b022f0c7e404887a7c5229788fc99eff9f9a80d5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2054362/+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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Hi R. Diez, The patch was merged upstream in 6.8-rc5: commit 4860abb91f3d7fbaf8147d54782149bb1fc45892 Author: Steve French Date: Tue Feb 6 16:34:22 2024 -0600 Subject: smb: Fix regression in writes when non-standard maximum write size negotiated Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892 I'll work on getting this SRU'd into Ubuntu kernels. Thanks, Matthew -- 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/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb 1.0 mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, etc. An example of a broken file is: https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt [Where problems could occur] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+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 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: Fix Committed Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2054366] Re: Fix backported kria device tree changes
** Description changed: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. - [ Other Info ] + [ Fixes ] + * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported + * 6.1 compatible string for ethernet@ff0b incorrectly backported + * dwc3_[01] quirks incorrectly updated for 6.1 + * xilinx_ams field incorrectly updated. + [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
Hi Sergio, Thanks~ -- 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/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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 2054489] [NEW] Crash on lock screen
Public bug reported:
When my computer locks due to inactivity the screen goes white and
requires a reboot to recover.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 17:29:43 2024
InstallationDate: Installed on 2024-02-02 (19 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
--
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/2054489
Title:
Crash on lock screen
Status in linux package in Ubuntu:
New
Bug description:
When my computer locks due to inactivity the screen goes white and
requires a reboot to recover.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 17:29:43 2024
InstallationDate: Installed on 2024-02-02 (19 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+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 2054489] Re: Crash on lock screen
see attached last boot
** Attachment added: "journalctl-last-boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+attachment/5747880/+files/journalctl-last-boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054489
Title:
Crash on lock screen
Status in linux package in Ubuntu:
New
Bug description:
When my computer locks due to inactivity the screen goes white and
requires a reboot to recover.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 17:29:43 2024
InstallationDate: Installed on 2024-02-02 (19 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon -- 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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: 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: Fix Released 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] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-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.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Tags added: oem-priority originate-from-2054365 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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: 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: Fix Released 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] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Noble will include this commit soon ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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: 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: Fix Released 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] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 2054487] [NEW] There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
Public bug reported: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Fix Released ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** 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: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: Fix Released ** Affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-2054365 somerville ** 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 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 ** 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 -- 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms 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: 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: Fix Released 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] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 1786013] Autopkgtest regression report (linux-meta-azure/6.5.0.1016.18)
All autopkgtests for the newly accepted linux-meta-azure (6.5.0.1016.18) for mantic have finished running. The following regressions have been reported in tests triggered by the package: systemd/253.5-1ubuntu6.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2054483] [NEW] Add headers package for IGX out-of-tree modules
Public bug reported: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Also affects: linux-nvidia-tegra-igx-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx-modules (Ubuntu) Status: New => Fix Committed ** Also affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx-modules (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+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 2054366] Re: Fix backported kria device tree changes
** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: In Progress Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Other Info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu3 --- alsa-ucm-conf (1.2.10-1ubuntu3) noble; urgency=medium * Dropped changes: - d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch - replace it with patches accepted by upstream * Added changes: - d/p/0001-ucm2-MediaTek-mt8390-evk-Add-alsa-ucm-support.patch - d/p/0002-ucm2-MediaTek-mt8395-evk-Add-alsa-ucm-support.patch - d/p/0003-ucm2-MediaTek-mt8370-evk-Add-alsa-ucm-support.patch - d/p/0001-ucm2-conf.d-mt8370-evk-Fix-the-type-of-mt8370-evk.co.patch - d/p/0001-ucm-MediaTek-mt8395-evk-Add-HDMIRX-config.patch - add supports for MediaTek mt8390-evk, mt8395-evk, and mt8370-evk. - fix a file type issue on the mt8370-evk config - add mt8395 HDMI RX support (LP: #2051199) -- Ethan Hsieh Thu, 25 Jan 2024 13:29:18 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Noble) Status: In Progress => Fix Released -- 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/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Released Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
I have verified that all of the patches listed in the description are indeed in the currently 6.8 proposed kernel and should be in 24.04. $ git describe --tags Ubuntu-6.8.0-11.11-1-g04cdb2da2df3 -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 1904265] Re: Deterministic bluetooth disconnects after login and bluetooth restart
Even though I reported this issue already a few years ago, unluckily it is still present. I ignored it in the meanwhile, however I started to locate the problem's cause again. My mouse is a multi-device, so I paired it again using a live Linux (to avoid any inference with the existing paring) but as a separate device. Surprisingly, the issue is not present then. Calling sudo /etc/init.d/bluetooth restart shortly disconnects the mouse (as expected) but thereafter it's working without any freezes. I tried to find out what's different, and comparing the configuration files inside /var/lib/bluetooth// I noticed that the respective 'info' files are not the same. Of course, the keys are different, but besides the, the non-working connection contains the following two sections: [ConnectionParameters] MinInterval=6 MaxInterval=9 Latency=44 Timeout=216 [ServiceChanged] CCC_LE=2 I tried to manually delete these sections, but calling sudo /etc/init.d/bluetooth restart recreates the file including both sections. I suspect that these values were negotiated using the initial pairing under Windows and saved on the mouse itself, therefore Linux uses them, too, were they cause the reconnection issues. Can this information be used to fixed this issue? Can I overwrite this configuration somehow? -- 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/1904265 Title: Deterministic bluetooth disconnects after login and bluetooth restart Status in linux package in Ubuntu: Confirmed Bug description: Hello everyone, a few months ago I upgraded from 18.04 to 20.04 and since then, I'm into some bluetooth connection issues. I'm a KDE user currently using Ubuntu 5.4.0-53.59-generic 5.4.65, still the reported issue also appears with plain ubuntu 20.04, even a clean live USB version of ubuntu 20.04 reproduces it such that it is independent of any KDE library. I've noticed the following bug already a few months ago, still I would like to wait and see if it might be resolved with a new kernel update or something else. Since it still persists, I now would like to report it to the devs. I found no similar reported bug but if it already has been reported, I'd like to excuse for reporting a duplicate. So, I'm using a Logitech bluetooth LE mouse and with ubuntu 18.04 (actually on any distro based on 18.04 that I tested), everything works fine and without any problems. Still with 20.04, I'm into the following bug that I would like to report. After starting ubuntu, the bluetooth connection to the mouse works (i.e. pointer is moving) and after about 30-40 seconds it stops moving and freezes for about 10-15 seconds and thereafter works again and stays working. The same issue can be reproduced by executing (for instance on a live ubuntu) sudo /etc/init.d/bluetooth restart which stops the bluetooth connection for a few seconds (as expected), immediately it works again but after additional 30-40 seconds, the connection breaks for another 10-15 seconds and thereafter works flawlessly. I checked all configuration files from the /etc/bluetooth/ directory, everything is the same between 18.04 and 20.04 and even modifying the parameters does not change anything at all. As a conclusion of my testing I strongly guess it has either anything to do with a different kernel version or a with a changed bluetooth library between 18.04 and 20.04. So in summary: Expected behavior: Bluetooth connection shortly breaks after 'sudo /etc/init.d/bluetooth restart' and does not break again after 30-40 seconds (as it is the case with ubuntu 18.04) Actual behavior: Bluetooth connection breaks again after reestablishing the connection I'm hoping that this issue can easily be fixed and please let me know if you need any further information :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5435 F pulseaudio /dev/snd/controlC2: ubuntu 5435 F pulseaudio /dev/snd/controlC1: ubuntu 5435 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion Gaming Laptop 15-cx0xxx NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash nomodeset --- ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A
[Kernel-packages] [Bug 2051199] Re: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
Hi Ethan, I uploaded the change to Noble. It's better to wait for it to migrate before proceed with the other uploads. Also, this is an Ubuntu Sponsors bug, so I will leave the other uploads to whoever is on the patch pilot shift. Thanks. ** Also affects: alsa-ucm-conf (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Noble) Status: New => 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/2051199 Title: Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: In Progress Bug description: [Impact] Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs. mt8370-evk (G510): https://github.com/alsa-project/alsa-ucm-conf/pull/380 https://github.com/alsa-project/alsa-ucm-conf/commit/a0856afae4e8e071e7626958667cde049ec81e97 mt8390-evk (G700): https://github.com/alsa-project/alsa-ucm-conf/pull/321 https://github.com/alsa-project/alsa-ucm-conf/commit/c5366bdff656092241225d2ad663c3e41b146f8b mt8395-evk (G1200): https://github.com/alsa-project/alsa-ucm-conf/pull/322 https://github.com/alsa-project/alsa-ucm-conf/commit/5e75929e8a487498e24db27023be0b57bac222b0 Fix a file type issue: https://github.com/alsa-project/alsa-ucm-conf/pull/386 https://github.com/alsa-project/alsa-ucm-conf/commit/d864e945ce4171fcaf6249bebec4f683fef0f5cf mt8395-evk (G1200) HDMI RX: https://github.com/alsa-project/alsa-ucm-conf/pull/389 https://github.com/alsa-project/alsa-ucm-conf/commit/1ab2d020d71a570f691fafbd341782fabb6569d1 [Where problems could occur] 1. Patches (LP: #2000228) for mt8390-evk and mt8395-evk merged into Ubuntu archive was rejected by upstream. Replace them with new patches accepted by upstream. 2. Add initial support for mt8370-evk 3. Add mt8395-evk HDMI RX support [Test Case] Verify audio function on MediaTek Genio boards (mt8370-evk, mt8390-evk, and mt8395-evk). 1. Headset Jack Playback 2. Audio (Speaker) Jack Playback 3. mt8395-evk: HDMI RX Play audio by following commands. $ speaker-test -D pulse -c 2 -r 48000 -f S16_LE -t wav [Regression Potential] 1. mt8370-evk: Add initial support for mt8370-evk. There should be no risk. 2. mt8390-evk and mt8395-evk: changes in configs were reviewed by upstream and new configs have been verified by MediaTek. It should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2051199/+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 2052576] Re: GCP TDX Support
This bug is awaiting verification that the linux-gcp/6.5.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-gcp' to 'verification-done-mantic- linux-gcp'. If the problem still exists, change the tag 'verification- needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-gcp-v2 verification-needed-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
This bug is awaiting verification that the linux-azure/6.5.0-1016.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2039720] Re: Intel IDPF support
** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke (Ubuntu Mantic) ** Changed in: linux-gke (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Released Status in linux-gke source package in Jammy: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+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 2051871] Re: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2051871 Title: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This is a cherry-pick fix from upstream to drop Tx network packet when Tx TmFIFO is full. [Fix] Starting from Linux 5.16 kernel, Tx timeout mechanism was added in the virtio_net driver which prints the "Tx timeout" warning message when a packet stays in Tx queue for too long. Below is an example of the reported message: "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since last trans: 3079892256". This issue could happen when external host driver which drains the FIFO is restared, stopped or upgraded. To avoid such confusing "Tx timeout" messages, this commit adds logic to drop the outstanding Tx packet if it's not able to transmit in two seconds due to Tx FIFO full, which can be considered as congestion or out-of-resource drop. This commit also handles the special case that the packet is half- transmitted into the Tx FIFO. In such case, the packet is discarded with remaining length stored in vring->rem_padding. So paddings with zeros can be sent out when Tx space is available to maintain the integrity of the packet format. The padded packet will be dropped on the receiving side. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2051871/+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 2052479] Re: apply nvidia-tegra patches 2024 Jan 16-Feb 5
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (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/2052479 Title: apply nvidia-tegra patches 2024 Jan 16-Feb 5 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra and linux-nvida-tegra-igx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2052479/+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 2054452] [NEW] Longhorn rwx nfs mount issue - Protocol not supported
Public bug reported: Hello, I'm experiencing issues with longhorn rwx feature on k3s cluster since upgrade to kernel 5.15.0-1046-raspi The symptom are exactly the same as the one describe on longhorn KB (https://longhorn.io/kb/troubleshooting-rwx-volume-fails-to-attached- caused-by-protocol-not-supported/) My version deployed on my rasberry pi root@my-pi:~$ uname -a Linux my-pi 5.15.0-1046-raspi #49-Ubuntu SMP PREEMPT Thu Jan 18 12:45:41 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux Mount request (with options) root@my-pi:~$ sudo mount -t nfs -o vers=4.2,noresvport,softerr,timeo=600,retrans=5 XX.XX.XX.XX:/pvc-UID /mnt/nfs -vvv mount.nfs: timeout set for Tue Feb 20 11:00:38 2024 mount.nfs: trying text-based options 'vers=4.2,noresvport,softerr,timeo=600,retrans=5,proto=tcp,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Mount request (without options) root@my-pi:~$mount -t nfs XX.XX.XX.XX:/pvc-UID /mnt/nfs -vvv mount.nfs: timeout set for Tue Feb 20 11:02:29 2024 mount.nfs: trying text-based options 'vers=4.2,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /lib/systemd/system/rpc-statd.service. mount.nfs: trying text-based options 'addr=XX.XX.XX.XX' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 13, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: Protocol not supported On another node (not using RPI) I had same issue with kernel linux- image-5.15.0-94-generic.Downgrading to kernel linux- image-5.15.0-92-generic solved the issue. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/2054452 Title: Longhorn rwx nfs mount issue - Protocol not supported Status in linux-raspi package in Ubuntu: New Bug description: Hello, I'm experiencing issues with longhorn rwx feature on k3s cluster since upgrade to kernel 5.15.0-1046-raspi The symptom are exactly the same as the one describe on longhorn KB (https://longhorn.io/kb/troubleshooting-rwx-volume-fails-to-attached- caused-by-protocol-not-supported/) My version deployed on my rasberry pi root@my-pi:~$ uname -a Linux my-pi 5.15.0-1046-raspi #49-Ubuntu SMP PREEMPT Thu Jan 18 12:45:41 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux Mount request (with options) root@my-pi:~$ sudo mount -t nfs -o vers=4.2,noresvport,softerr,timeo=600,retrans=5 XX.XX.XX.XX:/pvc-UID /mnt/nfs -vvv mount.nfs: timeout set for Tue Feb 20 11:00:38 2024 mount.nfs: trying text-based options 'vers=4.2,noresvport,softerr,timeo=600,retrans=5,proto=tcp,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: Protocol not supported Mount request (without options) root@my-pi:~$mount -t nfs XX.XX.XX.XX:/pvc-UID /mnt/nfs -vvv mount.nfs: timeout set for Tue Feb 20 11:02:29 2024 mount.nfs: trying text-based options 'vers=4.2,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'vers=4,addr=XX.XX.XX.XX,clientaddr=YY.YY.YY.YY' mount.nfs: mount(2): Protocol not supported Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /lib/systemd/system/rpc-statd.service. mount.nfs: trying text-based options 'addr=XX.XX.XX.XX' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 13, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: Protocol not supported On another node (not using RPI) I had same issue with kernel linux- image-5.15.0-94-generic.Downgrading to kernel linux- image-5.15.0-92-generic solved the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2054452/+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 2054447] Re: Title: System Freeze Post Suspend with Browser and Sensor App Open
Here are my logs from the time of the issue. Thank you very much for
your kind consideration.
** Attachment added: "logs_crash_broad.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054447/+attachment/5747722/+files/logs_crash_broad.txt
--
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/2054447
Title:
Title: System Freeze Post Suspend with Browser and Sensor App Open
Status in linux package in Ubuntu:
New
Bug description:
I've encountered a recurring system freeze issue on my Ubuntu machine.
The system was left unattended with two instances of Firefox open, one
on ChatGPT and another on Coursera, as well as the hardware sensor
notification program running. Upon returning and resuming from
suspend, I was able to log in, but the system was entirely
unresponsive. Ctrl-Alt-Delete resulted in a system reboot. This issue
had ceased occurring for about a week but has now reappeared.
Previously, similar freezes would occur, but Ctrl-Alt-Delete led to a
black screen requesting login details, necessitating a forced
shutdown. There is a possibility that the open applications may be
contributing to the freezing issue, although the problem had paused
for several days before returning, which is puzzling. This
intermittent nature of the problem adds complexity to pinpointing the
exact cause.
Steps to Reproduce:
1. Leave the system idle with Firefox open on ChatGPT and Coursera.
2. Run the hardware sensor notification program.
3. Enter system suspend state.
4. Resume from suspend after an extended period.
5. Attempt to interact with the system post-login.
Expected Result:
The system should resume from suspend and allow normal operation without
freezing.
Actual Result:
The system becomes unresponsive after resuming from suspend, requiring a
reboot via Ctrl-Alt-Delete or, in previous instances, necessitating a forced
shutdown after a black screen appears.
Additional Information:
- Occurrences have been intermittent, with a period of one week where the
issue did not manifest.
- The problem may be related to the system suspend/resume process,
potentially exacerbated by the running applications at the time of suspend.
This summary should provide a concise and clear description of the
issue for a bug report, outlining the problem, the steps to reproduce
it, and the unexpected behavior experienced.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: qd91 2735 F wireplumber
/dev/snd/seq:qd91 2715 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 16:32:25 2024
InstallationDate: Installed on 2024-02-08 (12 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb 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-17-generic N/A
linux-backports-modules-6.5.0-17-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-02-10 (11 days ago)
dmi.bios.date: 11/10/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0772C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
dmi.product.family: Latitude
dmi.product.name: Latitude 5420
dmi.product.sku: 0A20
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054447/+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 2054447] [NEW] Title: System Freeze Post Suspend with Browser and Sensor App Open
Public bug reported:
I've encountered a recurring system freeze issue on my Ubuntu machine.
The system was left unattended with two instances of Firefox open, one
on ChatGPT and another on Coursera, as well as the hardware sensor
notification program running. Upon returning and resuming from suspend,
I was able to log in, but the system was entirely unresponsive. Ctrl-
Alt-Delete resulted in a system reboot. This issue had ceased occurring
for about a week but has now reappeared.
Previously, similar freezes would occur, but Ctrl-Alt-Delete led to a
black screen requesting login details, necessitating a forced shutdown.
There is a possibility that the open applications may be contributing to
the freezing issue, although the problem had paused for several days
before returning, which is puzzling. This intermittent nature of the
problem adds complexity to pinpointing the exact cause.
Steps to Reproduce:
1. Leave the system idle with Firefox open on ChatGPT and Coursera.
2. Run the hardware sensor notification program.
3. Enter system suspend state.
4. Resume from suspend after an extended period.
5. Attempt to interact with the system post-login.
Expected Result:
The system should resume from suspend and allow normal operation without
freezing.
Actual Result:
The system becomes unresponsive after resuming from suspend, requiring a reboot
via Ctrl-Alt-Delete or, in previous instances, necessitating a forced shutdown
after a black screen appears.
Additional Information:
- Occurrences have been intermittent, with a period of one week where the issue
did not manifest.
- The problem may be related to the system suspend/resume process, potentially
exacerbated by the running applications at the time of suspend.
This summary should provide a concise and clear description of the issue
for a bug report, outlining the problem, the steps to reproduce it, and
the unexpected behavior experienced.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-17-generic 6.5.0-17.17
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: qd91 2735 F wireplumber
/dev/snd/seq:qd91 2715 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 16:32:25 2024
InstallationDate: Installed on 2024-02-08 (12 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic
root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb 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-17-generic N/A
linux-backports-modules-6.5.0-17-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-02-10 (11 days ago)
dmi.bios.date: 11/10/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0772C9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd11/10/2023:br1.33:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:
dmi.product.family: Latitude
dmi.product.name: Latitude 5420
dmi.product.sku: 0A20
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
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/2054447
Title:
Title: System Freeze Post Suspend with Browser and Sensor App Open
Status in linux package in Ubuntu:
New
Bug description:
I've encountered a recurring system freeze issue on my Ubuntu machine.
The system was left unattended with two instances of Firefox open, one
on ChatGPT and another on Coursera, as well as the hardware sensor
notification program running. Upon returning and resuming from
suspend, I was able to log in, but the system was entirely
unresponsive. Ctrl-Alt-Delete resulted in a system reboot. This issue
had ceased occurring for about a week but has now reappeared.
Previously, similar freezes would occur, but Ctrl-Alt-Delete led to a
black screen requesting login details, necessitating a forced
shutdown. There is a possibility that the open applications may be
contributing to the freezing issue, although the problem had paused
for several days before returning, which is puzzling. This
intermittent nature of the problem adds complexity to pinpointing
[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2054439] Re: RM obsolete binaries from noble to allow linux to migrate
Proceed with the removal of linux-modules-ipu6-oem-22.04, linux-modules- ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules- nvidia-450-oem-20.04 from noble and noble-proposed, please. ** Changed in: linux (Ubuntu Noble) Status: Incomplete => Confirmed -- 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/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+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 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
** Information type changed from Private to Public -- 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/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: New Bug description: [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+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 2044657] Re: Multiple data corruption issues in zfs
I struggle to reproduce the issue on focal with v5.4 and
0.8.3-1ubuntu12.16 zfs
but also see no regressions with the proposed 12.17 update.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 2054442] [NEW] Include the Support of AMD Turin Processor for Ubuntu 24.04
Private bug reported: Include the Support of AMD Turin Processor for Ubuntu 24.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- 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/2054442 Title: Include the Support of AMD Turin Processor for Ubuntu 24.04 Status in linux package in Ubuntu: New Bug description: Include the Support of AMD Turin Processor for Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054442/+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 2054439] Re: RM obsolete binaries from noble to allow linux to migrate
unless linux-meta is buggy and produces non-installable packages -- 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/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+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 2054439] [NEW] RM obsolete binaries from noble to allow linux to migrate
Public bug reported: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) 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/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Ping, would love to see this resolved. dmi-sysfs has no firmware dependency and as such should be a good fit for linux-modules instead of linux-modules-extra. The same goes for qemu-fw-cfg as well actually which also isn't a part of linux-modules. -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+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 2054434] [NEW] firmware-sof-signed last version
Public bug reported: Hi! I have gpd pocket 3 with essx8336 audio card. In 22.04 and event in noble https://packages.ubuntu.com/search?keywords=firmware-sof-signed there is old version of driver 2.2.6, with this driver audio doesn't work. But esx3886 has latest firmware, for example https://packages.debian.org/firmware-sof-signed 2023.12-1 with this driver audio works fine. I don't know, when I tried debian 12 - with audio everything was ok (but I didn't check version of driver) Could you add latest driver, 2023, or used with debian 12? ** Affects: firmware-sof (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2054434 Title: firmware-sof-signed last version Status in firmware-sof package in Ubuntu: New Bug description: Hi! I have gpd pocket 3 with essx8336 audio card. In 22.04 and event in noble https://packages.ubuntu.com/search?keywords=firmware-sof-signed there is old version of driver 2.2.6, with this driver audio doesn't work. But esx3886 has latest firmware, for example https://packages.debian.org/firmware-sof-signed 2023.12-1 with this driver audio works fine. I don't know, when I tried debian 12 - with audio everything was ok (but I didn't check version of driver) Could you add latest driver, 2023, or used with debian 12? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2054434/+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 2054387] Re: Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Tags added: amdgpu radeon regression-update -- 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/2054387 Title: Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel. Status in linux package in Ubuntu: New Bug description: Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel. It is working good till version linux- image-5.15.0-84-generic (currently using). after this version able to boot system only in recovery mode. (currently installed: linux- image-5.15.0-94-generic) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 11:25:37 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-10 (862 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054387/+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 2054387] [NEW] Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel.
You have been subscribed to a public bug: Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel. It is working good till version linux-image-5.15.0-84-generic (currently using). after this version able to boot system only in recovery mode. (currently installed: linux-image-5.15.0-94-generic) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-94.104-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 11:25:37 2024 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-10 (862 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- Facing display issue (not sure if it is related to display. Display distortion and shows distorted lines) on booting after upgrading to new kernel. https://bugs.launchpad.net/bugs/2054387 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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
** Merge proposal linked: https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/460810 -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Released Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2054411] [NEW] Jammy update: v5.15.147 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.147 upstream stable release from git://git.kernel.org/ block: Don't invalidate pagecache for invalid falloc modes ALSA: hda/realtek: Fix mute and mic-mute LEDs for HP ProBook 440 G6 Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()" wifi: iwlwifi: pcie: don't synchronize IRQs from IRQ drm/bridge: ti-sn65dsi86: Never store more than msg->size bytes in AUX xfer nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local octeontx2-af: Fix marking couple of structure as __packed drm/i915/dp: Fix passing the correct DPCD_REV for drm_dp_set_phy_test_pattern i40e: Fix filter input checks to prevent config with invalid values igc: Report VLAN EtherType matching back to user igc: Check VLAN TCI mask igc: Check VLAN EtherType mask ASoC: fsl_rpmsg: Fix error handler with pm_runtime_enable mlxbf_gige: fix receive packet race condition net: sched: em_text: fix possible memory leak in em_text_destroy() r8169: Fix PCI error on system resume net: Implement missing getsockopt(SO_TIMESTAMPING_NEW) can: raw: add support for SO_TXTIME/SCM_TXTIME can: raw: add support for SO_MARK net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init sfc: fix a double-free bug in efx_probe_filters net: bcmgenet: Fix FCS generation for fragmented skbuffs netfilter: nft_immediate: drop chain reference counter on error net: Save and restore msg_namelen in sock_sendmsg i40e: fix use-after-free in i40e_aqc_add_filters() ASoC: meson: g12a-toacodec: Validate written enum values ASoC: meson: g12a-tohdmitx: Validate written enum values ASoC: meson: g12a-toacodec: Fix event generation ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux i40e: Restore VF MSI-X state during PCI reset igc: Fix hicredit calculation net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues octeontx2-af: Don't enable Pause frames by default octeontx2-af: Set NIX link credits based on max LMAC octeontx2-af: Always configure NIX TX link credits based on max frame size octeontx2-af: Re-enable MAC TX in otx2_stop processing asix: Add check for usbnet_get_endpoints bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() net: Implement missing SO_TIMESTAMPING_NEW cmsg support selftests: secretmem: floor the memory size to the multiple of page_size mm/memory-failure: check the mapcount of the precise page firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and ASM108x/VT630x PCIe cards x86/kprobes: fix incorrect return address calculation in kprobe_emulate_call_indirect i2c: core: Fix atomic xfer check for non-preempt config mm: fix unmap_mapping_range high bits shift bug mmc: meson-mx-sdhc: Fix initialization frozen issue mmc: rpmb: fixes pause retune on all RPMB partitions. mmc: core: Cancel delayed work before releasing host mmc: sdhci-sprd: Fix eMMC init failure after hw reset ipv6: remove max_size check inline with ipv4 perf inject: Fix GEN_ELF_TEXT_OFFSET for jit kallsyms: Make module_kallsyms_on_each_symbol generally available tracing/kprobes: Fix symbol counting logic by looking at modules as well net: usb: ax88179_178a: remove redundant init code net: usb: ax88179_178a: move priv to driver_priv Linux 5.15.147 UBUNTU: Upstream stable to v5.15.147 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Manuel Diewald (diewald) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Manuel Diewald (diewald) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the
[Kernel-packages] [Bug 2054406] [NEW] Focal update: v5.4.267 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.267 upstream stable release from git://git.kernel.org/ nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local i40e: Fix filter input checks to prevent config with invalid values net: sched: em_text: fix possible memory leak in em_text_destroy() can: raw: add support for SO_TXTIME/SCM_TXTIME can: raw: add support for SO_MARK net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init net: bcmgenet: Fix FCS generation for fragmented skbuffs net: Save and restore msg_namelen in sock_sendmsg i40e: fix use-after-free in i40e_aqc_add_filters() ASoC: meson: g12a: extract codec-to-codec utils UBUNTU: [Config] Update annotations for CONFIG_SND_MESON_CODEC_GLUE ASoC: meson: g12a-tohdmitx: Validate written enum values ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux i40e: Restore VF MSI-X state during PCI reset net/qla3xxx: switch from 'pci_' to 'dma_' API net/qla3xxx: fix potential memleak in ql_alloc_buffer_queues asix: Add check for usbnet_get_endpoints bnxt_en: Remove mis-applied code from bnxt_cfg_ntp_filters() net: Implement missing SO_TIMESTAMPING_NEW cmsg support mm/memory-failure: check the mapcount of the precise page firewire: ohci: suppress unexpected system reboot in AMD Ryzen machines and ASM108x/VT630x PCIe cards i2c: core: Fix atomic xfer check for non-preempt config mm: fix unmap_mapping_range high bits shift bug mmc: rpmb: fixes pause retune on all RPMB partitions. mmc: core: Cancel delayed work before releasing host mmc: sdhci-sprd: Fix eMMC init failure after hw reset ath10k: Wait until copy complete is actually done before completing ath10k: Add interrupt summary based CE processing ath10k: Keep track of which interrupts fired, don't poll them ath10k: Get rid of "per_ce_irq" hw param PCI: Extract ATS disabling to a helper function PCI: Disable ATS for specific Intel IPU E2000 devices net/dst: use a smaller percpu_counter batch for dst entries accounting ipv6: make ip6_rt_gc_expire an atomic_t ipv6: remove max_size check inline with ipv4 ASoC: meson: codec-glue: fix pcm format cast warning Linux 5.4.267 UBUNTU: Upstream stable to v5.4.267 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Manuel Diewald (diewald) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Manuel Diewald (diewald) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.267 upstream stable release from git://git.kernel.org/ - + nfc: llcp_core: Hold a ref to llcp_local->dev when holding a ref to llcp_local + i40e: Fix filter input checks to prevent config with invalid values + net: sched: em_text: fix possible memory leak in em_text_destroy() + can: raw: add support for SO_TXTIME/SCM_TXTIME + can: raw: add support for SO_MARK + net-timestamp: extend SOF_TIMESTAMPING_OPT_ID to HW timestamps + ARM: sun9i: smp: Fix array-index-out-of-bounds read in sunxi_mc_smp_init + net: bcmgenet: Fix FCS generation for fragmented skbuffs + net: Save and restore msg_namelen in sock_sendmsg + i40e: fix use-after-free in i40e_aqc_add_filters() + ASoC: meson: g12a: extract codec-to-codec utils + UBUNTU: [Config] Update annotations for CONFIG_SND_MESON_CODEC_GLUE + ASoC: meson: g12a-tohdmitx: Validate written enum values + ASoC: meson: g12a-tohdmitx: Fix event generation for S/PDIF mux + i40e: Restore VF MSI-X state during PCI reset + net/qla3xxx: switch from 'pci_' to 'dma_' API + net/qla3xxx: fix
