[Kernel-packages] [Bug 1860306] 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 1860306 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/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: Incomplete Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+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 1859724] Re: disco/linux: 5.0.0-40.44 -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: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 16. January 2020 04:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: + bionic/linux-bluefield: bug 1858546 bionic/linux-oem-osp1: bug 1859722 disco/linux-aws: bug 1858531 disco/linux-azure: bug 1858534 disco/linux-gcp: bug 1858539 disco/linux-kvm: bug 1858541 disco/linux-oracle: bug 1858543 disco/linux-raspi2: bug 1858529 disco/linux-snapdragon: bug 1858544 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/1859724 Title: disco/linux: 5.0.0-40.44 -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: 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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- 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, 16. January 2020 04:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1858546 bionic/linux-oem-osp1: bug 1859722 disco/linux-aws: bug 1858531 disco/linux-azure: bug 1858534 disco/linux-gcp: bug 1858539 disco/linux-kvm: bug 1858541 disco/linux-oracle: bug 1858543 disco/linux-raspi2: bug 1858529 disco/linux-snapdragon: bug 1858544 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859724/+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 1812822] Re: Guest crashed when detaching the ovs interface device
** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: qemu (Ubuntu) Status: Incomplete => 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/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: In Progress Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+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 1812822] Re: Guest crashed when detaching the ovs interface device
The mentioned commit 6ab79a20af3a7b3bf610ba9aebb446a9f0b05930 is in qemu 4.1 and later. Since we will have qemu 4.2 in 20.04 please retry with that once available. I'll set a bug tak reference in the changelog of the update. ** Tags removed: qemu-19.10 ** Tags added: qemu-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: In Progress Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+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 988799]
https://sportinfo.com.ng/ -- 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/988799 Title: Precise freezes under heavy i/o Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Whilst creating a VM with 20 GB persistent HD and my system froze until the disk was created. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gema 2526 F pulseaudio /dev/snd/controlC0: gema 2526 F pulseaudio /dev/snd/controlC1: gema 2526 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 52' Mixer name : 'VIA VT1708S' Components : 'HDA:11060397,104383c4,0010' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'U0x46d0x81d'/'USB Device 0x46d:0x81d at usb-:00:1d.0-1.3, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:081d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 16 Mono: Capture 12 [75%] [24.00dB] [on] Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbbfc000 irq 53' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Thu Apr 26 11:59:11 2012 HibernationDevice: RESUME=UUID=f32abdd2-8167-48c2-9d93-61eeb2632ca0 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IwConfig: lono wireless extensions. virbr0no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/zsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=109d1e55-4f64-489e-91e8-48ff46f6ba16 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-04-25 (0 days ago) dmi.bios.date: 03/26/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E LX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd03/26/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-ELX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/988799/+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 1628238]
[366338.166585] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41 [366338.166652] usbcore: registered new interface driver uvcvideo [366338.166652] USB Video Class driver (1.1.1) [366357.978516] usbcore: deregistering interface driver uvcvideo [366377.298295] usb 5-4: USB disconnect, device number 16 [366382.517118] usb 5-4: new high-speed USB device number 17 using xhci_hcd [366382.539011] usb 5-4: config 1 interface 1 altsetting 0 endpoint 0x82 has wMaxPacketSize 0, skipping [366382.539015] usb 5-4: New USB device found, idVendor=eb1a, idProduct=299f, bcdDevice= 6.09 [366382.539017] usb 5-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [366382.596668] uvcvideo: Found UVC 1.00 device (eb1a:299f) [366382.601384] uvcvideo: No streaming interface found for terminal 2. [366382.601390] uvcvideo 5-4:1.0: Entity type for entity Extension 4 was not initialized! [366382.601395] uvcvideo 5-4:1.0: Entity type for entity Processing 3 was not initialized! [366382.601397] uvcvideo 5-4:1.0: Entity type for entity Camera 1 was not initialized! [366382.601536] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input42 [366382.601624] usbcore: registered new interface driver uvcvideo [366382.601625] USB Video Class driver (1.1.1) 5.4.11-050411-generic camera worked pre kernel 4's and before going from Ubuntu 18 - 19 -- 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/1628238 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [5.525445] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [5.525452] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [5.525456] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2084 F...m pulseaudio /dev/snd/controlC0: caravena 2084 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 27 15:21:42 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (429 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1628238/+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 1860306] [NEW] Linux kernel 5.3.0-26 breaks nvidia driver
Public bug reported: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description:Linux Mint 19.3 Tricia Release:19.3 ** 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/1860306 Title: Linux kernel 5.3.0-26 breaks nvidia driver Status in linux package in Ubuntu: New Bug description: Upon installation of kernel update 5.3.0.26.95, after a reboot, Second screen would not come on and nvidia control panel was missing majority of options Graphics driver settings could not be changed and upon reinstallation attempt of nvidia driver 390, installation failed and drivers became corrupted. Ended up reinstalling OS, but discovered later that booting in an older kernel fixed the issue. VERSION.LOG: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Release: Description: Linux Mint 19.3 Tricia Release: 19.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860306/+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 1860123] Re: bionic/linux: 4.15.0-76.86 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 + bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 - xenial/linux-hwe: bug 1860122, bug 1859704 + xenial/linux-hwe: bug 1859704, bug 1860122 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/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux-raspi2: bug 1859700 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1859704, bug 1860122 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 620074]
https://sportinfo.com.ng/ -- 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/620074 Title: Thrashing turns system unusable Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Thrashing on Ubuntu seems to make it almost impossible to interact with the system. It can be minutes before any interaction has an effect, including remote connections. This means that if a program either misbehaves or simply needs more memory than available RAM, it might be hard or impossible to stop it, either locally or remotely. This can be both an annoyance and a security threat (since a process without elevated privileges can effectively hang the system). It is not hard to make a system go into thrashing, especially if it is low on memory (that's probably true in general, not only of Ubuntu). On my ASUS netbook running Ubuntu 10.04, with only 1GB RAM, thrashing can occur as easily as running both Chromium (which is a bit of a memory hog) and the Resynthesizer plugin in the GIMP at the same time. Running these programs plus another memory-intensive program like Mathematica can generate thrashing even when 2GB or 4GB of physical memory are available. I am including a short C++ program that allocates and accesses a large amount of memory, guaranteeing thrashing will occur on any system. Using this or any other memory-intensive program, the steps required to reproduce the condition I described are 1. Start one or more memory-intensive programs. 2. As RAM is filled, paging will start, and if the programs try to access the memory that has been swapped out, thrashing occurs. What happens? - Interactivity with the system drops to almost zero. Mouse barely moves, keyboard interaction has huge delays (tens of seconds), starting a terminal or switching to one if one is already open can take minutes, as is the case with remote (e.g. SSH) connections. What I would expect/want to happen? - The system should keep interactivity levels high at all times. While I'm not at all an expert on this, I would think this could be achieved by either not allowing paging out of essential user-interface elements, or more generally by giving processes that generate a lot of page faults comparatively lower priority than other processes, especially processes that are just starting, or are part of the user interface. To use the included program, compile with g++ -o bug bug.cc and run with ./bug where is the amount of memory in MB to be allocated. One can run several instances of the program at the same time, to compete for memory. One can use top, free or the System Monitor to check when RAM is completely filled, and thrashing starts. PS: This seems to be a long-standing issue with Linux, it's not limited to the current version of Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.39 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tibi 1596 F pulseaudio /dev/snd/pcmC0D0p: tibi 1596 F...m pulseaudio /dev/snd/controlC1: tibi 1596 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfe02 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,10250153,00100202 HDA:10de0002,10de0101,0010' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-:00:04.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:08da' Controls : 3 Simple ctrls : 2 Date: Wed Aug 18 13:01:30 2010 HibernationDevice: RESUME=UUID=9464cfb9-e39a-46ab-bf3a-01a7f2194ab1 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: eMachines EL1210-09 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=93f3d657-74ac-4853-acab-704f74ab4cd0 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 RfKill: SourcePackage: linux dmi.bios.date: 09/23/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: R01-A0 dmi.board.name: WMCP78M dmi.board.vendor: eMachines dmi.chassis.asset.tag: 00 dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias:
[Kernel-packages] [Bug 1858529] Re: disco/linux-raspi2: 5.0.0-1025.26 -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: '1859724' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 14. January 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858529 Title: disco/linux-raspi2: 5.0.0-1025.26 -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-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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 14. January 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- 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/1858529/+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 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -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: '1859724' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- 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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -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-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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- 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/1858544/+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 1858544] Re: disco/linux-snapdragon: 5.0.0-1029.31 -proposed tracker
Image is not ready. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858544 Title: disco/linux-snapdragon: 5.0.0-1029.31 -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-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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- 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/1858544/+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 1858529] Re: disco/linux-raspi2: 5.0.0-1025.26 -proposed tracker
No official image for this kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1858529 Title: disco/linux-raspi2: 5.0.0-1025.26 -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-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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859724' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 14. January 2020 13:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- 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/1858529/+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 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -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: In Progress 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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 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-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+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 1858588] Re: xenial/linux-snapdragon: 4.4.0-1132.140 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1858588 Title: xenial/linux-snapdragon: 4.4.0-1132.140 -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: In Progress 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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1859718' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1858587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858588/+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 1859700] Re: bionic/linux-raspi2: 4.15.0-1054.58 -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: 1859705 + kernel-stable-master-bug: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 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 1859699 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/1859700 Title: bionic/linux-raspi2: 4.15.0-1054.58 -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: In Progress 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 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 1859699 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859700/+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 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1859692 Title: eoan/linux-raspi2: 5.3.0-1017.19 -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: In Progress 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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1859694 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 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-5.3: bug 1859691 eoan/linux-raspi2/pi-kernel: bug 1859690 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859692/+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 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -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: In Progress 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 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: '1859718' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Monday, 13. January 2020 14:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+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 1859700] Re: bionic/linux-raspi2: 4.15.0-1054.58 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1859700 Title: bionic/linux-raspi2: 4.15.0-1054.58 -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: In Progress 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: '1860123' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 16. January 2020 00:31 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 1859699 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859700/+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 1860303] 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/1860303 Title: Backlight brightness cannot be adjusted using keys Status in linux package in Ubuntu: Confirmed Bug description: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaredy 1649 F pulseaudio /dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 19 19:51:45 2020 InstallationDate: Installed on 2020-01-03 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13t-aw100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13t-aw100 dmi.product.sku: 6YG70AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860303/+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 1860303] [NEW] Backlight brightness cannot be adjusted using keys
Public bug reported: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaredy 1649 F pulseaudio /dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 19 19:51:45 2020 InstallationDate: Installed on 2020-01-03 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13t-aw100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5f505587-b59b-4abd-b8f2-28c04ab84c64 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FA dmi.board.vendor: HP dmi.board.version: 87.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd11/15/2019:svnHP:pnHPSpectrex360Convertible13t-aw100:pvr:rvnHP:rn86FA:rvr87.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13t-aw100 dmi.product.sku: 6YG70AV dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Bug report following guidance on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques; https://bugs.launchpad.net/bugs/1860303/+attachment/5321620/+files/backlight%20bug%20report.tar.xz -- 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/1860303 Title: Backlight brightness cannot be adjusted using keys Status in linux package in Ubuntu: New Bug description: I cannot adjust the screen brightness using the keyboard keys or changing /sys/call/backlight/intel_backlight/brightness values. I've only been able to adjust the backlight using xrandr. Followed bug report on https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Techniques and attached files. Additional information: 1. echo 8 > /sys/class/backlight/intel_backlight/brightness does not change the screen brightness 2. video.use_bios_initial_backlight=0 does not enable brightness to be changed 3. Cannot login to when using kernel paramater acpi_osi=. Login does not work and on one boot "y"s were being continuously typed without any keys being depressed. It was odd. 4. video.use_native_backlight=1 does not enabel brightness to be changed 5. Created file /usr/share/X11/xorg.conf.d/80-backlight.conf and it had no impact ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaredy 1649 F pulseaudio /dev/snd/pcmC0D0p: jaredy 1649 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 19 19:51:45 2020 InstallationDate: Installed on 2020-01-03 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 13t-aw100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Status in backport-iwlwifi-dkms source package in Eoan: Fix Released Status in gcc-9 source package in Eoan: Won't Fix Status in linux source package in Eoan: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Confirmed Status in nvidia-graphics-drivers-430 source package in Eoan: Fix Released Status in virtualbox source package in Eoan: Won't Fix Status in xtables-addons source package in Eoan: Won't Fix Bug description: [SRU Justification for backport-iwlwifi-dkms] [Impact] FTBFS against v5.3 kernels on Eoan/Focal. [Fix] * Backport fix from upstream commit f47729b94e11 (backport: rename ktime_get_boot_ns for v5.3+). * Also updates -fcf-protection=none usage for bug 1830961. [Test Case] Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal. [Regression Risk] Low. There is no functional changes in comparison to 7906-0ubuntu1. original bug description Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+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 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 1830961 *** https://bugs.launchpad.net/bugs/1830961 ** Summary changed: - package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 + package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] ** This bug has been marked a duplicate of bug 1830961 Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 [error: ‘-mindirect-branch’ and â €˜-fcf-protection’ are not compatible] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Doing a do-release-upgrade -d from 19.04 to 19.10. The upgrade crashed out part way through, automatically reporting this bug. update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Processing triggers for menu (2.1.47ubuntu3) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (624.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 01:17:46 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-23 (531 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Status in backport-iwlwifi-dkms source package in Eoan: Fix Released Status in gcc-9 source package in Eoan: Won't Fix Status in linux source package in Eoan: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Confirmed Status in nvidia-graphics-drivers-430 source package in Eoan: Fix Released Status in virtualbox source package in Eoan: Won't Fix Status in xtables-addons source package in Eoan: Won't Fix Bug description: [SRU Justification for backport-iwlwifi-dkms] [Impact] FTBFS against v5.3 kernels on Eoan/Focal. [Fix] * Backport fix from upstream commit f47729b94e11 (backport: rename ktime_get_boot_ns for v5.3+). * Also updates -fcf-protection=none usage for bug 1830961. [Test Case] Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal. [Regression Risk] Low. There is no functional changes in comparison to 7906-0ubuntu1. original bug description Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+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 1860230] Re: Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 It appears the Nvidia-390 kernel driver doesn't support kernel 5.3 and is not loading anymore. ** Summary changed: - Resolution incorrect after updating kernel to 5.3 + Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1860230 Title: Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC 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.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 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/nvidia-graphics-drivers-390/+bug/1860230/+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 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in gcc-9 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Won't Fix Status in xtables-addons package in Ubuntu: Won't Fix Status in backport-iwlwifi-dkms source package in Eoan: Fix Released Status in gcc-9 source package in Eoan: Won't Fix Status in linux source package in Eoan: Fix Released Status in nvidia-graphics-drivers-390 source package in Eoan: Confirmed Status in nvidia-graphics-drivers-430 source package in Eoan: Fix Released Status in virtualbox source package in Eoan: Won't Fix Status in xtables-addons source package in Eoan: Won't Fix Bug description: [SRU Justification for backport-iwlwifi-dkms] [Impact] FTBFS against v5.3 kernels on Eoan/Focal. [Fix] * Backport fix from upstream commit f47729b94e11 (backport: rename ktime_get_boot_ns for v5.3+). * Also updates -fcf-protection=none usage for bug 1830961. [Test Case] Verified DKMS module build on linux-oem/linux-oem-osp1/linux-generic >= 4.10 kernels on series Xenial/Bionic/Cosmic/Disco/Eoan and Focal. [Regression Risk] Low. There is no functional changes in comparison to 7906-0ubuntu1. original bug description Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+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 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’]
** Summary changed: - nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 + nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] ** Tags added: eoan ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1851162 Title: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: With linux-image-5.0.0-23 I had no problems. Following an update linux-image-5.3.0-19 was installed, the DKMS build failed, and the system became unusable. Removing 5.3.0 brings the system back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 3 19:55:57 2019 InstallationDate: Installed on 2019-06-09 (147 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+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 1860295] Re: dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error: redefinition of ‘list_is_first’]
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 ** Summary changed: - dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 + dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error: redefinition of ‘list_is_first’] ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1860295 Title: dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error: redefinition of ‘list_is_first’] Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After the update from 5.0 to 5.3 the dkms reconfigure of the nvidia-390 kernel module fails. The problem seems to be in a conflict between the "list_is_first" routine in the module and the new kernel, which causes a compile error. I will upload /var/lib/dkms/nvidia/390.116/build/make.log The reference in the log to autoconf.h missing is spurious. The generated/autoconf.h exists. Here is the reconfigure output # dpkg-reconfigure nvidia-dkms-390 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-390.116 DKMS files... Building for 5.3.0-26-generic Building for architecture x86_64 Building initial module for 5.3.0-26-generic Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-5.3.0-26-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 19 19:34:34 2020 InstallationDate: Installed on 2012-12-14 (2592 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-29 (630 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860295/+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 1860230] Re: Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works
*** This bug is a duplicate of bug 1851162 *** https://bugs.launchpad.net/bugs/1851162 It looks like this will be bug 1851162, or bug 1830961 ** This bug has been marked a duplicate of bug 1851162 nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error: redefinition of ‘list_is_first’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1860230 Title: Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC 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.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 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/nvidia-graphics-drivers-390/+bug/1860230/+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 1860230] [NEW] Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works
You have been subscribed to a public bug: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC 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.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC: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. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 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: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic resolution third-party-packages ubuntu -- Nvidia-390 resolution incorrect after updating kernel to 5.3 but 5.0 works https://bugs.launchpad.net/bugs/1860230 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 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 1859071] 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/1859071 Title: Native mode 2560x1080 is randomly unavailable on some boots Status in linux package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu1 Candidate: 1.30.0-0ubuntu1 Version table: *** 1.30.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs. 1. Displays at the proper native resolution of 2560x1080, 2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or 3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution). Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm. Please let me know what additional information I can provide at this time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7] InstallationDate: Installed on 2020-01-05 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2478A44 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan ubuntu Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET96WW(2.56) dmi.board.asset.tag: Not Available dmi.board.name: 2478A44 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L530 dmi.product.name: 2478A44 dmi.product.sku: LENOVO_MT_2478 dmi.product.version: ThinkPad L530 dmi.sys.vendor: LENOVO 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes
[Kernel-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Thanks but that crash report is not relevant here. Please follow the instructions in comment #8. Please also update your system by running: sudo apt update sudo apt full-upgrade -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub 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 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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 N/A 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/1859730/+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 1859071] Re: Modesetting randomly fails to offer all modes available in the EDID
Great, thanks. Indeed the native mode of the monitor is missing from that list so this is a kernel or hardware problem. I assume the same command /usually/ shows more modes..? ** No longer affects: xorg-server (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - Modesetting randomly fails to offer all modes available in the EDID + Native mode 2560x1080 is randomly unavailable on some boots -- 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/1859071 Title: Native mode 2560x1080 is randomly unavailable on some boots Status in linux package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu1 Candidate: 1.30.0-0ubuntu1 Version table: *** 1.30.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs. 1. Displays at the proper native resolution of 2560x1080, 2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or 3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution). Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm. Please let me know what additional information I can provide at this time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f7] InstallationDate: Installed on 2020-01-05 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 2478A44 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=5b93649d-7f54-41f8-85e1-dc9d5d494872 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Tags: eoan ubuntu Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET96WW(2.56) dmi.board.asset.tag: Not Available dmi.board.name: 2478A44 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET96WW(2.56):bd08/23/2013:svnLENOVO:pn2478A44:pvrThinkPadL530:rvnLENOVO:rn2478A44:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L530 dmi.product.name: 2478A44 dmi.product.sku: LENOVO_MT_2478 dmi.product.version: ThinkPad L530 dmi.sys.vendor: LENOVO 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied:
[Kernel-packages] [Bug 1836858] Re: i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
There is no "fix" for this bug. You need to ignore the previous messages. -- 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 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 1796437] Re: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome)
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 ** Tags added: nouveau ** Summary changed: - X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) + [nouveau] X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) ** Summary changed: - [nouveau] X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) + [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() ** Tags removed: cosmic ** Changed in: xorg-server (Ubuntu) Status: Won't Fix => Confirmed ** No longer affects: gstreamer-vaapi (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: ubuntu-mate-meta (Ubuntu) ** No longer affects: ubuntu-mate-welcome (Ubuntu) ** This bug has been marked a duplicate of bug 1745345 Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. -- 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/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
[Kernel-packages] [Bug 1860295] [NEW] dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26
Public bug reported: After the update from 5.0 to 5.3 the dkms reconfigure of the nvidia-390 kernel module fails. The problem seems to be in a conflict between the "list_is_first" routine in the module and the new kernel, which causes a compile error. I will upload /var/lib/dkms/nvidia/390.116/build/make.log The reference in the log to autoconf.h missing is spurious. The generated/autoconf.h exists. Here is the reconfigure output # dpkg-reconfigure nvidia-dkms-390 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-390.116 DKMS files... Building for 5.3.0-26-generic Building for architecture x86_64 Building initial module for 5.3.0-26-generic Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-5.3.0-26-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 19 19:34:34 2020 InstallationDate: Installed on 2012-12-14 (2592 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-29 (630 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "error log for dkms build of the nvidia module" https://bugs.launchpad.net/bugs/1860295/+attachment/5321601/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1860295 Title: dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After the update from 5.0 to 5.3 the dkms reconfigure of the nvidia-390 kernel module fails. The problem seems to be in a conflict between the "list_is_first" routine in the module and the new kernel, which causes a compile error. I will upload /var/lib/dkms/nvidia/390.116/build/make.log The reference in the log to autoconf.h missing is spurious. The generated/autoconf.h exists. Here is the reconfigure output # dpkg-reconfigure nvidia-dkms-390 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-390.116 DKMS files... Building for 5.3.0-26-generic Building for architecture x86_64 Building initial module for 5.3.0-26-generic Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64) Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information. Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-5.3.0-26-generic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-dkms-390 390.116-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 19 19:34:34 2020 InstallationDate: Installed on 2012-12-14 (2592 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to bionic on 2018-04-29 (630 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1860295/+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 1859734] Re: i915 vulnerability
On 2020-01-19 16:15:58, aaronleung wrote: > My OS have this bug, i try to install kernel 5.4 in my linuxmint19.3, > bug, instailing not found samething with from /lib/firmware/i915/ ,again. > i try to download from > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/. > I download 5 .bin file and move to /lib/firmware/i915/. > after reinstall kernel 5.3 again, bug is fix!!! That is unrelated to this bug report. Please file a new bug report. 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/1859734 Title: i915 vulnerability Status in linux package in Ubuntu: Fix Committed Bug description: Ubuntu kernel currently lacks the complete i915 fix for other Intel hardware. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bc8a76a152c5f9ef3b48104154a65a68a8b76946 CVE-2019-14615 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Jan 14 20:09:58 2020 MachineType: LENOVO 2847CZU ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/tank-root ro spec_store_bypass_disable=on RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET88WW (1.46 ) dmi.board.name: 2847CZU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET88WW(1.46):bd04/01/2011:svnLENOVO:pn2847CZU:pvrThinkPadSL510:rvnLENOVO:rn2847CZU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad SL510 dmi.product.name: 2847CZU dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859734/+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 1860228] Re: addition of zfsutils-linux scrib every 2nd sunday
zfs-linux (0.6.5.6-2) unstable; urgency=medium
...
* Scrub all healthy pools monthly from Richard Laager
So Debian stretch, but not Ubuntu 16.04.
Deleting the file should be safe, as dpkg should retain that. It sounds
like you never deleted it, as you didn’t have it before this upgrade. So
it wasn’t an issue of the file coming back, just appearing for the first
time. Deleting and editing conffiles is a standard thing in Debian
systems.
These days, we may want to convert this to a system timer/service pair
instead, which you could then disable/mask if you don’t want. Of course,
the initial conversion will cause the same complaint you have here:
something changed on upgrade and enabled a job you don’t want.
** Changed in: zfs-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860228
Title:
addition of zfsutils-linux scrib every 2nd sunday
Status in zfs-linux package in Ubuntu:
Invalid
Bug description:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
Type Version/Name
Distribution Name Ubuntu
Distribution Version 18.04.3 LTS
Linux Kernel 4.15.0-73-generic
Architecture x86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
}}}
==When did this file get added into zfsonlinux ecosystem?==
{{{
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the month to
avoid system I/O overload on any one day of the month, like this:
{{{
# zfsmain scrub: 2:30AM 7th of every month
30 02 7 * * /sbin/zpool scrub zfsmain
# zstorage scrub: 2:30AM 5th of every month
30 02 5 * * /sbin/zpool scrub zstorage
# zmedia scrub: 1:00AM 14th of every month
00 01 14 * * /sbin/zpool scrub zmedia
# zstorage scrub: 2:30AM 21st of every month
30 02 21 * * /sbin/zpool scrub ztank
}}}
However suddenly I noticed in an adhoc check of zpool status that ALL my
pools were scrubbed on Sunday January 12th 2020!
{{{
# zpool status | grep -i "scrub"
scan: scrub repaired 0B in 0h13m with 0 errors on Sun Jan 12 00:37:31 2020
scan: scrub repaired 0B in 11h24m with 0 errors on Tue Jan 14 12:24:33 2020
<-- (one of my own since the Jan12 mega scrub)
scan: scrub repaired 0B in 0h45m with 0 errors on Sun Jan 12 01:09:40 2020
scan: scrub repaired 0B in 7h10m with 0 errors on Sun Jan 12 07:34:11 2020
}}}
this is NOT what I had configured, so I went digging and found that zfsutil
cron file :(
{{{
# cat /usr/lib/zfs-linux/scrub
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
This MAY be a desirable default for some system admins, but having it
suddenly appear IMO is at the same time undesirable for many.
==Describe how to reproduce the problem==
* Having been a ZoL user sys admin for many years.
* Be a decent sys admin and know the basics, you've configured your own
cron/schedule for pool scrubbing per guidelines and individual needs.
* Follow stable upgrade channels. (for me this is Ubuntu LTS 16.04, then
18.04)
* Suddenly after some upgrade version XX(?) your pools start scrubbing on the
2nd Sunday of every month without your having configured it or asked for that.
==Expectations==
Hoping we can:
1. Confirm when and why this was rolled out to all systems by default (does
the explanation make sense? is it really OK to do this? how was it
communicated?)
2. Ensure "how to disable" is documented and supported (i.e. if I just
delete that cron file, will some future upgrade replace and re-enable it?)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.7
ProcVersionSignature: Ubuntu 4.15.0-73.82-generic 4.15.18
Uname: Linux 4.15.0-73-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
Date: Sat Jan 18 13:41:29 2020
InstallationDate: Installed on 2015-06-28 (1664 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
[Kernel-packages] [Bug 1860196] Re: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI
Thank you advice. but I do not use nomodeset option. I use ipv6.disable=1 option. please show attachment file(grub). ** Attachment added: "my boot option /etc/default/grub" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+attachment/5321568/+files/grub -- 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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1860228] Re: addition of zfsutils-linux scrib every 2nd sunday
@rlaager ref for "long time ago"? (Looking for release notes and
specific version)
I've been reasonably diligent in monitoring my pool scrub activity, I
would "guess" that maybe in the last 2-3 months I may have lost track.
But also I only upgraded from Ubuntu 16.04 LTS sometime late-2019 Fall
(iirc) - couldn't find a way to precisely determine when. -- the below
details suggest in Sept 2019.
So "LONG time ago", certainly possible, but many users might not pick
this up until an upgrade from 16.04 LTS to 18.04 LTS.
Here's the history of the package. (only have so much detail due to log
rotation)
```
/var/log/apt$ for file in $(ls -1 | grep history.log | grep gz | sort -V); do
echo "==="; echo; echo $file; ls -al $file | awk '{print $6, $7, $8}'; zgrep
zfsutils-linux $file | tr ", " "\n" | grep -A1 zfsutils-linux; done
===
history.log.1.gz
Jan 1 00:00
===
history.log.2.gz
Nov 28 06:53
===
history.log.3.gz
Oct 31 06:39
===
history.log.4.gz
Sep 30 06:20
zfsutils-linux:amd64
(0.7.5-1ubuntu16.4
===
history.log.5.gz
Aug 30 06:57
===
history.log.6.gz
Jul 31 06:27
===
history.log.7.gz
Jun 30 2019
===
history.log.8.gz
May 31 2019
===
history.log.9.gz
Apr 30 2019
===
history.log.10.gz
Mar 30 2019
zfsutils-linux:amd64
(0.6.5.6-0ubuntu25
===
history.log.11.gz
Mar 1 2019
===
history.log.12.gz
Feb 1 2019
```
The above at least definitely proves that I was previously on 0.6.5.6
(likely while on Ubuntu 16.04) - where the zfsutils-linux cron scrub was
NOT present to my knowledge -- then in Sep 2019 we jump to 0.7.5 (likely
when I upgraded the server to Ubuntu 18.04).
To be clear, I've never deleted it, nor edited it, as only this week I
uncovered the "problem".
I agree that deletion of the file may be ill-advised ... since the next time
dpkg updates it would probably to re-add it?
The suggestion to edit the file and comment out the scrub command is
likely safest, however then all future upgrades will complain about the
conflict.
It would be preferable if there was a configuration to enable/disable
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860228
Title:
addition of zfsutils-linux scrib every 2nd sunday
Status in zfs-linux package in Ubuntu:
New
Bug description:
FULL REF: https://github.com/zfsonlinux/zfs/issues/9858 (initially
submitted there mistakenly)
==System information==
{{{
Type Version/Name
Distribution Name Ubuntu
Distribution Version 18.04.3 LTS
Linux Kernel 4.15.0-73-generic
Architecture x86_64
ZFS Version 0.7.5-1ubuntu16.6
SPL Version 0.7.5-1ubuntu2
Describe the problem you're observing
}}}
==When did this file get added into zfsonlinux ecosystem?==
{{{
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
I've been a ZoL user for many years now, and have had my own cron setup
tailored to distribute pool scrubs once per month, spread across the month to
avoid system I/O overload on any one day of the month, like this:
{{{
# zfsmain scrub: 2:30AM 7th of every month
30 02 7 * * /sbin/zpool scrub zfsmain
# zstorage scrub: 2:30AM 5th of every month
30 02 5 * * /sbin/zpool scrub zstorage
# zmedia scrub: 1:00AM 14th of every month
00 01 14 * * /sbin/zpool scrub zmedia
# zstorage scrub: 2:30AM 21st of every month
30 02 21 * * /sbin/zpool scrub ztank
}}}
However suddenly I noticed in an adhoc check of zpool status that ALL my
pools were scrubbed on Sunday January 12th 2020!
{{{
# zpool status | grep -i "scrub"
scan: scrub repaired 0B in 0h13m with 0 errors on Sun Jan 12 00:37:31 2020
scan: scrub repaired 0B in 11h24m with 0 errors on Tue Jan 14 12:24:33 2020
<-- (one of my own since the Jan12 mega scrub)
scan: scrub repaired 0B in 0h45m with 0 errors on Sun Jan 12 01:09:40 2020
scan: scrub repaired 0B in 7h10m with 0 errors on Sun Jan 12 07:34:11 2020
}}}
this is NOT what I had configured, so I went digging and found that zfsutil
cron file :(
{{{
# cat /usr/lib/zfs-linux/scrub
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
# cat /etc/cron.d/zfsutils-linux
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]
&& /usr/lib/zfs-linux/scrub
}}}
This MAY be a desirable default for some system admins, but having it
suddenly appear IMO is at the same time undesirable for many.
==Describe how to reproduce the problem==
* Having been a ZoL user sys admin for many
[Kernel-packages] [Bug 1860284] 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_working_dmesg_dock_plugged_before_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321565/+files/ubuntu_5.3.0-26_working_dmesg_dock_plugged_before_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_notworking_lspci_dock_plugged_after_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321563/+files/ubuntu_5.3.0-26_notworking_lspci_dock_plugged_after_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] [NEW] thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
Public bug reported: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail)
[Kernel-packages] [Bug 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_working_lsusb_dock_plugged_before_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321567/+files/ubuntu_5.3.0-26_working_lsusb_dock_plugged_before_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_working_lspci_dock_plugged_before_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321566/+files/ubuntu_5.3.0-26_working_lspci_dock_plugged_before_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_notworking_dmesg_dock_plugged_after_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321562/+files/ubuntu_5.3.0-26_notworking_dmesg_dock_plugged_after_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot
** Attachment added: "ubuntu_5.3.0-26_notworking_lsusb_dock_plugged_after_boot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321564/+files/ubuntu_5.3.0-26_notworking_lsusb_dock_plugged_after_boot.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/1860284 Title: thinkpad thunderbolt 3 dock gen2 does not work on Yoga C940 unless plugged in before boot Status in linux package in Ubuntu: New Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW 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: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+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 1859734] Re: i915 vulnerability
My OS have this bug, i try to install kernel 5.4 in my linuxmint19.3, bug, instailing not found samething with from /lib/firmware/i915/ ,again. i try to download from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/. I download 5 .bin file and move to /lib/firmware/i915/. after reinstall kernel 5.3 again, bug is fix!!! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859734 Title: i915 vulnerability Status in linux package in Ubuntu: Fix Committed Bug description: Ubuntu kernel currently lacks the complete i915 fix for other Intel hardware. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bc8a76a152c5f9ef3b48104154a65a68a8b76946 CVE-2019-14615 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-26-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card29.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card29.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Jan 14 20:09:58 2020 MachineType: LENOVO 2847CZU ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/tank-root ro spec_store_bypass_disable=on RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6JET88WW (1.46 ) dmi.board.name: 2847CZU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6JET88WW(1.46):bd04/01/2011:svnLENOVO:pn2847CZU:pvrThinkPadSL510:rvnLENOVO:rn2847CZU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad SL510 dmi.product.name: 2847CZU dmi.product.version: ThinkPad SL510 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859734/+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 1824886] Re: Battery level stuck at 100% and Estimating...
I got the same situation and output. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Confirmed Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+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 1796437] Re: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome)
The issue is more generic - Yelp and Cheese crash in the VirtualBox on MATE, Xfce, Budgie and GNOME FlashBack (metacity) sessions. -- 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/1796437 Title: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1855339] Re: CONFIG_LEGACY_PTYS should be disabled
** Description changed: - + Legacy BSD PTYs have been replaced by UNIX 98 PTYs a long time ago. + Disable legacy BSD PTY support as it is no longer needed. + + This config option is recommended by the Kernel Self Protection + Project[1] and a 2019 study performed by Capsule 8 shows that it is + enabled in some other major distro kernels[2]. + + [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings + [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ -- 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: Legacy BSD PTYs have been replaced by UNIX 98 PTYs a long time ago. Disable legacy BSD PTY support as it is no longer needed. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in some other major distro kernels[2]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ 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 1855341] Re: CONFIG_USELIB should be disabled
** Description changed: - + We should disable CONFIG_USELIB to make the uselib(2) system call + unreachable in an effort to reduce the kernel attack surface. + + The system call is only used by very old libc implementations and is + unlikely to be used today. + + This config option is recommended by the Kernel Self Protection + Project[1] and a 2019 study performed by Capsule 8 shows that it is + enabled in some other major distro kernels[2]. + + [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings + [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ -- 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: We should disable CONFIG_USELIB to make the uselib(2) system call unreachable in an effort to reduce the kernel attack surface. The system call is only used by very old libc implementations and is unlikely to be used today. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in some other major distro kernels[2]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ 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 1855338] Re: CONFIG_IO_STRICT_DEVMEM should be enabled
** Description changed: - + We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of + active io-memory ranges. + + This could impact kernel debugability. In that case, you may reboot with + iomem=relaxed on the kernel commandline to override this setting. + + + This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in many other major distro kernels[2]. + + [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings + [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ -- 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: We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of active io-memory ranges. This could impact kernel debugability. In that case, you may reboot with iomem=relaxed on the kernel commandline to override this setting. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in many other major distro kernels[2]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ 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 1796437] Re: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome)
** Summary changed: - X11 crashed when attempting to open Budgie and MATE Welcome + X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) -- 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/1796437 Title: X11 crashed when attempting to open GtkWebKit- and gstreamer-based applications (as Yelp, Cheese, Budgie and MATE Welcome) Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this
[Kernel-packages] [Bug 1855337] Re: CONFIG_DEBUG_NOTIFIERS should be enabled
** Description changed: - + We should enable CONFIG_DEBUG_NOTIFIERS to ensure that notifier functions are present in the core kernel text or module text sections before calling + those functions. + + If an invalid function pointer is detected, a warning is issued and the + function is not called. This helps in attack prevention and detection. + + This config option is recommended by the Kernel Self Protection + Project[1]. + + [1] + https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings -- 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: We should enable CONFIG_DEBUG_NOTIFIERS to ensure that notifier functions are present in the core kernel text or module text sections before calling those functions. If an invalid function pointer is detected, a warning is issued and the function is not called. This helps in attack prevention and detection. This config option is recommended by the Kernel Self Protection Project[1]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings 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 1855336] Re: CONFIG_DEBUG_SG should be enabled
** Description changed: - + Enable CONFIG_DEBUG_SG to perform sanity checks when performing + operations on scatterlists. If a sanity check fails a loud warning is + printed to the logs. + + This change may help in detection of an attack that relies on + scatterlist manipulation. ** Description changed: - Enable CONFIG_DEBUG_SG to perform sanity checks when performing + We should enable CONFIG_DEBUG_SG to perform sanity checks when performing operations on scatterlists. If a sanity check fails a loud warning is printed to the logs. This change may help in detection of an attack that relies on scatterlist manipulation. + + This config option is recommended by the Kernel Self Protection + Project[1]. + + [1] + https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings -- 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: We should enable CONFIG_DEBUG_SG to perform sanity checks when performing operations on scatterlists. If a sanity check fails a loud warning is printed to the logs. This change may help in detection of an attack that relies on scatterlist manipulation. This config option is recommended by the Kernel Self Protection Project[1]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings 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 1860123] Re: bionic/linux: 4.15.0-76.86 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 + bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 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/1860123 Title: bionic/linux: 4.15.0-76.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Saturday, 18. January 2020 03:27 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-aws: bug 1859795 bionic/linux-snapdragon: bug 1859793 bionic/linux/pc-kernel: bug 1860120 bionic/linux/pc-lowlatency-kernel: bug 1860121 xenial/linux-azure: bug 1859798 xenial/linux-hwe: bug 1860122, bug 1859704 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1860123/+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 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
@john This problem was meanwhile worked around by setting radeon.agp.mode=-1 as default in recent kernels (=> 5.0 ?). So you don't need to fiddle around with your settings here. Unfortunately Ubuntu ppc support is dead, only ppc64le option is maintained. But there are other distros (Void, Adelie). Void has very good ppc support, a working Firefox 72 for ppc64 and working epiphany browser for ppc. Also live images are avaiable: https://voidlinux-ppc.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The freeze happens every time unless I use "radeon.agpmode=-1" as a kernel parameter. Affected machines: PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6 Uname: Linux 4.4.0-18-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2 Architecture: powerpc AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.373 CurrentDesktop: MATE Date: Sun Apr 17 21:08:40 2016 IwConfig: lono wireless extensions. enP2p36s15f0 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc (20160417.1) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed boot=casper quiet --- radeon.agpmode=-1 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-powerpc-smp N/A linux-backports-modules-4.4.0-18-powerpc-smp N/A linux-firmware1.157 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+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 1626731]
[366338.166585] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41 [366338.166652] usbcore: registered new interface driver uvcvideo [366338.166652] USB Video Class driver (1.1.1) [366357.978516] usbcore: deregistering interface driver uvcvideo [366377.298295] usb 5-4: USB disconnect, device number 16 [366382.517118] usb 5-4: new high-speed USB device number 17 using xhci_hcd [366382.539011] usb 5-4: config 1 interface 1 altsetting 0 endpoint 0x82 has wMaxPacketSize 0, skipping [366382.539015] usb 5-4: New USB device found, idVendor=eb1a, idProduct=299f, bcdDevice= 6.09 [366382.539017] usb 5-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [366382.596668] uvcvideo: Found UVC 1.00 device (eb1a:299f) [366382.601384] uvcvideo: No streaming interface found for terminal 2. [366382.601390] uvcvideo 5-4:1.0: Entity type for entity Extension 4 was not initialized! [366382.601395] uvcvideo 5-4:1.0: Entity type for entity Processing 3 was not initialized! [366382.601397] uvcvideo 5-4:1.0: Entity type for entity Camera 1 was not initialized! [366382.601536] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input42 [366382.601624] usbcore: registered new interface driver uvcvideo [366382.601625] USB Video Class driver (1.1.1) 5.4.11-050411-generic camera worked pre kernel 4's and before going from Ubuntu 18 - 19 -- 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/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+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] Re: CONFIG_DEBUG_CREDENTIALS should be enabled
** Description changed: - + We should enable CONFIG_DEBUG_CREDENTIALS to perform sanity checks, such as verifying usage counts and proper magic values, when handling cred + structs. If a cred sanity check fails a loud warning is printed to the + logs. + + The config option raises the bar on the effort required to implement an + exploit based on cred manipulation. CONFIG_DEBUG_CREDENTIALS will not + prevent the attack but may aide an administrator in discovering such an + attack on the system. + + This config option is recommended by the Kernel Self Protection + Project[1]. + + [1] + https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings -- 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: We should enable CONFIG_DEBUG_CREDENTIALS to perform sanity checks, such as verifying usage counts and proper magic values, when handling cred structs. If a cred sanity check fails a loud warning is printed to the logs. The config option raises the bar on the effort required to implement an exploit based on cred manipulation. CONFIG_DEBUG_CREDENTIALS will not prevent the attack but may aide an administrator in discovering such an attack on the system. This config option is recommended by the Kernel Self Protection Project[1]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings 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 1855334] Re: CONFIG_DEBUG_LIST should be enabled
** Description changed: - + We should turn on CONFIG_DEBUG_LIST which does some sanity checking on the + surrounding linked list elements when adding or removing an element. If the sanity check fails, the list manipulation operation is not and a loud warning is printed to the logs in the form of a WARN(). + + This may prevent some exploits that involve manipulating a linked list. + + This config option is recommended by the Kernel Self Protection + Project[1] and a 2019 study performed by Capsule 8 shows that it is + enabled in some other major distro kernels[2]. + + [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings + [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ -- 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: We should turn on CONFIG_DEBUG_LIST which does some sanity checking on the surrounding linked list elements when adding or removing an element. If the sanity check fails, the list manipulation operation is not and a loud warning is printed to the logs in the form of a WARN(). This may prevent some exploits that involve manipulating a linked list. This config option is recommended by the Kernel Self Protection Project[1] and a 2019 study performed by Capsule 8 shows that it is enabled in some other major distro kernels[2]. [1] https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings [2] https://capsule8.com/blog/millions-of-binaries-later-a-look-into-linux-hardening-in-the-wild/ 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 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -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: 1859705 + kernel-stable-master-bug: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 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 verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs ** 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 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-snapdragon/dragonboard-kernel: bug 1859791 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 17. January 2020 10:36 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-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+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 1860196] Re: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI
You use nouveau, but have set the boot option nomodeset. So it is your fault. Bionic with kernel 5.3.0-26 and nouveau work fine. -- 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/1860196 Title: kernel-5.3.0-26 could not use appliicatins on geforce 8600GTI Status in linux package in Ubuntu: Incomplete Bug description: dear everyone. I update ubuntu-18.04.3 to use software-updater, then kernel update to 5.3.0-26. Desktop PC environment(Core2 Duo E8400, so old PC) are updated and boot up fine. but could not use applicaion, may be hung up. could not click icon, but mouse are moved. I use to restore backup and retry 3 times, but same result. I reboot another patition ubuntu-18.04, and get /var/log/syslog. I attached this report. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nakasima 1711 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-30 (140 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190808) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5K/EPU Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=7bb03d3f-117f-4243-ab29-c91ee32f2b44 ro recovery nomodeset ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.173.14 RfKill: Tags: bionic Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd03/06/2008:svnSystemmanufacturer:pnP5K/EPU:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K/EPU:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: P5K/EPU dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+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 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
With the new kernel update this issue happens to me. No connection to wifi. Not possible. I am using a Clevo notebook, which was rebranded by Tuxedo. -- 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/1853050 Title: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) Status in linux package in Ubuntu: Confirmed Bug description: Wifi just fails to connect to an access point after upgrading from Ubuntu 19.04 to 19.10. Some outputs: uname -a Linux mothership 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci The typical failure looks like this in journalctl: Nov 18 23:04:13 mothership kernel: wlp3s0: send auth to d4:60:e3:15:4d:71 (try 3/3) Nov 18 23:04:13 mothership kernel: [ cut here ] Nov 18 23:04:13 mothership kernel: purge skb(s) not reported by firmware Nov 18 23:04:13 mothership kernel: WARNING: CPU: 5 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Modules linked in: nf_conntrack_netlink xt_owner xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter aufs overlay binfmt_misc nvidia_uvm(O Nov 18 23:04:13 mothership kernel: spi_pxa2xx_platform videobuf2_memops asus_wmi videobuf2_v4l2 i915 mxm_wmi wmi_bmof sparse_keymap serio_raw videobuf2_common cfg80211 dw_dmac soundcore dw_dmac_core videodev input_leds drm_kms_helper joydev ipmi_devintf libarc4 mc ipmi_ Nov 18 23:04:13 mothership kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P W OE 5.3.0-23-generic #25-Ubuntu Nov 18 23:04:13 mothership kernel: Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.300 08/29/2017 Nov 18 23:04:13 mothership kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 cd b3 c0 e8 f6 fa 7b f6 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 3f 1c f7 48 8d 7b e0 49 89 c4 e8 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b4020ce48 EFLAGS: 00010286 Nov 18 23:04:13 mothership kernel: RAX: RBX: 913317bed848 RCX: 0006 Nov 18 23:04:13 mothership kernel: RDX: 0007 RSI: 0082 RDI: 91331eb57440 Nov 18 23:04:13 mothership kernel: RBP: a25b4020ce60 R08: 1754 R09: 0004 Nov 18 23:04:13 mothership kernel: R10: R11: 0001 R12: 91331eb5b600 Nov 18 23:04:13 mothership kernel: R13: 913317bed848 R14: c0adb7d0 R15: 913317bed848 Nov 18 23:04:13 mothership kernel: FS: () GS:91331eb4() knlGS: Nov 18 23:04:13 mothership kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:04:13 mothership kernel: CR2: 7fb4eee0b000 CR3: 0003818bc005 CR4: 003606e0 Nov 18 23:04:13 mothership kernel: Call Trace: Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: call_timer_fn+0x32/0x130 Nov 18 23:04:13 mothership kernel: __run_timers.part.0+0x177/0x270 Nov 18 23:04:13 mothership kernel: ? enqueue_hrtimer+0x3d/0x90 Nov 18 23:04:13 mothership kernel: ? recalibrate_cpu_khz+0x10/0x10 Nov 18 23:04:13 mothership kernel: ? ktime_get+0x42/0xa0 Nov 18 23:04:13 mothership kernel: run_timer_softirq+0x2a/0x50 Nov 18 23:04:13 mothership kernel: __do_softirq+0xe1/0x2d6 Nov 18 23:04:13 mothership kernel: ? hrtimer_interrupt+0x13b/0x220 Nov 18 23:04:13 mothership kernel: irq_exit+0xae/0xb0 Nov 18 23:04:13 mothership kernel: smp_apic_timer_interrupt+0x7b/0x140 Nov 18 23:04:13 mothership kernel: apic_timer_interrupt+0xf/0x20 Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x420 Nov 18 23:04:13 mothership kernel: Code: ff e8 5f 73 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 ce 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b400f3e38 EFLAGS: 0246 ORIG_RAX: ff13 Nov 18 23:04:13 mothership kernel: RAX: 91331eb6a740 RBX: b895a740 RCX: 001f Nov 18 23:04:13 mothership kernel: RDX: RSI: 4041ceb5 RDI: Nov 18 23:04:13 mothership kernel: RBP:
