[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Hello, I confirm that the incident is resolved. I updated Ubuntu 22.04 server remotely via SSH (on a Dell PowerEdge R210 II server with a Matrox MGA G200eW WPCM450 internal card) and the local console (by plugging a monitor into the server's VGA port) works fine. $ uname -a Linux serveur 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Thanks, Vivien -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
I tested Ubuntu server 21.10 and everything is ok. Ubuntu server 22.04 with kernel 5.15.0-30-generic: no screen display, unless I boot in safe mode (choice available at GRUB level) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
On a Dell PowerEdge R210 II server I have the same problem: - Ubuntu 22.04 server launched from a liveusb: The screen remains black after loading the kernel - Ubuntu 22.04 desktop launched from a liveusb: The screen remains black after loading the kernel - Update Ubuntu 22.04 server on Ubuntu 21.10 server: The screen is black on reboot while ok under Ubuntu 21.10. Ssh is ok. 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) (prog-if 00 [VGA controller]) DeviceName: Embedded Video Subsystem: Dell MGA G200eW WPCM450 Flags: bus master, medium devsel, latency 0, IRQ 19, IOMMU group 5 Memory at c400 (32-bit, prefetchable) [size=8M] Memory at c500 (32-bit, non-prefetchable) [size=16K] Memory at c480 (32-bit, non-prefetchable) [size=8M] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [dc] Power Management version 1 Kernel driver in use: mgag200 Kernel modules: matroxfb_base, mgag200 $ sudo dmesg | grep -i mgag200 [3.030128] fb0: switching to mgag200 from EFI VGA [3.046095] mgag200 :03:03.0: vgaarb: deactivate vga console [3.049400] [drm] Initialized mgag200 1.0.0 20110418 for :03:03.0 on minor 0 [3.051146] fbcon: mgag200drmfb (fb0) is primary device [3.051975] mgag200 :03:03.0: [drm] drm_plane_enable_fb_damage_clips() not called [3.502482] mgag200 :03:03.0: [drm] fb0: mgag200drmfb frame buffer device $ uname -a Linux serveur 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable
Using 5.8.0-51 has fixed the problem for me. My PC : - Dell Inc. Inspiron 3847/088DT1, BIOS A11 05/07/2019 - EFI v2.31 by American Megatrends - Secure boot disable - CPU : Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz - GPU : Intel HD Graphics 4400 - A single screen connected via HDMI. Resolution: 1920x1080 - RAM : 16 GB DDR3 My Ubuntu 20.10 : - X11 - GNOME 3.38.2 - French language -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-5.8 package in Ubuntu: Confirmed Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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)
I updated the Ubuntu servers affected by the "tx_timeout" problem with the Kernel HWE => I do not meet any more "tx_timeout" since this update. Command used to install kernel 4.18 : sudo apt install --install-recommends linux-generic-hwe-18.04 Network card driver i40e : - Linux 4.15 : Intel(R) Ethernet Connection XL710 Network Driver - version 2.1.14-k - Linux 4.18 : Intel(R) Ethernet Connection XL710 Network Driver - version 2.3.2-k -- You 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: In Progress Status in linux source package in Bionic: In Progress Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
How to know in which kernels are these patches? Using the kernel linux-generic-hwe-18.04-edge (kernel used for Ubuntu 18.10) solves the problem ? -- You 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: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)
** Summary changed: - i40e driver does not work with kernel 4.15 + Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware 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-firmware package in Ubuntu: Confirmed Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+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 1779756] Re: i40e driver does not work with kernel 4.15
Cf bug https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1795587 Intel released the 6.01 Firmware for the Intel XL710 network cards. As stated in the feature support matrix [1] in the table 9 on page 18, the minimum kernel driver version for the 6.01 Firmware i40e must be 2.1.26, the recent driver version is 2.4.10 [2] The i40 driver version included in the 4.15.0-36 (Bionic, LTS) is 2.1.14-k. $ uname -a Linux ubuntu-bionic 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ modinfo i40e filename: /lib/modules/4.15.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko version: 2.1.14-k license: GPL description: Intel(R) Ethernet Connection XL710 Network Driver Release notes: [3] [4] [5] [6] [7] The firmware 6.01 introduce better performance for DPDK and SR-IOV applications for those cards, and NFV application workloads would perform better. [1] Intel® Ethernet Controller X710/ XXV710/XL710 Feature Support Matrix https://www.intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-matrix.pdf [2] Intel® Network Adapter Driver for PCIe* 40 Gigabit Ethernet Network Connections Under Linux* https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=75021 [3] Intel(R) Network Connections Software Version 23.2 Release Notes https://downloadmirror.intel.com/24411/eng/readme.txt [4] Intel(R) Network Connections Software Version 23.1 Release Notes https://downloadmirror.intel.com/27869/eng/readme.txt [5] Intel(R) Network Connections Software Version 22.10 Release Notes https://downloadmirror.intel.com/27547/eng/readme.txt [6] Intel(R) Network Connections Software Version 22.9 Release Notes https://downloadmirror.intel.com/27547/eng/readme.txt [7] Intel(R) Network Connections Software Version 22.6 Release Notes https://downloadmirror.intel.com/27189/eng/readme.txt ** Package changed: linux-meta-hwe (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1779756 Title: i40e driver does not work with kernel 4.15 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel 4.13 to the Kernel 4.15.0-24-generic. On a "Dell PowerEdge R330" server with a network adapter "Intel Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network card no longer works and permanently displays these three lines : [ 98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1 [ 98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, hung_queue 8 [ 98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+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 1795587] Re: Upgrade i40e driver to support 6.01 Firmware - Intel XL710
Does this have any connection to the bug "i40e driver does not work with kernel 4.15" described on https://bugs.launchpad.net/ubuntu/+source /linux-meta-hwe/+bug/1779756 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1795587 Title: Upgrade i40e driver to support 6.01 Firmware - Intel XL710 Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: Intel released the 6.01 Firmware for the Intel XL710 network cards. As stated in the feature support matrix [1] in the table 9 on page 18, the minimum kernel driver version for the 6.01 Firmware i40e must be 2.1.26, the recent driver version is 2.4.10 [2] The i40 driver version included in the 4.15.0-36 (Bionic, LTS) is 2.1.14-k. $ uname -a Linux ubuntu-bionic 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ modinfo i40e filename: /lib/modules/4.15.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko version:2.1.14-k license:GPL description:Intel(R) Ethernet Connection XL710 Network Driver Release notes: [3] [4] [5] [6] [7] The firmware 6.01 introduce better performance for DPDK and SR-IOV applications for those cards, and NFV application workloads would perform better. [1] Intel® Ethernet Controller X710/ XXV710/XL710 Feature Support Matrix https://www.intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-matrix.pdf [2] Intel® Network Adapter Driver for PCIe* 40 Gigabit Ethernet Network Connections Under Linux* https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=75021 [3] Intel(R) Network Connections Software Version 23.2 Release Notes https://downloadmirror.intel.com/24411/eng/readme.txt [4] Intel(R) Network Connections Software Version 23.1 Release Notes https://downloadmirror.intel.com/27869/eng/readme.txt [5] Intel(R) Network Connections Software Version 22.10 Release Notes https://downloadmirror.intel.com/27547/eng/readme.txt [6] Intel(R) Network Connections Software Version 22.9 Release Notes https://downloadmirror.intel.com/27547/eng/readme.txt [7] Intel(R) Network Connections Software Version 22.6 Release Notes https://downloadmirror.intel.com/27189/eng/readme.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15
** Description changed: - At boot time there are many periods when the boot freezes before the timeout of 10 seconds. + With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 Integrated Graphics (driver i915). In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! Regression is present since linux kernel 4.8 with Ubuntu 16.04 To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. ** Description changed: With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 Integrated Graphics (driver i915). In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! - Regression is present since linux kernel 4.8 with Ubuntu 16.04 + Regression is present since linux kernel 4.8 (with Ubuntu 16.04). To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767808 Title: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15 Status in linux package in Ubuntu: New Bug description: With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 Integrated Graphics (driver i915). In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! Regression is present since linux kernel 4.8 (with Ubuntu 16.04). To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767808] [NEW] "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15
Public bug reported: At boot time there are many periods when the boot freezes before the timeout of 10 seconds. In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! Regression is present since linux kernel 4.8 with Ubuntu 16.04 To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: gm965 i915 ** Attachment added: "dmesg Ubuntu 18.04 with Intel Mobile GM965/GL960 Integrated Graphics" https://bugs.launchpad.net/bugs/1767808/+attachment/5130165/+files/201804_ubuntu1804_kernel_4.15.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767808 Title: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15 Status in linux package in Ubuntu: New Bug description: At boot time there are many periods when the boot freezes before the timeout of 10 seconds. In total it is 198 seconds that are lost in these timeouts during boot, more than 3 minutes! Regression is present since linux kernel 4.8 with Ubuntu 16.04 To fix, explicitly disable the port with an i915 module setting with video=SVIDEO-1:d in the kernel command line parameter in the bootloader. 1/ sudo gedit /etc/default/grub 2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line 3/ sudo update-grub After applying this, the system boots up much faster, there are no "drm ... timed out" messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
For how long do the Xenial HWE kernels stay in the "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/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Bug description:
== SRU Justification ==
We are seeing this on multiple servers after upgrading from previous 4.10
series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory
is continously decreasing at a high rate and the servers start swapping and
finally OOMing services within days. With the 4.10 kernel, decrease of free
memory is slower and stabilizes after a while.
Latest kernel tested is linux-image-4.13.0-32-generic but the issue
also affects older kernels from that series, tested back to linux-
image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic.
The servers are running as OpenStack controller nodes using either
Ocata or Pike UCA plus ceph. See attached graph for the memory
behaviour.
== Fix ==
2b9478ffc550("i40e: Fix memory leak related filter programming status")
62b4c6694dfd("i40e: Add programming descriptors to cleaned_count")
== Regression Potential ==
Low. Limited to i40e and fix existing regression.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 9 09:45:50 2018
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
I have a significant memory leak after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series for Ubuntu 16.04 server with Ethernet controller Intel X710 for 10GbE SFP+ # dmesg | grep i40e [1.625565] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 2.1.14-k [1.625565] i40e: Copyright (c) 2013 - 2014 Intel Corporation. [1.688509] i40e :02:00.0: fw 5.40.47690 api 1.5 nvm 5.40 0x80002d35 18.0.17 [1.959126] i40e :02:00.0: MAC address: 3c:fd:fe:1a:1d:e0 [2.060021] i40e :02:00.0: PCI-Express: Speed 8.0GT/s Width x4 [2.060091] i40e :02:00.0: PCI-Express bandwidth available for this device may be insufficient for optimal performance. [2.060096] i40e :02:00.0: Please move the device to a different PCI-e link with more lanes and/or higher transfer rate. [2.085931] i40e :02:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 8 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA [2.140793] i40e :02:00.1: fw 5.40.47690 api 1.5 nvm 5.40 0x80002d35 18.0.17 [2.422817] i40e :02:00.1: MAC address: 3c:fd:fe:1a:1d:e2 [2.442684] i40e :02:00.1: PCI-Express: Speed 8.0GT/s Width x4 [2.442696] i40e :02:00.1: PCI-Express bandwidth available for this device may be insufficient for optimal performance. [2.442715] i40e :02:00.1: Please move the device to a different PCI-e link with more lanes and/or higher transfer rate. [2.443043] i40e :02:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 8 RSS FD_ATR FD_SB NTUPLE DCB VxLAN Geneve PTP VEPA [2.480205] i40e :02:00.0 enp2s0f0: renamed from eth1 [2.512183] i40e :02:00.1 enp2s0f1: renamed from eth0 [5.800514] i40e :02:00.0 enp2s0f0: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None ** Attachment added: "201802_nperf_memory-week.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+attachment/5063316/+files/201802_nperf_memory-week.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Is-it possible to build new ISOs of Ubuntu 17.10, with the kernel version 4.13.0-21 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D
I have the same problem with a Dell PowerEdge R210 II, with Dell DRAC under Ubuntu Server 14.04 LTS and 3.13 kernel: Process khubd will block in state D too. => need to do a hard reboot Screenshot of htop: https://lafibre.info/serveur-linux/load- average/msg372058/#msg372058 The "dmesg" data corresponding ; [11273834.551052] type=1400 audit(1473524094.532:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=22297 comm="apparmor_parser" [11273834.551236] type=1400 audit(1473524094.532:29): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=22297 comm="apparmor_parser" [11273834.551388] type=1400 audit(1473524094.532:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=22297 comm="apparmor_parser" [11359185.861753] usb 1-1.1: reset full-speed USB device number 3 using ehci-pci [11359190.938076] usb 1-1.1: device descriptor read/64, error -32 [11359191.114227] usb 1-1.1: device descriptor read/64, error -32 [11359191.290375] usb 1-1.1: reset full-speed USB device number 3 using ehci-pci [11359191.362427] usb 1-1.1: device descriptor read/64, error -32 [11359191.538586] usb 1-1.1: device descriptor read/64, error -32 [11359191.714748] usb 1-1.1: reset full-speed USB device number 3 using ehci-pci [11359192.123084] usb 1-1.1: device not accepting address 3, error -32 [11359192.195140] usb 1-1.1: reset full-speed USB device number 3 using ehci-pci [11359192.603502] usb 1-1.1: device not accepting address 3, error -32 [11359192.604316] usb 1-1.1: USB disconnect, device number 3 [11359384.590873] INFO: task khubd:71 blocked for more than 120 seconds. [11359384.591241] Not tainted 3.13.0-85-generic #129-Ubuntu [11359384.591574] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11359384.592047] khubd D 88043fc93180 071 2 0x [11359384.592052] 880428cd7c80 0046 8804293d6000 880428cd7fd8 [11359384.592057] 00013180 00013180 8804293d6000 880428c290e8 [11359384.592061] 880428c290ec 8804293d6000 880428c290f0 [11359384.592065] Call Trace: [11359384.592074] [] schedule_preempt_disabled+0x29/0x70 [11359384.592078] [] __mutex_lock_slowpath+0x135/0x1b0 [11359384.592082] [] mutex_lock+0x1f/0x2f [11359384.592088] [] usb_disconnect+0x64/0x200 [11359384.592091] [] hub_port_connect_change+0xd3/0xb20 [11359384.592096] [] ? hub_port_status+0xdd/0x120 [11359384.592099] [] hub_events+0x4d4/0xa20 [11359384.592102] [] hub_thread+0x35/0x160 [11359384.592106] [] ? prepare_to_wait_event+0x100/0x100 [11359384.592109] [] ? hub_events+0xa20/0xa20 [11359384.592113] [] kthread+0xd2/0xf0 [11359384.592117] [] ? kthread_create_on_node+0x1c0/0x1c0 [11359384.592121] [] ret_from_fork+0x58/0x90 [11359384.592125] [] ? kthread_create_on_node+0x1c0/0x1c0 [11359384.592133] INFO: task kworker/4:2:18579 blocked for more than 120 seconds. [11359384.592544] Not tainted 3.13.0-85-generic #129-Ubuntu [11359384.592869] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11359384.593321] kworker/4:2 D 88043fd13180 0 18579 2 0x [11359384.593336] Workqueue: events hid_reset [usbhid] [11359384.593338] 8803f27af850 0046 8800badb9800 8803f27affd8 [11359384.593341] 00013180 00013180 8800badb9800 8803f27af998 [11359384.593345] 8803f27af9a0 7fff 8800badb9800 8800badb9800 [11359384.593348] Call Trace: [11359384.593352] [] schedule+0x29/0x70 [11359384.593355] [] schedule_timeout+0x279/0x320 [11359384.593359] [] ? __enqueue_entity+0x78/0x80 [11359384.593364] [] ? enqueue_entity+0x2ad/0xc00 [11359384.593367] [] wait_for_completion+0xa6/0x160 [11359384.593372] [] ? wake_up_state+0x20/0x20 [11359384.593377] [] flush_work+0xed/0x1b0 [11359384.593381] [] ? wake_up_worker+0x30/0x30 [11359384.593385] [] __cancel_work_timer+0x92/0x1a0 [11359384.593390] [] ? lock_timer_base.isra.35+0x2b/0x50 [11359384.593394] [] cancel_work_sync+0x10/0x20 [11359384.593400] [] usbhid_close+0xbc/0x100 [usbhid] [11359384.593407] [] hidinput_close+0x22/0x30 [hid] [11359384.593412] [] input_close_device+0x4a/0x70 [11359384.593417] [] evdev_cleanup+0xbf/0xd0 [11359384.593421] [] evdev_disconnect+0x2b/0x60 [11359384.593425] [] __input_unregister_device+0xc5/0x1b0 [11359384.593429] [] input_unregister_device+0x4d/0x80 [11359384.593436] [] hidinput_disconnect+0x96/0xc0 [hid] [11359384.593442] [] hid_disconnect+0x60/0x70 [hid] [11359384.593447] [] hid_device_remove+0xbd/0xd0 [hid] [11359384.593453] [] __device_release_driver+0x7f/0xf0 [11359384.593457] [] device_release_driver+0x23/0x30 [11359384.593461] [] bus_remove_device+0x108/0x180 [11359384.593464] [] device_del+0x129/0x1c0
