[Kernel-packages] [Bug 1888001] Re: Focal minimal cloud image: failed to apply kernel variables
This is because CONFIG_BASE_SMALL is set to 1 in the kvm kernels. When CONFIG_BASE_SMALL=1, the maximum number of PIDs is (PAGE_SIZE * 8), which comes out to (4096 * 8) = 32768 on amd64. When CONFIG_BASE_SMALL=0 (like in normal kernels), the maximum number of PIDs for amd64 is (4 * 1024 * 1024) = 4194304. The correct solution here is to fix the systemd unit. -- 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/1888001 Title: Focal minimal cloud image: failed to apply kernel variables Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Focal minimal images have always shipped with a failing systemd unit: "systemd-sysctl.service" with the error "Couldn't write '4194304' to 'kernel/pid_max': Invalid argument" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables From the journal: Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Main process exit ed, code=exited, status=1/FAILURE Jul 20 12:18:53 ubuntu systemd[1]: systemd-sysctl.service: Faile d with result 'exit-code'. Jul 20 12:18:53 ubuntu systemd[1]: Failed to start Apply Kernel Variables. Jul 20 12:18:53 ubuntu systemd-sysctl[135]: Couldn't write '4194304' to 'ker nel/pid_max': Invalid argument Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-20.04-minimal-cloudimg-amd64.img --name=focal-minimal $ multipass exec focal-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1018-kvm root=PARTUUID=4a94aad5-09c7-46a5-aa33-f2f2e03254e7 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 5.4.0-1018.18-kvm 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-1018-kvm N/A linux-backports-modules-5.4.0-1018-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1018-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888001/+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 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
This is a bug in the open-iscsi package in xenial and bionic. That package installs this file: /lib/modules-load.d/open-iscsi.conf Which contains the following: iscsi_tcp ib_iser This causes systemd to always try and load the iscsi_tcp and ib_iser modules on boot. In eoan, the open-iscsi package doesn't do this; there's no /lib/modules-load.d/open-iscsi.conf file in the eoan cloud image. An update to xenial/bionic open-iscsi packages to match the behavior of eoan's open-iscsi package should resolve this I think. -- 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/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Steps to reproduce --- $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1069-kvm N/A linux-backports-modules-4.15.0-1069-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+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 1888551] [NEW] perf vendor events s390: Add new deflate counters for IBM z15
Public bug reported: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390: Add new deflate counters for IBM z15" [Test Case] * Requires the fix/patch of the kernel (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new extended counters for IBM z15") * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * Since these patches are upstream in kernel 5.7 they will automatically land in groovy. ** Affects: ubuntu-z-systems Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) 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/1888551 Title: perf vendor events s390: Add new deflate counters for IBM z15 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * e7950166e40271c025e0eec348cdf5c63ac734fa "perf vendor events s390: Add new deflate counters for IBM z15" [Test Case] * Requires the fix/patch of the kernel (d68d5d51dc898895b4e15bea52e5668ca9e76180 "s390/cpum_cf: Add new extended counters for IBM z15") * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * Since these patches are upstream in kernel 5.7 they will automatically land in groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888551/+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 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
perf tool patch submitted to the mailing list. -- 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/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b "s390/cpum_cf: Add new extended counters for IBM z15" [Test Case] * Requires the fix/patch of the perf tool, as mentioned in the bug, too. * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * This requires a patch to be included into the perf itself, too - please see bug description for more details. * Since this patch is upstream in kernel 5.7 it will automatically land in groovy. __ ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
The script responsible for updating the /boot/initrd.img symlink is called `linux-update-symlinks`. If a kernel is installed without that script being run, the symlink will not be updated. The only place where `linux-update-symlinks` is run is inside each of our kernels, in `debian/templates/image.postinst.in`. This means that when our kernels are built as .deb packages, the appropriate machinery will be placed inside the .deb to thus update the /boot/initrd.img symlink. I checked the change history to `installkernel` and could not find any point in time in which it ran `linux-update-symlinks`. Furthermore, the help info inside `linux-update-symlinks` contains the following note: "This command is intended to be called from the postinst and postrm maintainer scripts of Linux kernel packages." It looks like `linux- update-symlinks` was only ever intended to be used in postinst/postrm hooks for .deb packages (and not called by `installkernel`). There are a few remedies to this problem I can see, but I'm not sure which is the correct solution: 1. Add a call to `linux-update-symlinks` into `installkernel` or 2. Add a script into /etc/kernel/postinst.d to run `linux-update-symlinks` or 3. Run `linux-update-symlinks` manually after installing a kernel directly via `installkernel` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1876501] Re: package linux-modules-extra-5.4.0-28-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxgu
Does this error happen again if you try to repeat what you were doing? -- 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/1876501 Title: package linux-modules-extra-5.4.0-28-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-28-generic/kernel /virtualbox-guest/vboxguest.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: linux-image-generic-hwe-20.04: Depends: linux-modules- extra-5.4.0-28-generic but it is not installed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-28-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-modules-extra-5.4.0-28-generic:amd64: Install linux-headers-5.4.0-28:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philipe1304 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 15:06:55 2020 DpkgTerminalLog: Preparing to unpack .../linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb ... Unpacking linux-modules-extra-5.4.0-28-generic (5.4.0-28.32) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxguest.ko.dpkg-new': Operation not permitted DuplicateSignature: package:linux-modules-extra-5.4.0-28-generic:(not installed) Unpacking linux-modules-extra-5.4.0-28-generic (5.4.0-28.32) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.4.0-28-generic_5.4.0-28.32_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxguest.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxguest.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-modules-extra-5.4.0-28-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-28-generic/kernel/virtualbox-guest/vboxguest.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0798VN dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd11/08/2019:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0798VN:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876501/+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 1882854] Re: package linux-libc-dev 5.4.0-33.37 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-libc-dev:amd64.list-new': Operation not permitted
Does this error happen again if you try to repeat what you were doing? -- 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/1882854 Title: package linux-libc-dev 5.4.0-33.37 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-libc-dev:amd64.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: package linux-libc-dev 5.4.0-33.37 failed to install/upgrade: ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-libc-dev 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: az 838 F pulseaudio /dev/snd/controlC0: az 838 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jun 10 01:13:28 2020 Dependencies: DuplicateSignature: package:linux-libc-dev:5.4.0-33.37 Unpacking linux-libc-dev:amd64 (5.4.0-33.37) ... dpkg: error processing archive /tmp/apt-dpkg-install-I0RnEp/069-linux-libc-dev_5.4.0-33.37_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-libc-dev:amd64.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-libc-dev:amd64.list-new': Operation not permitted InstallationDate: Installed on 2020-06-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard p6639de ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=2b463057-1cc6-4e67-a0de-52d4aa5832d8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-libc-dev 5.4.0-33.37 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-libc-dev:amd64.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.14 dmi.board.name: 2A9C dmi.board.vendor: MSI dmi.board.version: 1.1 dmi.chassis.asset.tag: CZC050967C dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.14:bd11/05/2010:svnHewlett-Packard:pnp6639de:pvrxxx0204GR0:rvnMSI:rn2A9C:rvr1.1:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: p6639de dmi.product.sku: XS594EA#ABD dmi.product.version: xxx0204GR0 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882854/+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 1884474] Re: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-37-generic/kernel/drivers/nfc/pn544/pn544
Does this error happen again if you try to repeat what you were doing? -- 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/1884474 Title: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-37-generic/kernel/drivers/nfc/pn544/pn544_mei.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Hello, did not install updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-37-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vicente1908 F pulseaudio /dev/snd/controlC0: vicente1908 F pulseaudio CasperMD5CheckResult: skip Date: Sun Jun 21 22:12:46 2020 DuplicateSignature: package:linux-modules-extra-5.4.0-37-generic:(not installed) Unpacking linux-modules-extra-5.4.0-37-generic (5.4.0-37.41) ... dpkg: error processing archive /tmp/apt-dpkg-install-22nuuE/60-linux-modules-extra-5.4.0-37-generic_5.4.0-37.41_amd64.deb (--unpack): unable to open '/lib/modules/5.4.0-37-generic/kernel/drivers/nfc/pn544/pn544_mei.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-37-generic/kernel/drivers/nfc/pn544/pn544_mei.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-01 (21 days ago) InstallationMedia: MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2a9fafe8-6819-4e8d-9839-c4c6e3794098 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux StagingDrivers: r8188eu Title: package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-37-generic/kernel/drivers/nfc/pn544/pn544_mei.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.05 dmi.board.asset.tag: MXL34013Y2 dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL34013Y2 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.05:bd06/10/2013:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: E3S99LT#ABM dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884474/+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 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
It looks like this is fixed upstream with this change: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=178af2f97dcaea27611f0420ec7b61c1a27d6776 Which is contained in the Ubuntu-4.4.0-185 kernel already. So Ubuntu-4.4.0-185 should be fixed. -- 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/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instances. #202669 paniced in icmpv6_route_lookup and this one dies already in icmpv6_send. Between 2020-06-11 and 2020-06-15, on a set of 12 VMs running 4.4.0-184-generic, there were 85 crashes like this, on servers with noticeable IPv6 traffic. All of the 12 VMs with 4.4.0-184-generic crashed at least once. (There are more than 12 VMs experiencing this, this is just the set I had linux-crashdump on.) [57063.487084] BUG: unable to handle kernel NULL pointer dereference at 0018 [57063.487184] IP: [] icmp6_send+0x1fb/0x970 [57063.487218] PGD 0 [57063.487231] Oops: [#1] SMP [57063.488665] Call Trace: [57063.488679] [57063.488705] [] ? __netif_receive_skb+0x18/0x60 [57063.488739] [] ? task_tick_fair+0x4c8/0x8e0 [57063.488771] [] ? _raw_spin_unlock_bh+0x20/0x50 [57063.488802] [] icmpv6_send+0x21/0x30 [57063.488829] [] ip6_expire_frag_queue+0x115/0x1b0 [57063.488862] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.488897] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [57063.488937] [] call_timer_fn+0x37/0x140 [57063.488965] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.489002] [] run_timer_softirq+0x234/0x330 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+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 1878484] Re: kernel panic on i915
Please test this kernel which has a potential fix: https://kernel.ubuntu.com/~sultan/i915-lp1878484/ Source code is here: https://git.launchpad.net/~kerneltoast/ubuntu/+source/linux/+git/focal/log/?h=i915-lp1878484 -- 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/1878484 Title: kernel panic on i915 Status in linux package in Ubuntu: Incomplete Bug description: I'm using 20.04 fully up to date on an Asrock N3700. I'm getting random crashes every now and then. Total crash, no ssh or anything (later I found out it's a kernel panic). Not tied to any app, but it happened more often during gaming. Logs didn't show anything, they just stop. I set up netconsole, with debug and ignore_loglevel in the command line and I got this: [77196.866485] BUG: unable to handle page fault for address: 00a72860 [77196.866527] #PF: supervisor read access in kernel mode [77196.866535] #PF: error_code(0x) - not-present page [77196.866542] PGD 0 P4D 0 [77196.866552] Oops: [#1] SMP PTI [77196.866567] CPU: 2 PID: 1408 Comm: Xorg Tainted: P O 5.4.0-29-generic #33-Ubuntu [77196.866575] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3700-ITX, BIOS P2.00 04/16/2018 [77196.866743] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [77196.866748] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00 [77196.866753] RSP: 0018:a48380c2b9e0 EFLAGS: 00010006 [77196.866759] RAX: 00a72800 RBX: 961bed909a30 RCX: 9619a559edb0 [77196.866764] RDX: 961bed909a50 RSI: 961beaa21180 RDI: 9619a559edc0 [77196.866769] RBP: a48380c2ba78 R08: 961bf73f4420 R09: 9619a559ed80 [77196.866773] R10: R11: 0208 R12: 961bf73f4000 [77196.866783] R13: a48380c2b9f0 R14: 1000 R15: a48380c2b9c0 [77196.866788] FS: 7f6ee2aa9a80() GS:961bf830() knlGS: [77196.866794] CS: 0010 DS: ES: CR0: 80050033 [77196.866798] CR2: 00a72860 CR3: 00026a0a2000 CR4: 001006e0 [77196.866802] Call Trace: [77196.866887] i915_schedule+0x2d/0x50 [i915] [77196.866979] __fence_set_priority+0x6b/0x90 [i915] [77196.867067] fence_set_priority+0x23/0x60 [i915] [77196.867117] i915_gem_object_wait_priority+0x13e/0x170 [i915] [77196.867194] intel_prepare_plane_fb+0x1ab/0x2d0 [i915] [77196.867232] drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper] [77196.867305] intel_atomic_commit+0xc2/0x2b0 [i915] [77196.867370] drm_atomic_nonblocking_commit+0x4d/0x60 [drm] [77196.867401] drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper] [77196.867443] drm_mode_page_flip_ioctl+0x59d/0x630 [drm] [77196.867469] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [77196.867490] drm_ioctl_kernel+0xae/0xf0 [drm] [77196.867512] drm_ioctl+0x234/0x3d0 [drm] [77196.867536] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [77196.867550] do_vfs_ioctl+0x407/0x670 [77196.867560] ? fput+0x13/0x15 [77196.867568] ? __sys_recvmsg+0x88/0xa0 [77196.867575] ksys_ioctl+0x67/0x90 [77196.867582] __x64_sys_ioctl+0x1a/0x20 [77196.867592] do_syscall_64+0x57/0x190 [77196.867603] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [77196.867611] RIP: 0033:0x7f6ee2e0737b [77196.867618] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [77196.867624] RSP: 002b:7ffe6ff493d8 EFLAGS: 0246 ORIG_RAX: 0010 [77196.867631] RAX: ffda RBX: 7ffe6ff49410 RCX: 7f6ee2e0737b [77196.867635] RDX: 7ffe6ff49410 RSI: c01864b0 RDI: 000e [77196.867640] RBP: c01864b0 R08: 002bf8f2 R09: 006a [77196.867645] R10: 000e R11: 0246 R12: 56454c520040 [77196.867649] R13: 000e R14: 002bf8f2 R15: 0002 [77196.867655] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr mei_hdcp snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_common intel_powerclamp coretemp kvm_intel kvm punit_atom_debug intel_cstate snd_seq snd_seq_device snd_timer snd mei_txe soundcore mei hci_uart intel_xhci_usb_role_switch btqca roles btrtl btbcm btintel bluetooth ecdh_generic ecc rfkill_gpio acpi_pad
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. [Fix] The sauce patch I made should be dropped in exchange for the proper upstream fix. [Test] I tested the upstream fix and can confirm it fixes the crashes I experienced. [Regression Potential] Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Changed in: linux (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification: [Impact] Users are experiencing a frequent NULL pointer dereference crash in i915_active_acquire when using kms, which is used by default. [Fix] The fix is a cherry pick from upstream which was supposed to be backported to 5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to resolve some uninitialized pointer usage. [Test] Verified by multiple bug reporters. [Regression Potential] Medium. Although there are a lot of lines added, they're mostly boilerplate, and this patch is confirmed by multiple users to fix a crash. --- uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Changed in: linux (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification: [Impact] A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. [Fix] The sauce patch I made should be dropped in exchange for the proper upstream fix. [Test] I tested the upstream fix and can confirm it fixes the crashes I experienced. [Regression Potential] Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Description changed: + SRU Justification: + + [Impact] + A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. + + [Fix] + The sauce patch I made should be dropped in exchange for the proper upstream fix. + + [Test] + I tested the upstream fix and can confirm it fixes the crashes I experienced. + + [Regression Potential] + Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. + --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. [Fix] The sauce patch I made should be dropped in exchange for the proper upstream fix. [Test] I tested the upstream fix and can confirm it fixes the crashes I experienced. [Regression Potential] Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Description changed: + SRU Justification: + [Impact] + Users are experiencing a frequent NULL pointer dereference crash in + i915_active_acquire when using kms, which is used by default. + + [Fix] + The fix is a cherry pick from upstream which was supposed to be backported to + 5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to + resolve some uninitialized pointer usage. + + [Test] + Verified by multiple bug reporters. + + [Regression Potential] + Medium. Although there are a lot of lines added, they're mostly boilerplate, and + this patch is confirmed by multiple users to fix a crash. + --- uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page - [ 2556.956085] PGD 0 P4D 0 + [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152 [ 2556.956409]
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Description changed: This is what the crash looks like: - BUG: unable to handle page fault for address: 3448 - RIP: 0010:gen8_emit_flush_render+0x163/0x190 - Call Trace: - execlists_request_alloc+0x25/0x40 - __i915_request_create+0x1f4/0x2c0 - i915_request_create+0x71/0xc0 - i915_gem_do_execbuffer+0xb98/0x1a80 - ? preempt_count_add+0x68/0xa0 - ? _raw_spin_lock+0x13/0x30 - ? _raw_spin_unlock+0x16/0x30 - i915_gem_execbuffer2_ioctl+0x1de/0x3c0 - ? i915_gem_busy_ioctl+0x7f/0x1d0 - ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 - drm_ioctl_kernel+0xb2/0x100 - drm_ioctl+0x209/0x360 - ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 - ksys_ioctl+0x87/0xc0 - __x64_sys_ioctl+0x16/0x20 - do_syscall_64+0x4e/0x150 - entry_SYSCALL_64_after_hwframe+0x44/0xa9 + BUG: unable to handle page fault for address: 3448 + RIP: 0010:gen8_emit_flush_render+0x163/0x190 + Call Trace: + execlists_request_alloc+0x25/0x40 + __i915_request_create+0x1f4/0x2c0 + i915_request_create+0x71/0xc0 + i915_gem_do_execbuffer+0xb98/0x1a80 + ? preempt_count_add+0x68/0xa0 + ? _raw_spin_lock+0x13/0x30 + ? _raw_spin_unlock+0x16/0x30 + i915_gem_execbuffer2_ioctl+0x1de/0x3c0 + ? i915_gem_busy_ioctl+0x7f/0x1d0 + ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 + drm_ioctl_kernel+0xb2/0x100 + drm_ioctl+0x209/0x360 + ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 + ksys_ioctl+0x87/0xc0 + __x64_sys_ioctl+0x16/0x20 + do_syscall_64+0x4e/0x150 + entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. + + More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 -- 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1877394] [NEW] Kernel panic due to NULL ringbuffer vaddr dereference in i915
Public bug reported: This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Focal) 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+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 1873673] Re: Kernel Error IRQ
I think i801_isr needs to be marked with IRQF_NO_THREAD. Please try this kernel and see if it fixes the problem: https://kernel.ubuntu.com/~sultan/i801-lp1873673/ -- 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/1873673 Title: Kernel Error IRQ Status in linux package in Ubuntu: Confirmed Bug description: Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0 - one with an external HD connected, and one USB-C) I noted that the mouse and keyboard using one Logitech Unifying receiver (connected through USB on the Laptop, not dock) started to jump over the screen and responded bad. I noted on dmesg the following error: [ 464.663455] [ cut here ] [ 464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled interrupts [ 464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 __handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core wmi_bmof serio_raw snd_rawmidi [ 464.663564] elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel [ 464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P O 5.4.0-24-lowlatency #28-Ubuntu [ 464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 ) 01/15/2020 [ 464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0 [ 464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 [ 464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286 [ 464.663647] RAX: RBX: 97bd37c54200 RCX: 0006 [ 464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0 [ 464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d [ 464.663653] R10: 0001eb4c R11: 0004 R12: 00a0 [ 464.663655] R13: R14: 97bd3825c700 R15: 0002 [ 464.663658] FS: () GS:97bd3c10() knlGS: [ 464.663661] CS: 0010 DS: ES: CR0: 80050033 [ 464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0 [ 464.663665] DR0: DR1: DR2: [ 464.663667] DR3: DR6: fffe0ff0 DR7: 0400 [ 464.663669] Call Trace: [ 464.663680] ? irq_finalize_oneshot.part.0+0xe0/0xe0 [ 464.663686] handle_irq_event_percpu+0x33/0x80 [ 464.663692] handle_irq_event+0x39/0x58 [ 464.663697] handle_simple_irq+0x6f/0xa0 [ 464.663703] generic_handle_irq+0x28/0x40 [ 464.663709] i2c_handle_smbus_host_notify+0x28/0x40 [ 464.663717] i801_isr+0x1ee/0x300 [i2c_i801] [ 464.663724] irq_forced_thread_fn+0x33/0x80 [ 464.663729] irq_thread+0xda/0x170 [ 464.663736] ? wake_threads_waitq+0x30/0x30 [ 464.663741] kthread+0x104/0x140 [ 464.663747] ? irq_thread_check_affinity+0xe0/0xe0 [ 464.663750] ? kthread_park+0x90/0x90 [ 464.663757]
[Kernel-packages] [Bug 1873684] Re: [Lenovo ThinkCentre M93] reboots instead of shutting down
I think another log is needed to debug this. Please do the following: 1. Try to shut down your computer from Ubuntu, so that it reboots. 2. After it reboots, run the following command in a terminal: sudo journalctl -b -1 -k > PreviousDmesg.txt 3. Upload PreviousDmesg.txt here. -- 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/1873684 Title: [Lenovo ThinkCentre M93] reboots instead of shutting down Status in linux package in Ubuntu: Confirmed Bug description: Computer restarts when i tell it shutdown. Does not happen when shutdown from grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-96-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Sun Apr 19 17:45:43 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 10AAS26000 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=93704773-d4bc-4268-acb0-35d5acc4a037 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT87AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD or WIN dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT87AUS:bd05/09/2014:svnLENOVO:pn10AAS26000:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvrSDK0E50512STDorWIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 10AAS26000 dmi.product.version: ThinkCentre M93p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873684/+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 1873714] Re: Computer freeze on application change (i915 GPU hang)
** Summary changed: - Computer freeze on application change / memory allocation + Computer freeze on application change (i915 GPU hang) -- 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/1873714 Title: Computer freeze on application change (i915 GPU hang) Status in linux package in Ubuntu: Confirmed Bug description: Experience behaviour: The system freezes for about 10 seconds often when - I change applications - I open applications - switch tabs in firefox - open new web pages - draw in GIMP with pen tablet Average occurance: - every 1 - 4 minutes // usual PC usage - every 30 seconds // when drawing in GIMP with pen tablet Reproducability: always My guess is: The system freezes, when memory management is done. Additional information: - 5.3.0-40-generic had none of these problems - 5.3.0-45-generic had similar problems, but instead of freezing for 10 seconds, the system would just freeze forever. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 1588 F pulseaudio /dev/snd/pcmC0D3p: nimono 1588 F...m pulseaudio /dev/snd/pcmC0D0c: nimono 1588 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Apr 20 11:19:29 2020 MachineType: FUJITSU FMVWB3U27 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-12-01 (141 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873714/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@leozinho29-eu The kernel from comment 34 was just a plain 5.4.0-26 kernel, with nothing added to it (which wasn't intentional). Could you reproduce the atomic update failure messages with an official Ubuntu kernel installed, and then create a new launchpad bug for it? Given that you encountered the atomic update failures with comment 34's kernel, which was just an unmodified Ubuntu kernel, I don't think the problem is related to the fix for this bug. The bisect from your duplicate doesn't make sense, but I think there's a reasonable explanation for that. This kernel panic is caused by a race, so any changes to code that could affect the timing of the GPU driver's code execution, in some indirect way, could either exacerbate or alleviate the crash. That said, there is a clear diagnosis for this bug, and it is definitely fixed by the upstream commit da42104f589d ("drm/i915: Hold reference to intel_frontbuffer as we track activity"). -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@leozinho29-eu Please try this kernel: https://kernel.ubuntu.com/~sultan/i915-lp1868551/ Note that there really is only one package to install. That single package contains everything. -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@leozinho29-eu For some reason, the builder I used to make the kernel in comment 34 didn't pick up the change that was supposed to fix this bug's crash... I'll rebuild it on my local machine for you. -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@leozinho29-eu Wow, that's really unexpected! I'll take a look. Thanks for the log and quick reply. -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152 [ 2556.956409] wmi_bmof mii mac80211
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@leozinho29-eu Can you add i915.enable_fbc=0 to the kernel command line and see if that fixes the "Atomic update failure" messages? If it does, then we'll know the problem is related to framebuffer compression. -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
@lordbaco Please install this kernel and see if it still crashes: https://kernel.ubuntu.com/~sultan/i915-lp1870265/ -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152 [ 2556.956409]
[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
*** This bug is a duplicate of bug 1868551 *** https://bugs.launchpad.net/bugs/1868551 ** This bug has been marked a duplicate of bug 1868551 Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire -- 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/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 Status in linux package in Ubuntu: Confirmed Bug description: After playing Gurumin: A Monstrous Adventure for some time, the system crashed in an unrecoverable way. REISUB was required to get some logs. This crash happened with default Ubuntu's kernel, default Mesa and default Xorg session. I never observed a crash this serious using the intel Xorg driver. However, using the default (modesetting), the following unrecoverable crash happened after two hours: The syslog contains the following: Apr 2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php session files... Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: Succeeded. Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php session files. Apr 2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel NULL pointer dereference, address: 0040 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: supervisor read access in kernel mode Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: error_code(0x) - not-present page Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops: [#1] SMP PTI Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 200385 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 0018:bd8446f979c8 EFLAGS: 00010286 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: RBX: 9c477afaca80 RCX: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 9c4633bfc500 RSI: 9c477afaca80 RDI: 0008 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 00014000 R11: 9c47d1918b00 R12: 9c4633bfc500 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 0008 R14: 9c4633bfc500 R15: 9c47d6f4db00 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS: 7f99a3564a80() GS:9c47de28() knlGS: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS: 0010 DS: ES: CR0: 80050033 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 0040 CR3: 000556ca0001 CR4: 003606e0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: DR1: DR2: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: DR6: fffe0ff0 DR7: 0400 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477] i915_active_ref+0x24/0x200 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564] eb_submit+0xff/0x440 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615] ? sock_def_readable+0x40/0x70 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618] ? __kmalloc_node+0x205/0x320 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 2 00:58:56
[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
@leozinho29-eu Please install this kernel and see if it still crashes: https://kernel.ubuntu.com/~sultan/i915-lp1870265/ -- 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/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 Status in linux package in Ubuntu: Confirmed Bug description: After playing Gurumin: A Monstrous Adventure for some time, the system crashed in an unrecoverable way. REISUB was required to get some logs. This crash happened with default Ubuntu's kernel, default Mesa and default Xorg session. I never observed a crash this serious using the intel Xorg driver. However, using the default (modesetting), the following unrecoverable crash happened after two hours: The syslog contains the following: Apr 2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php session files... Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: Succeeded. Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php session files. Apr 2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel NULL pointer dereference, address: 0040 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: supervisor read access in kernel mode Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: error_code(0x) - not-present page Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops: [#1] SMP PTI Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 200385 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 0018:bd8446f979c8 EFLAGS: 00010286 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: RBX: 9c477afaca80 RCX: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 9c4633bfc500 RSI: 9c477afaca80 RDI: 0008 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 00014000 R11: 9c47d1918b00 R12: 9c4633bfc500 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 0008 R14: 9c4633bfc500 R15: 9c47d6f4db00 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS: 7f99a3564a80() GS:9c47de28() knlGS: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS: 0010 DS: ES: CR0: 80050033 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 0040 CR3: 000556ca0001 CR4: 003606e0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: DR1: DR2: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: DR6: fffe0ff0 DR7: 0400 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477] i915_active_ref+0x24/0x200 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564] eb_submit+0xff/0x440 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615] ? sock_def_readable+0x40/0x70 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618] ? __kmalloc_node+0x205/0x320 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742] drm_ioctl_kernel+0xae/0xf0 [drm] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK
[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
This bug is fixed by upstream commit da42104f589d979bbe402703fd836cec60befae1: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da42104f589d979bbe402703fd836cec60befae1 It looks like that commit was *supposed* to be backported to 5.4 ("Cc: # v5.4+"), but the i915 maintainers didn't do it, so we'll need to backport it ourselves. -- 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/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 Status in linux package in Ubuntu: Confirmed Bug description: After playing Gurumin: A Monstrous Adventure for some time, the system crashed in an unrecoverable way. REISUB was required to get some logs. This crash happened with default Ubuntu's kernel, default Mesa and default Xorg session. I never observed a crash this serious using the intel Xorg driver. However, using the default (modesetting), the following unrecoverable crash happened after two hours: The syslog contains the following: Apr 2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php session files... Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: Succeeded. Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php session files. Apr 2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel NULL pointer dereference, address: 0040 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: supervisor read access in kernel mode Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: error_code(0x) - not-present page Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops: [#1] SMP PTI Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 200385 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 0018:bd8446f979c8 EFLAGS: 00010286 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: RBX: 9c477afaca80 RCX: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 9c4633bfc500 RSI: 9c477afaca80 RDI: 0008 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 00014000 R11: 9c47d1918b00 R12: 9c4633bfc500 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 0008 R14: 9c4633bfc500 R15: 9c47d6f4db00 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS: 7f99a3564a80() GS:9c47de28() knlGS: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS: 0010 DS: ES: CR0: 80050033 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 0040 CR3: 000556ca0001 CR4: 003606e0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: DR1: DR2: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: DR6: fffe0ff0 DR7: 0400 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477] i915_active_ref+0x24/0x200 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564] eb_submit+0xff/0x440 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615] ? sock_def_readable+0x40/0x70 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618] ? __kmalloc_node+0x205/0x320 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 2 00:58:56
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@eggie Yes, you should actually blacklist the nouveau module. Or instead, if you don't want your Nvidia card to drain power while you're using exclusively Intel graphics, run the following commands: sudo -i cat << EOF | sudo tee /etc/udev/rules.d/00-pcidevices.rules ACTION=="add", KERNEL==":01:00.0", SUBSYSTEM=="pci", RUN+="/bin/sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'" EOF This adds a permanent rule to eject the Nvidia card from your system so that it won't use any power. Reboot for it to take effect. On some laptops this doesn't stop the Nvidia card from draining power, but on Dell laptops it does. This is what I use on my Precision 5540, which is essentially the same laptop as yours. -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@eggie You shouldn't be using nouveau on your hardware; it has almost no support for the Turing architecture from Nvidia. You should blacklist nouveau and then reboot. If you want to make use of your Nvidia card, you'll have to use the binary Nvidia driver sadly. -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc.
[Kernel-packages] [Bug 1874124] Re: Add hw timestamps to received skbs in peak_canfd
** Description changed: + [Impact] + In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. + + [Test case] + + Apply the patch and compile. + + [Fix] + + Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F. + + [Regression potential] + + Low. This is a small upstream commit to an uncommonly used device + driver. ** Description changed: [Impact] - - In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw - timestamps were added to received messages in the peak_canfd driver. - Backport the patch so users of our kernels can make use of the - timestamps. + In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. [Test case] - Apply the patch and compile. [Fix] - Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F. [Regression potential] - - Low. This is a small upstream commit to an uncommonly used device - driver. + Low. This is a small upstream commit to an uncommonly used device driver. ** Description changed: [Impact] In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. + + SF 274042. [Test case] Apply the patch and compile. [Fix] Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F. [Regression potential] Low. This is a small upstream commit to an uncommonly used device driver. ** Description changed: [Impact] - In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. - - SF 274042. + SF 274042: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. [Test case] Apply the patch and compile. [Fix] Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F. [Regression potential] Low. This is a small upstream commit to an uncommonly used device driver. -- 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/1874124 Title: Add hw timestamps to received skbs in peak_canfd Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] SF 274042: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. [Test case] Apply the patch and compile. [Fix] Cherry pick 2b1a4547c122dcbe1a876236b44408c7d01c into B/E/F. [Regression potential] Low. This is a small upstream commit to an uncommonly used device driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874124/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@jlammrs You can't use that kernel with secure boot because it's unsigned. -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1874124] [NEW] Add hw timestamps to received skbs in peak_canfd
Public bug reported: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1874124 Title: Add hw timestamps to received skbs in peak_canfd Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: In commit 2b1a4547c122dcbe1a876236b44408c7d01c upstream, useful hw timestamps were added to received messages in the peak_canfd driver. Backport the patch so users of our kernels can make use of the timestamps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874124/+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 1869924] Re: High power consumption by Intel iGPU on Skylake+
*** This bug is a duplicate of bug 1853044 *** https://bugs.launchpad.net/bugs/1853044 Duplicate of https://launchpad.net/bugs/1853044 ** This bug has been marked a duplicate of bug 1853044 5.3.0-23-generic causes fans to spin when idle -- 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/1869924 Title: High power consumption by Intel iGPU on Skylake+ Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. Backporting this commit was not trivial due to i915's high rate of churn, but the backport didn't require changing any code from the original commit; it only required moving code around and not altering some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869924/+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 1869924] Re: High power consumption by Intel iGPU on Skylake+
** Changed in: linux (Ubuntu Focal) 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/1869924 Title: High power consumption by Intel iGPU on Skylake+ Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. Backporting this commit was not trivial due to i915's high rate of churn, but the backport didn't require changing any code from the original commit; it only required moving code around and not altering some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869924/+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 1870242] Re: Kernel oops in i915 on 5.4.0-18-generic
** Changed in: linux (Ubuntu Focal) 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/1870242 Title: Kernel oops in i915 on 5.4.0-18-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: I was running 5.4.0-18-generic and got the following splat doing nothing interesting in particular: BUG: unable to handle page fault for address: 84abf450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 Oops: 0010 [#1] SMP CPU: 11 PID: 1114 Comm: kworker/11:3 Tainted: P U O 5.4.0-18-generic #22 Hardware name: Dell Inc. Precision 5540/0FMYX6, BIOS 1.5.0 12/25/2019 Workqueue: events __intel_wakeref_put_work [i915] RIP: 0010:0x84abf450 Code: Bad RIP value. RSP: 0018:ad7380757cc0 EFLAGS: 00010246 RAX: RBX: 89ebc46a6d98 RCX: RDX: 0001 RSI: 0001 RDI: 89ebc46a6d98 RBP: ad7380757d40 R08: 89ebd88eeb58 R09: 89ebd88eec28 R10: R11: ac065868 R12: 89ebc46a6d98 R13: R14: 0001 R15: 89ebd00283c0 FS: () GS:89ebdc2c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 84abf426 CR3: 0004d420a002 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: ? __flush_work+0x51/0x1d0 ? wake_up_process+0x15/0x20 __cancel_work_timer+0x10e/0x190 ? _cond_resched+0x19/0x30 ? synchronize_irq+0x3e/0xb0 cancel_work_sync+0x10/0x20 gen6_disable_rps_interrupts+0xa0/0xd0 [i915] gen6_rps_idle+0x1f/0xf0 [i915] __gt_park+0x93/0xa0 [i915] intel_wakeref_put_last+0x1f/0x50 [i915] __intel_wakeref_put_work+0x37/0x40 [i915] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 I looked through the differences between 5.4.0-18 and the tip of master-next for focal ("UBUNTU: upstream stable to v5.4.29"), and there are no new changes to i915 that could've fixed this. I've filed a bug with Intel, since this doesn't seem to be Ubuntu- specific: https://gitlab.freedesktop.org/drm/intel/issues/1597 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870242/+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 1870242] Re: Kernel oops in i915 on 5.4.0-18-generic
** Description changed: I was running 5.4.0-18-generic and got the following splat doing nothing interesting in particular: BUG: unable to handle page fault for address: 84abf450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 Oops: 0010 [#1] SMP CPU: 11 PID: 1114 Comm: kworker/11:3 Tainted: P U O 5.4.0-18-generic #22 Hardware name: Dell Inc. Precision 5540/0FMYX6, BIOS 1.5.0 12/25/2019 Workqueue: events __intel_wakeref_put_work [i915] RIP: 0010:0x84abf450 Code: Bad RIP value. RSP: 0018:ad7380757cc0 EFLAGS: 00010246 RAX: RBX: 89ebc46a6d98 RCX: RDX: 0001 RSI: 0001 RDI: 89ebc46a6d98 RBP: ad7380757d40 R08: 89ebd88eeb58 R09: 89ebd88eec28 R10: R11: ac065868 R12: 89ebc46a6d98 R13: R14: 0001 R15: 89ebd00283c0 FS: () GS:89ebdc2c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 84abf426 CR3: 0004d420a002 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: ? __flush_work+0x51/0x1d0 ? wake_up_process+0x15/0x20 __cancel_work_timer+0x10e/0x190 ? _cond_resched+0x19/0x30 ? synchronize_irq+0x3e/0xb0 cancel_work_sync+0x10/0x20 gen6_disable_rps_interrupts+0xa0/0xd0 [i915] gen6_rps_idle+0x1f/0xf0 [i915] __gt_park+0x93/0xa0 [i915] intel_wakeref_put_last+0x1f/0x50 [i915] __intel_wakeref_put_work+0x37/0x40 [i915] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 I looked through the differences between 5.4.0-18 and the tip of master- next for focal ("UBUNTU: upstream stable to v5.4.29"), and there are no new changes to i915 that could've fixed this. + + I've filed a bug with Intel, since this doesn't seem to be Ubuntu- + specific: https://gitlab.freedesktop.org/drm/intel/issues/1597 -- 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/1870242 Title: Kernel oops in i915 on 5.4.0-18-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: I was running 5.4.0-18-generic and got the following splat doing nothing interesting in particular: BUG: unable to handle page fault for address: 84abf450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 Oops: 0010 [#1] SMP CPU: 11 PID: 1114 Comm: kworker/11:3 Tainted: P U O 5.4.0-18-generic #22 Hardware name: Dell Inc. Precision 5540/0FMYX6, BIOS 1.5.0 12/25/2019 Workqueue: events __intel_wakeref_put_work [i915] RIP: 0010:0x84abf450 Code: Bad RIP value. RSP: 0018:ad7380757cc0 EFLAGS: 00010246 RAX: RBX: 89ebc46a6d98 RCX: RDX: 0001 RSI: 0001 RDI: 89ebc46a6d98 RBP: ad7380757d40 R08: 89ebd88eeb58 R09: 89ebd88eec28 R10: R11: ac065868 R12: 89ebc46a6d98 R13: R14: 0001 R15: 89ebd00283c0 FS: () GS:89ebdc2c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 84abf426 CR3: 0004d420a002 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: ? __flush_work+0x51/0x1d0 ? wake_up_process+0x15/0x20 __cancel_work_timer+0x10e/0x190 ? _cond_resched+0x19/0x30 ? synchronize_irq+0x3e/0xb0 cancel_work_sync+0x10/0x20 gen6_disable_rps_interrupts+0xa0/0xd0 [i915] gen6_rps_idle+0x1f/0xf0 [i915] __gt_park+0x93/0xa0 [i915] intel_wakeref_put_last+0x1f/0x50 [i915] __intel_wakeref_put_work+0x37/0x40 [i915] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 I looked through the differences between 5.4.0-18 and the tip of master-next for focal ("UBUNTU: upstream stable to v5.4.29"), and there are no new changes to i915 that could've fixed this. I've filed a bug with Intel, since this doesn't seem to be Ubuntu- specific: https://gitlab.freedesktop.org/drm/intel/issues/1597 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870242/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1870242] [NEW] Kernel oops in i915 on 5.4.0-18-generic
Public bug reported: I was running 5.4.0-18-generic and got the following splat doing nothing interesting in particular: BUG: unable to handle page fault for address: 84abf450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 Oops: 0010 [#1] SMP CPU: 11 PID: 1114 Comm: kworker/11:3 Tainted: P U O 5.4.0-18-generic #22 Hardware name: Dell Inc. Precision 5540/0FMYX6, BIOS 1.5.0 12/25/2019 Workqueue: events __intel_wakeref_put_work [i915] RIP: 0010:0x84abf450 Code: Bad RIP value. RSP: 0018:ad7380757cc0 EFLAGS: 00010246 RAX: RBX: 89ebc46a6d98 RCX: RDX: 0001 RSI: 0001 RDI: 89ebc46a6d98 RBP: ad7380757d40 R08: 89ebd88eeb58 R09: 89ebd88eec28 R10: R11: ac065868 R12: 89ebc46a6d98 R13: R14: 0001 R15: 89ebd00283c0 FS: () GS:89ebdc2c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 84abf426 CR3: 0004d420a002 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: ? __flush_work+0x51/0x1d0 ? wake_up_process+0x15/0x20 __cancel_work_timer+0x10e/0x190 ? _cond_resched+0x19/0x30 ? synchronize_irq+0x3e/0xb0 cancel_work_sync+0x10/0x20 gen6_disable_rps_interrupts+0xa0/0xd0 [i915] gen6_rps_idle+0x1f/0xf0 [i915] __gt_park+0x93/0xa0 [i915] intel_wakeref_put_last+0x1f/0x50 [i915] __intel_wakeref_put_work+0x37/0x40 [i915] process_one_work+0x1eb/0x3b0 worker_thread+0x4d/0x400 kthread+0x104/0x140 ? process_one_work+0x3b0/0x3b0 ? kthread_park+0x90/0x90 ret_from_fork+0x1f/0x40 I looked through the differences between 5.4.0-18 and the tip of master- next for focal ("UBUNTU: upstream stable to v5.4.29"), and there are no new changes to i915 that could've fixed this. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Tags: focal ** Also affects: linux Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux ** No longer affects: kernel-sru-workflow ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: I was running 5.4.0-18-generic and got the following splat doing nothing interesting in particular: BUG: unable to handle page fault for address: 84abf450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page - PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 + PGD 4d420e067 P4D 4d420e067 PUD 4d420f063 PMD 0 Oops: 0010 [#1] SMP CPU: 11 PID: 1114 Comm: kworker/11:3 Tainted: P U O 5.4.0-18-generic #22 Hardware name: Dell Inc. Precision 5540/0FMYX6, BIOS 1.5.0 12/25/2019 Workqueue: events __intel_wakeref_put_work [i915] RIP: 0010:0x84abf450 Code: Bad RIP value. RSP: 0018:ad7380757cc0 EFLAGS: 00010246 RAX: RBX: 89ebc46a6d98 RCX: RDX: 0001 RSI: 0001 RDI: 89ebc46a6d98 RBP: ad7380757d40 R08: 89ebd88eeb58 R09: 89ebd88eec28 R10: R11: ac065868 R12: 89ebc46a6d98 R13: R14: 0001 R15: 89ebd00283c0 FS: () GS:89ebdc2c() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 84abf426 CR3: 0004d420a002 CR4: 003606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: - ? __flush_work+0x51/0x1d0 - ? wake_up_process+0x15/0x20 - __cancel_work_timer+0x10e/0x190 - ? _cond_resched+0x19/0x30 - ? synchronize_irq+0x3e/0xb0 - cancel_work_sync+0x10/0x20 - gen6_disable_rps_interrupts+0xa0/0xd0 [i915] - gen6_rps_idle+0x1f/0xf0 [i915] - __gt_park+0x93/0xa0 [i915] - intel_wakeref_put_last+0x1f/0x50 [i915] - __intel_wakeref_put_work+0x37/0x40 [i915] - process_one_work+0x1eb/0x3b0 - worker_thread+0x4d/0x400 - kthread+0x104/0x140 - ? process_one_work+0x3b0/0x3b0 - ? kthread_park+0x90/0x90 - ret_from_fork+0x1f/0x40 + ? __flush_work+0x51/0x1d0 + ? wake_up_process+0x15/0x20 + __cancel_work_timer+0x10e/0x190 + ? _cond_resched+0x19/0x30 + ? synchronize_irq+0x3e/0xb0 + cancel_work_sync+0x10/0x20 + gen6_disable_rps_interrupts+0xa0/0xd0 [i915] + gen6_rps_idle+0x1f/0xf0 [i915] + __gt_park+0x93/0xa0 [i915] + intel_wakeref_put_last+0x1f/0x50 [i915] + __intel_wakeref_put_work+0x37/0x40 [i915] + process_one_work+0x1eb/0x3b0 + worker_thread+0x4d/0x400 + kthread+0x104/0x140 + ?
[Kernel-packages] [Bug 1869924] [NEW] High power consumption by Intel iGPU on Skylake+
Public bug reported: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. Backporting this commit was not trivial due to i915's high rate of churn, but the backport didn't require changing any code from the original commit; it only required moving code around and not altering some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux Importance: Undecided Status: New ** No longer affects: lightdm (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake and newer. This bug was fixed upstream in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1]. My cover letter [2] describes the issue: - The first bug, fixed by - "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very - high power consumption by i915 hardware due to an old commit that broke the RC6 - power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with - an i9-9880H, the idle power consumption of my laptop with this commit goes down - from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I - tested, this commit reduced idle power consumption by at least a few watts. The - difference in power consumption can be observed by running `powertop` while - disconnected from the charger, or by using the intel-undervolt tool [1] and - running `intel-undervolt measure` which doesn't require being disconnected from - the charger. The psys measurement from intel-undervolt is the one of interest. + The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is very high power consumption by i915 hardware due to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I tested, this commit reduced idle power consumption by at least a few watts. The difference in power consumption can be observed by running `powertop` while disconnected from the charger, or by using the intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't require being disconnected from the charger. The psys measurement from intel-undervolt is the one of interest. - Backporting this commit was not trivial due to i915's high rate of churn, but - the backport didn't require changing any code from the original commit; it only - required moving code around and not altering some #includes. - + Backporting this commit was not trivial due to i915's high rate of + churn, but the backport didn't require changing any code from the + original commit; it only required moving code around and not altering + some #includes. [1] https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/ [2] https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/ -- 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/1869924 Title: High power consumption by Intel iGPU on Skylake+ Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Bug description: There is an outstanding regression in i915 that breaks the RC6 power state for Intel iGPUs on Skylake
[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
As a note: https://platform.leolabs.space/visualizations/leo is not a valid reproducer for this bug, since the lags it causes are from overloading the GPU, not from stressing memory. -- 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/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: [Impact] High watermark boosting can cause large swap activity under certain memory intensive workloads, making the system very unresponsive (screen does not refresh, keyboard not responding, etc.). This large swap activity seems to be prevented disabling high watermark boosting. [Test case] Opening this web page in chrome seems to be a good reproducer of the problem: https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040 When this page is opened we can clearly see from 'top' (for example) that the used swap is going up very quickly. With the fix applied swap is not used at all and the system is always responsive. [Fix] Set vm.watermark_boost_factor to 0, disabling watermark boosting by default. [Regression potential] Regression potential is minimal, setting vm.watermark_boost_factor to 0 by default restores the old kernel behavior before watermark boosting was introduced. In case of unexpected regressions we can always fix this in user-space via sysctl. [Original report] Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
FYI, this bug has nothing to do with the use of swap. It just happens that the slow writeback incurred by using a swap device backed by non- volatile memory makes kswapd's bouts of page thrashing last longer, enough to the point where there's a visual freeze. -- 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/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: [Impact] High watermark boosting can cause large swap activity under certain memory intensive workloads, making the system very unresponsive (screen does not refresh, keyboard not responding, etc.). This large swap activity seems to be prevented disabling high watermark boosting. [Test case] Opening this web page in chrome seems to be a good reproducer of the problem: https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040 When this page is opened we can clearly see from 'top' (for example) that the used swap is going up very quickly. With the fix applied swap is not used at all and the system is always responsive. [Fix] Set vm.watermark_boost_factor to 0, disabling watermark boosting by default. [Regression potential] Regression potential is minimal, setting vm.watermark_boost_factor to 0 by default restores the old kernel behavior before watermark boosting was introduced. In case of unexpected regressions we can always fix this in user-space via sysctl. [Original report] Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
This problem is caused by an upstream memory management feature called watermark boosting. Normally, when a memory allocation fails and falls back to the page allocator, the page allocator will wake up kswapd to free up pages in order to make the memory allocation succeed. kswapd tries to free memory until it reaches a minimum amount of memory for each memory zone called the high watermark. What watermark boosting does is try to preemptively fire up kswapd to free memory when there hasn't been an allocation failure. It does this by increasing kswapd's high watermark goal and then firing up kswapd. The reason why this causes freezes is because, with the increased high watermark goal, kswapd will steal memory from processes that need it in order to make forward progress. These processes will, in turn, try to allocate memory again, which will cause kswapd to steal necessary pages from those processes again, in a positive feedback loop known as page thrashing. When page thrashing occurs, your system is essentially livelocked until the necessary forward progress can be made to stop processes from trying to continuously allocate memory and trigger kswapd to steal it back. This problem already occurs with kswapd *without* watermark boosting, but it's usually only encountered on machines with a small amount of memory and/or a slow CPU. Watermark boosting just makes the existing problem worse enough to notice on higher spec'd machines. To fix the issue in this bug, watermark boosting can be disabled with the following: # echo 0 > /proc/sys/vm/watermark_boost_factor There's really no harm in doing so, because watermark boosting is an inherently broken feature... -- 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/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date:
[Kernel-packages] [Bug 1831566] Re: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset
Sorry for the late action. I made a patch (attached) adding the nitpicks we discussed above, and a couple others. Please take a look and let me know what you think. If all is well, I'll submit this all to the mailing list to be merged. ** Patch added: "0001-nvme-add-nitpicks-for-cq_cpulist-module-parameter.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+attachment/5334962/+files/0001-nvme-add-nitpicks-for-cq_cpulist-module-parameter.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831566 Title: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset Status in linux package in Ubuntu: Confirmed Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found it impossible to get rid of jitter introduced by Intel NVMe IRQs. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+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 1814231] Re: linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386
Powerpc hung on vfat stress using the 5.3.0-42.34 eoan kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/ppc64el/l/linux/20200229_025412_feca6@/log.gz -- 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/1814231 Title: linux 4.4.0-142.168 ADT test failure (ubuntu_vfat_stress): hung task on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190201_082722_4cb3e@/log.gz ubuntu_vfat_stress is causing a kernel hung task on xenial/linux i386: Started, PID 23212 Timed out waiting for stress-ng to finish Forcefully killing, PID 23212 (after 121 seconds) Found kernel warning and/or call trace: [ 3998.807995] Testing: --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3998.832802] Created loop image vfat-test-23176/vfat-image-23176.img on /dev/loop0 [ 3999.936713] ubuntu_vfat_str (23176): drop_caches: 1 [ 3999.944908] ubuntu_vfat_str (23176): drop_caches: 2 [ 3999.949450] ubuntu_vfat_str (23176): drop_caches: 3 [ 3999.967248] VFAT options: allow_utime=20 [ 3999.967299] Stress test: /tmp/autopkgtest.ytglRN/build.6Ql/src/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng --verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M --fallocate-bytes 2M --chdir 2 --rename 2 --hdd-write-size 512 [ 3999.967318] Mount point: /mnt/vfat-test-23176 [ 3999.967994] Started, PID 23212 [ 4121.902337] Timed out waiting for stress-ng to finish [ 4121.902488] Forcefully killing, PID 23212 (after 121 seconds) [ 4200.180102] INFO: task stress-ng:23229 blocked for more than 120 seconds. [ 4200.18] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.185438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.186581] stress-ng D c1214654 0 23229 1 0x0004 [ 4200.186587] c5bc9ebc 0086 c5bc9ea4 c1214654 ce0a5b00 64d56897 03a3 [ 4200.186591] 6497d7cf 03a3 d8185dc0 d239a800 c5bca000 d00ce5e0 c5bc9f08 c5bc9ec8 [ 4200.186595] c17e194d c5bc9f08 c5bc9ef0 c12146ad d239a800 c10b5340 d00ce5e4 [ 4200.186598] Call Trace: [ 4200.186608] [] ? wb_queue_work+0xe4/0xf0 [ 4200.186613] [] schedule+0x2d/0x80 [ 4200.186616] [] wb_wait_for_completion+0x4d/0x90 [ 4200.186620] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.186622] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.186624] [] sync_inodes_one_sb+0x15/0x20 [ 4200.186628] [] iterate_supers+0xcd/0xd0 [ 4200.186630] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.186632] [] sys_sync+0x3a/0xa0 [ 4200.186636] [] do_fast_syscall_32+0x9f/0x160 [ 4200.186639] [] sysenter_past_esp+0x3d/0x61 [ 4200.186641] INFO: task stress-ng:23242 blocked for more than 120 seconds. [ 4200.187628] Tainted: G OE 4.4.0-142-generic #168-Ubuntu [ 4200.188667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4200.189947] stress-ng D c1214654 0 23242 1 0x0004 [ 4200.189952] c011bebc 0086 c011bea4 c1214654 dd922680 65d2d986 03a3 [ 4200.189955] 65bb3d70 03a3 d8185dc0 cef0b200 c011c000 d00ce5e0 c011bf08 c011bec8 [ 4200.189958] c17e194d c011bf08 c011bef0 c12146ad cef0b200 c10b5340 c5bc9edc [ 4200.189962] Call Trace: [ 4200.189965] [] ? wb_queue_work+0xe4/0xf0 [ 4200.189968] [] schedule+0x2d/0x80 [ 4200.189971] [] wb_wait_for_completion+0x4d/0x90 [ 4200.189973] [] ? wake_atomic_t_function+0x70/0x70 [ 4200.189975] [] sync_inodes_sb+0x7d/0x1a0 [ 4200.189978] [] sync_inodes_one_sb+0x15/0x20 [ 4200.189980] [] iterate_supers+0xcd/0xd0 [ 4200.189983] [] ? SyS_tee+0x2a0/0x2a0 [ 4200.189985] [] sys_sync+0x3a/0xa0 [ 4200.189987] [] do_fast_syscall_32+0x9f/0x160 [ 4200.189989] [] sysenter_past_esp+0x3d/0x61 This is not a regression, different call traces or errors have been reported by older versions. To manage notifications about
[Kernel-packages] [Bug 1865493] Re: eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker
** Summary changed: - eoan/linux-oracle: -proposed tracker + eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1865493 Title: eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865111 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Monday, 02. March 2020 21:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863290 trackers: bionic/linux-oracle-5.3: bug 1865492 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865493/+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 1865438] Re: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker
** Summary changed: - eoan/linux-kvm: -proposed tracker + eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865438 Title: eoan/linux-kvm: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865111 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Monday, 02. March 2020 21:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1863283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865438/+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 1865482] Re: eoan/linux-aws: 5.3.0-1013.14 -proposed tracker
** Summary changed: - eoan/linux-aws: -proposed tracker + eoan/linux-aws: 5.3.0-1013.14 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1865482 Title: eoan/linux-aws: 5.3.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865111 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Monday, 02. March 2020 21:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1863272 trackers: bionic/linux-aws-5.3: bug 1865481 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865482/+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 1865491] Re: eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker
** Summary changed: - eoan/linux-gcp: -proposed tracker + eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1865491 Title: eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865111 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Monday, 02. March 2020 21:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863280 trackers: bionic/linux-gcp-5.3: bug 1865488 bionic/linux-gke-5.3: bug 1865490 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865491/+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 1865200] Re: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker
** Summary changed: - bionic/linux-oem: -proposed tracker + bionic/linux-oem: 4.15.0-1076.86 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- 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/1865200 Title: bionic/linux-oem: 4.15.0-1076.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865109 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Packaging phase-changed: Friday, 28. February 2020 19:43 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865200/+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 1865198] Re: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker
** Summary changed: - xenial/linux-azure: -proposed tracker + xenial/linux-azure: 4.15.0-1074.79 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865198 Title: xenial/linux-azure: 4.15.0-1074.79 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865109 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Friday, 28. February 2020 22:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1864745 trackers: trusty/linux-azure: bug 1865197 xenial/linux-azure/azure-kernel: bug 1865196 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865198/+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 1865193] Re: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1034.36 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865193 Title: bionic/linux-azure: 5.0.0-1034.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865110 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Friday, 28. February 2020 18:56 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863285 trackers: bionic/linux-azure/azure-kernel: bug 1865192 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865193/+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 1864730] Re: bionic/linux-oem: 4.15.0-1075.85 -proposed tracker
** Summary changed: - bionic/linux-oem: -proposed tracker + bionic/linux-oem: 4.15.0-1075.85 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- 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/1864730 Title: bionic/linux-oem: 4.15.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864753 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Packaging phase-changed: Wednesday, 26. February 2020 19:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864730/+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 1864741] Re: bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker
** Summary changed: - bionic/linux-oracle: -proposed tracker + bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1864741 Title: bionic/linux-oracle: 4.15.0-1035.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864753 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Wednesday, 26. February 2020 19:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863339 trackers: xenial/linux-oracle: bug 1864740 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864741/+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 1864748] Re: xenial/linux-gcp: 4.15.0-1057.61 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1057.61 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1864748 Title: xenial/linux-gcp: 4.15.0-1057.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864753 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Wednesday, 26. February 2020 19:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863347 trackers: xenial/linux-gcp/gcp-kernel: bug 1864746 xenial/linux-gcp/gke-kernel: bug 1864747 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864748/+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 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
The patch to disable PSR fixes these glitches on my XPS laptops. Marking the bug as verified. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: In Progress Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1863332] Re: linux-kvm: -proposed tracker
** Summary changed: - bionic/linux-kvm: 4.15.0-1054.54 -proposed tracker + linux-kvm: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package Assignee: Sultan Alsawaf (kerneltoast) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Sultan Alsawaf (kerneltoast) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1863332 Title: bionic/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Wednesday, 19. February 2020 17:37 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863332/+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 1863325] Re: bionic/linux-aws: 4.15.0-1061.63 -proposed tracker
** Summary changed: - bionic/linux-aws: -proposed tracker + bionic/linux-aws: 4.15.0-1061.63 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1863325 Title: bionic/linux-aws: 4.15.0-1061.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Wednesday, 19. February 2020 00:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-fips: bug 1863317 bionic/linux-aws/aws-kernel: bug 1863315 xenial/linux-aws-hwe: bug 1863320 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863325/+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 1863332] Re: bionic/linux-kvm: 4.15.0-1054.54 -proposed tracker
** Summary changed: - bionic/linux-kvm: -proposed tracker + bionic/linux-kvm: 4.15.0-1054.54 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1863332 Title: bionic/linux-kvm: 4.15.0-1054.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863350 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Saturday, 15. February 2020 04:08 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863332/+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 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
Try running the following command and reboot after: sudo bash -c "echo 'options i915 enable_psr=0' > /etc/modprobe.d/i915.conf" -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: Expired Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1862263] [NEW] test_sysctl in ubuntu_kernel_selftests fails to build on eoan
Public bug reported: test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’ 181 | .seek = 4, |^~~~ This affects all arches. Kernel 5.3.0-40.32. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Incomplete ** Tags: eoan ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Description changed: - test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’ - 181 | .seek = 4, - |^~~~ + test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’ + 181 | .seek = 4, + |^~~~ - This affects all arches. + This affects all arches. Kernel 5.3.0-40.32. -- 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/1862263 Title: test_sysctl in ubuntu_kernel_selftests fails to build on eoan Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: test_sysctl.c:181:4: error: ‘struct sysctl_test’ has no member named ‘seek’ 181 | .seek = 4, |^~~~ This affects all arches. Kernel 5.3.0-40.32. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862263/+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 1861160] Re: xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1861160 Title: xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Saturday, 01. February 2020 01:18 UTC reason: prepare-package: Pending -- version not specified trackers: xenial/linux-gcp/gcp-kernel: bug 1861158 xenial/linux-gcp/gke-kernel: bug 1861159 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861160/+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 1861156] Re: xenial/linux-azure: 4.15.0-1068.73 -proposed tracker
** Summary changed: - xenial/linux-azure: -proposed tracker + xenial/linux-azure: 4.15.0-1068.73 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1861156 Title: xenial/linux-azure: 4.15.0-1068.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861165 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 04. February 2020 01:41 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-azure: bug 1861155 xenial/linux-azure/azure-kernel: bug 1861154 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861156/+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 1861199] Re: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker
** Summary changed: - eoan/linux-aws: -proposed tracker + eoan/linux-aws: 5.3.0-1011.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1861199 Title: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Tuesday, 04. February 2020 00:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-5.3: bug 1861198 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861199/+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 1861201] Re: eoan/linux-azure: 5.3.0-1011.12 -proposed tracker
** Summary changed: - eoan/linux-azure: -proposed tracker + eoan/linux-azure: 5.3.0-1011.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1861201 Title: eoan/linux-azure: 5.3.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 04. February 2020 00:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-azure-5.3: bug 1861200 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861201/+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 1861205] Re: eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker
** Summary changed: - eoan/linux-gcp: -proposed tracker + eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1861205 Title: eoan/linux-gcp: 5.3.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 04. February 2020 00:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp-5.3: bug 1861202 bionic/linux-gke-5.3: bug 1861204 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861205/+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 1861115] Re: xenial/linux-snapdragon: 4.4.0-1133.141 -proposed tracker
** Summary changed: - xenial/linux-snapdragon: -proposed tracker + xenial/linux-snapdragon: 4.4.0-1133.141 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1861115 Title: xenial/linux-snapdragon: 4.4.0-1133.141 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861122 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Wednesday, 29. January 2020 19:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1861114 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861115/+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 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed
** Tags added: sru-20191202 -- 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/1830585 Title: cpuset_memory_spread from controllers test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: New Bug description: Test failed with: cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). <<>> tag=cpuset_memory_spread stime=1558937747 cmdline=" cpuset_memory_spread_testset.sh" contacts="" analysis=exit <<>> 100+0 records in 100+0 records out 104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected node(FilePages_For_Nodes(KB): _0: 2276 _1: 102428, Expect Nodes: 1). cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded. cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded. <<>> initiation_status="ok" duration=10 termination_type=exited termination_id=1 corefile=no cutime=364 cstime=383 <<>> ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 27 05:39 seq crw-rw 1 root audio 116, 33 May 27 05:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon May 27 06:16:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+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 1824228] Re: ept test fails in kvm_unit_tests
** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Status in linux-azure source package in Eoan: New Status in linux-kvm source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312 EPT_VLT_RD expected FAIL:
[Kernel-packages] [Bug 1859817] Re: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1859817 Title: eoan/linux-aws: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1860119' packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 16. January 2020 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1859816 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859817/+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 1845863] Re: vma05 in mm from ubuntu_ltp failed on 5.3 kernel
** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1845863 Title: vma05 in mm from ubuntu_ltp failed on 5.3 kernel Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Bug description: Test failed with: tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 Need to check if it has something to do with AppArmor startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845863/+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 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3
** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1851619 Title: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: The test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp) # selftests: net: test_blackhole_dev.sh # test_blackhole_dev: [FAIL] not ok 13 selftests: net: test_blackhole_dev.sh Need to run this manually to see what's going on there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851619/+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 1858534] Re: disco/linux-azure: 5.0.0-1029.31 -proposed tracker
** Summary changed: - disco/linux-azure: -proposed tracker + disco/linux-azure: 5.0.0-1029.31 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1858534 Title: disco/linux-azure: 5.0.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858547 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 13. January 2020 16:36 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-azure: bug 1858533 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858534/+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 1858539] Re: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker
** Summary changed: - disco/linux-gcp: -proposed tracker + disco/linux-gcp: 5.0.0-1029.30 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1858539 Title: disco/linux-gcp: 5.0.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858547 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Saturday, 11. January 2020 01:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp: bug 1858536 bionic/linux-gke-5.0: bug 1858538 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858539/+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 1858543] Re: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker
** Summary changed: - disco/linux-oracle: -proposed tracker + disco/linux-oracle: 5.0.0-1010.15 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1858543 Title: disco/linux-oracle: 5.0.0-1010.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858547 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Saturday, 11. January 2020 01:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-oracle-5.0: bug 1858542 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858543/+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 1858531] Re: disco/linux-aws: 5.0.0-1024.27 -proposed tracker
** Summary changed: - disco/linux-aws: -proposed tracker + disco/linux-aws: 5.0.0-1024.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1858531 Title: disco/linux-aws: 5.0.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1858547 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Saturday, 11. January 2020 01:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-5.0: bug 1858530 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858531/+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 1858956] Re: bionic/linux: 4.15.0-75.85 -proposed tracker
** Summary changed: - bionic/linux: -proposed tracker + bionic/linux: 4.15.0-75.85 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- 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/1858956 Title: bionic/linux: 4.15.0-75.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Friday, 10. January 2020 17:56 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-raspi2: bug 1858955 bionic/linux/pc-kernel: bug 1858952 bionic/linux/pc-lowlatency-kernel: bug 1858953 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858956/+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 1855059] Re: [Regression] 4.15.0-73.82 Can not boot ThunderX
This is the true fix for the issue: https://git.launchpad.net/~kerneltoast/+git/bionic- linux/commit/?id=4d161b28e6bd713f53d9097a6c74d3cb201c1363 -- 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/1855059 Title: [Regression] 4.15.0-73.82 Can not boot ThunderX Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: On ThunderX 1socket system. The kernel output log https://pastebin.ubuntu.com/p/35DGgPz5N4/ On ThunderX 2socket system, The kernel output log https://pastebin.ubuntu.com/p/T3fVzwxhmt/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059/+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 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
This patch fixes this issue: https://git.launchpad.net/~kerneltoast/+git /bionic-linux/commit/?id=4d161b28e6bd713f53d9097a6c74d3cb201c1363 Note that this issue is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059. -- 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/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Confirmed Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+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 1855059] Re: [Regression] 4.15.0-73.82 Can not boot ThunderX
This is caused by commit 07d6360bfefa "arm64: Do not mask out PTE_RDONLY in pte_same()" (https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/bionic/commit/?id=07d6360bfefa4a01ca6b7014f9de2e88da9edba0) -- 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/1855059 Title: [Regression] 4.15.0-73.82 Can not boot ThunderX Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Bug description: On ThunderX 1socket system. The kernel output log https://pastebin.ubuntu.com/p/35DGgPz5N4/ On ThunderX 2socket system, The kernel output log https://pastebin.ubuntu.com/p/T3fVzwxhmt/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855059/+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 1854751] Re: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1854751 Title: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Thursday, 05. December 2019 00:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854751/+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 1854751] Re: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker
** Summary changed: - eoan/linux-gcp: -proposed tracker + eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1854751 Title: eoan/linux-gcp: 5.3.0-1010.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Thursday, 05. December 2019 00:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp-5.3: bug 1854750 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854751/+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 1854749] Re: eoan/linux-azure: 5.3.0-1009.10 -proposed tracker
** Summary changed: - eoan/linux-azure: -proposed tracker + eoan/linux-azure: 5.3.0-1009.10 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1854749 Title: eoan/linux-azure: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 04. December 2019 23:55 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-azure-5.3: bug 1854747 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854749/+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 1854813] Re: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker
** Summary changed: - xenial/linux-azure: -proposed tracker + xenial/linux-azure: 4.15.0-1065.70 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1854813 Title: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 04. December 2019 19:02 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854813/+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 1820754] Re: bcache null pointer exception , recursive fault
Hi, please test the following kernel to see if the issue is fixed: https ://private-fileshare.canonical.com/~sultan/trusty-bcache-test1.tar.gz It's a tarball containing kernel .deb files. -- 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/1820754 Title: bcache null pointer exception , recursive fault Status in linux package in Ubuntu: Confirmed Bug description: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+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 1840835] Re: High power consumption using 5.0.0-25-generic
Could you please verify that disco is fixed as well? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Some Nvidia graphics card has audio function in addition to video function. When the video function is not bound to any driver, the audio function can't be runtime suspended, hence preventing the power resources from being turned off. [Fix] Allow Nvidia audio function to be runtime suspended. [Test] The user reported the fix works. [Regression Potential] Low. It only allows the audio function of discrete Nvidia GPU to be runtime suspended. Regular audio or audio function with a discrete GPU already bound to a driver are unaffected. === Original Bug Report === After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1851347] Re: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002
Jesse, could you please verify that this is fixed in -proposed? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851347 Title: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Impact == A Dell Edge Gateway 3002 user reported that `top` reports around 100% CPU usage for the libmbim-proxy process. Seen in at least 40% of their devices at some point during the last 6 months. The CPU keeps high at ~100% days or weeks, but does return back to normal without a reboot. The LTE connectivity is seemingly still working as usual. The issue starts after an EPIPE error in the syslogs: 'cdc_mbim 1-3:1.12: nonzero urb status received: -EPIPE'. == Fix == 8fec9355a968 USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse This has been in mainline kernel since 4.14. == Testcase == Connect to the LTE network and see if libmbim-proxy uses 100% after some point. == Risk of Regression == Low, since 1. Already tested by original reporter and no issue found after more than a week (usually it fails twice in a week). 2. Ignoring -EPIPE is the default behavior after 4.14. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1851347/+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 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker
** Summary changed: - eoan/linux-aws: -proposed tracker + eoan/linux-aws: 5.3.0-1008.9 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1852223 Title: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Thursday, 14. November 2019 13:28 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-aws-5.3: bug 185 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852223/+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 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker
** Summary changed: - eoan/linux-gcp: -proposed tracker + eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852227 Title: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Thursday, 14. November 2019 13:29 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+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 1850481] Re: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker
** Summary changed: - eoan/linux-gcp: -proposed tracker + eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1850481 Title: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 29. October 2019 23:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1849060 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850481/+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 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker
** Summary changed: - eoan/linux-aws: -proposed tracker + eoan/linux-aws: 5.3.0-1006.6 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Tuesday, 29. October 2019 23:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1849057 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850477/+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 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker
** Summary changed: - eoan/linux-azure: -proposed tracker + eoan/linux-azure: 5.3.0-1006.6 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 29. October 2019 23:36 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1849058 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+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 1831566] Re: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset
@mykizi-ericsson Could I get an update for my last comment? If CPU hotplugging can't be addressed then perhaps it'd be alright to just mark the new module parameter as unsafe... -- 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/1831566 Title: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset Status in linux package in Ubuntu: Confirmed Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found it impossible to get rid of jitter introduced by Intel NVMe IRQs. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+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 1831566] Re: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset
Thanks for the clarification, that makes sense to me now. It doesn't look like the patch handles CPU hotplugging though; a cpumask filled with *only* offline CPUs can be passed as a parameter, or all of the CPUs in the cpumask can be offlined after the setup is finished. This isn't a problem with the default behavior because num_possible_cpus() guarantees that there will always be at least one online CPU for the nvme queue (since the CPU hotplug code doesn't allow all CPUs to be offlined). -- 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/1831566 Title: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset Status in linux package in Ubuntu: Confirmed Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found it impossible to get rid of jitter introduced by Intel NVMe IRQs. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+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 1831566] Re: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset
It looks like the supplied patch is a no-op. A module parameter is introduced with a .set function, but the parameter does not have any write permission specified so the .set function can never execute (since userspace won't have permission to write to the module parameter file). module_param_cb(cq_cpulist, _cpulist_ops, NULL, 0); ~~^~ This 0 provided to module_param_cb() is the octal UNIX permissions argument to module_param_cb(). The correct value should be 0200 in this case, to specify write-only permission. -- 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/1831566 Title: [realtime app] not possible to redirect drivers/nvme IRQs from realtime cpuset Status in linux package in Ubuntu: Confirmed Bug description: We're running realtime application on Ubuntu 16.04 with linux-image 4.15 and found it impossible to get rid of jitter introduced by Intel NVMe IRQs. I'm providing here a patch which solved the issue for us. The realtime application is bound to isolated CPUs (one thread per CPU, nohz_full= in kernel cmdline, all IRQs moved to housekeeping CPUs), application doesn't use any linux kernel syscalls except in startup phase so we don't expect any interruptions of the application from the kernel or HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831566/+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 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 22. October 2019 20:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+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 1849046] Re: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker
** Summary changed: - xenial/linux-snapdragon: -proposed tracker + xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1849046 Title: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849051 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Monday, 21. October 2019 22:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1849045 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849046/+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 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker
** Summary changed: - xenial/linux-aws: -proposed tracker + xenial/linux-aws: 4.4.0-1097.108 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Monday, 21. October 2019 21:50 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+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