[Kernel-packages] [Bug 2081797] Re: linux in noble ftbfs with an updated GCC 13 (13.3.0)
fixed with the december update
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2081797
Title:
linux in noble ftbfs with an updated GCC 13 (13.3.0)
Status in linux package in Ubuntu:
Fix Released
Bug description:
seen while preparing a toolchain upgrade, linux in noble ftbfs with an
update GCC 13 (13.3.0)
[...]
check-config: loading annotations from
/<>/debian.master/config/annotations
check-config: CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND changed from y to -:
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64':
'y', 's390x': 'y'}>)
check-config: 1 config options have changed
make: *** [debian/rules.d/4-checks.mk:15: config-prepare-check-generic] Error
1
the check comes from init/Kconfig:
config GCC_ASM_GOTO_OUTPUT_WORKAROUND
bool
depends on CC_IS_GCC && CC_HAS_ASM_GOTO_OUTPUT
# Fixed in GCC 14, 13.3, 12.4 and 11.5
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921
default y if GCC_VERSION < 110500
default y if GCC_VERSION >= 12 && GCC_VERSION < 120400
default y if GCC_VERSION >= 13 && GCC_VERSION < 130300
the GCC issue is already fixed in the gcc-13 version in noble, but
unfortunately based on a version check.
so how to get a successful build with an updated compiler?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081797/+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 1769301] Re: resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument'
closing, no additional information provided
** Changed in: libselinux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
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/1769301
Title:
resetting /proc/thread-self/attr/fscreate results in 'Invalid
Argument'
Status in libselinux package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Won't Fix
Bug description:
root@ubuntu:~# useradd -g 100 tst003
useradd: failure while writing changes to /etc/passwd
root@ubuntu:~# sestatus
SELinux status: enabled
SELinuxfs mount:/sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: requested (insecure)
Max kernel policy version: 31
The problem does not occur when SELinux is complete disabled.
Please note that a very similar problem occurs using groupadd:
root@ubuntu:~# groupadd tstgrp001
groupadd: failure while writing changes to /etc/group
= journal =
(Please note that there is *no* AVC!)
May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004,
GID=100, home=/home/tst003, shell=/bin/sh
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0
res=success'
May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to
/etc/passwd
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0
res=failed'
May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted
= ltrace =
[pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
[pid 1074] <... fflush resumed> )= 0
[pid 1074] fileno(0x5595b21c6200)= 12
[pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154
[pid 1074] SYS_fsync(12) = 0
[pid 1074] <... fsync resumed> ) = 0
[pid 1074] fclose(0x5595b21c6200
[pid 1074] SYS_close(12) = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1
[pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
[pid 1074] <... utime resumed> ) = 0
[pid 1074] fclose(0x5595b21af2a0
[pid 1074] SYS_close(5) = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2
[pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
[pid 1074] SYS_write(5, nil, 0) = -22
[pid 1074] SYS_close(5) = 0
[pid 1074] <... setfscreatecon resumed> )= 0x
[pid 1074] free(0x5595b21b9dc0) =
[pid 1074] free(0x5595b21b8a00) =
[pid 1074] strlen("x") = 1
[pid 1074] memset(0x5595b21b7560, '\0', 1) = 0x5595b21b7560
[pid 1074] free(0x5595b21b7560) =
[pid 1074] free(0x5595b21b94e0) =
[pid 1074] free(0x5595b21b9000) =
[pid 1074] free(0x5595b21b8fc0) =
= strace =
write(12, "root:x:"..., 1360) = 1360
fsync(12) = 0
close(12) = 0
utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */,
modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0
close(5)= 0
openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5
write(5, NULL, 0) = -1 EINVAL (Invalid argument)
close(5)= 0
= Version Information =
root@ubuntu:~# lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa
ii passwd1:4.5-1ubuntu1
amd64change and administer password and group data
root@ubuntu:~# dpkg -l | grep selinux
ii libselinux1:amd64 2.7-2build2
amd64SELinux runtime shared libraries
ii python3-selinux 2.7-2build2
amd64Python3 bindings to SELinux shared libraries
ii selinux-basics0.5.6
all SELinux basic support
i
[Kernel-packages] [Bug 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
Well that was really painful to find. After hours of bisecting and building kernel manually I've found it: Kernel (and Ubuntu Devs) enabled Intel IOMMU by default: * https://github.com/torvalds/linux/commit/792fb43ce2c9 * https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440 Ubuntu Devs were even aware that this might break older systems: > A downside is that this change may introduce boot regressions on old systems (especially those with buggy firmware). However, you can workaround this issue by disabling Intel IOMMU manually by setting `intel_iommu=off` in /etc/default/grub -> GRUB_CMDLINE_LINUX_DEFAULT This made my 24.04 system boot the first time with the shipped 6.8 kernel. -- 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/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
6.6.0 -> Works 6.6.12 -> Works 6.6.15 -> Works 6.6.17 -> Works 6.6.18 -> Works 6.6.19 -> Broken 6.6.25 -> Broken -- 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/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
@romwriter: This works out fine for me: ``` $ lspci | grep SATA 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) ``` -- 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/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
Further tests showed, that it seems to be related to the Marvell 88SE9230 SATA chip my board is using. Connecting the disk to the second SATA chip available on the board, the OS boots up properly. Sadly this isn't an option for operating the system because those ports are normally used for my storage array. @romwriter: Can you confirm that your board is using a similar Marvell chipset? -- 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/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
Further testing with mainline kernel: 5.19.17 -> Works 6.2.0 -> Works 6.5.13 -> Works, but already seeing a LOT of strange ata log messages in dmesg. See attached dmesg log. ** Attachment added: "dmesg-6.5.0-060500-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+attachment/5825404/+files/dmesg-6.5.0-060500-generic.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/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2060709] Re: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate
Seeing similar issues on my Gigabyte Z87X-UD5H with a Samsung 840 SSD. Booting worked fine for years with same hardware. Upgrading to 24.04 and Kernel 6.8.0 ends in broken boot state. My current workaround is to boot the old 5.15 kernel. Using 6.8.6 mainline didn't work for me. ** Attachment added: "broken-boot.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+attachment/5825403/+files/broken-boot.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060709 Title: Kernel 6.8 and Gigabyte F2A88XM-D3H mainboard do not collaborate Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu with kernel 5.15 runs fine. With kernel 6.8, the system does not boot up. USB peripherals do not work, keyboard LEDs are off. Further error messages in screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xxx1799 F wireplumber /dev/snd/controlC0: xxx1799 F wireplumber /dev/snd/seq:xxx1797 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Apr 9 17:28:31 2024 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp1s0no wireless extensions. tun0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-101-generic root=UUID=1fb4c915-afb5-4195-90f9-1e21e105aa17 ro noplymouth PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-101-generic N/A linux-backports-modules-5.15.0-101-generic N/A linux-firmware 20240202.git36777504-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+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 2081797] Re: linux in noble ftbfs with an updated GCC 13 (13.3.0)
** Summary changed:
- linux in noble ftbfs with an update GCC 13 (13.3.0)
+ linux in noble ftbfs with an updated GCC 13 (13.3.0)
--
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/2081797
Title:
linux in noble ftbfs with an updated GCC 13 (13.3.0)
Status in linux package in Ubuntu:
New
Bug description:
seen while preparing a toolchain upgrade, linux in noble ftbfs with an
update GCC 13 (13.3.0)
[...]
check-config: loading annotations from
/<>/debian.master/config/annotations
check-config: CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND changed from y to -:
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64':
'y', 's390x': 'y'}>)
check-config: 1 config options have changed
make: *** [debian/rules.d/4-checks.mk:15: config-prepare-check-generic] Error
1
the check comes from init/Kconfig:
config GCC_ASM_GOTO_OUTPUT_WORKAROUND
bool
depends on CC_IS_GCC && CC_HAS_ASM_GOTO_OUTPUT
# Fixed in GCC 14, 13.3, 12.4 and 11.5
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921
default y if GCC_VERSION < 110500
default y if GCC_VERSION >= 12 && GCC_VERSION < 120400
default y if GCC_VERSION >= 13 && GCC_VERSION < 130300
the GCC issue is already fixed in the gcc-13 version in noble, but
unfortunately based on a version check.
so how to get a successful build with an updated compiler?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081797/+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 2081797] [NEW] linux in noble ftbfs with an update GCC 13 (13.3.0)
Public bug reported:
seen while preparing a toolchain upgrade, linux in noble ftbfs with an
update GCC 13 (13.3.0)
[...]
check-config: loading annotations from
/<>/debian.master/config/annotations
check-config: CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND changed from y to -:
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64':
'y', 's390x': 'y'}>)
check-config: 1 config options have changed
make: *** [debian/rules.d/4-checks.mk:15: config-prepare-check-generic] Error 1
the check comes from init/Kconfig:
config GCC_ASM_GOTO_OUTPUT_WORKAROUND
bool
depends on CC_IS_GCC && CC_HAS_ASM_GOTO_OUTPUT
# Fixed in GCC 14, 13.3, 12.4 and 11.5
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921
default y if GCC_VERSION < 110500
default y if GCC_VERSION >= 12 && GCC_VERSION < 120400
default y if GCC_VERSION >= 13 && GCC_VERSION < 130300
the GCC issue is already fixed in the gcc-13 version in noble, but
unfortunately based on a version check.
so how to get a successful build with an updated compiler?
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2081797
Title:
linux in noble ftbfs with an update GCC 13 (13.3.0)
Status in linux package in Ubuntu:
New
Bug description:
seen while preparing a toolchain upgrade, linux in noble ftbfs with an
update GCC 13 (13.3.0)
[...]
check-config: loading annotations from
/<>/debian.master/config/annotations
check-config: CONFIG_GCC_ASM_GOTO_OUTPUT_WORKAROUND changed from y to -:
policy<{'amd64': 'y', 'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64':
'y', 's390x': 'y'}>)
check-config: 1 config options have changed
make: *** [debian/rules.d/4-checks.mk:15: config-prepare-check-generic] Error
1
the check comes from init/Kconfig:
config GCC_ASM_GOTO_OUTPUT_WORKAROUND
bool
depends on CC_IS_GCC && CC_HAS_ASM_GOTO_OUTPUT
# Fixed in GCC 14, 13.3, 12.4 and 11.5
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113921
default y if GCC_VERSION < 110500
default y if GCC_VERSION >= 12 && GCC_VERSION < 120400
default y if GCC_VERSION >= 13 && GCC_VERSION < 130300
the GCC issue is already fixed in the gcc-13 version in noble, but
unfortunately based on a version check.
so how to get a successful build with an updated compiler?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081797/+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 2076576] Re: 5.15.0-118: NFS causes suspend to fail
Can confirm that this has been fixed with 5.15.0.122 on Ubuntu 22.04. -- 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/2076576 Title: 5.15.0-118: NFS causes suspend to fail Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: When attempting to suspend, I see the following in dmesg: [ 72.229192] PM: suspend entry (deep) [ 72.233002] Filesystems sync: 0.003 seconds [ 72.233311] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 72.234873] OOM killer disabled. [ 72.234874] Freezing remaining freezable tasks ... [ 92.242978] Freezing of tasks failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): [ 92.243079] task:NFSv4 callback state:I stack:0 pid: 1696 ppid: 2 flags:0x4000 [ 92.243090] Call Trace: [ 92.243094] [ 92.243099] __schedule+0x24e/0x590 [ 92.243111] schedule+0x69/0x110 [ 92.243119] nfs41_callback_svc+0x179/0x180 [nfsv4] [ 92.243202] ? wait_woken+0x70/0x70 [ 92.243212] ? nfs_map_gid_to_group+0x120/0x120 [nfsv4] [ 92.243274] kthread+0x127/0x150 [ 92.243283] ? set_kthread_struct+0x50/0x50 [ 92.243291] ret_from_fork+0x1f/0x30 [ 92.243302] [ 92.243411] Restarting kernel threads ... done. [ 92.243670] OOM killer enabled. [ 92.243671] Restarting tasks ... done. [ 92.255414] thermal thermal_zone1: failed to read out thermal zone (-61) [ 92.255434] PM: suspend exit [ 92.255480] PM: suspend entry (s2idle) I've restarted several times, and the problem is consistent and does not seem to be present in linux-image-5.15.0-117-generic $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ cat /proc/version_signature Ubuntu 5.15.0-118.128-generic 5.15.160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076576/+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 2052835] Re: Error running program on cifs filesystem
On my system 6.8.0-40-generic 22.04.3-Ubuntu this bug is still present. Found this notice after an hour... Try cache=strict as workaround. It works so far. Also cache=loose - but this is a bad option, i think. Is a scheduled plan to fix this? -- 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/2052835 Title: Error running program on cifs filesystem Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Hi When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error In the kernel log there is: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] [ cut here ] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: GW 6.5.0-17-generic #17~22.04.1-Ubuntu Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:b4ee07117b90 EFLAGS: 00010297 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: 9de487836418 RBX: 9de4878363c0 RCX: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: b4ee07117bdc RSI: 0100 RDI: 9de487836418 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: b4ee07117c18 R08: 0100 R09: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: R11: R12: 9de48f998000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: 9de48f982400 R14: 0100 R15: 9de49ba32000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 7f8f2ae67740() GS:9dfb5e20() knlGS: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: ES: CR0: 80050033 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 558a1cb1bf98 CR3: 0001abfd4001 CR4: 003706e0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: DR1: DR2: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: DR6: fffe0ff0 DR7: 0400 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190
[Kernel-packages] [Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
the failing autopkg tests are now down to two packages: - software-properties (all architectures) this is unrelated to the dpkg upload, it also fails for all other packages triggering this test in -proposed. - libxmlada (armhf) This is expected, needs updates for the 64bit time_t changes on armhf. I will follow-up on this with the gcc-13 and gcc-14 uploads to 24.04 LTS. The package itself looks ok, and also examining build logs and packages for the no-change uploads (see LP: #2076340) look ok. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- 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/2064538 Title: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain) Status in Ubuntu on IBM z Systems: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: Fix Committed Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: SRU Justification: [ Impact ] * The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. * This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. * The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit- frame-pointers should not be used on IBM Z. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg tes
[Kernel-packages] [Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
the failing autopkg tests are now down to two packages: - software-properties (all architectures) this is unrelated to the dpkg upload, it also fails for all other packages triggering this test in -proposed. - libxmlada (armhf) This is expected, needs updates for the 64bit time_t changes on armhf. I will follow-up on this with the gcc-13 and gcc-14 uploads to 24.04 LTS. The package itself looks ok, and also examining build logs and packages for the no-change uploads (see LP: #2076340) look ok. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: Fix Committed Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: SRU Justification: [ Impact ] * Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. * Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit- frame-pointers should not be used on Power. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg test build and/or builds of other packages with the modified dpkg version in place would show this. * The settings in dpkg might be overwritten by other settings/packages. Tests like above, would show this. * One may think there could be issues in an environment where some packages have frame-pointer enabled and other don't. This is fine and was confirmed by IBM tool
[Kernel-packages] [Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
test rebuild of a package with this dpkg upload: https://launchpad.net/~doko/+archive/ubuntu/ppa/+sourcepub/16312933/+listing-archive-extra reference build: https://launchpad.net/ubuntu/+source/lz4/1.9.4-1build1 - ppc64el: the -fno-omit-frame-pointer flags are gone - s390x: only -mbackchain is used - no build flag changes on other architectures this addresses item 3) for the validation. -- 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/2064538 Title: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain) Status in Ubuntu on IBM z Systems: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: SRU Justification: [ Impact ] * The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. * This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. * The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit- frame-pointers should not be used on IBM Z. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg test build and/or builds of other packages with the modified dpkg version in place would show this. * The settings in dpkg might be overwritten by other settings/packages. Tests like above, would show this. * One may think there could be issue
[Kernel-packages] [Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
test rebuild of a package with this dpkg upload: https://launchpad.net/~doko/+archive/ubuntu/ppa/+sourcepub/16312933/+listing-archive-extra reference build: https://launchpad.net/ubuntu/+source/lz4/1.9.4-1build1 - ppc64el: the -fno-omit-frame-pointer flags are gone - s390x: only -mbackchain is used - no build flag changes on other architectures this addresses item 3) for the validation. -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: Fix Committed Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: SRU Justification: [ Impact ] * Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. * Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit- frame-pointers should not be used on Power. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg test build and/or builds of other packages with the modified dpkg version in place would show this. * The settings in dpkg might be overwritten by other settings/packages. Tests like above, would show this. * One may think there could be issues in an environment where some packages have frame-pointer enabled and other don't. This is fine and was confirmed by IBM toolchain team and ours (as well as by a longer running test system, with FP disabled in kernel, that showed no issues - like expected). [ Other Info ] * These changes were implemented during the opening of the oracular series. The very
[Kernel-packages] [Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
for convenience, the diff for the noble upload. we'll do a binary copy for the upload to -proposed, because the package needs to reach the security pocket as well. ** Patch added: "dpkg.debdiff" https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2064539/+attachment/5801859/+files/dpkg.debdiff ** Description changed: Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on Power. + + SRU: + + these changes were implemented during the opening of the oracular + series. The very same changes are backported to 24.04 LTS. These only + affect the ppc64el and s390x architectures, for other architectures it's + a no-change upload. + + We didn't see any fallout for these changes during the development on + the oracular series, and therefore don't expect any fallout or + regressions in 24.04 LTS either. -- 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/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) Status in The Ubuntu-power-systems project: New Status in dpkg package in Ubuntu: Fix Released Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in dpkg source package in Noble: New Status in glibc source package in Noble: New Status in linux source package in Noble: New Status in dpkg source package in Oracular: Fix Released Status in glibc source package in Oracular: New Status in linux source package in Oracular: New Bug description: Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame-pointers should not be used on Power. SRU: these changes were implemented during the opening of the oracular series. The very same changes are backported to 24.04 LTS. These only affect the ppc64el and s390x architectures, for other architectures it's a no-change upload. We didn't see any fallout for these changes during the development on the oracular series, and therefore don't expect any fallout or regressions in 24.04 LTS either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064539/+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 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
In my case I face the same issue with the "delayed_fput" module. And yes, I am also running btrfs (OS Ubuntu 22.04.4 LTS / Kernel 6.5.0-45-generic). [ 208.207228] workqueue: delayed_fput hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 259.794567] workqueue: delayed_fput hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 378.217600] workqueue: delayed_fput hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 485.636678] workqueue: delayed_fput hogged CPU for >1us 32 times, consider switching to WQ_UNBOUND -- 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/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: dmesg has multiple messages: [ 852.580542] evict_inodes inode be24a21a, i_count = 1, was skipped! [ 852.580543] evict_inodes inode 2aea522e, i_count = 1, was skipped! [ 852.580544] evict_inodes inode 48d75a5c, i_count = 1, was skipped! [ 852.580545] evict_inodes inode d8a9e4c2, i_count = 1, was skipped! [ 852.580546] evict_inodes inode 3d2c905c, i_count = 1, was skipped! [ 852.580547] evict_inodes inode e5b1b232, i_count = 1, was skipped! [ 852.580548] evict_inodes inode 97383a6b, i_count = 1, was skipped! [ 852.580549] evict_inodes inode ca8e2b44, i_count = 1, was skipped! [ 1751.869281] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 1781.467278] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 1806.065364] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 1901.993975] evict_inodes inode abaa740e, i_count = 1, was skipped! [ 1901.993981] evict_inodes inode 515b9bf8, i_count = 1, was skipped! [ 1901.993983] evict_inodes inode 1a69d536, i_count = 1, was skipped! [ 1901.993984] evict_inodes inode 1403f675, i_count = 1, was skipped! [ 1901.993985] evict_inodes inode 757de21a, i_count = 1, was skipped! [ 1901.993986] evict_inodes inode 0cee9028, i_count = 1, was skipped! [ 1901.993987] evict_inodes inode d2827e77, i_count = 1, was skipped! Description:Ubuntu 22.04.3 LTS Release:22.04 linux-oem-22.04d: Installed: 6.5.0.1004.4 Candidate: 6.5.0.1004.4 Seems related to #2037214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+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 2043801] Re: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all
this is a no-go for now, linux-libc-dev providing all linux-libc-dev- cross-, making the c-t-b packages uninstallable and forcing the /usr/include on the include path of the cross toolchain -- 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/2043801 Title: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-mipsen package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: make linux-libc-dev & linux-libc-dev-cross M-A:foreign Arch:all 1) there was broad agreement in Riga 2) there is partial agreement in Debian too https://lists.debian.org/debian-kernel/2023/11/msg00131.html https://salsa.debian.org/kernel-team/linux/-/merge_requests/909/diffs 3) attempt to implement this in noble 4) changes required to: linux linux-uapi cross-toolchain-base-* 5) if things don't work out, fallback plan is to revert linux-libc- dev-cross; or to revert linux-libc-dev changes; or both of them and go back to how things were in mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/2043801/+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 2060560] Re: Remove obsolete kernels from noble
Removing packages from noble: linux-meta-starfive 6.5.0.1002.4 in noble linux-headers-starfive 6.5.0.1002.4 in noble riscv64 linux-image-starfive 6.5.0.1002.4 in noble riscv64 linux-starfive 6.5.0.1002.4 in noble riscv64 linux-tools-starfive 6.5.0.1002.4 in noble riscv64 linux-starfive 6.5.0-1002.3 in noble linux-buildinfo-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-headers-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-image-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-modules-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-modules-extra-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble amd64 linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble arm64 linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble armhf linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble i386 linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble ppc64el linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble riscv64 linux-starfive-headers-6.5.0-1002 6.5.0-1002.3 in noble s390x linux-starfive-tools-6.5.0-1002 6.5.0-1002.3 in noble riscv64 linux-tools-6.5.0-1002-starfive 6.5.0-1002.3 in noble riscv64 linux-laptop 6.5.0-1004.7 in noble linux-buildinfo-6.5.0-1004-laptop 6.5.0-1004.7 in noble arm64 linux-headers-6.5.0-1004-laptop 6.5.0-1004.7 in noble arm64 linux-image-6.5.0-1004-laptop 6.5.0-1004.7 in noble arm64 linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble amd64 linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble arm64 linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble armhf linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble i386 linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble ppc64el linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble riscv64 linux-laptop-headers-6.5.0-1004 6.5.0-1004.7 in noble s390x linux-laptop-tools-6.5.0-1004 6.5.0-1004.7 in noble arm64 linux-laptop-tools-common 6.5.0-1004.7 in noble amd64 linux-laptop-tools-common 6.5.0-1004.7 in noble arm64 linux-laptop-tools-common 6.5.0-1004.7 in noble armhf linux-laptop-tools-common 6.5.0-1004.7 in noble i386 linux-laptop-tools-common 6.5.0-1004.7 in noble ppc64el linux-laptop-tools-common 6.5.0-1004.7 in noble riscv64 linux-laptop-tools-common 6.5.0-1004.7 in noble s390x linux-laptop-tools-host 6.5.0-1004.7 in noble amd64 linux-laptop-tools-host 6.5.0-1004.7 in noble arm64 linux-laptop-tools-host 6.5.0-1004.7 in noble armhf linux-laptop-tools-host 6.5.0-1004.7 in noble i386 linux-laptop-tools-host 6.5.0-1004.7 in noble ppc64el linux-laptop-tools-host 6.5.0-1004.7 in noble riscv64 linux-laptop-tools-host 6.5.0-1004.7 in noble s390x linux-modules-6.5.0-1004-laptop 6.5.0-1004.7 in noble arm64 linux-tools-6.5.0-1004-laptop 6.5.0-1004.7 in noble arm64 Comment: LP: #2060560, obsolete kernel 3 packages successfully removed. ** Changed in: linux-laptop (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta-starfive (Ubuntu) Status: New => Fix Released ** Changed in: linux-starfive (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive in Ubuntu. https://bugs.launchpad.net/bugs/2060560 Title: Remove obsolete kernels from noble Status in linux-laptop package in Ubuntu: Fix Released Status in linux-meta-starfive package in Ubuntu: Fix Released Status in linux-starfive package in Ubuntu: Fix Released Bug description: The starfive and laptop kernels are obsolete, on mantic release version still, and should be removed per discussion with kernel team on Mattermost. $ reverse-depends src:linux-starfive # some reverse-depends bug $ reverse-depends src:linux-laptop No reverse dependencies found $ reverse-depends src:linux-meta-starfive No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2060560/+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
marked old toolchain versions as won't fix ** Changed in: gcc-9 (Ubuntu Noble) Status: Confirmed => Won't Fix ** Changed in: gcc-10 (Ubuntu Noble) Status: Confirmed => Won't Fix ** Changed in: gcc-11 (Ubuntu Noble) Status: Confirmed => Won't Fix ** Changed in: llvm-toolchain-14 (Ubuntu Noble) Status: Confirmed => Won't Fix ** Changed in: llvm-toolchain-15 (Ubuntu Noble) Status: Confirmed => Won't Fix -- 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 Released Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released 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: Won't Fix Status in gcc-11 source package in Noble: Won't Fix Status in gcc-12 source package in Noble: Confirmed Status in gcc-13 source package in Noble: Fix Released Status in gcc-8 source package in Noble: Invalid Status in gcc-9 source package in Noble: Won't Fix Status in linux source package in Noble: Fix Released Status in llvm-toolchain-14 source package in Noble: Won't Fix Status in llvm-toolchain-15 source package in Noble: Won't Fix 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 w
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
** No longer affects: gcc-14 (Ubuntu) ** No longer affects: gcc-14 (Ubuntu Noble) ** Changed in: gcc-8 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-8 package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New 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: New 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: New Status in llvm-toolchain-16 source package in Noble: New 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 : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./tes
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
** Changed in: gcc-13 (Ubuntu Noble) 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/2048768 Title: Autopkgtest failures on amd64 Status in gcc-10 package in Ubuntu: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: Fix Committed Status in gcc-14 package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New Status in gcc-13 source package in Noble: Fix Committed Status in gcc-14 source package in Noble: New Status in gcc-8 source package in Noble: New Status in gcc-9 source package in Noble: New 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: New Status in llvm-toolchain-16 source package in Noble: New 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 : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0"
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
** No longer affects: llvm-toolchain-17 (Ubuntu) ** No longer affects: llvm-toolchain-18 (Ubuntu) ** No longer affects: llvm-toolchain-17 (Ubuntu Noble) ** No longer affects: llvm-toolchain-18 (Ubuntu Noble) -- 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: New Status in gcc-11 package in Ubuntu: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: New Status in gcc-14 package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-9 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in llvm-toolchain-14 package in Ubuntu: Confirmed Status in llvm-toolchain-15 package in Ubuntu: New Status in llvm-toolchain-16 package in Ubuntu: New Status in gcc-10 source package in Noble: New Status in gcc-11 source package in Noble: New Status in gcc-12 source package in Noble: New Status in gcc-13 source package in Noble: New Status in gcc-14 source package in Noble: New Status in gcc-8 source package in Noble: New Status in gcc-9 source package in Noble: New 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: New Status in llvm-toolchain-16 source package in Noble: New 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
[Kernel-packages] [Bug 2011356] Re: network connection is lost every minute on Realtek rtl8152/3 USB Ethernet dongles
** Changed in: linux-hwe-5.19 (Ubuntu) Status: Confirmed => Invalid -- 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/2011356 Title: network connection is lost every minute on Realtek rtl8152/3 USB Ethernet dongles Status in linux-hwe-5.19 package in Ubuntu: Invalid Bug description: tail -F /var/log/kern.log Mar 12 14:26:19 rufy kernel: [ 1581.350668] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:26:28 rufy kernel: [ 1590.148179] r8152 2-3:1.0 enx58ef687e7bb5: carrier on Mar 12 14:26:28 rufy kernel: [ 1590.182915] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:26:32 rufy kernel: [ 1594.084354] r8152 2-3:1.0 enx58ef687e7bb5: carrier on Mar 12 14:34:47 rufy kernel: [ 2089.286793] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:34:56 rufy kernel: [ 2098.020350] r8152 2-3:1.0 enx58ef687e7bb5: carrier on === dmesg 2098.054894] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2101.988225] r8152 2-3:1.0 enx58ef687e7bb5: carrier on [ 2218.278463] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2226.980566] r8152 2-3:1.0 enx58ef687e7bb5: carrier on [ 2227.014909] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2229.508400] r8152 2-3:1.0 enx58ef687e7bb5: carrier on lsusb | grep -i realtek Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter === ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.16 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 14:45:18 2023 InstallationDate: Installed on 2022-12-05 (97 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2023-03-03 11:33:58 Upgrade: tcpdump:amd64 (4.99.1-3build2, 4.99.1-3ubuntu0.1), libqmi-proxy:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), libpango-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libmbim-glib4:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), python3-macaroonbakery:amd64 (1.3.1-2, 1.3.1-2ubuntu0.1), libpangocairo-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libmbim-proxy:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), libpangoft2-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libqmi-glib5:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), gir1.2-pango-1.0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libpangoxft-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1) End-Date: 2023-03-03 11:34:00 mtime.conffile..etc.logrotate.d.apport: 2022-12-19T17:32:59.287674 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2011356/+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 2032247] Re: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed
ok, so the missing rcrt1.o file looks like another issue. we probably should revert to the two-staged builds, if that configuration isn't picked up correctly. -- 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/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12-cross package in Ubuntu: New Status in gcc-13-cross package in Ubuntu: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized implementations. checking for S390 vector support in gcc... no checking for S390 arch13 zarch instruction support... no checking for S390 z10 zarch instruction support as default... no checking for S390 z196 zarch instruction support as default... no checking for S390 z13 zarch instruction support as default... no checking for S390 arch13 zarch instruction support as default... no Those checks were also adjusted in glibc-upstream. Please also pick this commits: commit "S390: Use compile-only instead of also link-tests in configure." (in glibc 2.38) https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8 I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40: binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed] libc6-dev-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed]
[Kernel-packages] [Bug 2011356] Re: network connection is lost every minute on Realtek rtl8152/3 USB Ethernet dongles
The problem is most probably related to the automatic link negotiation procedure, which does not seem to work on r8152/r8153. Please have a look here: https://superuser.com/questions/1272259/debian-stretch-and- realtek-r8152-chipset-carrier-off-on-error. One possibility is to disable it using "ethtool": sudo ethtool -s enx00e04c3617fb autoneg off Still thinking about the proper way to do this each time the USB dongle gets plugged in... ** Summary changed: - network connection is lost every minute + network connection is lost every minute on Realtek rtl8152/3 USB Ethernet dongles -- 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/2011356 Title: network connection is lost every minute on Realtek rtl8152/3 USB Ethernet dongles Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: tail -F /var/log/kern.log Mar 12 14:26:19 rufy kernel: [ 1581.350668] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:26:28 rufy kernel: [ 1590.148179] r8152 2-3:1.0 enx58ef687e7bb5: carrier on Mar 12 14:26:28 rufy kernel: [ 1590.182915] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:26:32 rufy kernel: [ 1594.084354] r8152 2-3:1.0 enx58ef687e7bb5: carrier on Mar 12 14:34:47 rufy kernel: [ 2089.286793] r8152 2-3:1.0 enx58ef687e7bb5: carrier off Mar 12 14:34:56 rufy kernel: [ 2098.020350] r8152 2-3:1.0 enx58ef687e7bb5: carrier on === dmesg 2098.054894] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2101.988225] r8152 2-3:1.0 enx58ef687e7bb5: carrier on [ 2218.278463] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2226.980566] r8152 2-3:1.0 enx58ef687e7bb5: carrier on [ 2227.014909] r8152 2-3:1.0 enx58ef687e7bb5: carrier off [ 2229.508400] r8152 2-3:1.0 enx58ef687e7bb5: carrier on lsusb | grep -i realtek Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter === ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.16 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Mar 12 14:45:18 2023 InstallationDate: Installed on 2022-12-05 (97 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2023-03-03 11:33:58 Upgrade: tcpdump:amd64 (4.99.1-3build2, 4.99.1-3ubuntu0.1), libqmi-proxy:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), libpango-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libmbim-glib4:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), python3-macaroonbakery:amd64 (1.3.1-2, 1.3.1-2ubuntu0.1), libpangocairo-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libmbim-proxy:amd64 (1.26.2-1build1, 1.28.0-1~ubuntu20.04.1), libpangoft2-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libqmi-glib5:amd64 (1.30.4-1, 1.32.0-1ubuntu0.22.04.1), gir1.2-pango-1.0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1), libpangoxft-1.0-0:amd64 (1.50.6+ds-2, 1.50.6+ds-2ubuntu1) End-Date: 2023-03-03 11:34:00 mtime.conffile..etc.logrotate.d.apport: 2022-12-19T17:32:59.287674 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2011356/+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 1848831]
I also have AX200 card with errors as mentioned above, and no wifi interface at startup. I tried solution from @invalidhandle and it worked: I left alone iwlwifi-cc-a0-50.ucode.zst (I don't have version 48) in /lib/firmware and rebooted. Then wifi was ok and I could connect to internet. I tried also with iwlwifi-cc-a0-77.ucode.zst without success (no interface showing up). I'm using kernel 6.6.2-arch1-1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC uname -a Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10. Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner $ ls /lib/firmware/iwlwifi-cc-* /lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel. $ rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no ~$ dmesg | grep iwl [ 12.312443] iwlwifi :01:00.0: enabling device ( -> 0002) [ 12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM [ 12.321102] iwlwifi :01:00.0: Found debug configuration: 0 [ 12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired. [ 13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414910] iwlwifi :01:00.0: Status: 0x, count: 6 [ 13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0 [ 13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0 [ 13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2 [ 13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1 [ 13.414917] iwlwifi :01:00.0: 0x1000 | data2 [ 13.414917] iwlwifi :01:00.0: 0xF000 | data3 [ 13.414918] iwlwifi :01:00.0: 0x | beacon time [ 13.414919] iwlwifi :01:00.0: 0x795F | tsf low [ 13.414919] iwlwifi :01:00.0: 0x | tsf hi [ 13.414920] iwlwifi :01:00.0: 0x | time gp1 [ 13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2 [ 13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major [ 13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor [ 13.414923] iwlwifi :01:00.0: 0x0340 | hw version [ 13.414924] iwlwifi :01:00.0: 0x18C89000 | board version [ 13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd [ 13.414925] iwlwifi :01:00.0: 0x0002 | isr0 [ 13.414926] iwlwifi :01:00.0: 0x | isr1 [ 13.414926] iwlwifi :01:00.0: 0x08F2 | isr2 [ 13.414927] iwlwifi :01:00.0: 0x00CC | isr3 [ 13.414928] iwlwifi :01:00.0: 0x | isr4 [ 13.414928] iwlwifi :01:00.0: 0x | last cmd Id [ 13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event [ 13.414930] iwlwifi :01:00.0: 0x | l2p_control [ 13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration [ 13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match [ 13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel [ 13.414933] iwlwifi :01:00.0: 0x | timestamp [ 13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler [ 13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414975] iwlwif
[Kernel-packages] [Bug 2032247] Re: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed
that should be fixed in mantic (23.10). -- 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/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12-cross package in Ubuntu: New Status in gcc-13-cross package in Ubuntu: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized implementations. checking for S390 vector support in gcc... no checking for S390 arch13 zarch instruction support... no checking for S390 z10 zarch instruction support as default... no checking for S390 z196 zarch instruction support as default... no checking for S390 z13 zarch instruction support as default... no checking for S390 arch13 zarch instruction support as default... no Those checks were also adjusted in glibc-upstream. Please also pick this commits: commit "S390: Use compile-only instead of also link-tests in configure." (in glibc 2.38) https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8 I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40: binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed] libc6-dev-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed] libc6-dev/lunar,now 2.37-0ubuntu2 s390x [installed] libc6-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed
[Kernel-packages] [Bug 2032247] Re: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Package changed: gcc-13 (Ubuntu) => gcc-13-cross (Ubuntu) ** Package changed: gcc-12 (Ubuntu) => gcc-12-cross (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/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12-cross package in Ubuntu: New Status in gcc-13-cross package in Ubuntu: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized implementations. checking for S390 vector support in gcc... no checking for S390 arch13 zarch instruction support... no checking for S390 z10 zarch instruction support as default... no checking for S390 z196 zarch instruction support as default... no checking for S390 z13 zarch instruction support as default... no checking for S390 arch13 zarch instruction support as default... no Those checks were also adjusted in glibc-upstream. Please also pick this commits: commit "S390: Use compile-only instead of also link-tests in configure." (in glibc 2.38) https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8 I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40: binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed] libc6-dev-s390x-cross/luna
[Kernel-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Happened to me also. Saw the attached error in dmesg.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038998/+attachment/5717812/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
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: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
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-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
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
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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/gnome-shell/+bug/2038998/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hello Andreas, I saw the same error on a 13th Gen Intel(R) Core(TM) i7-1370PE using the IOT release of jammy desktop. I can confirm that installing mutter from jammy-proposed fixed the issue on my system. $ uname -a Linux amr-rplp-01 5.15.0-1034-intel-iotg #39-Ubuntu SMP Thu Jun 22 20:56:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy Now I have this mutter release: $ apt list -a mutter Listing... Done mutter/jammy-proposed,now 42.9-0ubuntu3 amd64 [installed] mutter/jammy-updates 42.9-0ubuntu1 amd64 mutter/jammy 42.0-3ubuntu2 amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries
Debian has a kernel, where this can be enabled with a boot parameter (syscall.x32=y) -- 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/1994516 Title: Kernels after 5.16 cannot execute x32-ABI binaries Status in linux package in Ubuntu: Confirmed Bug description: The kernel configuration option CONFIG_X86_X32_ABI is outcommented for kernel 5.17 and higher (amd64). x32 binaries are now reporting: cannot execute binary file: Exec format error The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC intensive tasks) because it saves CPU time and critical resources like energy. So, the following approach (e.g. Debian) looks more appropriate: 1. Include the x32-relevant code, but disable its use on standard boots: CONFIG_X86_X32=y CONFIG_X86_X32_DISABLED=y 2. Users that must run x32 binaries can easily add the GRUB cmdline option syscall.x32=y to enable x32 binaries. This could be a good compromise between kernel complexity and resource efficiency. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (1 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: False dmi.bios.date: 10/13/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994516/+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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Hello. Same here, with a readeon HD7700 and Ubuntu 22.04.2 With kernel -35 there is no hdmi audio output, but after -32 restore everything is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+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 2008715] [NEW] Computer does not awake after sleep mode.
Public bug reported: I use the Desktopfeature "poweroff/logoff -> Bereitschaft" (i guess it is called sleep in english) After setting the laptop in sleep mode, it does not awake. Running linux 5.15.0-60 does not have this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 17:08:21 2023 InstallationDate: Installed on 2022-07-11 (231 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (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-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008715 Title: Computer does not awake after sleep mode. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I use the Desktopfeature "poweroff/logoff -> Bereitschaft" (i guess it is called sleep in english) After setting the laptop in sleep mode, it does not awake. Running linux 5.15.0-60 does not have this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 27 17:08:21 2023 InstallationDate: Installed on 2022-07-11 (231 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008715/+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 1742922] Re: no connection anymore with r8152 on 4.13.0-26
Also I can confirm the bug on Ubuntu 18.04.6 LTS and Kernel 5.4.0-135-generic x86_64. In my experience I have seen it mostly happening on standby/hibernation resume. Also powering off and switching on the laptop again does not always help, better is it to disconnect the plug. This post was very helpful: https://askubuntu.com/questions/1081128/usb-3-0-ethernet-adapter-not- working-ubuntu-18-04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1742922 Title: no connection anymore with r8152 on 4.13.0-26 Status in linux-hwe package in Ubuntu: Expired Bug description: Since yesterdays upgrade to linux-image-4.13.0-26-generic:amd64 my wired network is not working anymore. In the system log files I see hundrets of messages like this: kernel: r8152 2-2.2:1.0 enx949aa925a648: Tx status -71 The network card is detected, but it's not working properly. It still works with Kernel 4.10. lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 apt policy linux-signed-image-generic-hwe-16.04 linux-signed-image-generic-hwe-16.04: Installiert: 4.13.0.26.46 Installationskandidat: 4.13.0.26.46 Versionstabelle: *** 4.13.0.26.46 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 12 12:39:32 2018 InstallationDate: Installed on 2015-11-12 (792 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2016-07-29 (531 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1742922/+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 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries
** Tags added: regression-release rls-ll-incoming ** Tags added: rls-kk-incoming ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1994516 Title: Kernels after 5.16 cannot execute x32-ABI binaries Status in linux package in Ubuntu: Confirmed Bug description: The kernel configuration option CONFIG_X86_X32_ABI is outcommented for kernel 5.17 and higher (amd64). x32 binaries are now reporting: cannot execute binary file: Exec format error The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC intensive tasks) because it saves CPU time and critical resources like energy. So, the following approach (e.g. Debian) looks more appropriate: 1. Include the x32-relevant code, but disable its use on standard boots: CONFIG_X86_X32=y CONFIG_X86_X32_DISABLED=y 2. Users that must run x32 binaries can easily add the GRUB cmdline option syscall.x32=y to enable x32 binaries. This could be a good compromise between kernel complexity and resource efficiency. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (1 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: False dmi.bios.date: 10/13/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994516/+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 1982833] Re: Bump (kernel) '-mtune' to z16 / arch14 with 23.04
fixed in lunar for gcc-11 and gcc-12 ** Also affects: gcc-11 (Ubuntu) Importance: Undecided Status: New ** Changed in: gcc-11 (Ubuntu) Status: New => Fix Released ** Changed in: gcc-12 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982833 Title: Bump (kernel) '-mtune' to z16 / arch14 with 23.04 Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in gcc-12 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: Consider to bump the kernel '-mtune' to z16 (equals arch14), starting with 23.04. Discuss with IBM Z team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+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 1987870] Re: Demote to proposed LRM portions of intel-iotg
Demoting packages to kinetic-proposed: linux-restricted-modules-oem-5.17 5.17.0-1003.3+1 in kinetic linux-restricted-signatures-oem-5.17 5.17.0-1003.3+1 in kinetic linux-restricted-modules-intel-iotg 5.15.0-1004.6 in kinetic linux-restricted-signatures-intel-iotg 5.15.0-1004.6 in kinetic Comment: v5.19 kernel migration LP:#1987870 and LP:#1987869 Demote [y|N]? y Remove linux-restricted-modules-oem-5.17 from release [y|N]? y Remove linux-restricted-signatures-oem-5.17 from release [y|N]? y Remove linux-restricted-modules-intel-iotg from release [y|N]? y Remove linux-restricted-signatures-intel-iotg from release [y|N]? y 4 packages successfully demoted. ** Changed in: linux-restricted-modules-intel-iotg (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Fix Released Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Fix Released Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+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 1987158] Re: touchpad does not work after distupgrade to 22.04
please fix this, I like my linux on the xps but without touchpad it is almost useless. I can use the touchscreen, but it is not the same. -- 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/1987158 Title: touchpad does not work after distupgrade to 22.04 Status in linux package in Ubuntu: New Bug description: I upgraded my dual boot XPS 9870 to Ubuntu 22.04 and after a day or so the toucpad is not recognized. I looked up the dmesg errors online, it seems a common problem that Ubuntu had regularly over past years that a touchpad is recognized as generic mouse and cannot be activiated. interestingly it works in the login screen, but when the GUI starts, the touchpad cannot be actiavted again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 2327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Aug 20 07:30:52 2022 InstallationDate: Installed on 2019-04-04 (1233 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9b991c55-5313-4aa3-97a2-032ff0701df3 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-13 (6 days ago) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd12/09/2021:br1.18:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987158/+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 1987158] [NEW] touchpad does not work after distupgrade to 22.04
Public bug reported: I upgraded my dual boot XPS 9870 to Ubuntu 22.04 and after a day or so the toucpad is not recognized. I looked up the dmesg errors online, it seems a common problem that Ubuntu had regularly over past years that a touchpad is recognized as generic mouse and cannot be activiated. interestingly it works in the login screen, but when the GUI starts, the touchpad cannot be actiavted again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 2327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Aug 20 07:30:52 2022 InstallationDate: Installed on 2019-04-04 (1233 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9b991c55-5313-4aa3-97a2-032ff0701df3 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-13 (6 days ago) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd12/09/2021:br1.18:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/1987158 Title: touchpad does not work after distupgrade to 22.04 Status in linux package in Ubuntu: New Bug description: I upgraded my dual boot XPS 9870 to Ubuntu 22.04 and after a day or so the toucpad is not recognized. I looked up the dmesg errors online, it seems a common problem that Ubuntu had regularly over past years that a touchpad is recognized as generic mouse and cannot be activiated. interestingly it works in the login screen, but when the GUI starts, the touchpad cannot be actiavted again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 2327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Aug 20 07:30:52 2022 InstallationDate: Installed on 2019-04-04 (1233 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9b991c55-5313-4aa3-97a2-032ff0701df3 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-13 (6 days ago) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1933771] Re: Bluetooth headset random disconnects AX200
I still experience this issue with Jammy 22.04, with the 20220329.git681281e4-0ubuntu1 version of linux-firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933771 Title: Bluetooth headset random disconnects AX200 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Won't Fix Status in linux-firmware source package in Impish: Confirmed Bug description: [Impact] Using several different bluetooth headsets I find that the Bluetooth functionality of the built-in AX200 module of my motherboard keeps randomly disconnecting. I found that this has been fixed in recent Linux firmware updates, but I am not sure that fix has landed yet in Ubuntu Hirsute. Herewith I am posting the link to exactly the issue I am having: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1155 And the Linux Firmware commit that resolves this: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=73144e02dcff54529ab42d951de682740d204180 A related Fedora bug: https://bodhi.fedoraproject.org/updates/FEDORA-2021-93247f3274 It's difficult to relate the upstream kernel version firmware version in which this was fixed (linux-firmware-20210511) to the version of the linux-firmware Ubuntu package (for me). Perhaps someone can comment on whether this has been merged in. I am still experiencing disconnects with 1.197.1 at least. -- Description: Ubuntu 21.04 Release: 21.04 linux-firmware: Installed: 1.197.1 Candidate: 1.197.1 I expected: Bluetooth headset to remain connected What happened: Bluetooth headset connects, then randomly disconnects and reconnects while playing media [Test Case] See above. [Fix] Update AX20x firmware blobs. [Where Problems Could Occur] New firmware blobs so previously working adapter might now fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933771/+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 1960500] Re: [MIR] libxcvt
Override component to main libxcvt 0.1.1-3 in jammy: universe/misc -> main libxcvt-dev 0.1.1-3 in jammy amd64: universe/libdevel/optional/100% -> main libxcvt-dev 0.1.1-3 in jammy arm64: universe/libdevel/optional/100% -> main libxcvt-dev 0.1.1-3 in jammy armhf: universe/libdevel/optional/100% -> main libxcvt-dev 0.1.1-3 in jammy ppc64el: universe/libdevel/optional/100% -> main libxcvt-dev 0.1.1-3 in jammy riscv64: universe/libdevel/optional/100% -> main libxcvt-dev 0.1.1-3 in jammy s390x: universe/libdevel/optional/100% -> main libxcvt0 0.1.1-3 in jammy amd64: universe/libs/optional/100% -> main libxcvt0 0.1.1-3 in jammy arm64: universe/libs/optional/100% -> main libxcvt0 0.1.1-3 in jammy armhf: universe/libs/optional/100% -> main libxcvt0 0.1.1-3 in jammy ppc64el: universe/libs/optional/100% -> main libxcvt0 0.1.1-3 in jammy riscv64: universe/libs/optional/100% -> main libxcvt0 0.1.1-3 in jammy s390x: universe/libs/optional/100% -> main xcvt 0.1.1-3 in jammy amd64: universe/x11/optional/100% -> main xcvt 0.1.1-3 in jammy arm64: universe/x11/optional/100% -> main xcvt 0.1.1-3 in jammy armhf: universe/x11/optional/100% -> main xcvt 0.1.1-3 in jammy ppc64el: universe/x11/optional/100% -> main xcvt 0.1.1-3 in jammy riscv64: universe/x11/optional/100% -> main xcvt 0.1.1-3 in jammy s390x: universe/x11/optional/100% -> main 19 publications overridden. ** Changed in: libxcvt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libxcvt in Ubuntu. https://bugs.launchpad.net/bugs/1960500 Title: [MIR] libxcvt Status in libxcvt package in Ubuntu: Fix Released Bug description: [Availability] The package libxcvt is already in Ubuntu universe. The package libxcvt build for the architectures it is designed to work on. It currently builds and works for architetcures: amdg64 Link to package [[https://launchpad.net/ubuntu/+source/libxcvt|libxcvt]] [Rationale] - The package libxcvt is required in Ubuntu main for xorg-server, xwayland - The package libxcvt is required in Ubuntu main no later than jammy FFE due to landing new versions of xorg-server, xwayland [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...) [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu and has no bugs open - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libxcvt/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libxcvt [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't provide any - The package does not run an autopkgtest [Quality assurance - packaging] - debian/watch is present and works - This package does not yield massive lintian Warnings, Errors - Link to recent build log including a lintian run: https://launchpadlibrarian.net/567908139/buildlog_ubuntu-jammy-amd64.libxcvt_0.1.1-1_BUILDING.txt.gz - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions higher than medium - Packaging and build is easy, link to d/rules: https://salsa.debian.org/xorg-team/lib/libxcvt/-/blob/debian-unstable/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be kernel-packages - Team is already subscribed to the package - This does not use static builds - This does not use vendored code [Background information] The Package description explains the package well libxcvt0 is split from xorg-server so that xwayland can also use it. 'xcvt' is not needed in main. The library is tiny, has had in total of 21 commits over the years in xorg-server git tree before the split. Keep this in mind before requiring automated tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcvt/+bug/1960500/+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 1930086] Re: [22.04 FEAT] gcc tunings for power9
now built in jammy-proposed ** Changed in: llvm-toolchain-13 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: Fix Committed Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+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 1930086] Re: [22.04 FEAT] gcc tunings for power9
** Package changed: gcc-defaults (Ubuntu) => gcc-11 (Ubuntu) ** Also affects: llvm-toolchain-13 (Ubuntu) Importance: Undecided Status: New ** Changed in: llvm-toolchain-13 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930086 Title: [22.04 FEAT] gcc tunings for power9 Status in The Ubuntu-power-systems project: In Progress Status in gcc-11 package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-13 package in Ubuntu: In Progress Bug description: This is an Ubuntu-power-systems 22.04 LTS feature bug to track changing the gcc configure options from --with-cpu=power8 to --with- cpu=power9. Prerequisites for this bug include power9 builder hardware in Canonical datacenter. I'm still learning my way around Debian/Ubuntu source so go easy on me if this isn't the correct branch: https://salsa.debian.org/toolchain- team/gcc/-/blob/gcc-10-debian/debian/rules2#L394 But we'll want to add some logic around line 394 to add --with- cpu=power9 for 22.04 and possibly --with-tune=? but I'll reverse mirror this bug and verify with our IBM Power toolchain architect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1930086/+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 1936237] Re: use the upstream version for the kernel packaging
no logs missing ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1936237 Title: use the upstream version for the kernel packaging Status in linux package in Ubuntu: New Bug description: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind of information are you intending to consume it as a human, or scripted yes, or have a different binary version for every binary package built human i almost want to put a versioned provides on it then if something ever did care it could actually do something about it and what would be the package that you provide? linux-libc-dev-mainline (= foo) perhaps apw: TBH I wonder whether the "avoid new orig files" is still the right tradeoff. The size of a linux orig tarball looks rather less significant now than it did when we started this practice cjwatson, we would provide a new .orig for every single SRU cycle in the normal run of things, for every single kernel. so 180M for each of 82 kernels. which by my calculation is 14TB every 3 weeks? Hm yeah, I suppose ... I always forget what an absurdly enormous number of kernels you have or are you able to collesce the orig by contents? as there is more like only 4 for every cycle. No Well maybe if they're actually bitwise-identical they are bitwise identicle i assume you _arn't_ currently sharing the bits, but you might be able to? I think we are actually But I'll check after this meeting ack and thanks apw: Oh right, yeah, they get temporarily added as duplicates and then librarian-gc deduplicates them so the space usage wouldn't be an issue in the end? So it'd still be a TB a month or so, which isn't entirely insignificant Maybe better not change it until the librarian is on PS5 and we get a feel for what space usage looks like there Actually no, neither apw nor I can multiply apparently 180M * 82 is 14G not 14T ;p That makes rather more sense, I was wondering how you'd manage to generate like a sixth of the librarian's total storage size in three weeks So <1G extra per three weeks is noise and will not really be noticed from our point of view. I can't speak to whatever extra rebase work it might require of course. And of course it would presumably require some tooling changes. I do think it would be ultimately the right thing to do though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936237/+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 1939308] Re: armhf build failure
please provide verbose build logs, showing all arguments passed to the compiler. -- 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/1939308 Title: armhf build failure Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: Building an armhf kernel with gcc 11 fails like this: DTC arch/arm/boot/dts/rk3066a-bqcurie2.dtb AS [M] arch/arm/crypto/nh-neon-core.o CC arch/arm/mach-imx/mach-imx6sx.o DTC arch/arm/boot/dts/rk3066a-marsboard.dtb CC arch/arm/kernel/hw_breakpoint.o DTC arch/arm/boot/dts/rk3066a-mk808.dtb CC arch/arm/mach-imx/mach-imx6ul.o DTC arch/arm/boot/dts/rk3066a-rayeager.dtb CC [M] arch/arm/crypto/nhpoly1305-neon-glue.o CC arch/arm/kernel/pj4-cp0.o AS [M] arch/arm/crypto/curve25519-core.o CC arch/arm/mach-imx/mach-imx7d.o DTC arch/arm/boot/dts/rk3188-bqedison2qc.dtb AS arch/arm/kernel/iwmmxt.o CC arch/arm/mach-imx/mach-imx7ulp.o DTC arch/arm/boot/dts/rk3188-px3-evb.dtb CC arch/arm/kernel/perf_regs.o /tmp/ccV0AdoQ.s: Assembler messages: /tmp/ccV0AdoQ.s:95: Error: selected processor does not support `isb ' in ARM mode /tmp/ccV0AdoQ.s:103: Error: selected processor does not support `isb ' in ARM mode CC [M] arch/arm/crypto/curve25519-glue.o /tmp/ccV0AdoQ.s:178: Error: selected processor does not support `isb ' in ARM mode CC arch/arm/mach-imx/pm-imx7ulp.o DTC arch/arm/boot/dts/rk3188-radxarock.dtb AS arch/arm/mach-imx/suspend-imx6.o make[4]: *** [/tmp/kernel-juergh-254d24c-kP9S/build/scripts/Makefile.build:281: arch/arm/common/krait-l2-accessors.o] Error 1 make[4]: *** Waiting for unfinished jobs AS [M] arch/arm/crypto/aes-ce-core.o DTC arch/arm/boot/dts/rk3066a-bqcurie2.dtb AS [M] arch/arm/crypto/nh-neon-core.o CC arch/arm/mach-imx/mach-imx6sx.o DTC arch/arm/boot/dts/rk3066a-marsboard.dtb CC arch/arm/kernel/hw_breakpoint.o DTC arch/arm/boot/dts/rk3066a-mk808.dtb CC arch/arm/mach-imx/mach-imx6ul.o DTC arch/arm/boot/dts/rk3066a-rayeager.dtb CC [M] arch/arm/crypto/nhpoly1305-neon-glue.o CC arch/arm/kernel/pj4-cp0.o AS [M] arch/arm/crypto/curve25519-core.o CC arch/arm/mach-imx/mach-imx7d.o DTC arch/arm/boot/dts/rk3188-bqedison2qc.dtb AS arch/arm/kernel/iwmmxt.o CC arch/arm/mach-imx/mach-imx7ulp.o DTC arch/arm/boot/dts/rk3188-px3-evb.dtb CC arch/arm/kernel/perf_regs.o /tmp/ccV0AdoQ.s: Assembler messages: /tmp/ccV0AdoQ.s:95: Error: selected processor does not support `isb ' in ARM mode /tmp/ccV0AdoQ.s:103: Error: selected processor does not support `isb ' in ARM mode CC [M] arch/arm/crypto/curve25519-glue.o /tmp/ccV0AdoQ.s:178: Error: selected processor does not support `isb ' in ARM mode CC arch/arm/mach-imx/pm-imx7ulp.o DTC arch/arm/boot/dts/rk3188-radxarock.dtb AS arch/arm/mach-imx/suspend-imx6.o make[4]: *** [/tmp/kernel-juergh-254d24c-kP9S/build/scripts/Makefile.build:281: arch/arm/common/krait-l2-accessors.o] Error 1 make[4]: *** Waiting for unfinished jobs AS [M] arch/arm/crypto/aes-ce-core.o CC arch/arm/mach-omap2/id.o CC arch/arm/kernel/perf_callchain.o DTC arch/arm/boot/dts/rk3228-evb.dtb AS arch/arm/mach-imx/resume-imx6.o CC arch/arm/mach-qcom/platsmp.o CC arch/arm/mach-omap2/id.o CC arch/arm/kernel/perf_callchain.o DTC arch/arm/boot/dts/rk3228-evb.dtb AS arch/arm/mach-imx/resume-imx6.o CC arch/arm/mach-qcom/platsmp.o To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939308/+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 1936237] [NEW] use the upstream version for the kernel packaging
Public bug reported: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind of information are you intending to consume it as a human, or scripted yes, or have a different binary version for every binary package built human i almost want to put a versioned provides on it then if something ever did care it could actually do something about it and what would be the package that you provide? linux-libc-dev-mainline (= foo) perhaps apw: TBH I wonder whether the "avoid new orig files" is still the right tradeoff. The size of a linux orig tarball looks rather less significant now than it did when we started this practice cjwatson, we would provide a new .orig for every single SRU cycle in the normal run of things, for every single kernel. so 180M for each of 82 kernels. which by my calculation is 14TB every 3 weeks? Hm yeah, I suppose ... I always forget what an absurdly enormous number of kernels you have or are you able to collesce the orig by contents? as there is more like only 4 for every cycle. No Well maybe if they're actually bitwise-identical they are bitwise identicle i assume you _arn't_ currently sharing the bits, but you might be able to? I think we are actually But I'll check after this meeting ack and thanks apw: Oh right, yeah, they get temporarily added as duplicates and then librarian-gc deduplicates them so the space usage wouldn't be an issue in the end? So it'd still be a TB a month or so, which isn't entirely insignificant Maybe better not change it until the librarian is on PS5 and we get a feel for what space usage looks like there Actually no, neither apw nor I can multiply apparently 180M * 82 is 14G not 14T ;p That makes rather more sense, I was wondering how you'd manage to generate like a sixth of the librarian's total storage size in three weeks So <1G extra per three weeks is noise and will not really be noticed from our point of view. I can't speak to whatever extra rebase work it might require of course. And of course it would presumably require some tooling changes. I do think it would be ultimately the right thing to do though. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ii-incoming ** Tags added: rls-ii-incoming -- 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/1936237 Title: use the upstream version for the kernel packaging Status in linux package in Ubuntu: New Bug description: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind
[Kernel-packages] [Bug 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
I did an upgrade from kernel 5.4.0-74-generic to 5.4.0-77-generic and the problem disappeared. $ stty -F /dev/ttyACM0 speed 57600 baud; line = 0; eof = ^A; min = 1; time = 0; -brkint -icrnl -imaxbel -opost -onlcr -icanon -echo -echoe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931684/+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 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
excerpt from /var/log/apt/history.log: Update from 73 to 74: Commandline: aptdaemon role='role-commit-packages' sender=':1.165' Install: linux-image-5.4.0-74-generic:amd64 (5.4.0-74.83, automatic),... Update firmware/microcode: Commandline: aptdaemon role='role-commit-packages' sender=':1.173' Upgrade: intel-microcode:amd64 (3.20210216.0ubuntu0.20.04.1, 3.20210608.0ubuntu0.20.04.1), linux-firmware:amd64 (1.187.12, 1.187.14) ** Also affects: intel-microcode (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in intel-microcode package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931684/+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 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
Im using Ubuntu 20.04 LTS and have the same problem. I got the problem after upgrading from Kernel 5.4.0-73-generic to 5.4.0-74-generic. As I got in addition a firmware/microcode update it may be possible that the error is adjacent to that update too. If I boot to kernel 5.4.0-73-generic I have access to the serial line (e.g. /dev/ttyACM3). -- 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/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931684/+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 1912371] Re: [MIR] flashrom + libftdi
yes, disabling lto explicitly for the build seems reasonable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libftdi in Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi Status in flashrom package in Ubuntu: New Status in libftdi package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+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 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: rls-ff-incoming -- 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/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! Status in corosync package in Ubuntu: New Status in libaio package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in ocfs2-tools package in Ubuntu: New Bug description: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.934468] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.935659] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.938141] R13: 926a49917800
[Kernel-packages] [Bug 1912371] Re: [MIR] flashrom + libftdi
** Changed in: libftdi (Ubuntu) Assignee: Matthieu Clemenceau (mclemenceau) => Ubuntu Security Team (ubuntu-security) ** Changed in: libftdi (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libftdi in Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi Status in flashrom package in Ubuntu: New Status in libftdi package in Ubuntu: New Bug description: [Summary] Further review will be needed. The Package does not have a test suite that runs as autopkgtest. [Availability] Currently in universe. [Duplication] There is no other package in main providing the same functionality. [Rationale] fwupd depends on libflashrom1 for its flashrom plugin, something that's required to update Coreboot firmware. [Security] No CVE's, but due to the nature of the package security should review. [Quality Assurance] Package builds and runs easily [Dependencies] N/A [Standards Compliance] Complies with FHS, though the organization of files in the source package could be organized better. [Common blockers] flashrom does NOT have a test suite that runs at build time. flashrom does NOT have a test suite that runs as autopkgtest. [Maintenance] Actively maintained - https://github.com/flashrom/flashrom Packaging - https://salsa.debian.org/myczko-guest/flashrom.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+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 1499006] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [gcc: internal compiler error: Bus error (program cc1)]
closing, old issue and not enough information. please provide the preprocessed source and the command line options used if you want to reopen the issue. ** Changed in: gcc-defaults (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1499006 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build [gcc: internal compiler error: Bus error (program cc1)] Status in bcmwl package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Bug description: Wireless internet stopped working after update ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.13.0-51-generic Date: Wed Sep 23 20:09:41 2015 InstallationDate: Installed on 2014-10-31 (327 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1499006/+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 1663841] Re: toggling CAPS LOCK off freezes computer
according to the referenced issue in the red hat tracker, this is a kernel bug. ** Package changed: gcc-defaults (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1663841 Title: toggling CAPS LOCK off freezes computer Status in linux package in Ubuntu: New Bug description: From https://www.reddit.com/r/razer/comments/5orvy5/late_2016_rbs_qhd_linux_damage_report/ I'm having an issue on a Kaby Lake based device, where toggling CAPS LOCK on works, but toggling it off crashes the machine. The screen becomes glitched looking, and sometimes static plays over the speakers. Changing Desktop Environments and Window Managers does not change this. Dropping to a terminal via ctrl+alt+F1 seems to be unaffected. I thought this was an issue with X11 as per this (https://wiki.ubuntu.com/X/Troubleshooting/Freeze), but if I ssh into the machine, it becomes unresponsive after the crash. Ask Ubuntu thread: http://askubuntu.com/q/873626/644072 nick@nick-Blade-Stealth:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.10.0-rc7+ root=UUID=dc12ad20-3a6a-436d-96b1-cad68ca1bcef ro drm.debug=0xe plymouth:debug i915.enable_rc6=0 button.lid_init_state=open nick@nick-Blade-Stealth:~$ cat /proc/version Linux version 4.10.0-rc7+ (nick@nick-Blade-Stealth) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #1 SMP PREEMPT Sat Feb 11 00:21:50 PST 2017 nick@nick-Blade-Stealth:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1663841/+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 1795215] Re: package cpp 4:7.3.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installed cpp package post-installation script gab den Fehler-Ausgangsstatus 2 zurück
Entpacken von python-apport (2.20.9-0ubuntu7.4) über (2.20.9-0ubuntu7.3) ... cpp (4:7.3.0-3ubuntu2.1) wird eingerichtet ... update-alternatives: Fehler: »/usr/lib/nvidia-settings-319/ld.so.conf« kann nicht mit stat abgefragt werden: Zu viele Ebenen aus symbolischen Links dpkg: Fehler beim Bearbeiten des Paketes cpp (--configure): Unterprozess installed cpp package post-installation script gab den Fehler-Ausgangsstatus 2 zurück ** Package changed: gcc-defaults (Ubuntu) => nvidia-common (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-common in Ubuntu. https://bugs.launchpad.net/bugs/1795215 Title: package cpp 4:7.3.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installed cpp package post-installation script gab den Fehler- Ausgangsstatus 2 zurück Status in nvidia-common package in Ubuntu: New Bug description: crash appeared after an additional monitor was started. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cpp 4:7.3.0-3ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Sep 29 15:50:12 2018 ErrorMessage: Unterprozess installed cpp package post-installation script gab den Fehler-Ausgangsstatus 2 zurück InstallationDate: Installed on 2013-08-30 (1856 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: gcc-defaults Title: package cpp 4:7.3.0-3ubuntu2.1 failed to install/upgrade: Unterprozess installed cpp package post-installation script gab den Fehler-Ausgangsstatus 2 zurück UpgradeStatus: Upgraded to bionic on 2018-09-19 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1795215/+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 1608753] Re: Cannot build nvidia driver via dkms because compiler doesn't match kernel
this is not a compiler issue. Apparently you have to build the modules and the kernel with the same version of the compiler, which is now 5.4.x. We usually don't update the dependencies packages, the symlinks stay the same. ** Changed in: gcc-defaults (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1608753 Title: Cannot build nvidia driver via dkms because compiler doesn't match kernel Status in One Hundred Papercuts: Triaged Status in dkms package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Bug description: The kernel installed with 16.04 was built with gcc 5.3.1, but the default compiler installed is 5.4.0 - as such, DKMS refuses to build the nvidia video card driver due to the mismatch. Either build the kernel with the shipping compiler or ship the compiler that was used to build the kernel. cat /proc/version Linux version 4.4.0-34-lowlatency (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP PREEMPT Wed Jul 27 19:23:26 UTC 2016 gcc --version gcc (Ubuntu 5.4.0-6ubuntu1~16.04.1) 5.4.0 20160609 lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dkms 2.2.0.3-2ubuntu11.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-lowlatency 4.4.15 Uname: Linux 4.4.0-34-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 1 21:26:15 2016 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dkms UpgradeStatus: Upgraded to xenial on 2016-07-23 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1608753/+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 1910576] [NEW] [MIR] libbpf (dependency of iproute2)
Public bug reported: [MIR] libbpf (dependency of iproute2) ** Affects: iproute2 (Ubuntu) Importance: High Assignee: Kernel Packages (kernel-packages) Status: New ** Affects: libbpf (Ubuntu) Importance: High Assignee: Kernel Packages (kernel-packages) Status: Incomplete ** Tags: hirsute rls-hh-incoming ** Also affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu) Importance: Undecided => High ** Changed in: libbpf (Ubuntu) Importance: Undecided => High ** Tags added: rls-hh-incoming ** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) ** Changed in: libbpf (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: New Status in libbpf package in Ubuntu: Incomplete Bug description: [MIR] libbpf (dependency of iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Status in wpasupplicant package in Ubuntu: Confirmed Bug description: There are reproduce-able WiFi aborts with 20.04.1 LTS since update to kernel 5.4.0-56. Behaviour: nm-applet shows a window to enter the WLAN key that is pre- filled. Hitting the "Connect" button reconnects the WiFi network for a small period. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). You can see it in /var/log/syslog at the entry >>> wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available As a result 4-Way-Handshake fails and after disconnection the new (old) key is requested. >>> wpa_supplicant[xxx]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect >>> NetworkManager[xxx]: [xxx] device (wlp3s0): Activation: (wifi) disconnected during association, asking for new key There are a lot of people having this problem (see discussion in german moderated forum: >>> https://forum.ubuntuusers.de/topic/funknetz-schluessel-werden-staendig-abgefragt See also BUG #1908823 and question #694566 >>> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823 >>> https://answers.launchpad.net/ubuntu/+question/694566 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1909494/+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 1904757] Re: No sound after upgrade to linux-image-5.4.0-54-generic
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1904757 Title: No sound after upgrade to linux-image-5.4.0-54-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi Everyone, Just a heads up here... I'm working on Zorin OS 15.3, which is based on Ubuntu Bionic. I upgrade from the linux-image-5.4.0-53-generic kernel to the linux- image-5.4.0-54-generic kernel. After the upgrade to the 5.4.0-54 kernel sound stopped working. Settings showed a "Dummy Output" device and no others. A quick lsmod for snd_hda_intel showed the driver was not loaded. I was not able to load the Intel driver manually. I think there may be some sound driver problems with linux- image-5.4.0-54-generic. The user wanted her sound so I had to remove the 5.4.0-54 kernel. I won't be able to help troubleshoot it. If someone could make a quick pass on the module build results to ensure the drivers are being built for 5.4.0-54, it would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904757/+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 1904757] Re: No sound after upgrade to linux-image-5.4.0-54-generic
I have the same issue with sound via HDMI since kernel 5.4.0-54-generic (I'm using NVIDIA GP107GL High Definition Audio, see system settings below). The issue exists also with kernel 5.4.0-56-generic. As Youssef mentioned, the audio device is not shown, but a "Dummy Output". In contrast to Youssef, my headphones are working, when connected, but I suppose, they are working due to my separate intel audio control (see system settings below). Here are my current system settings: System:Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal Machine: Type: Desktop Mobo: MEDION model: H110H4-EM2 v: 1.0 serial: UEFI: American Megatrends v: 110M2W0X.203 date: 01/05/2017 CPU: Topology: Quad Core model: Intel Core i5-7400 bits: 64 type: MCP arch: Kaby Lake rev: 9 L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24000 Speed: 3399 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 3399 2: 3397 3: 3397 4: 3491 Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: Elite Systems driver: nvidia v: 455.38 bus ID: 01:00.0 chip ID: 10de:1c81 Display: x11 server: X.Org 1.20.8 driver: nvidia resolution: 1600x900~60Hz OpenGL: renderer: GeForce GTX 1050/PCIe/SSE2 v: 4.6.0 NVIDIA 455.38 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Elite Systems driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 Device-2: NVIDIA GP107GL High Definition Audio vendor: Elite Systems driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9 Sound Server: ALSA v: k5.4.0-56-generic Hopefully this helps to solve the problem. Kind regards Matthias ** Attachment added: "Only "Dummy-Output" shown within sound settings" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904757/+attachment/5440293/+files/Bildschirmfoto%20vom%202020-12-02%2009-40-15.png -- 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/1904757 Title: No sound after upgrade to linux-image-5.4.0-54-generic Status in linux package in Ubuntu: Incomplete Bug description: Hi Everyone, Just a heads up here... I'm working on Zorin OS 15.3, which is based on Ubuntu Bionic. I upgrade from the linux-image-5.4.0-53-generic kernel to the linux- image-5.4.0-54-generic kernel. After the upgrade to the 5.4.0-54 kernel sound stopped working. Settings showed a "Dummy Output" device and no others. A quick lsmod for snd_hda_intel showed the driver was not loaded. I was not able to load the Intel driver manually. I think there may be some sound driver problems with linux- image-5.4.0-54-generic. The user wanted her sound so I had to remove the 5.4.0-54 kernel. I won't be able to help troubleshoot it. If someone could make a quick pass on the module build results to ensure the drivers are being built for 5.4.0-54, it would be appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904757/+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 1896801] [NEW] python3-venv is gone
Public bug reported: please remove the build dependency on python3-venv. It's gone upstream. ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux-aws (Ubuntu) Importance: High Status: Confirmed ** Tags: rls-gg-incoming ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-gg-incoming ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu) Importance: Undecided => High -- 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/1896801 Title: python3-venv is gone Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: please remove the build dependency on python3-venv. It's gone upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896801/+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 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108
I was also affected in bionic (linux-image-5.3.0-62-generic), but (since today?) there is an update available: linux-image-5.4.0-42-generic (5.4.0-42.46~18.04.1) -- 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/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: [Impact] On systems using cgroups and sockets extensively, like docker, kubernetes, lxd, libvirt, a crash might happen when using linux 4.15.0-109-generic. [Fix] Revert the patch that disables sk_alloc cgroup refcounting when tasks are added to net_prio cgroup. [Test case] Test that such environments where the issue is reproduced survive some hours of uptime. A different bug was reproduced with a work-in-progress code and was not reproduced with the culprit reverted. [Regression potential] The reverted commit fix a memory leak on similar scenarios. But a leak is better than a crash. Two other bugs have been opened to track a real fix for this issue and the leak. -- Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_action+0x140/0x3a0 [ 696.397334] __do_softirq+0xe4/0x2d4 [ 696.397344] irq_exit+0xc5/0xd0 [ 696.397352] xen_evtchn_do_upcall+0x30/0x50 [ 696.397361] xen_hvm_callback_vector+0x90/0xa0 [ 696.397371] [ 696.397378] RIP: 0010:native_safe_halt+0x12/0x20 [ 696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: ff0c [ 696.397405] RAX: 8efc1800 RBX: 0006 RCX: 0
[Kernel-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
see https://sourceware.org/bugzilla/show_bug.cgi?id=25708
this seems to be an intended change.
** Bug watch added: Sourceware.org Bugzilla #25708
https://sourceware.org/bugzilla/show_bug.cgi?id=25708
** Package changed: binutils (Ubuntu Groovy) => linux (Ubuntu Groovy)
--
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/1887397
Title:
perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
New
Bug description:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
syntax error in dynamic list
collect2: error: ld returned 1 exit status
The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
And here is the chunk of Makefile that is generating this file:
define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{'; \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};'; \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM))
1>&2;\
fi
My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.
This problem is currently breaking all kernel builds in Groovy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887397/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
** Changed in: linux (Ubuntu Focal) Status: Incomplete => New ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-riscv source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-riscv source package in Groovy: New Bug description: # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1881107] Re: zfs: backport AES-GCM performance accelleration
I can confirm it. At the moment the kernel module is not patched and you need to install the package zfs-dkms. without patch: WRITE SPEED 25,3 MB/s READ SPEED 52,6 MB/s with patch (apt install zfs-dkms && reboot): WRITE SPEED 173 MB/s READ SPEED 230 MB/s Ubuntu 20.04 LTS linux-image-5.4.0-40-generic (5.4.0-40.44) amd64 zfs-dkms (0.8.3-1ubuntu12.1) all CPU: AMD Opteron(tm) X3216 APU zfs encryption: aes-256-gcm -- 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/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+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 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
to avoid that, please build linux-libc-dev from a separate source package. That would also allow providing an early user space package, while the various linux packages are still in the works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Focal: New Status in linux-riscv source package in Focal: New Status in linux source package in Groovy: New Status in linux-riscv source package in Groovy: New Bug description: # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+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 1882073] Re: Remove package after rename
Removing packages from groovy: linux-raspi2-5.4 5.4.0-1001.1 in groovy linux-buildinfo-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy arm64 linux-buildinfo-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy armhf linux-headers-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy arm64 linux-headers-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy armhf linux-image-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy arm64 linux-image-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy armhf linux-modules-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy arm64 linux-modules-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy armhf linux-raspi2-5.4-headers-5.4.0-1001 5.4.0-1001.1 in groovy arm64 linux-raspi2-5.4-headers-5.4.0-1001 5.4.0-1001.1 in groovy armhf linux-raspi2-5.4-tools-5.4.0-1001 5.4.0-1001.1 in groovy arm64 linux-raspi2-5.4-tools-5.4.0-1001 5.4.0-1001.1 in groovy armhf linux-tools-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy arm64 linux-tools-5.4.0-1001-raspi2 5.4.0-1001.1 in groovy armhf Comment: LP: #1882073, remove 1 package successfully removed. ** Changed in: linux-raspi2-5.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1882073 Title: Remove package after rename Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2-5.4 package in Ubuntu: Fix Released Bug description: linux-raspi2 was renamed to linux-raspi for Focal, but is still required for Bionic. Once Bionic is unsupported, this package can removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1882073/+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 1882073] Re: Remove package after rename
Removing packages from groovy: linux-raspi2 5.4.0-1006.6 in groovy linux-buildinfo-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy arm64 linux-buildinfo-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy armhf linux-headers-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy arm64 linux-headers-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy armhf linux-image-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy arm64 linux-image-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy armhf linux-modules-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy arm64 linux-modules-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy armhf linux-raspi2-headers-5.4.0-1006 5.4.0-1006.6 in groovy arm64 linux-raspi2-headers-5.4.0-1006 5.4.0-1006.6 in groovy armhf linux-raspi2-tools-5.4.0-1006 5.4.0-1006.6 in groovy arm64 linux-raspi2-tools-5.4.0-1006 5.4.0-1006.6 in groovy armhf linux-tools-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy arm64 linux-tools-5.4.0-1006-raspi2 5.4.0-1006.6 in groovy armhf Comment: LP: #1882073, remove 1 package successfully removed. ** Also affects: linux-raspi2-5.4 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1882073 Title: Remove package after rename Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2-5.4 package in Ubuntu: Fix Released Bug description: linux-raspi2 was renamed to linux-raspi for Focal, but is still required for Bionic. Once Bionic is unsupported, this package can removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1882073/+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 1871835] Re: [MIR] linux-raspi
Override component to main linux-raspi 5.4.0-1008.8 in focal: universe/devel -> main linux-buildinfo-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-buildinfo-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-headers-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-headers-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-image-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-image-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-modules-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-modules-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-raspi-headers-5.4.0-1008 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-raspi-headers-5.4.0-1008 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-raspi-tools-5.4.0-1008 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-raspi-tools-5.4.0-1008 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main linux-tools-5.4.0-1008-raspi 5.4.0-1008.8 in focal arm64: universe/devel/optional/100% -> main linux-tools-5.4.0-1008-raspi 5.4.0-1008.8 in focal armhf: universe/devel/optional/100% -> main 15 publications overridden. ** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- 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/1871835 Title: [MIR] linux-raspi Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Bug description: [Availability] The package is already in universe. [Rationale] The package is a core component on all supported Raspberry Pi images, both classic and core as it is responsible for pulling in the Raspberry Pi-specific kernel and headers. [Security] The raspi kernel is a derivative of the main/generic kernel (it's the same code-base with raspi specific patches and config changes). The kernel team track CVEs for the main kernel and do CVE respins of the Pi kernel in parallel with the main kernel (and all its other derivatives) if they think that a particular CVE affects the Pi kernel. They currently don't track Pi specific CVEs. [Quality assurance] There are no outstanding bugs which significantly affect the usability (i.e. our images boot successfully on all supported pi models), but there are high priority bugs open against our Pi kernel which we are actively working through (e.g. LP: #1857760). [Dependencies] There are no special dependencies compared to the main kernel package. [Standards Compliance] There are no differences in standards compliance to the main kernel package. [Maintenance] The package will be maintained by the kernel team. [Background information] As mentioned, this package is already used for all our pi images, so we are effectively already treating it as a package from main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1871835/+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 1871835] Re: [MIR] linux-raspi
Override component to main linux-meta-raspi 5.4.0.1008.8 in focal: universe/devel -> main linux-headers-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-headers-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-headers-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-headers-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-image-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-image-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-image-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-image-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal arm64: main/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal armhf: main/kernel/optional/100% -> main linux-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main linux-tools-raspi 5.4.0.1008.8 in focal arm64: universe/kernel/optional/100% -> main linux-tools-raspi 5.4.0.1008.8 in focal armhf: universe/kernel/optional/100% -> main linux-tools-raspi2 5.4.0.1008.8 in focal arm64: universe/metapackages/optional/100% -> main linux-tools-raspi2 5.4.0.1008.8 in focal armhf: universe/metapackages/optional/100% -> main 17 publications overridden; 2 publications remained the same. ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Fix Released -- 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/1871835 Title: [MIR] linux-raspi Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Bug description: [Availability] The package is already in universe. [Rationale] The package is a core component on all supported Raspberry Pi images, both classic and core as it is responsible for pulling in the Raspberry Pi-specific kernel and headers. [Security] The raspi kernel is a derivative of the main/generic kernel (it's the same code-base with raspi specific patches and config changes). The kernel team track CVEs for the main kernel and do CVE respins of the Pi kernel in parallel with the main kernel (and all its other derivatives) if they think that a particular CVE affects the Pi kernel. They currently don't track Pi specific CVEs. [Quality assurance] There are no outstanding bugs which significantly affect the usability (i.e. our images boot successfully on all supported pi models), but there are high priority bugs open against our Pi kernel which we are actively working through (e.g. LP: #1857760). [Dependencies] There are no special dependencies compared to the main kernel package. [Standards Compliance] There are no differences in standards compliance to the main kernel package. [Maintenance] The package will be maintained by the kernel team. [Background information] As mentioned, this package is already used for all our pi images, so we are effectively already treating it as a package from main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1871835/+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 1837525] Re: [20.04 FEAT] Set Architecture Level (ALS) to z13
won't fix this for gcc-10 in 20.10 either. Now enabled for the g-series ** Changed in: gcc-10 (Ubuntu) Status: New => Won't Fix -- 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/1837525 Title: [20.04 FEAT] Set Architecture Level (ALS) to z13 Status in Ubuntu on IBM z Systems: Fix Released Status in atlas package in Ubuntu: Fix Released Status in gcc-10 package in Ubuntu: Won't Fix Status in gcc-9 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: IBM requests to update the Architecture Level Set (ALS) as follow.. march=z13 mtune=z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837525/+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 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
sorry, this needs testing ** Changed in: llvm-toolchain-10 (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-10 package in Ubuntu: Incomplete Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on s390, other architectures are fine. Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To reproduce, clone the focal kernel tree and build the bpf selftests. $ git clone --single-branch --depth=1 -b master-next git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal $ make -C focal/tools/testing/selftests TARGETS=bpf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+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 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
not seen anymore with 1:10.0.0-1ubuntu2 ** Changed in: llvm-toolchain-10 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-10 package in Ubuntu: Fix Released Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on s390, other architectures are fine. Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To reproduce, clone the focal kernel tree and build the bpf selftests. $ git clone --single-branch --depth=1 -b master-next git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal $ make -C focal/tools/testing/selftests TARGETS=bpf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+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 1870091] [NEW] ftbfs in focal
Public bug reported: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946775/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-azure_5.4.0-1006.6_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1006-azure/lib/modules/5.4.0-1006-azure/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1006-azure ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-azure] Error 1 ** Affects: linux-restricted-modules-azure (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: linux-restricted-modules-azure (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules-azure (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-azure in Ubuntu. https://bugs.launchpad.net/bugs/1870091 Title: ftbfs in focal Status in linux-restricted-modules-azure package in Ubuntu: Confirmed Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946775/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-azure_5.4.0-1006.6_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1006-azure/lib/modules/5.4.0-1006-azure/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1006-azure ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-azure] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-azure/+bug/1870091/+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 1870094] [NEW] ftbfs in focal
Public bug reported: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946778/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oracle_5.4.0-1005.5_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1005-oracle/lib/modules/5.4.0-1005-oracle/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-oracle ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-oracle] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 ** Affects: linux-restricted-modules-oracle (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: linux-restricted-modules-oracle (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules-oracle (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1870094 Title: ftbfs in focal Status in linux-restricted-modules-oracle package in Ubuntu: Confirmed Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946778/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oracle_5.4.0-1005.5_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1005-oracle/lib/modules/5.4.0-1005-oracle/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-oracle ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-oracle] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oracle/+bug/1870094/+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 1870093] [NEW] ftbfs in focal
Public bug reported: seen in the second focal test rebuild https://launchpadlibrarian.net/471195717/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oem-5.4_5.4.0-1002.4_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1002-oem/lib/modules/5.4.0-1002-oem/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1002-oem ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-oem] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 ** Affects: linux-restricted-modules-oem-5.4 (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: linux-restricted-modules-oem-5.4 (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules-oem-5.4 (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1870093 Title: ftbfs in focal Status in linux-restricted-modules-oem-5.4 package in Ubuntu: Confirmed Bug description: seen in the second focal test rebuild https://launchpadlibrarian.net/471195717/buildlog_ubuntu-focal-amd64.linux-restricted-modules-oem-5.4_5.4.0-1002.4_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1002-oem/lib/modules/5.4.0-1002-oem/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-23ubuntu2) 9.2.1 20200110 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1002-oem ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-oem] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.4/+bug/1870093/+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 1870090] [NEW] ftbfs in focal
Public bug reported: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946774/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-aws_5.4.0-1005.5_BUILDING.txt.gz copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-aws ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-aws] Error 1 make[1]: Leaving directory '/<>' ** Affects: linux-restricted-modules-aws (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: linux-restricted-modules-aws (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules-aws (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-aws in Ubuntu. https://bugs.launchpad.net/bugs/1870090 Title: ftbfs in focal Status in linux-restricted-modules-aws package in Ubuntu: Confirmed Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946774/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-aws_5.4.0-1005.5_BUILDING.txt.gz copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-aws ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-aws] Error 1 make[1]: Leaving directory '/<>' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-aws/+bug/1870090/+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 1870092] [NEW] ftbfs in focal
Public bug reported: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946776/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-gcp_5.4.0-1005.5_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1005-gcp/lib/modules/5.4.0-1005-gcp/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-gcp ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-gcp] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 ** Affects: linux-restricted-modules-gcp (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: linux-restricted-modules-gcp (Ubuntu) Status: New => Confirmed ** Changed in: linux-restricted-modules-gcp (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1870092 Title: ftbfs in focal Status in linux-restricted-modules-gcp package in Ubuntu: Confirmed Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18946776/+files/buildlog_ubuntu-focal-amd64.linux-restricted-modules-gcp_5.4.0-1005.5_BUILDING.txt.gz II: dkms-build installing nvidia-390 into /<>/debian/linux-modules-nvidia-390-5.4.0-1005-gcp/lib/modules/5.4.0-1005-gcp/kernel/nvidia-390 copying nvidia-uvm.ko copying nvidia.ko copying nvidia-drm.ko copying nvidia-modeset.ko II: dkms-build override dkms-build--nvidia-N found, executing II: checking gcc version ... GCC: (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. WW: gcc version missmatch between linux and linux-restricted-modules WW: was: gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306 is: gcc (Ubuntu 9.3.0-8ubuntu1) 9.3.0 II: adding signatures from /usr/lib/linux/5.4.0-1005-gcp ... nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match make[1]: *** [debian/rules:129: nvidia-gcp] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:82: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-gcp/+bug/1870092/+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 1843742] Re: irda-utils ftbfs in eoan
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to irda-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1843742
Title:
irda-utils ftbfs in eoan
Status in irda-utils package in Ubuntu:
Confirmed
Bug description:
https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
.irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c
irdadump.c
irdadump.c: In function ‘print_time’:
irdadump.c:82:13: warning: g_string_append_printf
82 | g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
irdadump.c: In function ‘print_diff_time’:
irdadump.c:108:13: warning: g_string_append_printf
108 | g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
irdadump.c: In function ‘parse_irda_frame’:
irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
irdadump.c: In function ‘irdadump_loop’:
irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this
function); did you mean ‘SIOCGARP’?
286 | if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
irdadump.c:286:16: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: *** [Makefile:48: irdadump.o] Error 1
make[1]: Leaving directory '/<>/irdadump'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/1843742/+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 1867316] Re: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1
** Changed in: gcc-9 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867316 Title: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1 Status in chrony package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: This seems an almost global FTBFS with anything that includes limits.h $ cat > test.c << EOF > /* > * Test FTBFS 1867316 > */ > > #include > EOF ubuntu@focal-ftbfs:~/chrony-3.5$ gcc -c test.c In file included from test.c:5: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ Interestingly this fails on armhf/ppc64/s390x but works on x86. --- started as a chrony FTBFS despite tetsing a few hours before --- For bug 1866753 we built this yesterday in a proposed PPA and things worked! Now today on the final upload it failed to build on armhf/ppc64/s390x. In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26, from /usr/include/resolv.h:56, from nameserv.c:34: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ make[1]: *** [Makefile:108: nameserv.o] Error 1 The same error on all of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1867316/+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 1867316] Re: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1
the old version from -proposed is now restored, and building a 9.3.0-3ubuntu1 for a clean update to a fixed version. ** Changed in: gcc-9 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867316 Title: Almost global FTFBS due to dropping include-fixed dir in 9.3.0-1 Status in chrony package in Ubuntu: Invalid Status in gcc-9 package in Ubuntu: In Progress Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: This seems an almost global FTBFS with anything that includes limits.h $ cat > test.c << EOF > /* > * Test FTBFS 1867316 > */ > > #include > EOF ubuntu@focal-ftbfs:~/chrony-3.5$ gcc -c test.c In file included from test.c:5: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ Interestingly this fails on armhf/ppc64/s390x but works on x86. --- started as a chrony FTBFS despite tetsing a few hours before --- For bug 1866753 we built this yesterday in a proposed PPA and things worked! Now today on the final upload it failed to build on armhf/ppc64/s390x. In file included from /usr/include/powerpc64le-linux-gnu/sys/param.h:26, from /usr/include/resolv.h:56, from nameserv.c:34: /usr/include/limits.h:124:26: error: no include path in which to search for limits.h 124 | # include_next | ^ make[1]: *** [Makefile:108: nameserv.o] Error 1 The same error on all of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1867316/+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 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
please provide a test case. There's also a reason why clang is found in universe, not in main... Can you use llvm-9 as a work-around on s390x? ** Changed in: llvm-toolchain-10 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: New Status in llvm-toolchain-10 package in Ubuntu: Incomplete Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel: Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+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 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: New Status in llvm-toolchain-10 package in Ubuntu: Incomplete Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel: Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+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 1866925] Re: wrong gcc version for kernel prevents DKMS working
** Also affects: gcc-7 (Ubuntu) Importance: Undecided Status: New ** Package changed: gcc-defaults (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866925 Title: wrong gcc version for kernel prevents DKMS working Status in gcc-7 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Fresh install of minimal LUbuntu 18.04, fully updated (with new kernel). Install of NVIDIA graphics card drivers from NVIDIA script. DKMS (needed for re-compile with new kernel versions) fails as the available gcc is 7.5.0 from 18.04 and the gcc used for compiling the kernel was 7.4.0 from 18.01. The gcc for the running kernel is no longer available for installation. This mismatch is the bug. There are two alternative solutions: 1. ensure the gcc versions used to compile the available kernels are also available. 2. ensure the kernels are always compiled with the latest available gcc. The former is probably a better solution as the latter may cause unnecessary kernel recompiles as the gcc versions change. The former may require multiple installed versions of gcc, one for each installed kernel version, which would need a method of picking the gcc version which matches the kernel. It would also be useful if one of the meta-packages ensured that the installed gcc matches the installed kernel's compiler. ``` $ uname -a Linux xx 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ``` ... I'm sorry, but the DKMS make.log with the error has been deleted by a later re-run attempt for the install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcc 4:7.4.0-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Tue Mar 10 22:40:51 2020 InstallationDate: Installed on 2020-03-10 (0 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) SourcePackage: gcc-defaults UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1866925/+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 1787460] Re: Unattended upgrades removed linux-image-generic
Hi, this bug still exists! It is IMPOSSIBLE to install linux-generic- hwe-18.04 and virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack at the same time. (arch i386) I already reported this problem month ago here: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1856492 Seems like nobody cares! This is just pure shit! Some idiots think they have to release kernel 5.3, but they don't consider that nothing will work afterwards. What is even more stupid is that Kernel 5.0 is no longer available! idiots! idiots! idiots! Damn, fix that! How to reproduce this bug? -- 1.) create a minimal ubuntu with debootstrap 2.) use this sources.list: deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner 3.) update package lists apt-get update 4.) install kernel 5.3.0 from bionic-proposed apt-get install linux-generic-hwe-18.04 5.) install virtualbox apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack --- actual result: linux-generic-hwe-18.04 is being removed due to invalid dependencies expected result: linux-generic-hwe-18.04 keeps installed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Trusty: Fix Released Status in linux-meta source package in Trusty: New Status in linux-meta-hwe source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Released Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-0
[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
currently we don't build any cross compilers on s390x. Is this a scenario which is needed? We do that on ppc64el, given that you actually can buy even some workstations. and if needed, which targets should be supported? ** Changed in: ubuntu-z-systems Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs Status in Ubuntu on IBM z Systems: Incomplete Status in linux-5.4 package in Ubuntu: New Bug description: On s390x pull-lp-source linux-5.4 cd linux-* fakeroot ./debian/rules clean ./debian/rules editconfig dh_testdir; /bin/bash -e debian/scripts/misc/kernelconfig editconfigs Do you want to edit config: amd64/config.flavour.generic? [Y/n] n ... scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2 make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build' make[1]: *** [Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0' make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2 And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available to build on s390x for amd64, and also I don't want to touch amd64 configs. Only s390x ones. As a user, I should be able to rebuild ports architecture kernel with tweaked config for testing, self-hosted without cross-compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+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 1862776] Re: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
** Also affects: alsa-topology-conf (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-topology-conf (Ubuntu) Status: New => Incomplete ** Changed in: alsa-topology-conf (Ubuntu) Importance: Undecided => High ** Changed in: alsa-topology-conf (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1862776 Title: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) Status in alsa-topology-conf package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Bug description: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-topology-conf/+bug/1862776/+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 1862776] [NEW] [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib)
Public bug reported: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) ** Affects: alsa-ucm-conf (Ubuntu) Importance: High Assignee: Kernel Packages (kernel-packages) Status: Incomplete ** Tags: focal rls-ff-incoming ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. https://bugs.launchpad.net/bugs/1862776 Title: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) Status in alsa-ucm-conf package in Ubuntu: Incomplete Bug description: [MIR] alsa-ucm-conf & alsa-topology-conf (b-d of alsa-lib) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1862776/+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 1861837] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325248/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325247/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325245/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325250/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325246/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325251/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325252/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325249/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325242/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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 1861837] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1861837/+attachment/5325240/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+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
