[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
It's not bug 2049927 because that's amdgpu and this is i915. ** This bug is no longer a duplicate of bug 2049927 [amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Expired Status in linux-oem-6.5 package in Ubuntu: New Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+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 2049927] Re: [amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
** Summary changed:
- since Linux kernel 6.5.0-14 external monitors are no longer detected
+ [amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer detected
** Tags added: amdgpu
--
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/2049927
Title:
[amdgpu] since Linux kernel 6.5.0-14 external monitors are no longer
detected
Status in linux package in Ubuntu:
Confirmed
Bug description:
on my Lenovo ThinkPad P14s gen 4, external monitors are no longer
detected since installing 6.5.0-14.
Neither USB-C nor HDMI work. hwinfo and the "Displays" util don't show
any additional monitors, only the built-in one.
Charging through the monitor does work. also, the built-in USB hub of
the monitor works.
I have tried with 2 external monitors (both ultra-wide, one Dell, one
Samsung)
Going back to 6.5.0-13 fixes everything.
Let me know if there's any way I can help troubleshoot this.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 19 17:17:54 2024
InstallationDate: Installed on 2023-11-16 (64 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2023
dmi.bios.release: 1.16
dmi.bios.vendor: LENOVO
dmi.bios.version: R2FET36W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21K5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrR2FET36W(1.16):bd10/24/2023:br1.16:efr1.11:svnLENOVO:pn21K5CTO1WW:pvrThinkPadP14sGen4:rvnLENOVO:rn21K5CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K5_BU_Think_FM_ThinkPadP14sGen4:
dmi.product.family: ThinkPad P14s Gen 4
dmi.product.name: 21K5CTO1WW
dmi.product.sku: LENOVO_MT_21K5_BU_Think_FM_ThinkPad P14s Gen 4
dmi.product.version: ThinkPad P14s Gen 4
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049927/+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 2051763] Re: RTL8821CE did not work
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2051763 Title: RTL8821CE did not work Status in linux package in Ubuntu: Expired Bug description: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter did not work on 6.5 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051763/+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 2051994] Re: /tmp drive fills up
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/2051994
Title:
/tmp drive fills up
Status in linux package in Ubuntu:
Expired
Bug description:
If left at the login screen, after a day or so, /tmp seems to fill up
on its own. It will show an X window message upon login regarding
/tmp, then any applications, like LibreOffice, won't run. The files
don't shows up using du, likely because it's a tmpfs type.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-15-generic 6.5.0-15.15
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: russell1197 F wireplumber
/dev/snd/controlC1: russell1197 F wireplumber
/dev/snd/controlC0: russell1197 F wireplumber
/dev/snd/seq:russell1191 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Thu Feb 1 17:24:21 2024
InstallationDate: Installed on 2023-06-23 (223 days ago)
InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic
root=UUID=ff2b9230-f3ac-4af5-ae27-88eae14765d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-15-generic N/A
linux-backports-modules-6.5.0-15-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2024-01-26 (6 days ago)
dmi.bios.date: 05/09/2017
dmi.bios.release: 2.71
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L01 v02.71
dmi.board.asset.tag: 2UA4101ZMS
dmi.board.name: 18E7
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA4101ZMS
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL01v02.71:bd05/09/2017:br2.71:svnHewlett-Packard:pnHPProDesk600G1SFF:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct4:cvr:skuE3S71UT#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP ProDesk 600 G1 SFF
dmi.product.sku: E3S71UT#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051994/+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 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 I will add here as well that we have an update of the firefox profile coming that supports the /opt/firefox/firefox location used as the default install for the firefox downloaded directly from mozilla.org -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+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 2059991] Re: Mantic update: upstream stable patchset 2024-04-02
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Portia Stephens (portias) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-04-02 + + Ported from the following upstream stable releases: + v6.1.78, v6.6.17 + from git://git.kernel.org/ + + ext4: regenerate buddy after block freeing failed if under fc replay + dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools + dmaengine: ti: k3-udma: Report short packet errors + dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA + dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA + phy: renesas: rcar-gen3-usb2: Fix returning wrong error code + dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV + phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP + cifs: failure to add channel on iface should bump up weight + drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case + drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case + drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup + net: stmmac: xgmac: fix handling of DPP safety error for DMA channels + wifi: mac80211: fix waiting for beacons logic + netdevsim: avoid potential loop in nsim_dev_trap_report_work() + net: atlantic: Fix DMA mapping for PTP hwts ring + selftests: net: cut more slack for gro fwd tests. + selftests: net: avoid just another constant wait + tunnels: fix out of bounds access when building IPv6 PMTU error + atm: idt77252: fix a memleak in open_card_ubr0 + octeontx2-pf: Fix a memleak otx2_sq_init + hwmon: (aspeed-pwm-tacho) mutex for tach reading + hwmon: (coretemp) Fix out-of-bounds memory access + hwmon: (coretemp) Fix bogus core_id to attr name mapping + inet: read sk->sk_family once in inet_recv_error() + drm/i915/gvt: Fix uninitialized variable in handle_mmio() + rxrpc: Fix response to PING RESPONSE ACKs to a dead call + tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() + af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. + ppp_async: limit MRU to 64K + selftests: cmsg_ipv6: repeat the exact packet + netfilter: nft_compat: narrow down revision to unsigned 8-bits + netfilter: nft_compat: reject unused compat flag + netfilter: nft_compat: restrict match/target protocol to u16 + drm/amd/display: Implement bounds check for stream encoder creation in DCN301 + netfilter: nft_ct: reject direction for ct id + netfilter: nft_set_pipapo: store index in scratch maps + netfilter: nft_set_pipapo: add helper to release pcpu scratch area + netfilter: nft_set_pipapo: remove scratch_aligned pointer + fs/ntfs3: Fix an NULL dereference bug + scsi: core: Move scsi_host_busy() out of host lock if it is for per-command + blk-iocost: Fix an UBSAN shift-out-of-bounds warning + ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision + ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter + ALSA: usb-audio: add quirk for RODE NT-USB+ + USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e + USB: serial: option: add Fibocom FM101-GL variant + USB: serial: cp210x: add ID for IMST iM871A-USB + usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK + usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK + hrtimer: Report offline hrtimer enqueue + Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU + Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID + io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers + net: stmmac: xgmac: use #define for string constants + ALSA: usb-audio: Sort quirk table entries + net: stmmac: xgmac: fix a typo of register name in DPP safety handling + perf evlist: Fix evlist__new_default() for > 1 core PMU + cifs: avoid redundant calls to disable multichannel + rust: arc: add explicit `drop()` around `Box::from_raw()` + rust: task: remove redundant explicit link + rust: print: use explicit link in documentation + MAINTAINERS: add Catherine as xfs maintainer for 6.6.y + xfs: bump max fsgeom struct version + xfs: hoist freeing of rt data fork extent mappings + xfs: prevent rt growfs when quota is enabled + xfs: rt stubs should return negative errnos when rt disabled + xfs: fix units conversion error in
[Kernel-packages] [Bug 2059385] Re: Mantic update: upstream stable patchset 2024-03-28
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059385 Title: Mantic update: upstream stable patchset 2024-03-28 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Invalid 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: upstream stable patchset 2024-03-28 Ported from the following upstream stable releases: v6.1.78, v6.6.17 from git://git.kernel.org/ ext4: regenerate buddy after block freeing failed if under fc replay dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools dmaengine: ti: k3-udma: Report short packet errors dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA phy: renesas: rcar-gen3-usb2: Fix returning wrong error code dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP cifs: failure to add channel on iface should bump up weight drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup net: stmmac: xgmac: fix handling of DPP safety error for DMA channels wifi: mac80211: fix waiting for beacons logic netdevsim: avoid potential loop in nsim_dev_trap_report_work() net: atlantic: Fix DMA mapping for PTP hwts ring selftests: net: cut more slack for gro fwd tests. selftests: net: avoid just another constant wait tunnels: fix out of bounds access when building IPv6 PMTU error atm: idt77252: fix a memleak in open_card_ubr0 octeontx2-pf: Fix a memleak otx2_sq_init hwmon: (aspeed-pwm-tacho) mutex for tach reading hwmon: (coretemp) Fix out-of-bounds memory access hwmon: (coretemp) Fix bogus core_id to attr name mapping inet: read sk->sk_family once in inet_recv_error() drm/i915/gvt: Fix uninitialized variable in handle_mmio() rxrpc: Fix response to PING RESPONSE ACKs to a dead call tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. ppp_async: limit MRU to 64K selftests: cmsg_ipv6: repeat the exact packet netfilter: nft_compat: narrow down revision to unsigned 8-bits netfilter: nft_compat: reject unused compat flag netfilter: nft_compat: restrict match/target protocol to u16 drm/amd/display: Implement bounds check for stream encoder creation in DCN301 netfilter: nft_ct: reject direction for ct id netfilter: nft_set_pipapo: store index in scratch maps netfilter: nft_set_pipapo: add helper to release pcpu scratch area netfilter: nft_set_pipapo: remove scratch_aligned pointer fs/ntfs3: Fix an NULL dereference bug scsi: core: Move scsi_host_busy() out of host lock if it is for per-command blk-iocost: Fix an UBSAN shift-out-of-bounds warning ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter ALSA: usb-audio: add quirk for RODE NT-USB+ USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e USB: serial: option: add Fibocom FM101-GL variant USB: serial: cp210x: add ID for IMST iM871A-USB usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK hrtimer: Report offline hrtimer enqueue Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers net: stmmac: xgmac: use #define for string constants ALSA: usb-audio: Sort quirk table entries net: stmmac: xgmac: fix a typo of register name in DPP safety handling rust: upgrade to Rust 1.71.1 UBUNTU: [Config] updateconfigs for Rust 1.71.1 rust: upgrade to Rust 1.72.1 perf evlist: Fix evlist__new_default() for > 1 core PMU cifs: avoid redundant calls to disable multichannel rust: arc: add explicit `drop()` around `Box::from_raw()` rust: task: remove redundant explicit link rust: print: use explicit link in documentation rust: upgrade to Rust 1.73.0 MAINTAINERS: add Catherine as xfs maintainer for 6.6.y xfs: bump max fsgeom struct
[Kernel-packages] [Bug 2059991] [NEW] Mantic update: upstream stable patchset 2024-04-02
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: upstream stable patchset 2024-04-02 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Mantic) 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/2059991 Title: Mantic update: upstream stable patchset 2024-04-02 Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: New 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: upstream stable patchset 2024-04-02 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059991/+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 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
[Impact] error message "UBSAN: array-index-out-of-bounds in drivers/net/hyperv/netvsc.c:1446:41" appears multiple times during boot for a Hyper-V environment. [Fix] Clean cherry-pick commit bb9b0e46b84 for Focal, Jammy and Mantic. [Test case] check the dmesg to see if there is the error message "UBSAN: array-index-out-of-bounds" [Regression Potential] DPDK which processes netvsc packets, so it might incompatible with ancient DPDK, but modern DPDK had already used flexible array member. ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Mantic: New Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2058707] Re: Backport AXI 1-wire host driver
** Description changed: [ Impact ] + * Backport AXI 1-wire host driver Edit. + * The driver is used to interface with FPGA IP logic. + * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] + * Xilinx will test the functionality on a KD240 with an FPGA bitstream + that has the required IP logic. + [ Where problems could occur ] + * We are unable to run certification testing with the driver loaded + which creates a risk of breaking the driver in the future. + [ Other info ] + + Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 ** Description changed: [ Impact ] - * Backport AXI 1-wire host driver Edit. + * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 ** Description changed: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] - Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 + * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2058707 Title: Backport AXI 1-wire host driver Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * Backport AXI 1-wire host driver. * The driver is used to interface with FPGA IP logic. * The driver is only loaded when device tree overlay is applied on platforms that require the driver. [ Test Plan ] * Xilinx will test the functionality on a KD240 with an FPGA bitstream that has the required IP logic. [ Where problems could occur ] * We are unable to run certification testing with the driver loaded which creates a risk of breaking the driver in the future. [ Other info ] * Private LP bug: https://bugs.launchpad.net/limerick/+bug/2052477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2058707/+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 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hi cipricus, can you specify how and where your firefox was installed? We are trying to support multiple variations including downloading directly from mozilla if it is installed to the standard location? mruffell is correct in his assessment that this is due to firefox not correctly handling user namespace mediation. This can be seen in your dmesg with the following messages [ 69.033622] audit: type=1400 audit(1709714939.278:138): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=2922 comm=495043204C61756E6368 requested="userns_create" target="unprivileged_userns" [ 69.037108] audit: type=1400 audit(1709714939.282:139): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=2982 comm=53616E64626F7820466F726B6564 capability=21 capname="sys_admin" Unfortunately firefox does not handle the error returned when it tries an operation that require sys_admin capability gracefully resulting in the crash. mruffell has already provided all the relevant links so I will just supplement that information 1. The recommended way is updating the firefox profile in /etc/apparmor.d/firefox by adding the location you have firefox installed, and then reloading the profile with sudo apparmor_parser -r /etc/apparmor.d/firefox 2. You can disable user namespaces, this will keep firefox from trying to use them as part of ts sandbox https://lwn.net/Articles/673597/ 3. the least recommended way to fix this is you can disable the finer grained user namespace restrictions as outlined in https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user- namespaces -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+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 2059978] [NEW] linux-aws-5.15 ADT test MISS because it's unable to find package
Public bug reported: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux-aws-5.15-- modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024.03.04 F aws-5.15 ADT linux-aws-5.15 amd64 output" https://bugs.launchpad.net/bugs/2059978/+attachment/5761136/+files/2024.03.04%20F%20aws-5.15%20ADT%20linux-aws-5.15%20amd64%20output -- 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/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059978/+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 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
It happens about every other shutdown/reboot. I'm having occasional problems with suspend as well, which works fine 50% of the time or else freezes. -- 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/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 Status in snapd: Confirmed Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+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 2059973] [NEW] my touch pad doesn't wok at all.
Public bug reported: i'm new at linux. firstly i have installed ubuntu as dual boot besides windows 11 pro. that time the touchpad worked as expected. but when i gain confident enough that i can use linux, i installed ubuntu as primary setup, after that the touch pad is not working. it detects the touch pad as follows cat /proc/bus/input/devices I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Mouse" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input22 U: Uniq= H: Handlers=mouse0 event19 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Touchpad" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input23 U: Uniq= H: Handlers=mouse1 event20 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 02:29:41 2024 InstallationDate: Installed on 2024-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059973 Title: my touch pad doesn't wok at all. Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: i'm new at linux. firstly i have installed ubuntu as dual boot besides windows 11 pro. that time the touchpad worked as expected. but when i gain confident enough that i can use linux, i installed ubuntu as primary setup, after that the touch pad is not working. it detects the touch pad as follows cat /proc/bus/input/devices I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Mouse" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input22 U: Uniq= H: Handlers=mouse0 event19 B: PROP=0 B: EV=17 B: KEY=3 0 0 0 0 B: REL=3 B: MSC=10 I: Bus=0018 Vendor=06cb Product=ce78 Version=0100 N: Name="SYNA2BA6:00 06CB:CE78 Touchpad" P: Phys=i2c-SYNA2BA6:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA2BA6:00/0018:06CB:CE78.0001/input/input23 U: Uniq= H: Handlers=mouse1 event20 B: PROP=5 B: EV=1b B: KEY=e520 1 0 0 0 0 B: ABS=2e08003 B: MSC=20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 02:29:41 2024 InstallationDate: Installed on 2024-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059973/+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 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx
** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2059968] [NEW] Produce kernel snaps for linux-nvidia-tegra-igx
Public bug reported: We plan on producing Ubuntu Core images with the linux-nvidia-tegra-igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. ** Affects: linux-meta-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-signed-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Also affects: linux-meta-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: New => Fix Committed ** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+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 2059961] [NEW] genetlink: fix single op policy dump when do is present
Public bug reported: intro - Our internal test triggers a kernel crash dump below [ 888.690348] Sun Mar 24 23:51:59 2024: DriVerTest - Start Test [ 888.691834] [ 888.983912] mlx5_core :08:00.1 eth3: Link up [ 888.987644] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready [ 889.336577] mlx5_core :08:00.0 eth2: Link up [ 894.635836] Sun Mar 24 11:52:04 PM IST 2024 - DriVerTest Debug Heartbeat [ 940.431644] general protection fault, probably for non-canonical address 0x80020014: [#1] SMP NOPTI [ 940.432866] CPU: 7 PID: 94305 Comm: ethtool Tainted: G OE 5.15.0-1039.17.g0d63875-bluefield #1 [ 940.433970] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 940.435220] RIP: 0010:netlink_policy_dump_add_policy+0x95/0x160 [ 940.435893] Code: 48 c1 e0 04 4c 8b 34 01 4d 85 f6 74 5b 31 db eb 10 4c 89 e8 83 c3 01 48 c1 e0 04 39 5c 01 08 72 3f 89 d8 48 c1 e0 04 4c 01 f0 <0f> b6 10 83 ea 08 83 fa 01 77 dc 0f b7 50 02 48 8b 70 08 48 8d 7c [ 940.437921] RSP: 0018:ffa002d37a08 EFLAGS: 00010286 [ 940.438551] RAX: 80020014 RBX: RCX: ff1100027d00 [ 940.439351] RDX: fff8 RSI: 0018 RDI: ffa002d37a10 [ 940.440131] RBP: 0003 R08: 0040 R09: ff1100027d2d0f10 [ 940.440900] R10: 0318 R11: R12: ff1100011fa59bc0 [ 940.441683] R13: 0004 R14: 80020014 R15: 83fa6540 [ 940.442459] FS: 7f4a17993740() GS:ff1100085f9c() knlGS: [ 940.443394] CS: 0010 DS: ES: CR0: 80050033 [ 940.444044] CR2: 00429f50 CR3: 00012fc2e002 CR4: 00771ee0 [ 940.444847] DR0: DR1: DR2: [ 940.445639] DR3: DR6: fffe0ff0 DR7: 0400 [ 940.446431] PKRU: 5554 [ 940.446795] Call Trace: [ 940.447144] [ 940.447444] ? __die_body+0x1b/0x60 [ 940.447880] ? die_addr+0x39/0x60 [ 940.448315] ? exc_general_protection+0x1bc/0x3c0 [ 940.448867] ? asm_exc_general_protection+0x22/0x30 [ 940.449445] ? netlink_policy_dump_add_policy+0x95/0x160 [ 940.450058] ? netlink_policy_dump_add_policy+0xb2/0x160 [ 940.450714] ? ethtool_get_phc_vclocks+0x70/0x70 [ 940.451272] ctrl_dumppolicy_start+0xc4/0x2a0 [ 940.451788] ? ethnl_reply_init+0xd0/0xd0 [ 940.452284] ? __nla_parse+0x22/0x30 [ 940.452734] ? __cond_resched+0x15/0x30 [ 940.453211] ? kmem_cache_alloc_trace+0x44/0x390 [ 940.453750] genl_start+0xc3/0x150 [ 940.454179] __netlink_dump_start+0x175/0x250 [ 940.454706] genl_family_rcv_msg_dumpit.isra.0+0x9a/0x100 [ 940.455334] ? genl_family_rcv_msg_attrs_parse.isra.0+0xe0/0xe0 [ 940.455998] ? genl_unlock+0x20/0x20 [ 940.456453] ? genl_parallel_done+0x40/0x40 [ 940.456957] genl_rcv_msg+0x11f/0x2b0 [ 940.457421] ? genl_get_cmd+0x170/0x170 [ 940.457890] ? ctrl_dumppolicy_put_op.isra.0+0x1e0/0x1e0 [ 940.458515] ? genl_lock_done+0x60/0x60 [ 940.458987] ? genl_family_rcv_msg_doit.isra.0+0x110/0x110 [ 940.459634] netlink_rcv_skb+0x54/0x100 [ 940.460107] genl_rcv+0x24/0x40 [ 940.460504] netlink_unicast+0x18d/0x230 [ 940.460983] netlink_sendmsg+0x240/0x4a0 [ 940.461472] __sock_sendmsg+0x2f/0x40 [ 940.461922] __sys_sendto+0xee/0x160 [ 940.462384] ? __sys_recvmsg+0x56/0xa0 [ 940.462854] ? exit_to_user_mode_prepare+0x35/0x170 [ 940.463439] __x64_sys_sendto+0x25/0x30 [ 940.463906] do_syscall_64+0x35/0x80 [ 940.464368] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 940.464955] RIP: 0033:0x7f4a17aa940a [ 940.465415] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 940.467418] RSP: 002b:7ffc3612cac8 EFLAGS: 0246 ORIG_RAX: 002c [ 940.468284] RAX: ffda RBX: 00c3b3b0 RCX: 7f4a17aa940a [ 940.469057] RDX: 0024 RSI: 00c3b3b0 RDI: 0003 [ 940.469852] RBP: 00c3b2a0 R08: 7f4a17ba4200 R09: 000c [ 940.470674] R10: R11: 0246 R12: 00c3b340 [ 940.471470] R13: 00c3b350 R14: 7ffc3612caec R15: 00c3b3b0 [ 940.472257] [ 940.472570] Modules linked in: udp_diag(E) tcp_diag(E) inet_diag(E) iptable_raw(E) openvswitch(E) nsh(E) nf_conncount(E) rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) mlx5_core(OE) mlxfw(OE) auxiliary(OE) mlxdevm(OE) ib_uverbs(OE) ib_core(OE) mlx_compat(OE) memtrack(OE) psample(E) ptp(E) pps_core(E) nfsv3(E) nfs_acl(E) rpcsec_gss_krb5(E) xt_conntrack(E) auth_rpcgss(E)
[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Just updated the package from noble-proposed and the file is there with the agreed value. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in gamemode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in procps package in Ubuntu: Fix Committed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+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 2059958] [NEW] Include networking drivers used on Tegra platforms in initrd.img
Public bug reported: A race occurs between the probing of network devices and systemd- networkd detecting network devices to enable. This can be avoided by loading networking drivers earlier in the boot process, which we accomplish by including them in the initramfs. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Also affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx-modules-signed in Ubuntu. https://bugs.launchpad.net/bugs/2059958 Title: Include networking drivers used on Tegra platforms in initrd.img Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: A race occurs between the probing of network devices and systemd- networkd detecting network devices to enable. This can be avoided by loading networking drivers earlier in the boot process, which we accomplish by including them in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2059958/+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 2058808] Re: iwlwifi disconnect and crash - intel wifi7
Thank you! oem-6.5.0-1014 works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0: 0x9328 | interruptlink2 iwlwifi :05:00.0: 0xF46C | data1 iwlwifi :05:00.0: 0x0100 | data2 iwlwifi :05:00.0: 0x | data3 iwlwifi :05:00.0: 0xA0005E44 | beacon time iwlwifi :05:00.0: 0x2806818F | tsf low iwlwifi :05:00.0: 0x | tsf hi iwlwifi :05:00.0: 0x | time gp1 iwlwifi :05:00.0: 0x0BB840A7 | time gp2 iwlwifi :05:00.0: 0x0001 | uCode revision type iwlwifi :05:00.0: 0x0053 | uCode version major iwlwifi :05:00.0: 0xEC13314B | uCode version minor iwlwifi :05:00.0: 0x0472 | hw version iwlwifi :05:00.0: 0x00C80002 | board version iwlwifi :05:00.0: 0x03B7001C | hcmd iwlwifi :05:00.0: 0x67F68000 | isr0 iwlwifi :05:00.0: 0x0140 | isr1
[Kernel-packages] [Bug 2059846] Re: The canary thread is apparently starving. Taking actiont
Hello My iPad can be used correctly with a live USB 24.04 and I systematically use it in 22.04 to ensure the internet connection in the absence of a box. For troubleshooting, I used an iPhone -- 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/2059846 Title: The canary thread is apparently starving. Taking actiont Status in linux package in Ubuntu: New Bug description: Hello It is when i want connect mu iPAD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059846/+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 1684240] Re: Lagging square around mouse pointer
According to this bug: https://bugs.kde.org/show_bug.cgi?id=382812 the issue is not plasma-workspace, nor sddm, nor nvidia, but xorg and according to it the bug has been fixed in xorg. Closing now, if the bug still persists please reopen with details on a supported release. ** No longer affects: nvidia-graphics-drivers-375 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-384 (Ubuntu) ** Bug watch added: KDE Bug Tracking System #382812 https://bugs.kde.org/show_bug.cgi?id=382812 ** Changed in: plasma-workspace (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer Status in plasma-workspace package in Ubuntu: Fix Released Bug description: (This can also be an nvidia related problem) Mouse pointer behaves as if it has an invisible square attached to it. This square covers some area next to the pointer, but it is not always clear exactly where (a link to a screenshot is shown below, please note the white square with some text from the previous webpage displayed in that window). This makes selecting text difficult, as one never knows where exactly the selection ends. Also, scrolling in some windows becomes problematic, as the pointer shadows a part of the scrollbar. When a text is being typed, one needs to make sure that the pointer is parked sufficiently far from the text (so, to make a long story short, this is very annoying). This behavior does not depend on the choice of the cursor theme. (A link to the screenshot: https://goo.gl/photos/92KKGyFs3AkdxYb79) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: plasma-workspace 4:5.9.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 19 10:41:58 2017 InstallationDate: Installed on 2015-06-05 (684 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to zesty on 2017-04-13 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240/+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 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
A fix has been applied to vfs.fixes upstream and should land soon. I have tested this patch and verified that the panic no longer occurs. ** Changed in: linux (Ubuntu) Status: New => 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/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: Fix Committed Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Actually, it may not be an issue even for Jammy HWE. My copy shows block
cloning as an option that's off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059951] [NEW] mlxbf_gige: stop interface during shutdown
Public bug reported: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None ** 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/2059951 Title: mlxbf_gige: stop interface during shutdown Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+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 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
@dtl131 Why did the Ubuntu devs make this decision? Does this mean that the driver functionality will not work correctly and Ubuntu users will not be able to use Ubuntu? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
This issue is different. It's another problem with block copy. But
that's known to still be an issue. It's why block copy is disabled in
2.2.1. This is only an issue for the Jammy HWE, which has 2.2.0. No one
should be shipping 2.2.0 with anything. It should be replaced with 2.2.1
at least.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
FYI everyone, another corruption-with-zeros bug was found (so this issue
was not completely fixed): https://github.com/openzfs/zfs/issues/15933
The fixed was committed last week, and is not yet part of a release:
https://github.com/openzfs/zfs/pull/16019
** Bug watch added: github.com/openzfs/zfs/issues #15933
https://github.com/openzfs/zfs/issues/15933
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059237] Comment bridged from LTC Bugzilla
--- Comment From hariharan...@ibm.com 2024-04-01 04:37 EDT--- Kowshik, Can we close the defect. -- 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/2059237 Title: [Ubuntu-24.04] "array-index-out-of-bounds" error is observed after every reboot Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: == Comment:- Kowshik Jois B S == ---Problem Description--- Below trace messges are observed in dmesg after every reboot. [0.474287] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [0.475750] Freeing unused kernel image (initmem) memory: 8832K [0.507388] Checked W+X mappings: passed, no W+X pages found [0.507400] Run /init as init process [0.507403] with arguments: [0.507404] /init [0.507405] with environment: [0.507406] HOME=/ [0.507407] TERM=linux [0.507408] BOOT_IMAGE=/vmlinux-6.8.0-11-generic [0.511892] [ cut here ] [0.511904] UBSAN: array-index-out-of-bounds in /build/linux-MzA0lF/linux-6.8.0/arch/powerpc/kernel/module_64.c:353:17 [0.511909] index 0 is out of range for type 'char [*]' [0.511912] CPU: 13 PID: 1 Comm: systemd Not tainted 6.8.0-11-generic #11-Ubuntu [0.511917] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013) hv:phyp pSeries [0.511921] Call Trace: [0.511922] [c6683620] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.511931] [c6683650] [c0c7bc58] __ubsan_handle_out_of_bounds+0xc4/0x12c [0.511938] [c6683700] [c005d2a8] module_frob_arch_sections+0x4ec/0x8d0 [0.511943] [c66837e0] [c02b98cc] layout_and_allocate.isra.0+0x38/0x2a8 [0.511948] [c6683850] [c02b9dec] load_module+0x138/0xca0 [0.511953] [c6683990] [c02baca8] init_module_from_file+0xb4/0x14c [0.511958] [c6683a70] [c02baf70] sys_finit_module+0x230/0x48c [0.511963] [c6683b80] [c0033248] system_call_exception+0xe8/0x240 [0.511967] [c6683e50] [c000d15c] system_call_vectored_common+0x15c/0x2ec [0.511972] --- interrupt: 3000 at 0x7879b903b8a8 [0.511977] NIP: 7879b903b8a8 LR: CTR: [0.511980] REGS: c6683e80 TRAP: 3000 Not tainted (6.8.0-11-generic) [0.511984] MSR: 8000f033 CR: 48222428 XER: [0.511993] IRQMASK: 0 GPR00: 0161 7fffd683b580 7879b9166d00 0004 GPR04: 7879b8e0c160 0004 0010 0004 GPR08: 0001 GPR12: 7879b99d3a00 2000 0002 GPR16: 1b5c7d7453e0 7fffd683ba68 GPR20: 1b5c82154ae0 1b5c82142360 GPR24: 7879b957f7b0 1b5c82154ae0 1b5c82142160 GPR28: 7879b8e0c160 0002 1b5c82154ae0 1b5c82142380 [0.512029] NIP [7879b903b8a8] 0x7879b903b8a8 [0.512032] LR [] 0x0 [0.512034] --- interrupt: 3000 [0.512036] ---[ end trace ]--- [0.518326] systemd[1]: Inserted module 'autofs4' [0.521570] systemd[1]: systemd 255.2-3ubuntu2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) [0.521583] systemd[1]: Detected virtualization powervm. [0.521589] systemd[1]: Detected architecture ppc64-le. [0.521593] systemd[1]: Running in initrd. [0.521743] systemd[1]: No hostname configured, using default hostname. [0.521789] systemd[1]: Hostname set to . [0.521847] systemd[1]: Initializing machine ID from random generator. [0.600736] systemd[1]: Queued start job for default target initrd.target. Machine Type = P10 LPAR Contact Information = Kowshik Jois B S kowshik.j...@in.ibm.com ---Steps to Reproduce--- 1. reboot the system 2. Once the system is booted back, look at dmesg ---uname output--- Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux Additional Information: Same trace messages are seen on L2 guest as well. == Comment: - Kowshik Jois B S == Hello
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
The IPU6 webcam still does not work on my Dell XPS 16 (9640). I've tested it with Ubuntu 24.04 daily builds including with the 6.9-rc1 kernel. What information would you need to check the problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: Fix Released Status in ivsc-driver source package in Mantic: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI
[Kernel-packages] [Bug 2059781] Re: [22.04.4] The computer freezes after standby mode.
Hello, Thank you for your answers. Unfortunately, I don't know which package is experiencing the problem, it happens even if no application is running. Is there a way I can narrow down the problem ? I ran "apport-collect 2059781", I got this message : jr@jr-E16:~$ apport-collect 2059781 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=m7ZrdKqbtZvrbs09kxR1_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Package linux-oem-6.5 not installed and no hook available, ignoring jr@jr-E16:~$ Did it work ? Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059781 Title: [22.04.4] The computer freezes after standby mode. Status in linux-oem-6.5 package in Ubuntu: New Bug description: Hello, I declared the problem here : https://ubuntuforums.org/showthread.php?t=2494851 I installed the latest 22.04.4 LTS version. When I put my new Lenovo computer to sleep mode, it freezes (no Internet anymore and/or programs refuse to launch, I'm logged out, ...). Usually I have to shut down using the power button. Expected result : I get a functional environment after wake-up here is the hardware diagnostics, which seem fine : https://linux- hardware.org/?probe=0a59bd119b, nothing wrong at first sight. Lenovo tells me everything's fine hardware-wise. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2059781/+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
