[Kernel-packages] [Bug 1846214] Re: Freezes instead of suspending, most times
Please collect log via `journalctl -b -1 -k` at next boot after freeze. -- 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/1846214 Title: Freezes instead of suspending, most times Status in linux package in Ubuntu: Confirmed Bug description: Hi and thank you for all your free software work. This system usually freezes instead of suspending. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mightyiam 2139 F pulseaudio /dev/snd/controlC0: mightyiam 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:28:30 2019 MachineType: Micro-Star International Co., Ltd. GS60 2QE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H5IMS.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GS60 2QE dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Sorry, forgot to mention that I'm on eoan since yesterday and this error did not appear in disco -- 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/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [ 85.320174] iwlwifi :3b:00.0: 0xE000
[Kernel-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
So I guess `sudo apt build-dep linux` was missed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, when I turn off the computer, it hangs on the logo. I can not turn off the computer using alt + SysRq + REISUO. The light on the system unit continues to light, and the fan runs. This is a problem with kernel 5.0, 5.3. There is no such problem with the 4.15 kernel. It happens that after 90 seconds it turns off. And with a new core, he writes that he will turn off after 90 seconds, but he will not turn off. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq https://ibb.co/4JMGwvC sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ ProblemType: Bug DistroRelease: Ubuntu 18.04 Пакет: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 CurrentDesktop: XFCE Дата: Четверг 5 09:44:35 2019 Дата установки: установлено в 2019-08 -09 (26 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) ProcEnviron: LANGUAGE = ru_UA: ru PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_UA.UTF -8 SHELL = / bin / bash SourcePackage: gvfs UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- Тип проблемы: ошибка ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 AudioDevicesInUse: КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID / dev / snd / controlC0: макс. 1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Установлен 2019-08-09 (37 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) IwConfig: enp0s25 без беспроводных расширений. enp7s4 нет беспроводных расширений. нет никаких беспроводных расширений. Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower Пакет: Linux (не установлен) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 RelatedPackageV ersions: linux- restricted- modules- 4.15.0- 62-родовое N / A linux- backports- modules- 4.15.0 - 62-типовой N / A linux-прошивка 1.173.9 RfKill: Теги: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: нет журнала обновления (возможно, новая установка) Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 26.10.2015 dmi. bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board. asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis. asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: rn2820h: rvr: cvnHewlett- Packard: ct6: cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dvtwelet dv00 от компании HP : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
[ 14158.623] (II) NVIDIA(0): Setting mode "NULL" [ 14159.837] (EE) modeset(G0): failed to set mode: No such file or directory -- 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/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 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/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
Can you confirm it doesn't happen under 4.15 based kernel? -- 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/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 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/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
[ 14158.623] (II) NVIDIA(0): Setting mode "NULL" [ 14159.837] (EE) modeset(G0): failed to set mode: No such file or directory [ 14159.837] (EE) Fatal server error: [ 14159.837] (EE) EnterVT failed for gpu screen 0 [ 14159.837] (EE) [ 14159.837] (EE) -- 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/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 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/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849136] Re: errors at boot and long boot time
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc4/ -- 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/1849136 Title: errors at boot and long boot time Status in linux package in Ubuntu: Confirmed Bug description: I tried to install Xubuntu 18.04 LTS on a Fujitsu Lifebook E8310 but this did not boot. I then installed Xubuntu 16.04 LTS 64bit and it boots but it takes quite a long time. DMESG shows a number of error messages starting at 12 seconds, its output file is attached. The errors seem to relate to the graphics which is recognized as i915 but may be actually i955 related with the T9300 CPU that I use. The Lifebook itsself is OK as the original XP 32bit runs without any problem. --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guenter1339 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=b4d1b02c-67e6-47d4-a407-42c52c4703d2 InstallationDate: Installed on 2019-10-19 (2 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: FUJITSU SIEMENS LIFEBOOK E8310 Package: linux (not installed) ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-65-generic root=UUID=2a7f1443-a47f-44f3-b55c-2c7566879d06 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-65.74~16.04.1-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-65-generic N/A linux-backports-modules-4.15.0-65-generic N/A linux-firmware 1.157.22 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: irda smsc_ircc2 Tags: xenial staging Uname: Linux 4.15.0-65-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/31/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNB1CE dmi.board.vendor: FUJITSU dmi.board.version: 1PCP331350-04 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E8310 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd05/31/2010:svnFUJITSUSIEMENS:pnLIFEBOOKE8310:pvr:rvnFUJITSU:rnFJNB1CE:rvr1PCP331350-04:cvnFUJITSUSIEMENS:ct10:cvrE8310: dmi.product.name: LIFEBOOK E8310 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Getting the same error on an Asus Zenbook UX330 dmesg output is: [6.324661] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [6.475651] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [6.556523] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 10.059533] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x1200. [ 10.059779] iwlwifi :02:00.0: Start IWL Error Log Dump: [ 10.059781] iwlwifi :02:00.0: Status: 0x0080, count: 6 [ 10.059782] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 [ 10.059783] iwlwifi :02:00.0: 0x0038 | BAD_COMMAND [ 10.059784] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 [ 10.059785] iwlwifi :02:00.0: 0x | trm_hw_status1 [ 10.059785] iwlwifi :02:00.0: 0x00024200 | branchlink2 [ 10.059786] iwlwifi :02:00.0: 0x00039872 | interruptlink1 [ 10.059787] iwlwifi :02:00.0: 0x | interruptlink2 [ 10.059788] iwlwifi :02:00.0: 0x00350405 | data1 [ 10.059788] iwlwifi :02:00.0: 0x0036 | data2 [ 10.059789] iwlwifi :02:00.0: 0x0036 | data3 [ 10.059790] iwlwifi :02:00.0: 0x000A3DD4 | beacon time [ 10.059791] iwlwifi :02:00.0: 0x0035CA2C | tsf low [ 10.059791] iwlwifi :02:00.0: 0x | tsf hi [ 10.059792] iwlwifi :02:00.0: 0x | time gp1 [ 10.059793] iwlwifi :02:00.0: 0x0035CA2D | time gp2 [ 10.059794] iwlwifi :02:00.0: 0x0001 | uCode revision type [ 10.059794] iwlwifi :02:00.0: 0x0024 | uCode version major [ 10.059795] iwlwifi :02:00.0: 0x77D01142 | uCode version minor [ 10.059796] iwlwifi :02:00.0: 0x0201 | hw version [ 10.059797] iwlwifi :02:00.0: 0x00489008 | board version [ 10.059798] iwlwifi :02:00.0: 0x00350405 | hcmd [ 10.059798] iwlwifi :02:00.0: 0x00022080 | isr0 [ 10.059799] iwlwifi :02:00.0: 0x | isr1 [ 10.059800] iwlwifi :02:00.0: 0x28201802 | isr2 [ 10.059801] iwlwifi :02:00.0: 0x00400080 | isr3 [ 10.059801] iwlwifi :02:00.0: 0x | isr4 [ 10.059802] iwlwifi :02:00.0: 0x003401C8 | last cmd Id [ 10.059803] iwlwifi :02:00.0: 0x | wait_event [ 10.059804] iwlwifi :02:00.0: 0x1AEB | l2p_control [ 10.059804] iwlwifi :02:00.0: 0x | l2p_duration [ 10.059805] iwlwifi :02:00.0: 0x | l2p_mhvalid [ 10.059806] iwlwifi :02:00.0: 0x | l2p_addr_match [ 10.059807] iwlwifi :02:00.0: 0x008F | lmpm_pmg_sel [ 10.059808] iwlwifi :02:00.0: 0x08081421 | timestamp [ 10.059808] iwlwifi :02:00.0: 0x3048 | flow_handler [ 10.059997] iwlwifi :02:00.0: Start IWL Error Log Dump: [ 10.059998] iwlwifi :02:00.0: Status: 0x0080, count: 7 [ 10.059998] iwlwifi :02:00.0: 0x0070 | NMI_INTERRUPT_LMAC_FATAL [ 10.05] iwlwifi :02:00.0: 0x | umac branchlink1 [ 10.06] iwlwifi :02:00.0: 0xC0086B38 | umac branchlink2 [ 10.060001] iwlwifi :02:00.0: 0xC0083D08 | umac interruptlink1 [ 10.060002] iwlwifi :02:00.0: 0xC0087F7C | umac interruptlink2 [ 10.060002] iwlwifi :02:00.0: 0x0800 | umac data1 [ 10.060003] iwlwifi :02:00.0: 0xC0087F7C | umac data2 [ 10.060004] iwlwifi :02:00.0: 0xDEADBEEF | umac data3 [ 10.060005] iwlwifi :02:00.0: 0x0024 | umac major [ 10.060005] iwlwifi :02:00.0: 0x77D01142 | umac minor [ 10.060006] iwlwifi :02:00.0: 0xC0887EE0 | frame pointer [ 10.060007] iwlwifi :02:00.0: 0xC0887EE0 | stack pointer [ 10.060008] iwlwifi :02:00.0: 0x00350405 | last host cmd [ 10.060008] iwlwifi :02:00.0: 0x4008 | isr status reg [ 10.060151] iwlwifi :02:00.0: Fseq Registers: [ 10.060156] iwlwifi :02:00.0: 0xDB6464ED | FSEQ_ERROR_CODE [ 10.060160] iwlwifi :02:00.0: 0x1980D092 | FSEQ_TOP_INIT_VERSION [ 10.060165] iwlwifi :02:00.0: 0x060B1020 | FSEQ_CNVIO_INIT_VERSION [ 10.060169] iwlwifi :02:00.0: 0xA056 | FSEQ_OTP_VERSION [ 10.060174] iwlwifi :02:00.0: 0x7C0C6D24 | FSEQ_TOP_CONTENT_VERSION [ 10.060179] iwlwifi :02:00.0: 0x0DF8FB3C | FSEQ_ALIVE_TOKEN [ 10.060183] iwlwifi :02:00.0: 0x66298AF9 | FSEQ_CNVI_ID [ 10.060188] iwlwifi :02:00.0: 0xA7164D37 | FSEQ_CNVR_ID [ 10.060192] iwlwifi :02:00.0: 0x0300 | CNVI_AUX_MISC_CHIP [ 10.060200] iwlwifi :02:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP [ 10.060208] iwlwifi :02:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 10.060215] iwlwifi :02:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 10.060225] iwlwifi :02:00.0: Collecting data: trigger 2 fired. [ 10.060228] ieee80211 phy0: Hardware restart was requested [ 10.060245] iwlwifi :02:00.0: iwlwifi transaction failed, dumping registers [ 10.060246] iwlwifi :02:00.0: iwlwifi device config registers: [ 10.060559] iwlwifi :02:00.0: : 24f38086 00100
[Kernel-packages] [Bug 1846715] Re: [Microsoft Corporation Surface Pro 4] hibernate/resume failure
Is resume parameter for kernel and initramfs correctly set? -- 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/1846715 Title: [Microsoft Corporation Surface Pro 4] hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Attempting to get a surface pro 4 to hibernate. Apparently it doesn't work. Swap should be large enough: ed@flate2:~$ free totalusedfree shared buff/cache available Mem: 16321812 140017213582232 709580 1339408 13925688 Swap: 19530748 019530748 ed@flate2:~$ swapon -s Filename TypeSizeUsedPriority /dev/nvme0n1p3partition 19530748 0 -2 ProblemType: KernelOops DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-13-generic 5.3.0-13.14 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 862 F pulseaudio Date: Fri Oct 4 13:20:33 2019 DuplicateSignature: hibernate/resume:Microsoft Corporation Surface Pro 4:108.2706.768 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume InstallationDate: Installed on 2019-10-02 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) InterpreterPath: /usr/bin/python3.7 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 045e:07e8 Microsoft Corp. Surface Type Cover Bus 001 Device 004: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=e597918a-2b2c-4d5c-96eb-a8d7d007350e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 SourcePackage: linux StagingDrivers: ipu3_imgu Title: [Microsoft Corporation Surface Pro 4] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/18/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 108.2706.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849058] Re: eoan/linux-azure: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-eoan ** 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: 1849064 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Thursday, 24. October 2019 11:56 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 25. October 2019 06:20 UTC reason: - prepare-package-signed: Stalled -- package tag not yet published - promote-to-proposed: Pending -- source package tags missing + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849058 Title: eoan/linux-azure: 5.3.0-1005.5 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Friday, 25. October 2019 06:20 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
Correct: for this bug 1835879: $ md5sum intel/ibt-19-32-0.ddc intel/ibt-19-32-0.sfi a575af7c88f4c74841d71dd5fc273a3d intel/ibt-19-32-0.ddc 92f4fbe0c58d4b704ab590f7665b2f9c intel/ibt-19-32-0.sfi -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
And for this bug 1835879: $ md5sum intel/ibt-20-0-3.sfi intel/ibt-20-1-3.sfi intel/ibt-20-1-4.sfi b695c8d34009fcb325a61c8a49ab69cf intel/ibt-20-0-3.sfi b695c8d34009fcb325a61c8a49ab69cf intel/ibt-20-1-3.sfi b695c8d34009fcb325a61c8a49ab69cf intel/ibt-20-1-4.sfi -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827978] Re: [SGX]Flexible Launch Control
** Description changed: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx - Target Kernel: 5.2 - Target Release: 19.10 + Target Kernel: TBD + Target Release: 20.04 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827978 Title: [SGX]Flexible Launch Control Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Implement open source launch enclave and bundle it with the Linux kernel so that the kernel can generate launch tokens for enclaves that the user requests to run. Flexible Launch Control consists of: Enclave singing tool for kbuild (DONE) Launch Enclave and its user space (DONE) Host program for the LE that reads SIGSTRUCT instances from stdin and outputs them to stdout (DONE) Kbuild changes to generate LE signing key (IN PROGRESS) Driver changes to launch lehost using user space helper framework (IN PROGRESS) Kernel changes to link lehost to vmlinux (IN PROGRESS) Relevant URLs: Launch enclave and host program: https://github.com/jsakkine-intel/sgx-le Kernel tree: https://github.com/jsakkine-intel/linux-sgx Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1827978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730885] Re: [Feature] SGX mainline enabling
** Description changed: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 - Target Release: 19.10 + Target Release: 20.04 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730885 Title: [Feature] SGX mainline enabling Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description Umbrella task for SGX mainline kernel features. Target Kernel: 5.4 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842893] Re: Intel Bluetooth AX201, aka HarrisonPeak (HrP), not supported
Verified bionic 1.173.11, disco 1.178.5. Has the same md5sum as I proposed https://code.launchpad.net/~vicamo/ubuntu/+source/linux- firmware/+git/linux-firmware/+ref/bug-1842893/add-firmware-for-intel- bt-19-32-4/bionic, https://code.launchpad.net/~vicamo/ubuntu/+source /linux-firmware/+git/linux-firmware/+ref/bug-1842893/add-firmware-for- intel-bt-19-32-4/disco: $ md5sum intel/ibt-19-32-4.ddc intel/ibt-19-32-4.sfi a575af7c88f4c74841d71dd5fc273a3d intel/ibt-19-32-4.ddc 7753b2a34fa3647c76c116abf3240c22 intel/ibt-19-32-4.sfi -- 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/1842893 Title: Intel Bluetooth AX201, aka HarrisonPeak (HrP), not supported Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Released Bug description: [5.950346] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017 [5.951318] Bluetooth: hci0: Device revision is 2 [5.951319] Bluetooth: hci0: Secure boot is enabled [5.951320] Bluetooth: hci0: OTP lock is enabled [5.951320] Bluetooth: hci0: API lock is enabled [5.951321] Bluetooth: hci0: Debug lock is disabled [5.951322] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.952242] bluetooth hci0: Direct firmware load for intel/ibt-19-32-4.sfi failed with error -2 [5.952244] Bluetooth: hci0: Failed to load Intel firmware file (-2) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X16 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-13 (23 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) Tags: bionic Uname: Linux 5.3.0-050300rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849751] Re: [i915] doesn't boot after 19.10 upgrade
also, the logfile shows you are using nvidia.. that might break something -- 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/1849751 Title: [i915] doesn't boot after 19.10 upgrade Status in linux package in Ubuntu: Incomplete Bug description: after upgrading to ubuntu 19.10, vulkan support when using the intel card in my laptop is broken. running any of my example vulkan apps shows the following error: $ vkcube vkcube: /build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175: demo_init_vk: Assertion `!err' failed. Aborted (core dumped) note that since the update I can no longer boot my system at all without adding "nomodeset" the kernel params, something is broken in the intel modeset driver since 19.04. so this may very well be related. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-vulkan-drivers 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 20:04:54 2019 DistUpgraded: 2019-10-23 18:54:04,373 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.1, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:65a1] NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104BM [GeForce GTX 1070 Mobile] [1558:65a3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. EgisTec_ES603 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=ZFS=rpool/root ro root=ZFS=rpool/root quiet nomodeset SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: PCI And subscribe me. We need to discuss this with PCI/PM folks. -- 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/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Triaged Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
Verified bionic 1.173.11, disco 1.178.5. Has the same md5sum as I proposed https://code.launchpad.net/~vicamo/ubuntu/+source/linux- firmware/+git/linux-firmware/+ref/bug-1842893/add-firmware-for-intel- bt-19-32-4/bionic, https://code.launchpad.net/~vicamo/ubuntu/+source /linux-firmware/+git/linux-firmware/+ref/bug-1842893/add-firmware-for- intel-bt-19-32-4/disco: $ md5sum intel/ibt-19-32-4.ddc intel/ibt-19-32-4.sfi a575af7c88f4c74841d71dd5fc273a3d intel/ibt-19-32-4.ddc 7753b2a34fa3647c76c116abf3240c22 intel/ibt-19-32-4.sfi ** Tags removed: verification-needed-bionic verification-needed-disco ** Tags added: verification-done-bionic verification-done-disco -- 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/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841304] Re: sky2 ethernet card don't work after returning from suspension
Can you please attach dmesg when booting the test kernel? -- 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/1841304 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Linux 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux error similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 however, all kernel patches do not fix this error !! maybe it is related to specific hardware / BIOS version? in my case the Samsung R780 laptop terminal fix helps: sudo modprobe -r sky2; sudo modprobe -i sky2 or an entry in GRUB GRUB_CMDLINE_LINUX_DEFAULT = "quiet splash pci = nomsi, noaer" I think the problem is rather related to the option: pci = nomsi, noaer regards! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kris 1748 F pulseaudio /dev/snd/controlC0: kris 1748 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: SAMSUNG ELECTRONICS CO., LTD. R780/R778 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=89a089ca-faca-4b1e-be43-8cdd057ae525 ro quiet splash pci=nomsi,noaer ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 04JA.M017.20100114.LDG dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: R780/R778 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 04JA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr04JA.M017.20100114.LDG:bd01/14/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR780/R778:pvr04JA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR780/R778:rvr04JA:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: R780/R778 dmi.product.version: 04JA dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835340] Re: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications
** Description changed: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. - Target Release: 19.10 + Target Release: 20.04 Target Kernel: TBD ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. Target Release: 20.04 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849751] Re: vulkan support on intel broken after 19.10 upgrade
using 'nomodeset' disables the intel gpu completely, so vulkan not working is the least of your problems ;) you could try installing newer mainline kernels from kernel.ubuntu.com/~kernel-ppa/mainline/ maybe start from v5.4-rc and if it doesn't work, try drm-tip. Install the amd64 version of unsigned and modules packages ** Package changed: mesa (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Summary changed: - vulkan support on intel broken after 19.10 upgrade + [i915] doesn't boot after 19.10 upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849751 Title: [i915] doesn't boot after 19.10 upgrade Status in linux package in Ubuntu: Incomplete Bug description: after upgrading to ubuntu 19.10, vulkan support when using the intel card in my laptop is broken. running any of my example vulkan apps shows the following error: $ vkcube vkcube: /build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175: demo_init_vk: Assertion `!err' failed. Aborted (core dumped) note that since the update I can no longer boot my system at all without adding "nomodeset" the kernel params, something is broken in the intel modeset driver since 19.04. so this may very well be related. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-vulkan-drivers 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 20:04:54 2019 DistUpgraded: 2019-10-23 18:54:04,373 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.1, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:65a1] NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104BM [GeForce GTX 1070 Mobile] [1558:65a3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. EgisTec_ES603 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=ZFS=rpool/root ro root=ZFS=rpool/root quiet nomodeset SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849751] [NEW] vulkan support on intel broken after 19.10 upgrade
You have been subscribed to a public bug: after upgrading to ubuntu 19.10, vulkan support when using the intel card in my laptop is broken. running any of my example vulkan apps shows the following error: $ vkcube vkcube: /build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175: demo_init_vk: Assertion `!err' failed. Aborted (core dumped) note that since the update I can no longer boot my system at all without adding "nomodeset" the kernel params, something is broken in the intel modeset driver since 19.04. so this may very well be related. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-vulkan-drivers 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 20:04:54 2019 DistUpgraded: 2019-10-23 18:54:04,373 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.1, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:65a1] NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104BM [GeForce GTX 1070 Mobile] [1558:65a3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. EgisTec_ES603 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=ZFS=rpool/root ro root=ZFS=rpool/root quiet nomodeset SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Incomplete ** Tags: amd64 apport-bug eoan ubuntu -- vulkan support on intel broken after 19.10 upgrade https://bugs.launchpad.net/bugs/1849751 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836491] Re: Complete lock-up
Does the kernel 4.15.0-67.76 have this issue? -- 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/1836491 Title: Complete lock-up Status in linux package in Ubuntu: Confirmed Bug description: This kernel has caused my video system to completely freeze. A hard restart is required to recover, but it happens each time. I have reverted to prior kernel. --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: lmcor 2748 F...m pulseaudio /dev/snd/controlC1: lmcor 2748 F pulseaudio /dev/snd/controlC0: lmcor 2748 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=bf754a96-f70b-4964-bdbb-b7ab12e42018 InstallationDate: Installed on 2018-09-30 (287 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171127 MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic root=UUID=7663b459-8677-4afe-85fb-12424af45024 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-52.56~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-52-generic N/A linux-backports-modules-4.15.0-52-generic N/A linux-firmware 1.157.21 Tags: sylvia Uname: Linux 4.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3803 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)
** Description changed: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.4/Qemu-3.10 - Target Release: 19.10 + Target Release: 20.04 ** Tags removed: intel-virt-19.10 ** Tags added: intel-virt-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Fix Released Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.4/Qemu-3.10 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741394] Re: [Feature] Crystal Ridge - get DAX working with XFS realtime devices
** Description changed: Description Thus far we haven't had a compelling reason to spend our time making sure DAX is working properly with XFS realtime devices, but according to some comments on IRC, Darrick Wong is trying it and it isn't working: now i run into the problem that if the data device doesn't support dax then we refuse to enable it on the rt device ...also, if the datadev supports it but the rtdev does not, creating a dax rt file blow sup "pwrite: Operation not supported" mmap write just Bus errors • djwong discovers __bdev_dax_supported(), wonders why it takes a struct super_block * and not a struct block_device * i guess the answer is that xfs_fs_fill_super should only disable dax if none of the devices support it, and we should only set S_DAX if blk_queue_dax(whichever device the file is on) Fix this and get DAX + realtime devices working. Target Kernel: TBD - Target Release: 19.10 + Target Release: 20.04 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741394 Title: [Feature] Crystal Ridge - get DAX working with XFS realtime devices Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description Thus far we haven't had a compelling reason to spend our time making sure DAX is working properly with XFS realtime devices, but according to some comments on IRC, Darrick Wong is trying it and it isn't working: now i run into the problem that if the data device doesn't support dax then we refuse to enable it on the rt device ...also, if the datadev supports it but the rtdev does not, creating a dax rt file blow sup "pwrite: Operation not supported" mmap write just Bus errors • djwong discovers __bdev_dax_supported(), wonders why it takes a struct super_block * and not a struct block_device * i guess the answer is that xfs_fs_fill_super should only disable dax if none of the devices support it, and we should only set S_DAX if blk_queue_dax(whichever device the file is on) Fix this and get DAX + realtime devices working. Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1741394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704437] Re: [Bug] Crystal Ridge - libnvdimm: debug create-namespace sysfs collision report from Jeff
** Description changed: Description If you run ndctl create-namespace simultaneously on every cpu on a 72 cpu system, for exactly the same namespace, things break. Shocking, I know. I've attached the script and the panic. Not high priority, I don't think. I tried to attach the shell script, but your email server rejected it. So, it's inline below. Search for thrash-ns.sh. Cheers, Jeff [ 71.912227] ---[ cut here ]--- [ 71.935600] WARNING: CPU: 39 PID: 1039 at fs/sysfs/group.c:237 sysfs_remove_group+0x8e/0x90 [ 71.978797] sysfs group 'power' not found for kobject 'btt0.1' [ 72.004940] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter intel_rapl sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul vfat ghash_clmulni_intel fat pcbc aesni_intel nd_pmem crypto_simd ipmi_si glue_helper dax_pmem iTCO_wdt nd_btt iTCO_vendor_support dax cryptd ipmi_devintf hpwdt lpc_ich hpilo pcspkr i2c_i801 ioatdma sg ipmi_msghandler mfd_core wmi shpchp dca nfit acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs sr_mod cdrom sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea [ 72.326921] sysfillrect sysimgblt fb_sys_fops ttm bnx2x mdio ahci tg3 drm hpsa libahci ptp nvme libata pps_core i2c_core libcrc32c crc32c_intel scsi_transport_sas nvme_core dm_mirror dm_region_hash dm_log dm_mod [ 72.411729] CPU: 39 PID: 1039 Comm: kworker/u145:2 Not tainted 4.11.0-rc1+ #25 [ 72.444221] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/05/2016 [ 72.486852] Workqueue: events_unbound async_run_entry_fn [ 72.512078] Call Trace: [ 72.523223] dump_stack+0x63/0x87 [ 72.538230] __warn+0xd1/0xf0 [ 72.551520] warn_slowpath_fmt+0x5f/0x80 [ 72.569169] ? kernfs_find_and_get_ns+0x48/0x60 [ 72.589568] sysfs_remove_group+0x8e/0x90 [ 72.607495] dpm_sysfs_remove+0x57/0x60 [ 72.624715] device_del+0x111/0x350 [ 72.640292] ? pick_next_task_fair+0x122/0x540 [ 72.660482] device_unregister+0x1a/0x60 [ 72.678191] nd_async_device_unregister+0x22/0x30 [ 72.699306] async_run_entry_fn+0x39/0x170 [ 72.717642] process_one_work+0x165/0x410 [ 72.735566] worker_thread+0x137/0x4c0 [ 72.752370] kthread+0x101/0x140 [ 72.766449] ? rescuer_thread+0x3b0/0x3b0 [ 72.784357] ? kthread_park+0x90/0x90 [ 72.800810] ret_from_fork+0x2c/0x40 [ 72.816960] --[ end trace cb734114d5364186 ]-- [ 72.837661] BUG: unable to handle kernel NULL pointer dereference at 0020 [ 72.872912] IP: klist_put+0x1b/0x90 [ 72.31] PGD 0 [ 72.31] [ 72.904390] Oops: 1 SMP [ 72.918698] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter intel_rapl sb_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul vfat ghash_clmulni_intel fat pcbc aesni_intel nd_pmem crypto_simd ipmi_si glue_helper dax_pmem iTCO_wdt nd_btt iTCO_vendor_support dax cryptd ipmi_devintf hpwdt lpc_ich hpilo pcspkr i2c_i801 ioatdma sg ipmi_msghandler mfd_core wmi shpchp dca nfit acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs sr_mod cdrom sd_mod mgag200 i2c_algo_bit drm_kms_helper syscopyarea [ 73.245742] sysfillrect sysimgblt fb_sys_fops ttm bnx2x mdio ahci tg3 drm hpsa libahci ptp nvme libata pps_core i2c_core libcrc32c crc32c_intel scsi_transport_sas nvme_core dm_mirror dm_region_hash dm_log dm_mod [ 73.331485] CPU: 39 PID: 1039 Comm: kworker/u145:2 Tainted: G W 4.11.0-rc1+ #25 [ 73.370525] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 10/05/2016 [ 73.408108] Workqueue: events_unbound async_run_entry_fn [ 73.432199] task: 88046523 task.stack: c900061f4000 [ 73.458817] RIP: 0010:klist_put+0x1b/0x90 [ 73.479280] RSP: 0018:c900061f7d68 EFLAGS: 00010246 [ 73.507441] RAX: 88017ccd4b40 RBX: RCX: [ 73.539498] RDX: RSI: 0001 RDI: [ 73.571576] RBP: c900061f7d88 R08: fffe R09: 00047417 [ 73.603526] R10: 0005 R11: 00047416 R12: 88017ccd4b68 [ 73.635479] R13: 88017d558800 R14: 0001 R15: 880469cf44b0 [ 73.667484] FS: () GS:88046f94000
[Kernel-packages] [Bug 1734081] Re: [Feature] Crystal Ridge: Add a "memory registration with lease" semantic to V4L2
** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 ** Description changed: Description The Video for Linux v2 API suffers from the same problem as RDMA vs DAX, i.e. it wants to established long lived memory registrations. Add a semantic that allows the kernel to revoke access to the registration so that the elevated page counts are time bounded. - Target Kernel: 5.2 - Target Release: 19.10 + Target Kernel: TBD + Target Release: 20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734081 Title: [Feature] Crystal Ridge: Add a "memory registration with lease" semantic to V4L2 Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description The Video for Linux v2 API suffers from the same problem as RDMA vs DAX, i.e. it wants to established long lived memory registrations. Add a semantic that allows the kernel to revoke access to the registration so that the elevated page counts are time bounded. Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1734081/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842681] Re: ACPI Errors with 8-socket DCPMM system
** Description changed: Description A customer reporting ACPI errors during Linux boot in an 8 socket glueless system with 6 DCPMM modules installed per socket. After OS has completed initialization, any attempt to use NDCTL or IPMCTL results in a process or system hang. The system boots and the apps are ok when reducing the system configuration to 6 sockets. Log extract is below. A web search turned up what looks like the same problem. See https://lkml.org/lkml/2019/5/30/1290. This link describes a kernel change to increase the dimensions of the failing table. Your names appears in the signed-off of this link Can you confirm if it is the same problem described below (it looks like it is) and if the proposed kernel change describe in the link is the correction? - Customer has checked kernel.org and the latest versions of the affected files do not have kernel change. + Customer has checked kernel.org and the latest versions of the affected files do not have kernel change. They are validating RedHat and Suse Enterprise for 8+ socket system with maximum DCPMMs installed. Are there other items that must be updated to go along with the kernel change? These messages are extracted from the start-up log showing the OS and Kernel versions plus the ACPI errors. Welcome to SUSE Linux Enterprise Server 12 SP4 (x86_64) - Kernel 4.12.14-94.41-default (ttyS0). ACPI Error: Could not allocate new OwnerId (255 max), AE_OWNER_ID_LIMIT (20170303/utownerid-149) Merged for v5.4: 67a72420a326 ACPICA: Increase total number of possible Owner IDs - Target Release: 19.10 + Target Release: 20.04 Target Kernel: 5.4 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 ** Changed in: intel Status: Fix Released => 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/1842681 Title: ACPI Errors with 8-socket DCPMM system Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description A customer reporting ACPI errors during Linux boot in an 8 socket glueless system with 6 DCPMM modules installed per socket. After OS has completed initialization, any attempt to use NDCTL or IPMCTL results in a process or system hang. The system boots and the apps are ok when reducing the system configuration to 6 sockets. Log extract is below. A web search turned up what looks like the same problem. See https://lkml.org/lkml/2019/5/30/1290. This link describes a kernel change to increase the dimensions of the failing table. Your names appears in the signed-off of this link Can you confirm if it is the same problem described below (it looks like it is) and if the proposed kernel change describe in the link is the correction? Customer has checked kernel.org and the latest versions of the affected files do not have kernel change. They are validating RedHat and Suse Enterprise for 8+ socket system with maximum DCPMMs installed. Are there other items that must be updated to go along with the kernel change? These messages are extracted from the start-up log showing the OS and Kernel versions plus the ACPI errors. Welcome to SUSE Linux Enterprise Server 12 SP4 (x86_64) - Kernel 4.12.14-94.41-default (ttyS0). ACPI Error: Could not allocate new OwnerId (255 max), AE_OWNER_ID_LIMIT (20170303/utownerid-149) Merged for v5.4: 67a72420a326 ACPICA: Increase total number of possible Owner IDs Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744634] Re: [Bug]Crystal Ridge: fix badblocks routines not merging more than one range at a time
** Description changed: Description: The badblocks routines we used from md have a bug where if a new range being added overlaps with multiple distinct ranges, it only merges with the first one. Consider the following operations: badblocks_set(bb, 32, 1); badblocks_set(bb, 34, 1); badblocks_set(bb, 36, 1); badblocks_show will now correctly report: 32 1 34 1 36 1 Now if I do: badblocks_set(bb, 32, 12); Ideally, this should collapse all ranges into a single (32, 12).. But looks like badblocks_set only merges one set of adjacent mergeable ranges, and then returns, resulting in: 32 3 36 1 Now if I add the same (32, 12) range again, I get: 32 5 as one more set is merged. And finally after adding (32, 12) one final time, I get the expected 32 12. Target Kernel:TBD - Target Release:19.10 + Target Release:20.04 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744634 Title: [Bug]Crystal Ridge: fix badblocks routines not merging more than one range at a time Status in intel: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Description: The badblocks routines we used from md have a bug where if a new range being added overlaps with multiple distinct ranges, it only merges with the first one. Consider the following operations: badblocks_set(bb, 32, 1); badblocks_set(bb, 34, 1); badblocks_set(bb, 36, 1); badblocks_show will now correctly report: 32 1 34 1 36 1 Now if I do: badblocks_set(bb, 32, 12); Ideally, this should collapse all ranges into a single (32, 12).. But looks like badblocks_set only merges one set of adjacent mergeable ranges, and then returns, resulting in: 32 3 36 1 Now if I add the same (32, 12) range again, I get: 32 5 as one more set is merged. And finally after adding (32, 12) one final time, I get the expected 32 12. Target Kernel:TBD Target Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1744634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849178] Re: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients
Hi wdoekes, thanks for the research, that patch indeed does not exist in 4.15.0-66, it's now in 4.15.0-67 Benjamin, can you please give the Bionic kernel in -proposed a try (4.15.0-67), it contains these potential fixs mentioned by wdoekes: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-next&id=30b79decb8a3a9e5a003669bfe7dea05cd807a53 https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-next&id=198f548fbb7956cb46b687a4b8a70171652efb99 Thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-hwe (Ubuntu) ** No longer affects: linux-hwe (Ubuntu Bionic) ** Changed in: linux (Ubuntu Bionic) 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/1849178 Title: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: This is occurring with both 18.04, and 16.04 w/ HWE. After upgrading the linux kernel image to 4.15.0-66, logging in with a user that has a cephfs home directory hangs. Dmesg reports the following: [ 221.239709] general protection fault: [#1] SMP PTI [ 221.239712] Modules linked in: ceph libceph libcrc32c fscache vboxsf(OE) snd_intel8x0 snd_ac97_codec crct10dif_pclmul crc32_pclmul ac97_bus ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event snd_rawmidi aesni_intel aes_x86_64 vboxvideo(OE) joydev snd_seq snd_seq_device snd_timer crypto_simd ttm glue_helper snd drm_kms_helper input_leds cryptd intel_rapl_perf soundcore serio_raw vboxguest(OE) drm fb_sys_fops syscopyarea sysfillrect sysimgblt video mac_hid sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid ahci psmouse libahci i2c_piix4 e1000 pata_acpi [ 221.239746] CPU: 1 PID: 1795 Comm: kworker/1:4 Tainted: GW OE 4.15.0-66-generic #75-Ubuntu [ 221.239748] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 221.239759] Workqueue: ceph-msgr ceph_con_workfn [libceph] [ 221.239767] RIP: 0010:kmem_cache_alloc+0x81/0x1b0 [ 221.239769] RSP: 0018:b208812d7ae0 EFLAGS: 00010202 [ 221.239770] RAX: 0efb8a01a897ba8a RBX: 0efb8a01a897bfea RCX: 001a [ 221.239772] RDX: 0019 RSI: 01400040 RDI: 4929e00040d0 [ 221.239773] RBP: b208812d7b10 R08: d2087fd040d0 R09: 88de94ad6640 [ 221.239774] R10: R11: e3f68484 R12: 01400040 [ 221.239775] R13: 88de962eb800 R14: 0efb8a01a897ba8a R15: 88de962eb800 [ 221.239777] FS: () GS:88de9fd0() knlGS: [ 221.239778] CS: 0010 DS: ES: CR0: 80050033 [ 221.239779] CR2: 5604162106a8 CR3: c5e0a004 CR4: 000606e0 [ 221.239782] DR0: DR1: DR2: [ 221.239783] DR3: DR6: fffe0ff0 DR7: 0400 [ 221.239784] Call Trace: [ 221.239792] ? ceph_alloc_inode+0x1d/0x3b0 [ceph] [ 221.239798] ceph_alloc_inode+0x1d/0x3b0 [ceph] [ 221.239801] alloc_inode+0x20/0x90 [ 221.239804] iget5_locked+0xea/0x1f0 [ 221.239809] ? ceph_d_init+0x45/0x60 [ceph] [ 221.239813] ? ceph_ino_compare+0x30/0x30 [ceph] [ 221.239817] ? ceph_mount+0x8a0/0x8a0 [ceph] [ 221.239822] ceph_get_inode+0x36/0xc0 [ceph] [ 221.239827] ceph_readdir_prepopulate+0x4e9/0xcb0 [ceph] [ 221.239834] handle_reply+0x954/0xcc0 [ceph] [ 221.239841] dispatch+0xcf/0xb40 [ceph] [ 221.239843] ? __switch_to_asm+0x35/0x70 [ 221.239845] ? __switch_to_asm+0x41/0x70 [ 221.239847] ? __switch_to_asm+0x35/0x70 [ 221.239848] ? __switch_to_asm+0x41/0x70 [ 221.239850] ? __switch_to_asm+0x35/0x70 [ 221.239856] try_read+0x64a/0x11a0 [libceph] [ 221.239858] ? __switch_to_asm+0x41/0x70 [ 221.239860] ? __switch_to_asm+0x35/0x70 [ 221.239861] ? __switch_to_asm+0x41/0x70 [ 221.239863] ? __switch_to_asm+0x35/0x70 [ 221.239864] ? __switch_to_asm+0x41/0x70 [ 221.239866] ? __switch_to_asm+0x35/0x70 [ 221.239871] ceph_con_workfn+0xda/0x610 [libceph] [ 221.239874] process_one_work+0x1de/0x420 [ 221.239876] worker_thread+0x32/0x410 [ 221.239878] kthread+0x121/0x140 [ 221.239880] ? process_one_work+0x420/0x420 [ 221.239881] ? kthread_create_worker_on_cpu+0x70/0x70 [ 221.239883] ret_from_fork+0x35/0x40 [ 221.239885] Code: f4 5b 74 49 83 78 10 00 4d 8b 30 0f 84 00 01 00 00 4d 85 f6 0f 84 f7 00 00 00 49 63 5f 20 49 8b 3f 48 8
[Kernel-packages] [Bug 1837547] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup blackscreen - Hardreset needed
Does this issue still happen if all packages are updated? -- 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/1837547 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup blackscreen - Hardreset needed Status in linux package in Ubuntu: Confirmed Bug description: Sometimes I boot the ThinkPad T460p, put it into sleep, wake it up and only receive a blackscreen until I hardreset the laptop with the power button, last time all happen without AC power I recognize now. I don't know if it was coincidence. $ uname -a Linux deus-ex-machina 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 18.04 / Linux Mint 19.1 In the journalctl I recognize DRM errors. I put it in sleep 11:xx o'clock and woke it up 14:xx o'lock. Then I got these DRM errors and did need to hardreset it. (Documented as REBOOT in the log). I assume that my 3 bug reports (this, docking station, user session crash) are related to the nvidia driver in combination with the ubuntu kernel? Or just coincidence. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (367 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 005: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 001 Device 004: ID 04f2:b541 Chicony Electronics Co., Ltd Bus 001 Device 002: 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) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 mitigations=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: tessa Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET89W (2.29 ) 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:bvrR07ET89W(2.29):bd04/30/2019: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/1837547/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840708 Title: HP Envy with AMD Ryzen 5 2500U processor hangs on boot Status in linux package in Ubuntu: Expired Bug description: Ubuntu 18.04.3, kernel 5.0.0-25-generic When grub menu disappears, the screen remains blank. I include a syslog file from a failed boot. The important part is at line 1175: irq 7: nobody cared (try booting with the "irqpoll" option) This laptop boots correctly with the 4.18 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834410] Re: iTCO watchdog No Reboot bit needs to move from side band to a TCOBASE register bit
** Description changed: Description: CDF has the WDT No Reboot bit as bit one of P2SB.SBREG_BAR64 +CFh + Ch which is cannot be read from the OS. This issue manifest itself in Linux by a -EBUSY error when loading the iTCO_wdt driver. [ 23.060317] intel_rapl: Found RAPL domain package [ 23.068017] intel_rapl: RAPL package 0 domain package locked by BIOS [ 23.080641] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 23.203352] iTCO_vendor_support: vendor-support=0 [ 23.220844] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 23.221060] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5] [ 23.221072] iTCO_wdt: probe of iTCO_wdt failed with error -16 [ 23.224465] Adding 4194300k swap on /dev/mapper/rhel-swap. Priority:-2 extents:1 across:4194300k SSFS [ 24.614448] XFS (dm-2): Mounting V5 Filesystem [ 24.632588] XFS (dm-2): Starting recovery (logdev: internal) [ 24.642160] XFS (dm-2): Ending recovery (logdev: internal) [ 24.754306] RPC: Registered named UNIX socket transport module. [ 24.760402] RPC: Registered udp transport module. - - In systems that have a WDAT table, this is not an issue as such table contains the watchdog information. However, Jacobsville will not have a WDAT table. Therefore, when creating the iTCO_wdt platform device (in drivers/i2c/busses/i2c-i801.c), we need to take care of the updated location. - + + In systems that have a WDAT table, this is not an issue as such table + contains the watchdog information. However, Jacobsville will not have a + WDAT table. Therefore, when creating the iTCO_wdt platform device (in + drivers/i2c/busses/i2c-i801.c), we need to take care of the updated + location. + Please see attached document. This update will be available in Cedar Fork B0. - - This issue is being tracked in the HSD https://hsdes.intel.com/appstore/article/#/2007770607. + This issue is being tracked in the HSD + https://hsdes.intel.com/appstore/article/#/2007770607. - Target Kernel: TBD - Target Release: 19.10 + Target Kernel:5.4 + Target Release: 20.04 ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834410 Title: iTCO watchdog No Reboot bit needs to move from side band to a TCOBASE register bit Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: CDF has the WDT No Reboot bit as bit one of P2SB.SBREG_BAR64 +CFh + Ch which is cannot be read from the OS. This issue manifest itself in Linux by a -EBUSY error when loading the iTCO_wdt driver. [ 23.060317] intel_rapl: Found RAPL domain package [ 23.068017] intel_rapl: RAPL package 0 domain package locked by BIOS [ 23.080641] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 23.203352] iTCO_vendor_support: vendor-support=0 [ 23.220844] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 23.221060] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5] [ 23.221072] iTCO_wdt: probe of iTCO_wdt failed with error -16 [ 23.224465] Adding 4194300k swap on /dev/mapper/rhel-swap. Priority:-2 extents:1 across:4194300k SSFS [ 24.614448] XFS (dm-2): Mounting V5 Filesystem [ 24.632588] XFS (dm-2): Starting recovery (logdev: internal) [ 24.642160] XFS (dm-2): Ending recovery (logdev: internal) [ 24.754306] RPC: Registered named UNIX socket transport module. [ 24.760402] RPC: Registered udp transport module. In systems that have a WDAT table, this is not an issue as such table contains the watchdog information. However, Jacobsville will not have a WDAT table. Therefore, when creating the iTCO_wdt platform device (in drivers/i2c/busses/i2c-i801.c), we need to take care of the updated location. Please see attached document. This update will be available in Cedar Fork B0. This issue is being tracked in the HSD https://hsdes.intel.com/appstore/article/#/2007770607. Target Kernel:5.4 Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-eoan ** 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: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Thursday, 24. October 2019 23:36 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 25. October 2019 03:55 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Friday, 25. October 2019 03:55 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829689] Re: [AEP]Sub-section memory hotplug support, fix namepsace padding
326e1b8f83a4 46d945aeab4d 49ba3c6b37b3 7cc7867fb061 7e3e888dfc13
7ea6216049ff 96da4359 9a845030427c a0653406a3a6 a3619190d62e
ba72b4c8cf60 e9c0a3f05477 f1eca35a0dc7 f46edbd1b151
v5.3
** Changed in: intel
Status: New => 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/1829689
Title:
[AEP]Sub-section memory hotplug support, fix namepsace padding
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Bug description:
The memory hotplug section is an arbitrary / convenient unit for memory
hotplug. 'Section-size' units have bled into the user interface
('memblock' sysfs) and can not be changed without breaking existing
userspace. The section-size constraint, while mostly benign for typical
memory hotplug, has and continues to wreak havoc with 'device-memory'
use cases, persistent memory (pmem) in particular. Recall that pmem uses
devm_memremap_pages(), and subsequently arch_add_memory(), to allocate a
'struct page' memmap for pmem. However, it does not use the 'bottom
half' of memory hotplug, i.e. never marks pmem pages online and never
exposes the userspace memblock interface for pmem. This leaves an
opening to redress the section-size constraint.
To date, the libnvdimm subsystem has attempted to inject padding to
satisfy the internal constraints of arch_add_memory(). Beyond
complicating the code, leading to bugs [2], wasting memory, and limiting
configuration flexibility, the padding hack is broken when the platform
changes this physical memory alignment of pmem from one boot to the
next. Device failure (intermittent or permanent) and physical
reconfiguration are events that can cause the platform firmware to
change the physical placement of pmem on a subsequent boot, and device
failure is an everyday event in a data-center.
It turns out that sections are only a hard requirement of the
user-facing interface for memory hotplug and with a bit more
infrastructure sub-section arch_add_memory() support can be added for
kernel internal usages like devm_memremap_pages(). Here is an analysis
of the current design assumptions in the current code and how they are
addressed in the new implementation:
Current design assumptions:
Sections that describe boot memory (early sections) are never
unplugged / removed.
pfn_valid(), in the CONFIG_SPARSEMEM_VMEMMAP=y, case devolves to a
valid_section() check
__add_pages() and helper routines assume all operations occur in
PAGES_PER_SECTION units.
The memblock sysfs interface only comprehends full sections
New design assumptions:
Sections are instrumented with a sub-section bitmask to track (on x86)
individual 2MB sub-divisions of a 128MB section.
Partially populated early sections can be extended with additional
sub-sections, and those sub-sections can be removed with
arch_remove_memory(). With this in place we no longer lose usable memory
capacity to padding.
pfn_valid() is updated to look deeper than valid_section() to also check the
active-sub-section mask. This indication is in the same cacheline as
the valid_section() so the performance impact is expected to be
negligible. So far the lkp robot has not reported any regressions.
Outside of the core vmemmap population routines which are replaced,
other helper routines like shrink_{zone,pgdat}_span() are updated to
handle the smaller granularity. Core memory hotplug routines that deal
with online memory are not touched.
The existing memblock sysfs user api guarantees / assumptions are
not touched since this capability is limited to !online
!memblock-sysfs-accessible sections.
Meanwhile the issue reports continue to roll in from users that do not
understand when and how the 128MB constraint will bite them. The current
implementation relied on being able to support at least one misaligned
namespace, but that immediately falls over on any moderately complex
namespace creation attempt. Beyond the initial problem of 'System RAM'
colliding with pmem, and the unsolvable problem of physical alignment
changes, Linux is now being exposed to platforms that collide pmem
ranges with other pmem ranges by default [3]. In short,
devm_memremap_pages() has pushed the venerable section-size constraint
past the breaking point, and the simplicity of section-aligned
arch_add_memory() is no longer tenable.
Target Kernel: 5.3
Target Release: 19.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1829689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843774] Re: [CML] New device IDs for CML-U
** Changed in: intel Status: New => Fix Released -- 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/1843774 Title: [CML] New device IDs for CML-U Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: Description This task is to identify what new device IDs are required for CML. CML PCH-LP: CML-U CML PCH-V: ControllerKernel Version Commit Approved to be published Comments SMBus 0x02a3 v5.1-rc35cd1c56c42be SPI 0x02aa 0x02ab 0x02fbv5.2dd6629073a97 41a918026407 GPIO INT34BB It seems the same as for CNL. Does it have same IDs? According to dump from Wendy the ID is INT34BB which is CNL-LP. Nothing needs to be done here. Chap03_CMP-H_Pins_Chap18_GPIO_Automation_v3 1.0.xlsx is in use UFS Is there a CML design with UFS this has been only POR for IoTG? AHCI Not Needed supported by Class ID. XHCI Not needed supported by Class ID. eMMC 0x02c4 v5.2-rc1765c59675ab5 SD Card 0x02f5 v5.2-rc1765c59675ab5 is in oem (4.15) and up: NPK 0x02a6 v5.2e60e9a4b231a I²C 0x02c5 0x02c6 0x02e8 0x02e9 0x02ea 0x02eb v5.2 dd6629073a97https://lkml.org/lkml/2019/4/9/548 HS-UART 0x02a8 0x02a9 0x02c7v5.2dd6629073a97 https://lkml.org/lkml/2019/4/9/548 not in oem (4.15) or oem-osp1 (5.0): SPI Flash Controller 0x02a4 v5.2e43f53c22a93 Target Kernel: 5.2 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1843774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 @Scott, About the bluetooth, this is a comment from Dave Jones: And one thing which isn't a bug: Bluetooth: we don't support bluetooth out of the box. Ubuntu on Pi is primarily a server distro and thus a stable serial console was prioritized over out-of-the-box Bluetooth support (note: I don't work on Ubuntu MATE; that's something separate). Bluetooth can be enabled by installing the "pi-bluetooth" package and switching a line in "syscfg.txt" on the boot partition from "include nobtcfg.txt" to "include "btcfg.txt". A tool to manage the hardware configuration on the Pi (including Bluetooth) is being developed, but I didn't have time to finish it for Eoan. -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847063] Re: Fix non-working Realtek USB ethernet after system resume
** Tags removed: verification-needed-disco verification-needed-eoan ** Tags added: verification-done-disco verification-done-eoan -- 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/1847063 Title: Fix non-working Realtek USB ethernet after system resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] If mac passthrough is enbled, Realtek USB ethernet (r8152) doesn't work under the following steps: 1. Connect to a Dell dock 2. Suspend the system 3. Re-plug the dock 4. Resume the system 5. Ethernet stops working [Fix] The USB port lose its power when the dock gets replugged, so we need to re-write the MAC address at reset_resume callback. [Test] The fix is succesfully tested on Dell WD15 dock and TB16 dock. [Regression Potential] Low. The fix limits to one single device and only take affect when MAC passthrough is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741381] Re: [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info
** Changed in: intel Status: Triaged => 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/1741381 Title: [Feature] Crystal Ridge - dynamic filesystem DAX based on HMAT info Status in intel: Invalid Status in linux package in Ubuntu: Incomplete Bug description: Description: Have the kernel automatically choose whether or not to use filesystem DAX based on information in the HMAT. This depends on the outcome of the "mount option and inode flag" discussion in the community. Target Release: 19.10 Target Kernel:TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1741381/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843775] Re: [CML-U] Comet lake platform need ISH driver support
** Changed in: intel Status: Fix Committed => Fix Released -- 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/1843775 Title: [CML-U] Comet lake platform need ISH driver support Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Enable Integrated Sensor Hub (ISH) driver for Comet lake platform CML-U ISH device_ID is: 02fc a50e8e2ecc1428df28c748c6af6255eb65faf9f3 Target Release: 19.10 Target Kernel: 5.1 [Test case] Boot the kernel on a CML machine and check that the ISH driver is used. [Regression potential] none, it just adds a device id for ISH To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1843775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834408] Re: Support set_mce_nospec() for kernel encountered poison.
** Description changed: Description: The memory_failure() path for userspace consumed poison takes preventative measures that are skipped by kernelspace consume poison, like set_mce_nospec. - Target Kernel: 5.2 - Target ReleasE: 19.10 + Target Kernel: 5.5 + Target ReleasE: 20.04 ** Tags removed: intel-19.10-kernel ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834408 Title: Support set_mce_nospec() for kernel encountered poison. Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: The memory_failure() path for userspace consumed poison takes preventative measures that are skipped by kernelspace consume poison, like set_mce_nospec. Target Kernel: 5.5 Target ReleasE: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834407] Re: ndctl/namespace: Suppress errors on seed devices (check-namespace)
** Description changed: Description: Similar to recent changes made to make "destroy-namespace all" ignore errors on seed devices, do the same for "check-namespace all" - Target Kernel: 5.2 - Target ReleasE: 19.10 + Target Kernel: TBD + Target ReleasE: 20.04 ** Tags removed: intel-19.10-kernel ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834407 Title: ndctl/namespace: Suppress errors on seed devices (check-namespace) Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Similar to recent changes made to make "destroy-namespace all" ignore errors on seed devices, do the same for "check-namespace all" Target Kernel: TBD Target ReleasE: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835175] Re: ICX: PCIe Non-Transparent Bridge
** Description changed: Description: Adding driver support for Intel PCIe Non-Transparent bridge for ICX platform. NTB is a point to point platform interconnect over PCIe. - Target Release: 19.10 + Target Release: 20.04 Target Kernel: TBD ** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835175 Title: ICX: PCIe Non-Transparent Bridge Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Adding driver support for Intel PCIe Non-Transparent bridge for ICX platform. NTB is a point to point platform interconnect over PCIe. Target Release: 20.04 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849026] Re: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849026 Title: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834419] Re: mcelog support for Idaville
** Tags removed: intel-kernel-19.10 ** Tags added: intel-kernel-20.04 ** Description changed: Description: Add any new machine check bank "MSCOD" values for ICX -D that mcelog can use to provide a more detailed error report. Also add support for ICX -D cpuid model numbers. Target Kerne:TBD - Target Release: 5.3 + Target Release:TBD ** Description changed: Description: Add any new machine check bank "MSCOD" values for ICX -D that mcelog can use to provide a more detailed error report. Also add support for ICX -D cpuid model numbers. Target Kerne:TBD - Target Release:TBD + Target Release:20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834419 Title: mcelog support for Idaville Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Add any new machine check bank "MSCOD" values for ICX -D that mcelog can use to provide a more detailed error report. Also add support for ICX -D cpuid model numbers. Target Kerne:TBD Target Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849540] Re: "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" causing boot delays
** 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/1849540 Title: "PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)" causing boot delays Status in linux package in Ubuntu: Incomplete Bug description: ubuntu shows pci bus error severity=corrected when shutting down takes time for login page to pop up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 13:32:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13d1] InstallationDate: Installed on 2019-10-09 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 003: ID 13d3:5a11 IMC Networks Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash i915.alpha_support=1 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UAR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 14_ASUS Laptop X441UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834588] Re: ICX: Add PMU support for adaptive and enhanced PEBS
** Changed in: intel Status: New => 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/1834588 Title: ICX: Add PMU support for adaptive and enhanced PEBS Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: Description: Add support for new ICX PMU features: Adaptive PEBS, and Enhanced PEBS. Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL
I mis-input the comment for LP#1834588. It is about PEBs. Intel_idle in ICL is not finished. -- 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/1834558 Title: intel_idle enable in ICL Status in intel: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Bug description: Description: Support for intel_idle on Ice Lake (client) Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL
Information from upstream: The CPU architects are performing some experiments to root cause the issue we found with high latency times for ICL. Until then ICL will just use cpu_idle. So, the feature is not finished. Keep tune. Sorry for confusion. -- 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/1834558 Title: intel_idle enable in ICL Status in intel: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Bug description: Description: Support for intel_idle on Ice Lake (client) Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL
I am checking the status with upstream. ** Tags removed: intel-kernel-20.04 ** Tags added: intel-kernel-19.10 ** Changed in: intel Status: Fix Released => 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/1834558 Title: intel_idle enable in ICL Status in intel: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Bug description: Description: Support for intel_idle on Ice Lake (client) Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14: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 + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 24. October 2019 14: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: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 @Ricardo, just download the deb (https://people.canonical.com/~hwang4/rpiv2/arm64/) to your pi's rootfs Then run: sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb sudo reboot -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 @Scott, We haven't tested the bluetooth both under old kernel and under patched kernel, do you know how to verify the bluetooth on the pi? And we are going to look at bluetooth after fixing the usb host issue. -- 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/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Pi 4 new install. System boots up but USB bus is not working. Tried 3 keyboards no key presses detected, 2 usb memory drives don't show up in lsblk. output of $lspci 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 10) 01:00.0 USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) output of $dmesg on pastebin here http://pastebin.com/h7A3n9xa or attached to this bug report. Not the only one experiencing bug. Another user created a post on the ubuntu forums: https://ubuntuforums.org/showthread.php?t=2429396&s=01a0c4b0cb4c05e605cbf9d41f660e08&p=13898142#post13898142 64bit raspberry pi 4&4 image pulled from https://ubuntu.com/download/iot/raspberry-pi page. Specifically http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849484] Re: Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
Are you using some kind of adaptor between HDMI and DisplayPort? I wonder if this monitor needs proper DisplayPort for multi-stream. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] + [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849484] Re: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only]
Hmm, it shouldn't be a multi-stream problem. It looks like you only need HDMI v1.3 to drive that resolution and your laptop supports HDMI 1.4b already. So mainly I suspect a bad HDMI cable, bad HDMI adaptor, or just faulty EDID data coming from the monitor. -- 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/1849484 Title: [X1 Carbon 7, i915, HDMI] Ultra-wide monitor recognized properly when plugged in only intermittently [Xorg only] Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849623] Re: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea)
** Description changed: + [Impact] + https://bugs.launchpad.net/bugs/1848790 + https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703 + Recently we had 2 bugs about the usb host on rpi4 with 4G ram, and I found + the kernel in the github already had the fix for this issue, and besides this + fix, it also had 106 more patches than our eoan kernel, those patches were + merged during or after we prepared our eoan kernel, now let us pick those + patches to our eoan too. + + [Fix] + For the usb host issue, it adds a fix by setting the usb dma bounce buffer + under 1G. + + [Test Case] + some users and I alreaady tested the armhf and arm64 kernel on pi4 and pi3 + boards, the usb host worked well and no other regressions introduced. + + [Regression Risk] + Low, these patches are from the github which is the pi official kernel + repository. And we already tested armhf and arm64 kernel on pi4/3 boards. + + + The rpi kernel of https://github.com/raspberrypi/linux.git has been updated, for the branch of rpi-5.3.y (Eoan kernel base on this branch), there are 107 new patches merged, we also need to merge those patches to Eoan kernel. -- 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/1849623 Title: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: [Impact] https://bugs.launchpad.net/bugs/1848790 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703 Recently we had 2 bugs about the usb host on rpi4 with 4G ram, and I found the kernel in the github already had the fix for this issue, and besides this fix, it also had 106 more patches than our eoan kernel, those patches were merged during or after we prepared our eoan kernel, now let us pick those patches to our eoan too. [Fix] For the usb host issue, it adds a fix by setting the usb dma bounce buffer under 1G. [Test Case] some users and I alreaady tested the armhf and arm64 kernel on pi4 and pi3 boards, the usb host worked well and no other regressions introduced. [Regression Risk] Low, these patches are from the github which is the pi official kernel repository. And we already tested armhf and arm64 kernel on pi4/3 boards. The rpi kernel of https://github.com/raspberrypi/linux.git has been updated, for the branch of rpi-5.3.y (Eoan kernel base on this branch), there are 107 new patches merged, we also need to merge those patches to Eoan kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** 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: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Holding before Promote to Proposed - phase-changed: Thursday, 24. October 2019 23:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 25. October 2019 02:00 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: 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-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Friday, 25. October 2019 02:00 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: amdgpu -- 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/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xo
[Kernel-packages] [Bug 1849711] Re: Only GRUB2 have MAX BRIGHTNESS in 19.04 and 19.10
I think Ubuntu 19.10 is better at remembering your previous brightness values and yes indeed that will change after grub2. So I don't think this is a bug. Unless you're saying it's the wrong brightness value being remembered? See also (probably unrelated) bug 1848360 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** 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/1849711 Title: Only GRUB2 have MAX BRIGHTNESS in 19.04 and 19.10 Status in linux package in Ubuntu: Incomplete Bug description: whenever I boot into Ubuntu the grub 2 boot loader have maximum brightness but after selecting Ubuntu OS, system return to its normal brightness value , previously my Ubuntu version is 19.04 and this problem exists but after upgrading to 19.10 this issue still there and nothing works by upgrading system, grub remains at high brightness value (even function keys not working at that time). Every time i reboot the system the grub 2 have max brightness and it returns to normal brightness after reaching to log on screen and then everything works fine even functions keys also working. laptop specs: AMD reyzen 3 2200u AMD Radeon Vega 3 HP g7 245 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 21:52:44 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:8562] MachineType: Hewlett-Packard HP 245 G7 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro quiet splash acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8562 dmi.board.vendor: Hewlett-Packard dmi.board.version: 84.24 dmi.chassis.asset.tag: 5CG9212QLP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G7 Notebook PC dmi.product.sku: 6JM93PA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849711] [NEW] Only GRUB2 have MAX BRIGHTNESS in 19.04 and 19.10
You have been subscribed to a public bug: whenever I boot into Ubuntu the grub 2 boot loader have maximum brightness but after selecting Ubuntu OS, system return to its normal brightness value , previously my Ubuntu version is 19.04 and this problem exists but after upgrading to 19.10 this issue still there and nothing works by upgrading system, grub remains at high brightness value (even function keys not working at that time). Every time i reboot the system the grub 2 have max brightness and it returns to normal brightness after reaching to log on screen and then everything works fine even functions keys also working. laptop specs: AMD reyzen 3 2200u AMD Radeon Vega 3 HP g7 245 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 21:52:44 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [103c:8562] MachineType: Hewlett-Packard HP 245 G7 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=380079ae-40a6-4aed-8280-2b263a41cf1e ro quiet splash acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2019 dmi.bios.vendor: AMI dmi.bios.version: F.42 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8562 dmi.board.vendor: Hewlett-Packard dmi.board.version: 84.24 dmi.chassis.asset.tag: 5CG9212QLP dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.42:bd07/03/2019:svnHewlett-Packard:pnHP245G7NotebookPC:pvr:rvnHewlett-Packard:rn8562:rvr84.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 245 G7 Notebook PC dmi.product.sku: 6JM93PA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug eoan ubuntu -- Only GRUB2 have MAX BRIGHTNESS in 19.04 and 19.10 https://bugs.launchpad.net/bugs/1849711 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -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 -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
I've proposed changing the error message to point to a webpage w/ a better explanation: https://marc.info/?l=linux-raid&m=157196348406853&w=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/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849062] Re: eoan/linux-oracle: 5.3.0-1004.4 -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: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1849062 Title: eoan/linux-oracle: 5.3.0-1004.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849003] Re: disco/linux: 5.0.0-33.35 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 15:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1849000 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849003 Title: disco/linux: 5.0.0-33.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 15:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1849000 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4
** Description changed: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. + + + == Temporary Workaround == + + As noted by various people below, the following line can be added to the + "usercfg.txt" file on the boot partition: + + total_mem=3072 + + This will limit the available RAM to 3Gb, but otherwise things should + operate normally. Note that this bug does not affect Pi 4Bs with less + than 4Gb of RAM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:51 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: 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-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:51 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://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 1832963] Re: sound doesn't work
yes sort of. some you tube doesn't work and some does. I have to open sound preferences to adjust any sound. it is strange On Thu, Oct 24, 2019 at 11:06 AM Kai-Heng Feng wrote: > bmike1, do you still see this issue? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832963 > > Title: > sound doesn't work > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > after installing new kernel RV770 HDMI Audio [Radeon HD > 4850/4870](Radeon 4850 512MB GODR3 PCI-E Dual Slot Fansin. reported as > Disabled and off in sound preferences->hardware > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: bmike1 1895 F pulseaudio >/dev/snd/controlC2: bmike1 1895 F pulseaudio >/dev/snd/controlC1: bmike1 1895 F pulseaudio > CurrentDesktop: MATE > DistroRelease: Linux Mint 19.1 > InstallationDate: Installed on 2019-01-15 (151 days ago) > InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 > MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H > Package: linux (not installed) > ProcFB: 0 radeondrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic > root=UUID=6298f990-6b80-4665-80ab-e83034a72ae5 ro quiet splash > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M > vt.handoff=1 > ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 > RelatedPackageVersions: >linux-restricted-modules-5.0.0-16-generic N/A >linux-backports-modules-5.0.0-16-generic N/A >linux-firmware1.173.6 > RfKill: >0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > Tags: tessa > Uname: Linux 5.0.0-16-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 09/16/2009 > dmi.bios.vendor: Award Software International, Inc. > dmi.bios.version: F4 > dmi.board.name: GA-MA785G-UD3H > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.modalias: > dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: > dmi.product.name: GA-MA785G-UD3H > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832963/+subscriptions > -- :-)~MIKE~(-: -- 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/1832963 Title: sound doesn't work Status in linux package in Ubuntu: Confirmed Bug description: after installing new kernel RV770 HDMI Audio [Radeon HD 4850/4870](Radeon 4850 512MB GODR3 PCI-E Dual Slot Fansin. reported as Disabled and off in sound preferences->hardware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmike1 1895 F pulseaudio /dev/snd/controlC2: bmike1 1895 F pulseaudio /dev/snd/controlC1: bmike1 1895 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-01-15 (151 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=6298f990-6b80-4665-80ab-e83034a72ae5 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-MA785G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/16/2009:svnGiga
[Kernel-packages] [Bug 1848953] Re: Intel wifi 3165 not working properly in Ubuntu 19.10
Confirm this issue -- 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/1848953 Title: Intel wifi 3165 not working properly in Ubuntu 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a bug appeared. I could not login to the 2.4 GHz Wifi network at home with the fresh installed Ubuntu, it says the password is wrong, but it is not. I have Dual Band Intel AC 3165 it seems. My card appears in the Additional Drivers list with the notice that the device is not working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: florin 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:49:04 2019 InstallationDate: Installed on 2019-10-19 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD Bus 001 Device 006: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE P50-C dmi.product.sku: PSPUFE dmi.product.version: PSPUFE-001009G6 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Packaging - phase-changed: Thursday, 24. October 2019 23:26 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 24. October 2019 23:51 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: 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-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:51 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -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 -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:36 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
** Changed in: charm-neutron-openvswitch Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Fix Released Status in neutron: New Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Thursday, 24. October 2019 07:06 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 24. October 2019 23:36 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:queued,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Thursday, 24. October 2019 23:36 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:queued,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff 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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Ready for Packaging - phase-changed: Thursday, 24. October 2019 06:33 UTC + phase: Packaging + phase-changed: Thursday, 24. October 2019 23:26 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: 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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Thursday, 24. October 2019 23:26 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849033] Re: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- 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/1849033 Title: xenial/linux-deeplens: 4.15.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress 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: Invalid 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 Xenial: 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 -- kernel-stable-master-bug: 1849034 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Packaging phase-changed: Thursday, 24. October 2019 06:33 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
** Changed in: charm-neutron-openvswitch Milestone: None => 19.10 -- 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Fix Committed Status in neutron: New Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803179]
(In reply to arpie from comment #140) > After hours of experimenting on this laptop : > > Computer : PC Specialist OptimusIX 15 (aka Clevo N8xxEP6) > BIOS : American Megatrends 1.07.13 > OS : Arch Linux > GPU : NVIDIA GTX 1060 Mobile > > Until recently, any attempt to use bumblebee or acpi commands to power down > the GPU have resulted in a system freeze with lspci, suspend, power cable > plug in, etc. No kernel line parameters seem to have any effect. > > I have discovered that the system freeze is closely linked to the > interaction between the nvidia graphics card on pci address :01:00.0 and > its associated sound card at pci address :01:00.1 (I don't actually > know what that sound card is doing - I presume it's for the HDMI port?) > > If I completely disable the audio card using : > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove > > Then the system hangs are completely cured - I can acpi _OFF or _ON or _PS3 > or _PS0 to my hearts content and the gfx card will power up and down > perfectly, lspci behaves perfectly normally (without any lag), and > suspend/resume and power cable plug/unplug all works. Even better, kernel > power management on the PCI bus seems to work perfectly too, but only kicks > in when I rmmod nvidia. So far, bumblebee and bbswitch also seem to be > totally happy. > > Can anybody else confirm similar findings? > > Bear in mind that the audio card needs to be removed BEFORE the kernel loads > any audio modules. I do it like this : > > [Unit] > Description=Nvidia Audio Card OnBoot Disabler > Before=bumblebeed.service > > [Service] > Type=oneshot > RemainAfterExit=yes > ExecStart=/usr/bin/sh -c "echo 1 > /sys/bus/pci/devices/:01:00.1/remove" > ExecStop=/usr/bin/sh -c "echo 1 > /sys/bus/pci/rescan" > > [Install] > WantedBy=sysinit.target Not working for me. Still freezing with this. -- 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/1803179 Title: System does not reliably come out of suspend Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Confirmed Bug description: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849745] [NEW] hp spectre x360 15 df0033dx
Public bug reported: I used to own hp spectre 15 ch011dx, had issues with ubuntu 18.04 on it so i upgraded to 19.04 and literally every problem on it was fixed. The issues i used to have on 18.04 that got fixed in 19.04 Never used to sleep. Microphone Didn't work until i used an ear piece that had one. Bluetooth never connected Battery was being drained at an enormous rate. Now using the newer version of hp spectre 15 the issues have returned. I even had to move from 19.04 to 19.10 and these issues still persist. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1849745 Title: hp spectre x360 15 df0033dx Status in linux-firmware package in Ubuntu: New Bug description: I used to own hp spectre 15 ch011dx, had issues with ubuntu 18.04 on it so i upgraded to 19.04 and literally every problem on it was fixed. The issues i used to have on 18.04 that got fixed in 19.04 Never used to sleep. Microphone Didn't work until i used an ear piece that had one. Bluetooth never connected Battery was being drained at an enormous rate. Now using the newer version of hp spectre 15 the issues have returned. I even had to move from 19.04 to 19.10 and these issues still persist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1849745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849062] Re: eoan/linux-oracle: 5.3.0-1004.4 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1849062 Title: eoan/linux-oracle: 5.3.0-1004.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
Thanks Paul. Adding the alsa-ucm files and boosting alsa settings has enabled the audio. Are you hearing substantial static? I'm going to install the topology file if that will take care of it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We tested the EOAN kernel on the LENOVO or Dell machines which have dmic directly connnected to PCH, the dmic didn't work. [Fix] We need to enable SOF_HDA link and codec, then the sof driver and Legacy HDA driver work together to make the dmic work. [Test Case] Install the latest 19.10 image, build a new kernel with this patch and replace the existing kernel, After installing the blacklist package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, the dmic and all output devices (speaker/hdmi) work. [Regression Risk] Low, these configs are already enabled in the oem-b-osp1 kernel for a long time, and we tested it on many lenovo/dell machines witch have or have no dmic, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849060] Re: eoan/linux-gcp: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1849060 Title: eoan/linux-gcp: 5.3.0-1006.6 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Thursday, 24. October 2019 07:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
** Description changed: Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. - Upstream is dealing with this by adding a versioned layout in v5.4, and - backporting that via stable. Version 1 is the pre-3.14 layout, Version 2 + This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: + https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 + + To summarize, upstream is dealing with this by adding a versioned layout + in v5.4, and that is being backported to stable kernels - which is why + we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. - - These changes are now coming into our kernels via stable backports of - the following commit, which describes the problem in the commit message: - - https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. + Note that it also seems like we should investigate backporting this to < + 3.14 kernels. Imagine a user switching between the trusty HWE kernel and + the GA kernel. + References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. -- 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/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layo
[Kernel-packages] [Bug 1849062] Re: eoan/linux-oracle: 5.3.0-1004.4 -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: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Thursday, 24. October 2019 18:52 UTC + phase: Promote to Proposed + phase-changed: Thursday, 24. October 2019 21:21 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1849062 Title: eoan/linux-oracle: 5.3.0-1004.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849062] Re: eoan/linux-oracle: 5.3.0-1004.4 -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) => Andy Whitcroft (apw) -- 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/1849062 Title: eoan/linux-oracle: 5.3.0-1004.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 21:21 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
** Description changed: Users of RAID0 arrays are susceptible to a corruption issue if: - - The members of the RAID array are not all the same size[*] - - Data has been written to the array while running kernels < 3.14 and >= 3.14. + - The members of the RAID array are not all the same size[*] + - Data has been written to the array while running kernels < 3.14 and >= 3.14. Upstream is dealing with this by adding a versioned layout in v5.4, and backporting that via stable. Version 1 is the pre-3.14 layout, Version 2 - is post 3.14. However, unless a layout-version-aware kernel *created* - the array, there's no way for the kernel to know which version was used - to write the existing data. This undefined mode is considered "Version - 0", and the kernel will now refuse to start these arrays w/o user - intervention. + is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. + However, unless a layout-version-aware kernel *created* the array, + there's no way for the kernel to know which version(s) was used to write + the existing data. This undefined mode is considered "Version 0", and + the kernel will now refuse to start these arrays w/o user intervention. These changes are now coming into our kernels via stable backports of the following commit, which describes the problem in the commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 - - What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable. + What that is trying to say is that you should determine if your data - + specifically the data toward the end of your array - was most likely + written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with + the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on + the kernel command line. And note it should be *raid0.default_layout* + not *raid.default_layout* as the message says - a fix for that message + is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) + + IMHO, we should work with upstream to create a web page that clearly + walks the user through this process, and update the error message to + point to that page. I'd also like to see if we can detect this problem + *before* the user reboots (debconf?) and help the user fix things. e.g. + "We detected that you have RAID0 arrays that maybe susceptible to a + corruption problem", guide the user to choosing a layout, and update the + mdadm initramfs hook to poke the answer in via sysfs before starting the + array on reboot. + [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. ** Description changed: Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - - Data has been written to the array while running kernels < 3.14 and >= 3.14. + - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. Upstream is dealing with this by adding a versioned layout in v5.4, and backporting that via stable. Version 1 is the pre-3.14 layout, Version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. These changes are now coming into our kernels via stable backports of the following commit, which describes the problem in the commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
** Description changed: - [Impact] - After installing the 4.15.0-67.76 kernel from bionic-proposed, our Nvidia DGX2 system is no longer bootable. + Users of RAID0 arrays are susceptible to a corruption issue if: + - The members of the RAID array are not all the same size[*] + - Data has been written to the array while running kernels < 3.14 and >= 3.14. - [Test Case] - [Fix] - [Regression Risk] + Upstream is dealing with this by adding a versioned layout in v5.4, and + backporting that via stable. Version 1 is the pre-3.14 layout, Version 2 + is post 3.14. However, unless a layout-version-aware kernel *created* + the array, there's no way for the kernel to know which version was used + to write the existing data. This undefined mode is considered "Version + 0", and the kernel will now refuse to start these arrays w/o user + intervention. + + These changes are now coming into our kernels via stable backports of + the following commit, which describes the problem in the commit message: + + https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 + + The user experience is pretty awful here. A user upgrades to the next + SRU and all of a sudden their system stops at an (initramfs) prompt. A + clueful user can spot something like the following in dmesg: + + Here's the message which , as you can see from the log in Comment #1, is + hidden in a ton of other messages: + + [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting + [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 + [ 72.733979] md: pers->run() failed ... + mdadm: failed to start array /dev/md0: Unknown error 524 + + + What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable. + + https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) + + [*] Which surprisingly is not the case reported in this bug - the user + here had a raid0 of 8 identically-sized devices. I suspect there's a bug + in the detection code somewhere. -- 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/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. Upstream is dealing with this by adding a versioned layout in v5.4, and backporting that via stable. Version 1 is the pre-3.14 layout, Version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. These changes are now coming into our kernels via stable backports of the following commit, which describes the problem in the commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://git
[Kernel-packages] [Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848997 Title: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- kernel-stable-master-bug: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 11:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 11:56 UTC reason: - promote-to-proposed: Stalled -- review FAILED + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848997 Title: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- kernel-stable-master-bug: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 11:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848741] Re: Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u
what equipment do you have on my Huawei matebook d 14 from ryzen I noticed problems waking up from sleep Pozdrawiam Arkadiusz Plich -- 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/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849023] Re: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Thursday, 24. October 2019 20:35 UTC + phase: Testing + phase-changed: Thursday, 24. October 2019 20:46 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849023 Title: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 24. October 2019 20:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849023] Re: bionic/linux-fips: 4.15.0-1019.22 -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: 1849035 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Promote to Proposed - phase-changed: Thursday, 24. October 2019 17:16 UTC + phase: Promote to Proposed + phase-changed: Thursday, 24. October 2019 20:35 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849023 Title: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 24. October 2019 20:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
Also using a Lenovo X1 7th generation. I can confirm that everything works using 5.3.0-20. I suspect that I've compared to Joel above me, taken a few extra steps: * Added snd_hda_intel and snd_soc_skl to /etc/modprobe/blacklist.conf * Added the alsa-ucm files from [1] to /usr/share/alsa/ucm/sof- skl_hda_card * Added this sof topology file [2] from a Lenovo employee to /usr/lib/firmware/intel/sof-tplg I have the following devices displayed using `arecord -l` card 0: sofsklhdacard [sof-skl_hda_card], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsklhdacard [sof-skl_hda_card], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsklhdacard [sof-skl_hda_card], device 6: DMIC32 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsklhdacard [sof-skl_hda_card], device 7: DMIC16 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 In pulseaudio I have the following sources index: 4 name: driver: flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 1030 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max rewind: 0 KiB sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 341,00 ms monitor_of: 2 card: 2 module: 9 properties: device.description = "Monitor of Cannon Point-LP High Definition Audio Controller HDMI3/DP3 Output" device.class = "monitor" alsa.card = "0" alsa.card_name = "sof-skl_hda_card" alsa.long_card_name = "LENOVO-20QDS0A600-ThinkPadX1Carbon7th-20QDS0A600" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9dc8" device.product.name = "Cannon Point-LP High Definition Audio Controller" device.string = "0" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" index: 5 name: driver: flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 1030 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max rewind: 0 KiB sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 341,00 ms monitor_of: 3 card: 2 module: 9 properties: device.description = "Monitor of Cannon Point-LP High Definition Audio Controller HDMI2/DP2 Output" device.class = "monitor" alsa.card = "0" alsa.card_name = "sof-skl_hda_card" alsa.long_card_name = "LENOVO-20QDS0A600-ThinkPadX1Carbon7th-20QDS0A600" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9dc8" device.product.name = "Cannon Point-LP High Definition Audio Controller" device.string = "0" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" index: 6 name: driver: flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 1030 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max rewind: 0 KiB sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0
[Kernel-packages] [Bug 1849023] Re: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1849023 Title: bionic/linux-fips: 4.15.0-1019.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Thursday, 24. October 2019 20:35 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822797] Re: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta)
For what it is worth, zfs works quite well for a root fs rpool on a 4Gb RPI4b. -- 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/1822797 Title: ZFS module is installed for wrong kernel on arm64-raspi3 systems (19.04 beta) Status in linux-raspi2 package in Ubuntu: Triaged Bug description: Platform: Raspberry Pi 3 running ubuntu-19.04-beta-preinstalled- server-arm64+raspi3.img Kernel: Default (Linux ubuntu 4.18.0-1010-raspi2 #12-Ubuntu SMP PREEMPT Tue Feb 12 12:17:11 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux) Problem: The ZFS module is installed for a kernel that can not be used. apt-get install zfs-initramfs Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-zed zfsutils-linux Suggested packages: fdutils linux-doc-5.0.0 | linux-source-5.0.0 linux-tools linux-headers-5.0.0-8-snapdragon nfs-kernel-server samba-common-bin The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-8-snapdragon linux-modules-5.0.0-8-snapdragon zfs-initramfs zfs-zed zfsutils-linux 0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded. Need to get 55.7 MB of archives. After this operation, 305 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-modules-5.0.0-8-snapdragon arm64 5.0.0-8.9 [47.5 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 linux-image-unsigned-5.0.0-8-snapdragon arm64 5.0.0-8.9 [7169 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libnvpair1linux arm64 0.7.12-1ubuntu5 [42.8 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libuutil1linux arm64 0.7.12-1ubuntu5 [50.7 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzpool2linux arm64 0.7.12-1ubuntu5 [498 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 libzfs2linux arm64 0.7.12-1ubuntu5 [121 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfsutils-linux arm64 0.7.12-1ubuntu5 [267 kB] Get:8 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-initramfs arm64 0.7.12-1ubuntu5 [22.2 kB] Get:9 http://ports.ubuntu.com/ubuntu-ports disco/main arm64 zfs-zed arm64 0.7.12-1ubuntu5 [57.5 kB] Fetched 55.7 MB in 37s (1486 kB/s) Selecting previously unselected package linux-modules-5.0.0-8-snapdragon. (Reading database ... 61671 files and directories currently installed.) Preparing to unpack .../0-linux-modules-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package linux-image-unsigned-5.0.0-8-snapdragon. Preparing to unpack .../1-linux-image-unsigned-5.0.0-8-snapdragon_5.0.0-8.9_arm64.deb ... Unpacking linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ... Selecting previously unselected package libnvpair1linux. Preparing to unpack .../2-libnvpair1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libnvpair1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libuutil1linux. Preparing to unpack .../3-libuutil1linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libuutil1linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzpool2linux. Preparing to unpack .../4-libzpool2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzpool2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package libzfs2linux. Preparing to unpack .../5-libzfs2linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking libzfs2linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfsutils-linux. Preparing to unpack .../6-zfsutils-linux_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfsutils-linux (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-initramfs. Preparing to unpack .../7-zfs-initramfs_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-initramfs (0.7.12-1ubuntu5) ... Selecting previously unselected package zfs-zed. Preparing to unpack .../8-zfs-zed_0.7.12-1ubuntu5_arm64.deb ... Unpacking zfs-zed (0.7.12-1ubuntu5) ... Setting up libuutil1linux (0.7.12-1ubuntu5) ... Setting up linux-modules-5.0.0-8-snapdragon (5.0.0-8.9) ... Setting up linux-image-unsigned-5.0.0-8-snapdragon (5.0.0-8.9) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.0.0-8-snapdragon I: /boot/initrd.img is now a symlink to initrd.img-5.0.0-8-snapdragon Setting up libnvpair1linux (0.7.12-1ubuntu5) ... Setting up libzpool2linux (0.7.12-1ubuntu5) ... Setting up libzfs2linux (0.7.12-1ubuntu5)
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
I pulled the various .deb packages from https://launchpad.net /~canonical-kernel-team/+archive/ubuntu/ppa/+build/17953251/+files/ and installed them on my Bionic host. $ uname -a Linux c2d.mgmt.sdeziel.info 5.3.0-20-generic #21-Ubuntu SMP Wed Oct 23 16:20:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With that kernel it works so marking as verified for Eoan. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfK
[Kernel-packages] [Bug 1849724] 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/1849724 Title: Thinkpad T470s failure to suspend Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 19.10, my Thinkpad T470s sometimes refuses to suspend. This *appears* to happen if I've previously suspended it since the last full reboot, though it's hard to be sure that this is always the case. When it fails to suspend, the following is logged to kern.log: Oct 24 12:09:42 localhost kernel: [15809.059931] Filesystems sync: 0.010 seconds Oct 24 12:09:42 localhost kernel: [15809.060368] Freezing user space processes ... (elapsed 0.004 seconds) done. Oct 24 12:09:42 localhost kernel: [15809.065301] OOM killer disabled. Oct 24 12:09:42 localhost kernel: [15809.065302] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Oct 24 12:09:42 localhost kernel: [15809.066938] printk: Suspending console(s) (use no_console_suspend to debug) Oct 24 12:09:42 localhost kernel: [15809.947126] e1000e: EEE TX LPI TIMER: 0011 Oct 24 12:09:42 localhost kernel: [15809.954275] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x60 [e1000e] returns -2 Oct 24 12:09:42 localhost kernel: [15809.954277] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 Oct 24 12:09:42 localhost kernel: [15809.954278] PM: Device :00:1f.6 failed to suspend async: error -2 Oct 24 12:09:42 localhost kernel: [15809.989504] PM: Some devices failed to suspend, or early wake event detected Oct 24 12:09:42 localhost kernel: [15810.747730] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4762] Oct 24 12:09:42 localhost kernel: [15810.782411] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..] Oct 24 12:09:42 localhost kernel: [15810.893760] OOM killer enabled. Oct 24 12:09:42 localhost kernel: [15810.893761] Restarting tasks ... Oct 24 12:09:42 localhost kernel: [15810.899483] mei_hdcp mei::b638ab7e-94e2-4ea2-a552-d1c54b627f04:01: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Oct 24 12:09:42 localhost kernel: [15810.907488] done. Oct 24 12:09:42 localhost kernel: [15810.909513] thermal thermal_zone2: failed to read out thermal zone (-61) Oct 24 12:09:42 localhost kernel: [15810.946024] PM: suspend exit Oct 24 12:09:42 localhost kernel: [15811.200265] [drm] Reducing the compressed framebuffer size. This may lead to less power sa vings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. This looks to me like a bug in the Intel ethernet driver. In dmesg, on boot I see the following ethernet driver loaded: [0.674440] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2060 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 24 15:51:11 2019 InstallationDate: Installed on 2017-08-16 (798 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-04 (20 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW 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:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi
[Kernel-packages] [Bug 1849724] [NEW] Thinkpad T470s failure to suspend
Public bug reported: Since upgrading to Ubuntu 19.10, my Thinkpad T470s sometimes refuses to suspend. This *appears* to happen if I've previously suspended it since the last full reboot, though it's hard to be sure that this is always the case. When it fails to suspend, the following is logged to kern.log: Oct 24 12:09:42 localhost kernel: [15809.059931] Filesystems sync: 0.010 seconds Oct 24 12:09:42 localhost kernel: [15809.060368] Freezing user space processes ... (elapsed 0.004 seconds) done. Oct 24 12:09:42 localhost kernel: [15809.065301] OOM killer disabled. Oct 24 12:09:42 localhost kernel: [15809.065302] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Oct 24 12:09:42 localhost kernel: [15809.066938] printk: Suspending console(s) (use no_console_suspend to debug) Oct 24 12:09:42 localhost kernel: [15809.947126] e1000e: EEE TX LPI TIMER: 0011 Oct 24 12:09:42 localhost kernel: [15809.954275] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x60 [e1000e] returns -2 Oct 24 12:09:42 localhost kernel: [15809.954277] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 Oct 24 12:09:42 localhost kernel: [15809.954278] PM: Device :00:1f.6 failed to suspend async: error -2 Oct 24 12:09:42 localhost kernel: [15809.989504] PM: Some devices failed to suspend, or early wake event detected Oct 24 12:09:42 localhost kernel: [15810.747730] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4762] Oct 24 12:09:42 localhost kernel: [15810.782411] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..] Oct 24 12:09:42 localhost kernel: [15810.893760] OOM killer enabled. Oct 24 12:09:42 localhost kernel: [15810.893761] Restarting tasks ... Oct 24 12:09:42 localhost kernel: [15810.899483] mei_hdcp mei::b638ab7e-94e2-4ea2-a552-d1c54b627f04:01: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) Oct 24 12:09:42 localhost kernel: [15810.907488] done. Oct 24 12:09:42 localhost kernel: [15810.909513] thermal thermal_zone2: failed to read out thermal zone (-61) Oct 24 12:09:42 localhost kernel: [15810.946024] PM: suspend exit Oct 24 12:09:42 localhost kernel: [15811.200265] [drm] Reducing the compressed framebuffer size. This may lead to less power sa vings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. This looks to me like a bug in the Intel ethernet driver. In dmesg, on boot I see the following ethernet driver loaded: [0.674440] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 2060 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 24 15:51:11 2019 InstallationDate: Installed on 2017-08-16 (798 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-04 (20 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW 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:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849724 Title: Thinkpad T470s failure to suspend Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 19.10, my Thinkpad T470s
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Same with the ASUS Zenbook UX333FA on Ubuntu 19.10. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
Using a Lenovo x1 7th generation, I've installed 5.3.0-20 and verified that I see "# CONFIG_SND_SOC_SOF_NOCODEC_SUPPORT is not set" (I don't see any of the SKYLAKE changes on the other thread.) I've added the following blacklist lines to modprobe.d: blacklist snd_hda_intel blacklist snd_soc_skl I see Input Device as "Multichannel Input - Cannon Point-LP High Definition Audio Controller" in sound preferences, and card sof- skl_hda_card in alsamixer. The speakers work, but the mic does not pick anything up. -- 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/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We tested the EOAN kernel on the LENOVO or Dell machines which have dmic directly connnected to PCH, the dmic didn't work. [Fix] We need to enable SOF_HDA link and codec, then the sof driver and Legacy HDA driver work together to make the dmic work. [Test Case] Install the latest 19.10 image, build a new kernel with this patch and replace the existing kernel, After installing the blacklist package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, the dmic and all output devices (speaker/hdmi) work. [Regression Risk] Low, these configs are already enabled in the oem-b-osp1 kernel for a long time, and we tested it on many lenovo/dell machines witch have or have no dmic, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849056] Re: eoan/linux-raspi2: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1849056 Title: eoan/linux-raspi2: 5.3.0-1009.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849064 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 24. October 2019 15:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
