[Kernel-packages] [Bug 2000414] Re: package linux-firmware 1.187.35 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Disk failure:
[ 152.032214] ata1.00: exception Emask 0x0 SAct 0x88193 SErr 0x5 action 0x0
[ 152.032237] ata1.00: irq_stat 0x4001
[ 152.032244] ata1: SError: { PHYRdyChg CommWake }
[ 152.032258] ata1.00: failed command: READ FPDMA QUEUED
[ 152.032265] ata1.00: cmd 60/00:00:e0:80:c9/01:00:17:00:00/40 tag 0 ncq dma
131072 in
res 41/40:00:e0:80:c9/00:01:17:00:00/40 Emask 0x409
(media error)
[ 152.032290] ata1.00: status: { DRDY ERR }
[ 152.032298] ata1.00: error: { UNC }
[ 152.032307] ata1.00: failed command: READ FPDMA QUEUED
--
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/2000414
Title:
package linux-firmware 1.187.35 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned
error exit status 1
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
package linux-firmware 1.187.35 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned
error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.35
ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ansa 1358 F pulseaudio
CasperMD5CheckResult: skip
Date: Sat Dec 24 18:10:20 2022
Dependencies:
ErrorMessage: installed linux-firmware package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2022-08-29 (116 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 14-3468
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic
root=UUID=a6869efe-e649-4bf1-a802-2daa06df7a01 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.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
SourcePackage: linux-firmware
Title: package linux-firmware 1.187.35 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned error exit
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2020
dmi.bios.release: 3.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.6.0
dmi.board.name: 0VCX0K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr3.6.0:bd06/30/2020:br3.6:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0VCX0K:rvrA00:cvnDellInc.:ct9:cvr:sku0792:
dmi.product.family: Vostro
dmi.product.name: Vostro 14-3468
dmi.product.sku: 0792
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2000414/+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 2000169] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: unable to stat './lib/firmware/vsc/soc_a1_prod/ivsc_fw.bin' (which was about to be
Your disk is having problems: [ 216.089815] blk_update_request: critical medium error, dev nvme0n1, sector 727593536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 216.089823] EXT4-fs warning (device nvme0n1p6): ext4_dx_find_entry:1771: inode #4588013: lblock 2: comm dpkg: error -5 reading directory block [ 233.790484] blk_update_request: critical medium error, dev nvme0n1, sector 727593536 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 233.790501] EXT4-fs warning (device nvme0n1p6): ext4_dx_find_entry:1771: inode #4588013: lblock 2: comm apport-gtk: error -5 reading directory block [ 233.793995] blk_update_request: critical medium error, dev nvme0n1, sector 727593528 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 [ 233.794014] EXT4-fs warning (device nvme0n1p6): ext4_dx_find_entry:1771: inode #4588013: lblock 1: comm apport-gtk: error -5 reading directory block ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2000169 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: unable to stat './lib/firmware/vsc/soc_a1_prod/ivsc_fw.bin' (which was about to be installed): Erro de entrada/saída Status in linux-firmware package in Ubuntu: Invalid Bug description: I can't update the system because of the problem "linux-firmware" ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dilson10 2009 F pulseaudio CasperMD5CheckResult: pass Date: Tue Dec 20 13:41:40 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu4 ErrorMessage: unable to stat './lib/firmware/vsc/soc_a1_prod/ivsc_fw.bin' (which was about to be installed): Erro de entrada/saída InstallationDate: Installed on 2022-04-24 (240 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 012: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=5fa462fc-1380-45a4-b5c5-39c0c071a359 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. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: unable to stat './lib/firmware/vsc/soc_a1_prod/ivsc_fw.bin' (which was about to be installed): Erro de entrada/saída UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2019 dmi.bios.release: 1.38 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.ec.firmware.release: 1.38 dmi.modalias: dmi:bvnLENOVO:bvrASCN38WW:bd08/15/2019:br1.38:efr1.38:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:skuLENOVO_MT_81S9_BU_idea_FM_IdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2000169/+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 2000133] Re: amdgpu: missing firmware for navi31
** Tags added: kern-5238 -- 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/2000133 Title: amdgpu: missing firmware for navi31 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: Won't Fix Status in linux-firmware source package in Lunar: Triaged Bug description: [5.232972] amdgpu :03:00.0: Direct firmware load for amdgpu/psp_13_0_0_sos.bin failed with error -2 [5.232974] amdgpu :03:00.0: amdgpu: failed to init sos firmware [5.232975] [drm:psp_sw_init [amdgpu]] *ERROR* Failed to load psp firmware! [5.233097] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 [5.233232] amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed [5.233233] amdgpu :03:00.0: amdgpu: Fatal error during GPU init [5.233235] amdgpu :03:00.0: amdgpu: amdgpu: finishing device. [5.233459] amdgpu: probe of :03:00.0 failed with error -2 The following new firmware binaries are introduced to linux- firmware.git. 31c57349 amdgpu: add VCN 4.0.0 firmware for amd-5.4 a7351589 amdgpu: add SMU 13.0.0 firmware for amd-5.4 0bef6bb1 amdgpu: Add SDMA 6.0.0 firmware for amd-5.4 bb56d1a7 amdgpu: add PSP 13.0.0 firmware for amd-5.4 e32209f0 amdgpu: add GC 11.0.0 firmware for amd-5.4 613db81f amdgpu: add DCN 3.2.0 firmware for amd-5.4 These are all needed for supporting navi31 dGPU. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1573 F pulseaudio /dev/snd/controlC1: gdm1573 F pulseaudio CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4 [origin: Ubuntu] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish+X12 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-19 (124 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 MachineType: Intel Corporation Raptor Lake Client Platform Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1009-oem root=UUID=1513ef0d-bc45-444e-906e-d81039e5f411 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1009.9-oem 6.0.9 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.0.0-1009-oem N/A linux-backports-modules-6.0.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy third-party-packages Uname: Linux 6.0.0-1009-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/29/2022 dmi.bios.vendor: Intel Corporation dmi.bios.version: RPLSFWI1.R00.3047.A00.2201290228 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RPL-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnIntelCorporation:bvrRPLSFWI1.R00.3047.A00.2201290228:bd01/29/2022:efr1.51:svnIntelCorporation:pnRaptorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRPL-SADP-SDDR5UDIMMCRB:rvr1:cvnIntelCorporation:ct3:cvr0.1:sku11390001: dmi.product.family: Raptor Lake Client System dmi.product.name: Raptor Lake Client Platform dmi.product.sku: 11390001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000133/+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 2000700] Re: Resolve problem with mainline builds
The problem with mainline builds is that a) kernel configs handling has changed and b) checker scripts have moved to a subdirectory. Our mainline build scripts 'disable' the checker scripts but since they moved that no longer happens, hence the error you're seeing. I'm working on it. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Critical => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- 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/2000700 Title: Resolve problem with mainline builds Status in linux package in Ubuntu: Confirmed Bug description: [Impact] No able to build mainline kernel (6.1/6.1.1). [Test Case] Log available https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.1.1/amd64/log. For local builds: $ git clone --branch cod/mainline/v6.1.1 --depth 1 git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack kernel $ cd kernel $ LANG=C fakeroot debian/rules clean $ LANG=C fakeroot debian/rules binary-headers binary-generic binary-perarch Problem Description == I can see problems with checking of signatures during building of mainline kernel, for example https://kernel.ubuntu.com/~kernel- ppa/mainline/v6.1.1/amd64/log: ... II: Checking signature of staging modules for generic... II: Use signature inclusion file(s): /home/kernel/COD/linux/debian/scripts/checks/../../../debian/signature-inclusion II: Checking modules directory: debian/linux-modules-6.1.1-060101-generic FAIL (signed) : fb_agm1264k-fl.ko FAIL (signed) : fb_bd663474.ko ... It looks like in case of CONFIG_MODULE_SIG_ALL we sign all modules, we should take it into account. After fixing that problem I found another one: II: Checking for ABI changes... Traceback (most recent call last): File "/data/CLionProjects/mainline-crack/debian/scripts/checks/abi-check", line 108, in if vals['loc'] != vals['old']['loc']: KeyError: 'loc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000700/+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 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works) Status in linux package in Ubuntu: Fix Released Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+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 1994144] [NEW] External display monitor not recognized
You have been subscribed to a public bug: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge same ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 08:45:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:899b] InstallationDate: Installed on 2022-10-24 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn2xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 899B dmi.board.vendor: HP dmi.board.version: 06.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.26 dmi.modalias: dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn2xxx dmi.product.sku: 641G6UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy multimonitor ubuntu -- External display monitor not recognized https://bugs.launchpad.net/bugs/1994144 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 1994485] [NEW] Suspend screen bug Gnome and Gnome with video card AMD RX6500XT
You have been subscribed to a public bug: Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 26 09:35:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug kinetic wayland-session -- Suspend screen bug Gnome and Gnome with video card AMD RX6500XT https://bugs.launchpad.net/bugs/1994485 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 1994485] Re: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT
In comment #6 it looks like gnome-shell is stuck on a bug in the amdgpu kernel driver. But I should have been able to tell that from the beginning... дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2186, emitted seq=2188 дек 23 17:09:14 d-3600xt-22 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1818 thread gnome-shel:cs0 pid 1835 дек 23 17:09:14 d-3600xt-22 kernel: amdgpu :0c:00.0: amdgpu: GPU reset begin! ** Tags added: amdgpu ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994485 Title: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT Status in linux package in Ubuntu: Incomplete Bug description: Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 26 09:35:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 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/1994485/+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 1994144] Re: External display monitor not recognized
Sounds like a kernel issue. Please run this command to see what ports the kernel thinks are connected: grep . /sys/class/drm/*/status ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994144 Title: External display monitor not recognized Status in linux package in Ubuntu: Incomplete Bug description: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge same ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 08:45:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:899b] InstallationDate: Installed on 2022-10-24 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn2xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 899B dmi.board.vendor: HP dmi.board.version: 06.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.26 dmi.modalias: dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn2xxx dmi.product.sku: 641G6UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994144/+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 1995682] [NEW] gnome session freeze when open settings
You have been subscribed to a public bug: gnome session freeze when open settings and do some operation e.g scroll down by mouse wheel to the bottom of the pannel ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Nov 4 16:01:04 2022 SourcePackage: gnome-session UpgradeStatus: Upgraded to kinetic on 2022-09-07 (58 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug kinetic -- gnome session freeze when open settings https://bugs.launchpad.net/bugs/1995682 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 1999731] Re: disk stress test failing with code 7
Thanks cking and David, I am running 0.11.07-1ubuntu2 from archive, 0.14.06-0~202210291239~ubuntu20.04.1 from ppa:hardware- certification/public and 0.15.01-1~f1 from ppa:colin-king/stress-ng with 5.4.0-135.152 kernel to see if stress-ng version matters. If not, next step is to test on kernels. -- 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/1999731 Title: disk stress test failing with code 7 Status in Stress-ng: In Progress Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: In Progress Bug description: Since mid of November we see lots of disk stress test failing with multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them are with lockofd stressor and system are still alive after stress test. 05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds... ** stress-ng exited with code 7 To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1999731/+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 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect
** No longer affects: bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995329 Title: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect Status in linux package in Ubuntu: Confirmed Bug description: Recently upgraded to 22.10 (from I believe 20.04, not actually completely sure) and both of my Bluetooth devices have stopped working. They can pair and connect initially, but disconnect after 4-5 seconds. My headphones worked a while, but have not since been able to have them stay connected. Here's an output from bluetoothctl, which doesn't say much? Agent registered [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D TxPower: -21 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00 ...1..t@ 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 87 04 02 48 e2 09 0e 30 0b 11 7a .H...0..z [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -39 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [NEW] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 88 b5 06 90 44 00 8d e6 00 11 30 ..D.0 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device 94:DB:56:4F:20:7F Connected: yes [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device 94:DB:56:4F:20:7F Connected: no [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [bluetooth]# [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value: 04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00 ...1..t` 00 00 00 ... [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: fe2c--1000-8000-00805f9b34fb [CHG] Device CB:78:4F:E1:45:7D ServiceData Value: 00 90 14 08 8e 2b 3a 42 02 89 00 11 74 .+:Bt [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -35 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -36 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [DEL] Device D9:A2:A2:B7:40:35 P mesh [CHG] Device CB:78:4F:E1:45:7D RSSI: -38 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 [CHG] Device CB:78:4F:E1:45:7D RSSI: -37 Seems all
[Kernel-packages] [Bug 1994485] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1994485 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994485 Title: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT Status in linux package in Ubuntu: Incomplete Bug description: Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 26 09:35:26 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 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/1994485/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Sorry for the delay - it was a long end of year break. As a sanity test I am currently waiting for the bug to happen in vanilla lunar (5.19.0-21-generic) but it hasn't happened yet... I can't say whether any new kernel has fixed it if the original problem isn't happening on the old kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Committed Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be 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-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.b
[Kernel-packages] [Bug 1995682] Re: gnome session freeze when open settings
*** This bug is a duplicate of bug 1998950 ***
https://bugs.launchpad.net/bugs/1998950
I see...
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GPU HANG: ecode
12:1:84db, in gnome-control-c [5686]
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] Resetting chip
for stopped heartbeat on rcs0
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] gnome-shell[4227]
context reset due to GPU hang
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm]
gnome-control-c[5686] context reset due to GPU hang
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC firmware
i915/adlp_guc_70.1.1.bin version 70.1
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] HuC firmware
i915/tgl_huc_7.9.3.bin version 7.9
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] HuC authenticated
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC submission
enabled
12月 15 16:08:08 y9000x-nul kernel: i915 :00:02.0: [drm] GuC SLPC enabled
** Package changed: gnome-session (Ubuntu) => linux (Ubuntu)
** This bug has been marked a duplicate of bug 1998950
GPU hang on Alder Lake laptop
--
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/1995682
Title:
gnome session freeze when open settings
Status in linux package in Ubuntu:
Incomplete
Bug description:
gnome session freeze when open settings and do some operation e.g
scroll down by mouse wheel to the bottom of the pannel
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Nov 4 16:01:04 2022
SourcePackage: gnome-session
UpgradeStatus: Upgraded to kinetic on 2022-09-07 (58 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995682/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
The fix is landed in linux-firmware version: Ubuntu-20220923.gitf09bebf3-0ubuntu1.2 Ubuntu-20220923.gitf09bebf3-0ubuntu1.3 ** Tags added: verification-done-kinetic -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 2000805] Re: rtl8156B loaded with wrong driver and not working
From https://lore.kernel.org/netdev/1e6d7b8c3af444ae900fd4248f2a9...@realtek.com/ There are three configurations for RTL8156. config #1: vendor mode (r8152) config #2: NCM mode (cdc_ncm) config #3: ECM mode (cdc_ether) The USB core selects config #2 for default, so cdc_ncm is loaded. If you plan to use vendor mode, you have to switch the configuration to config #1. For example, echo 1 > /sys/bus/usb/devices/2-7/bConfigurationValue So this does not seem to be considered a kernel bug. -- 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/2000805 Title: rtl8156B loaded with wrong driver and not working Status in linux package in Ubuntu: Incomplete Bug description: I have a 2.5G USB Ethernet dongle that use the Realtek 8156B chipset. The default driver being loaded are cdc_mbim and cdc_ncm, but this driver (cdc_ncm) is an incorrect driver that does not work with the chip. Instead, I have to manually load the r8152 driver to make it work; I cannot blacklist cdc_ncm as I am also using it with other devices. Current Platform: Ubuntu 22.04.1, kernel 5.15.0-56-lowlatency Reproducible: always Expects: plugging in the USB dongle will have correct driver loaded, and just work Steps to fix: --- rmmod cdc_mbim rmmod cdc_ncm rmmod cdc_ether modprobe r8152 echo 0bda 8156 > /sys/bus/usb/drivers/r8152/new_id --- reference links: https://forum.manjaro.org/t/no-carrier-network-link-problem-with-usb-2-5-gbit-lan-adapter-realtek-rtl8156b-on-x86-64/97195 https://lore.kernel.org/netdev/20211227182124.5cbc0...@kicinski-fedora-pc1c0hjn.hsd1.ca.comcast.net/#t To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000805/+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 2000909] [NEW] Microphone mute LED not working as expected after pressing the mic mute hotkey
Public bug reported: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Incomplete => In Progress -- 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/2000909 Title: Microphone mute LED not working as expected after pressing the mic mute hotkey Status in linux package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: New Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem To manage notifications about this bug go to: https:/
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.15/5.15.0.1024.29~20.04.1)
All autopkgtests for the newly accepted linux-meta-gke-5.15 (5.15.0.1024.29~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gke-5.15/5.15.0-1024.29~20.04.1 (amd64, arm64) systemd/245.4-4ubuntu3.19 (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/focal/update_excuses.html#linux-meta-gke-5.15 [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 packing 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 2000909] Re: Microphone mute LED not working as expected after pressing the mic mute hotkey
** Changed in: linux (Ubuntu Lunar) Status: New => In Progress -- 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/2000909 Title: Microphone mute LED not working as expected after pressing the mic mute hotkey Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000909/+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 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
** Summary changed:
- Soundwire support for the Intel RPL Gen platforms -- follow-ups
+ Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/230
Title:
Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
Status in firmware-sof package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
New
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
New
Status in firmware-sof source package in Lunar:
New
Status in linux source package in Lunar:
Incomplete
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
This is a follow-up to bug 1997944 that supports more RPL gen
platforms.
Staging fixes:
*
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
*
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+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 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
SRU: https://lists.ubuntu.com/archives/kernel-
team/2023-January/135814.html (unstable/lunar/oem-6.1/oem-6.0)
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => High
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Missing support for two additional product model of Intel RPL Gen
+ Soundwire.
+
+ [Fix]
+
+ Two additional commits merged in upstream sof development repository on
+ GitHub.
+
+ [Test Case]
+
+ Apply the two changes along with an alsa ucm conf fix, then perform audio
+ automatic/manual checkbox tests.
+
+ [Where problems could occur]
+
+ New hardware. No known issue so far, but might have minor issues in the
+ future.
+
+ [Other Info]
+
+ Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug 1997944.
+
+ == original bug report ==
+
This is a follow-up to bug 1997944 that supports more RPL gen platforms.
Staging fixes:
*
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
*
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
** No longer affects: firmware-sof (Ubuntu Lunar)
** No longer affects: firmware-sof (Ubuntu Jammy)
** No longer affects: firmware-sof (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/230
Title:
Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing support for two additional product model of Intel RPL Gen
Soundwire.
[Fix]
Two additional commits merged in upstream sof development repository
on GitHub.
[Test Case]
Apply the two changes along with an alsa ucm conf fix, then perform audio
automatic/manual checkbox tests.
[Where problems could occur]
New hardware. No known issue so far, but might have minor issues in
the future.
[Other Info]
Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug
1997944.
== original bug report ==
This is a follow-up to bug 1997944 that supports more RPL gen
platforms.
Staging fixes:
*
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
*
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/230/+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 2000792] Re: Source not compile because of missing overlays directory
Well, you're downloading the Debian source package so you need to build it like a Debian package and not like an upstream kernel. I.e. simply using 'make' won't work. See https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/2000792 Title: Source not compile because of missing overlays directory Status in linux-raspi package in Ubuntu: Invalid Bug description: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' The error message: scripts/Makefile.build:44: arch/arm64/boot/dts/overlays/Makefile: No such file or directory make[2]: *** No rule to make target 'arch/arm64/boot/dts/overlays/Makefile'. Stop. make[1]: *** [scripts/Makefile.build:560: arch/arm64/boot/dts/overlays] Error 2 make: *** [Makefile:1442: dtbs] Error 2 Comment: The whole overlay directory is missing Host/Target/Build: RPi4 - aarch64-linux-gnu - Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2000792/+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-aws/5.19.0.1015.12)
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1015.12) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: systemd/251.4-1ubuntu7 (amd64, 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/kinetic/update_excuses.html#linux-meta-aws [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 packing 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 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107&id=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+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 1930921] Re: Apache 2.4.41 corrupts files from samba share
According to the Debian bug this seems to be a bug in linux and not in samba and apache2. ** Changed in: apache2 (Ubuntu) Status: Incomplete => Invalid ** Changed in: samba (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in samba package in Ubuntu: Invalid Status in Debian: Fix Released Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+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 1999491] Re: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.9 --- linux-firmware (20220329.git681281e4-0ubuntu3.9) jammy; urgency=medium * Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821 (LP: #1999491) - linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098 linux-firmware (20220329.git681281e4-0ubuntu3.8) jammy; urgency=medium * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) * New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468) - amdgpu: update DMCUB firmware for DCN 3.1.6 -- Juerg Haefliger Tue, 13 Dec 2022 10:34:26 +0100 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1999491 Title: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821. [Fix] Use the updated firmware for rtl8821c to fix issue. [Test] 1. Prepare two Ubuntu 22.04 systems with Realtek 8821. 2. Open Bluetooth Settings and launch research available device automatically. 3. Found this two systems are visible in research list for connection, Bluetooth connection can be established normally without problem. [Where problems could occur] It's binary so anything would happen. [Other Info] This firmware has existed in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1999491] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1999491 Title: Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821. [Fix] Use the updated firmware for rtl8821c to fix issue. [Test] 1. Prepare two Ubuntu 22.04 systems with Realtek 8821. 2. Open Bluetooth Settings and launch research available device automatically. 3. Found this two systems are visible in research list for connection, Bluetooth connection can be established normally without problem. [Where problems could occur] It's binary so anything would happen. [Other Info] This firmware has existed in Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999491/+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 1998468] Re: New DMCUB FW for AMD amdgpu DCN 3.1.6
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.9
---
linux-firmware (20220329.git681281e4-0ubuntu3.9) jammy; urgency=medium
* Fix The Bluetooth connection cannot be established between two Ubuntu 22.04
systems with Realtek 8821 (LP: #1999491)
- linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098
linux-firmware (20220329.git681281e4-0ubuntu3.8) jammy; urgency=medium
* Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
* New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468)
- amdgpu: update DMCUB firmware for DCN 3.1.6
-- Juerg Haefliger Tue, 13 Dec 2022
10:34:26 +0100
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/1998468
Title:
New DMCUB FW for AMD amdgpu DCN 3.1.6
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Kinetic:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Multiple issues in DP alt mode, PSR-SU(Panel Self Refresh–Selective
Update), and HDMI signal integrity.
[Fix]
Upstream commit b0f995cd61cd ("amdgpu: update DMCUB firmware for DCN
3.1.6") that updates binary firmware.
[Test Case]
Can only be verified with dedicated equipment from vendor.
[Where problems could occur]
Binary firmware, everything can go wrong.
[Other Info]
Already in korg upstream, included in Lunar, too. Only Jammy and
Kinetic will be nominated for fix.
== original bug report ==
Some fixes for DP alt mode and PSR-SU(Panel Self Refresh–Selective
Update), and also improve HDMI signal integrity. This FW would be
tuning PHY of HDMI to enhance signal integrity in eye diagram to reach
HDMI spec(2.0/1.4b), and also avoid any risk on monitor with multiple
resolutions over HDMI output.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=b0f995cd61cd29e7eee1dc22aeeacb2eadc21227
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998468/+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 1998468] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1998468
Title:
New DMCUB FW for AMD amdgpu DCN 3.1.6
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Kinetic:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Multiple issues in DP alt mode, PSR-SU(Panel Self Refresh–Selective
Update), and HDMI signal integrity.
[Fix]
Upstream commit b0f995cd61cd ("amdgpu: update DMCUB firmware for DCN
3.1.6") that updates binary firmware.
[Test Case]
Can only be verified with dedicated equipment from vendor.
[Where problems could occur]
Binary firmware, everything can go wrong.
[Other Info]
Already in korg upstream, included in Lunar, too. Only Jammy and
Kinetic will be nominated for fix.
== original bug report ==
Some fixes for DP alt mode and PSR-SU(Panel Self Refresh–Selective
Update), and also improve HDMI signal integrity. This FW would be
tuning PHY of HDMI to enhance signal integrity in eye diagram to reach
HDMI spec(2.0/1.4b), and also avoid any risk on monitor with multiple
resolutions over HDMI output.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=b0f995cd61cd29e7eee1dc22aeeacb2eadc21227
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1998468/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.9 --- linux-firmware (20220329.git681281e4-0ubuntu3.9) jammy; urgency=medium * Fix The Bluetooth connection cannot be established between two Ubuntu 22.04 systems with Realtek 8821 (LP: #1999491) - linux-firmware: rtl_bt: Update RTL8821C BT(USB I/F) FW to 0x75b8_f098 linux-firmware (20220329.git681281e4-0ubuntu3.8) jammy; urgency=medium * Mediatek WLAN RZ616(MT7922) SAR table control (LP: #1997200) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) * New DMCUB FW for AMD amdgpu DCN 3.1.6 (LP: #1998468) - amdgpu: update DMCUB firmware for DCN 3.1.6 -- Juerg Haefliger Tue, 13 Dec 2022 10:34:26 +0100 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26
[Kernel-packages] [Bug 1997200] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+subscriptions -- Mailing list: https://launchpad.net/~kern
[Kernel-packages] [Bug 2000299] Re: Fix W6400 hang after resume of S3 stress
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AaronMa (mapengyu) -- 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/2000299 Title: Fix W6400 hang after resume of S3 stress Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] amdgpu hang when stress S3 on AMD W6400 GPU. [Fix] Add a WA to manually adjust strobe calculation using FCLK restrict. [Test] Suspend AMD W6400 for 40 times, it works fine. [Where problems could occur] Low risk, upstream fix. It may cause AMD GPU hang. The patch is in 5.16, only Jammy kernel needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000299/+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 2000947] [NEW] UVC Quanta 0408:4035 camera PROBLEM
Public bug reported: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: module uvcvideo ** Patch added: "logs and uvc_drive.c files" https://bugs.launchpad.net/bugs/2000947/+attachment/5638957/+files/uvc%20camera.zip -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: New Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2
[Kernel-packages] [Bug 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
** Changed in: linux-oem-6.0 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/230
Title:
Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing support for two additional product model of Intel RPL Gen
Soundwire.
[Fix]
Two additional commits merged in upstream sof development repository
on GitHub.
[Test Case]
Apply the two changes along with an alsa ucm conf fix, then perform audio
automatic/manual checkbox tests.
[Where problems could occur]
New hardware. No known issue so far, but might have minor issues in
the future.
[Other Info]
Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug
1997944.
== original bug report ==
This is a follow-up to bug 1997944 that supports more RPL gen
platforms.
Staging fixes:
*
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
*
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/230/+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 1996093] Re: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154
** Changed in: linux-azure-4.15 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996093 Title: [RELEASE BLOCKER] Call trace during nvme storage performance test in bionic/linux-azure 4.15.0-1154 Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Bug description: SRU Justification [Impact] Hypervisor only allocates interrupts to happen on a single physical GPU, which can lead to CPU soft locks when using PCI NVME under heavy load. [Test Case] Microsoft tested [Where things could go wrong] Hypervisor PCI driver may not load correctly. Patch did not apply cleanly and could lead to merge conflicts once the upstream patch is pulled in. [Other Info] SF: #00347669 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996093/+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 2000397] [NEW] Port in LACP not forward packets after restart one switch in stack - Intel x520 (ixgbe)
You have been subscribed to a public bug: We have several servers connected to stack switches. The servers have 2 x X520's and are connected 2x10GB(bonding). After restarting one switch in the stack, the port that flaped not forwarded packets except for arp(one way) and LACP is UP on two ports. The problem occurs when the restarted switch returns and LACP will be connected. LACP works incorrect and some packets are sent with a problematic link and they do not reach their destination. We are seeing a lot of packet loss because of this. If you disable this port, the problem does not occur, if I enable it again, the problem returns. Restarting the server or reloading the network driver solves the problem until the switch is restarted, e.g. during a switch upgrade. Do you have any idea how to solve this problem or how to debug it? -- # cat /etc/netplan/01-netcfg.yaml bonds: bond0: mtu: 9000 macaddress: 90:e2:ba:c9:b6:34 interfaces: [ens1f0, ens2f0] parameters: mode: 802.3ad bond1: mtu: 9000 macaddress: 90:e2:ba:c9:b6:35 interfaces: [ens1f1, ens2f1] parameters: mode: 802.3ad # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal uname -a Linux server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # dpkg -l | grep bonding ii ifenslave2.9ubuntu1 all configure network interfaces for parallel routing (bonding) # modinfo ixgbe filename: /lib/modules/5.4.0-26-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:5.1.0-k license:GPL v2 description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: 436CCBE2A80978751F572E6 # cat /proc/net/bonding/bond1 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: 3c:ec:ef:38:3b:4a Active Aggregator Info: Aggregator ID: 1 Number of ports: 2 Actor Key: 15 Partner Key: 5953 Partner Mac Address: 7c:1c:f1:88:33:31 Slave Interface: ens2f1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 90:e2:ba:c9:b6:35 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: 3c:ec:ef:38:3b:4a port key: 15 port priority: 255 port number: 1 port state: 61 details partner lacp pdu: system priority: 32768 system mac address: 7c:1c:f1:88:33:31 oper key: 5953 port priority: 32768 port number: 23 port state: 61 Slave Interface: ens1f1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: f8:f2:1e:12:be:65 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: 3c:ec:ef:38:3b:4a port key: 15 port priority: 255 port number: 2 port state: 61 details partner lacp pdu: system priority: 32768 system mac address: 7c:1c:f1:88:33:31 oper key: 5953 port priority: 32768 port number: 108 port state: 61 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Port in LACP not forward packets after restart one switch in stack - Intel x520 (ixgbe) https://bugs.launchpad.net/bugs/2000397 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 1990167] Re: cma alloc failure in large 5.15 arm instances
The patch didn't get dropped, it was actually applied to jammy/linux- azure instead of AWS. ** Changed in: linux-aws (Ubuntu Jammy) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Jammy: In Progress Status in linux-aws source package in Kinetic: Invalid Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+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 2000089] [NEW] Emulex FC driver fails to start HBA
You have been subscribed to a public bug: Starting from linux hwe 5.15.0-53-generic ( and newer ) emulex FC ( lpfc ) is no longer able to start the fibre channel on HPE ProLiant BL460c Gen10/ProLiant BL460c Gen10, BIOS I41 07/14/2022: [Wed Dec 14 21:32:01 2022] Call Trace: [Wed Dec 14 21:32:01 2022] [Wed Dec 14 21:32:01 2022] __const_udelay+0x40/0x50 [Wed Dec 14 21:32:01 2022] lpfc_sli4_wait_bmbx_ready+0x58/0x80 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli4_post_sync_mbox+0xd4/0x4c0 [lpfc] [Wed Dec 14 21:32:01 2022] ? __kmalloc+0x1ab/0x4b0 [Wed Dec 14 21:32:01 2022] lpfc_sli_issue_mbox_s4+0x58a/0x7d0 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_issue_mbox+0xf/0x20 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_pci_function_reset+0xb9/0x270 [lpfc] [Wed Dec 14 21:32:01 2022] ? raw_pci_write+0x27/0x50 [Wed Dec 14 21:32:01 2022] lpfc_sli4_brdreset+0x120/0x220 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_brdrestart_s4+0x4a/0x160 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_brdrestart+0x12/0x20 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_reset_hba+0x3c/0xa0 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_mbox_timeout_handler.cold+0x13f/0x14e [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_work_done+0x1c3/0x830 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_do_work+0x5b/0x1a0 [lpfc] [Wed Dec 14 21:32:01 2022] ? wait_woken+0x60/0x60 [Wed Dec 14 21:32:01 2022] ? lpfc_work_done+0x830/0x830 [lpfc] [Wed Dec 14 21:32:01 2022] kthread+0x127/0x150 [Wed Dec 14 21:32:01 2022] ? set_kthread_struct+0x50/0x50 [Wed Dec 14 21:32:01 2022] ret_from_fork+0x1f/0x30 [Wed Dec 14 21:32:01 2022] [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: start 7 end 79 cnt 72 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 7: [ 44.922753] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 8: [ 44.922758] 0:(0):0339 Abort xri x0, original iotag x800, abort cmd iotag x7ff retval x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 9: [ 44.922761] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 10: [ 44.922764] 0:(0):0011 Free RPI x0 on ndlp: x9fb44f3be800 did xfe [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 11: [ 44.922768] 0:(0):0211 DSM in event xc on NPort xfe in state 0 rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 12: [ 44.922770] 0:(0):0212 DSM out state 0 on NPort xfe rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 13: [ 44.922772] 0:(0):0211 DSM in event xb on NPort xfe in state 0 rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 14: [ 44.922775] 0:(0):0212 DSM out state 255 on NPort xfe rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 15: [ 45.030383] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 16: [ 45.030396] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 17: [ 45.030397] 0:0460 Bring Adapter offline [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 18: [ 45.030399] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 19: [ 45.046420] 0:1236 Moving 66 buffers from pbl_pool[0] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 20: [ 45.046430] 0:1237 Moving 0 buffers from pvt_pool[0] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 21: [ 45.046432] 0:1236 Moving 66 buffers from pbl_pool[1] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 22: [ 45.046442] 0:1237 Moving 0 buffers from pvt_pool[1] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 23: [ 45.046444] 0:1236 Moving 66 buffers from pbl_pool[2] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 24: [ 45.046454] 0:1237 Moving 0 buffers from pvt_pool[2] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 25: [ 45.046455] 0:1236 Moving 66 buffers from pbl_pool[3] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 26: [ 45.046465] 0:1237 Moving 0 buffers from pvt_pool[3] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 27: [ 45.046466] 0:1236 Moving 66 buffers from pbl_pool[4] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 28: [ 45.046476] 0:1237 Moving 0 buffers from pvt_pool[4] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 29: [ 45.046477] 0:1236 Moving 66 buffers from pbl_pool[5] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 30: [ 45.046489] 0:1237 Moving 0 buffers from pvt_pool[5] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 31: [ 45.046490] 0:1236 Moving 66 buffers from pbl_pool[6] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 32: [ 45.046499] 0:1237 Moving 0 buffers from pvt_pool[6] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 33: [ 45.046500] 0:1236 Moving 66 buffers from pbl_pool[7] TO PUT list [Wed Dec 14
[Kernel-packages] [Bug 2000397] Re: Port in LACP not forward packets after restart one switch in stack - Intel x520 (ixgbe)
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000397 Title: Port in LACP not forward packets after restart one switch in stack - Intel x520 (ixgbe) Status in linux package in Ubuntu: New Bug description: We have several servers connected to stack switches. The servers have 2 x X520's and are connected 2x10GB(bonding). After restarting one switch in the stack, the port that flaped not forwarded packets except for arp(one way) and LACP is UP on two ports. The problem occurs when the restarted switch returns and LACP will be connected. LACP works incorrect and some packets are sent with a problematic link and they do not reach their destination. We are seeing a lot of packet loss because of this. If you disable this port, the problem does not occur, if I enable it again, the problem returns. Restarting the server or reloading the network driver solves the problem until the switch is restarted, e.g. during a switch upgrade. Do you have any idea how to solve this problem or how to debug it? -- # cat /etc/netplan/01-netcfg.yaml bonds: bond0: mtu: 9000 macaddress: 90:e2:ba:c9:b6:34 interfaces: [ens1f0, ens2f0] parameters: mode: 802.3ad bond1: mtu: 9000 macaddress: 90:e2:ba:c9:b6:35 interfaces: [ens1f1, ens2f1] parameters: mode: 802.3ad # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal uname -a Linux server 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # dpkg -l | grep bonding ii ifenslave2.9ubuntu1 all configure network interfaces for parallel routing (bonding) # modinfo ixgbe filename: /lib/modules/5.4.0-26-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:5.1.0-k license:GPL v2 description:Intel(R) 10 Gigabit PCI Express Network Driver author: Intel Corporation, srcversion: 436CCBE2A80978751F572E6 # cat /proc/net/bonding/bond1 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: 3c:ec:ef:38:3b:4a Active Aggregator Info: Aggregator ID: 1 Number of ports: 2 Actor Key: 15 Partner Key: 5953 Partner Mac Address: 7c:1c:f1:88:33:31 Slave Interface: ens2f1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 90:e2:ba:c9:b6:35 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: 3c:ec:ef:38:3b:4a port key: 15 port priority: 255 port number: 1 port state: 61 details partner lacp pdu: system priority: 32768 system mac address: 7c:1c:f1:88:33:31 oper key: 5953 port priority: 32768 port number: 23 port state: 61 Slave Interface: ens1f1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: f8:f2:1e:12:be:65 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: 3c:ec:ef:38:3b:4a port key: 15 port priority: 255 port number: 2 port state: 61 details partner lacp pdu: system priority: 32768 system mac address: 7c:1c:f1:88:33:31 oper key: 5953 port priority: 32768 port number: 108 port state: 61 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000397/+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 2000089] Re: Emulex FC driver fails to start HBA
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/289 Title: Emulex FC driver fails to start HBA Status in linux package in Ubuntu: New Bug description: Starting from linux hwe 5.15.0-53-generic ( and newer ) emulex FC ( lpfc ) is no longer able to start the fibre channel on HPE ProLiant BL460c Gen10/ProLiant BL460c Gen10, BIOS I41 07/14/2022: [Wed Dec 14 21:32:01 2022] Call Trace: [Wed Dec 14 21:32:01 2022] [Wed Dec 14 21:32:01 2022] __const_udelay+0x40/0x50 [Wed Dec 14 21:32:01 2022] lpfc_sli4_wait_bmbx_ready+0x58/0x80 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli4_post_sync_mbox+0xd4/0x4c0 [lpfc] [Wed Dec 14 21:32:01 2022] ? __kmalloc+0x1ab/0x4b0 [Wed Dec 14 21:32:01 2022] lpfc_sli_issue_mbox_s4+0x58a/0x7d0 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_issue_mbox+0xf/0x20 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_pci_function_reset+0xb9/0x270 [lpfc] [Wed Dec 14 21:32:01 2022] ? raw_pci_write+0x27/0x50 [Wed Dec 14 21:32:01 2022] lpfc_sli4_brdreset+0x120/0x220 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_brdrestart_s4+0x4a/0x160 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_sli_brdrestart+0x12/0x20 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_reset_hba+0x3c/0xa0 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_mbox_timeout_handler.cold+0x13f/0x14e [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_work_done+0x1c3/0x830 [lpfc] [Wed Dec 14 21:32:01 2022] lpfc_do_work+0x5b/0x1a0 [lpfc] [Wed Dec 14 21:32:01 2022] ? wait_woken+0x60/0x60 [Wed Dec 14 21:32:01 2022] ? lpfc_work_done+0x830/0x830 [lpfc] [Wed Dec 14 21:32:01 2022] kthread+0x127/0x150 [Wed Dec 14 21:32:01 2022] ? set_kthread_struct+0x50/0x50 [Wed Dec 14 21:32:01 2022] ret_from_fork+0x1f/0x30 [Wed Dec 14 21:32:01 2022] [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: start 7 end 79 cnt 72 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 7: [ 44.922753] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 8: [ 44.922758] 0:(0):0339 Abort xri x0, original iotag x800, abort cmd iotag x7ff retval x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 9: [ 44.922761] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 10: [ 44.922764] 0:(0):0011 Free RPI x0 on ndlp: x9fb44f3be800 did xfe [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 11: [ 44.922768] 0:(0):0211 DSM in event xc on NPort xfe in state 0 rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 12: [ 44.922770] 0:(0):0212 DSM out state 0 on NPort xfe rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 13: [ 44.922772] 0:(0):0211 DSM in event xb on NPort xfe in state 0 rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 14: [ 44.922775] 0:(0):0212 DSM out state 255 on NPort xfe rpi x Data: x0 x4 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 15: [ 45.030383] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 16: [ 45.030396] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 17: [ 45.030397] 0:0460 Bring Adapter offline [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 18: [ 45.030399] 0:(0):0248 Cancel Discovery Timer state x0 Data: x90010 x0 x0 [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 19: [ 45.046420] 0:1236 Moving 66 buffers from pbl_pool[0] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 20: [ 45.046430] 0:1237 Moving 0 buffers from pvt_pool[0] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 21: [ 45.046432] 0:1236 Moving 66 buffers from pbl_pool[1] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 22: [ 45.046442] 0:1237 Moving 0 buffers from pvt_pool[1] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 23: [ 45.046444] 0:1236 Moving 66 buffers from pbl_pool[2] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 24: [ 45.046454] 0:1237 Moving 0 buffers from pvt_pool[2] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 25: [ 45.046455] 0:1236 Moving 66 buffers from pbl_pool[3] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 26: [ 45.046465] 0:1237 Moving 0 buffers from pvt_pool[3] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 27: [ 45.046466] 0:1236 Moving 66 buffers from pbl_pool[4] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 28: [ 45.046476] 0:1237 Moving 0 buffers from pvt_pool[4] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 29: [ 45.046477] 0:1236 Moving 66 buffers from pbl_pool[5] TO PUT list [Wed Dec 14 21:32:09 2022] lpfc :37:00.2: 30: [ 45.046489] 0:1237 Moving 0 buffers from pvt_pool[5] TO PUT
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
** Tags added: patch -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: New Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+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 2001545] [NEW] i915: repetable Kernel Oops after resuming from standby
Public bug reported: I have an Intel i915 Haswell system which - after upgrading from Ubuntu 20.04 to 22.04 - experiences repeated crashes when resuming from hibernation. Unfortunately, "ubuntu-bug" claims my kernel package is "not an official package" (which is untrue, at least to my knowledge - I installed from the official sources) so I cannot use 'ubuntu-bug'. $ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 I will attach the lspci output. This is the dmesg trace: Jan 3 17:16:33 linuxkiste kernel: [164294.599802] BUG: unable to handle page fault for address: e2fc5108 Jan 3 17:16:33 linuxkiste kernel: [164294.599809] #PF: supervisor read access in kernel mode Jan 3 17:16:33 linuxkiste kernel: [164294.599811] #PF: error_code(0x) - not-present page Jan 3 17:16:33 linuxkiste kernel: [164294.599813] PGD 0 P4D 0 Jan 3 17:16:33 linuxkiste kernel: [164294.599815] Oops: [#1] SMP PTI Jan 3 17:16:33 linuxkiste kernel: [164294.599818] CPU: 1 PID: 93586 Comm: chrome Tainted: G OE 5.15.0-56-generic #62-Ubuntu Jan 3 17:16:33 linuxkiste kernel: [164294.599820] Hardware name: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015 Jan 3 17:16:33 linuxkiste kernel: [164294.599822] RIP: 0010:kfree+0x68/0x250 Jan 3 17:16:33 linuxkiste kernel: [164294.599827] Code: 80 49 01 dc 0f 82 f2 01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d Jan 3 17:16:33 linuxkiste kernel: [164294.599829] RSP: 0018:b98e88c47930 EFLAGS: 00010286 Jan 3 17:16:33 linuxkiste kernel: [164294.599831] RAX: 6bf38000 RBX: 40c0 RCX: 00392c14 Jan 3 17:16:33 linuxkiste kernel: [164294.599833] RDX: b98e8000 RSI: a04d669e RDI: 40c0 Jan 3 17:16:33 linuxkiste kernel: [164294.599834] RBP: b98e88c47970 R08: R09: Jan 3 17:16:33 linuxkiste kernel: [164294.599835] R10: 940e24fc1000 R11: 940e090c5ad4 R12: e2fc5100 Jan 3 17:16:33 linuxkiste kernel: [164294.599836] R13: 000a R14: R15: 0230 Jan 3 17:16:33 linuxkiste kernel: [164294.599837] FS: 7f3c96764340() GS:94100ea8() knlGS: Jan 3 17:16:33 linuxkiste kernel: [164294.599839] CS: 0010 DS: ES: CR0: 80050033 Jan 3 17:16:33 linuxkiste kernel: [164294.599840] CR2: e2fc5108 CR3: 0001f49d8001 CR4: 001706e0 Jan 3 17:16:33 linuxkiste kernel: [164294.599842] Call Trace: Jan 3 17:16:33 linuxkiste kernel: [164294.599843] Jan 3 17:16:33 linuxkiste kernel: [164294.599845] kvfree+0x2e/0x40 Jan 3 17:16:33 linuxkiste kernel: [164294.599850] eb_relocate_parse_slow+0x133/0x470 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.599937] eb_relocate_parse+0x129/0x1b0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.69] i915_gem_do_execbuffer+0x373/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600083] ? __alloc_pages+0x311/0x330 Jan 3 17:16:33 linuxkiste kernel: [164294.600088] ? i915_memcpy_init_early+0x40/0x40 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600140] i915_gem_execbuffer2_ioctl+0x12e/0x280 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600200] ? i915_gem_do_execbuffer+0xba0/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600256] drm_ioctl_kernel+0xb3/0x100 [drm] Jan 3 17:16:33 linuxkiste kernel: [164294.600290] drm_ioctl+0x268/0x4b0 [drm] Jan 3 17:16:33 linuxkiste kernel: [164294.600308] ? i915_gem_do_execbuffer+0xba0/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600367] ? __check_object_size.part.0+0x3a/0x150 Jan 3 17:16:33 linuxkiste kernel: [164294.600372] ? __fget_files+0x86/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600376] __x64_sys_ioctl+0x95/0xd0 Jan 3 17:16:33 linuxkiste kernel: [164294.600379] do_syscall_64+0x5c/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600383] ? __fget_files+0x86/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600386] ? fput+0x13/0x20 Jan 3 17:16:33 linuxkiste kernel: [164294.600388] ? exit_to_user_mode_prepare+0x37/0xb0 Jan 3 17:16:33 linuxkiste kernel: [164294.600392] ? syscall_exit_to_user_mode+0x27/0x50 Jan 3 17:16:33 linuxkiste kernel: [164294.600395] ? do_syscall_64+0x69/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600397] ? irqentry_exit+0x1d/0x30 Jan 3 17:16:33 linuxkiste kernel: [164294.600399] ? exc_page_fault+0x89/0x170 Jan 3 17:16:33 linuxkiste kernel: [164294.600402] entry_SYSCALL_64_after_hwframe+0x61/0xcb Jan 3 17:16:33 linuxkiste kernel: [164294.600406] RIP: 0033:0x7f3c97b93aff Jan 3 17:16:33 linuxkiste kernel: [164294.600408] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 Jan 3 17:16:33
[Kernel-packages] [Bug 2001545] Re: i915: repetable Kernel Oops after resuming from standby
** Attachment added: "lspci output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001545/+attachment/5638976/+files/lspci.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/2001545 Title: i915: repetable Kernel Oops after resuming from standby Status in linux package in Ubuntu: New Bug description: I have an Intel i915 Haswell system which - after upgrading from Ubuntu 20.04 to 22.04 - experiences repeated crashes when resuming from hibernation. Unfortunately, "ubuntu-bug" claims my kernel package is "not an official package" (which is untrue, at least to my knowledge - I installed from the official sources) so I cannot use 'ubuntu-bug'. $ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 I will attach the lspci output. This is the dmesg trace: Jan 3 17:16:33 linuxkiste kernel: [164294.599802] BUG: unable to handle page fault for address: e2fc5108 Jan 3 17:16:33 linuxkiste kernel: [164294.599809] #PF: supervisor read access in kernel mode Jan 3 17:16:33 linuxkiste kernel: [164294.599811] #PF: error_code(0x) - not-present page Jan 3 17:16:33 linuxkiste kernel: [164294.599813] PGD 0 P4D 0 Jan 3 17:16:33 linuxkiste kernel: [164294.599815] Oops: [#1] SMP PTI Jan 3 17:16:33 linuxkiste kernel: [164294.599818] CPU: 1 PID: 93586 Comm: chrome Tainted: G OE 5.15.0-56-generic #62-Ubuntu Jan 3 17:16:33 linuxkiste kernel: [164294.599820] Hardware name: MSI MS-7817/CSM-B85M-E45 (MS-7817), BIOS V10.9 04/21/2015 Jan 3 17:16:33 linuxkiste kernel: [164294.599822] RIP: 0010:kfree+0x68/0x250 Jan 3 17:16:33 linuxkiste kernel: [164294.599827] Code: 80 49 01 dc 0f 82 f2 01 00 00 48 c7 c0 00 00 00 80 48 2b 05 42 63 39 01 49 01 c4 49 c1 ec 0c 49 c1 e4 06 4c 03 25 20 63 39 01 <49> 8b 44 24 08 48 8d 50 ff a8 01 4c 0f 45 e2 49 8b 54 24 08 48 8d Jan 3 17:16:33 linuxkiste kernel: [164294.599829] RSP: 0018:b98e88c47930 EFLAGS: 00010286 Jan 3 17:16:33 linuxkiste kernel: [164294.599831] RAX: 6bf38000 RBX: 40c0 RCX: 00392c14 Jan 3 17:16:33 linuxkiste kernel: [164294.599833] RDX: b98e8000 RSI: a04d669e RDI: 40c0 Jan 3 17:16:33 linuxkiste kernel: [164294.599834] RBP: b98e88c47970 R08: R09: Jan 3 17:16:33 linuxkiste kernel: [164294.599835] R10: 940e24fc1000 R11: 940e090c5ad4 R12: e2fc5100 Jan 3 17:16:33 linuxkiste kernel: [164294.599836] R13: 000a R14: R15: 0230 Jan 3 17:16:33 linuxkiste kernel: [164294.599837] FS: 7f3c96764340() GS:94100ea8() knlGS: Jan 3 17:16:33 linuxkiste kernel: [164294.599839] CS: 0010 DS: ES: CR0: 80050033 Jan 3 17:16:33 linuxkiste kernel: [164294.599840] CR2: e2fc5108 CR3: 0001f49d8001 CR4: 001706e0 Jan 3 17:16:33 linuxkiste kernel: [164294.599842] Call Trace: Jan 3 17:16:33 linuxkiste kernel: [164294.599843] Jan 3 17:16:33 linuxkiste kernel: [164294.599845] kvfree+0x2e/0x40 Jan 3 17:16:33 linuxkiste kernel: [164294.599850] eb_relocate_parse_slow+0x133/0x470 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.599937] eb_relocate_parse+0x129/0x1b0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.69] i915_gem_do_execbuffer+0x373/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600083] ? __alloc_pages+0x311/0x330 Jan 3 17:16:33 linuxkiste kernel: [164294.600088] ? i915_memcpy_init_early+0x40/0x40 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600140] i915_gem_execbuffer2_ioctl+0x12e/0x280 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600200] ? i915_gem_do_execbuffer+0xba0/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600256] drm_ioctl_kernel+0xb3/0x100 [drm] Jan 3 17:16:33 linuxkiste kernel: [164294.600290] drm_ioctl+0x268/0x4b0 [drm] Jan 3 17:16:33 linuxkiste kernel: [164294.600308] ? i915_gem_do_execbuffer+0xba0/0xba0 [i915] Jan 3 17:16:33 linuxkiste kernel: [164294.600367] ? __check_object_size.part.0+0x3a/0x150 Jan 3 17:16:33 linuxkiste kernel: [164294.600372] ? __fget_files+0x86/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600376] __x64_sys_ioctl+0x95/0xd0 Jan 3 17:16:33 linuxkiste kernel: [164294.600379] do_syscall_64+0x5c/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600383] ? __fget_files+0x86/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600386] ? fput+0x13/0x20 Jan 3 17:16:33 linuxkiste kernel: [164294.600388] ? exit_to_user_mode_prepare+0x37/0xb0 Jan 3 17:16:33 linuxkiste kernel: [164294.600392] ? syscall_exit_to_user_mode+0x27/0x50 Jan 3 17:16:33 linuxkiste kernel: [164294.600395] ? do_syscall_64+0x69/0xc0 Jan 3 17:16:33 linuxkiste kernel: [164294.600397] ? irqentry_exit+0x1d/0x30 Jan 3
Re: [Kernel-packages] [Bug 1994144] Re: External display monitor not recognized
Thanks Daniel, output is below: As far as physical ports, my laptop has 1 HDMI, 2 USB 2.0, 1 high-speed USB, and a headphone jack. b.p. On Tuesday, January 3, 2023 at 04:06:18 AM EST, Daniel van Vugt <1994...@bugs.launchpad.net> wrote: Sounds like a kernel issue. Please run this command to see what ports the kernel thinks are connected: grep . /sys/class/drm/*/status ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1994144 Title: External display monitor not recognized Status in linux package in Ubuntu: Incomplete Bug description: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge same ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 08:45:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:899b] InstallationDate: Installed on 2022-10-24 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn2xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 899B dmi.board.vendor: HP dmi.board.version: 06.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.26 dmi.modalias: dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn2xxx dmi.product.sku: 641G6UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994144/+subscriptions ** Attachment added: "1672766790492blob.jpg" https://bugs.launchpad.net/bugs/1994144/+attachment/5638977/+files/1672766790492blob.jpg -- 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/1994144 Title: External display monitor not recognized Status in linux package in Ubuntu: Incomplete Bug description: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge
[Kernel-packages] [Bug 1749961]
FYI: I have built a kernel with the previously (on this thread) discussed patch (on a 5.4 kernel) and I still have the error multiple times per day. (In reply to James H from comment #207) > I'm using a 2.5gb ethernet usb device and getting this error intermittently > (a dozen times per day). > > $ uname -a > Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC > 2022 x86_64 x86_64 x86_64 GNU/Linux > > > $ lsusb > > Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB > 10/100/1G/2.5G > > > > This is what plays out via /var/log/syslog each time: > > Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, > device number 15 > Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: > unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM > Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: > Network is down > Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1... > Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process > Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process > Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed > Gen 1 USB device number 16 using xhci_hcd > Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device > found, idVendor=0bda, idProduct=8156, bcdDevice=31.00 > Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device > strings: Mfr=1, Product=2, SerialNumber=6 > Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB > 10/100/1G/2.5G LAN > Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: > Realtek > Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: > 00101 > Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: > MAC-Address: xx:xx:xx:xx:xx:xx > Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting > rx_max = 16384 > Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting > tx_max = 16384 > Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: > register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx > Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface > naming scheme 'v245'. > Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation > is unset or enabled, the speed and duplex are not writable. > Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN. > (then things start back up and the ethernet link goes live again after about > 10 seconds) -- 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in Linux: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/
[Kernel-packages] [Bug 2001557] [NEW] Integrate Nvidia Orin enablement patches
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2001557 Title: Integrate Nvidia Orin enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2001557/+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-aws/5.19.0.1016.13)
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1016.13) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: systemd/251.4-1ubuntu7 (amd64, 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/kinetic/update_excuses.html#linux-meta-aws [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 packing 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 1667750]
FYI: I have built a kernel with the previously (on this thread) discussed patch (on a 5.4 kernel) and I still have the error multiple times per day. (In reply to James H from comment #207) > I'm using a 2.5gb ethernet usb device and getting this error intermittently > (a dozen times per day). > > $ uname -a > Linux hephaestus 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC > 2022 x86_64 x86_64 x86_64 GNU/Linux > > > $ lsusb > > Bus 003 Device 016: ID 0bda:8156 Realtek Semiconductor Corp. USB > 10/100/1G/2.5G > > > > This is what plays out via /var/log/syslog each time: > > Dec 21 10:26:47 hephaestus kernel: [346923.166782] usb 3-4: USB disconnect, > device number 15 > Dec 21 10:26:47 hephaestus kernel: [346923.166913] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus kernel: [346923.166927] cdc_ncm 3-4:2.0 eth1: > unregister 'cdc_ncm' usb-:00:14.0-4, CDC NCM > Dec 21 10:26:47 hephaestus kernel: [346923.167071] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus kernel: [346923.170644] xhci_hcd :00:14.0: > WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. > Dec 21 10:26:47 hephaestus dhclient[320734]: receive_packet failed on eth1: > Network is down > Dec 21 10:26:47 hephaestus systemd[1]: Stopping ifup for eth1... > Dec 21 10:26:47 hephaestus dhclient[325522]: Killed old client process > Dec 21 10:26:47 hephaestus ifdown[325522]: Killed old client process > Dec 21 10:26:47 hephaestus kernel: [346923.478913] usb 3-4: new SuperSpeed > Gen 1 USB device number 16 using xhci_hcd > Dec 21 10:26:47 hephaestus kernel: [346923.499567] usb 3-4: New USB device > found, idVendor=0bda, idProduct=8156, bcdDevice=31.00 > Dec 21 10:26:47 hephaestus kernel: [346923.499573] usb 3-4: New USB device > strings: Mfr=1, Product=2, SerialNumber=6 > Dec 21 10:26:47 hephaestus kernel: [346923.499577] usb 3-4: Product: USB > 10/100/1G/2.5G LAN > Dec 21 10:26:47 hephaestus kernel: [346923.499580] usb 3-4: Manufacturer: > Realtek > Dec 21 10:26:47 hephaestus kernel: [346923.499583] usb 3-4: SerialNumber: > 00101 > Dec 21 10:26:47 hephaestus kernel: [346923.523736] cdc_ncm 3-4:2.0: > MAC-Address: xx:xx:xx:xx:xx:xx > Dec 21 10:26:47 hephaestus kernel: [346923.523742] cdc_ncm 3-4:2.0: setting > rx_max = 16384 > Dec 21 10:26:47 hephaestus kernel: [346923.523836] cdc_ncm 3-4:2.0: setting > tx_max = 16384 > Dec 21 10:26:47 hephaestus kernel: [346923.524578] cdc_ncm 3-4:2.0 eth1: > register 'cdc_ncm' at usb-:00:14.0-4, CDC NCM, xx:xx:xx:xx:xx:xx > Dec 21 10:26:47 hephaestus systemd-udevd[325501]: Using default interface > naming scheme 'v245'. > Dec 21 10:26:47 hephaestus systemd-udevd[325501]: ethtool: autonegotiation > is unset or enabled, the speed and duplex are not writable. > Dec 21 10:26:47 hephaestus systemd[1]: Found device USB_10_100_1G_2.5G_LAN. > (then things start back up and the ethernet link goes live again after about > 10 seconds) -- 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/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily- live/current/zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that hav
[Kernel-packages] [Bug 1318951] Re: kernel update fails with /boot on FAT32
Verified this is still happening installing linux- image-5.15.0-56-generic_5.15.0-56.62_amd64. /etc/kernel-img.conf workaround still does not work and computer is placed in the grub command line after reboot. -- 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/1318951 Title: kernel update fails with /boot on FAT32 Status in linux package in Ubuntu: Confirmed Bug description: My latest system upgrade failed because it can't upgrade the kernel: $sudo env LANGUAGE=en_US apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-signed-image-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic (= 3.13.0-24.47) but 3.13.0-24.46 is installed E: Unmet dependencies. Try using -f. When trying to install linux-image-3.13.0-24-generic manually it fails because it can't create a backup link for the old kernel. This really doesn't surprise me, because /boot is on a fat32 filesystem ( EFI System Partition ) so it shouldn't be possible to create any links at all. My fstab entries for boot are as follows: UUID=0E1E-3E58/mnt/efi vfatdefaults 0 2 /mnt/efi/ubuntu /boot none bind0 0 Here is the output of me trying to install the kernel manually: $sudo env LANGUAGE=en_US apt-get install linux-image-3.13.0-24-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: efibootmgr secureboot-db shim Use 'apt-get autoremove' to remove them. Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools Recommended packages: grub-pc grub-efi-amd64 grub-efi-ia32 grub lilo The following packages will be upgraded: linux-image-3.13.0-24-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 114 not fully installed or removed. Need to get 0 B/15,0 MB of archives. After this operation, 1.024 B disk space will be freed. (Reading database ... 205799 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb ... Done. Unpacking linux-image-3.13.0-24-generic (3.13.0-24.47) over (3.13.0-24.46) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb (--unpack): unable to make backup link of `./boot/vmlinuz-3.13.0-24-generic' before installing new version: Operation not permitted dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.47_amd64.deb E : Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318951/+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 1999629] Re: xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - xorg-core package does not provide xorg-video-abi under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below + xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below ** Summary changed: - xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under kinetic(22.10), which breaks Nvidia CUDA for graphics cards with graphics drivers version 510 and below + xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older ** Description changed: Description: Ubuntu 22.10 Release: 22.10 xserver-xorg-core: - Installed: 2:21.1.4-2ubuntu1 - Candidate: 2:21.1.4-2ubuntu1 - Version table: - *** 2:21.1.4-2ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2:21.1.4-2ubuntu1 + Candidate: 2:21.1.4-2ubuntu1 + Version table: + *** 2:21.1.4-2ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages + 100 /var/lib/dpkg/status + + Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't + because the only compatible mix of CUDA and drivers results in a virtual + dependency problem. + + apparently the problem is the lack the xorg-video-abi-24 in the xserver- + xorg-core package + + as the grep command shows, only the video-abi-25 is provided in ubuntu + 22 , but in order to install cuda 10.2 (or older), the version 24 is + needed. + + $ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)' + Package: xserver-xorg-core + Version: 2:21.1.3-2ubuntu2.5 + Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting + Package: xserver-xorg-core + Version: 2:21.1.3-2ubuntu2 + Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting - Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because the only compatible mix of CUDA and drivers results in a virtual dependency problem. + installing cuda 10.2 or older will give you this error: - The latest version of the nividia-drivers on my system is 510,for all - packages newer than this the persistence daemon fails. No problem I - suppose, I'll just install 510 and cuda-drivers-510. + xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not installable or + xorg-video-abi-23 but it is not installable or + xorg-video-abi-20 but it is not installable or + xorg-video-abi-19 but it is not installable or + xorg-video-abi-18 but it is not installable or + xorg-video-abi-15 but it is not installable or + xorg-video-abi-14 but it is not installable or + xorg-video-abi-13 but it is not installable or + xorg-video-abi-12 but it is not installable or + xorg-video-abi-11 but it is not installable or + xorg-video-abi-10 but it is not installable or + xorg-video-abi-8 but it is not installable or + xorg-video-abi-6.0 but it is not installable - Only that doesn't work, because apparently though this package is - installed it doesn't rprovide any of the xorg-video-abi virtual packages - like it did in prior versions. - - sudo apt-get install cuda-drivers-510 - Reading package lists... Done - Building dependency tree... Done - Reading state information... Done - Some packages could not be installed. This may mean that you have - requested an impossible situation or if you are using the unstable - distribution that some required packages have not yet been created - or been moved out of Incoming. - The following information may help resolve the situation: - - The following packages have unmet dependencies: - xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not installable or - xorg-video-abi-23 but it is not installable or - xorg-video-abi-20 but it is not installable or - xorg-video-abi-19 but it is not installable or - xorg-video-abi-18 but it is not installable or - xorg-video-abi-15 but it is
[Kernel-packages] [Bug 2001558] [NEW] legacy nas units fail using 22.04 mount cifs and nfs
Public bug reported: My legacy nas units are Quantum SnapServers. They can support Microsoft networking and NFS. Using the linux mount cifs utilities, I can access the Microsoft-networking server and everything works (ls, mkdir, touch, rm, etc) but I cannot write to a file no mattter what options I try. Using 20.04, I could access the nfs server thru linux mount nfs and everything worked. After upgrading to 22.04, I lost nfs access to the nas. I am unable to make any software changes to the nas units. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1534 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 3 15:48:23 2023 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-01-11 (721 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d2457659-a716-47d5-aa0c-1c2a3fb6edf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 15:49:20.493: The udisks-daemon is running (name-owner :1.14). UpgradeStatus: Upgraded to jammy on 2022-12-31 (3 days ago) dmi.bios.date: 04/30/2010 dmi.bios.release: 5.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 03NVJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/30/2010:br5.0:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn03NVJ6:rvrA00:cvnDellInc.:ct15:cvr:sku: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2001558 Title: legacy nas units fail using 22.04 mount cifs and nfs Status in linux package in Ubuntu: New Bug description: My legacy nas units are Quantum SnapServers. They can support Microsoft networking and NFS. Using the linux mount cifs utilities, I can access the Microsoft-networking server and everything works (ls, mkdir, touch, rm, etc) but I cannot write to a file no mattter what options I try. Using 20.04, I could access the nfs server thru linux mount nfs and everything worked. After upgrading to 22.04, I lost nfs access to the nas. I am unable to make any software changes to the nas units. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1534 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 3 15:48:23 2023 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-01-11 (721 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d2457659-a716-47d5-aa0c-1c2a3fb6edf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 15:49:20.493: The udisks-daemon is running (name-owner :1.14). UpgradeStatus: Upgraded to ja
[Kernel-packages] [Bug 2001564] [NEW] Kernel crash due to Bluefield pka TRNG ioctl call
Public bug reported: Reproducible with TLS/HTTPS client initiates TLS handshake on BF3 with Ubuntu 22.04, OpenSSL 3.0.2. wget https://google.com kernel will crash with the following logs. [ 1126.234077] Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 [ 1126.255579] Mem abort info: [ 1126.261186] ESR = 0x960f [ 1126.267319] EC = 0x25: DABT (current EL), IL = 32 bits [ 1126.277968] SET = 0, FnV = 0 [ 1126.284081] EA = 0, S1PTW = 0 [ 1126.290367] FSC = 0x0f: level 3 permission fault [ 1126.299964] Data abort info: [ 1126.305727] ISV = 0, ISS = 0x000f [ 1126.313411] CM = 0, WnR = 0 [ 1126.319349] user pgtable: 4k pages, 48-bit VAs, pgdp=000154bf1000 [ 1126.332259] [ce65d328] pgd=08011927a003, p4d=08011927a003, pud=080103a97003, pmd=080156cba003, pte=00e8000115a3ff43 [ 1126.357360] Internal error: Oops: 960f [#1] PREEMPT SMP ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/2001564 Title: Kernel crash due to Bluefield pka TRNG ioctl call Status in linux-bluefield package in Ubuntu: New Bug description: Reproducible with TLS/HTTPS client initiates TLS handshake on BF3 with Ubuntu 22.04, OpenSSL 3.0.2. wget https://google.com kernel will crash with the following logs. [ 1126.234077] Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 [ 1126.255579] Mem abort info: [ 1126.261186] ESR = 0x960f [ 1126.267319] EC = 0x25: DABT (current EL), IL = 32 bits [ 1126.277968] SET = 0, FnV = 0 [ 1126.284081] EA = 0, S1PTW = 0 [ 1126.290367] FSC = 0x0f: level 3 permission fault [ 1126.299964] Data abort info: [ 1126.305727] ISV = 0, ISS = 0x000f [ 1126.313411] CM = 0, WnR = 0 [ 1126.319349] user pgtable: 4k pages, 48-bit VAs, pgdp=000154bf1000 [ 1126.332259] [ce65d328] pgd=08011927a003, p4d=08011927a003, pud=080103a97003, pmd=080156cba003, pte=00e8000115a3ff43 [ 1126.357360] Internal error: Oops: 960f [#1] PREEMPT SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2001564/+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 2001567] [NEW] Add support for newer I219-LM NICs to the 5.4.0 kernel
Public bug reported: Some newer Dell systems (I experienced this on an Optiplex 7000) include an Intel I219-LM NIC that is not supported by the 5.4.0 kernel. Later versions of the HWE kernel do support this NIC. That makes it impossible to use these systems with the FIPS kernel. Since our imaging environment does not have FIPS mode enabled, we need support for this NIC when used both with and without FIPS mode. Please backport the latest stable e1000e driver to both the 5.4.0 non- FIPS kernel & the 5.4.0 FIPS kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001567 Title: Add support for newer I219-LM NICs to the 5.4.0 kernel Status in linux package in Ubuntu: New Bug description: Some newer Dell systems (I experienced this on an Optiplex 7000) include an Intel I219-LM NIC that is not supported by the 5.4.0 kernel. Later versions of the HWE kernel do support this NIC. That makes it impossible to use these systems with the FIPS kernel. Since our imaging environment does not have FIPS mode enabled, we need support for this NIC when used both with and without FIPS mode. Please backport the latest stable e1000e driver to both the 5.4.0 non- FIPS kernel & the 5.4.0 FIPS kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001567/+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 2001564] Re: Kernel crash due to Bluefield pka TRNG ioctl call
** Description changed: - Reproducible with TLS/HTTPS client initiates TLS handshake on BF3 with - Ubuntu 22.04, OpenSSL 3.0.2. + SRU Justification - wget https://google.com + [Impact] + Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue is with TRNG ioctl call. The kernel logs show the following errors. - kernel will crash with the following logs. + Unable to handle kernel access to user memory outside uaccess routines + at virtual address ce65d328 - [ 1126.234077] Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 - [ 1126.255579] Mem abort info: - [ 1126.261186] ESR = 0x960f - [ 1126.267319] EC = 0x25: DABT (current EL), IL = 32 bits - [ 1126.277968] SET = 0, FnV = 0 - [ 1126.284081] EA = 0, S1PTW = 0 - [ 1126.290367] FSC = 0x0f: level 3 permission fault - [ 1126.299964] Data abort info: - [ 1126.305727] ISV = 0, ISS = 0x000f - [ 1126.313411] CM = 0, WnR = 0 - [ 1126.319349] user pgtable: 4k pages, 48-bit VAs, pgdp=000154bf1000 - [ 1126.332259] [ce65d328] pgd=08011927a003, p4d=08011927a003, pud=080103a97003, pmd=080156cba003, pte=00e8000115a3ff43 - [ 1126.357360] Internal error: Oops: 960f [#1] PREEMPT SMP + BF3 on Ubuntu 22.04, OpenSSl 3.0.2 + + [Fix] + * Change RNG ioctl kernel handler code to copy data from user to kernel space. + + [Test Case] + openssl rand -engine pka 512 -- 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/2001564 Title: Kernel crash due to Bluefield pka TRNG ioctl call Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification [Impact] Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue is with TRNG ioctl call. The kernel logs show the following errors. Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 BF3 on Ubuntu 22.04, OpenSSl 3.0.2 [Fix] * Change RNG ioctl kernel handler code to copy data from user to kernel space. [Test Case] openssl rand -engine pka 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2001564/+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 2001558] Re: legacy nas units fail using 22.04 mount cifs and nfs
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: linux (Ubuntu) => nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2001558 Title: legacy nas units fail using 22.04 mount cifs and nfs Status in nfs-utils package in Ubuntu: New Bug description: My legacy nas units are Quantum SnapServers. They can support Microsoft networking and NFS. Using the linux mount cifs utilities, I can access the Microsoft-networking server and everything works (ls, mkdir, touch, rm, etc) but I cannot write to a file no mattter what options I try. Using 20.04, I could access the nfs server thru linux mount nfs and everything worked. After upgrading to 22.04, I lost nfs access to the nas. I am unable to make any software changes to the nas units. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1534 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 3 15:48:23 2023 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2021-01-11 (721 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. OptiPlex 780 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d2457659-a716-47d5-aa0c-1c2a3fb6edf8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 15:49:20.493: The udisks-daemon is running (name-owner :1.14). UpgradeStatus: Upgraded to jammy on 2022-12-31 (3 days ago) dmi.bios.date: 04/30/2010 dmi.bios.release: 5.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 03NVJ6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd04/30/2010:br5.0:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn03NVJ6:rvrA00:cvnDellInc.:ct15:cvr:sku: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2001558/+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 2001570] [NEW] Jammy update: v5.15.79 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.79 upstream stable release
from git://git.kernel.org/
fuse: fix readdir cache race
drm/amdkfd: avoid recursive lock in migrations back to RAM
drm/amdkfd: handle CPU fault on COW mapping
drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
hwspinlock: qcom: correct MMIO max register for newer SoCs
phy: stm32: fix an error code in probe
wifi: cfg80211: silence a sparse RCU warning
wifi: cfg80211: fix memory leak in query_regdb_file()
soundwire: qcom: reinit broadcast completion
soundwire: qcom: check for outanding writes before doing a read
bpf, verifier: Fix memory leak in array reallocation for stack state
bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
wifi: mac80211: Set TWT Information Frame Disabled bit as 1
bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE
HID: hyperv: fix possible memory leak in mousevsc_probe()
bpf, sockmap: Fix sk->sk_forward_alloc warn_on in sk_stream_kill_queues
bpf: Fix sockmap calling sleepable function in teardown path
bpf, sock_map: Move cancel_work_sync() out of sock lock
bpf: Add helper macro bpf_for_each_reg_in_vstate
bpf: Fix wrong reg type conversion in release_reference()
net: gso: fix panic on frag_list with mixed head alloc types
macsec: delete new rxsc when offload fails
macsec: fix secy->n_rx_sc accounting
macsec: fix detection of RXSCs when toggling offloading
macsec: clear encryption keys from the stack after setting up offload
octeontx2-pf: Use hardware register for CQE count
octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
net: tun: Fix memory leaks of napi_get_frags
bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
net: fman: Unregister ethernet device on removal
capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
phy: ralink: mt7621-pci: add sentinel to quirks table
KVM: s390: pv: don't allow userspace to set the clock under PV
net: lapbether: fix issue of dev reference count leakage in
lapbeth_device_event()
hamradio: fix issue of dev reference count leakage in bpq_device_event()
net: wwan: iosm: fix memory leak in ipc_wwan_dellink
net: wwan: mhi: fix memory leak in mhi_mbim_dellink
drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register()
tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
can: af_can: fix NULL pointer dereference in can_rx_register()
net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
net: broadcom: Fix BCMGENET Kconfig
tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header
dmaengine: pxa_dma: use platform_get_irq_optional
dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()
dmaengine: ti: k3-udma-glue: fix memory leak when register device fail
net: lapbether: fix issue of invalid opcode in lapbeth_open()
drivers: net: xgene: disable napi when register irq failed in xgene_enet_open()
perf stat: Fix printing os->prefix in CSV metrics output
perf tools: Add the include/perf/ directory to .gitignore
netfilter: nfnetlink: fix potential dead lock in nfnetlink_rcv_msg()
netfilter: Cleanup nft_net->module_list from nf_tables_exit_net()
net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init()
net: nixge: disable napi when enable interrupts failed in nixge_open()
net: wwan: iosm: fix memory leak in ipc_pcie_read_bios_cfg
net/mlx5: Bridge, verify LAG state when adding bond to bridge
net/mlx5: Allow async trigger completion execution on single CPU systems
net/mlx5e: E-Switch, Fix comparing termination table instance
net: cpsw: disable napi in cpsw_ndo_open()
net: cxgb3_main: disable napi when bind qsets failed in cxgb_up()
stmmac: intel: Enable 2.5Gbps for Intel AlderLake-S
stmmac: intel: Update PCH PTP clock rate from 200MHz to 204.8MHz
mctp: Fix an error handling path in mctp_init()
cxgb4vf: shut down the adapter when t4vf_update_port_info() failed in
cxgb4vf_open()
stmmac: dwmac-loongson: fix missing pci_disable_msi() while module exiting
stmmac: dwmac-loongson: fix missing pci_disable_device() in
loongson_dwmac_probe()
stmmac: dwmac-loongson: fix missing of_node_put() while module exiting
net: phy: mscc: macsec: clear encryption keys when freeing a flow
net: atlantic: macsec: clear encryption keys from the stack
ethernet: s2io: disable napi when start nic failed in s2io_card_up()
net: mv643xx_eth: disable napi when init rxq or txq failed in mv643xx_et
[Kernel-packages] [Bug 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed
Any update for this issue? -- 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/1976228 Title: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan- scsi-bus.sh -r' command is executed Status in linux package in Ubuntu: Confirmed Bug description: OS:Ubuntu 22.04 LTS kernel:5.15.0-33-generic host model:Dell PowerEdge R630 issue description: After I mapped luns from array to my host, I ran 'rescan-scsi-bus.sh -r' to scan for luns, my host crashed and became read-only.After the KVM forcibly restarts the host, the host is restored to normal. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 08:33 seq crw-rw 1 root audio 116, 33 May 30 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-26 (4 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 02C2CP dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn02C2CP:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+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 1994144] Re: [i915] Kernel cannot detect HDMI connection
** Summary changed: - External display monitor not recognized + [i915] Kernel cannot detect HDMI connection ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags added: i915 -- 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/1994144 Title: [i915] Kernel cannot detect HDMI connection Status in linux package in Ubuntu: New Bug description: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge same ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 08:45:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:899b] InstallationDate: Installed on 2022-10-24 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn2xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 899B dmi.board.vendor: HP dmi.board.version: 06.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.26 dmi.modalias: dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn2xxx dmi.product.sku: 641G6UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994144/+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 1994144] Re: [i915] Kernel cannot detect HDMI connection
Given you CPU is relatively new compared to the kernel version I suggest trying a newer kernel like sudo apt install linux-image-6.0.0-1009-oem or something from https://kernel.ubuntu.com/~kernel- ppa/mainline/?C=M;O=D -- 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/1994144 Title: [i915] Kernel cannot detect HDMI connection Status in linux package in Ubuntu: New Bug description: xrandr lists four disconnected DPs (though my laptop has zero Display Ports) but does not list an HDMI, which is what I use to connect external monitor. Cable is sound b/c I have a dual boot setup and Windows recognizes the display without issue. Using Ubuntu 22.04.1 LTS I expected OS to recognize that I have a an HDMI port or alternatively that something is plugged into it OS does not seem to acknowledge same ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 08:45:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:899b] InstallationDate: Installed on 2022-10-24 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn2xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 899B dmi.board.vendor: HP dmi.board.version: 06.26 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 6.26 dmi.modalias: dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn2xxx dmi.product.sku: 641G6UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994144/+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 1999629] Re: xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older
** Tags added: kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510-server in Ubuntu. https://bugs.launchpad.net/bugs/1999629 Title: xorg-core package does not provide xorg-video-abi version 24 ( it is version 25) under ubuntu 22 and later, makes it impossible to install cuda 10.2 or older Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510-server package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.10 Release: 22.10 xserver-xorg-core: Installed: 2:21.1.4-2ubuntu1 Candidate: 2:21.1.4-2ubuntu1 Version table: *** 2:21.1.4-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Under Ubuntu 22, I was trying to make NVIDIA CUDA work, but I can't because the only compatible mix of CUDA and drivers results in a virtual dependency problem. apparently the problem is the lack the xorg-video-abi-24 in the xserver-xorg-core package as the grep command shows, only the video-abi-25 is provided in ubuntu 22 , but in order to install cuda 10.2 (or older), the version 24 is needed. $ apt-cache show xserver-xorg-core | grep -E '(Package|Version|Provides)' Package: xserver-xorg-core Version: 2:21.1.3-2ubuntu2.5 Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting Package: xserver-xorg-core Version: 2:21.1.3-2ubuntu2 Provides: xorg-input-abi-24, xorg-video-abi-25, xserver-xorg-video-modesetting installing cuda 10.2 or older will give you this error: xserver-xorg-video-nvidia-510 : Depends: xorg-video-abi-24 but it is not installable or xorg-video-abi-23 but it is not installable or xorg-video-abi-20 but it is not installable or xorg-video-abi-19 but it is not installable or xorg-video-abi-18 but it is not installable or xorg-video-abi-15 but it is not installable or xorg-video-abi-14 but it is not installable or xorg-video-abi-13 but it is not installable or xorg-video-abi-12 but it is not installable or xorg-video-abi-11 but it is not installable or xorg-video-abi-10 but it is not installable or xorg-video-abi-8 but it is not installable or xorg-video-abi-6.0 but it is not installable According to my research this package is the provider in focal https://packages.ubuntu.com/focal/xorg-video-abi-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1999629/+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 2000240] Re: Unable to switch GDM User -
** Package changed: linux (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000240 Title: Unable to switch GDM User - Status in gdm3 package in Ubuntu: Confirmed Bug description: Hello since upgrading to 22.04.1 LTS it's no longer possible to switch users from graphical menu. The behaviour is as follows: - from user A session, click on System menu and then Change user - the user list is displayed - clicking on another user (B) then I'm prompted for the password - when I enter the password, there is a lag, and then the user list is displayed again I tried alternatives - locking the A session before trying to open B session > no success - using the Wayland logging possiblity > no success Using journalctl wit support from experienced Ubunteros I tried to find issues and apparently there is an error related to the problem (I do not know if it's the cause or the consequence) sept. 04 17:55:12 pcmail gdm3[1002]: GLib-GObject: g_object_set_is_valid_property: object class 'GdmLocalDisplay' has no property named 'supported-session-tyes' there has also been a problem with apparmor (several messages logged) sept. 04 17:55:21 pcmail audit[746]: USER_AVC pid=746 uid=103 auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/login1" interface=> exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olmaillard 18811 F pulseaudio /dev/snd/controlC1: olmaillard 18811 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-01 (445 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-17 (125 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd10/11/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olmaillard 18811 F pulseaudio /dev/snd/controlC1: olmaillard 18811 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-10-01 (445 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=87e4303c-d957-47d2-a76b-a46611c78fbd ro quiet
[Kernel-packages] [Bug 2000162] Re: e1000 transmit queue timeout in net-traffic heavy generic vm
** Package changed: linux (Ubuntu) => qemu (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000162 Title: e1000 transmit queue timeout in net-traffic heavy generic vm Status in qemu package in Ubuntu: Confirmed Bug description: Using the latest generic 'jammy' kernel, in a mate-desktop VM with no GUI/user activity, mostly used as a router/gateway, after at least 12 hours of typical operations, we see: Dec 20 01:11:53 gate2.1.quietfountain.com systemd-networkd[331]: enp0s3: Lost carrier Dec 20 01:11:54 gate2.1.quietfountain.com kernel: e1000 :00:03.0 enp0s3: Reset adapter Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ---[ end trace ed46aa86d43e4a6f ]--- Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ret_from_fork+0x22/0x30 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ? set_kthread_struct+0x50/0x50 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: kthread+0x12a/0x150 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ? smpboot_register_percpu_thread+0x140/0x140 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: smpboot_thread_fn+0xba/0x160 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: run_ksoftirqd+0x2f/0x50 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: __do_softirq+0xd9/0x2e7 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: run_timer_softirq+0x2a/0x60 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ? raw_spin_rq_unlock+0x10/0x30 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ? psi_task_switch+0xc6/0x220 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: __run_timers.part.0+0x1e3/0x270 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: call_timer_fn+0x2c/0x120 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: ? pfifo_fast_enqueue+0x160/0x160 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Call Trace: Dec 20 01:11:54 gate2.1.quietfountain.com kernel: CR2: 55abc0c231d0 CR3: 09efe000 CR4: 000406f0 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: CS: 0010 DS: ES: CR0: 80050033 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: FS: () GS:933601a0() knlGS: Dec 20 01:11:54 gate2.1.quietfountain.com kernel: R13: 933557e79e80 R14: 0001 R15: 933570ad84c0 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: R10: 2065756575712074 R11: 696d736e61727420 R12: Dec 20 01:11:54 gate2.1.quietfountain.com kernel: RBP: a2e80006bda0 R08: 0003 R09: fffcd4e8 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: RDX: 933601a20588 RSI: 0001 RDI: 933601a20580 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: RAX: RBX: 933570ad8000 RCX: 0027 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: RSP: 0018:a2e80006bd68 EFLAGS: 00010286 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Code: eb 97 48 8b 5d d0 c6 05 d7 23 69 01 01 48 89 df e8 2e 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 28 5a 8d b9 48 89 c2 e8 a0 d0 19 00 <0f> 0b eb 80 e9 d3 39 23 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: RIP: 0010:dev_watchdog+0x277/0x280 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: CPU: 0 PID: 12 Comm: ksoftirqd/0 Not tainted 5.15.0-56-generic #62-Ubuntu Dec 20 01:11:54 gate2.1.quietfountain.com kernel: hid_generic qxl drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt usbhid fb_sys_fops psmouse hid cec virtio_scsi rc_core virtio_blk drm e1000 i2c_piix4 pata_acpi floppy Dec 20 01:11:54 gate2.1.quietfountain.com kernel: Modules linked in: nfsd nfs_acl lockd grace tls ceph libceph fscache netfs i6300esb tcp_htcp lz4 lz4_compress zram nft_reject_ipv6 nf_reject_ipv6 nft_nat nft_masq nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_l> Dec 20 01:11:54 gate2.1.quietfountain.com kernel: WARNING: CPU: 0 PID: 12 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280 Dec 20 01:11:54 gate2.1.quietfountain.com kernel: NETDEV WATCHDOG: enp0s3 (e1000): transmit queue 0 timed out Dec 20 01:11:54 gate2.1.quietfountain.com kernel: [ cut here ] That one interface is the only 'physical' interface. There are a few vlans and a couple mostly idle wireguard links. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Found on K-5.19 s390x ** Tags added: kinetic sru-20221114 ** Also affects: linux (Ubuntu Kinetic) 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: New Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+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 1979886] Re: xHCI race conditions 5.15.0-40-generic
I can confirm the same kind of behavior on a ASMedia Technology Inc.
ASM2142/ASM3142 USB 3.1 Host Controller.
It has been plaguing me for years, xhci_hcd seems broken when using USB
hubs such as the one used by the Valve Index (VR headset). I have to
use my reset_usb script once in a while to rebind xhci_hcd and reset the
whole thing. At least I don't have to reboot anymore but it is more
than annoying.
Same behavior as yours, USB works then suddenly one or more device
behind the hub stops responding. Then everything is frozen until I
unplug a device, then it loops with
[46588.094379] hub 3-2:1.0: hub_ext_port_status failed (err = -110)
This script is able to reset the driver to make everything working again
but, of course, will crash my virtual reality session.
```
#!/bin/bash
[ `id -u` -ne 0 ] && exec sudo "$0"
cd /sys/bus/pci/drivers/xhci_hcd
BUS=":b3:00.0"
echo "$BUS" > unbind
sleep 5
echo "$BUS" > bind
sleep 5
find "$BUS/" -name control -exec /bin/sh -c "echo on > {}" \;
```
--
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/1979886
Title:
xHCI race conditions 5.15.0-40-generic
Status in linux package in Ubuntu:
Confirmed
Bug description:
In 22.04 there are plenty of usb troubles from xHCI
Some hardware gets the xHCI dead and complete usb shutdown
other hardware works better with first tier of hubs
second hub tier is still unreliable, pointing to race conditions
troubled devices seems to be VIA 2109:0822 2109:0715
Here I have a 5 Gb/port, hub then hub 2109:0822
echoed to console:
Jun 19 23:51:15 kernel: [29817.094981] hub 2-5:1.0: hub_ext_port_status
failed (err = -110)
Jun 19 23:51:17 kernel: [29819.142955] usb 2-5.3: Port disable: can't
disable remote wake
Jun 19 23:51:18 kernel: [29820.166925] usb 2-5-port3: cannot disable (err =
-110)
Jun 19 23:51:20 kernel: [29822.374883] usb 1-8: Failed to suspend device,
error -110
Jun 19 23:51:23 kernel: [29825.286836] hub 2-5:1.0: hub_ext_port_status
failed (err = -110)
key here: Port disable: can't disable remote wake
-110 is ETIMEDOUT which when plugged in direct host produces xHCI dead
If the device is unplugged, unplug is undetected and leads to infinite errors
-110 -71
— missed unplug has also been seen with usb storage 2109:0715
other key errors:
LPM exit latency is zeroed, disabling LPM.
usb_reset_and_verify_device Failed to disable LPM
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-40-generic 5.15.0-40.43
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D10p',
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p',
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sat Jun 25 08:49:26 2022
HibernationDevice: RESUME=none
MachineType: Apple Inc. Macmini8,1
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
TERM=screen
PATH=(custom, no user)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: root=ZFS=rpool/ROOT/ubuntu_mc4at7 ro
initrd=EFI\hostname\initrd.img
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-40-generic N/A
linux-backports-modules-5.15.0-40-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.2
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2022
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 1731.120.10.0.0 (iBridge: 19.16.15071.0.0,0)
dmi.board.name: Mac-7BA5B2DFE22DDD8C
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini8,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7BA5B2DFE22DDD8C
dmi.modalias:
dmi:bvnAppleInc.:bvr1731.120.10.0.0(iBridge19.16.15071.0.0,0):bd04/24/2022:br0.1:svnAppleInc.:pnMacmini8,1:pvr1.0:rvnAppleInc.:rnMac-7BA5B2DFE22DDD8C:rvrMacmini8,1:cvnAppleInc.:ct9:cvrMac-7BA5B2DFE22DDD8C:sku:
dmi.product.family: Mac mini
dmi.product.name: Macmini8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979886/+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.n
[Kernel-packages] [Bug 1976473] Re: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop
Does this issue happen on Linux 6.1? There are some new fixes in the ACPI backlight. -- 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/1976473 Title: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Confirmed Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+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 2001570] Re: Jammy update: v5.15.79 upstream stable release
Would it be possible to bump up to 5.15.83 this cycle instead? Wanting
to see
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=249011f4c3b8a636f019c9740d5c4356d11031be
land.
--
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/2001570
Title:
Jammy update: v5.15.79 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Bug description:
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.79 upstream stable release
from git://git.kernel.org/
fuse: fix readdir cache race
drm/amdkfd: avoid recursive lock in migrations back to RAM
drm/amdkfd: handle CPU fault on COW mapping
drm/amdkfd: Fix NULL pointer dereference in svm_migrate_to_ram()
hwspinlock: qcom: correct MMIO max register for newer SoCs
phy: stm32: fix an error code in probe
wifi: cfg80211: silence a sparse RCU warning
wifi: cfg80211: fix memory leak in query_regdb_file()
soundwire: qcom: reinit broadcast completion
soundwire: qcom: check for outanding writes before doing a read
bpf, verifier: Fix memory leak in array reallocation for stack state
bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues
wifi: mac80211: Set TWT Information Frame Disabled bit as 1
bpftool: Fix NULL pointer dereference when pin {PROG, MAP, LINK} without FILE
HID: hyperv: fix possible memory leak in mousevsc_probe()
bpf, sockmap: Fix sk->sk_forward_alloc warn_on in sk_stream_kill_queues
bpf: Fix sockmap calling sleepable function in teardown path
bpf, sock_map: Move cancel_work_sync() out of sock lock
bpf: Add helper macro bpf_for_each_reg_in_vstate
bpf: Fix wrong reg type conversion in release_reference()
net: gso: fix panic on frag_list with mixed head alloc types
macsec: delete new rxsc when offload fails
macsec: fix secy->n_rx_sc accounting
macsec: fix detection of RXSCs when toggling offloading
macsec: clear encryption keys from the stack after setting up offload
octeontx2-pf: Use hardware register for CQE count
octeontx2-pf: NIX TX overwrites SQ_CTX_HW_S[SQ_INT]
net: tun: Fix memory leaks of napi_get_frags
bnxt_en: Fix possible crash in bnxt_hwrm_set_coal()
bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
net: fman: Unregister ethernet device on removal
capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
phy: ralink: mt7621-pci: add sentinel to quirks table
KVM: s390: pv: don't allow userspace to set the clock under PV
net: lapbether: fix issue of dev reference count leakage in
lapbeth_device_event()
hamradio: fix issue of dev reference count leakage in bpq_device_event()
net: wwan: iosm: fix memory leak in ipc_wwan_dellink
net: wwan: mhi: fix memory leak in mhi_mbim_dellink
drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register()
tcp: prohibit TCP_REPAIR_OPTIONS if data was already sent
ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
can: af_can: fix NULL pointer dereference in can_rx_register()
net: stmmac: dwmac-meson8b: fix meson8b_devm_clk_prepare_enable()
net: broadcom: Fix BCMGENET Kconfig
tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header
dmaengine: pxa_dma: use platform_get_irq_optional
dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()
dmaengine: ti: k3-udma-glue: fix memory leak when register device fail
net: lapbether: fix issue of invalid opcode in lapbeth_open()
drivers: net: xgene: disable napi when register irq failed in
xgene_enet_open()
perf stat: Fix printing os->prefix in CSV metrics output
perf tools: Add the include/perf/ directory to .gitignore
netfilter: nfnetlink: fix potential dead lock in nfnetlink_rcv_msg()
netfilter: Cleanup nft_net->module_list from nf_tables_exit_net()
net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init()
net: nixge: disable napi when enable interrupts failed in nixge_open()
net: wwan: iosm: fix memory leak in ipc_pcie_read_bios_cfg
net/mlx5: Bridge, verify LAG state when adding bond to bridge
net/mlx5: Allow async trigger completion execution on single CPU systems
net/mlx5e: E-Switch, Fix comparing termination table instance
net: cpsw: disable napi in cpsw_ndo_open()
net: cxgb3_main: disable napi when bind qsets failed in cxgb_up()
stmmac: intel: Enable 2.5Gbps for Intel AlderLake-S
stmmac: int
[Kernel-packages] [Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
*** This bug is a duplicate of bug 1967707 *** https://bugs.launchpad.net/bugs/1967707 "drmModeAtomicCommit: Invalid argument" is also being tracked in bug 1968040 although it might have multiple causes. "clutter_frame_clock_notify_presented: code should not be reached" is being tracked in bug 1967707 and I think that's the main issue here. ** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags added: jammy nvidia nvidia-wayland wayland wayland-session ** This bug has been marked a duplicate of bug 1967707 Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/1999830 Title: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: - ubuntu 22.04.1 - 5.15.0-56-generic - mutter 42.5-0ubuntu1 - using gdm3 - nvidia Driver Version: 525.60.11 (nvidia-driver-525) - prime select to on-demand - 1 external display, 1 internal LCD ``` Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting. Added device '/dev/dri/card0' (i915) using atomic mode setting. Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1' Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0' Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as primary Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed (Failed to create gbm_surface: No such file or directory). Falling back to GPU-less > Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2 for managed services) Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0' ``` 0. open a terminal `journalctl -f` 1. Open the display setting, switch to join displays, choose external display as primary. 2. try to change some settings like scale, position of the screen, refresh rate, etc, then applay 3. repeat above step several times After 2 changes the external screen freeze forever. Internal screen is still responsible. On each `Apply` The journal recorded an kernel error about nvidia_drm and flooded with clutter-frame-clock error. ``` Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to map NvKmsKapiMemory 0x5> Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit: Invalid argument Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached Dec 15 22:19:26 gnome-shell[3203]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached ``` one may ignore the drmModeAtomicCommit warning, they are always flooding the log (though it may be related issue) The clutter warning then flood the log forever till reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- Mailing lis
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
Hi,
How to check whether it is an issue with lab networking?Could you help to
share the methods?
And please help to point out the root cause of this defect shown in sos
report log?
Thanks a lot.
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in subiquity:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1998168/+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
