[Kernel-packages] [Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
Ah that's easy then. There is no backlight and we don't support it yet. This problem with OLED is being tracked in https://trello.com/c/JVHWYLLa/68-2004-support-adjusting-brightness-on- oled-panel -- 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/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Confirmed Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1851833/+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 1855399] [NEW] [TGL] graphics kernel support
Public bug reported: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-20.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+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 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest
Cosmic EOL, removed. -- 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/1825778 Title: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Released Bug description: The run_afpackettests will be marked as passed regardless the return value of those sub-tests in the script: running psock_tpacket test [FAIL] selftests: run_afpackettests [PASS] Fix this by changing the return value for each tests. Patch sent to upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+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 1825778] Re: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest
For Disco, it's fixed with Disco update: 5.0.17 upstream stable release. ** Changed in: linux (Ubuntu Disco) Status: New => Fix Released ** No longer affects: linux (Ubuntu Cosmic) -- 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/1825778 Title: False positive test result in run_afpackettests from net in ubuntu_kernel_selftest Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Disco: Fix Released Bug description: The run_afpackettests will be marked as passed regardless the return value of those sub-tests in the script: running psock_tpacket test [FAIL] selftests: run_afpackettests [PASS] Fix this by changing the return value for each tests. Patch sent to upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825778/+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 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
Yes it does -- 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/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Confirmed Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1851833/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
Hi @kai.heng.feng, Sure. Attaching alsa-info.txt.qXIkCLj45c ** Attachment added: "alsa-info.txt.qXIkCLj45c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+attachment/5310158/+files/alsa-info.txt.qXIkCLj45c -- 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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Confirmed Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1852752] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852752 Title: DPMS does not switch off the monitor back light on Raspberry Pi 4 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: 'xset dpms force off' blanks the screen but does not switch off the HDMI (LCD) monitor backlight. 'xset -q' shows DPMS is enabled. 'tvservice -o' does switch off the monitor. No warnings/errors related to dpms in /var/log/XOrg.0.log Not sure if this is a xorg, kernel, libxcb-dpms0 or other issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1012.14-raspi2 5.3.7 Uname: Linux 5.3.0-1012-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Nov 15 18:33:52 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:17:19:0B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) 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 N/A 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/1852752/+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 1852655] Re: kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509!
Actually Ts'o said it's unlikely a fsck is going to help. That said, I have done a fsck of the file system after a couple of the crashes. They didn't turn up any major problems. -- 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/1852655 Title: kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509! Status in linux package in Ubuntu: Confirmed Bug description: We have had this problem happen 3 times in the last 5 months. Each time it happens, soon after, processes start getting stuck in IOWAIT and eventually we have to reboot the machine to get things working again. The system was running for years without problems as a VMWare guest running Ubuntu 14.04. In 9/2018 it was upgraded to Ubuntu 16.04 with a 4.4 kernel. Then in 4/2019 we installed linux-generic-hwe-16.04 to get the 4.15 kernel and it was migrated to a hyper-v server. The first crash was logged on July 29 2019, the second on Sept 17 2019, and the most recent on Nov 1 2019. ubuntu-bug linux reports "Problem in linux-image-4.15.0-67-generic This is not an official Ubuntu package." but it is the kernel package apt received from Ubuntu's servers. Nov 1 11:33:59 localhost kernel: [520860.078388] [ cut here ] Nov 1 11:33:59 localhost kernel: [520860.078390] kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509! Nov 1 11:33:59 localhost kernel: [520860.080005] invalid opcode: [#1] SMP PTI Nov 1 11:33:59 localhost kernel: [520860.080005] Modules linked in: input_leds serio_raw intel_rapl_perf i2c_piix4 hyperv_fb joydev mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hyperv_keyboard hv_storvsc hv_utils ptp scsi_transport_fc hid hv_netvsc pps_core crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd psmouse hv_vmbus pata_acpi floppy Nov 1 11:33:59 localhost kernel: [520860.080005] CPU: 0 PID: 41 Comm: kswapd0 Not tainted 4.15.0-67-generic #76~16.04.1-Ubuntu Nov 1 11:33:59 localhost kernel: [520860.080005] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 Nov 1 11:33:59 localhost kernel: [520860.080005] EIP: clear_inode+0x88/0xb0 Nov 1 11:33:59 localhost kernel: [520860.080005] EFLAGS: 00010002 CPU: 0 Nov 1 11:33:59 localhost kernel: [520860.080005] EAX: 0002 EBX: cb4d1160 ECX: cb4d125c EDX: Nov 1 11:33:59 localhost kernel: [520860.080005] ESI: cb4d125c EDI: cb4d1218 EBP: f5cd3d98 ESP: f5cd3d90 Nov 1 11:33:59 localhost kernel: [520860.080005] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 1 11:33:59 localhost kernel: [520860.080005] CR0: 80050033 CR2: 09bdcb80 CR3: 2acfe000 CR4: 003406f0 Nov 1 11:33:59 localhost kernel: [520860.080005] DR0: DR1: DR2: DR3: Nov 1 11:33:59 localhost kernel: [520860.080005] DR6: fffe0ff0 DR7: 0400 Nov 1 11:33:59 localhost kernel: [520860.080005] Call Trace: Nov 1 11:33:59 localhost kernel: [520860.080005] ext4_clear_inode+0x17/0x80 Nov 1 11:33:59 localhost kernel: [520860.080005] ext4_evict_inode+0x94/0x560 Nov 1 11:33:59 localhost kernel: [520860.080005] evict+0xa9/0x180 Nov 1 11:33:59 localhost kernel: [520860.080005] dispose_list+0x34/0x50 Nov 1 11:33:59 localhost kernel: [520860.080005] prune_icache_sb+0x47/0x70 Nov 1 11:33:59 localhost kernel: [520860.080005] ? iput+0x1e0/0x1e0 Nov 1 11:33:59 localhost kernel: [520860.080005] super_cache_scan+0x109/0x170 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_slab.part.55+0x1bb/0x3f0 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_slab+0x3a/0x50 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_node+0xed/0x2e0 Nov 1 11:33:59 localhost kernel: [520860.080005] kswapd+0x289/0x680 Nov 1 11:33:59 localhost kernel: [520860.080005] kthread+0xd8/0x110 Nov 1 11:33:59 localhost kernel: [520860.080005] ? mem_cgroup_shrink_node+0x160/0x160 Nov 1 11:33:59 localhost kernel: [520860.080005] ? kthread_bind+0x30/0x30 Nov 1 11:33:59 localhost kernel: [520860.080005] ret_from_fork+0x2e/0x38 Nov 1 11:33:59 localhost kernel: [520860.080005] Code: c0 00 00 00 8d 93 c0 00 00 00 39 c2 75 3d c7 43 70 60 00 00 00 5b 5e 5d c3 8d 76 00 8d bc 27 00 00 00 00 0f 0b 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 Nov 1 11:33:59 localhost kernel: [520860.080005] EIP: clear_inode+0x88/0xb0 SS:ESP: 0068:f5cd3d90 Nov 1 11:33:59 localhost kernel: [520860.080005] ---[ end trace c32eec6b685002fb ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852655/+s
[Kernel-packages] [Bug 1852752] Re: DPMS does not switch off the monitor back light
Since Xorg is using the modeset driver here I think this might be an issue with the Raspberry Pi kernel driver(s) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - DPMS does not switch off the monitor back light + DPMS does not switch off the monitor back light on Raspberry Pi 4 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852752 Title: DPMS does not switch off the monitor back light on Raspberry Pi 4 Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: 'xset dpms force off' blanks the screen but does not switch off the HDMI (LCD) monitor backlight. 'xset -q' shows DPMS is enabled. 'tvservice -o' does switch off the monitor. No warnings/errors related to dpms in /var/log/XOrg.0.log Not sure if this is a xorg, kernel, libxcb-dpms0 or other issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1012.14-raspi2 5.3.7 Uname: Linux 5.3.0-1012-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Nov 15 18:33:52 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:17:19:0B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) 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 N/A 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/1852752/+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 1852837] Re: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up!
Please confirm the above update has resolved this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852837 Title: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up! Status in linux package in Ubuntu: Incomplete Bug description: Hello, I didn't exactly know which category to slected during bug report submission, but after I updated my Ubuntu 19.10 installation yesterday, whenever I press restart either through gui or terminal the system boot into blinking underscore immediately after bios post screen. Not even grub menu shows up. I have to shutdown the system, then turn it on again to fix the problem. The system boot normally from a shutdown. I have already tried clean installing Ubuntu 19.10 but the problem returned after installing the updates by executing sudo apt upgrade command! I guess this issue happens after upgrading the linux-firmware package to the latest 1.183.2 version. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..65.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:65:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 15 22:56:48 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c39caed8-873a-4a54-a075-6917258f368e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd09/25/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1852837/+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 1852837] Re: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up!
Sounds like the fix has been released then. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852837 Title: Ubuntu 19.10 boots into blinking underscore when manually restart, not even grub shows up! Status in linux package in Ubuntu: Incomplete Bug description: Hello, I didn't exactly know which category to slected during bug report submission, but after I updated my Ubuntu 19.10 installation yesterday, whenever I press restart either through gui or terminal the system boot into blinking underscore immediately after bios post screen. Not even grub menu shows up. I have to shutdown the system, then turn it on again to fix the problem. The system boot normally from a shutdown. I have already tried clean installing Ubuntu 19.10 but the problem returned after installing the updates by executing sudo apt upgrade command! I guess this issue happens after upgrading the linux-firmware package to the latest 1.183.2 version. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..65.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:65:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 15 22:56:48 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-16 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c39caed8-873a-4a54-a075-6917258f368e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2002 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2002:bd09/25/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_KBLX dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1852837/+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 1845825] Re: i2c_designware and i2c_hid failures on shutdown
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4/ -- 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/1845825 Title: i2c_designware and i2c_hid failures on shutdown Status in linux package in Ubuntu: Confirmed Bug description: 1. Using Ubuntu 19.10 2. Shutdown system 3. System get stuck at the windows with this messages: i2c_designware i2c_designware.0: controller timed out i2c_designware i2c_designware.0: controller timed out i2c_designware i2c_designware.0: controller timed out i2c_hid i2c-MSFT0001:00: failed to change power setting. i2c_designware i2c_designware.0: controller timed out It might not be related to the shutdown not happening, still that's the only clue I have. I attach the screenshot and dmesg output after the following boot. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845825/+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 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
I can see a couple of pixel-layout-related settings here: dithering depth: auto supported: auto, 6 bpc, 8 bpc dithering mode: auto supported: auto, off, static 2x2, dynamic 2x2, temporal The nouveau kernel driver provides them regardless of the attached monitor. You can tweak them with: xrandr --output DP-1 --set or similar. Though that might not help... What might help is installing the proprietary Nvidia driver instead. Have a look in: Software & Updates > Additional Drivers to install the Nvidia 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. 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.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1849419] Re: kernel panic after upgrading from 19.04 to 19.10
Removed preload and prelink from the two pc . Upgraded to 19.10. Two days running. A ok now. Preload and prelink cause the kernel panic . Please take care about this bug bacause will drive crazy everyone that Has these installed . Maybe we have to open a bugreport specific to sign out this prob ? -- 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/1849419 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Incomplete Bug description: Upgrading from 19.04 to 19.10 on two of my pc does the same thing. the upgrade is ok , boot ok, but after some time, and never the same, every app is crashing unable to reboot. i manage a reset with the pc button, but after that kernel panic and no boot. every kernel listed is having a panic. only chance after that is clonezilla and turn back to previous image 19.04 that i saved. unable to enter recovery menu. grub works bios secure boot disabled. description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 13GiB *-cpu product: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 size: 3715MHz capacity: 3900MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq *-pci description: Host bridge product: Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 09 width: 32 bits clock: 33MHz configuration: driver=ivb_uncore resources: irq:0 *-pci:0 description: PCI bridge product: Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 09 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 ioport:e000(size=4096) memory:f7e0-f7ef ioport:e000(size=268435456) *-display description: VGA compatible controller product: Turks XT [Radeon HD 6670/7670] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:27 memory:e000-efff memory:f7e2-f7e3 ioport:e000(size=256) memory:c-d *-multimedia description: Audio device product: Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:30 memory:f7e4-f7e43fff *-usb:0 description: USB controller product: 7 Series/C210 Series Chipset Family USB xHCI Host Controller vendor: Intel Corporation physical id: 14 bus info: pci@:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:25 memory:f7f0-f7f0 *-communication description: Communication controller product: 7 Series/C216 Chipset Family MEI Controller #1 vendor:
[Kernel-packages] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
Does the problem occur if you log into 'Ubuntu on Wayland' ? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. 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.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+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 1852655] Re: kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509!
Ok. Have you tried fsck as Ts'o suggested? -- 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/1852655 Title: kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509! Status in linux package in Ubuntu: Confirmed Bug description: We have had this problem happen 3 times in the last 5 months. Each time it happens, soon after, processes start getting stuck in IOWAIT and eventually we have to reboot the machine to get things working again. The system was running for years without problems as a VMWare guest running Ubuntu 14.04. In 9/2018 it was upgraded to Ubuntu 16.04 with a 4.4 kernel. Then in 4/2019 we installed linux-generic-hwe-16.04 to get the 4.15 kernel and it was migrated to a hyper-v server. The first crash was logged on July 29 2019, the second on Sept 17 2019, and the most recent on Nov 1 2019. ubuntu-bug linux reports "Problem in linux-image-4.15.0-67-generic This is not an official Ubuntu package." but it is the kernel package apt received from Ubuntu's servers. Nov 1 11:33:59 localhost kernel: [520860.078388] [ cut here ] Nov 1 11:33:59 localhost kernel: [520860.078390] kernel BUG at /build/linux-hwe-dEW6RG/linux-hwe-4.15.0/fs/inode.c:509! Nov 1 11:33:59 localhost kernel: [520860.080005] invalid opcode: [#1] SMP PTI Nov 1 11:33:59 localhost kernel: [520860.080005] Modules linked in: input_leds serio_raw intel_rapl_perf i2c_piix4 hyperv_fb joydev mac_hid ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic hid_hyperv hyperv_keyboard hv_storvsc hv_utils ptp scsi_transport_fc hid hv_netvsc pps_core crc32_pclmul pcbc aesni_intel aes_i586 crypto_simd cryptd psmouse hv_vmbus pata_acpi floppy Nov 1 11:33:59 localhost kernel: [520860.080005] CPU: 0 PID: 41 Comm: kswapd0 Not tainted 4.15.0-67-generic #76~16.04.1-Ubuntu Nov 1 11:33:59 localhost kernel: [520860.080005] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 Nov 1 11:33:59 localhost kernel: [520860.080005] EIP: clear_inode+0x88/0xb0 Nov 1 11:33:59 localhost kernel: [520860.080005] EFLAGS: 00010002 CPU: 0 Nov 1 11:33:59 localhost kernel: [520860.080005] EAX: 0002 EBX: cb4d1160 ECX: cb4d125c EDX: Nov 1 11:33:59 localhost kernel: [520860.080005] ESI: cb4d125c EDI: cb4d1218 EBP: f5cd3d98 ESP: f5cd3d90 Nov 1 11:33:59 localhost kernel: [520860.080005] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 1 11:33:59 localhost kernel: [520860.080005] CR0: 80050033 CR2: 09bdcb80 CR3: 2acfe000 CR4: 003406f0 Nov 1 11:33:59 localhost kernel: [520860.080005] DR0: DR1: DR2: DR3: Nov 1 11:33:59 localhost kernel: [520860.080005] DR6: fffe0ff0 DR7: 0400 Nov 1 11:33:59 localhost kernel: [520860.080005] Call Trace: Nov 1 11:33:59 localhost kernel: [520860.080005] ext4_clear_inode+0x17/0x80 Nov 1 11:33:59 localhost kernel: [520860.080005] ext4_evict_inode+0x94/0x560 Nov 1 11:33:59 localhost kernel: [520860.080005] evict+0xa9/0x180 Nov 1 11:33:59 localhost kernel: [520860.080005] dispose_list+0x34/0x50 Nov 1 11:33:59 localhost kernel: [520860.080005] prune_icache_sb+0x47/0x70 Nov 1 11:33:59 localhost kernel: [520860.080005] ? iput+0x1e0/0x1e0 Nov 1 11:33:59 localhost kernel: [520860.080005] super_cache_scan+0x109/0x170 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_slab.part.55+0x1bb/0x3f0 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_slab+0x3a/0x50 Nov 1 11:33:59 localhost kernel: [520860.080005] shrink_node+0xed/0x2e0 Nov 1 11:33:59 localhost kernel: [520860.080005] kswapd+0x289/0x680 Nov 1 11:33:59 localhost kernel: [520860.080005] kthread+0xd8/0x110 Nov 1 11:33:59 localhost kernel: [520860.080005] ? mem_cgroup_shrink_node+0x160/0x160 Nov 1 11:33:59 localhost kernel: [520860.080005] ? kthread_bind+0x30/0x30 Nov 1 11:33:59 localhost kernel: [520860.080005] ret_from_fork+0x2e/0x38 Nov 1 11:33:59 localhost kernel: [520860.080005] Code: c0 00 00 00 8d 93 c0 00 00 00 39 c2 75 3d c7 43 70 60 00 00 00 5b 5e 5d c3 8d 76 00 8d bc 27 00 00 00 00 0f 0b 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 Nov 1 11:33:59 localhost kernel: [520860.080005] EIP: clear_inode+0x88/0xb0 SS:ESP: 0068:f5cd3d90 Nov 1 11:33:59 localhost kernel: [520860.080005] ---[ end trace c32eec6b685002fb ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1855264] Re: Kernel upgrade 5.3.0-23 to -24 results in panic
Please test 5.3.0-25.27 in -proposed. -- 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/1855264 Title: Kernel upgrade 5.3.0-23 to -24 results in panic Status in linux package in Ubuntu: Confirmed Bug description: Dell XPS 15 7590 2019 version. Apt linux kernel update from 5.3.0-23 to 5.3-0-24 and boot failed, kernel panic. Attached file with booting with 5.3.0-24 debug display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855264/+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 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
One interesting observation is that your logs are saying that 60Hz is the preferred native mode of the monitor: [ 1165.229] (II) modeset(0): First detailed timing is preferred mode [ 1165.229] (II) modeset(0): Preferred mode is native pixel format and refresh rate ... [ 1165.229] (II) modeset(0): Printing probed modes for output DP-1 [ 1165.229] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) [ 1165.229] (II) modeset(0): Modeline "1920x1080"x144.0 356.39 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (162.0 kHz e) [ 1165.229] (II) modeset(0): Modeline "1920x1080"x120.0 297.00 1920 1968 2000 2200 1080 1083 1088 1125 +hsync +vsync (135.0 kHz e) ... Which is also shown in this list: 1920x1080 (0x48) 148.500MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x49) 356.390MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 162.00KHz v: height 1080 start 1084 end 1089 total 1125 clock 144.00Hz 1920x1080 (0x4a) 297.000MHz +HSync +VSync h: width 1920 start 1968 end 2000 total 2200 skew0 clock 135.00KHz v: height 1080 start 1083 end 1088 total 1125 clock 120.00Hz So it sounds like this might be a hardware limitation. Maybe it's changing something unusual to go above 60Hz and maybe just the Windows 10 driver is better at handling that, whatever it is. If this is a software bug then it should probably be assigned to the Linux kernel or Xorg modeset driver. Because the details of the pixel layout are only known and controllable there. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. 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.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Sun May
[Kernel-packages] [Bug 1851833] Re: [Sager Clevo notebook model PB50_70RF, RD, RC] Unable to adjust brightness of backlight
Does it have an OLED panel? -- 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/1851833 Title: [Sager Clevo notebook model PB50_70RF,RD,RC] Unable to adjust brightness of backlight Status in linux package in Ubuntu: Confirmed Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/1851833/+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 1852166] [NEW] [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
You have been subscribed to a public bug: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. 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.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro 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 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug eoan nouveau ubuntu -- [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works https://bugs.launchpad.net/bugs/1852166 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
Please update it to 5.3.0-24-generic and see if it helps. -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Information
[Kernel-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
Can you please attach alsa-info? -- 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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Confirmed Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1855380] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855380 Title: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855380/+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 1855380] Re: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK)
** Summary changed: - Touchpad not working + Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1855380 Title: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855380/+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 1855380] [NEW] Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK)
You have been subscribed to a public bug: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) https://bugs.launchpad.net/bugs/1855380 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852194] Re: The mouse does not work smoothly (shakes when moving, works with ping)
Please run these commands on the affected machine: dmesg > dmesg.txt lspci > lspci.txt lsusb > lsusb.txt And then attach all three resulting files to this bug. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - The mouse does not work smoothly (shakes when moving, works with ping) + The bluetooth mouse does not work smoothly (shakes when moving and is delayed) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1852194 Title: The bluetooth mouse does not work smoothly (shakes when moving and is delayed) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After the upgrade is installed, the bluetooth does not work smoothly (shakes when moving, works with ping) 1) Ubuntu 18.04.3 LTS 2) --- 3) The bluetooth mouse should work as smoothly as before update system 4) The bluetooth mouse doesn't work smoothly (shakes when moving, works with ping) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-26 (258 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: bionic dist-upgrade Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom contraxsuite_docker_user dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852194/+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 1852071] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Confirmed Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: New Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1852083] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852083 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement Status in linux package in Ubuntu: Fix Released Bug description: 1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't use Logitech bluetooth dongle, use built in laptop bluetooth) 2. Move cursor. Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate. Workaround: execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 --max 8` This command must be used every time the mouse is connected to the laptop (after turning on the laptop, after some time of mouse inactivity etc.). When using Logitech bluetooth dongle this problem never occurs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 14:35:49 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot open /sys/bus/pci/devices/:05:02.0/resource: No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852083/+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 1852083] [NEW] [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement
You have been subscribed to a public bug: 1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't use Logitech bluetooth dongle, use built in laptop bluetooth) 2. Move cursor. Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate. Workaround: execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 --max 8` This command must be used every time the mouse is connected to the laptop (after turning on the laptop, after some time of mouse inactivity etc.). When using Logitech bluetooth dongle this problem never occurs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 14:35:49 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot open /sys/bus/pci/devices/:05:02.0/resource: No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux (Ubuntu) Importance: Low Status: Fix Released ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement https://bugs.launchpad.net/bugs/1852083 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852071] [NEW] [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
You have been subscribed to a public bug: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys https://bugs.launchpad.net/bugs/1852071 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844430] Re: [TGL] PCIe Gen4 support
$ git describe --contains d6112f8def514e019658bcc9b57d53acdb71ca3f v4.20-rc1~128^2~14^2 ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844430 Title: [TGL] PCIe Gen4 support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description PCIe Gen4 in TGL. d6112f8def514e019658bcc9b57d53acdb71ca3f Target Release: 19.10 Target Kernel: 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1844430/+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 1854835] Re: xenial/linux: 4.4.0-171.200 -proposed tracker
** Description changed: 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 04. December 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1854833 trusty/linux-lts-xenial: bug 1854834 + unknown/unknown: bug 1854820 xenial/linux-aws: bug 1854824 xenial/linux-cascade: bug 1854825 xenial/linux-fips: bug 1854832 xenial/linux-kvm: bug 1854826 xenial/linux-raspi2: bug 1854829 xenial/linux-snapdragon: bug 1854831 xenial/linux/caracalla-kernel: bug 1854820 xenial/linux/pc-kernel: bug 1854821 xenial/linux/stlouis-kernel: bug 1854822 variant: debs -- 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/1854835 Title: xenial/linux: 4.4.0-171.200 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux 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 -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 04. December 2019 14:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1854833 trusty/linux-lts-xenial: bug 1854834 unknown/unknown: bug 1854820 xenial/linux-aws: bug 1854824 xenial/linux-cascade: bug 1854825 xenial/linux-fips: bug 1854832 xenial/linux-kvm: bug 1854826 xenial/linux-raspi2: bug 1854829 xenial/linux-snapdragon: bug 1854831 xenial/linux/caracalla-kernel: bug 1854820 xenial/linux/pc-kernel: bug 1854821 xenial/linux/stlouis-kernel: bug 1854822 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854835/+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 1851715] Re: Screen brightness adjustment delay in Xorg sessions only
** Summary changed: - Screen brightness adjustment delay + Screen brightness adjustment delay in Xorg sessions only ** Package changed: linux (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Confirmed => New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851715 Title: Screen brightness adjustment delay in Xorg sessions only Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Every time I adjust my laptop's screen brightness using the dedicated brightness keys, there is a substantial delay between when I press the button and the screen adjusts. Sometimes it even "twitches" and decreasing the brightness by tapping the button two times will quickly drop the brightness all the way to the lowest setting after the delay takes place. I've noticed the issue in the default Ubuntu session and in my current vanilla gnome-session. It also doesn't matter which extensions I have installed. The keys work flawlessly in Windows so it isn't a hardware issue. I have been meaning to report this for a while and have just never gotten around to it until just now. 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Nov 7 14:37:43 2019 DistUpgraded: 2019-10-21 20:16:37,104 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] Subsystem: Huawei Technologies Co., Ltd. GP108M [GeForce MX150] [19e5:3e04] InstallationDate: Installed on 2019-09-08 (59 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=75fe2138-1abd-47b2-a73f-83280ff782ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-22 (16 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M14 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M14 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C128 dmi.product.version: M14 dmi.sys.vendor: HUAWEI 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 19.2.1-1ubuntu1 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/mutter/+bug/1851715/+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 1854114] Re: My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435
** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1854114 Title: My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Here's what happened: I have Ubuntu 19.10 installed + NVIDIA driver 340 + 4K screen. Everything works file. I upgraded my NVIDIA driver to 435 and then everything is still fine until the login screen. When I enter my password, the screen goes black. So, I connected my old HD monitor, rebooted, and it worked! Funny thing is that, when I'm logged in the OS, if I reconnect my 4K monitor, it works! But if I restart my system, the problem persists. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 26 19:21:07 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-23-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-22-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2019-10-18 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=ab778d32-5ce1-4c38-a14e-2024d96eb5d3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A32 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA32:bd09/24/2019:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/nvidia-graphics-drivers-435/+bug/1854114/+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 1852001] Re: GUI freeze on high disk IO, but disabling swap fixes it
Also please run this when the problem is happening: ps auxw > processes.txt and attach the file to this bug. ** Tags added: performance -- 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/1852001 Title: GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Incomplete Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 19.2.1-1ubuntu1 version.xser
[Kernel-packages] [Bug 1852001] Re: GUI freeze on high disk or CPU load, but disabling swap fixes it
Which GUI are you using that exhibits the problem? ** Summary changed: - Xorg freeze on high disk or cpu load or random + GUI freeze on high disk or CPU load, but disabling swap fixes it ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - GUI freeze on high disk or CPU load, but disabling swap fixes it + GUI freeze on high disk IO, but disabling swap fixes it -- 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/1852001 Title: GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Incomplete Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default s
[Kernel-packages] [Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
If that's the same fix as discussed above then there are three problems: 1. It's not a fix for this bug. It should not be linked to this bug. 2. It's been proposed to eoan without going to focal first. 3. I no longer have any eoan systems handy to test it. That can be remedied easily but see 1 and 2. -- 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/1836858 Title: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Committed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836858/+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 1852001] [NEW] GUI freeze on high disk or CPU load, but disabling swap fixes it
You have been subscribed to a public bug: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 19.2.1-1ubuntu1 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan false-gpu-hang freeze ubuntu -- GUI freeze on high disk or CPU load, but disabling swap fixes it https://bugs.launchpad.net/bugs/185200
[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: 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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+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 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1810 -- 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/1799393 Title: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: == SRU Justification == The requested commit fixes a regression introduce by mainline commit 3a2f70331226, in v4.18-rc1. The commit is only needed in Cosmic. Do to the regression, A Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core) == Fix == 37fdffb217a4 ("net/mlx5: WQ, fixes for fragmented WQ buffers API") == Regression Potential == Low. This commit has been cc'd to stable, so it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Michael Ranweiler - 2018-10-18 11:34:40 == ---Problem Description--- At the system if u do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 Will see that rx side is hitting issue. ---Additional Hardware Info--- Mellanox CX5 Ethernet 100G lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Using a CX5 Ethernet 100G card lspci 0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] just configure IP ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up then partner system configure IP and then try ping -f ping -f 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 5413 packets transmitted, 5373 received, 0% packet loss, time 934ms rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms # ping 33.33.33.33 PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data. ^C --- 33.33.33.33 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1071ms then at the recv system then do ethtool -S enP48p1s0f0 | grep wqe_err rx_wqe_err: 1 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 1 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 rx11_wqe_err: 0 rx12_wqe_err: 0 rx13_wqe_err: 0 rx14_wqe_err: 0 rx15_wqe_err: 0 you will see rx_wqe_err with a counter non-zero. This is fixed by this patch: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0 == Comment: #1 - Carol L. Soto - 2018-10-18 11:46:00 == I did a git clone to the cosmic tree and loaded the kernel in a system. kernel 4.18.12 and I can recreate it. lspci | grep Mell | grep ConnectX-5 :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] 0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] :~# ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 2 rx0_wqe_err: 1 rx1_wqe_err: 1 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0 rx8_wqe_err: 0 rx9_wqe_err: 0 rx10_wqe_err: 0 ... Let me check if the proposed patch needs backport or not. == Comment: #3 - Carol L. Soto - 2018-10-18 13:34:46 == I was able to apply the proposed patch as it to the cosmic git tree and no issue. (no need to backport) using a kernel 4.18.12+. With the proposed patch I do not see wqe err and ping does not stop. ethtool -S enp1s0f0 | grep wqe_err rx_wqe_err: 0 rx0_wqe_err: 0 rx1_wqe_err: 0 rx2_wqe_err: 0 rx3_wqe_err: 0 rx4_wqe_err: 0 rx5_wqe_err: 0 rx6_wqe_err: 0 rx7_wqe_err: 0
[Kernel-packages] [Bug 1849720] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310075/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
[Kernel-packages] [Bug 1849720] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310077/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 2
[Kernel-packages] [Bug 1849720] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310076/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui
[Kernel-packages] [Bug 1849720] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310072/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/
[Kernel-packages] [Bug 1849720] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310073/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.
[Kernel-packages] [Bug 1849720] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310074/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:192
[Kernel-packages] [Bug 1849720] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310079/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:
[Kernel-packages] [Bug 1849720] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310078/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 2
[Kernel-packages] [Bug 1849720] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310067/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1
[Kernel-packages] [Bug 1849720] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310069/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22
[Kernel-packages] [Bug 1849720] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310070/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22
[Kernel-packages] [Bug 1849720] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310065/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
[Kernel-packages] [Bug 1849720] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310071/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:192
[Kernel-packages] [Bug 1849720] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310066/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22
[Kernel-packages] [Bug 1849720] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1849720/+attachment/5310068/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
[Kernel-packages] [Bug 1849720] apport information
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: trixy 2281 F pulseaudio /dev/snd/controlC0: trixy 2281 F pulseaudio /dev/snd/pcmC0D8p: trixy 2281 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-05 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: qemu (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=147e6b06-3c63-4fc0-847a-2bfdea6d3636 ro quiet splash iommu=pt iommu=1 amd_iommu=on vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.62 dmi.board.name: X570 AQUA dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. 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:bvnAmericanMegatrendsInc.:bvrP1.62:bd11/18/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570AQUA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- 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/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 2
[Kernel-packages] [Bug 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker
This bug was fixed in the package linux-azure - 5.3.0-1008.9 --- linux-azure (5.3.0-1008.9) eoan; urgency=medium * eoan/linux-azure: 5.3.0-1008.9 -proposed tracker (LP: #1852225) [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() - btrfs: silence maybe-uninitialized warning in clone_range - arm64: armv8_deprecated: Checking return value for memory allocation - sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision - sched/vtime: Fix guest/system mis-accounting on task switch - perf/core: Rework memory accounting in perf_mmap() - perf/core: Fix corner case in perf_rotate_context() - perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp - drm/amdgpu: fix memory leak - iio: imu: adis16400: release allocated memory on failure - iio: imu: adis16400: fix memory leak - iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller - MIPS: include: Mark __xchg as __always_inline - MIPS: fw: sni: Fi
[Kernel-packages] [Bug 1849058] Re: eoan/linux-azure: 5.3.0-1005.5 -proposed tracker
*** This bug is a duplicate of bug 1850480 *** https://bugs.launchpad.net/bugs/1850480 This bug was fixed in the package linux-azure - 5.3.0-1008.9 --- linux-azure (5.3.0-1008.9) eoan; urgency=medium * eoan/linux-azure: 5.3.0-1008.9 -proposed tracker (LP: #1852225) [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() - btrfs: silence maybe-uninitialized warning in clone_range - arm64: armv8_deprecated: Checking return value for memory allocation - sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision - sched/vtime: Fix guest/system mis-accounting on task switch - perf/core: Rework memory accounting in perf_mmap() - perf/core: Fix corner case in perf_rotate_context() - perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp - drm/amdgpu: fix memory leak - iio: imu: adis16400: release allocated memory on failure - iio: imu: adis16400: fix memory leak - iio: imu: st_lsm6dsx: fix waitime for st_lsm6ds
[Kernel-packages] [Bug 1848632] Re: eoan/linux-azure: 5.3.0-1004.4 -proposed tracker
This bug was fixed in the package linux-azure - 5.3.0-1008.9 --- linux-azure (5.3.0-1008.9) eoan; urgency=medium * eoan/linux-azure: 5.3.0-1008.9 -proposed tracker (LP: #1852225) [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() - btrfs: silence maybe-uninitialized warning in clone_range - arm64: armv8_deprecated: Checking return value for memory allocation - sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision - sched/vtime: Fix guest/system mis-accounting on task switch - perf/core: Rework memory accounting in perf_mmap() - perf/core: Fix corner case in perf_rotate_context() - perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp - drm/amdgpu: fix memory leak - iio: imu: adis16400: release allocated memory on failure - iio: imu: adis16400: fix memory leak - iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller - MIPS: include: Mark __xchg as __always_inline - MIPS: fw: sni: Fi
[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
This bug was fixed in the package linux-azure - 5.3.0-1008.9 --- linux-azure (5.3.0-1008.9) eoan; urgency=medium * eoan/linux-azure: 5.3.0-1008.9 -proposed tracker (LP: #1852225) [ Ubuntu: 5.3.0-24.26 ] * eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232) * Eoan update: 5.3.9 upstream stable release (LP: #1851550) - io_uring: fix up O_NONBLOCK handling for sockets - dm snapshot: introduce account_start_copy() and account_end_copy() - dm snapshot: rework COW throttling to fix deadlock - Btrfs: fix inode cache block reserve leak on failure to allocate data space - btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents() - iio: adc: meson_saradc: Fix memory allocation order - iio: fix center temperature of bmc150-accel-core - libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature - perf tests: Avoid raising SEGV using an obvious NULL dereference - perf map: Fix overlapped map handling - perf script brstackinsn: Fix recovery from LBR/binary mismatch - perf jevents: Fix period for Intel fixed counters - perf tools: Propagate get_cpuid() error - perf annotate: Propagate perf_env__arch() error - perf annotate: Fix the signedness of failure returns - perf annotate: Propagate the symbol__annotate() error return - perf annotate: Fix arch specific ->init() failure errors - perf annotate: Return appropriate error code for allocation failures - perf annotate: Don't return -1 for error when doing BPF disassembly - staging: rtl8188eu: fix null dereference when kzalloc fails - RDMA/siw: Fix serialization issue in write_space() - RDMA/hfi1: Prevent memory leak in sdma_init - RDMA/iw_cxgb4: fix SRQ access from dump_qp() - RDMA/iwcm: Fix a lock inversion issue - HID: hyperv: Use in-place iterator API in the channel callback - kselftest: exclude failed TARGETS from runlist - selftests/kselftest/runner.sh: Add 45 second timeout per test - nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request - arm64: cpufeature: Effectively expose FRINT capability to userspace - arm64: Fix incorrect irqflag restore for priority masking for compat - arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419 - tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' - tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' - serial/sifive: select SERIAL_EARLYCON - tty: n_hdlc: fix build on SPARC - misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach - RDMA/core: Fix an error handling path in 'res_get_common_doit()' - RDMA/cm: Fix memory leak in cm_add/remove_one - RDMA/nldev: Reshuffle the code to avoid need to rebind QP in error path - RDMA/mlx5: Do not allow rereg of a ODP MR - RDMA/mlx5: Order num_pending_prefetch properly with synchronize_srcu - RDMA/mlx5: Add missing synchronize_srcu() for MW cases - gpio: max77620: Use correct unit for debounce times - fs: cifs: mute -Wunused-const-variable message - arm64: vdso32: Fix broken compat vDSO build warnings - arm64: vdso32: Detect binutils support for dmb ishld - serial: mctrl_gpio: Check for NULL pointer - serial: 8250_omap: Fix gpio check for auto RTS/CTS - arm64: Default to building compat vDSO with clang when CONFIG_CC_IS_CLANG - arm64: vdso32: Don't use KBUILD_CPPFLAGS unconditionally - efi/cper: Fix endianness of PCIe class code - efi/x86: Do not clean dummy variable in kexec path - MIPS: include: Mark __cmpxchg as __always_inline - riscv: avoid kernel hangs when trapped in BUG() - riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() - riscv: Correct the handling of unexpected ebreak in do_trap_break() - x86/xen: Return from panic notifier - ocfs2: clear zero in unaligned direct IO - fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock() - fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc() - btrfs: silence maybe-uninitialized warning in clone_range - arm64: armv8_deprecated: Checking return value for memory allocation - sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision - sched/vtime: Fix guest/system mis-accounting on task switch - perf/core: Rework memory accounting in perf_mmap() - perf/core: Fix corner case in perf_rotate_context() - perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp - drm/amdgpu: fix memory leak - iio: imu: adis16400: release allocated memory on failure - iio: imu: adis16400: fix memory leak - iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller - MIPS: include: Mark __xchg as __always_inline - MIPS: fw: sni: Fi
[Kernel-packages] [Bug 1854813] Re: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker
** Description changed: 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: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 21:12 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs -- 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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 21:12 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued 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 1854793] Re: bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker
** Description changed: 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: 1854819 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 03. December 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854792 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854793 Title: bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 03. December 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854792 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854793/+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 1724120] Re: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured
*** This bug is a duplicate of bug 1706247 *** https://bugs.launchpad.net/bugs/1706247 ** Tags removed: targetmilestone-inin16043 ** Tags added: targetmilestone-inin1804 -- 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/1724120 Title: Ubuntu 16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: Issue: Call traces occurs when memory-hotplug script is run with 16Gb hugepages configured. Environment: ppc64le PowerVM Lpar root@ltctuleta-lp1:~# uname -r 4.4.0-34-generic root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge AnonHugePages: 0 kB HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@ltctuleta-lp1:~# free -h totalusedfree shared buff/cache available Mem:85G 32G 52G 16M193M 52G Swap: 43G 0B 43G Steps to reproduce: 1 - Download kernel source and enter to the directory- tools/testing/selftests/memory-hotplug/ 2 - Run mem-on-off-test.sh script in it. System gives call traces like: offline_memory_expect_success 639: unexpected fail online-offline 668 [ 57.552964] Unable to handle kernel paging request for data at address 0x0028 [ 57.552977] Faulting instruction address: 0xc029bc04 [ 57.552987] Oops: Kernel access of bad area, sig: 11 [#1] [ 57.552992] SMP NR_CPUS=2048 NUMA pSeries [ 57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel rtc_generic mdio libcrc32c [ 57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 4.4.0-34-generic #53-Ubuntu [ 57.553059] task: c0072773c8e0 ti: c0072778 task.ti: c0072778 [ 57.553067] NIP: c029bc04 LR: c029bbdc CTR: c01107f0 [ 57.553076] REGS: c00727783770 TRAP: 0300 Not tainted (4.4.0-34-generic) [ 57.553083] MSR: 80019033 CR: 24242882 XER: 0002 [ 57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 SOFTE: 1 GPR00: c029bbdc c007277839f0 c15b5d00 GPR04: 0029d000 0800 fa01 GPR08: fa700020 0008 c185e270 c00e7e50 GPR12: 2200 ce6ea200 0029d000 2200 GPR16: 1000 c15e2200 0a70 GPR20: 0001 0100 0200 c15f16d0 GPR24: c1876510 0001 c1872a00 GPR28: 0029d000 f000 fa70 0029c000 [ 57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220 [ 57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 [ 57.553226] Call Trace: [ 57.553231] [c007277839f0] [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 (unreliable) [ 57.553244] [c00727783a80] [c02dcbc8] __offline_pages.constprop.6+0x3f8/0x900 [ 57.553254] [c00727783bd0] [c06fbb38] memory_subsys_offline+0xa8/0x110 [ 57.553265] [c00727783c00] [c06d6424] device_offline+0x104/0x140 [ 57.553274] [c00727783c40] [c06fba80] store_mem_state+0x180/0x190 [ 57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0 [ 57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0 [ 57.553302] [c00727783d00] [c0397028] kernfs_fop_write+0x188/0x200 [ 57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0 [ 57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230 [ 57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110 [ 57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4 [ 57.553346] Instruction dump: [ 57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 fabe0020 [ 57.553366] fade0028 79294620 79291764 7d234a14 3908 f9030028 81091458 [ 57.553383] ---[ end trace 617f7bdd75bcfc10 ]--- [ 57.557133] Segmentation fault The following commit IDs were built into a 4.10.0-37-generic #41 test kernel and verified to fix the problem: a525108cf1cc14651602d678da38fa627a76a724 e1073d1e7920946ac4776a619cc40668b9e1401b 40692eb5eea209c2dd55857f44b4e1d7206e91d6 e24a1307ba1f99fc62a0bd61d5e87f
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
Super! Thanks for your effort Hui, Brian, and anybody else who worked on this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1784659] Re: P9 PMU Events Update #5
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1904 -- 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/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+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 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: 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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Promote to Proposed - phase-changed: Thursday, 05. December 2019 17:57 UTC + phase: Testing + phase-changed: Thursday, 05. December 2019 22:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- 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/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+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
Re: [Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
On Thu, Dec 05, 2019 at 10:20:31PM -, Stephan van Ingen wrote: > I find in the main download pages > (http://cdimage.ubuntu.com/releases/19.10/release) "ubuntu-19.10.1 > -preinstalled-server-arm64+raspi3.img.xz" of date Dec3 (16:50) - does > that build include this bug-correction? Yes it does. -- Brian Murray -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1853369] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1853369 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: Incomplete Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Po
[Kernel-packages] [Bug 1855186] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855186 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855186 Title: Trackpad scrolling and taps not working on resume Status in linux package in Ubuntu: Incomplete Bug description: Lenovo Thinkpad T480 Ubuntu 18.04.03 On resume (e.g. after closing and then opening lid), the track pad will no longer allow me to scroll, tap or drag. The problem can be temporarily resolved by entering the following commands into the terminal... sudo modprobe -r psmouse && sudo modprobe psmouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+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 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
** Changed in: nouveau Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #100 https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/100 -- 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/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash Status in Nouveau Xorg driver: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: CID: 201305-13527 Dell Precision M4800 Xorg would crash and restart (you will see the login screen again and again) when the HDMI / DP cable is connected to the system. Steps: 1. Install 14.04 + update (3.13.0-36), boot to desktop 2. Connect a HDMI / DP cable Expected result: * The external monitor should work Actual result: * The external monitor screen is black, and the Xorg crashed -> black screen on this laptop -> login screen shows up -> black screen... repeat. WORKAROUND: * Install the proprietary nvidia driver I'm not sure if this should be consider as a blocker. But hey, we need to certified this I+N system with the proprietary driver, I think it's OK to not to call this a blocker. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio /dev/snd/controlC1: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 06:20:44 2014 HibernationDevice: RESUME=UUID=46ed949d-eff8-48e9-b337-6425f480cf12 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e7f55d08-44a4-447e-8fc6-563864d60df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+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 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
There are two upstream commits that make the SOF and SST drivers mutually exclusive on a specific platform. The one for Broadwell is now merged into the Ubuntu kernel: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/commit/?id=d46917958a6366f3c63501e9962b60dd7d33a3bd But the matching one for Baytrail is missing. It should be merged as well: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=df7257e544faf838c3e7ad6b4e89ffe59e87f5e1 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in HWE Next: Confirmed Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: New Bug description: [Impact] With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT is set to Y, then it will make the legacy intel soc driver fail, and moreover the current sof driver can't support broadwell well, as a result, many broadwell computers with I2S codec can't support sound anymore. [Fix] Intel submitted a patch, it will make those two kconfig options exclusive, and the legacy soc's option has higher priority, if both of them are enabled, sof's option will be disabled. [Test Case] Build the kernel and check the debian/build/$buidling_dir/.config, the SND_SOC_SOF_BROADWELL_SUPPORT is disabled. [Regression Risk] Low, so far, the sof driver can't support broadwell machine well, so there is no machine use this driver yet. Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs -- 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/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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 prepare-package-signed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+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 1855186] Re: Trackpad scrolling and taps not working on resume
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: bionic -- 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/1855186 Title: Trackpad scrolling and taps not working on resume Status in linux package in Ubuntu: New Bug description: Lenovo Thinkpad T480 Ubuntu 18.04.03 On resume (e.g. after closing and then opening lid), the track pad will no longer allow me to scroll, tap or drag. The problem can be temporarily resolved by entering the following commands into the terminal... sudo modprobe -r psmouse && sudo modprobe psmouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855186/+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 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" Status in linux package in Ubuntu: New Bug description: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Information
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
I find in the main download pages (http://cdimage.ubuntu.com/releases/19.10/release) "ubuntu-19.10.1 -preinstalled-server-arm64+raspi3.img.xz" of date Dec3 (16:50) - does that build include this bug-correction? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1378744]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video- nouveau/issues/100. -- 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/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash Status in Nouveau Xorg driver: Unknown Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: CID: 201305-13527 Dell Precision M4800 Xorg would crash and restart (you will see the login screen again and again) when the HDMI / DP cable is connected to the system. Steps: 1. Install 14.04 + update (3.13.0-36), boot to desktop 2. Connect a HDMI / DP cable Expected result: * The external monitor should work Actual result: * The external monitor screen is black, and the Xorg crashed -> black screen on this laptop -> login screen shows up -> black screen... repeat. WORKAROUND: * Install the proprietary nvidia driver I'm not sure if this should be consider as a blocker. But hey, we need to certified this I+N system with the proprietary driver, I think it's OK to not to call this a blocker. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-36-generic 3.13.0-36.63 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio /dev/snd/controlC1: ubuntu 7071 F pulseaudio ubuntu 7529 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Oct 8 06:20:44 2014 HibernationDevice: RESUME=UUID=46ed949d-eff8-48e9-b337-6425f480cf12 InstallationDate: Installed on 2014-10-08 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=e7f55d08-44a4-447e-8fc6-563864d60df4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-36-generic N/A linux-backports-modules-3.13.0-36-generic N/A linux-firmware 1.127.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+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 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid 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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Thursday, 05. December 2019 21:01 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+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 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Thursday, 05. December 2019 21:01 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+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 1855186] [NEW] Trackpad scrolling and taps not working on resume
You have been subscribed to a public bug: Lenovo Thinkpad T480 Ubuntu 18.04.03 On resume (e.g. after closing and then opening lid), the track pad will no longer allow me to scroll, tap or drag. The problem can be temporarily resolved by entering the following commands into the terminal... sudo modprobe -r psmouse && sudo modprobe psmouse ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Trackpad scrolling and taps not working on resume https://bugs.launchpad.net/bugs/1855186 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853369] [NEW] [19.10] Boot hangs at "loading initial ramdisk"
You have been subscribed to a public bug: [19.10] Boot hangs at "loading initial ramdisk" So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic). Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10): acpi=off dis_ucode_ldr disabling secure boot recovery mode making sure all packages are up to date I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?) I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system. Hardware Dell XPS 9550 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 91 structures occupying 5683 bytes. Table at 0x000E. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 1.11.2 Release Date: 07/30/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.11 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: XPS 15 9550 Version: Not Specified Serial Number: 5QRHRF2 UUID: 4c4c4544-0051-5210-8048-b5c04f524632 Wake-up Type: Power Switch SKU Number: 06E4 Family: XPS Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0N7TVV Version: A01 Serial Number: /5QRHRF2/CN129636CS0026/ Asset Tag: Not Specified Features: Board is a hosting board Board is replaceable Location In Chassis: Not Specified Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Dell Inc. Type: Laptop Lock: Not Present Version: Not Specified Serial Number: 5QRHRF2 Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Laptop Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSB2 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JUSBC1 Internal Connector Type: None External Reference Designator: USB TYPEC External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JHDMI1 Internal Connector Type: None External Reference Designator: HDMI External Connector Type: Other Port Type: Video Port Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: JCR Internal Connector Type: None External Reference Designator: CARD READER
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Thursday, 05. December 2019 20:52 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure: bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+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 1855341] [NEW] CONFIG_USELIB should be disabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855341 Title: CONFIG_USELIB should be disabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855341/+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 1855340] [NEW] CONFIG_HARDENED_USERCOPY_FALLBACK should be disabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855340 Title: CONFIG_HARDENED_USERCOPY_FALLBACK should be disabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855340/+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 1855342] [NEW] CONFIG_SLAB_MERGE_DEFAULT should be disabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855342 Title: CONFIG_SLAB_MERGE_DEFAULT should be disabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855342/+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 1855339] [NEW] CONFIG_LEGACY_PTYS should be disabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855339 Title: CONFIG_LEGACY_PTYS should be disabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855339/+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 1855337] [NEW] CONFIG_DEBUG_NOTIFIERS should be enabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855337 Title: CONFIG_DEBUG_NOTIFIERS should be enabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855337/+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 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Description changed: 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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 17:57 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- 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/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~16.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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 17:57 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854807/+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 1855334] [NEW] CONFIG_DEBUG_LIST should be enabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855334 Title: CONFIG_DEBUG_LIST should be enabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855334/+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 1855177] Re: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create-namespace namespace1.0 might fail
>From comment #5, i was able to make changes persistent with access='shared': /tmp/.nbdpath1.2898617 1048576 0 256 so now backing files are updated (and can even be shared among 2 vms). -- 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/1855177 Title: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create- namespace namespace1.0 might fail Status in linux package in Ubuntu: Fix Released Status in ndctl package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Status in ndctl source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Bug description: I got a probe error for pfn1.0 (from both pfn0.0 and pfn1.0) when dealing with ndctl: [11257.765457] memory add fail, invalid altmap [11257.765489] WARNING: CPU: 6 PID: 5680 at arch/x86/mm/init_64.c:852 add_pages+0x5d/0x70 [11257.765489] Modules linked in: nls_iso8859_1 edac_mce_amd crct10dif_pclmul crc32_pclmul dax_pmem_compat device_dax dax_pmem_core nd_pmem nd_btt ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper input_leds joydev mac_hid nfit serio_raw qemu_fw_cfg sch_fq_codel ip_tables x_tables autofs4 virtio_net net_failover psmouse failover pata_acpi virtio_blk i2c_piix4 floppy [11257.765505] CPU: 6 PID: 5680 Comm: ndctl Not tainted 5.3.0-24-generic #26-Ubuntu [11257.765505] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [11257.765507] RIP: 0010:add_pages+0x5d/0x70 [11257.765509] Code: 33 c2 01 76 20 48 89 15 99 33 c2 01 48 89 15 a2 33 c2 01 48 c1 e2 0c 48 03 15 97 96 39 01 48 89 15 48 0e c2 01 5b 41 5c 5d c3 <0f> 0b eb ba 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 [11257.765509] RSP: 0018:a360c09dfbf0 EFLAGS: 00010282 [11257.765510] RAX: ffea RBX: 0017ffe0 RCX: [11257.765511] RDX: RSI: 8acb7db17448 RDI: 8acb7db17448 [11257.765512] RBP: a360c09dfc00 R08: 8acb7db17448 R09: 0004 [11257.765512] R10: R11: 0001 R12: 0003fe20 [11257.765513] R13: 0001 R14: a360c09dfc48 R15: 8acb7a7226f8 [11257.765515] FS: 7febc9fd6bc0() GS:8acb7db0() knlGS: [11257.765516] CS: 0010 DS: ES: CR0: 80050033 [11257.765517] CR2: 55eec8aab398 CR3: 00013a8fa000 CR4: 000406e0 [11257.765519] Call Trace: [11257.765523] arch_add_memory+0x41/0x50 [11257.765525] devm_memremap_pages+0x47c/0x640 [11257.765529] pmem_attach_disk+0x173/0x610 [nd_pmem] [11257.765531] ? devm_memremap+0x67/0xa0 [11257.765532] nd_pmem_probe+0x7f/0xa0 [nd_pmem] [11257.765542] nvdimm_bus_probe+0x6b/0x170 [11257.765547] really_probe+0xfb/0x3a0 [11257.765549] driver_probe_device+0x5f/0xe0 [11257.765550] device_driver_attach+0x5d/0x70 [11257.765551] bind_store+0xd3/0x110 [11257.765553] drv_attr_store+0x24/0x30 [11257.765554] sysfs_kf_write+0x3e/0x50 [11257.76] kernfs_fop_write+0x11e/0x1a0 [11257.765557] __vfs_write+0x1b/0x40 [11257.765558] vfs_write+0xb9/0x1a0 [11257.765559] ksys_write+0x67/0xe0 [11257.765561] __x64_sys_write+0x1a/0x20 [11257.765567] do_syscall_64+0x5a/0x130 [11257.765693] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [11257.765696] RIP: 0033:0x7febc9e81327 [11257.765698] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [11257.765698] RSP: 002b:7ffd599433f8 EFLAGS: 0246 ORIG_RAX: 0001 [11257.765699] RAX: ffda RBX: 7febc9fd6ae8 RCX: 7febc9e81327 [11257.765700] RDX: 0007 RSI: 55eec8a9bfa0 RDI: 0004 [11257.765701] RBP: 0004 R08: 0006 R09: 7375622f7379732f [11257.765701] R10: R11: 0246 R12: 55eec8a9bfa0 [11257.765702] R13: 0001 R14: 0007 R15: 7ffd59943448 [11257.765703] ---[ end trace 442db04e33790cb5 ]--- [11257.782659] nd_pmem: probe of pfn1.0 failed with error -22 It seems that after this point I can't play with my second virtual nvdimm device (pfn1.0). A namespace destroy works but a namespace creation does not: rafaeldtinoco@ndctltest:~$ sudo ndctl list -B [ { "provider":"ACPI.NFIT", "dev":"ndbus0" } ] rafaeldtinoco@ndctltest:~$ sudo ndctl list -D [ { "dev":"nmem1", "id":"8680-57341200", "handle":2, "phys_id":0 }, { "dev":"nmem0", "id":"8680-56341200", "handle"
[Kernel-packages] [Bug 1855336] [NEW] CONFIG_DEBUG_SG should be enabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855336 Title: CONFIG_DEBUG_SG should be enabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855336/+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 1855335] [NEW] CONFIG_DEBUG_CREDENTIALS should be enabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855335 Title: CONFIG_DEBUG_CREDENTIALS should be enabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855335/+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 1855338] [NEW] CONFIG_IO_STRICT_DEVMEM should be enabled
Public bug reported: ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tyler Hicks (tyhicks) Status: 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/1855338 Title: CONFIG_IO_STRICT_DEVMEM should be enabled Status in linux package in Ubuntu: In Progress Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855338/+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 1855326] Re: Focal update: v5.4.2 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855326 Title: Focal update: v5.4.2 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.2 upstream stable release from git://git.kernel.org/ Linux 5.4.2 platform/x86: hp-wmi: Fix ACPI errors caused by passing 0 as input size platform/x86: hp-wmi: Fix ACPI errors caused by too small buffer HID: core: check whether Usage Page item is after Usage ID items crypto: talitos - Fix build error by selecting LIB_DES Revert "jffs2: Fix possible null-pointer dereferences in jffs2_add_frag_to_fragtree()" ext4: add more paranoia checking in ext4_expand_extra_isize handling r8169: fix resume on cable plug-in r8169: fix jumbo configuration for RTL8168evl selftests: pmtu: use -oneline for ip route list cache tipc: fix link name length check selftests: bpf: correct perror strings selftests: bpf: test_sockmap: handle file creation failures gracefully net/tls: use sg_next() to walk sg entries net/tls: remove the dead inplace_crypto code selftests/tls: add a test for fragmented messages net: skmsg: fix TLS 1.3 crash with full sk_msg net/tls: free the record on encryption error net/tls: take into account that bpf_exec_tx_verdict() may free the record openvswitch: remove another BUG_ON() openvswitch: drop unneeded BUG_ON() in ovs_flow_cmd_build_info() sctp: cache netns in sctp_ep_common slip: Fix use-after-free Read in slip_open sctp: Fix memory leak in sctp_sf_do_5_2_4_dupcook openvswitch: fix flow command message size net: sched: fix `tc -s class show` no bstats on class with nolock subqueues net: psample: fix skb_over_panic net: macb: add missed tasklet_kill net: dsa: sja1105: fix sja1105_parse_rgmii_delays() mdio_bus: don't use managed reset-controller macvlan: schedule bc_work even if error gve: Fix the queue page list allocated pages count x86/fpu: Don't cache access to fpu_fpregs_owner_ctx thunderbolt: Power cycle the router if NVM authentication fails mei: me: add comet point V device id mei: bus: prefix device names on bus with the bus name USB: serial: ftdi_sio: add device IDs for U-Blox C099-F9P staging: rtl8723bs: Add 024c:0525 to the list of SDIO device-ids staging: rtl8723bs: Drop ACPI device ids staging: rtl8192e: fix potential use after free staging: wilc1000: fix illegal memory access in wilc_parse_join_bss_param() usb: dwc2: use a longer core rest timeout in dwc2_core_reset() driver core: platform: use the correct callback type for bus_find_device crypto: inside-secure - Fix stability issue with Macchiatobin net: disallow ancillary data for __sys_{send,recv}msg_file() net: separate out the msghdr copy from ___sys_{send,recv}msg() io_uring: async workers should inherit the user creds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855326/+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
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: 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: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 21:12 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs -- 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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 21:12 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait 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 1855177] Re: qemu nvdimm virtualization + linux 5.3.0-24-generic kernel PROBE ERROR
This way more complex than I thought and its not so easy to address. Lets see if I can summarize the issue here. Whenever developing the regressions tests for ndctl, it occurred to me the same backtrace, over and over, when realizing the tests: [ 271.705646] memory add fail, invalid altmap [ 271.705677] WARNING: CPU: 5 PID: 886 at arch/x86/mm/init_64.c:852 add_pages+0x5d/0x70 [ 271.705679] Modules linked in: nls_iso8859_1 edac_mce_amd dax_pmem_compat nd_pmem device_dax nd_btt dax_pmem_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev aesni_intel aes_x86_64 crypto_simd input_leds cryptd glue_helper serio_raw mac_hid qemu_fw_cfg nfit sch_fq_codel ip_tables x_tables autofs4 virtio_net psmouse net_failover virtio_blk i2c_piix4 failover pata_acpi floppy [ 271.705707] CPU: 5 PID: 886 Comm: ndctl Not tainted 5.3.0-24-generic #26-Ubuntu [ 271.705709] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [ 271.705720] RIP: 0010:add_pages+0x5d/0x70 [ 271.705721] Code: 33 c2 01 76 20 48 89 15 99 33 c2 01 48 89 15 a2 33 c2 01 48 c1 e2 0c 48 03 15 97 96 39 01 48 89 15 48 0e c2 01 5b 41 5c 5d c3 <0f> 0b eb ba 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 [ 271.705722] RSP: 0018:ba02c0d2bbf0 EFLAGS: 00010282 [ 271.705723] RAX: ffea RBX: 0017ffc0 RCX: [ 271.705723] RDX: RSI: 9aaa3da97448 RDI: 9aaa3da97448 [ 271.705724] RBP: ba02c0d2bc00 R08: 9aaa3da97448 R09: 0004 [ 271.705724] R10: R11: 0001 R12: 0003fe40 [ 271.705725] R13: 0001 R14: ba02c0d2bc48 R15: 9aa975efaaf8 [ 271.705727] FS: 7f70a62d4bc0() GS:9aaa3da8() knlGS: [ 271.705728] CS: 0010 DS: ES: CR0: 80050033 [ 271.705729] CR2: 5594a0aaa158 CR3: 00013811 CR4: 000406e0 [ 271.705731] Call Trace: [ 271.705734] arch_add_memory+0x41/0x50 [ 271.705737] devm_memremap_pages+0x47c/0x640 [ 271.705740] pmem_attach_disk+0x173/0x610 [nd_pmem] [ 271.705741] ? devm_memremap+0x67/0xa0 [ 271.705743] nd_pmem_probe+0x7f/0xa0 [nd_pmem] [ 271.705745] nvdimm_bus_probe+0x6b/0x170 [ 271.705747] really_probe+0xfb/0x3a0 [ 271.705749] driver_probe_device+0x5f/0xe0 [ 271.705750] device_driver_attach+0x5d/0x70 [ 271.705751] bind_store+0xd3/0x110 [ 271.705753] drv_attr_store+0x24/0x30 [ 271.705754] sysfs_kf_write+0x3e/0x50 [ 271.705755] kernfs_fop_write+0x11e/0x1a0 [ 271.705757] __vfs_write+0x1b/0x40 [ 271.705758] vfs_write+0xb9/0x1a0 [ 271.705759] ksys_write+0x67/0xe0 [ 271.705760] __x64_sys_write+0x1a/0x20 [ 271.705762] do_syscall_64+0x5a/0x130 [ 271.705764] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 271.705765] RIP: 0033:0x7f70a6189327 [ 271.705767] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24 [ 271.705767] RSP: 002b:7ffc616998b8 EFLAGS: 0246 ORIG_RAX: 0001 [ 271.705768] RAX: ffda RBX: 7f70a62d4ae8 RCX: 7f70a6189327 [ 271.705769] RDX: 0007 RSI: 5594a0aa01a0 RDI: 0006 [ 271.705769] RBP: 0006 R08: 0006 R09: 7375622f7379732f [ 271.705770] R10: R11: 0246 R12: 5594a0aa01a0 [ 271.705770] R13: 0001 R14: 0007 R15: 7ffc61699908 [ 271.705772] ---[ end trace 7ee621e68332018c ]--- And I realized that I could NOT re-generate the SECOND namespace (the first one always worked). First I had to read about how qemu emulated nvdimms and check why namespaces were not persistent on qemu nvdimms emulation, then I had to discover why it looked like virtual nvdimms had no labels (as RAW namespaces are always created by default) and then I had to understand why the mapping was failing, to realize the real issue. First things first. ### QEMU emulated nvdimms: https://github.com/qemu/qemu/blob/master/docs/nvdimm.txt Whenever backing filesystems are not DAX capable (on a REAL NVDIMM HW, for example) then after the instance is shutdown all nvdimm data (written to the backing files) are gone. ### QEMU virtual nvdimms lack of labels: Label - QEMU v2.7.0 and later implement the label support for vNVDIMM devices. To enable label on vNVDIMM devices, users can simply add "label-size=$SZ" option to "-device nvdimm", e.g. -device nvdimm,id=nvdimm1,memdev=mem1,label-size=128K Note: 1. The minimal label size is 128KB. 2. QEMU v2.7.0 and later store labels at the end of backend storage. If a memory backend file, which was previously used as the backend of a vNVDIMM device without labels, is now used for a vNVDIMM device with label, the data in the label area at the end of file will be inaccessible to the guest. If any useful data (e.g. the meta-data of t
[Kernel-packages] [Bug 1855177] Re: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create-namespace namespace1.0 might fail
The Linux Kernel fix is here: commit 274b924088e9 Author: Jeff Moyer Date: Wed Aug 28 12:49:46 2019 libnvdimm/pfn: Fix namespace creation on misaligned addresses Yi reported[1] that after commit a3619190d62e ("libnvdimm/pfn: stop padding pmem namespaces to section alignment"), it was no longer possible to create a device dax namespace with a 1G alignment. The reason was that the pmem region was not itself 1G-aligned. The code happily skips past the first 512M, but fails to account for a now misaligned end offset (since space was allocated starting at that misaligned address, and extending for size GBs). Reintroduce end_trunc, so that the code correctly handles the misaligned end address. This results in the same behavior as before the introduction of the offending commit. [1] https://lists.01.org/pipermail/linux-nvdimm/2019-July/022813.html Fixes: a3619190d62e ("libnvdimm/pfn: stop padding pmem namespaces ...") Reported-and-tested-by: Yi Zhang Signed-off-by: Jeff Moyer Link: https://lore.kernel.org/r/x49ftll8f39@segfault.boston.devel.redhat.com Signed-off-by: Dan Williams So marking kernel as Fix Released (as this is included in Focal). ** Also affects: qemu (Ubuntu Focal) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Medium Status: Fix Released ** Also affects: ndctl (Ubuntu Focal) Importance: Medium Status: 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/1855177 Title: QEMU emulated nvdimm regions alignment need (128MB) or ndctl create- namespace namespace1.0 might fail Status in linux package in Ubuntu: Fix Released Status in ndctl package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Status in ndctl source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Bug description: I got a probe error for pfn1.0 (from both pfn0.0 and pfn1.0) when dealing with ndctl: [11257.765457] memory add fail, invalid altmap [11257.765489] WARNING: CPU: 6 PID: 5680 at arch/x86/mm/init_64.c:852 add_pages+0x5d/0x70 [11257.765489] Modules linked in: nls_iso8859_1 edac_mce_amd crct10dif_pclmul crc32_pclmul dax_pmem_compat device_dax dax_pmem_core nd_pmem nd_btt ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper input_leds joydev mac_hid nfit serio_raw qemu_fw_cfg sch_fq_codel ip_tables x_tables autofs4 virtio_net net_failover psmouse failover pata_acpi virtio_blk i2c_piix4 floppy [11257.765505] CPU: 6 PID: 5680 Comm: ndctl Not tainted 5.3.0-24-generic #26-Ubuntu [11257.765505] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 [11257.765507] RIP: 0010:add_pages+0x5d/0x70 [11257.765509] Code: 33 c2 01 76 20 48 89 15 99 33 c2 01 48 89 15 a2 33 c2 01 48 c1 e2 0c 48 03 15 97 96 39 01 48 89 15 48 0e c2 01 5b 41 5c 5d c3 <0f> 0b eb ba 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 [11257.765509] RSP: 0018:a360c09dfbf0 EFLAGS: 00010282 [11257.765510] RAX: ffea RBX: 0017ffe0 RCX: [11257.765511] RDX: RSI: 8acb7db17448 RDI: 8acb7db17448 [11257.765512] RBP: a360c09dfc00 R08: 8acb7db17448 R09: 0004 [11257.765512] R10: R11: 0001 R12: 0003fe20 [11257.765513] R13: 0001 R14: a360c09dfc48 R15: 8acb7a7226f8 [11257.765515] FS: 7febc9fd6bc0() GS:8acb7db0() knlGS: [11257.765516] CS: 0010 DS: ES: CR0: 80050033 [11257.765517] CR2: 55eec8aab398 CR3: 00013a8fa000 CR4: 000406e0 [11257.765519] Call Trace: [11257.765523] arch_add_memory+0x41/0x50 [11257.765525] devm_memremap_pages+0x47c/0x640 [11257.765529] pmem_attach_disk+0x173/0x610 [nd_pmem] [11257.765531] ? devm_memremap+0x67/0xa0 [11257.765532] nd_pmem_probe+0x7f/0xa0 [nd_pmem] [11257.765542] nvdimm_bus_probe+0x6b/0x170 [11257.765547] really_probe+0xfb/0x3a0 [11257.765549] driver_probe_device+0x5f/0xe0 [11257.765550] device_driver_attach+0x5d/0x70 [11257.765551] bind_store+0xd3/0x110 [11257.765553] drv_attr_store+0x24/0x30 [11257.765554] sysfs_kf_write+0x3e/0x50 [11257.76] kernfs_fop_write+0x11e/0x1a0 [11257.765557] __vfs_write+0x1b/0x40 [11257.765558] vfs_write+0xb9/0x1a0 [11257.765559] ksys_write+0x67/0xe0 [11257.765561] __x64_sys_write+0x1a/0x20 [11257.765567] do_syscall_64+0x5a/0x130 [11257.765693] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [11257.765696] RIP: 0033:0x7febc9e81327 [11257.765698] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c
[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Updates - phase-changed: Thursday, 05. December 2019 20:46 UTC + phase: Holding before Promote to Security + phase-changed: Thursday, 05. December 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs -- 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/1852225 Title: eoan/linux-azure: 5.3.0-1008.9 -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 prepare-package-signed 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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Fix Released 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Security phase-changed: Thursday, 05. December 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Holding -- not ready for security (replication dwell) trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+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
** Description changed: 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: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Thursday, 05. December 2019 20:59 UTC + phase: Promote to Proposed + phase-changed: Thursday, 05. December 2019 21:12 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs -- 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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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 -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Thursday, 05. December 2019 21:12 UTC reason: promote-to-proposed: Ongoing -- review in progress 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 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Updates - phase-changed: Thursday, 05. December 2019 18:52 UTC + phase: Complete + phase-changed: Thursday, 05. December 2019 21:01 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Pending -- ready to copy variant: debs -- 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/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Thursday, 05. December 2019 21:01 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+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