[Kernel-packages] [Bug 1796789] Re: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly
** Description changed: - Steps: - 1. Installed system and log in. - 2. Do something on M715q-RR-1 or let it idle - 3. Verify the system once per 10 minutes + [Impact] + On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it + switchs to amdgpufb, the system will hang randomlly, sometimes it hangs during + boot, reboot or poweroff, sometimes it hangs with longtime standby. - Actual result: - System got hang during working. + + [Fix] + Through bisecting, I found this patch can fix the problem, looks like without + this patch the ATOM BIOS can't be parsed correctlly. + + + [Test Case] + Did the test of "boot, reboot and poweroff" 5 times, worked very well. + Let the system standby over one night, worked very well. + + [Regression Potential] + Very low, I tested this patch on at least 6 differnt lenovo machines + and those machines have different AMD GPUs on them, all of them worked + as well as before. -- 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/1796789 Title: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it switchs to amdgpufb, the system will hang randomlly, sometimes it hangs during boot, reboot or poweroff, sometimes it hangs with longtime standby. [Fix] Through bisecting, I found this patch can fix the problem, looks like without this patch the ATOM BIOS can't be parsed correctlly. [Test Case] Did the test of "boot, reboot and poweroff" 5 times, worked very well. Let the system standby over one night, worked very well. [Regression Potential] Very low, I tested this patch on at least 6 differnt lenovo machines and those machines have different AMD GPUs on them, all of them worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796789] Re: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly
** Tags added: originate-from-1789802 sutton -- 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/1796789 Title: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Installed system and log in. 2. Do something on M715q-RR-1 or let it idle 3. Verify the system once per 10 minutes Actual result: System got hang during working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796789] 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 1796789 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/1796789 Title: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Installed system and log in. 2. Do something on M715q-RR-1 or let it idle 3. Verify the system once per 10 minutes Actual result: System got hang during working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796789] [NEW] the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly
Public bug reported: Steps: 1. Installed system and log in. 2. Do something on M715q-RR-1 or let it idle 3. Verify the system once per 10 minutes Actual result: System got hang during working. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1789802 sutton ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1796789 Title: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Installed system and log in. 2. Do something on M715q-RR-1 or let it idle 3. Verify the system once per 10 minutes Actual result: System got hang during working. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796786] Re: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd)
** Summary changed: - screen displays normally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) + screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) ** Description changed: - Steps: - 1. Installed system. - 2. Verify the screen in the P2 of installation. + [Impact] + On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it + switchs to amdgpufb, the screen displays abnormally, we tested with a couple monitors, + all of them can reproduce this issue. - Actual result: - Screen displays abnormally, please refer to the picture in attachment. + [Fix] + Backported 3 patches from mainline kernel, all of them focus on the change of + disable_vga(). After applying these 3 patches, the issue disappears. - Expected result: - Display should be good in all stage. + + [Test Case] + boot the system, run glxgears, everything works well + + [Regression Potential] + Very low, these patches come from upstream, and I have tested them on at least 6 different + lenovo machines and those machines have different AMD GPUs on them, all of them worked + as well as before. -- 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/1796786 Title: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it switchs to amdgpufb, the screen displays abnormally, we tested with a couple monitors, all of them can reproduce this issue. [Fix] Backported 3 patches from mainline kernel, all of them focus on the change of disable_vga(). After applying these 3 patches, the issue disappears. [Test Case] boot the system, run glxgears, everything works well [Regression Potential] Very low, these patches come from upstream, and I have tested them on at least 6 different lenovo machines and those machines have different AMD GPUs on them, all of them worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796346] Re: linux: 4.18.0-9.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796346 Title: linux: 4.18.0-9.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge) derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 1796351 (linux-gcp), bug 1796353 (linux-kvm) -- swm properties -- phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796346/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Re: Kernel panic at boot
[Expired for linux (Ubuntu Cosmic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Expired -- 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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX 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.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780466] Re: Kernel panic at boot
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- 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/1780466 Title: Kernel panic at boot Status in linux package in Ubuntu: Expired Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Expired Bug description: Initially I have reported this issue here: https://bugzilla.kernel.org/show_bug.cgi?id=197815 But after testing out linux-image-4.17.0-4-generic on Ubuntu 18.10 dev the details changed a bit. Mainly I'm getting the error message "VFS: Cannot open root device "sda1" or unknown-block(0,0): error -6". Informations on the web imply that it might be possible that the required drivers are not anymore in recent kernel versions so I decided to post that issue now here too. The last working kernel version for me was linux-image-4.13.0-15-generic and the next version did already create a kernel panic for which I created originally the upstream report. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-15-generic. ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sworddragon 1521 F pulseaudio /dev/snd/controlC0: sworddragon 1521 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 18.10 EcryptfsInUse: Yes IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-15-generic N/A linux-backports-modules-4.13.0-15-generic N/A linux-firmware 1.174 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: cosmic Uname: Linux 4.13.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX 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.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX: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.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786094] Re: Dell XPS 9550 does not suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1786094 Title: Dell XPS 9550 does not suspend Status in linux package in Ubuntu: Expired Bug description: After a recent kernel update I have had several suspend failures on a Dell XPS 9550. Instead of suspending as usual the system stays on and is unresponsive with a black screen. Strangely enough this does NOT happen on every suspend, it usually happens after several successful suspend-resume cycle. The issue started with a kernel upgrade to linux- image-4.15.0-29-generic on Ubuntu 16.04.5. I have subsequently upgraded to kernel linux-image-4.15.0-30-generic on Ubuntu 18.04.1 where the issue persists. The workaround for me at the moment is to install and use linux- image-4.15.0-24-generic. Laptop is running the latest Dell BIOS, currently with no Nvidia proprietary drivers. The issue was also present with the nvidia proprietary drivers from the Ubuntu 16.04.5 repositories. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kstoilov 2508 F...m pulseaudio /dev/snd/controlC0: kstoilov 2508 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 8 21:44:40 2018 InstallationDate: Installed on 2016-04-29 (831 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=UUID=539a3d5f-4f1b-4fdc-b884-75fb289fe957 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-04 (4 days ago) dmi.bios.date: 02/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd02/23/2018:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786048] Re: display brightness not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1786048 Title: display brightness not working Status in linux package in Ubuntu: Expired Bug description: Using intel dual_core processor i just upgrade lts-16.04 to ubuntu 18.04 now i unable to reduce or increase brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-6-generic 4.17.0-6.7 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic i686 ApportVersion: 2.20.10-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rahul 1460 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Aug 8 19:43:11 2018 HibernationDevice: RESUME=UUID=88199ab0-6838-4b90-a76c-b652cdaa92e7 InstallationDate: Installed on 2018-08-03 (4 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) MachineType: LENOVO INVALID ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic root=UUID=f569a9d4-9d61-428a-9277-bcfd42fe2e8c ro quiet splash acpi_backlight=video vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.17.0-6-generic N/A linux-backports-modules-4.17.0-6-generic N/A linux-firmware1.174 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-08-07 (0 days ago) dmi.bios.date: 12/26/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 4FCNA1WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr4FCNA1WW:bd12/26/2011:svnLENOVO:pnINVALID:pvrLenovoB460e:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: INVALID dmi.product.version: Lenovo B460e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786322] Re: package linux-image-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: package linux-image-4.13.0-41-generic is not ready for configuration cannot co
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1786322 Title: package linux-image-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: package linux-image-4.13.0-41-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Expired Bug description: kernel ver. 48-16.04.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-41-generic 4.13.0-41.46~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Aug 9 13:50:54 2018 DuplicateSignature: package:linux-image-4.13.0-41-generic:4.13.0-41.46~16.04.1 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package linux-image-4.13.0-36-generic (--configure): package linux-image-4.13.0-36-generic is not ready for configuration ErrorMessage: package linux-image-4.13.0-41-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-20 (110 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-image-4.13.0-41-generic 4.13.0-41.46~16.04.1 failed to install/upgrade: package linux-image-4.13.0-41-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786161] Re: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: installed linux-image-4.15.0-29-generic package pre-removal script subprocess returned
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1786161 Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: installed linux-image-4.15.0-29-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: So, around time of use ubuntu 18.04 lts - 6h , it appeared one problema with my operacional system: when it showed me the atualization of kernel, my computer reincialized , but it didnt run the inicialization of system. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm4267 F pulseaudio mcv4607 F pulseaudio Date: Thu Aug 9 01:04:07 2018 ErrorMessage: installed linux-image-4.15.0-29-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-08 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b337 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E1-571 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=2f87b717-b7d7-4888-84ef-1903f45dc6aa ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: linux Title: package linux-image-4.15.0-29-generic 4.15.0-29.31 failed to install/upgrade: installed linux-image-4.15.0-29-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HC_HR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnAcer:bvrV2.21:bd12/16/2013:svnAcer:pnAspireE1-571:pvrV2.21:rvnAcer:rnEA50_HC_HR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.21: dmi.product.family: Type1Family dmi.product.name: Aspire E1-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796786] 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 1796786 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/1796786 Title: screen displays normally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Installed system. 2. Verify the screen in the P2 of installation. Actual result: Screen displays abnormally, please refer to the picture in attachment. Expected result: Display should be good in all stage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796786] [NEW] screen displays normally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd)
Public bug reported: Steps: 1. Installed system. 2. Verify the screen in the P2 of installation. Actual result: Screen displays abnormally, please refer to the picture in attachment. Expected result: Display should be good in all stage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1789801 sutton ** Tags added: originate-from-1789801 sutton -- 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/1796786 Title: screen displays normally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Steps: 1. Installed system. 2. Verify the screen in the P2 of installation. Actual result: Screen displays abnormally, please refer to the picture in attachment. Expected result: Display should be good in all stage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1796786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796550] Re: Separate keyboard brightness control keys (down/up) don't work
Also, the kernel does recognise the keys: Event: time 1539010310.047487, -- SYN_REPORT Event: time 1539010313.623520, type 1 (EV_KEY), code 229 (KEY_KBDILLUMDOWN), value 1 Event: time 1539010313.623520, -- SYN_REPORT Event: time 1539010313.735405, type 1 (EV_KEY), code 229 (KEY_KBDILLUMDOWN), value 0 Event: time 1539010313.735405, -- SYN_REPORT Event: time 1539010314.263525, type 1 (EV_KEY), code 230 (KEY_KBDILLUMUP), value 1 Event: time 1539010314.263525, -- SYN_REPORT Event: time 1539010314.359497, type 1 (EV_KEY), code 230 (KEY_KBDILLUMUP), value 0 Event: time 1539010314.359497, -- SYN_REPORT So we have all the kernel bits we need. Only the GUI is broken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: Separate keyboard brightness control keys (down/up) don't work Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/100 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats
did a test on a hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
gui screen shows blue background, lubuntu (logo) and dots (normal plymouth)
text screen shows
[ 99.99] ehci-pci :00:1d.0:dma_direct_map_sg: overflow
0x000223ad7000+2048 of device mask
scrolling by endlessly... (till I rebooted at ~1650.99 timestamp
message)
alas lubuntu 18.10 x86 image was maybe 2 days old..
I updated image to latest, same result (but I didn't wait as long)
** Attachment added: "lshw_hp_8200.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+attachment/5198943/+files/lshw_hp_8200.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/1794922
Title:
lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
" repeats
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Unknown
Bug description:
-- Background --
Testing the x86 (32bit) ISO image on various machines.
After zsync download, the thumb-drive is tested ("check disk for
defects") & passes; and worked fine on two systems today (dell d610 &
hp dx6120), however
-- Issue --
dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
lubuntu plymouth screen.
switching to messages, it's just the following repeating
// on dell 755
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048
of device mask "
// on hp dc7700
"ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048
of device mask "
NOTE: I can't copy/paste from systems, as it never completes boot; I
left it >30mins (on 755) & it just kept repeating message. I've
manually typed it; so typo's could have been made.
A discussion on #lubuntu-devel provided a possible cause (Thank you
Walter!) -
---
guiverc: lyorian:
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
seems like it's a usb issue of some kind with 4.18
---
This fits because whilst I do my testing mostly on d610 & t43 (no
issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
issues. My last test was also long enough ago to be on 4.17 kernel.
I'll add `lshw` files for the two failed systems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796250] Re: sysfs test ubuntu_stress_smoke_test will cause kernel oops on X-lowlatency
repeated course bisect, now got something more reasonable:
4.8 fail
4.9 fail
4.10 - ok
4.11 - ok
4.12 - ok
4.14 - ok
4.18 - ok
--
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/1796250
Title:
sysfs test ubuntu_stress_smoke_test will cause kernel oops on
X-lowlatency
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
This is found on a SRU testing node "gonzo", with 4.4 amd64 lowlatency
kernel.
This issue cannot be reproduced with the kernel 4.4.0-137 in -updates (a bit
random, see comment #4)
And cannot be reproduced with the AMD64 generic kernel in -proposed
(4.4.0-138) as well
16:50:01 DEBUG| [stdout] timer STARTING
16:50:05 ERROR| [stderr]
/home/ubuntu/autotest/client/tests/ubuntu_stress_smoke_test/ubuntu_stress_smoke_test.sh:
line 111: 39506 Killed ./stress-ng -v -t ${DURATION} --${s}
${INSTANCES} ${STRESS_OPTIONS} &> ${TMP_FILE}
16:50:05 DEBUG| [stdout] timer RETURNED 137
16:50:05 DEBUG| [stdout] timer FAILED (kernel oopsed)
16:50:05 DEBUG| [stdout] [ 1418.982110] BUG: unable to handle kernel paging
request at 00010001
16:50:05 DEBUG| [stdout] [ 1419.065329] IP: []
kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1419.137102] PGD 16f6dd067 PUD 0
16:50:05 DEBUG| [stdout] [ 1419.175602] Oops: [#6] SMP
16:50:05 DEBUG| [stdout] [ 1419.214101] Modules linked in: unix_diag
binfmt_misc vhost_net vhost macvtap cuse macvlan dccp_ipv4 dccp
jitterentropy_rng algif_rng ghash_generic salsa20_generic salsa20_x86_64
camellia_generic camellia_aesni_avx_x86_64 camellia_x86_64 cast6_avx_x86_64
cast6_generic cast_common serpent_avx_x86_64 serpent_sse2_x86_64
serpent_generic twofish_generic twofish_avx_x86_64 twofish_x86_64_3way
twofish_x86_64 twofish_common xts algif_skcipher tgr192 wp512 rmd320 rmd256
rmd160 rmd128 md4 algif_hash af_alg aufs kvm_amd kvm ipmi_devintf ipmi_ssif
irqbypass dcdbas ipmi_si fam15h_power acpi_power_meter joydev input_leds
ipmi_msghandler serio_raw i2c_piix4 k10temp amd64_edac_mod 8250_fintek mac_hid
shpchp edac_mce_amd edac_core ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core
ib_addr iscsi_tcp libiscsi_tcp libiscsi
16:50:05 DEBUG| [stdout] [ 1420.062172] scsi_transport_iscsi autofs4 btrfs
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul
ghash_clmulni_intel mptsas mptscsih pata_acpi hid_generic aesni_intel
aes_x86_64 mptbase lrw gf128mul glue_helper psmouse ahci ablk_helper usbhid
cryptd pata_atiixp libahci scsi_transport_sas bnx2 hid
16:50:05 DEBUG| [stdout] [ 1420.472200] CPU: 3 PID: 39506 Comm:
ubuntu_stress_s Tainted: G D 4.4.0-138-generic #164-Ubuntu
16:50:05 DEBUG| [stdout] [ 1420.588693] Hardware name: Dell Inc. PowerEdge
R415/08WNM9, BIOS 1.9.3 04/26/2012
16:50:05 DEBUG| [stdout] [ 1420.678138] task: 880177823800 ti:
88016a5b task.ti: 88016a5b
16:50:05 DEBUG| [stdout] [ 1420.767584] RIP: 0010:[]
[] kmem_cache_alloc+0x77/0x1f0
16:50:05 DEBUG| [stdout] [ 1420.868478] RSP: 0018:88016a5b3bd0 EFLAGS:
00010202
16:50:05 DEBUG| [stdout] [ 1420.931924] RAX: RBX:
024000c0 RCX: 0129e216
16:50:05 DEBUG| [stdout] [ 1421.017209] RDX: 0129e215 RSI:
024000c0 RDI: 0001a5c0
16:50:05 DEBUG| [stdout] [ 1421.102496] RBP: 88016a5b3c00 R08:
8802156da5c0 R09: 00010001
16:50:05 DEBUG| [stdout] [ 1421.187782] R10: 88000ff0 R11:
0ff0 R12: 024000c0
16:50:05 DEBUG| [stdout] [ 1421.273070] R13: 811d53e8 R14:
880215003b00 R15: 880215003b00
16:50:05 DEBUG| [stdout] [ 1421.358354] FS: 7f1323076700()
GS:8802156c() knlGS:
16:50:05 DEBUG| [stdout] [ 1421.455081] CS: 0010 DS: ES: CR0:
80050033
16:50:05 DEBUG| [stdout] [ 1421.523728] CR2: 00010001 CR3:
00016f6dc000 CR4: 000406f0
16:50:05 DEBUG| [stdout] [ 1421.609013] Stack:
16:50:05 DEBUG| [stdout] [ 1421.632941] 88019c080a28
cfff
16:50:05 DEBUG| [stdout] [ 1421.721371] 7fffefec 88020ff29000
88016a5b3c38 811d53e8
16:50:05 DEBUG| [stdout] [ 1421.809805] 0002 88019c080a28
cfff 7fffefec
16:50:05 DEBUG| [stdout] [ 1421.898237] Call Trace:
16:50:05 DEBUG| [stdout] [ 1421.927367] []
anon_vma_prepare+0x48/0x180
16:50:05 DEBUG| [stdout] [ 1421.996017] []
handle_mm_fault+0x13ed/0x1b70
16:50:05 DEBUG| [stdout] [ 1422.066743] [] ?
atime_needs_update+0x6f/0xd0
16:50:05 DEBUG| [stdout] [ 1422.138510] [] ?
touch_atime+0x33/0xd0
16:50:05 DEBUG| [stdout] [ 1422.202997] [] ?
generic_file_read_iter+0x5dc/0x6b0
16:50:05
[Kernel-packages] [Bug 1793753] Re: kernel panic - null pointer dereference on ipset operations
I've tested the proposed kernel under the previous test environment -
after two hours the host was still up, where as it would have previously
crashed within 30 minutes or so. As such, this appears to prevent the
panic.
--
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/1793753
Title:
kernel panic - null pointer dereference on ipset operations
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
A regression was introduced in Xenial, even prior to v4.4 Final. I did
not test prior to this kernel once I found the bug was fixed in
mainline. The bug reporter experienced crashes on machines running
iptables using ipsets. He could get a trace from the console on one of
them which is attached to the bug report.
On these machines, some ipset commands are automatically run to update the
sets, and/or to dump them (ipset restore, swap, delete ... / ipset save).
I was able to reproduce this bug as was cking. This bug was found to be
fixed by mainline commits 596cf3fe5854 and e5173418ac59.
== Fixes ==
596cf3fe5854 ("netfilter: ipset: fix race condition in ipset save, swap and
delete")
e5173418ac59 ("netfilter: ipset: Fix race between dump and swap")
== Regression Potential ==
Low. This fixes a regression and is limited to netfilter.
== Test Case ==
A test kernel was built with these patches and tested by myself and cking.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Found patch [0] fixing module build. Observe the same behavior. [0] https://www.hlmjr.com/index.php/2018/08/21/nvidia-drivers-390-77-vs-linux-kernel-4-18 ** Tags added: kernel-bug-exists-upstream -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the gnome freezes after GDM login. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Yes it is started right after the upgrade from 18.04. 18.04 with the latest SW was running just fine (on kernel 4.15.0-36-generic). Have not seen it working on 18.10. Tried 4.19-rc7. Observations: * Update manager "enables" driver, but it is not loaded * Manual install of nvidia-driver-390 xserver-xorg-video-nvidia-390 shows the issue: ERROR (dkms apport): kernel package linux-headers-4.19.0-041900rc7-generic is not supported Error! Bad return status for module build on kernel: 4.19.0-041900rc7-generic (x86_64) Consult /var/lib/dkms/nvidia/390.87/build/make.log for more information. Looks like compatibility issue with kernel 4.19. Not sure, though. ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+attachment/5198878/+files/make.log ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a
Haven't asked for a new wifi card yet, as I don't think it's the hardware. But I might get annoyed enough to try. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1793997 Title: iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a Status in linux-signed package in Ubuntu: Confirmed Bug description: Every few days iwlwifi decides to stop working. Only recourse is restart. From syslog: Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi transaction failed, dumping registers Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi device config registers: Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: : 08b18086 0010 028000bb 0004 Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 0020: 40708086 00c8 0100 Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi device memory mapped registers: Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: : Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 0020: Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi device AER capability structure: Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: : 14010001 0010 00462031 3141 2000 0014 4001 Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 0020: 000f ec100460 Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config registers: Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 00810010 00040400 20f0 Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1 0040 00100405 Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here ] Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at /build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi] Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt intel_rapl x86_pkg_temp_thermal Sep 24 11:42:10 bonobo kernel: [109525.538898] intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp parport ip_tables Sep 24 11:42:10 bonobo kernel: [109525.538952] x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 libahci ipmi_devintf mii ipmi_msghandler video wmi Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 Tainted: P OE4.15.0-34-generic #37-Ubuntu Sep 24
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
test on Bionic
--
original:
$ uname -a
Linux mfo-sf194734 4.15.0-37-generic #40-Ubuntu SMP Tue Oct 2 15:36:54 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
$
$ ./neighlist
$
modified:
$ uname -a
Linux mfo-sf194734 4.15.0-37-generic #40+sf1947341 SMP Mon Oct 8 15:41:38
-03 2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
$ ./neighlist
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0x0, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x1, 0x0, 0x5e, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0xff, 0xe9, 0x9d,
0x60}, LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
family).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796757] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package
Public bug reported: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libnvidia-compute-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Oct 9 01:01:42 2018 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2018-10-06 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1796757 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu /libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libnvidia-compute-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Oct 9 01:01:42 2018 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2018-10-06 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package nvidia-340 340.106-0ubuntu3 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/1796757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1796542] Re: Silent corruption in Linux kernel 4.15
** Also affects: linux-signed-hwe (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1796542
Title:
Silent corruption in Linux kernel 4.15
Status in linux-signed package in Ubuntu:
Confirmed
Status in linux-signed-hwe package in Ubuntu:
New
Bug description:
TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
introduced silent data corruption for O_DIRECT uses, it's fixed in
17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)
A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
of O_DIRECT, in our case a KVM virtual machine with drives which use
qemu's "cache=none" option.
This is the commit which fixes the issue:
-
commit 17d51b10d7773e4618bcac64648f30f12d4078fb
Author: Martin Wilck
Date: Wed Jul 25 23:15:09 2018 +0200
block: bio_iov_iter_get_pages: pin more pages for multi-segment
IOs
bio_iov_iter_get_pages() currently only adds pages for the next non-zero
segment from the iov_iter to the bio. That's suboptimal for callers,
which typically try to pin as many pages as fit into the bio. This patch
converts the current bio_iov_iter_get_pages() into a static helper, and
introduces a new helper that allocates as many pages as
1) fit into the bio,
2) are present in the iov_iter,
3) and can be pinned by MM.
Error is returned only if zero pages could be pinned. Because of 3), a
zero return value doesn't necessarily mean all pages have been pinned.
Callers that have to pin every page in the iov_iter must still call this
function in a loop (this is currently the case).
This change matters most for __blkdev_direct_IO_simple(), which calls
bio_iov_iter_get_pages() only once. If it obtains less pages than
requested, it returns a "short write" or "short read", and
__generic_file_write_iter() falls back to buffered writes, which may
lead to data corruption.
Fixes: 72ecad22d9f1 ("block: support a full bio worth of IO for
simplified bdev direct-io")
Reviewed-by: Christoph Hellwig
Signed-off-by: Martin Wilck
Signed-off-by: Jens Axboe
-
Since there were a lot of components involved in the initial report to
us (xfs, guest kernel, guest virtio drivers, qemu, host kernel,
storage system), we had to isolate it. This is the commit which fixes
the data corruption bug. We created a reliable reproduction and tested
with the patch and without the patch. We also created a version of the
kernel which prints when the data-corrupting path in the kernel is
triggered.
> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu
# lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
> 2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
# apt-cache policy linux-image-4.15.0-36-generic
linux-image-4.15.0-36-generic:
Installed: 4.15.0-36.39
Candidate: 4.15.0-36.39
Version table:
*** 4.15.0-36.39 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
> 3) What you expected to happen
We ran a fio random write workload over 8x 512MB files over XFS in guest OS,
over qemu/kvm, over kernel 4.15.0-36.39-generic.
qemu-system was configured with cache=none, which means Direct IO. This is a
very common configuration.
qemu-system was with aio=threads -- the default.
We were expecting no data corruption.
> 4) What happened instead
The guest filesystem was corrupted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1796542/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
** 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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
family).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] 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 1796748
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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
family).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
Ah yes, cold boot seems to fix it for now. I'll need to wait and see if the bug now occurs during normal operation. -- 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/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
** Description changed:
[Impact]
- * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
+ * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
- * Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
-such request/family currently receive nothing back in the kernel response.
+ * Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
+ such request/family currently receive nothing back in the kernel response.
- * The upstream fix resolves the breakage in the userspace-kernel interface
-by explicitly checking for the old/broken request to ensure it's replied.
+ * The upstream fix resolves the breakage in the userspace-kernel interface
+ by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
- * The command 'ip --family bridge neigh' returns nothing on broken kernels,
-and matches 'bridge fdb show' on fixed kernels.
+ * The command 'ip --family bridge neigh' returns nothing on broken kernels,
+ and matches 'bridge fdb show' on fixed kernels.
- * Before:
+ * Before:
- $ ip --family bridge neigh
- $
+ $ ip --family bridge neigh
+ $
- * After:
+ * After:
- $ ip --family bridge neigh
- dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
- dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
- dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
+ $ ip --family bridge neigh
+ dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
+ dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
+ dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
- * Reference:
+ * Reference:
- $ bridge fdb show
- 33:33:00:00:00:01 dev ens3 self permanent
- 01:00:5e:00:00:01 dev ens3 self permanent
- 33:33:ff:e9:9d:60 dev ens3 self permanent
+ $ bridge fdb show
+ 33:33:00:00:00:01 dev ens3 self permanent
+ 01:00:5e:00:00:01 dev ens3 self permanent
+ 33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
- * Low, for three reasons:
+ * Low, for three reasons:
- * The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
-which is apparently not very used (this regression has existed between
-v4.12 and v4.19).
+ * The fix is fairly contained (RTM_GETNEIGH request for PF_BRIDGE
+ family).
- * The checks introduced by the fix are conservative, based on the size
-of the old request (the size of the old/new requests are different),
-and it does nothing different in case the (old) size doesn't match.
+ * The checks introduced by the fix are conservative, based on the size
+ of the old request (the size of the old/new requests are different),
+ and it does nothing different in case the (old) size doesn't match.
- * Given the above, only applications with message length and contents
-specially hand-crafted (and likely not valid nor useful) might fail.
-To the best of my knowledge, this is not the common case out there.
+ * Given the above, only applications with message length and contents
+ specially hand-crafted (and likely not valid nor useful) might fail.
+ To the best of my knowledge, this is not the common case out there.
[Other Info]
-
- * The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
- * The patch is the same for Bionic, Cosmic, and unstable.
+ * The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
- * Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
-
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
+ * The patch is the same for Bionic, Cosmic, and unstable.
- * I'll submit the patch shortly to the kernel-team mailing list.
+ * Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
+
+ * I'll submit the patch shortly to the kernel-team mailing list.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
Incomplete
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12
** Summary changed:
- regression in 'ip --family bridge neigh' since linux v4.12+
+ regression in 'ip --family bridge neigh' since linux v4.12
--
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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
which is apparently not very used (this regression has existed between
v4.12 and v4.19).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12+
test on unstable:
-
original:
$ uname -a
Linux mfo-sf194734 4.19.0-1-generic #2 SMP Mon Oct 8 14:38:01 -03 2018
x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
$
$ ./neighlist
$
modified:
$ uname -a
Linux mfo-sf194734 4.19.0-1-generic #2+sf1947341 SMP Mon Oct 8 12:57:16 -03
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
$ ./neighlist
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0x0, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x1, 0x0, 0x5e, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0xff, 0xe9, 0x9d,
0x60}, LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
which is apparently not very used (this regression has existed between
v4.12 and v4.19).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] Re: regression in 'ip --family bridge neigh' since linux v4.12+
test on Cosmic
--
original:
$ uname -a
Linux mfo-sf194734 4.18.0-9-generic #10-Ubuntu SMP Fri Oct 5 16:49:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
$
$ ./neighlist
$
modified:
$ uname -a
Linux mfo-sf194734 4.18.0-9-generic #10+sf1947341 SMP Mon Oct 8 11:46:22
-03 2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
$ ./neighlist
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0x0, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x1, 0x0, 0x5e, 0x0, 0x0, 0x1},
LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
netlink.Neigh{LinkIndex:2, Family:7, State:128, Type:0, Flags:2,
IP:net.IP(nil), HardwareAddr:net.HardwareAddr{0x33, 0x33, 0xff, 0xe9, 0x9d,
0x60}, LLIPAddr:net.IP(nil), Vlan:0, VNI:0}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
which is apparently not very used (this regression has existed between
v4.12 and v4.19).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796748] [NEW] regression in 'ip --family bridge neigh' since linux v4.12
Public bug reported:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
which is apparently not very used (this regression has existed between
v4.12 and v4.19).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
** 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/1796748
Title:
regression in 'ip --family bridge neigh' since linux v4.12
Status in linux package in Ubuntu:
New
Bug description:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the breakage in the userspace-kernel interface
by explicitly checking for the old/broken request to ensure it's replied.
[Test Case]
* The command 'ip --family bridge neigh' returns nothing on broken kernels,
and matches 'bridge fdb show' on fixed kernels.
* Before:
$ ip --family bridge neigh
$
* After:
$ ip --family bridge neigh
dev ens3 lladdr 33:33:00:00:00:01 PERMANENT
dev ens3 lladdr 01:00:5e:00:00:01 PERMANENT
dev ens3 lladdr 33:33:ff:e9:9d:60 PERMANENT
* Reference:
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
33:33:ff:e9:9d:60 dev ens3 self permanent
[Regression Potential]
* Low, for three reasons:
* The fix is contained in the RTM_GETNEIGH request for PF_BRIDGE family,
which is apparently not very used (this regression has existed between
v4.12 and v4.19).
* The checks introduced by the fix are conservative, based on the size
of the old request (the size of the old/new requests are different),
and it does nothing different in case the (old) size doesn't match.
* Given the above, only applications with message length and contents
specially hand-crafted (and likely not valid nor useful) might fail.
To the best of my knowledge, this is not the common case out there.
[Other Info]
* The patch is only applicable to v4.12+ (so not Trusty nor Xenial).
* The patch is the same for Bionic, Cosmic, and unstable.
* Upstream commit: bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
header")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd961c9bc66497f0c63f4ba1d02900bb85078366
* I'll submit the patch shortly to the kernel-team mailing list.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796748/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
** 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** This bug is no longer a duplicate of bug 1796726 Ubuntu 18.10 regression: nvidia driver does not work ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Description changed: - Extra info for bug 1796433 + Problems started after upgrade to 18.10 and first reboot. + Symptoms: + * Login screen appears + * After providing credentials desktop does not start + + --- + + Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-4.18.0-8-generic N/A - linux-backports-modules-4.18.0-8-generic N/A - linux-firmware1.175 + linux-restricted-modules-4.18.0-8-generic N/A + linux-backports-modules-4.18.0-8-generic N/A + linux-firmware1.175 RfKill: - 0: phy0: Wireless LAN - Soft blocked: yes - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start --- Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon
[Kernel-packages] [Bug 1796726] Re: Ubuntu 18.10 regression: nvidia driver does not work
*** This bug is a duplicate of bug 1796730 *** https://bugs.launchpad.net/bugs/1796730 ** This bug has been marked a duplicate of bug 1796730 Ubuntu 18.10 regression: nvidia driver does not work -- 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/1796726 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2824 F pulseaudio /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work
*** This bug is a duplicate of bug 1796730 *** https://bugs.launchpad.net/bugs/1796730 ** This bug is no longer a duplicate of bug 1796726 Ubuntu 18.10 regression: nvidia driver does not work ** This bug has been marked a duplicate of bug 1796730 Ubuntu 18.10 regression: nvidia driver does not work -- 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/1796433 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 02:03:52 2018 InstallationDate: Installed on 2016-01-06 (1003 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend
It seems this fix also fixes the touch screen not working (no irq storm) after a suspend on an Acer Aspire Switch 11 (and possibly also other modules). See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1792309 Title: Fix I2C touchpanels' interrupt storms after system suspend Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] Some I2C touchpanels generate IRQ storm after system suspend/resume. [Test] After applying the fix, the IRQ storm stops generated by Raydium touchpanels. [Fix] Instead of requesting i2c reset, simply requesting the device to power on. The HID over I2C spec doesn't specify how the device should do upon resume from suspend, so some devices expect a power on instead of reset. [Regression Potential] Low. I tested other vendors' touchpanels, didn't observe any side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1792309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788686] Re: Acer laptop does not boot Ubuntu 16.04.5
bellajohsan (bellajohsan), I am booting from a USB key into RAM. That boot fails as per screenshots. Power source and storage are immaterial. This is not an Acer issue. To all, could it be UEFI related? I tried to disable this in BIOS, but that option is not available. -- 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/1788686 Title: Acer laptop does not boot Ubuntu 16.04.5 Status in linux package in Ubuntu: In Progress Bug description: *** *** Please change package to the appropriate one *** Trying to boot Acer laptop () from USB2 key on USB3 port with Ubuntu 16.04.5 LTS fails as per attached screenshots. This is reproducible. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Aug 23 15:11:08 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-22 (397 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
Good call, thanks! This turns out to be fixed in the latest mainline kernel. Looking at the git log for the i2c_hid driver, I found this commit which I suspect is the fix for my problem. https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8 https://patchwork.kernel.org/patch/10589793/ This fix first appeared in the 4.19-rc4 kernel. I tested 4.19-rc3, which is broken while 4.19-rc4 works, which supports my suspicion. I also tested 4.15.0-37.40 (from bionic proposed), which has this same fix backported and also works. I guess this issue can be closed / marked as fix released, but I'm not sure how exactly, so I'll leave that to others. -- 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/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in linux package in Ubuntu: Incomplete Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
[Kernel-packages] [Bug 1796743] 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/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in linux package in Ubuntu: Confirmed Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work
*** This bug is a duplicate of bug 1796726 *** https://bugs.launchpad.net/bugs/1796726 ** This bug has been marked a duplicate of bug 1796726 Ubuntu 18.10 regression: nvidia driver does not work -- 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/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: New Bug description: Extra info for bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796743] [NEW] Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
Public bug reported: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796743 Title: Ubuntu 18.10 - Alienware 17 R5 crashes on sleep Status in linux package in Ubuntu: Confirmed Bug description: If the machine goes to sleep, either because I close the lid or because it idles too long, it ends up in a weird state when I try to resume. If I press the power/Alien button, the fan runs and the keyboard/trackpad light up but nothing happens. Ultimately I need to hard power off the laptop (by holding the power button in for three seconds) which causes it to boot from scratch. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feoh 2895 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 8 14:25:16 2018 InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793461] Re: Improvements to the kernel source package preparation
** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-edge (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793461 Title: Improvements to the kernel source package preparation Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux-hwe-edge source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in linux-hwe-edge source package in Trusty: New Status in linux source package in Xenial: Fix Committed Status in linux-hwe-edge source package in Xenial: New Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-hwe-edge source package in Cosmic: New Bug description: We need to improve the automation of the process that we use to prepare kernel source packages. That requires changes in both the tooling and in the kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796726] Re: Ubuntu 18.10 regression: nvidia driver does not work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796726 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2824 F pulseaudio /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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
[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work
*** This bug is a duplicate of bug 1796726 *** https://bugs.launchpad.net/bugs/1796726 Data collected by "ubuntu-bug linux", while system was using proprietary nvidia driver can be found in bug 1796730 -- 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/1796433 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 02:03:52 2018 InstallationDate: Installed on 2016-01-06 (1003 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796730] [NEW] Ubuntu 18.10 regression: nvidia driver does not work
Public bug reported: Extra info for bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796730 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: New Bug description: Extra info for bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Oct 8 20:01:33 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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:
[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work
*** This bug is a duplicate of bug 1796726 *** https://bugs.launchpad.net/bugs/1796726 ** This bug has been marked a duplicate of bug 1796726 Ubuntu 18.10 regression: nvidia driver does not work -- 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/1796433 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 02:03:52 2018 InstallationDate: Installed on 2016-01-06 (1003 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796726] 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/1796726 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2824 F pulseaudio /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796726] Re: Ubuntu 18.10 regression: nvidia driver does not work
** Description changed: - Extra info for bug 1796433 + Problems started after upgrade to 18.10 and first reboot. + Symptoms: + * Login screen appears + * After providing credentials desktop does not start + + Part of dmesg: + - + ... + [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] + [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs + [ 10.801510] [ cut here ] + [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! + [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 + [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel + [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii + [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu + ... + - + + Extra info for Bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: alexei 2824 F pulseaudio - /dev/snd/controlC0: alexei 2824 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: alexei 2824 F pulseaudio + /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.18.0-8-generic N/A - linux-backports-modules-4.18.0-8-generic N/A - linux-firmware1.175 + linux-restricted-modules-4.18.0-8-generic N/A + linux-backports-modules-4.18.0-8-generic N/A + linux-firmware1.175 RfKill: - 0: phy0: Wireless LAN - Soft blocked: yes - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796726 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: Confirmed Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource
[Kernel-packages] [Bug 1796726] [NEW] Ubuntu 18.10 regression: nvidia driver does not work
Public bug reported: Extra info for bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2824 F pulseaudio /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796726 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in linux package in Ubuntu: New Bug description: Extra info for bug 1796433 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alexei 2824 F pulseaudio /dev/snd/controlC0: alexei 2824 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 19:47:11 2018 HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546 InstallationDate: Installed on 2016-01-06 (1005 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago) dmi.bios.date: 09/16/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: HM65-MXM 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.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work
Submitted bug 1796726 -- 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/1796433 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 02:03:52 2018 InstallationDate: Installed on 2016-01-06 (1003 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795413] Re: linux-kvm: 4.18.0-1002.2 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.18.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-phase:Released + kernel-phase-changed:Monday, 08. October 2018 17:31 UTC ** Description changed: This bug is for tracking the 4.18.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-phase:Released - kernel-phase-changed:Monday, 08. October 2018 17:31 UTC ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1795413 Title: linux-kvm: 4.18.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Cosmic: Fix Released Bug description: This bug is for tracking the 4.18.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
this report is from running lm-sensor when system is idle: kernel 4.18.0.8 amdgpu-pci-6500 Adapter: PCI adapter vddgfx: +0.77 V fan1: 974 RPM temp1:+30.0°C (crit = +94.0°C, hyst = -273.1°C) power1:6.11 W (cap = 48.00 W) kernel 4.18.0.9.10 amdgpu-pci-6500 Adapter: PCI adapter vddgfx: +1.08 V fan1: 974 RPM temp1:+41.0°C (crit = +94.0°C, hyst = -273.1°C) power1:18.47 W (cap = 48.00 W) clearly the voltage increase is the reason or the dynamic power management is broken... tried with amdgpu.dpm=1 on boot with no luck -- 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1796720] [NEW] High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Public bug reported: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd08/03/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic package-from-proposed ** Description changed: Hello, - Today I have received an update for Linux kernel which ugrade the kernel - on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after + Today I have received an update for Linux kernel which upgraded
[Kernel-packages] [Bug 1791724] Re: linux-oem: 4.15.0-1019.22 -proposed tracker
*** This bug is a duplicate of bug 1794428 *** https://bugs.launchpad.net/bugs/1794428 This bug was fixed in the package linux-oem - 4.15.0-1021.24 --- linux-oem (4.15.0-1021.24) bionic; urgency=medium [ Ubuntu: 4.15.0-36.39 ] * CVE-2018-14633 - iscsi target: Use hex2bin instead of a re-implementation * CVE-2018-17182 - mm: get rid of vmacache_flush_all() entirely linux-oem (4.15.0-1020.23) bionic; urgency=medium * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656) * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume linux-oem (4.15.0-1019.22) bionic; urgency=medium * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724) * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * Miscellaneous Ubuntu changes - Rebase to 4.15.0-35.38 - [Config] update configs following rebase to 4.15.0-35.38 * drm/i915: Drop backported support for Cannonlake. (LP: #1792589) [ Ubuntu: 4.15.0-35.38 ] * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719) * device hotplug of vfio devices can lead to deadlock in vfio_pci_release (LP: #1792099) - SAUCE: vfio -- release device lock before userspace requests * L1TF mitigation not effective in some CPU and RAM combinations (LP: #1788563) - x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit - x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM - x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ * CVE-2018-15594 - x86/paravirt: Fix spectre-v2 mitigations for paravirt guests * CVE-2017-5715 (Spectre v2 s390x) - KVM: s390: implement CPU model only facilities - s390: detect etoken facility - KVM: s390: add etoken support for guests - s390/lib: use expoline for all bcr instructions - s390: fix br_r1_trampoline for machines without exrl - SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance) (LP: #1790602) - cpuidle: powernv: Fix promotion from snooze if next state disabled * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636) - powerpc: hard disable irqs in smp_send_stop loop - powerpc: Fix deadlock with multiple calls to smp_send_stop - powerpc: smp_send_stop do not offline stopped CPUs - powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled * Security fix: check if IOMMU page is contained in the pinned physical page (LP: #1785675) - vfio/spapr: Use IOMMU pageshift rather than pagesize - KVM: PPC: Check if IOMMU page is contained in the pinned physical page * Missing Intel GPU pci-id's (LP: #1789924) - drm/i915/kbl: Add KBL GT2 sku - drm/i915/whl: Introducing Whiskey Lake platform - drm/i915/aml: Introducing Amber Lake platform - drm/i915/cfl: Add a new CFL PCI ID. * CVE-2018-15572 - x86/speculation: Protect against userspace-userspace spectreRSB * Support Power Management for Thunderbolt Controller (LP: #1789358) - thunderbolt: Handle NULL boot ACL entries properly - thunderbolt: Notify userspace when boot_acl is changed - thunderbolt: Use 64-bit DMA mask if supported by the platform - thunderbolt: Do not unnecessarily call ICM get route - thunderbolt: No need to take tb->lock in domain suspend/complete - thunderbolt: Use correct ICM commands in system suspend - thunderbolt: Add support for runtime PM * random oopses on s390 systems using NVMe devices (LP: #1790480) - s390/pci: fix out of bounds access during irq setup * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit (LP: #1787993) // CVE-2018-3639 (arm64) - arm64: alternatives: Add dynamic patching feature - KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state - KVM: arm64: Avoid storing the vcpu pointer on the stack - arm/arm64: smccc: Add SMCCC-specific return codes - arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 - arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 - arm64: Add ARCH_WORKAROUND_2 probing - arm64: Add 'ssbd' command-line option - arm64: ssbd: Add global mitigation state accessor - arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation - arm64: ssbd: Restore mitigation status on CPU resume - arm64: ssbd: Introduce thread flag to control userspace mitigation - arm64: ssbd: Add prctl interface for per-thread mitigation - arm64: KVM: Add HYP per-cpu accessors - arm64: KVM: Add ARCH_WORKAROUND_2 support for guests - arm64: KVM: Handle guest's
[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend
This bug was fixed in the package linux-oem - 4.15.0-1021.24 --- linux-oem (4.15.0-1021.24) bionic; urgency=medium [ Ubuntu: 4.15.0-36.39 ] * CVE-2018-14633 - iscsi target: Use hex2bin instead of a re-implementation * CVE-2018-17182 - mm: get rid of vmacache_flush_all() entirely linux-oem (4.15.0-1020.23) bionic; urgency=medium * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656) * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume linux-oem (4.15.0-1019.22) bionic; urgency=medium * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724) * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * Miscellaneous Ubuntu changes - Rebase to 4.15.0-35.38 - [Config] update configs following rebase to 4.15.0-35.38 * drm/i915: Drop backported support for Cannonlake. (LP: #1792589) [ Ubuntu: 4.15.0-35.38 ] * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719) * device hotplug of vfio devices can lead to deadlock in vfio_pci_release (LP: #1792099) - SAUCE: vfio -- release device lock before userspace requests * L1TF mitigation not effective in some CPU and RAM combinations (LP: #1788563) - x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit - x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM - x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ * CVE-2018-15594 - x86/paravirt: Fix spectre-v2 mitigations for paravirt guests * CVE-2017-5715 (Spectre v2 s390x) - KVM: s390: implement CPU model only facilities - s390: detect etoken facility - KVM: s390: add etoken support for guests - s390/lib: use expoline for all bcr instructions - s390: fix br_r1_trampoline for machines without exrl - SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance) (LP: #1790602) - cpuidle: powernv: Fix promotion from snooze if next state disabled * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636) - powerpc: hard disable irqs in smp_send_stop loop - powerpc: Fix deadlock with multiple calls to smp_send_stop - powerpc: smp_send_stop do not offline stopped CPUs - powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled * Security fix: check if IOMMU page is contained in the pinned physical page (LP: #1785675) - vfio/spapr: Use IOMMU pageshift rather than pagesize - KVM: PPC: Check if IOMMU page is contained in the pinned physical page * Missing Intel GPU pci-id's (LP: #1789924) - drm/i915/kbl: Add KBL GT2 sku - drm/i915/whl: Introducing Whiskey Lake platform - drm/i915/aml: Introducing Amber Lake platform - drm/i915/cfl: Add a new CFL PCI ID. * CVE-2018-15572 - x86/speculation: Protect against userspace-userspace spectreRSB * Support Power Management for Thunderbolt Controller (LP: #1789358) - thunderbolt: Handle NULL boot ACL entries properly - thunderbolt: Notify userspace when boot_acl is changed - thunderbolt: Use 64-bit DMA mask if supported by the platform - thunderbolt: Do not unnecessarily call ICM get route - thunderbolt: No need to take tb->lock in domain suspend/complete - thunderbolt: Use correct ICM commands in system suspend - thunderbolt: Add support for runtime PM * random oopses on s390 systems using NVMe devices (LP: #1790480) - s390/pci: fix out of bounds access during irq setup * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit (LP: #1787993) // CVE-2018-3639 (arm64) - arm64: alternatives: Add dynamic patching feature - KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state - KVM: arm64: Avoid storing the vcpu pointer on the stack - arm/arm64: smccc: Add SMCCC-specific return codes - arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 - arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 - arm64: Add ARCH_WORKAROUND_2 probing - arm64: Add 'ssbd' command-line option - arm64: ssbd: Add global mitigation state accessor - arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation - arm64: ssbd: Restore mitigation status on CPU resume - arm64: ssbd: Introduce thread flag to control userspace mitigation - arm64: ssbd: Add prctl interface for per-thread mitigation - arm64: KVM: Add HYP per-cpu accessors - arm64: KVM: Add ARCH_WORKAROUND_2 support for guests - arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests - arm64: KVM: Add ARCH_WORKAROUND_2 discovery through
[Kernel-packages] [Bug 1791731] Re: linux-kvm: 4.15.0-1022.22 -proposed tracker
*** This bug is a duplicate of bug 1794433 *** https://bugs.launchpad.net/bugs/1794433 This bug was fixed in the package linux-kvm - 4.18.0-1002.2 --- linux-kvm (4.18.0-1002.2) cosmic; urgency=medium * linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413) * Miscellaneous Ubuntu changes - kvm: [Config] CONFIG_HARDENED_USERCOPY=y - kvm: [Config] CONFIG_DEBUG_WX=y -- Seth Forshee Mon, 01 Oct 2018 09:27:19 -0500 ** Changed in: linux-kvm (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1791731 Title: linux-kvm: 4.15.0-1022.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1791719 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790605] Re: please include the kernel module IPIP
This bug was fixed in the package linux-kvm - 4.18.0-1002.2 --- linux-kvm (4.18.0-1002.2) cosmic; urgency=medium * linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413) * Miscellaneous Ubuntu changes - kvm: [Config] CONFIG_HARDENED_USERCOPY=y - kvm: [Config] CONFIG_DEBUG_WX=y -- Seth Forshee Mon, 01 Oct 2018 09:27:19 -0500 ** Changed in: linux-kvm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790605 Title: please include the kernel module IPIP Status in cloud-images: Won't Fix Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: Fix Released Bug description: In order to run calico with ubuntu cloud image one needs the ipip kernel module, which is unfortunately not present. $ grep IPIP /boot/config-4.4.0-1032-kvm # CONFIG_NET_IPIP is not set To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1790605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3
This bug was fixed in the package linux-oem - 4.15.0-1021.24 --- linux-oem (4.15.0-1021.24) bionic; urgency=medium [ Ubuntu: 4.15.0-36.39 ] * CVE-2018-14633 - iscsi target: Use hex2bin instead of a re-implementation * CVE-2018-17182 - mm: get rid of vmacache_flush_all() entirely linux-oem (4.15.0-1020.23) bionic; urgency=medium * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656) * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume linux-oem (4.15.0-1019.22) bionic; urgency=medium * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724) * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * Miscellaneous Ubuntu changes - Rebase to 4.15.0-35.38 - [Config] update configs following rebase to 4.15.0-35.38 * drm/i915: Drop backported support for Cannonlake. (LP: #1792589) [ Ubuntu: 4.15.0-35.38 ] * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719) * device hotplug of vfio devices can lead to deadlock in vfio_pci_release (LP: #1792099) - SAUCE: vfio -- release device lock before userspace requests * L1TF mitigation not effective in some CPU and RAM combinations (LP: #1788563) - x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit - x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM - x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ * CVE-2018-15594 - x86/paravirt: Fix spectre-v2 mitigations for paravirt guests * CVE-2017-5715 (Spectre v2 s390x) - KVM: s390: implement CPU model only facilities - s390: detect etoken facility - KVM: s390: add etoken support for guests - s390/lib: use expoline for all bcr instructions - s390: fix br_r1_trampoline for machines without exrl - SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance) (LP: #1790602) - cpuidle: powernv: Fix promotion from snooze if next state disabled * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636) - powerpc: hard disable irqs in smp_send_stop loop - powerpc: Fix deadlock with multiple calls to smp_send_stop - powerpc: smp_send_stop do not offline stopped CPUs - powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled * Security fix: check if IOMMU page is contained in the pinned physical page (LP: #1785675) - vfio/spapr: Use IOMMU pageshift rather than pagesize - KVM: PPC: Check if IOMMU page is contained in the pinned physical page * Missing Intel GPU pci-id's (LP: #1789924) - drm/i915/kbl: Add KBL GT2 sku - drm/i915/whl: Introducing Whiskey Lake platform - drm/i915/aml: Introducing Amber Lake platform - drm/i915/cfl: Add a new CFL PCI ID. * CVE-2018-15572 - x86/speculation: Protect against userspace-userspace spectreRSB * Support Power Management for Thunderbolt Controller (LP: #1789358) - thunderbolt: Handle NULL boot ACL entries properly - thunderbolt: Notify userspace when boot_acl is changed - thunderbolt: Use 64-bit DMA mask if supported by the platform - thunderbolt: Do not unnecessarily call ICM get route - thunderbolt: No need to take tb->lock in domain suspend/complete - thunderbolt: Use correct ICM commands in system suspend - thunderbolt: Add support for runtime PM * random oopses on s390 systems using NVMe devices (LP: #1790480) - s390/pci: fix out of bounds access during irq setup * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit (LP: #1787993) // CVE-2018-3639 (arm64) - arm64: alternatives: Add dynamic patching feature - KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state - KVM: arm64: Avoid storing the vcpu pointer on the stack - arm/arm64: smccc: Add SMCCC-specific return codes - arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 - arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 - arm64: Add ARCH_WORKAROUND_2 probing - arm64: Add 'ssbd' command-line option - arm64: ssbd: Add global mitigation state accessor - arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation - arm64: ssbd: Restore mitigation status on CPU resume - arm64: ssbd: Introduce thread flag to control userspace mitigation - arm64: ssbd: Add prctl interface for per-thread mitigation - arm64: KVM: Add HYP per-cpu accessors - arm64: KVM: Add ARCH_WORKAROUND_2 support for guests - arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests - arm64: KVM: Add ARCH_WORKAROUND_2 discovery through
[Kernel-packages] [Bug 1794807] Re: linux-kvm: 4.18.0-1001.1 -proposed tracker
*** This bug is a duplicate of bug 1795413 *** https://bugs.launchpad.net/bugs/1795413 This bug was fixed in the package linux-kvm - 4.18.0-1002.2 --- linux-kvm (4.18.0-1002.2) cosmic; urgency=medium * linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413) * Miscellaneous Ubuntu changes - kvm: [Config] CONFIG_HARDENED_USERCOPY=y - kvm: [Config] CONFIG_DEBUG_WX=y -- Seth Forshee Mon, 01 Oct 2018 09:27:19 -0500 ** Changed in: linux-kvm (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1794807 Title: linux-kvm: 4.18.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Cosmic: Fix Released Bug description: This bug is for tracking the 4.18.0-1001.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1794807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793841] Re: IP_SET modules not included in kernel build, prevents container functionality
This bug was fixed in the package linux-kvm - 4.18.0-1002.2 --- linux-kvm (4.18.0-1002.2) cosmic; urgency=medium * linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413) * Miscellaneous Ubuntu changes - kvm: [Config] CONFIG_HARDENED_USERCOPY=y - kvm: [Config] CONFIG_DEBUG_WX=y -- Seth Forshee Mon, 01 Oct 2018 09:27:19 -0500 ** Changed in: linux-kvm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1793841 Title: IP_SET modules not included in kernel build, prevents container functionality Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Fix Committed Bug description: I would like to run Ubuntu Minimal Cloud Image as the base OS on which I run Kubernetes and various other containers, but it requires ipset and various kernel modules included in the build. Is there a way to have those added by default, or a documented process for me to modify the kernel on my Minimal Cloud images? I tried to use kube-router as a routing platform for connecting the containers between Ubuntu hosts, but this requires ipset. The error from kube-router: I0921 00:19:45.773157 1 kube-router.go:207] Running /usr/local/bin/kube-router version v0.2.0, built on 2018-09-12T08:03:59-0400, go1.10.3 Failed to run kube-router: Failed to create network routing controller: Failed to create ipset set on system: ipset v6.34: Kernel error received: set type not supported After some digging, it seems I need the following modules at least compiled into the kernel as modules: root@deva-controller0:~# cat "/boot/config-`uname -r`" | grep IP_SET CONFIG_IP_SET=y CONFIG_IP_SET_MAX=256 # CONFIG_IP_SET_BITMAP_IP is not set # CONFIG_IP_SET_BITMAP_IPMAC is not set # CONFIG_IP_SET_BITMAP_PORT is not set # CONFIG_IP_SET_HASH_IP is not set # CONFIG_IP_SET_HASH_IPMARK is not set # CONFIG_IP_SET_HASH_IPPORT is not set # CONFIG_IP_SET_HASH_IPPORTIP is not set # CONFIG_IP_SET_HASH_IPPORTNET is not set # CONFIG_IP_SET_HASH_IPMAC is not set # CONFIG_IP_SET_HASH_MAC is not set # CONFIG_IP_SET_HASH_NETPORTNET is not set # CONFIG_IP_SET_HASH_NET is not set # CONFIG_IP_SET_HASH_NETNET is not set # CONFIG_IP_SET_HASH_NETPORT is not set # CONFIG_IP_SET_HASH_NETIFACE is not set # CONFIG_IP_SET_LIST_SET is not set Ubuntu Release: ~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" Any help is greatly appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1793841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793656] Re: linux-oem: 4.15.0-1020.23 -proposed tracker
*** This bug is a duplicate of bug 1794428 *** https://bugs.launchpad.net/bugs/1794428 This bug was fixed in the package linux-oem - 4.15.0-1021.24 --- linux-oem (4.15.0-1021.24) bionic; urgency=medium [ Ubuntu: 4.15.0-36.39 ] * CVE-2018-14633 - iscsi target: Use hex2bin instead of a re-implementation * CVE-2018-17182 - mm: get rid of vmacache_flush_all() entirely linux-oem (4.15.0-1020.23) bionic; urgency=medium * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656) * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume linux-oem (4.15.0-1019.22) bionic; urgency=medium * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724) * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * Miscellaneous Ubuntu changes - Rebase to 4.15.0-35.38 - [Config] update configs following rebase to 4.15.0-35.38 * drm/i915: Drop backported support for Cannonlake. (LP: #1792589) [ Ubuntu: 4.15.0-35.38 ] * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719) * device hotplug of vfio devices can lead to deadlock in vfio_pci_release (LP: #1792099) - SAUCE: vfio -- release device lock before userspace requests * L1TF mitigation not effective in some CPU and RAM combinations (LP: #1788563) - x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit - x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM - x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ * CVE-2018-15594 - x86/paravirt: Fix spectre-v2 mitigations for paravirt guests * CVE-2017-5715 (Spectre v2 s390x) - KVM: s390: implement CPU model only facilities - s390: detect etoken facility - KVM: s390: add etoken support for guests - s390/lib: use expoline for all bcr instructions - s390: fix br_r1_trampoline for machines without exrl - SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance) (LP: #1790602) - cpuidle: powernv: Fix promotion from snooze if next state disabled * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636) - powerpc: hard disable irqs in smp_send_stop loop - powerpc: Fix deadlock with multiple calls to smp_send_stop - powerpc: smp_send_stop do not offline stopped CPUs - powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled * Security fix: check if IOMMU page is contained in the pinned physical page (LP: #1785675) - vfio/spapr: Use IOMMU pageshift rather than pagesize - KVM: PPC: Check if IOMMU page is contained in the pinned physical page * Missing Intel GPU pci-id's (LP: #1789924) - drm/i915/kbl: Add KBL GT2 sku - drm/i915/whl: Introducing Whiskey Lake platform - drm/i915/aml: Introducing Amber Lake platform - drm/i915/cfl: Add a new CFL PCI ID. * CVE-2018-15572 - x86/speculation: Protect against userspace-userspace spectreRSB * Support Power Management for Thunderbolt Controller (LP: #1789358) - thunderbolt: Handle NULL boot ACL entries properly - thunderbolt: Notify userspace when boot_acl is changed - thunderbolt: Use 64-bit DMA mask if supported by the platform - thunderbolt: Do not unnecessarily call ICM get route - thunderbolt: No need to take tb->lock in domain suspend/complete - thunderbolt: Use correct ICM commands in system suspend - thunderbolt: Add support for runtime PM * random oopses on s390 systems using NVMe devices (LP: #1790480) - s390/pci: fix out of bounds access during irq setup * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit (LP: #1787993) // CVE-2018-3639 (arm64) - arm64: alternatives: Add dynamic patching feature - KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state - KVM: arm64: Avoid storing the vcpu pointer on the stack - arm/arm64: smccc: Add SMCCC-specific return codes - arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 - arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 - arm64: Add ARCH_WORKAROUND_2 probing - arm64: Add 'ssbd' command-line option - arm64: ssbd: Add global mitigation state accessor - arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation - arm64: ssbd: Restore mitigation status on CPU resume - arm64: ssbd: Introduce thread flag to control userspace mitigation - arm64: ssbd: Add prctl interface for per-thread mitigation - arm64: KVM: Add HYP per-cpu accessors - arm64: KVM: Add ARCH_WORKAROUND_2 support for guests - arm64: KVM: Handle guest's
[Kernel-packages] [Bug 1792589] Re: Drop Cannonlake support from drm/i915
This bug was fixed in the package linux-oem - 4.15.0-1021.24 --- linux-oem (4.15.0-1021.24) bionic; urgency=medium [ Ubuntu: 4.15.0-36.39 ] * CVE-2018-14633 - iscsi target: Use hex2bin instead of a re-implementation * CVE-2018-17182 - mm: get rid of vmacache_flush_all() entirely linux-oem (4.15.0-1020.23) bionic; urgency=medium * linux-oem: 4.15.0-1020.23 -proposed tracker (LP: #1793656) * Fix unusable NVIDIA GPU after S3 (LP: #1793338) - PCI: Reprogram bridge prefetch registers on resume linux-oem (4.15.0-1019.22) bionic; urgency=medium * linux-oem: 4.15.0-1019.22 -proposed tracker (LP: #1791724) * Fix I2C touchpanels' interrupt storms after system suspend (LP: #1792309) - HID: i2c-hid: Fix flooded incomplete report after S3 on Rayd touchscreen - HID: i2c-hid: Don't reset device upon system resume * Miscellaneous Ubuntu changes - Rebase to 4.15.0-35.38 - [Config] update configs following rebase to 4.15.0-35.38 * drm/i915: Drop backported support for Cannonlake. (LP: #1792589) [ Ubuntu: 4.15.0-35.38 ] * linux: 4.15.0-35.38 -proposed tracker (LP: #1791719) * device hotplug of vfio devices can lead to deadlock in vfio_pci_release (LP: #1792099) - SAUCE: vfio -- release device lock before userspace requests * L1TF mitigation not effective in some CPU and RAM combinations (LP: #1788563) - x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on 32bit - x86/speculation/l1tf: Fix off-by-one error when warning that system has too much RAM - x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ * CVE-2018-15594 - x86/paravirt: Fix spectre-v2 mitigations for paravirt guests * CVE-2017-5715 (Spectre v2 s390x) - KVM: s390: implement CPU model only facilities - s390: detect etoken facility - KVM: s390: add etoken support for guests - s390/lib: use expoline for all bcr instructions - s390: fix br_r1_trampoline for machines without exrl - SAUCE: s390: use expoline thunks for all branches generated by the BPF JIT * Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance) (LP: #1790602) - cpuidle: powernv: Fix promotion from snooze if next state disabled * Watchdog CPU:19 Hard LOCKUP when kernel crash was triggered (LP: #1790636) - powerpc: hard disable irqs in smp_send_stop loop - powerpc: Fix deadlock with multiple calls to smp_send_stop - powerpc: smp_send_stop do not offline stopped CPUs - powerpc/powernv: Fix opal_event_shutdown() called with interrupts disabled * Security fix: check if IOMMU page is contained in the pinned physical page (LP: #1785675) - vfio/spapr: Use IOMMU pageshift rather than pagesize - KVM: PPC: Check if IOMMU page is contained in the pinned physical page * Missing Intel GPU pci-id's (LP: #1789924) - drm/i915/kbl: Add KBL GT2 sku - drm/i915/whl: Introducing Whiskey Lake platform - drm/i915/aml: Introducing Amber Lake platform - drm/i915/cfl: Add a new CFL PCI ID. * CVE-2018-15572 - x86/speculation: Protect against userspace-userspace spectreRSB * Support Power Management for Thunderbolt Controller (LP: #1789358) - thunderbolt: Handle NULL boot ACL entries properly - thunderbolt: Notify userspace when boot_acl is changed - thunderbolt: Use 64-bit DMA mask if supported by the platform - thunderbolt: Do not unnecessarily call ICM get route - thunderbolt: No need to take tb->lock in domain suspend/complete - thunderbolt: Use correct ICM commands in system suspend - thunderbolt: Add support for runtime PM * random oopses on s390 systems using NVMe devices (LP: #1790480) - s390/pci: fix out of bounds access during irq setup * [Bionic] Spectre v4 mitigation (Speculative Store Bypass Disable) support for arm64 using SMC firmware call to set a hardware chicken bit (LP: #1787993) // CVE-2018-3639 (arm64) - arm64: alternatives: Add dynamic patching feature - KVM: arm/arm64: Do not use kern_hyp_va() with kvm_vgic_global_state - KVM: arm64: Avoid storing the vcpu pointer on the stack - arm/arm64: smccc: Add SMCCC-specific return codes - arm64: Call ARCH_WORKAROUND_2 on transitions between EL0 and EL1 - arm64: Add per-cpu infrastructure to call ARCH_WORKAROUND_2 - arm64: Add ARCH_WORKAROUND_2 probing - arm64: Add 'ssbd' command-line option - arm64: ssbd: Add global mitigation state accessor - arm64: ssbd: Skip apply_ssbd if not using dynamic mitigation - arm64: ssbd: Restore mitigation status on CPU resume - arm64: ssbd: Introduce thread flag to control userspace mitigation - arm64: ssbd: Add prctl interface for per-thread mitigation - arm64: KVM: Add HYP per-cpu accessors - arm64: KVM: Add ARCH_WORKAROUND_2 support for guests - arm64: KVM: Handle guest's ARCH_WORKAROUND_2 requests - arm64: KVM: Add ARCH_WORKAROUND_2 discovery through
[Kernel-packages] [Bug 1795413] Re: linux-kvm: 4.18.0-1002.2 -proposed tracker
This bug was fixed in the package linux-kvm - 4.18.0-1002.2 --- linux-kvm (4.18.0-1002.2) cosmic; urgency=medium * linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413) * Miscellaneous Ubuntu changes - kvm: [Config] CONFIG_HARDENED_USERCOPY=y - kvm: [Config] CONFIG_DEBUG_WX=y -- Seth Forshee Mon, 01 Oct 2018 09:27:19 -0500 ** Changed in: linux-kvm (Ubuntu Cosmic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1795413 Title: linux-kvm: 4.18.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Cosmic: Fix Released Bug description: This bug is for tracking the 4.18.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795595] Re: linux: 3.13.0-161.211 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795595 Title: linux: 3.13.0-161.211 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1795596 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796641] Re: linux-oem: 4.15.0-1023.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1796641 Title: linux-oem: 4.15.0-1023.26 -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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795572] Re: linux-kvm: 4.15.0-1024.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1795572 Title: linux-kvm: 4.15.0-1024.24 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Kai-Heng Feng: I did some more testing and I don't see the problem in the cosmic proposed kernel 4.18.0-9.10. 1) the live CD appeared to boot fine, but I didn't totally trust the test procedure. 2) I installed cosmic 4.18.0-9.10 from https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/15513541 and then booted the same way. This also booted fine with splash enabled. 3) I confirmed that booting the current release for bionic still caused the problem: 4.15.0-36 I also thought perhaps i was missing some module which caused the problem, but I confirmed that noveau is getting loaded in both cases. -- 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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. WORKAROUND2: Remove "splash" from kernel command line parameters by editing /etc/default/grub file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793753] Re: kernel panic - null pointer dereference on ipset operations
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1793753
Title:
kernel panic - null pointer dereference on ipset operations
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
A regression was introduced in Xenial, even prior to v4.4 Final. I did
not test prior to this kernel once I found the bug was fixed in
mainline. The bug reporter experienced crashes on machines running
iptables using ipsets. He could get a trace from the console on one of
them which is attached to the bug report.
On these machines, some ipset commands are automatically run to update the
sets, and/or to dump them (ipset restore, swap, delete ... / ipset save).
I was able to reproduce this bug as was cking. This bug was found to be
fixed by mainline commits 596cf3fe5854 and e5173418ac59.
== Fixes ==
596cf3fe5854 ("netfilter: ipset: fix race condition in ipset save, swap and
delete")
e5173418ac59 ("netfilter: ipset: Fix race between dump and swap")
== Regression Potential ==
Low. This fixes a regression and is limited to netfilter.
== Test Case ==
A test kernel was built with these patches and tested by myself and cking.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793753/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (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/1764087 Title: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37) Status in X.Org X server: Won't Fix Status in lightdm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 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-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.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 xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795583] Re: linux-aws: 4.4.0-1032.35 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1795583 Title: linux-aws: 4.4.0-1032.35 -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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796228] Re: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7ffffc00
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796228 Title: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7c00 Status in linux package in Ubuntu: Incomplete Bug description: I was playing some audio files, the following message appears, ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred And the WIFI is disconnected. I have experienced problems, (1)The gnome-sound-recorder sometime works sometime doesn't. (2) Click the LibreOffice Calc, after the empty worksheet loads, when i try to open another document by using "File->Open" on the menu, the application is not responding at all and I have to force it quit ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dcansheng 2110 F pulseaudio /dev/snd/controlC1: dcansheng 2110 F pulseaudio Date: Fri Oct 5 10:56:26 2018 Failure: oops HibernationDevice: RESUME=UUID=2bbccbb3-89de-4207-9146-7a829c7e83a8 InstallationDate: Installed on 2018-08-29 (36 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=0bcc11bd-c39c-4a17-9eb3-67098d0bca7f ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: irq/51-iwlwifi/408/0x7c00 UpgradeStatus: Upgraded to cosmic on 2018-08-30 (35 days ago) dmi.bios.date: 11/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9DCN29WW(V2.09) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo B40-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo B40-70 dmi.modalias: dmi:bvnLENOVO:bvr9DCN29WW(V2.09):bd11/21/2014:svnLENOVO:pn20392:pvrLenovoB40-70:rvnLENOVO:rnLenovoB40-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB40-70: dmi.product.family: IDEAPAD dmi.product.name: 20392 dmi.product.sku: LENOVO_MT_20392_BU_idea_FM_Lenovo B40-70 dmi.product.version: Lenovo B40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796641] Re: linux-oem: 4.15.0-1023.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1796641 Title: linux-oem: 4.15.0-1023.26 -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-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796385 Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] Status in linux package in Ubuntu: Incomplete Bug description: I can use the system for a while, then at random, the screen blinks and freezes. Must reboot. Seems to happen both with Wayland and Xorg. ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 2039 F pulseaudio /dev/snd/controlC1: greg 2039 F pulseaudio Date: Tue Oct 2 15:56:23 2018 Failure: oops InstallationDate: Installed on 2018-09-28 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: X99-UD4-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd06/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UD4-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796433] Re: Ubuntu 18.10 regression: nvidia driver does not work
Hello, It would be possible to create this report with: $ ubuntu-bug linux To add all the necessary technical information Thanks for helping to create a better Ubuntu... -- Cristian Aravena Romero (caravena) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Incomplete -- 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/1796433 Title: Ubuntu 18.10 regression: nvidia driver does not work Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Problems started after upgrade to 18.10 and first reboot. Symptoms: * Login screen appears * After providing credentials desktop does not start Part of dmesg: - ... [ 10.482929] resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000c-0x000d window] [ 10.483149] caller os_map_kernel_space.part.9+0xd4/0x120 [nvidia] mapping multiple BARs [ 10.801510] [ cut here ] [ 10.801512] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)! [ 10.801522] WARNING: CPU: 3 PID: 1188 at mm/usercopy.c:81 usercopy_warn+0x81/0xa0 [ 10.801523] Modules linked in: snd_hda_codec_hdmi binfmt_misc nvidia_uvm(POE) nls_iso8859_1 wmi_bmof mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc nvidia_drm(POE) aesni_intel nvidia_modeset(POE) aes_x86_64 crypto_simd cryptd glue_helper nvidia(POE) intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl_perf ath9k snd_seq ath9k_common ath9k_hw drm_kms_helper joydev ath snd_seq_device input_leds snd_timer mac80211 drm snd cfg80211 ipmi_devintf ir_rc6_decoder ipmi_msghandler fb_sys_fops syscopyarea soundcore mei_me sysfillrect sysimgblt mei rc_rc6_mce video nuvoton_cir mac_hid rc_core wmi sch_fq_codel [ 10.801559] nct6775 hwmon_vid coretemp parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid gpio_ich ahci r8169 libahci lpc_ich mii [ 10.801572] CPU: 3 PID: 1188 Comm: Xorg Tainted: P OE 4.18.0-8-generic #9-Ubuntu ... - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 02:03:52 2018 InstallationDate: Installed on 2016-01-06 (1003 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
The error appears to be different that the error posted in the bug description. The descriptions mentions a tx_timeout. Are you seeing that error still as well? Also, the descriptions seems to indication this is a regression. Was there a specific prior kernel version that did not exhibit this but? -- 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/1779756 Title: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796641] Re: linux-oem: 4.15.0-1023.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1796641 Title: linux-oem: 4.15.0-1023.26 -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-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795092] Re: xubuntu 18.10 daily image (x86) fails to boot - initramfs
Thanks for all the testing, Chris. It leaves me a little baffled. That said, to Joseph et al, two questions: 1. This seems to be the same messages from 1794922 but slightly different symptoms. Should they be considered as the same? 2. With the kernel apparently working in Bionic, that suggests some sort of regression in some component outside the kernel that is calling on the USB. What might be likely candidates? -- 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/1795092 Title: xubuntu 18.10 daily image (x86) fails to boot - initramfs Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: x86 daily image (32bit) XUBUNTU 18.10 - booted & ran fine on dell latitude d610 - booted & ran fine on ibm thinkpad t43 fails on - hp dc7700 small form factor desktop - dell 755 desktop - lenovo thinkpad x201 I don't get the "try xubuntu / install xubuntu" screen, instead it eventually drops to "BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands (initramfs) Unable to find a medium containing a live file system Note: I typed the messages in so typos may exist I suspect it's the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922 where Walter (wxl) gave a possible link to http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow- on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html I've been testing xubuntu 18.10 daily images for awhile (but not logging on qa-tracker - my bad, sorry!!!) without issue on t43 & d610, and only rarely booting on other boxes (like 755/dc7700/..) It may have been ~15-20 days since last tested on dell 755; but it worked fine back then (& prior) but due to my QA-tracking omission, we can't be exact - sorry again! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
** Bug watch added: Linux Kernel Bug Tracker #201291 https://bugzilla.kernel.org/show_bug.cgi?id=201291 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201291 Importance: Unknown Status: Unknown -- 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/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in linux package in Ubuntu: Incomplete Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796355] Re: USB-C ValueLine network adapter fails to connect
There's something wrong going on here. I first reported this issue as a 'linux' bug, based on a hasty reading of documentation. I never finished that report, so I expect that to be incomplete. Shortly afterwards I re-reported it as a probable NetworkManager issue. It seems that these two issues have got the same #number. Any confusion about whether this is confirmed or not is, I'm afraid of your own making. -- 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/1796355 Title: USB-C ValueLine network adapter fails to connect Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with no external identifying information. lsusb lists it as Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp. It works fine on a Windows 10 system (same hardware platform), where it's identified as a 10/100/1000 Realtek adapter. When I connect it to my system (Asus Zenbook UX490UA) internal lights go on, but no connection is produced. The network icon (upper right) is shown briefly, then disappears, the is show, then disappears. After some time it seems to give up. Kernel logs show repeated occurrences of: Oct 5 17:02:22 athasus kernel: [ 317.843590] usb 4-2: new SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 317.863719] usb 4-2: New USB device found, idVendor=0bda, idProduct=8153 Oct 5 17:02:22 athasus kernel: [ 317.863728] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Oct 5 17:02:22 athasus kernel: [ 317.863735] usb 4-2: Product: USB 10/100/1000 LAN Oct 5 17:02:22 athasus kernel: [ 317.863741] usb 4-2: Manufacturer: Realtek Oct 5 17:02:22 athasus kernel: [ 317.863745] usb 4-2: SerialNumber: 0100 Oct 5 17:02:22 athasus kernel: [ 318.000268] usb 4-2: reset SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 318.057875] r8152 4-2:1.0 eth0: v1.09.9 Oct 5 17:02:22 athasus kernel: [ 318.138042] r8152 4-2:1.0 enxa0cec809bf58: renamed from eth0 Oct 5 17:02:22 athasus kernel: [ 318.170397] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.176359] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.354745] r8152 4-2:1.0 enxa0cec809bf58: Stop submitting intr, status -71 Oct 5 17:02:22 athasus kernel: [ 318.543737] usb 4-2: USB disconnect, device number 121 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:35:17 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE ATH 79577e92-4b01-46c4-bbff-2088aaf0750a wifi 1538753528 fre 5 okt 2018 17:32:08 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 ATH 79577e92-4b01-46c4-bbff-2088aaf0750a /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume
Hmmm, do you still see this if you cold boot with the quirk? -- 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/1790454 Title: Bluetooth (btintel) stops working after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: I run cosmic on my Dell Latitude E7470, which has an intel usb bluetooth device (8087:0a2b). Sometimes (not every time) after a suspend/resume cycle, my laptop's bluetooth stops working. hciconfig shows: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 and dmesg tells me (various combinations of): [237660.728312] Bluetooth: hci0: command tx timeout [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout [237925.202500] Bluetooth: hci0: Reading Intel version information failed (-110) Trying to reinitialize the device by reloading the driver has no effect: ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe btusb shows in dmesg: [237938.219190] usbcore: deregistering interface driver btusb [237938.601731] usbcore: registered new interface driver btusb [237940.626392] Bluetooth: hci0: Reading Intel version information failed (-110) [237940.626426] Bluetooth: hci0: command tx timeout Strangely enough, reloading the module sometimes does work, upon which the kernel tells me : aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download to complete aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Looking further back in the kernel log, the difference between failed and successful resumes seems to be this: Resume with broken bt: [236481.370814] Restarting tasks ... [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110) Resume with working bt: [16562.706263] Restarting tasks ... [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [16562.716050] Bluetooth: hci0: Device revision is 5 [16562.716052] Bluetooth: hci0: Secure boot is enabled [16562.716053] Bluetooth: hci0: OTP lock is enabled [16562.716054] Bluetooth: hci0: API lock is enabled [16562.716055] Bluetooth: hci0: Debug lock is disabled [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs [16564.203091] Bluetooth: hci0: Waiting for device to boot [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed and everything works fine after that. The first kernel on which this error occurred was 4.17.0-6-generic. Before that, I used 4.15.0-25-generic which works perfectly. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bas4871 F...m pulseaudio /dev/snd/controlC0: bas4871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=UUID=16195e13-9fb3-41b2-9671-fb4e1df1ff93 #RESUME=/dev/dm-2 #RESUME=/dev/mapper/regan-swap InstallationDate: Installed on 2016-12-22 (619 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** Changed in: ubuntu-power-systems Status: Triaged => 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/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788782] Re: Ubuntu 16.04.03(P8/Tuleta): SEGV-panic in smp_send_reschedule(). Machine keeps rebooting with oops message even after reboot.
Marking as "Incomplete" while waiting for test kernel results to be posted. ** Changed in: ubuntu-power-systems Status: In Progress => 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/1788782 Title: Ubuntu 16.04.03(P8/Tuleta): SEGV-panic in smp_send_reschedule(). Machine keeps rebooting with oops message even after reboot. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-07-25 06:18:00 == ---Problem Description--- Ubuntu 16.04.03: Fadump fails when dump is triggered after dlpar operation. Machine keeps rebooting with oops message even after reboot. ---Environment-- Kernel Build: Ubuntu 16.04.03 System Name : Tuleta Model/Type : P8 Platform: LPAR ---Uname output--- root@tuleta4u-lp9:/home/ubuntu# uname -a Linux tuleta4u-lp9 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:17:50 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- 1. Configure fadump. 2. Add memory with dlpar operation. 3. Remove memory with dlpar operation. 4. Check fadump service is up. 5. Trigger crash ---Logs Attaching full console log. [ OK ] Reached target Remote File Systems. Starting LSB: automatic crash report generation... Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"... Starting LSB: Load kernel image with kexec... Starting LSB: daemon to balance interrupts for SMP systems... Starting Permit User Sessions... [ 10.997932] Unable to handle kernel paging request for data at address 0xa000 [ 10.997948] Faulting instruction address: 0xc00459f4 [ 10.997956] Oops: Kernel access of bad area, sig: 11 [#1] [ 10.997960] SMP NR_CPUS=2048 [ 10.997961] NUMA [ 10.997965] pSeries [ 10.997971] Modules linked in: binfmt_misc vmx_crypto pseries_rng ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c ibmvscsi crc32c_vpmsum [ 10.998013] CPU: 5 PID: 2212 Comm: kdump-config Not tainted 4.10.0-28-generic #32~16.04.2-Ubuntu [ 10.998020] task: c000fd8b8c00 task.stack: c000fc364000 [ 10.998026] NIP: c00459f4 LR: c0127628 CTR: c0141390 [ 10.998031] REGS: c000fc367a60 TRAP: 0300 Not tainted (4.10.0-28-generic) [ 10.998037] MSR: 8280b033 [ 10.998046] CR: 28222824 XER: [ 10.998053] CFAR: c0008860 DAR: a000 DSISR: 4000 SOFTE: 0 [ 10.998053] GPR00: c0127628 c000fc367ce0 c14ad100 0007 [ 10.998053] GPR04: c01fd47e5800 0002 0001 0800 [ 10.998053] GPR08: 0804 a000 [ 10.998053] GPR12: 2842 cfb82d00 2200 0100012ab908 [ 10.998053] GPR16: 0001 [ 10.998053] GPR20: 0060 [ 10.998053] GPR24: c01fd489d980 c01fd47e5880 c000fd934b00 [ 10.998053] GPR28: c01fd47e6044 c01f4fee3280 0007 c01f4fee3280 [ 10.998127] NIP [c00459f4] smp_send_reschedule+0x24/0x80 [ 10.998135] LR [c0127628] resched_curr+0x168/0x190 [ 10.998139] Call Trace: [ 10.998143] [c000fc367ce0] [c0127628] resched_curr+0x168/0x190 (unreliable) [ 10.998152] [c000fc367d10] [c0128728] check_preempt_curr+0xc8/0xf0 [ 10.998159] [c000fc367d40] [c012b3bc] wake_up_new_task+0x16c/0x2d0 [ 10.998167] [c000fc367da0] [c00e7304] _do_fork+0x174/0x520 [ 10.998175] [c000fc367e30] [c000b410] ppc_clone+0x8/0xc [ 10.998180] Instruction dump: [ 10.998185] 6000 6000 6042 3c4c0146 38427730 7c0802a6 f8010010 6000 [ 10.998196] 3d220006 e9297bc0 2fa9 4d9e0020 2fa9 419e0044 7c0802a6 [ 10.998210] ---[ end trace 7ad373050ad8891c ]--- [ 11.003011] == Comment: #1 - PAVITHRA R. PRAKASH - 2017-07-25 06:24:46 == == Comment: #8 - PAVITHRA R. PRAKASH - 2017-08-29 08:35:18 == I could not recreate the issue mentioned in bug, But machine is going in to Error state after below steps. 1. Activate the partition with 130GB. 2. Add 20GB. 3. Remove 20GB. 4. Trigger fadump. Thanks, Pavithra == Comment: #9 - Hari Krishna Bathini - 2017-08-29 11:03:53 == (In reply to
[Kernel-packages] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Marking as "Incomplete" while waiting for test kernel results to be posted. ** Changed in: ubuntu-power-systems Status: In Progress => 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/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795413] Re: linux-kvm: 4.18.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1795413 Title: linux-kvm: 4.18.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1791663 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795413/+subscriptions -- Mailing list: https://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 1796608] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’; did you mean ‘init_t
*** This bug is a duplicate of bug 1757008 *** https://bugs.launchpad.net/bugs/1757008 Hello, Was able to get this to load. This is a new install of ubuntu 18.04. Had to run the "install -f" cmd a few times, then the updates worked. Mark Dannunzio > On October 7, 2018 at 10:26 PM Daniel van Vugt > wrote: > > > *** This bug is a duplicate of bug 1757008 *** > https://bugs.launchpad.net/bugs/1757008 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1757008, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** Summary changed: > > - bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed > to build > + bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed > to build [error: implicit declaration of function ‘init_timer’; did you mean > ‘init_timers’?] > > ** This bug has been marked a duplicate of bug 1757008 >Broadcom wireless drivers failed to build [error: implicit declaration of > function ‘init_timer’] > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1796608 > > Title: > bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module > failed to build [error: implicit declaration of function ‘init_timer’; > did you mean ‘init_timers’?] > > Status in bcmwl package in Ubuntu: > New > > Bug description: > package will not load > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 > ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 > Uname: Linux 4.15.0-29-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > DKMSKernelVersion: 4.15.0-29-generic > Date: Sun Oct 7 21:26:55 2018 > DuplicateSignature: > dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2: > error: implicit declaration of function ‘init_timer’; did you mean > ‘init_timers’? [-Werror=implicit-function-declaration] > InstallationDate: Installed on 2018-10-05 (2 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > PackageVersion: 6.30.223.248+bdcom-0ubuntu8 > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3ubuntu1 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.3 > SourcePackage: bcmwl > Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1796608/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1796608 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?] Status in bcmwl package in Ubuntu: New Bug description: package will not load ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DKMSKernelVersion: 4.15.0-29-generic Date: Sun Oct 7 21:26:55 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2: error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2018-10-05 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageVersion: 6.30.223.248+bdcom-0ubuntu8 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1796608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
89.93
0| 0| 3| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
93.26
This fix (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze
if next state disabled") is in the -next branch of the powerpc tree and
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)
Since we are already on kernel 4.18.0.8.9 in cosmic that incl. the mentioned patches: $ git log --oneline | grep "Check if IOMMU page is contained in the pinned physical page" 76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page fheimes@T570:~/ubuntu-cosmic$ git tag --contains 76fa497 Ubuntu-4.18.0-7.8 Ubuntu-4.18.0-8.9 Ubuntu-4.18.0-9.10 v4.18 $ git log --oneline | grep "powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang" bd5050e powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang $ git tag --contains bd5050e Ubuntu-4.18.0-7.8 Ubuntu-4.18.0-8.9 Ubuntu-4.18.0-9.10 v4.18 $ git log --oneline | grep "powerpc/mm: Change function prototype" e4c1112 powerpc/mm: Change function prototype $ git tag --contains e4c1112 Ubuntu-4.18.0-7.8 Ubuntu-4.18.0-8.9 Ubuntu-4.18.0-9.10 v4.18 $ git log --oneline | grep "powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly" f069ff3 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly $ git tag --contains f069ff3 Ubuntu-4.18.0-7.8 Ubuntu-4.18.0-8.9 Ubuntu-4.18.0-9.10 v4.18 this can be set to Fix Released for cosmic, too. -- 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/1789772 Title: tlbie master timeout checkstop (using NVidia/GPU) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: A hung state machine in the chip's NMU logic can trigger a fatal condition that will be flagged by hardware through a checkstop. Hence, customers that have a Power 9 Whitherspoon (equipped with GPUs) will experience a crash on their server when using NVIDIA's toolkit. The server will crash with the following hardware failing message: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0 In this case, a `NCUFIR[10] tlbie master timeout` has been observed by only starting the NVIDIA ATS driver. This issue is being triggered because the NMU logic is getting stuck when a page is upgraded from RO -> RW without a following tlbie. This is addressed with the following patches: bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype 044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from radix.h to pgtable-radix.c f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790602] Re: Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next state disabled (performance)
Since we are at kernel level 4.18.0.8.9 in cosmic that incl. the fix:
$ git log --oneline | grep "cpuidle: powernv: Fix promotion from snooze if next
state disabled"
0a4ec6a cpuidle: powernv: Fix promotion from snooze if next state disabled
$ git tag --contains 0a4ec6a
Ubuntu-4.18.0-7.8
Ubuntu-4.18.0-8.9
Ubuntu-4.18.0-9.10
v4.18
This can be marked as Fix Released for cosmic, too.
--
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/1790602
Title:
Ubuntu18.04.1: cpuidle: powernv: Fix promotion from snooze if next
state disabled (performance)
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== Comment: #0 - Michael Ranweiler - 2018-09-04
00:50:14 ==
The CPUs remain in snooze state on an idle system when only the
shallow states disabled resulting in increased power consumption.
The commit 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze
to deeper idle state") introduced a timeout for the snooze idle state so that
it could be eventually be promoted to a deeper idlestate. The snooze
timeout value is static and set to the target residency of the next idle
state, which would train the cpuidle governor to pick the next idle state
eventually.
The unfortunate side-effect of this is that if the next idle state(s) is
disabled, the CPU will forever remain in snooze, despite the fact that the
system is completely idle, and other deeper idle states are available.
This patch fixes the issue by dynamically setting the snooze timeout to the
target residency of the next enabled state on the device.
Before Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01297 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 96.41| 0.00| 0.00
0| 8| 1| 96.43| 0.00| 0.00
0| 8| 2| 96.47| 0.00| 0.00
0| 8| 3| 96.35| 0.00| 0.00
0| 8| 4| 96.37| 0.00| 0.00
0| 8| 5| 96.37| 0.00| 0.00
0| 8| 6| 96.47| 0.00| 0.00
0| 8| 7| 96.47| 0.00| 0.00
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1, stop2)
disabled:
$ cpupower monitor sleep 30
sleep took 30.05033 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 16| 0| 89.79| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 1| 90.12| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 2| 90.21| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
0| 16| 3| 90.29| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
0.00
After Patch:
POWER8 : Only nap disabled.
$ cpupower monitor sleep 30
sleep took 30.01200 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | Nap | Fast
0| 8| 0| 16.58| 0.00| 77.21
0| 8| 1| 18.42| 0.00| 75.38
0| 8| 2| 4.70| 0.00| 94.09
0| 8| 3| 17.06| 0.00| 81.73
0| 8| 4| 3.06| 0.00| 95.73
0| 8| 5| 7.00| 0.00| 96.80
0| 8| 6| 1.00| 0.00| 98.79
0| 8| 7| 5.62| 0.00| 94.17
POWER9: Shallow states (stop0lite, stop1lite, stop2lite, stop0, stop1,
stop2) disabled:
$ cpupower monitor sleep 30
sleep took 30.02110 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop |
stop
0| 0| 0| 0.69| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 9.39|
89.70
0| 0| 1| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.05|
93.21
0| 0| 2| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
89.93
0| 0| 3| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00| 0.00|
93.26
This fix (commit 0a4ec6aa035a "cpuidle: powernv: Fix promotion from snooze
if next state disabled") is in the -next branch of the powerpc tree and
upstream:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/cpuidle/cpuidle-powernv.c?id=0a4ec6aa035a52c422eceb2ed51ed88392a3d6c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790602/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
That already in the current cosmic kernel:
$ git log --oneline | grep "Check if IOMMU page is contained in the pinned
physical page"
76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page
$ git tag --contains 76fa497
Ubuntu-4.18.0-7.8
Ubuntu-4.18.0-8.9
Ubuntu-4.18.0-9.10
v4.18
So can be marked as Fix Released for cosmic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1785675
Title:
Security fix: check if IOMMU page is contained in the pinned physical
page
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
mainline commit 1463edca6734 as a prereq.
Both these commits have already been cc'd to upstream stable, but they
have not landed in Bionic as of yet.
== Fixes ==
1463edca6734 ("vfio/spapr: Use IOMMU pageshift rather than pagesize")
76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned
physical page")
== Regression Potential ==
Low. These commits have also been sent to upstream stable, so have had
additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06
12:27:59 ==
Please, add the following security fix to the distro kernel:
76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
Also already available in the 4.14 stable tree:
58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
And in the 4.17 stable tree:
970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785675] Re: Security fix: check if IOMMU page is contained in the pinned physical page
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1785675
Title:
Security fix: check if IOMMU page is contained in the pinned physical
page
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
mainline commit 1463edca6734 as a prereq.
Both these commits have already been cc'd to upstream stable, but they
have not landed in Bionic as of yet.
== Fixes ==
1463edca6734 ("vfio/spapr: Use IOMMU pageshift rather than pagesize")
76fa4975f3ed ("KVM: PPC: Check if IOMMU page is contained in the pinned
physical page")
== Regression Potential ==
Low. These commits have also been sent to upstream stable, so have had
additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Leonardo Augusto Guimaraes Garcia - 2018-08-06
12:27:59 ==
Please, add the following security fix to the distro kernel:
76fa4975f3ed KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
Also already available in the 4.14 stable tree:
58113603a4ea KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
And in the 4.17 stable tree:
970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned
physical page
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1785675/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789772] Re: tlbie master timeout checkstop (using NVidia/GPU)
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789772 Title: tlbie master timeout checkstop (using NVidia/GPU) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: A hung state machine in the chip's NMU logic can trigger a fatal condition that will be flagged by hardware through a checkstop. Hence, customers that have a Power 9 Whitherspoon (equipped with GPUs) will experience a crash on their server when using NVIDIA's toolkit. The server will crash with the following hardware failing message: Unrecoverable Hardware Failure, (Critical) A system checkstop occurred (AffectedSubsystem: Canister/Appliance, PID: 19703), Resolved: 0 In this case, a `NCUFIR[10] tlbie master timeout` has been observed by only starting the NVIDIA ATS driver. This issue is being triggered because the NMU logic is getting stuck when a page is upgraded from RO -> RW without a following tlbie. This is addressed with the following patches: bd5050e38aec3055ff4257ade987d808ac93b582 powerpc/mm/radix: Change pte relax sequence to handle nest MMU hang e4c1112c3fc503fc78379fa61450bfda3f0717fe powerpc/mm: Change function prototype 044003b52a78bcbda7103633c351da16505096cf powerpc/mm/radix: Move function from radix.h to pgtable-radix.c f069ff396d657ac7bdb5de866c3ec28b8d08d953 powerpc/mm/hugetlb: Update huge_ptep_set_access_flags to call __ptep_set_access_flags directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1789772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794477] Re: [Azure] Accelerated networking broken in 18.10 daily
This is now broken also on Hyper-V VMs, tested with 4.18.0-8-generic and daily 18.10 server -- 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/1794477 Title: [Azure] Accelerated networking broken in 18.10 daily Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: While testing Ubuntu 18.10 daily from cloud-images repo, on Azure, we discovered that accelerated networking wasn’t working inside the VM. No VF shows up inside the VM and lspci didn’t show any Mellanox drivers in use. We tested the daily build on Hyper-V also, but there the Mellanox VF is functional, with the same mlx4 drivers. To give more details about this: • No mellanox logs are showing up in dmesg or syslog. • Modinfo mlx4_core/mlx4_en finds the module, but lsmod doesn’t show it as loaded, although Accelerated Networking is enabled for the Azure VM, so this should happen transparently. • Modprobe -r mlx4_core && modprobe mlx4_core is giving 0 exit code, but nothing really happens. And no Mellanox messages are logged in dmesg/syslog. - There are no entries in the logs to show anything about the drivers or netvsc/pci-hyperv that might relate to this issue. Kernel: 4.18.0-7-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709784] Re: KVM on 16.04.3 throws an error
As this ticket only relates to Xenial and 4.4 kernel, marking as "Fix Released". ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruction dump: [ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 340.182938] ---[ end trace bc5080cb7d18f102 ]--- [ 340.276202] This was with the
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: systemd (Ubuntu Xenial) 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794763] Re: High utilisation of memory freezes Ubuntu completely for a long time, with an extremely high access to the hard disk
** Tags added: kernel-bug-reported-upstream -- 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/1794763 Title: High utilisation of memory freezes Ubuntu completely for a long time, with an extremely high access to the hard disk Status in linux package in Ubuntu: Triaged Bug description: I observed this occasionally on Ubuntu 16.04 and very frequently on Ubuntu 18.04 (Ubuntu 18.04.1 LTS) I can reproduce it with a regular use of Chromium, Firefox or LibreOffice, by instance. In a Ubuntu system, when there is "little" free memory, if I open some new tabs on the browser, the system freezes and it's impossible to do anything. Also, there are some worksheets that I can open quickly and without problems when I have a lot of free memory, but when I try to open the same document with little free memory, the system freezes. Then, sometimes the system becomes very very slow but I can change to a tty and enter some commands to kill Chromium, Firefox or LibreOffice... and the system responds again. Sometimes, after and hour or so the system accept commands again. Although it's also possible "recover" the system using SysRq memory-full-oom-kill(f), but with the consequence of the crashing of one or more applications (it doesn't have to be the one that apparently caused the problem) In all cases, the hard disk starts to work intensely... until the system has returned to "normal" condition. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/28087/fd/23: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC1: carles 1811 F pulseaudio /dev/snd/controlC0: carles 1811 F pulseaudio Date: Thu Sep 27 15:10:47 2018 HibernationDevice: RESUME=UUID=f06d0abe-a1c3-43f8-8413-9dac4c4a2c8d InstallationDate: Installed on 2016-03-07 (934 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: HP HP ProDesk 600 G2 SFF ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic root=UUID=31064b95-e0f1-4307-a03e-8cc5b5210093 ro rootflags=subvol=@ quiet splash reboot=pci vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-06 (21 days ago) dmi.bios.date: 07/17/2018 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.36 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC60572P2 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.36:bd07/17/2018:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794763/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
