[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.15.0.1055.51)
All autopkgtests for the newly accepted linux-meta-gcp (5.15.0.1055.51) for jammy have finished running. The following regressions have been reported in tests triggered by the package: systemd/249.11-0ubuntu3.12 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
9:14:36 No SSL Possible. Attached.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5756414/+files/prevboot.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 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=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
This certainly effected my use of kubuntu-desktop. As far as I know, kubuntu requires X11 so I can't believe that it can be ignored. Dennis ** Changed in: linux-raspi (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in SDDM: New Status in linux-raspi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/2044718/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
** Also affects: sddm Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in SDDM: New Status in linux-raspi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/sddm/+bug/2044718/+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 2058109] [NEW] Kernel 5.15.0-100 breaks Intel NIC
You have been subscribed to a public bug: From syslog: Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and update motd... Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3% ...trimmed content Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new metadata: 0 local devices supported Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated successfully. Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and update motd. Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:05:00 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount: Deactivated successfully. Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:30:01 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount: Deactivated successfully. Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: #AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3 Mar 15 14:07:33 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount: Deactivated successfully. Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDH <9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDT <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_use <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_clean<9e> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] time_stamp <1348a0aab> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch<9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] jiffies <1348a0bb0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch.status <0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status <40080083> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status <3800> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDH <9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDT <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_use <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_clean<9e> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] buffer_info[next_to_clean]: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] time_stamp <1348a0aab> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_watch<9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] jiffies <1348a0da1> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_watch.status <0> Mar 15 14:20:05 kvmMini kernel:
[Kernel-packages] [Bug 2058109] Re: Kernel 5.15.0-100 breaks Intel NIC
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: jammy -- 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/2058109 Title: Kernel 5.15.0-100 breaks Intel NIC Status in linux package in Ubuntu: New Bug description: From syslog: Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and update motd... Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3% ...trimmed content Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100% Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new metadata: 0 local devices supported Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated successfully. Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and update motd. Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:05:00 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount: Deactivated successfully. Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: #AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xf80746442fb3 Mar 15 13:30:01 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount: Deactivated successfully. Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: #AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xf80521c42fb3 Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: #AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xf8041de42fb3 Mar 15 14:07:33 kvmMini systemd[1]: run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount: Deactivated successfully. Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDH <9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] TDT <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_use <9> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_clean<9e> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]: Mar 15 14:20:03 kvmMini kernel: [3526150.403065] time_stamp <1348a0aab> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch<9f> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] jiffies <1348a0bb0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] next_to_watch.status <0> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status <40080083> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status <796d> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status <3800> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status<3000> Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status <10> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e :00:1f.6 eno2: Detected Hardware Unit Hang: Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDH <9f> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] TDT <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_use <9> Mar 15 14:20:05 kvmMini kernel: [3526152.391042] next_to_clean<9e> Mar 15 14:20:05 kvmMini kernel:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.4.0.1121.114)
All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1121.114) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.23 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-12 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while :
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-10 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while :
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-9 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while : ;
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: llvm-toolchain-15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: llvm-toolchain-16 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while :
[Kernel-packages] [Bug 2038645] Re: Ubuntu Mate 22.04 scaling problem
After the latest driver update, the system was unable to load Nvidia drivers.
Driver Manager was unable to install / load other drivers.
( /usr/bin/software-properties-gtk --open-tab=4 )
Something ... " libhvloc-plugins: requires libxnvctrl0 " ...
I used
apt-get purge *nvidia*
apt --fix-broken install
apt autoremove
apt install nvidia-driver-545
and that solved my problem with manager for drivers.
Thank you for supporting VESA.
During the repair, I used both the Noveau and VESA drivers.
At the moment:
1. I still can't save resolution in nvidia-settings
" Unable to open X config file '/etc/X11/xorg.conf' for writing "
2. changing from 1920x1080 to 4K now working
3. About Steam icon I'll try reporting to Steam on github
4. There are two problems with scaling.
4.1 The image is smaller, but without the menu bar.
- Let's assume it's a driver or monitor problem.
4.2 Some TVs can scale the image automatically, but my monitor doesn't.
Enjoy your work,
Good luck.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038645
Title:
Ubuntu Mate 22.04 scaling problem
Status in nvidia-settings package in Ubuntu:
New
Bug description:
I changed monitor from 24" LG to 32" Samsung LS32A704NWPXEN
The situation looks like this:
1. 4K starts default, I can save settings to /etc/X11/xorg.conf only with
sudo chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit
2. Problem I have with HDMI and DisplayPort, the situation is the same,
after changing from 1920x1080 to 4K I can see 1/4 of the screen
lower left part of the screen.
The problem does not occur from 4K to 1920x1080 when 4K is default.
To switch to 4K I need remove /etc/X11/xorg.conf and reboot system.
3. Scaling in Mate does not change the size of the Steam icon xD wtf? Why?
I have only option 100% and 200%.
4. Scaling with Nvidia, ( Option Underscan in second tab of nvidia-settings,
default is 0 )
I managed to check by placing the panel at the top and then changing the
scaling in nvidia
(because the image is cut off from the bottom)
It seems to me that this option does not scale, but crops the image.
Because the font and icon sizes looks identical.
Only the picture frame is cut off and the center remains.
5. This monitor does not have an image scaling option.
nvidia-settings 510.47.03-0ubuntu1
System Info
{
inxi -Fxxrzc0
System:
Kernel: 5.15.0-84-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: MATE 1.26.0 wm: marco dm: LightDM
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: MSI model: B150M PRO-VDH (MS-7982) v: 1.0
serial: UEFI: American Megatrends v: 3.H0
date: 07/10/2018
CPU:
Info: quad core model: Intel Core i5-6400 bits: 64 type: MCP
arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 2256 high: 3219 min/max: 800/3300 cores: 1: 1271
2: 1623 3: 2912 4: 3219 bogomips: 21599
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
v: 525.125.06 pcie: speed: 2.5 GT/s lanes: 8 ports: active: none
off: HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2 bus-ID: 01:00.0
chip-ID: 10de:2507
Display: x11 server: X.Org v: 1.21.1.4 compositors: 1: Picom v: 9
2: marco v: 1.26.0 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 69
Monitor-1: HDMI-0 res: 1920x1080 dpi: 70 diag: 801mm (31.5")
OpenGL: renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
v: 4.6.0 NVIDIA 525.125.06 direct render: Yes
...
Sensors:
System Temperatures: cpu: 29.8 C pch: 37.0 C mobo: 27.8 C gpu: nvidia
temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: 3100 apt: 3082 snap: 18
Active apt repos in: /etc/apt/sources.list
1: deb http://pl.archive.ubuntu.com/ubuntu/ jammy main restricted
2: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
3: deb http://pl.archive.ubuntu.com/ubuntu/ jammy universe
4: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates universe
5: deb http://pl.archive.ubuntu.com/ubuntu/ jammy multiverse
6: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
7: deb http://pl.archive.ubuntu.com/ubuntu/ jammy-backports main
restricted universe multiverse
8: deb http://security.ubuntu.com/ubuntu jammy-security main restricted
9: deb http://security.ubuntu.com/ubuntu jammy-security universe
10: deb http://security.ubuntu.com/ubuntu jammy-security multiverse
No active apt repos in:
/etc/apt/sources.list.d/minetestdevs-ubuntu-stable-jammy.list
Active apt repos in:
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
Hello, I see https://git.launchpad.net/ubuntu/+source/gcc-13/commit/?id=6c5be2a496335c513dbe6fa85df2402cfc0f0a8b imported the LLVM patch for Asan. There was also a similar change in LLVM for LSan: https://github.com/llvm/llvm- project/commit/5ffe955570a5d743bbbae204ce1b132e89fa86dc. I was wondering if it was planned to also include that patch ? I've experience the same kind of failure with Lsan on GCC 13: https://github.com/phil- blain/git/actions/runs/8281327655/job/22659588626. This is the `linux- leaks` job in the Git CI suite which uses GCC 13.1.0 from the ubuntu- toolchain-r/test PPA. Side question: will the PPA also be updated with the Asan patch? Thanks! -- 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/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: Confirmed Status in gcc-11 package in Ubuntu: Confirmed Status in gcc-12 package in Ubuntu: Confirmed Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: Confirmed Status in llvm-toolchain-16 package in Ubuntu: Confirmed Status in gcc-10 source package in Noble: Confirmed Status in gcc-11 source package in Noble: Confirmed Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Committed Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Confirmed Status in linux source package in Noble: Confirmed Status in llvm-toolchain-14 source package in Noble: Confirmed Status in llvm-toolchain-15 source package in Noble: Confirmed Status in llvm-toolchain-16 source package in Noble: Confirmed Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1
[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller
I have encountered similar problem in Linux 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux . Here is my hardware infomation: ``` $ sudo lspci -knnv -s 3:00.0 03:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] (rev 11) (prog-if 01 [AHCI 1.0]) Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 13 I/O ports at e050 [size=8] I/O ports at e040 [size=4] I/O ports at e030 [size=8] I/O ports at e020 [size=4] I/O ports at e000 [size=32] Memory at fc41 (32-bit, non-prefetchable) [size=2K] Expansion ROM at fc40 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [e0] SATA HBA v0.0 Capabilities: [100] Advanced Error Reporting Kernel driver in use: ahci Kernel modules: ahci ``` and my syslog(snipped): ``` kernel: [2.076538] ata14.00: ATAPI: MARVELL VIRTUAL, 1.09, max UDMA/66 kernel: [2.082784] ahci :03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xcffe3840 flags=0x0050] kernel: [ 74.990910] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) kernel: [ 80.032244] ata14.00: qc timeout after 5000 msecs (cmd 0xa1) kernel: [ 80.532224] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) ``` I haven't reproduced this in Linux5.15.0. Does anyone have information about this? -- 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/1810239 Title: amd_iommu conflict with Marvell 88SE9230 SATA Controller Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: Fix Released Status in linux package in Fedora: Unknown Bug description: Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153 WORKAROUND: Use kernel boot parameter: amd_iommu=off --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythfe 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mythnew/swap InstallationDate: Installed on 2016-07-02 (913 days ago) InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/mythnew-root ro verbose drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.173.2 RfKill: Tags: bionic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago) UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2c dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810239/+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 2058124] [NEW] Touchpad and Microphone not recognized
Public bug reported: Ubuntu20.04 Kernel:`5.15.0-100-generic #110~20.04.1-Ubuntu SMP Tue Feb 13 14:25:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux` The TouchPad and Microphone in my HP Laptop could not be recognized, but both are OK in Windows 11 system. `xinput` command result： ``` (base) ➜ ~ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Instant USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ HP True Vision FHD Camera: HP T id=10 [slave keyboard (3)] ↳ Intel HID events id=11 [slave keyboard (3)] ↳ Intel HID 5 button array id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ HP WMI hotkeysid=14 [slave keyboard (3)] ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-100.110~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 09:10:00 2024 InstallationDate: Installed on 2024-03-02 (14 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "sound.png" https://bugs.launchpad.net/bugs/2058124/+attachment/5756473/+files/sound.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2058124 Title: Touchpad and Microphone not recognized Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Ubuntu20.04 Kernel:`5.15.0-100-generic #110~20.04.1-Ubuntu SMP Tue Feb 13 14:25:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux` The TouchPad and Microphone in my HP Laptop could not be recognized, but both are OK in Windows 11 system. `xinput` command result： ``` (base) ➜ ~ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Instant USB Optical Mouse id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP True Vision FHD Camera: HP T id=10 [slave keyboard (3)] ↳ Intel HID eventsid=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ HP WMI hotkeys id=14 [slave keyboard (3)] ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-100-generic 5.15.0-100.110~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-100.110~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 09:10:00 2024 InstallationDate: Installed on 2024-03-02 (14 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2058124/+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 1906067] Re: Boot from ISO - exFAT support missing
*** This bug is a duplicate of bug 2038694 *** https://bugs.launchpad.net/bugs/2038694 ** Package changed: linux (Ubuntu) => casper (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906067 Title: Boot from ISO - exFAT support missing Status in casper package in Ubuntu: Confirmed Bug description: Please add support for booting the ISO image via grub2 (loopback) in initrd. For larger images and a USB sticks, FAT32 is no longer sufficient. Most popular distributions already have support for exFAT in initrd (they can find and mount ISO on this filesystem). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1906067/+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
