[Kernel-packages] [Bug 1823618] 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 1823618 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe package in Ubuntu: New Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823547] Re: Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700
I cannot add a kernel log, as I wasn't even able to boot the system and install the Operating System. ** Description changed: - I have the same issue, but with a Ryzen 7 1700 with the following - setups: + I have this issue with a Ryzen 7 1700 with the following setups: Setup 1: Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Asus Mining Radeon RX 470 4G GDDR5 SSD: 240 GB WD Green Setup 2: Motherboard: ASRock AB350M Pro4 (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Sapphire Radeon RX 550 2G GDDR5 SSD: 240 GB WD Green The issue first started after installing the second GPU on each of the systems. I can't even boot the system, as the errors appear right after BIOS initialization. The errors are like: [exerpt] AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out ... AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7560] Entering emergecy mode. Exit the shell to continue. Type "journalctl" to view system logs. AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb75d0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7700] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7630] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7660] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb7690] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76c0] AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=22:00.0 address=0x000174bb76f0] ... AMD-Vi: Completion-Wait loop timed out AMD-Vi: Event logged [IO_PAGE_FAULT device=23:00.3 domain=0x000 address=0xfffd3990 flags=0x0070] ... Buffer I/O error on dev dm-0, logical block 104857472, async page read Buffer I/O error on dev dm-0, logical block 104857473, async page read Buffer I/O error on dev dm-0, logical block 104857474, async page read Buffer I/O error on dev dm-0, logical block 104857475, async page read Buffer I/O error on dev dm-0, logical block 104857476, async page read Buffer I/O error on dev dm-0, logical block 104857477, async page read . I can't even install any new system, because the errors are the same... After some research I discovered that it is a IOMMU issue. I turned IOMMU off on both motherboards, and I managed to boot the system. I have been trying with CentOS 7, Ubuntu 18.04.2 and Fedora 29. I am an architect and I use blender for GPU rendering (this is the idea of having two cards), but the AMDGPU-Pro driver from the AMD's website (the only one that Blender uses for GPU rendering, as it can't use the open one) affects the way Gnome works on Xorg. In Ubuntu 18.04 Gnome doesn't start at all, it hangs up stating an error about snapd. Even after purging snapd, it still doesn't start... Fedora 29 is the only one that works, but the official AMDGPU-Pro don't work in it, thus I don't have the GPU rendering available. - Any ideas? Two years have passed, or probably even more, and this IOMMU issues on AMD are yet not resolved... I have two different chipsets on my MBs (B350 and B450) and the issues are still there... Please help. Last resort is to start using Windows, after 15 years of using only Linux, but I don't really find this very appealing... Thanks. ** 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/1823547 Title: Kernel crash during boot with IOMMU - on Dual GPU AMD system using Ryzen 7 1700 Status in linux package in Ubuntu: Confirmed Bug description: I have this issue with a Ryzen 7 1700 with the following setups: Setup 1: Motherboard: Gigabyte B450 Aorus M (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Asus Mining Radeon RX 470 4G GDDR5 SSD: 240 GB WD Green Setup 2: Motherboard: ASRock AB350M Pro4 (Latest BIOS installed) RAM: 32 GB DDR4 Crucial 3000 Mhz GPU1: Sapphire Radeon RX 580 Nitro+ Special Edition 8GB GDDR5 GPU2: Sapphire Radeon RX 550 2G GDDR5 SSD: 240 GB WD Green The issue first started after installing the second GPU on each of the systems. I can't even boot the system, as the errors appear right after BIOS initialization. The errors are like: [exerpt] AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out AMD-Vi: Completion-Wait loop timed out ... AMD-Vi: E
[Kernel-packages] [Bug 1823428] Re: linux-oem ftbfs in disco
also in cosmic: https://launchpadlibrarian.net/418308443/buildlog_ubuntu-cosmic-amd64.linux-oem_4.15.0-1034.39_BUILDING.txt.gz ** Tags added: rls-cc-incoming -- 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/1823428 Title: linux-oem ftbfs in disco Status in linux-oem package in Ubuntu: New Bug description: https://launchpadlibrarian.net/417924465/buildlog_ubuntu-disco-amd64 .linux-oem_4.15.0-1034.39_BUILDING.txt.gz HOSTLD scripts/mod/modpost HOSTCC scripts/selinux/genheaders/genheaders In file included from /<>/scripts/selinux/genheaders/genheaders.c:19: /<>/security/selinux/include/classmap.h:247:2: error: #error New address family defined, please update secclass_map. #error New address family defined, please update secclass_map. ^ make[6]: *** [scripts/Makefile.host:90: scripts/selinux/genheaders/genheaders] Error 1 make[5]: *** [/<>/scripts/Makefile.build:606: scripts/selinux/genheaders] Error 2 make[4]: *** [/<>/scripts/Makefile.build:606: scripts/selinux] Error 2 make[3]: *** [/<>/Makefile:589: scripts] Error 2 make[2]: *** [/<>/Makefile:278: __build_one_by_one] Error 2 make[2]: Leaving directory '/<>/debian/build/build-oem' make[1]: *** [Makefile:146: sub-make] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules.d/2-binary-arch.mk:31: /<>/debian/stamps/stamp-prepare-tree-oem] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1823428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823429] Re: linux-oracle ftbfs in disco
also in cosmic: https://launchpadlibrarian.net/418308401/buildlog_ubuntu-cosmic-amd64.linux-oracle_4.15.0-1009.11_BUILDING.txt.gz ** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1823429 Title: linux-oracle ftbfs in disco Status in linux-oracle package in Ubuntu: New Bug description: https://launchpadlibrarian.net/417924791/buildlog_ubuntu-disco-amd64 .linux-oracle_4.15.0-1010.12_BUILDING.txt.gz HOSTLD scripts/mod/modpost HOSTCC scripts/selinux/genheaders/genheaders In file included from /<>/scripts/selinux/genheaders/genheaders.c:19: /<>/security/selinux/include/classmap.h:247:2: error: #error New address family defined, please update secclass_map. #error New address family defined, please update secclass_map. ^ make[6]: *** [scripts/Makefile.host:90: scripts/selinux/genheaders/genheaders] Error 1 make[5]: *** [/<>/scripts/Makefile.build:606: scripts/selinux/genheaders] Error 2 make[4]: *** [/<>/scripts/Makefile.build:606: scripts/selinux] Error 2 make[3]: *** [/<>/Makefile:589: scripts] Error 2 make[2]: *** [/<>/Makefile:278: __build_one_by_one] Error 2 make[2]: Leaving directory '/<>/debian/build/build-oracle' make[1]: *** [Makefile:146: sub-make] Error 2 make[1]: Leaving directory '/<>' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1823429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_scr
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-410 in Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size Status in budgie-desktop package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c WORKAROUNDS Don't use kernel parameter nvidia-drm.modeset=1 - or - Before trying to log in: 1. Ctrl+Alt+F4, log in to VT4 and run: sudo Xorg :4 vt4 2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in normally. ORIGINAL DESCRIPTION I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3 vertical displays. I changed to the X.org driver and rebooted. This error popped up on reboot. And now only one display is working. This one display is only working in landscape instead of portrait mode. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: budgie-core 10.5-0ubuntu1 Uname: Linux 5.0.2-050002-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Apr 1 09:16:50 2019 ExecutablePath: /usr/bin/budgie-wm InstallationDate: Installed on 2019-01-10 (80 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) ProcCmdline: budgie-wm ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: budgie-desktop StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0 Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1823618/+attachment/5254000/+files/dmidecode.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
Confirmed to silence the bot, attaching a few logs on my own since apport refuses to do so -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
Setting linux-hwe per discussion ** Package changed: linux-signed-hwe (Ubuntu) => linux-hwe (Ubuntu) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) + Only resolves with a hard shutdown (5 sec power press), pressing it + shortly doesn't help - also the keyboard shortcuts for and further e.g. + CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. ** Tags added: regression-update ** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. + + So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 + right away. ** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD) + - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999)
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
** Attachment added: "lspci.log" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1823618/+attachment/5254001/+files/lspci.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
Apport still refuses to attach data :-/ But I since I have the journal with the crash attached that should be ok. ** Changed in: linux-hwe (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-hwe (Ubuntu) Status: New => Confirmed ** 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/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - - boot into 4.18.0-17-generic + - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823320] Re: Asus Zenbook 14 UX433F - NumPad
*** This bug is a duplicate of bug 1810183 *** https://bugs.launchpad.net/bugs/1810183 I see a message running apport-collect 1823320 saying that I'm not the owner of the bug report or it is a duplicate. I subscribed the duplicated bug report, if you need additional info from logs please let me know. Thanks, Andrea -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823320 Title: Asus Zenbook 14 UX433F - NumPad Status in linux package in Ubuntu: Incomplete Bug description: I just bought this amazing laptop, installed Linux Ubuntu 18.04 LTS, upgraded the kernel to v5.0.6 to get sound working. Everything is working except the new feature of the numpad keys within the touchpad. Discussion already opened in the past but never solved: https://unix.stackexchange.com/questions/494400/asus-zenbook- ux433-ux333-configure-touchpad-embedded-numpad-on-linux https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183 Thanks for any hints To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux-hwe (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-hwe (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-hwe (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Only resolves with a hard shutdown (5 sec power press), pressing it shortly doesn't help - also the keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
@arighi - will this fix go into disco soon? I have an OVS upload for a high fix blocked on failing tests on i386 - just need to know whether to update the hinter or wait for the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_stor
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
We discussed if just the Graphics output might be dead, I'll set up SSH and try to retrigger. ** Description changed: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) - Only resolves with a hard shutdown (5 sec power press), pressing it - shortly doesn't help - also the keyboard shortcuts for and further e.g. - CTRL+ALT+F* does not switch to consoles anymore. + Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to + consoles anymore. I can only hard reset via 5sec power button. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I can only hard reset via 5sec power button. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823655] [NEW] Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work
Public bug reported: As suggested in following thread; https://forum.snapcraft.io/t/second-sd-card-on-rpi3-cm3-with-ubuntu- core-18/10465 a bug report. The configuration works for a Ubuntu Core 16 device. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1823655 Title: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work Status in linux-raspi2 package in Ubuntu: New Bug description: As suggested in following thread; https://forum.snapcraft.io/t/second-sd-card-on-rpi3-cm3-with-ubuntu- core-18/10465 a bug report. The configuration works for a Ubuntu Core 16 device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814054] Re: BUG: unable to handle kernel paging request at ee835a95
*** This bug is a duplicate of bug 1813244 *** https://bugs.launchpad.net/bugs/1813244 ** This bug is no longer a duplicate of bug 1736390 openvswitch: kernel oops destroying interfaces on i386 ** This bug has been marked a duplicate of bug 1813244 systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814054 Title: BUG: unable to handle kernel paging request at ee835a95 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Incomplete Bug description: Booting Bionic i386 in a VM and running the following commands repeatedly: ovs-vsctl add-br test ovs-vsctl del-br test eventually leads to: [ 44.476751] IP: kmem_cache_alloc_trace+0x91/0x1d0 [ 44.477299] *pdpt = 1ae13001 *pde = [ 44.477956] Oops: [#1] SMP [ 44.478340] Modules linked in: dummy openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack isofs kvm_intel kvm irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net floppy [ 44.483687] CPU: 0 PID: 553 Comm: systemd-network Tainted: GW 4.15.0-44-generic #47-Ubuntu [ 44.484819] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 [ 44.485865] EIP: kmem_cache_alloc_trace+0x91/0x1d0 [ 44.486451] EFLAGS: 00010286 CPU: 0 [ 44.486917] EAX: df719701 EBX: ee835a95 ECX: e8e4 EDX: e8e3 [ 44.487663] ESI: df7197e0 EDI: df401a00 EBP: df7cbda0 ESP: df7cbd78 [ 44.488440] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 44.489103] CR0: 80050033 CR2: ee835a95 CR3: 1f7f7ac0 CR4: 06f0 [ 44.489918] DR0: DR1: DR2: DR3: [ 44.490717] DR6: fffe0ff0 DR7: 0400 [ 44.491265] Call Trace: [ 44.491655] ? seq_open+0x2d/0x80 [ 44.492136] seq_open+0x2d/0x80 [ 44.492602] kernfs_fop_open+0x1a0/0x360 [ 44.493146] do_dentry_open+0x1ac/0x2f0 [ 44.493688] ? kernfs_seq_start+0x90/0x90 [ 44.494258] vfs_open+0x41/0x70 [ 44.494717] path_openat+0x5e0/0x13f0 [ 44.495234] ? dput.part.23+0xcf/0x1e0 [ 44.495761] ? mntput+0x20/0x40 [ 44.496227] do_filp_open+0x6a/0xd0 [ 44.496739] ? __alloc_fd+0x36/0x160 [ 44.497267] do_sys_open+0x1ad/0x2b0 [ 44.497800] SyS_openat+0x1b/0x20 [ 44.498297] do_fast_syscall_32+0x7f/0x1e0 [ 44.498882] entry_SYSENTER_32+0x4e/0x7c [ 44.499450] EIP: 0xb7f0dd09 [ 44.499888] EFLAGS: 0282 CPU: 0 [ 44.500410] EAX: ffda EBX: ff9c ECX: bfa5fdc0 EDX: 00088000 [ 44.501244] ESI: EDI: EBP: 00088000 ESP: bfa5fc60 [ 44.502078] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [ 44.502833] Code: 33 87 b8 00 00 00 89 75 dc 89 c3 89 45 e0 8b 45 f0 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 bb 8b 75 dc 3b 75 e0 74 0e 03 5f 14 <33> 1b 33 9f b8 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 f7 [ 44.505346] EIP: kmem_cache_alloc_trace+0x91/0x1d0 SS:ESP: 0068:df7cbd78 [ 44.506250] CR2: ee835a95 [ 44.506751] ---[ end trace 3c49b27dd79507a3 ]--- [ 44.508624] BUG: unable to handle kernel paging request at ee835a95 [ 44.509508] IP: __kmalloc+0x85/0x220 [ 44.510020] *pdpt = 1ae13001 *pde = [ 44.510829] Oops: [#2] SMP [ 44.511307] Modules linked in: dummy openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack isofs kvm_intel kvm irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net floppy [ 44.517190] CPU: 0 PID: 1854 Comm: journal-offline Tainted: G D W 4.15.0-44-generic #47-Ubuntu [ 44.518478] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.1-1ubuntu1 04/01/2014 [ 44.519730] EIP: __kmalloc+0x85/0x220 [ 44.520275] EFLAGS: 00010086 CPU: 0 [ 44.520794] EAX: dfacdbf0 EBX: ECX: ee835a95 EDX: e8e4 [ 44.521666] ESI: dae09bf0 EDI: df401a00 EBP: dcaf59fc ESP: dcaf59d4 [ 44.522497] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [
[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests
*** This bug is a duplicate of bug 1813244 *** https://bugs.launchpad.net/bugs/1813244 ** This bug is no longer a duplicate of bug 1736390 openvswitch: kernel oops destroying interfaces on i386 ** This bug has been marked a duplicate of bug 1813244 systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1712831 Title: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Hi, this seems to me to be a kernel crash of some sorts. Somewhat in the spirit of older bugs: - bug 1630940 - bug 1630578 Xnox asked me to look into a hang on openvswitch dep8 tests. What I found initially was in the log just "ERROR: Removing temporary files on testbed timed out" That message brought me to the two bugs above. But in there I read that this was the infra running dep8 crashing. So for a better bug report I tried to reproduce locally and that actually seems to work very reliable. To reproduce do: $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G $ pull-lp-source openvswitch $ autopkgtest --apt-upgrade --shell --no-built-binaries openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu ~/work/autopkgtest-artful-i386.img # This guest currently will crash after a while of testing But with that running you can attach to the console and monitor of that guest. For example: $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0 That gave me a crash on the hang which kind of matches the older bugs, here the console: [ 54.256253] BUG: unable to handle kernel NULL pointer dereference at (null) [ 54.257156] IP: add_grec+0x28/0x440 [ 54.257553] *pdpt = 1a869001 *pde = [ 54.257555] [ 54.258338] Oops: [#1] SMP [ 54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net floppy pata_acpi [ 54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.12.0-11-generic #12-Ubuntu [ 54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [ 54.263610] task: c7b622c0 task.stack: c7b5a000 [ 54.264039] EIP: add_grec+0x28/0x440 [ 54.264378] EFLAGS: 00010202 CPU: 0 [ 54.264711] EAX: EBX: dd062540 ECX: 0006 EDX: dd062540 [ 54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0 [ 54.265793] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.266297] CR0: 80050033 CR2: CR3: 1e930d80 CR4: 06f0 [ 54.266885] Call Trace: [ 54.267120] [ 54.267349] mld_ifc_timer_expire+0xfe/0x250 [ 54.267754] ? mld_dad_timer_expire+0x50/0x50 [ 54.268173] call_timer_fn+0x30/0x120 [ 54.268524] ? mld_dad_timer_expire+0x50/0x50 [ 54.268942] ? mld_dad_timer_expire+0x50/0x50 [ 54.269364] run_timer_softirq+0x3c5/0x420 [ 54.269760] ? __softirqentry_text_start+0x8/0x8 [ 54.270198] __do_softirq+0xa9/0x245 [ 54.270539] ? __softirqentry_text_start+0x8/0x8 [ 54.270976] do_softirq_own_stack+0x24/0x30 [ 54.271373] [ 54.271611] irq_exit+0xad/0xb0 [ 54.271913] smp_apic_timer_interrupt+0x38/0x50 [ 54.272344] apic_timer_interrupt+0x39/0x40 [ 54.272745] EIP: native_safe_halt+0x5/0x10 [ 54.273139] EFLAGS: 0246 CPU: 0 [ 54.273624] EAX: EBX: ECX: 0001 EDX: [ 54.274000] ESI: EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10 [ 54.274361] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 54.274687] default_idle+0x1c/0xf0 [ 54.274896] arch_cpu_idle+0xe/0x10 [ 54.275286] default_idle_call+0x1e/0x30 [ 54.275787] do_idle+0x145/0x1c0 [ 54.276092] cpu_startup_entry+0x65/0x70 [ 54.276441] rest_init+0x62/0x70 [ 54.276718] start_kernel+0x3be/0x3d7 [ 54.276974] i386_start_kernel+0x9d/0xa1 [ 54.277260] startup_32_smp+0x16b/0x16d [ 54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b [ 54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0 [ 54.279829] CR2: [ 54.280143] ---[ end trace 3164b1c0dd7745bc ]--- [ 54.280550] Kernel panic - not syncing: Fatal exception in interrupt [ 54.281078] Kernel Offset: 0x600 from 0xc1000
[Kernel-packages] [Bug 1823653] [NEW] Wireless key does not work on Dell G7 7588 with Bionic
Public bug reported: The wireless key (fn + PrtScn) does not work on this system. "sudo showkey -s" does not return anything But it will generate some noise in dmesg: [ 1863.388925] keyboard: can't emulate rawmode for keycode 240 [ 1863.408641] keyboard: can't emulate rawmode for keycode 247 [ 1863.408667] keyboard: can't emulate rawmode for keycode 247 "sudo showkey -k" will show: keycode 240 press keycode 247 press keycode 247 release xev returns: KeyPress event, serial 37, synthetic NO, window 0x281, root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x281, root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:58:37 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: The wireless key (fn + PrtScn) does not work on this system. "sudo showkey -s" does not return anything + But it will generate some noise in dmesg: + [ 1863.388925] keyboard: can't emulate rawmode for keycode 240 + [ 1863.408641] keyboard: can't emulate rawmode for keycode 247 + [ 1863.408667] keyboard: can't emulate rawmode for keycode 247 + + "sudo showkey -k" will show: keycode 240 press keycode 247 press keycode 247 release xev returns: KeyPress event, serial 37, synthetic NO, window 0x281, - root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), - state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, - XLookupString gives 0 bytes: - XmbLookupString gives 0 bytes: - XFilterEvent returns: False + root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), + state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, + XLookupString gives 0 bytes: + XmbLookupString gives 0 bytes: + XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x281, - root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), - state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, - XLookupString gives 0 bytes: - XFilterEvent returns: False + root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), + state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, + XLookupString gives 0 bytes: + XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 15:58:37 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1823653 Title: Wireless key does not work on Dell G7 7588 with Bionic Status in linux-signed package in Ubuntu: New Bug description: The wireless key (fn + PrtScn) does not work on this system. "sudo showkey -s" does not return anything But it will generate some noise in dmesg: [ 1863.388925] keyboard: can't emulate rawmode for keycode 240 [ 1863.408641] keyboard: can't emulate rawmode for keycode 247 [ 1863.408667] keyboard: can't emulate rawmode for keycode 247 "sudo showkey -k" will show: keycode 240 press keycode 247 press keycode 247 release xev returns: KeyPress event, serial 37, synthetic NO, window 0x281, root 0x263, subw 0x0, time 1542623, (357,334), root:(547,505), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x281, root 0x263,
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
*** This bug is a duplicate of bug 1813244 ***
https://bugs.launchpad.net/bugs/1813244
** This bug has been marked a duplicate of bug 1813244
systemd cause kernel trace "BUG: unable to handle kernel paging request at
6db23a14" on Cosmic i386
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736390
Title:
openvswitch: kernel oops destroying interfaces on i386
Status in linux package in Ubuntu:
In Progress
Status in openvswitch package in Ubuntu:
Invalid
Status in linux source package in Artful:
Won't Fix
Status in openvswitch source package in Artful:
Invalid
Status in linux source package in Bionic:
In Progress
Status in openvswitch source package in Bionic:
Invalid
Status in linux source package in Cosmic:
In Progress
Status in openvswitch source package in Cosmic:
Invalid
Status in linux source package in Disco:
In Progress
Status in openvswitch source package in Disco:
Invalid
Bug description:
== SRU Justification ==
Commit 120645513f55 ("openvswitch: Add eventmask support to CT
action.") introduced a regression on i386. Simply running the
following commands in a loop will trigger a crash rather quickly:
ovs-vsctl add-br test
ovs-vsctl del-br test
== Fix ==
Disable the logic introduced by the above commit on i386.
== Regression Potential ==
Low, the above commit introduced a new feature. Per upstream, the
result of not having this feature results in higher CPU usage and
potential buffering issues in user space.
== Test Case ==
See SRU justification above.
Original bug description:
Reproducable on bionic using the autopkgtest's from openvswitch on
i386:
[ 41.420568] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 41.421000] IP: igmp_group_dropped+0x21/0x220
[ 41.421246] *pdpt = 1d62c001 *pde =
[ 41.421659] Oops: [#1] SMP
[ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse
virtio_blk virtio_net pata_acpi floppy
[ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW
4.13.0-18-generic #21-Ubuntu
[ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.10.2-1ubuntu1 04/01/2014
[ 41.424849] Workqueue: netns cleanup_net
[ 41.425071] task: db8fba80 task.stack: dba1
[ 41.425346] EIP: igmp_group_dropped+0x21/0x220
[ 41.425656] EFLAGS: 00010202 CPU: 0
[ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002
[ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
[ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0
[ 41.427340] Call Trace:
[ 41.427485] ? __wake_up+0x36/0x40
[ 41.427680] ip_mc_down+0x27/0x90
[ 41.427869] inetdev_event+0x398/0x4e0
[ 41.428082] ? skb_dequeue+0x5b/0x70
[ 41.428286] ? wireless_nlevent_flush+0x4c/0x90
[ 41.428541] notifier_call_chain+0x4e/0x70
[ 41.428772] raw_notifier_call_chain+0x11/0x20
[ 41.429023] call_netdevice_notifiers_info+0x2a/0x60
[ 41.429301] dev_close_many+0x9d/0xe0
[ 41.429509] rollback_registered_many+0xd7/0x380
[ 41.429768] unregister_netdevice_many.part.102+0x10/0x80
[ 41.430075] default_device_exit_batch+0x134/0x160
[ 41.430344] ? do_wait_intr_irq+0x80/0x80
[ 41.430650] ops_exit_list.isra.8+0x4d/0x60
[ 41.430886] cleanup_net+0x18e/0x260
[ 41.431090] process_one_work+0x1a0/0x390
[ 41.431317] worker_thread+0x37/0x450
[ 41.431525] kthread+0xf3/0x110
[ 41.431714] ? process_one_work+0x390/0x390
[ 41.431941] ? kthread_create_on_node+0x20/0x20
[ 41.432187] ret_from_fork+0x19/0x24
[ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
[ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
[ 41.433750] CR2:
[ 41.433961] ---[ end trace 595db54cab84070c ]---
system then becomes unresponsive; no further interfaces can be
created.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
@james-page, the fix has been sent to the Ubuntu kernel mailing list [1], so it's scheduled for the next SRU cycle (assuming it gets two ACKs). [1] https://lists.ubuntu.com/archives/kernel-team/2019-April/099883.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kerne
[Kernel-packages] [Bug 1823618] Re: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade
As usual - thanks bug - with a proper ssh set up and logged in it just doesn't trigger anymore :-/ I tried multiple reboots and we can keep the bug if others are affected to join forces, but for now it is incomplete as I can no more reproduce it :-/ ** Changed in: linux-hwe (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Incomplete ** 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/1823618 Title: 4.18.0-17 crashes on i915 driver with multiple monitors since upgrade Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux-hwe source package in Cosmic: Invalid Bug description: On 2019-04-03 I updated to the latest linux-image-generic- hwe-18.04:amd64 and then I got on a trip where things worked fine at first. Back home I realized that the new version 4.18.0-17-generic has issues initializing gnome with multiple monitors. Steps to reproduce: - boot into 4.18.0-17-generic (to be specific Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 as seen in the boot log) - start Ubuntu Desktop (gdm works fine at first) - Log in I have found that this only triggers: - with multiple monitors attached ( I have laptop fullHD + 2* external fullHD; with just the laptop screen it works) - only with 4.18.0-17-generic, 4.18.0-16-generic seems fine (=>upgrade-regression?) On init of the gnome shell the system crashes with: kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected d293602a, found 7548bc60) [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999) [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Keyboard shortcuts for and further e.g. CTRL+ALT+F* does not switch to consoles anymore. I can only hard reset via 5sec power button. I'll attach a full journal of the system and run an apport run on it. Let me know if I can help any further. So far I had 3/3 crashes with 4.18.0-17 and it worked with 4.18.0-16 right away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820990] Re: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1820990 Title: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] When no acpi hid match the device, there will be a NULL dereference in amd iommu. It will make system hang. [Fix] Check NULL pointer before using it. [Test] Tested on several AMD platforms, bugs are fixed with this patch. [Regression Potential] Low, upstream fix, Verified on several platforms. It should be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
@juergh ok I'll propose a hint for disco them! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.049951] htree_dirblock_to_tree+0xd2/0x230 Jan 25 00:00:37 onza kernel: [452
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I've been running disco for a while with `generic` Ubuntu kernel 5.0.0 (currently 5.0.0-8), and I haven't experienced that problem for a while. I still get some USB issues from time to time with the Dell dock - where the USB does not connect when I plug the dock to the laptop, at which point I pull the TB plug out and connect it again and it is usually OK (sometimes it takes a couple of tries), but I no longer see "unknown event" errors and the USB no longer dies in the middle of a work day. I never booted into Windows at any point - neither for a firmware upgrade nor for the "reset workaround". I'm updating firmware using the BIOS update facility and I'm currently running Firmware version 1.12.0 which comes with TB controller firmware version 26.01. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New US
[Kernel-packages] [Bug 1820153] Re: [SRU][B/C/OEM]IOMMU: add kernel dma protection
** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- 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/1820153 Title: [SRU][B/C/OEM]IOMMU: add kernel dma protection Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Bug description: SRU justification: [Impact] Recent systems shipping with "kernel DMA protection" = "enabled" by default in BIOS. This setting option changed "Thunderbolt Security Level" = "No Security (SL0)". With this setting systems will be vulnerable to a DMA attack by a thunderbolt device. OS can use IOMMU to defend against DMA attacks from a PCI device like thunderbolt one. Intel adds DMA_CTRL_PLATFORM_OPT_IN_FLAG flag in DMAR ACPI table. Use this flag to enable IOMMU and use _DSD to identify untrusted PCI devices. [Fix] Enable IOMMU when BIOS supports DMA opt in flag and ExternalFacingPort in _DSD. Disable ATS on the untrusted PCI device. [Test] Tested on 2 Intel platforms that supports DMA opt in flag with a thunderbolt dock station. iommu enabled as expected with this fix. Verified by QA's full test with a temporary build of bionic-oem kernel. All test passed on one supported "DMA protection" system and one non-supported "DMA protection" system. [Regression Potential] Upstream fix, Verified on supported platforms, no affection on not supported platforms. Backported changes are fairly minimal. These patches are included in 5.0 kernel, disco is good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Still seeing this on 5.0.6. PPA mainline. Booting windows prior to linux is WAR for me. Dell 5530 w/TB16. Don't think it is fixed in 5. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1823216] Re: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG:
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823216 Title: [trusty] 3.13.0-167-generic repeatedly trips kernel paging request BUG: Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: While trying to diagnose a problem with getting a kernel BUG: Bad page map in process retriever (retriever is the name of our serving binary), causing the serving binary to crash, we tried upgrading from 3.13.0-121-generic to 3.13.0-167-generic and instead started more regularly tripping a different bug that hardlocks the system when we attempt to stop & restart the affected process. We are running Trusty on AWS in i3.xlarge instances. BUG: unable to handle kernel paging request at eaf0 [89149.537277] IP: [] _raw_spin_lock+0xe/0x50 [89149.543462] PGD 0 [89149.545919] Oops: 0002 [#1] SMP [89149.549887] Modules linked in: 8021q garp stp mrp llc dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy [89149.574925] CPU: 3 PID: 21681 Comm: retriever Not tainted 3.13.0-167-generic #217-Ubuntu [89149.583168] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [89149.589649] task: 8807f2f7e000 ti: 88015b674000 task.ti: 88015b674000 [89149.597338] RIP: 0010:[] [] _raw_spin_lock+0xe/0x50 [89149.605845] RSP: :88015b675d88 EFLAGS: 00010206 [89149.611431] RAX: 0002 RBX: 00c0dee00020 RCX: f000cf53 [89149.618873] RDX: 8800 RSI: 00c0 RDI: eaf0 [89149.626336] RBP: 88015b675d88 R08: 3fe0 R09: 00a9 [89149.633705] R10: R11: f000ff53f000ff53 R12: 880037471900 [89149.641019] R13: 8807f49c57b8 R14: 8807f2eb2680 R15: eaf0 [89149.648287] FS: 7f92262dd700() GS:88081fc6() knlGS: [89149.657764] CS: 0010 DS: ES: CR0: 80050033 [89149.664294] CR2: eaf0 CR3: 0007f438 CR4: 00160670 [89149.672158] DR0: DR1: DR2: [89149.680246] DR3: DR6: fffe0ff0 DR7: 0400 [89149.688126] Stack: [89149.690903] 88015b675e20 811831fe 81e85225 8807f2eb2680 [89149.700310] 88015b675f20 88015b675e10 0007 f000cf53 [89149.709739] 00a9 f000ff53f000ff53 8800 8003 [89149.719331] Call Trace: [89149.722581] [] handle_mm_fault+0x27e/0xfb0 [89149.729984] [] __do_page_fault+0x183/0x570 [89149.737506] [] ? do_futex+0x10a/0x760 [89149.744529] [] ? set_next_entity+0x95/0xb0 [89149.752059] [] ? pick_next_task_fair+0x5f/0x1b0 [89149.76] [] ? sched_clock_cpu+0xb5/0x100 [89149.767489] [] do_page_fault+0x1a/0x70 [89149.774460] [] page_fault+0x28/0x30 [89149.781134] Code: 00 00 55 48 89 e5 f0 81 07 00 00 10 00 48 89 f7 57 9d 0f 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 b8 00 00 02 00 0f c1 07 89 c2 c1 ea 10 66 39 c2 75 02 5d c3 83 e2 fe 0f b7 [89149.820963] RIP [] _raw_spin_lock+0xe/0x50 [89149.828646] RSP [89149.833460] CR2: eaf0 [89149.843886] ---[ end trace 5e5ae13dbb1d0f6e ]--- BUG: unable to handle kernel paging request at eaf0 [66384.498399] IP: [] _raw_spin_lock+0xe/0x50 [66384.502611] PGD 0 [66384.504586] Oops: 0002 [#1] SMP [66384.507578] Modules linked in: 8021q garp stp mrp llc dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel serio_raw isofs aesni_intel aes_x86_64 glue_helper lrw gf128mul ablk_helper cryptd psmouse nvme ena floppy [66384.525392] CPU: 1 PID: 21144 Comm: retriever Not tainted 3.13.0-167-generic #217-Ubuntu [66384.531418] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [66384.535812] task: 88074a9a9800 ti: 8807f411e000 task.ti: 8807f411e000 [66384.542092] RIP: 0010:[] [] _raw_spin_lock+0xe/0x50 [66384.548699] RSP: :8807f411fd88 EFLAGS: 00010206 [66384.552560] RAX: 0002 RBX: 00c2b0c0 RCX: f000cf53 [66384.557499] RDX: 8800 RSI: 00c0 RDI: eaf0 [66384.562419] RBP: 8807f411fd88 R08: 3fe0 R09: 00a9 [66384.567450] R10: R11: f000ff53f000ff53 R12: 8807f4af9f00 [66384.572935] R13: 8807f2ed9c30 R14: 8807f3ee2680 R15: eaf0 [66384.578165] FS: 7f9886ac4700() GS:88081fc2(
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Packaging - phase-changed: Sunday, 07. April 2019 05:05 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 08. April 2019 09:09 UTC reason: - prepare-package-meta: Pending -- package tag not yet published - promote-to-proposed: Pending -- source package tags missing + promote-to-proposed: Pending -- ready for review -- 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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Monday, 08. April 2019 09:09 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823581] Re: Multi-touch screen test of checkbox failed on Disco 19.04
multitouch doesn't work on this machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823581 Title: Multi-touch screen test of checkbox failed on Disco 19.04 Status in linux package in Ubuntu: Incomplete Bug description: Summary: I use a Dell Precision 5530 (I+N). The tests of checkbox failed: 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch- zoom Steps to reproduce: 1. Install checkbox $ sudo add-apt-repository ppa:hardware-certification/public $ sudo apt-get update $ sudo apt-get install checkbox-ng plainbox-provider-resource-generic plainbox-provider-certification-client plainbox-provider-checkbox 2. Run the test cases - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom via checkbox $ checkbox-cli Expected result: The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom passed Actual result: The tests - 3-touch-tap, 4-touch-tap, multitouch-rotate and multitouch-zoom failed Additional Information: The tests can be passed on XPS 13 9380 Failure rate: 100% - GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b system-manufacturer: Dell Inc. bios-version: 1.6.0 CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) system-product-name: Precision 5530 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 2343 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-29 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5530 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=8e4bee3f-6d32-4221-8bd7-7cdbfcf163b7 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821027] Re: Feedback on the Dell G7 7588 Boot Time
Grabbed a Dell G7 7588, I can see the following behaviour: * 4.15.47 - Startup finished in 9.204s (firmware) + 12.063s (loader) + 18.618s (kernel) + 35.425s (userspace) = 1min 15.312s - graphical.target reached after 35.321s in userspace * 4.15.46 - Startup finished in 9.960s (firmware) + 26.601s (loader) + 5.682s (kernel) + 21.687s (userspace) = 1min 3.932s - graphical.target reached after 21.675s in userspace * 4.15.45 Please ignore the loader, it the grub menu that I used to switch between different kernels -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821027 Title: Feedback on the Dell G7 7588 Boot Time Status in linux package in Ubuntu: Incomplete Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
** 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821027] Re: Feedback on the Dell G7 7588 Boot Time
Grabbed a Dell G7 7588 (GTX1060), I can see the following behaviour (without the proprietary NVIDIA driver): * 4.15.47 - Startup finished in 9.204s (firmware) + 12.063s (loader) + 18.618s (kernel) + 35.425s (userspace) = 1min 15.312s - graphical.target reached after 35.321s in userspace * 4.15.46 - Startup finished in 9.960s (firmware) + 26.601s (loader) + 5.682s (kernel) + 21.687s (userspace) = 1min 3.932s - graphical.target reached after 21.675s in userspace * 4.15.45 - Startup finished in 10.107s (firmware) + 10.019s (loader) + 3.652s (kernel) + 20.518s (userspace) = 44.298s - graphical.target reached after 20.501s in userspace Please ignore the time cost in "loader", it the grub menu that I used to switch between different kernels. So if we assume the loader costs 10 second, the start time will be: * 4.15.47 - 73s * 4.15.46 - 47s * 4.15.45 - 44s After installing the proprietary video driver (nvidia-driver-390), the boot time looks ok to me: * 4.15.47 - Startup finished in 13.981s (firmware) + 13.375s (loader) + 3.796s (kernel) + 15.451s (userspace) = 46.604s - graphical.target reached after 15.424s in userspace * 4.15.46 - Startup finished in 8.506s (firmware) + 17.742s (loader) + 8.274s (kernel) + 11.884s (userspace) = 46.407s - graphical.target reached after 11.879s in userspace * 4.15.45 - Startup finished in 8.433s (firmware) + 7.836s (loader) + 2.664s (kernel) + 13.392s (userspace) = 32.327s - graphical.target reached after 13.149s in userspace I guess when booting without the proprietary driver, it's affected by the nouveau timeout issue (bug 1822987) Clement Yuan, can you install the proprietary driver and give it a try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821027 Title: Feedback on the Dell G7 7588 Boot Time Status in linux package in Ubuntu: Incomplete Bug description: Hi Ubuntu Team, My laptop take more than 45 sec to boot up Ubuntu. Here is my kernel log. Feb 5 13:26:57 my-laptop kernel: [2.461535] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Feb 5 13:26:57 my-laptop kernel: [2.780579] [drm] RC6 on Feb 5 13:26:57 my-laptop kernel: [ 33.565700] SGI XFS with ACLs, security attributes, realtime, no debug enabled Feb 5 13:26:57 my-laptop kernel: [ 33.567361] XFS (nvme0n1p10): Mounting V5 Filesystem Here is the problem. It take more than 30 sec to do load the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock
I used Last boot: journalctl -o short-precise -k -b -1 Two boots prior: journalctl -o short-precise -k -b -2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820243 Title: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 (linux-image-4.18.0-16-generic) ThinkPad 460P Intel i7-6700HQ Nvidia GTX940MX (nvidia 415 drivers) When using with dock, attached monitor is not detected, laptop monitor remains blank. Laptop freezes until I detach it from the UltraDock again. Requires a reboot with the UltraDock attached to make it working. It worked in the past since 4.18 with the Laptop booted with the UltraDock and detach ad attach the laptop again. This time I detached the Laptop, worked a few days without the UltraDock (used Standby over night) and tried to attach it again. Maybe it happens because I use HWE now. But the errors in dmesg and logcat are looking like my bugreport for kernel 4.15 where the UltraDock didn't worked. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin17549 F pulseaudio /dev/snd/pcmC0D0p: martin17549 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (236 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock
Sorry to write another message, but I can't edit the previous one. I updated my GPU driver from 415 to 418. My kernel from linux-image-4.18.0-16-generic to linux-image-4.18.0-17-generic No fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820243 Title: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 (linux-image-4.18.0-16-generic) ThinkPad 460P Intel i7-6700HQ Nvidia GTX940MX (nvidia 415 drivers) When using with dock, attached monitor is not detected, laptop monitor remains blank. Laptop freezes until I detach it from the UltraDock again. Requires a reboot with the UltraDock attached to make it working. It worked in the past since 4.18 with the Laptop booted with the UltraDock and detach ad attach the laptop again. This time I detached the Laptop, worked a few days without the UltraDock (used Standby over night) and tried to attach it again. Maybe it happens because I use HWE now. But the errors in dmesg and logcat are looking like my bugreport for kernel 4.15 where the UltraDock didn't worked. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin17549 F pulseaudio /dev/snd/pcmC0D0p: martin17549 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (236 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: New 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 verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Monday, 08. April 2019 09:09 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) 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/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 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: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769
[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock
** Attachment added: "dmesg_standby_disconnectDock_wakeup_usersessionLost.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+attachment/5254044/+files/dmesg_standby_disconnectDock_wakeup_usersessionLost.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820243 Title: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 (linux-image-4.18.0-16-generic) ThinkPad 460P Intel i7-6700HQ Nvidia GTX940MX (nvidia 415 drivers) When using with dock, attached monitor is not detected, laptop monitor remains blank. Laptop freezes until I detach it from the UltraDock again. Requires a reboot with the UltraDock attached to make it working. It worked in the past since 4.18 with the Laptop booted with the UltraDock and detach ad attach the laptop again. This time I detached the Laptop, worked a few days without the UltraDock (used Standby over night) and tried to attach it again. Maybe it happens because I use HWE now. But the errors in dmesg and logcat are looking like my bugreport for kernel 4.15 where the UltraDock didn't worked. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin17549 F pulseaudio /dev/snd/pcmC0D0p: martin17549 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (236 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock
** Attachment added: "dmesg_standby_disconnectDock_wakeup_usersessionLost2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+attachment/5254045/+files/dmesg_standby_disconnectDock_wakeup_usersessionLost2.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820243 Title: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 (linux-image-4.18.0-16-generic) ThinkPad 460P Intel i7-6700HQ Nvidia GTX940MX (nvidia 415 drivers) When using with dock, attached monitor is not detected, laptop monitor remains blank. Laptop freezes until I detach it from the UltraDock again. Requires a reboot with the UltraDock attached to make it working. It worked in the past since 4.18 with the Laptop booted with the UltraDock and detach ad attach the laptop again. This time I detached the Laptop, worked a few days without the UltraDock (used Standby over night) and tried to attach it again. Maybe it happens because I use HWE now. But the errors in dmesg and logcat are looking like my bugreport for kernel 4.15 where the UltraDock didn't worked. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin17549 F pulseaudio /dev/snd/pcmC0D0p: martin17549 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (236 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820243] Re: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock
My display manager is lightDM. How can I set it to debug? And with "syslog" you mean you mean journalctl ? Here are two DMESG now. Connected with dock -> standby -> disconnect -> wakeup -> usersession lost. Disconnected with dock -> standby -> connect -> wakeup -> black screen and nothing happens, maybe a display flash after a long waiting time. The first dmesg I have made again with timestamps. ** Attachment added: "dmesg_standby_connectDock_wakeup_blackscreen.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+attachment/5254043/+files/dmesg_standby_connectDock_wakeup_blackscreen.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820243 Title: linux-image-4.18.0-16-generic breaks Lenovo T460P on Ultradock Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 (linux-image-4.18.0-16-generic) ThinkPad 460P Intel i7-6700HQ Nvidia GTX940MX (nvidia 415 drivers) When using with dock, attached monitor is not detected, laptop monitor remains blank. Laptop freezes until I detach it from the UltraDock again. Requires a reboot with the UltraDock attached to make it working. It worked in the past since 4.18 with the Laptop booted with the UltraDock and detach ad attach the laptop again. This time I detached the Laptop, worked a few days without the UltraDock (used Standby over night) and tried to attach it again. Maybe it happens because I use HWE now. But the errors in dmesg and logcat are looking like my bugreport for kernel 4.15 where the UltraDock didn't worked. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781904 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin17549 F pulseaudio /dev/snd/pcmC0D0p: martin17549 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (236 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 007: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823684] [NEW] Right click does not work as expected on Dell G7 7588
Public bug reported: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpadid=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Button id=9[slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Intel HID events id=14 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309562, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 309563, (167,148), root:(357,319), state 0x110, button 1, same_screen YES ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 8 17:50:24 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1823684 Title: Right click does not work as expected on Dell G7 7588 Status in linux-signed package in Ubuntu: New Bug description: The right button on the touchpad of this system does not work as expected, the click event will get treated as a regular left click. $ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ DELL0825:00 06CB:7E92 Touchpad id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=11 [slave keyboard (3)] ↳ Intel HID 5 button arrayid=13 [slave keyboard (3)] ↳ Intel HID eventsid=14 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] xev for left click and right click: ButtonPress event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304106, (167,148), root:(357,319), state 0x10, button 1, same_screen YES ButtonRelease event, serial 37, synthetic NO, window 0x301, root 0x263, subw 0x0, time 304146, (167,
[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): amd64:latest/beta' snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): amd64:latest/edge' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822826] Re: linux-kvm: 4.4.0-1044.50 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Released => New -- 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/1822826 Title: linux-kvm: 4.4.0-1044.50 -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-signing-to-proposed series: Invalid 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 verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Signoff phase-changed: Friday, 05. April 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822790 Title: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): amd64:18/beta' snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): amd64:18/edge' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- 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/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Saturday, 06. April 2019 00:06 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Ready for Promote to Proposed - phase-changed: Monday, 08. April 2019 09:09 UTC + phase: Promote to Proposed + phase-changed: Monday, 08. April 2019 09:57 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- 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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822816 Title: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822817 phase: Ready for Promote to Proposed phase-changed: Friday, 05. April 2019 17:41 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822824] Re: linux-aws: 4.4.0-1080.90 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- 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/1822824 Title: linux-aws: 4.4.0-1080.90 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Ready for Promote to Proposed phase-changed: Friday, 05. April 2019 10:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822826] Re: linux-kvm: 4.4.0-1044.50 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- 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/1822826 Title: linux-kvm: 4.4.0-1044.50 -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-signing-to-proposed series: Invalid 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 verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Signoff phase-changed: Friday, 05. April 2019 11:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822826/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): amd64:latest/beta' snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): amd64:latest/edge' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822790 Title: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): amd64:18/beta' snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): amd64:18/edge' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1822802 Title: linux-raspi2: 4.15.0-1034.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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 promote-signing-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Friday, 05. April 2019 10:05 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822809] Re: linux-kvm: 4.15.0-1032.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid -- 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/1822809 Title: linux-kvm: 4.15.0-1032.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Friday, 05. April 2019 10:36 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)
Zingam, thanks for your feedback. As this patch seems to fix many others' issue and your test result was provided after the package has been released. Can you open a new bug for the problem that you encountered with 4.18.0-15.16? Thanks in advance. ** Tags removed: verification-failed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814555 Title: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Fix Released Bug description: Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic, requested a reboot, and was unable to boot. After the "Starting Load/Save RF Kill Switch Status..." line it is waiting forever. (Or/and doing something behind the scenes. After a while, even the HDD indicator led go out.) This is a permanent error, so kernel 4.18.0-14 does NOT boot. I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub starts.) My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, hu and en), Xcfe4, gdm3, gnome-screensaver. I have already upgraded to the latest packages. (sudo apt-get dist-upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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)
** Tags added: 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/1779756 Title: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] The i40e driver can get stalled on tx timeouts. This can happen when DCB is enabled on the connected switch. This can also trigger a second situation when a tx timeout occurs before the recovery of a previous timeout has completed due to CPU load, which is not handled correctly. This leads to networking delays, drops and application timeouts and hangs. Note that the first tx timeout cause is just one of the ways to end up in the second situation. This issue was seen on a heavily loaded Kafka broker node running the 4.15.0-38-generic kernel on Xenial. Symptoms include messages in the kernel log of the form: --- [4733544.982116] i40e :18:00.1 eno2: tx_timeout: VSI_seid: 390, Q 6, NTC: 0x1a0, HWB: 0x66, NTU: 0x66, TAIL: 0x66, INT: 0x0 [4733544.982119] i40e :18:00.1 eno2: tx_timeout recovery level 1, hung_queue 6 With the test kernel provided in this LP bug which had these two commits compiled in, the problem has not been seen again, and has been running successfully for several months: "i40e: Fix for Tx timeouts when interface is brought up if DCB is enabled" Commit: fa38e30ac73fbb01d7e5d0fd1b12d412fa3ac3ee "i40e: prevent overlapping tx_timeout recover" Commit: d5585b7b6846a6d0f9517afe57be3843150719da * The first commit is already in Disco, Cosmic * The second commit is already in Disco * Bionic needs both patches and Cosmic needs the second [Test Case] * We are considering the case of both issues above occurring. * Seen by reporter on a Kafka broker node with heavy traffic. * Not easy to reproduce as it requires something like the following example environment and heavy load: Kernel: 4.15.0-38-generic Network driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 NIC: Intel 40Gb XL710 DCB enabled [Regression Potential] Low, as the first only impacts i40e DCB environment, and has been running for several months in production-load testing successfully. --- Original 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 1822805] Re: linux-aws: 4.15.0-1036.38 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Ready for Promote to Proposed phase-changed: Saturday, 06. April 2019 00:06 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784688] Re: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nv
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1784688 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After upgrade form 16.04 this bug starts to comming out ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 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 Date: Tue Jul 31 10:54:36 2018 Dependencies: ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 InstallationDate: Installed on 2017-02-19 (527 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 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/1784688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- 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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822987] Re: nouveau timeout on Disco with nvidia GTX 1060
for Bionic, I can see that this issue occurs from 4.15.0-46. 4.15.0-45 does not have this issue. Please find the attachment for the dmesg output $ cat dmesg-4.15.0-45 | grep nouveau [1.409849] nouveau: detected PR support, will not use DSM [1.409881] nouveau :01:00.0: enabling device (0006 -> 0007) [1.410094] nouveau :01:00.0: NVIDIA GP106 (136000a1) [1.476982] nouveau :01:00.0: bios: version 86.06.60.00.2d [1.523252] nouveau :01:00.0: fb: 6144 MiB GDDR5 [1.591767] nouveau :01:00.0: DRM: VRAM: 6144 MiB [1.591768] nouveau :01:00.0: DRM: GART: 536870912 MiB [1.591769] nouveau :01:00.0: DRM: BIT table 'A' not found [1.591770] nouveau :01:00.0: DRM: BIT table 'L' not found [1.591771] nouveau :01:00.0: DRM: TMDS table version 2.0 [1.591771] nouveau :01:00.0: DRM: DCB version 4.1 [1.591773] nouveau :01:00.0: DRM: DCB outp 00: 02022f62 00020010 [1.591774] nouveau :01:00.0: DRM: DCB conn 02: 00010261 [1.596851] nouveau :01:00.0: DRM: MM: using COPY for buffer copies [1.599401] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 [ 10.998306] nouveau :01:00.0: gr: intr 0040 ** Attachment added: "dmesg-4.15.0-45" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822987/+attachment/5254076/+files/dmesg-4.15.0-45 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822987 Title: nouveau timeout on Disco with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 00
[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Ready for Promote to Proposed - phase-changed: Saturday, 06. April 2019 00:06 UTC + phase: Promote to Proposed + phase-changed: Monday, 08. April 2019 10:36 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- 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/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 10:36 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) 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/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
Hey there, I'm having this issue with a Mint 19 (bionic) installation and two Marvell 88E8053 NICs. Logged in, press the power button or the Suspend menu, computer goes to sleep. When awoken from the power button, "Network cable is disconnected". I found the workaround of "sudo modprobe -r sky2; modprobe -i sky2" to work quite nicely. $ uname -rms Linux 4.15.0-47-generic x86_64 Tested with: * linux-image-4.15.0-47-generic/bionic-updates,bionic-security,now 4.15.0-47.50 amd64 * linux-image-4.18.0-17-generic/bionic-updates,bionic-security,now 4.18.0-17.18~18.04.1 amd64 If you need any more details, please feel free to be as analytical as possible ;) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822820 Title: linux: 4.15.0-48.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/beta armhf:18/beta i386:18/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/edge armhf:18/edge i386:18/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822987] Re: nouveau timeout on Disco with nvidia GTX 1060
There are two nouveau related patches added in 4.15.0-46 - drm/nouveau: Use drm_connector_list_iter_* for iterating connectors - drm/nouveau: Avoid looping through fake MST connectors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822987 Title: nouveau timeout on Disco with nvidia GTX 1060 Status in linux package in Ubuntu: Confirmed Bug description: The following error message could be found while booting this Dell G7 with Disco LiveUSB (20190403) Despite there is a such error message, the graphic looks OK. [ 15.714767] [ cut here ] [ 15.714768] nouveau :01:00.0: timeout [ 15.714818] WARNING: CPU: 7 PID: 2038 at drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd intel_soc_dts_iosf dell_wmi int3403_thermal [ 15.714833] virt_dma intel_hid wmi_bmof sparse_keymap intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel [ 15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic #9-Ubuntu [ 15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018 [ 15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau] [ 15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61 [ 15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286 [ 15.714869] RAX: RBX: 9b950cdde300 RCX: 0006 [ 15.714870] RDX: 0007 RSI: 0096 RDI: 9b951f3d6440 [ 15.714870] RBP: ac7305a07a10 R08: 0001 R09: 03e2 [ 15.714870] R10: 0004 R11: R12: [ 15.714871] R13: 9b951921a800 R14: 0040 R15: 9b951ab96940 [ 15.714872] FS: 7f14f3629a80() GS:9b951f3c() knlGS: [ 15.714872] CS: 0010 DS: ES: CR0: 80050033 [ 15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 003606e0 [ 15.714873] DR0: DR1: DR2: [ 15.714874] DR3: DR6: fffe0ff0 DR7: 0400 [ 15.714874] Call Trace: [ 15.714893] acr_r352_bootstrap+0x1a9/0x2b0 [nouveau] [ 15.714910] acr_r352_reset+0x39/0x230 [nouveau] [ 15.714926] nvkm_secboot_reset+0x35/0x70 [nouveau] [ 15.714944] gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau] [ 15.714962] ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau] [ 15.714979] gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau] [ 15.714997] gf100_gr_init+0x563/0x590 [nouveau] [ 15.715015] gf100_gr_init_+0x5b/0x60 [nouveau] [ 15.715032] nvkm_gr_init+0x1d/0x20 [nouveau] [ 15.715041] nvkm_engine_init+0xb9/0x1f0 [nouveau] [ 15.715052] nvkm_subdev_init+0xbc/0x210 [nouveau] [ 15.715061] nvkm_engine_ref.part.0+0x4a/0x70 [nouveau] [ 15.715071] nvkm_engine_ref+0x13/0x20 [nouveau] [ 15.715081] nvkm_ioctl_new+0x129/0x220 [nouveau] [ 15.715098] ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau] [ 15.715115] ? gf100_gr_dtor+0xd0/0xd0 [nouveau] [ 15.715125] nvkm_ioctl+0xe2/0x180 [nouveau] [ 15.715143] nv
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
** Description changed: + [SRU justification] + + == Impact == + Ethernet connection using a SKY2 card stops working after suspend. + + == Fix == + A fix for this landed in v5.0 upstream and was picked up in Xenial via upstream stable but not yet in Bionic and Cosmic. The change simply increases a timeout. + + == Testcase == + Suspend/resume with affected hardware present. + + == Risk of Regression == + Very low as only changing a timeout value in a specific hardware driver. + + --- + Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network-manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: [SRU justification] == Impact == Ethernet connection using a SKY2 card stops working after suspend. == Fix == A fix for this landed in v5.0 upstream and was picked up in Xenial via upstream stable but not yet in Bionic and Cosmic. The change simply increases a timeout. == Testcase == Suspend/resume with affected hardware present. == Risk of Regression == Very low as only changing a timeout value in a specific hardware driver. --- Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/beta - armhf:18/beta i386:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/edge - armhf:18/edge i386:18/edge' + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/beta - i386:latest/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/edge - i386:latest/edge' + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing 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/1822834 Title: linux: 4.4.0-146.172 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:latest/beta' - snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:latest/edge' + snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:latest/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): amd64:latest/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823706] [NEW] Sequence of main, restriced, multiverse, universe in the source.list has been changed
Public bug reported: >From this cycle, I saw some system got their source.list in this way: deb http://archive.ubuntu.com/ubuntu trusty universe multiverse main restricted Not the way it used to be: deb http://archive.ubuntu.com/ubuntu trusty main restricted multiverse universe Reporting this as it is the first time that I saw this. And we're using "trusty main" as a key to enable the proposed pocket, this issue is causing some trouble for our automation. (Can be fixed from our tool easily though) Also it's noteworthy that this seems to be a bit random. Sometime it will act like this but sometimes it will just like the old days. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-168-generic 3.13.0-168.218 ProcVersionSignature: User Name 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 8 11:42 seq crw-rw 1 root audio 116, 33 Apr 8 11:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 48.898467] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 8 11:45:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-168-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro console=ttyS0,1152008n1 RelatedPackageVersions: linux-restricted-modules-3.13.0-168-generic N/A linux-backports-modules-3.13.0-168-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823706 Title: Sequence of main, restriced, multiverse, universe in the source.list has been changed Status in linux package in Ubuntu: New Bug description: From this cycle, I saw some system got their source.list in this way: deb http://archive.ubuntu.com/ubuntu trusty universe multiverse main restricted Not the way it used to be: deb http://archive.ubuntu.com/ubuntu trusty main restricted multiverse universe Reporting this as it is the first time that I saw this. And we're using "trusty main" as a key to enable the proposed pocket, this issue is causing some trouble for our automation. (Can be fixed from our tool easily though) Also it's noteworthy that this seems to be a bit random. Sometime it will act like this but sometimes it will just like the old days. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-168-generic 3.13.0-168.218 ProcVersionSignature: User Name 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 8 11:42 seq crw-rw 1 root audio 116, 33 Apr 8 11:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 48.898467] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 8 11:45:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001
[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:18/beta' - snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:18/edge' + snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:18/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822790 Title: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): amd64:18/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823706] 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/1823706 Title: Sequence of main, restriced, multiverse, universe in the source.list has been changed Status in linux package in Ubuntu: Confirmed Bug description: From this cycle, I saw some system got their source.list in this way: deb http://archive.ubuntu.com/ubuntu trusty universe multiverse main restricted Not the way it used to be: deb http://archive.ubuntu.com/ubuntu trusty main restricted multiverse universe Reporting this as it is the first time that I saw this. And we're using "trusty main" as a key to enable the proposed pocket, this issue is causing some trouble for our automation. (Can be fixed from our tool easily though) Also it's noteworthy that this seems to be a bit random. Sometime it will act like this but sometimes it will just like the old days. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-168-generic 3.13.0-168.218 ProcVersionSignature: User Name 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 8 11:42 seq crw-rw 1 root audio 116, 33 Apr 8 11:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 48.898467] init: plymouth-upstart-bridge main process ended, respawning Date: Mon Apr 8 11:45:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-168-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro console=ttyS0,1152008n1 RelatedPackageVersions: linux-restricted-modules-3.13.0-168-generic N/A linux-backports-modules-3.13.0-168-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823407] Re: net and ftrace selftests failures due to missing test modules
** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed -- 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/1823407 Title: net and ftrace selftests failures due to missing test modules Status in linux-aws package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux- modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. Test Case: Run the test cases with the patch applied and observe that they behave as skipped tests rather than failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822813] Re: linux-fips: 4.15.0-1003.4 -proposed tracker
** Tags added: kernel-block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822813 Title: linux-fips: 4.15.0-1003.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822820 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 14:06 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 Status in linux package in Ubuntu: Fix Committed 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: SRU Justification: [Impact] * Flow action buffer can be incorrectly resized to contain the newly added action entries: the buffer is always resized multiplying the previous size by 2, but this might be not enough if the requested size is bigger than previous_size*2, causing a buffer overflow * The fix correctly resizes the buffer to prevent the buffer overflow * Despite the subject this bug can be triggered potentially on any architecture, but it is very likely to happen on i386 running the following test case [Test Case] * run this openvswitch test case: https://launchpadlibrarian.net/416589265/lp1262692 [Fix] * Instead of resizing the buffer by a factor of 2, use max(current_size * 2, current_size + requested_size) [Regression Potential] * Fix has been tested on the affected platform and verified using slub_debug. The patch has been queued up for -stable by David Miller, it will be included upstream for the next merge window. It is also a very small patch (a one-liner basically), so backport changes are minimal. [Original bug report] This issue was found after leaving a SUT to run overnight (was testing the ubuntu_cts_kernel test 13 hours ago before this happens). Can't tell if this is a regression, as I haven't find a way to reproduce it. But I do see similar reports on the Internet [1] After checking the systemd service timers, it looks like this is caused by the logrotate.service: $ sudo systemctl list-timers --all NEXT LEFT LAST PASSEDUNIT ACTIVATES Fri 2019-01-25 06:18:58 UTC 1h 40min left Thu 2019-01-24 06:34:15 UTC 22h ago apt-daily-upgrade.timer apt-daily-upgrade.service Fri 2019-01-25 09:15:54 UTC 4h 37min left Fri 2019-01-25 03:43:24 UTC 55min ago apt-daily.timer apt-daily.service Fri 2019-01-25 17:02:47 UTC 12h left Fri 2019-01-25 04:20:17 UTC 18min ago motd-news.timer motd-news.service Sat 2019-01-26 00:00:00 UTC 19h left Fri 2019-01-25 00:00:37 UTC 4h 38min ago logrotate.timer logrotate.service Sat 2019-01-26 04:02:38 UTC 23h left Fri 2019-01-25 04:02:38 UTC 36min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv Mon 2019-01-28 00:00:00 UTC 2 days left Wed 2019-01-23 10:44:18 UTC 1 day 17h ago fstrim.timer fstrim.service n/a n/a n/a n/a snapd.snap-repair.timer snapd.snap-repair.service 7 timers listed. After this happens, you won't be able to reboot it with the command. $ sudo reboot sudo: unable to resolve host onza: Resource temporarily unavailable Killed Here is the error message, please refer to the attachment for a complete syslog: Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files... Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel paging request at 6db23a14 Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = Jan 25 00:00:37 onza kernel: [45282.968650] Oops: [#1] SMP Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012 Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240 Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 3f 01 Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 350d EDX: 350c Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: f461fd9c ESP: f461fd74 Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010206 Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 29d304a0 CR4: 06f0 Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace: Jan 25 00:00:37 onza kernel: [45283.040395] ? ext4_htree_store_dirent+0x2e/0x120 Jan 25 00:00:37 onza kernel: [45283.045255] ext4_h
[Kernel-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux-oem (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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Committed Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822813] Re: linux-fips: 4.15.0-1003.4 -proposed tracker
** Tags added: kernel-block-ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822813 Title: linux-fips: 4.15.0-1003.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822820 phase: Holding before Promote to Proposed phase-changed: Friday, 05. April 2019 14:06 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822813/+subscriptions -- Mailing list: https://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 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen
Upon doing the first command you suggested, after a reboot, the PC screen turned on and off a few times and now the screen is just black. I'm force-rebooting the PC now and seeing if I'll regain the image on my screen. On Sun, Apr 7, 2019, 10:00 PM Daniel van Vugt wrote: > That's good news. > > Now please try these while the image is open: > > xrandr --output DVI-I-1 --set "dithering mode" "off" > > or > > xrandr --output DVI-I-1 --set "dithering mode" "static 2x2" > > and change 'DVI-I-1' if you are using a different connector now. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819023 > > Title: > [nouveau] Scrolling screen flicker, especially on default Ubuntu lock > screen > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > My screen is experiencing a weird "scrolling" flicker, especially > while displaying blue, indigo, and violet hues/colors, such as on the > default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker > scrolls up and down, with the brightest part of the flicker being > towards the top, with a gradient that fades back to the original color > near the bottom. > > Problem occurs on any one monitor on any one video output protocol > (DVI-D, HDMI, and VGA). > > > I will upload an illustration or render as soon as possible for better > explanation. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: xorg 1:7.7+19ubuntu8 > ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 > Uname: Linux 4.18.0-16-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 7 10:39:50 2019 > DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistroCodename: cosmic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828] > InstallationDate: Installed on 2018-08-17 (202 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: BIOSTAR Group A880G+ > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic > root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.product.sku: To Be Filled By O.E.M. > dmi.sys.vendor: BIOSTAR Group > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819023/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819023 Title: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen Status in linux package in Ubuntu: Incomplete Bug description: My screen is experiencing a weird "scrolling" flicker, especially while displaying blue, indigo, and violet hues/colors, such as on the default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up and down, with the brightest part of the flicker being towards the top, with a gradient that fades back to the original color near the bottom. Problem
[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 10:36 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 10:36 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1822805 Title: linux-aws: 4.15.0-1036.38 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 10:36 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:latest/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Friday, 05. April 2019 17:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820275] Re: btrfs-kernel oops from btrfs subvolume delete command
** Changed in: ubuntu-z-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/1820275 Title: btrfs-kernel oops from btrfs subvolume delete command Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: This report show a kernel oops in the btrfs lugin , happened every few days when running a test suite on a test system. It looks like their systemd/Journal failed to kick off a dump immediately following the panic. The exploiter is using the kernel 4.15.0-42 We're not sure it's the btrfs subvolume delete that's causing it yet Following infos are attached: - syslog - sosreport - kdump output here : https://ibm.ent.box.com/folder/70219521934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1820275/+subscriptions -- Mailing list: https://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 1819023] Re: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen
Alright, got the computer to reboot a second time and it appears as if the problem is fixed! The gradient on the login screen isn't a perfect gradient, but that's a different issue. Maybe dithering should be forced "off" in a near future update? On Sun, Apr 7, 2019, 10:00 PM Daniel van Vugt wrote: > That's good news. > > Now please try these while the image is open: > > xrandr --output DVI-I-1 --set "dithering mode" "off" > > or > > xrandr --output DVI-I-1 --set "dithering mode" "static 2x2" > > and change 'DVI-I-1' if you are using a different connector now. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819023 > > Title: > [nouveau] Scrolling screen flicker, especially on default Ubuntu lock > screen > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > My screen is experiencing a weird "scrolling" flicker, especially > while displaying blue, indigo, and violet hues/colors, such as on the > default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker > scrolls up and down, with the brightest part of the flicker being > towards the top, with a gradient that fades back to the original color > near the bottom. > > Problem occurs on any one monitor on any one video output protocol > (DVI-D, HDMI, and VGA). > > > I will upload an illustration or render as soon as possible for better > explanation. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: xorg 1:7.7+19ubuntu8 > ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 > Uname: Linux 4.18.0-16-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 7 10:39:50 2019 > DistUpgraded: 2018-10-19 10:50:54,557 ERROR got error from > PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to > execute child process “./xorg_fix_proprietary.py” (No such file or > directory) (8)) > DistroCodename: cosmic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828] > InstallationDate: Installed on 2018-08-17 (202 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: BIOSTAR Group A880G+ > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic > root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (139 days ago) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.product.sku: To Be Filled By O.E.M. > dmi.sys.vendor: BIOSTAR Group > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.95-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819023/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819023 Title: [nouveau] Scrolling screen flicker, especially on default Ubuntu lock screen Status in linux package in Ubuntu: Incomplete Bug description: My screen is experiencing a weird "scrolling" flicker, especially while displaying blue, indigo, and violet hues/colors, such as on the default Ubuntu 18.10 (x64 Desktop) lock screen. The screen flicker scrolls up and down, with the brightest part of the flicker being towards the top, with a gradient that fades back to the original color
[Kernel-packages] [Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap azure-kernel not in expected channel(s): - amd64:18/candidate' stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822790 Title: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 phase: Testing phase-changed: Friday, 05. April 2019 17:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
Test kernels are up here: https://people.canonical.com/~jlane/testkernels/ Please test each and report back ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) 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/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
Issue still remains with the mainline kernel. The contents of the kernel Oops message differs slightly, but still very similar: [ 27.532858] BUG: unable to handle kernel NULL pointer dereference at 03e8 [ 27.532862] #PF error: [WRITE] [ 27.532865] PGD 0 P4D 0 [ 27.532869] Oops: 0002 [#1] SMP NOPTI [ 27.532873] CPU: 3 PID: 82 Comm: kworker/3:1 Not tainted 5.1.0-050100rc3-generic #201904010618 [ 27.532875] Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 [ 27.532982] Workqueue: events dm_irq_work_func [amdgpu] [ 27.532989] RIP: 0010:queue_work_on+0x1b/0x40 [ 27.532992] Code: 75 01 01 e8 f9 13 fe ff 0f 0b e9 b5 fc ff ff 0f 1f 44 00 00 55 48 89 e5 53 9c 58 0f 1f 44 00 00 48 89 c3 fa 66 0f 1f 44 00 00 48 0f ba 2a 00 73 11 31 c9 48 89 df 57 9d 0f 1f 44 00 00 89 c8 [ 27.532994] RSP: 0018:c16bc1eebc88 EFLAGS: 00010002 [ 27.532996] RAX: 0202 RBX: 0202 RCX: 0001 [ 27.532998] RDX: 03e8 RSI: 9dde1e80d200 RDI: 2000 [ 27.533000] RBP: c16bc1eebc90 R08: 00027080 R09: b8210b0b [ 27.533002] R10: fc35106d5500 R11: 9dde1e86ca90 R12: 9dde0f2db646 [ 27.533003] R13: 9dde1b4b9a80 R14: 9dde195eb000 R15: [ 27.533006] FS: () GS:9dde1ecc() knlGS: [ 27.533008] CS: 0010 DS: ES: CR0: 80050033 [ 27.533010] CR2: 03e8 CR3: 000411ca6000 CR4: 003406a0 [ 27.533011] Call Trace: [ 27.533026] drm_dp_mst_handle_up_req+0x503/0x550 [drm_kms_helper] [ 27.533037] drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper] [ 27.533045] ? drm_dp_mst_hpd_irq+0xbe/0xaa0 [drm_kms_helper] [ 27.533133] handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu] [ 27.533219] ? handle_hpd_rx_irq+0x22c/0x2e0 [amdgpu] [ 27.533306] dm_irq_work_func+0x53/0x70 [amdgpu] [ 27.533309] process_one_work+0x20f/0x410 [ 27.533312] worker_thread+0x34/0x400 [ 27.533315] kthread+0x120/0x140 [ 27.533318] ? process_one_work+0x410/0x410 [ 27.533320] ? __kthread_parkme+0x70/0x70 [ 27.533325] ret_from_fork+0x22/0x40 [ 27.533327] Modules linked in: cmac bnep btusb btrtl btbcm btintel bluetooth ecdh_generic bonding uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media nfc edac_mce_amd kvm_amd ccp kvm arc4 irqbypass nls_iso8859_1 crct10dif_pclmul crc32_pclmul snd_hda_codec_conexant ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm aesni_intel iwlmvm snd_seq_midi snd_seq_midi_event aes_x86_64 crypto_simd mac80211 cryptd snd_rawmidi glue_helper snd_seq iwlwifi snd_seq_device joydev snd_timer input_leds hp_wmi serio_raw sparse_keymap wmi_bmof snd k10temp cfg80211 soundcore ipmi_devintf ipmi_msghandler ucsi_acpi typec_ucsi typec hp_wireless mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 amdgpu chash gpu_sched amd_iommu_v2 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme psmouse ahci drm libahci i2c_piix4 r8169 nvme_core realtek [ 27.533372] wmi i2c_hid hid video [ 27.533378] CR2: 03e8 [ 27.533380] ---[ end trace af80d2e3030b9f18 ]--- ** Tags added: kernel-bug-exists-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/1819924 Title: System hangs when hot-plugging dual monitor dock Status in linux package in Ubuntu: Confirmed Bug description: When plugging in my Cable Matters USB-C Dual 4K DisplayPort Docking Station into my system, after it has already booted, the system hangs with a kernel OOPS. This is always repeatable. Steps to reproduce: 1. Ensure docking station is unplugged or shut-off. 2. Boot up computer. 3. Turn-on docking station and plug into to system. If the docking station is plugged in before the system boots, it works fine. It can even be unpluged and hot-plugged without issue at that point. This kernel Oops occurs when the system hangs: BUG: unable to handle kernel NULL pointer dereference at 0320 PGD 0 P4D 0 SMP NOPTI CPU: 3 PID: 84 Comm: kworker/3:1 Tainted: G DOE 4.18.0-16-generic #17-Ubuntu Hardware name: HP HP EliteBook 755 G5/83D5, BIOS Q81 Ver. 01.04.01 09/13/2018 Workqueue: events_long drm_dp_mst_link_probe_work [drm_kms_helper] RIP: 0010:mutex_lock+0x1d/0x30 Code: 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 8e df ff ff 31 c0 65 48 8b 14 25 00 5c 01 00 48 0f b1 13 74 08 48 89 df e8 b4 ff ff ff 5b 5d c3 90 0f 1f 44 RSP: 0018:b6c0c1efbd78 EFLAGS: 00010246 RAX: RBX: 0320 RCX: 8ed7cfb5c800 RDX: 8ed7d383 RSI: 0202 RDI: 0320 RBP: b6c0c1e
[Kernel-packages] [Bug 1823725] [NEW] packet: reset network header if packet shorter than ll reserved space
Public bug reported:
After backport of linux upstream commit 9ed988cd5915 ("packet: validate
variable length ll headers") (https://kernel.ubuntu.com/git/ubuntu
/ubuntu-bionic.git/commit/?id=c6026847a0a1) the following upstream patch
is missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
** Affects: linux (Ubuntu)
Importance: Undecided
Status: 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/1823725
Title:
packet: reset network header if packet shorter than ll reserved space
Status in linux package in Ubuntu:
Incomplete
Bug description:
After backport of linux upstream commit 9ed988cd5915 ("packet:
validate variable length ll headers")
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823725] 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 1823725
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/1823725
Title:
packet: reset network header if packet shorter than ll reserved space
Status in linux package in Ubuntu:
Incomplete
Bug description:
After backport of linux upstream commit 9ed988cd5915 ("packet:
validate variable length ll headers")
(https://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=c6026847a0a1) the following upstream patch is
missing :
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ed988cd5915
9ed988cd5915 ("packet: validate variable length ll headers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823725/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
Hi Michael R, I tried to apply your patches to test them and support the effort to get them included in the Bionic kernel, but I'm having some trouble applying them: ubuntu@dja-bionic:~/bionic$ git am ../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch Patch format detection failed. ubuntu@dja-bionic:~/bionic$ git am ../patches/01-powerpc-64s-add-support-for-ori-barrier_nospec.patch --patch-format mbox Applying: commit 2eea7f067f495e33b8b116b35b5988ab2b8aec55 fatal: empty ident name (for <>) not allowed How are you generating them? They don't look like they've been generated with git format-patch...? Regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Promote to Proposed phase-changed: Monday, 08. April 2019 09:57 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822883] Re: linux: 3.13.0-169.219 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - - backports: bug 1822882 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 05. April 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1822883 Title: linux: 3.13.0-169.219 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 05. April 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822882] Re: linux-lts-trusty: -proposed tracker
** Tags removed: kernel-sru-backport-of-1822883 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1822883 phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 14:32 UTC reason: prepare-package: Pending -- version not specified ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1822882 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Ready for Packaging phase-changed: Wednesday, 03. April 2019 14:32 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822805] Re: linux-aws: 4.15.0-1036.38 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Promote to Proposed - phase-changed: Monday, 08. April 2019 10:36 UTC + phase: Testing + phase-changed: Monday, 08. April 2019 14:06 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap aws-kernel not in expected channel(s): amd64:18/beta' + snap-release-to-edge: 'Pending -- snap aws-kernel not in expected channel(s): amd64:18/edge' + verification-testing: Ongoing -- testing in progress -- 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/1822805 Title: linux-aws: 4.15.0-1036.38 -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-signing-to-proposed series: Invalid 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 snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Monday, 08. April 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap aws-kernel not in expected channel(s): amd64:18/beta' snap-release-to-edge: 'Pending -- snap aws-kernel not in expected channel(s): amd64:18/edge' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1709889] Re: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
The fixes identified here are available in Bionic:
5be6b75610ce cfq-iosched: fix the delay of cfq_group's vdisktime under iops mode
142bbdfccc8b cfq: Disable writeback throttling by default
marking this bug as fix-released. Please retest with latest Bionic
kernel and reopen this bug if this is still an issue.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Released
** Changed in: ubuntu-power-systems
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/1709889
Title:
Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Bionic:
Fix Released
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic - still valid up to latest kernel in Bionic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
Hi Leonardo, unfortunately there was an issue with the SRU request and Juerg NACK-ed it, please have a look here: https://lists.ubuntu.com/archives/kernel-team/2019-March/099128.html Please re-submit the SRU request with the requested corrections. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** 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/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ubuntu-power-systems 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/1766201 Title: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Application Cdeadmin - 2018-04-20 05:56:03 == == Comment: #1 - Application Cdeadmin - 2018-04-20 05:56:05 == State: Open by: stccdenv on 18 April 2018 06:27:28 This defect was opened automatically using defect_template with only logs. Please refer to 2nd seq for the problem description. ==Automatic entries== Full Log: http://w3.austin.ibm.com/afs/awd.austin.ibm.com/u/stccdenv/logs/devops4fp1_defect_template_20180418060138 Contact: Thirukumaran V T (thirukuma...@in.ibm.com), Tommy Adams(tnad...@us.ibm.com) Backup: Atit Patel (a...@us.ibm.com) System Name: devops4fp1 FSP IP: 9.3.136.192 (devops4fp1.aus.stglabs.ibm.com) System Firmware Level: Current Side Driver:.fips861/b0413a_1816.861 Non-Current Side Driver:.fips861/b0410a_1816.861 Lpar Access: Please refer https://pcajet.aus.stglabs.ibm.com/ for the lab password. (The Lab Test Passwords are now accessible only through the auto or manual install web apps. For example, from the manual install web app, enter your email address, check the Lab Passwords checkbox and then click on Submit.) (To access the Lpars in 10.33.x.x network, login to any LCB or HMC then ssh/telnet to 10.33.x.x lpars) --- HMC IP: 9.3.118.110 (vhmccloudtst100.aus.stglabs.ibm.com) HMC Version: "version= Version: 9 Release: 1 Service Pack: 910 HMC Build level 1803052221 ","base_version=V9R1 " --- =Logs SNAP : devops4p02: /tmp/ibmsupt/snap.pax.Z.devops4p02.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p02.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p02 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p02 devops4p03: /tmp/ibmsupt/snap.pax.Z.devops4p03.180418060149 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p03.180418060149 /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p03 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p03 devops4p04: /tmp/ibmsupt/snap.pax.Z.devops4p04.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p04.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p04 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p04 devops4p05: /tmp/ibmsupt/snap.pax.Z.devops4p05.180418060148 and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/snap.pax.Z.devops4p05.180418060148 /tmp/IBM.DRM.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060148.tar.gz.devops4p05 /tmp/htx.180418060148.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060148.tar.gz.devops4p05 devops4p06: /tmp/ctsupt/ctsnap.linux-hjmh.04180701.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.linux-hjmh.04180701.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/log/nts_linux-hjmh_180418_0703.tbz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/nts_linux-hjmh_180418_0703.tbz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p06 /tmp/htx.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/htx.180418060149.tar.gz.devops4p06 devops4p07: /tmp/ctsupt/ctsnap.devops4p07.04180601.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/ctsnap.devops4p07.04180601.tar.gz /tmp/var_log.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/var_log.180418060149.tar.gz /var/tmp/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/sosreport-devops4p07.aus.stglabs.ibm.com-20180418060350.tar.xz /tmp/IBM.DRM.180418060149.tar.gz and also @ (NFS)9.41.164.242:/fspmount/hmc_dumps/IBM.DRM.180418060149.tar.gz.devops4p07 /tmp/htx.
[Kernel-packages] [Bug 1811470] Re: [witherspoon] removing module nouveau causes cpu hard lockup
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-power-systems Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811470 Title: [witherspoon] removing module nouveau causes cpu hard lockup Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: Installed 18.04 and upgraded kernel to linux-image-generic-hwe-18.04 (4.18.0-13-generic #14~18.04.1-Ubuntu SMP Thu Dec 6 14:03:47). Copied gv100 firmware to /lib/firmware/nvidia, removed and reloaded nouveau (modprobe -r and modprobe). Tried to remove nouveau again using modprobe -r and I see the trace below. After a while the modprobe -r command completed the module was removed successfully. [ 618.185258] nouveau 0035:04:00.0: DRM: failed to idle channel 1 [DRM] [ 630.314599] watchdog: CPU 4 self-detected hard LOCKUP @ ioread32+0x2c/0x170 [ 630.314601] watchdog: CPU 4 TB:415266697100, last heartbeat TB:410146341428 (1ms ago) [ 630.314601] Modules linked in: nouveau(-) ofpart at24 cmdlinepart uio_pdrv_genirq ipmi_powernv ipmi_devintf powernv_flash uio mtd opal_prd ipmi_msghandler ibmpowernv vmx_crypto sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm crct10dif_vpmsum ahci crc32c_vpmsum tg3 libahci drm_panel_orientation_quirks [last unloaded: nouveau] [ 630.314629] CPU: 4 PID: 6623 Comm: modprobe Not tainted 4.18.0-13-generic #14~18.04.1-Ubuntu [ 630.314630] NIP: c0729afc LR: c0080f766990 CTR: c0729ad0 [ 630.314630] REGS: c03fffd87d80 TRAP: 0900 Not tainted (4.18.0-13-generic) [ 630.314631] MSR: 9280b033 CR: 44002824 XER: [ 630.314638] CFAR: c0080f7b2ac4 IRQMASK: 1 [ 630.314639] GPR00: c0080f7ad3f8 c03f6c1bb850 c178c200 c00c8e7e [ 630.314642] GPR04: 0008 [ 630.314644] GPR08: c03fa800 7fff c00c8e7e c0080f7b2ab0 [ 630.314647] GPR12: c0729ad0 c03fa800 0001 [ 630.314649] GPR16: 039a7cc60074 039a7cc3c978 [ 630.314652] GPR20: 039a7cc60070 78448f88 [ 630.314654] GPR24: 039a8bf40ee8 c0080f82dca0 c03fed072098 [ 630.314657] GPR28: c000203968a2c290 c000203968840908 c000203968840900 0001 [ 630.314660] NIP [c0729afc] ioread32+0x2c/0x170 [ 630.314660] LR [c0080f766990] nouveau_bo_rd32+0x48/0x70 [nouveau] [ 630.314661] Call Trace: [ 630.314662] [c03f6c1bb850] [c03f6c1bb890] 0xc03f6c1bb890 (unreliable) [ 630.314663] [c03f6c1bb880] [c03f6c1bb8b0] 0xc03f6c1bb8b0 [ 630.314664] [c03f6c1bb8a0] [c0080f7ad3f8] nv84_fence_read+0x40/0x60 [nouveau] [ 630.314666] [c03f6c1bb8c0] [c0080f7aab3c] nouveau_fence_update+0x44/0x100 [nouveau] [ 630.314667] [c03f6c1bb900] [c0080f7ab5d8] nouveau_fence_done+0x100/0x180 [nouveau] [ 630.314668] [c03f6c1bb940] [c0080f7ab8c8] nouveau_fence_wait+0x90/0x150 [nouveau] [ 630.314669] [c03f6c1bb970] [c0080f7a8f90] nouveau_channel_idle+0xd8/0x140 [nouveau] [ 630.314670] [c03f6c1bba00] [c0080f75f75c] nouveau_accel_fini+0x74/0xe0 [nouveau] [ 630.314671] [c03f6c1bba30] [c0080f75f8e8] nouveau_drm_unload+0x60/0x130 [nouveau] [ 630.314672] [c03f6c1bba60] [c00813b1b118] drm_dev_unregister+0x70/0x160 [drm] [ 630.314673] [c03f6c1bbaa0] [c00813b1b3f0] drm_put_dev+0x48/0xa0 [drm] [ 630.314675] [c03f6c1bbb10] [c0080f760f8c] nouveau_drm_device_remove+0x54/0x90 [nouveau] [ 630.314676] [c03f6c1bbb50] [c07a746c] pci_device_remove+0x6c/0x120 [ 630.314677] [c03f6c1bbb90] [c08a7014] device_release_driver_internal+0x294/0x380 [ 630.314678] [c03f6c1bbbe0] [c08a719c] driver_detach+0x7c/0x140 [ 630.314679] [c03f6c1bbc20] [c08a5304] bus_remove_driver+0x84/0x170 [ 630.314680] [c03f6c1bbc90] [c08a7ef8] driver_unregister+0x48/0x90 [ 630.314681] [c03f6c1bbd00] [c07a52b8] pci_unregister_driver+0x38/0x150 [ 630.314682] [c03f6c1bbd50] [c0080f7af048] nouveau_drm_exit+0x30/0xfc08 [nouveau] [ 630.314683] [c03f6c1bbd70] [c01e6b14] sys_delete_module+0x1d4/0x310 [ 630.314684] [c03f6c1bbe30] [c000b288] system_call+0x5
