[Kernel-packages] [Bug 1878544] [NEW] kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
Public bug reported: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "Image capturing the full bug" https://bugs.launchpad.net/bugs/1878544/+attachment/5371316/+files/IMG_20200513_232520.jpg -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatu
[Kernel-packages] [Bug 1878544] 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Hey AaronMa, What do you mean with "found that LID close until the BIOS logo show, unless the laptop will shut down."? So you tested using the HDMI cable directly attached to the laptop and everything worked even with something attached to the thunderbolt port? Which kind of docking station are you using? With that said I've tried the latest BIOS: BIOS Information Vendor: LENOVO Version: N2OET42W (1.29 ) Release Date: 01/20/2020 Address: 0xE Runtime Size: 128 kB ROM Size: 32 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 kB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.29 Firmware Revision: 1.22 And results are the same: if something is attached to thunderbolt, no way to see even grub, if nothing is attached (and LID is closed) then I see grub loading on the external monitor but I don't get GDM. What do you mean exactly with "BIOS should be default setting with optimized enabled"? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed Status in linux package in Ubuntu: Confirmed Bug description: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET43W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.as
[Kernel-packages] [Bug 1878365] Re: abc file missing
I'm closing this as it does not look like a valid bug report. Please feel free to open a a new one. Thanks ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1878365 Title: abc file missing Status in linux package in Ubuntu: Invalid Bug description: abc file missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
try kernel 5.7.0-994.20200511220 see: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 -- 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/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW 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:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U
after more hours of testing i do not get any more freeze with 5.7.0-994.20200511220 -- 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/1873594 Title: sporadic black screen freeze on lenovo e595 Ryzen 3700U Status in linux package in Ubuntu: Incomplete Bug description: Hi, i have sporadic black screen freeze on my lenovo e595 3700U during reboot. The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT Problem occure also on linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64 and linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64 19.10 was working with 5.0 kernel regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gizzmo 1345 F pulseaudio /dev/snd/controlC1: gizzmo 1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:28:37 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 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 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW 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:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876919] Re: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)
*** This bug is a duplicate of bug 1878045 *** https://bugs.launchpad.net/bugs/1878045 ** This bug has been marked a duplicate of bug 1878045 doing dist-upgrade got error related do Broadcom -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1876919 Title: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch) Status in bcmwl package in Ubuntu: Confirmed Bug description: Diagnostics from apt & dkms post-install : Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-28-generic 5.4.0-29-generic Building for architecture x86_64 Building initial module for 5.4.0-28-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. Probably the patch 0028 adding kernel 5.6 support should not be applied during building on kernel 5.4 As I understand, right now Ubuntu Groovy is still at kernel 5.4, not 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1876919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877414] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1878045 *** https://bugs.launchpad.net/bugs/1878045 ** This bug is no longer a duplicate of bug 1876919 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch) ** This bug has been marked a duplicate of bug 1878045 doing dist-upgrade got error related do Broadcom -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1877414 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: Output from apt full-upgrade bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) wird eingerichtet ... Removing old bcmwl-6.30.223.271+bdcom DKMS files... -- Deleting module version: 6.30.223.271+bdcom completely from the DKMS tree. -- Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-26-generic Building for architecture x86_64 Building initial module for 5.4.0-26-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: Fehler beim Bearbeiten des Paketes bcmwl-kernel-source (--configure): »installiertes bcmwl-kernel-source-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 6 zurück Fehler traten auf beim Bearbeiten von: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) Lubuntu 20.10 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu32 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-26-generic Date: Thu May 7 17:39:25 2020 InstallationDate: Installed on 2019-09-21 (229 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190920) PackageVersion: 6.30.223.271+bdcom-0ubuntu6 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu6: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1877414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878554] [NEW] alsa/hdmi: restore the component support patch_nvhdmi
Public bug reported: this is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: originate-from-1876671 sutton ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: originate-from-1876671 sutton ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux-oem-5.6 (Ubuntu Groovy) -- 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/1878554 Title: alsa/hdmi: restore the component support patch_nvhdmi Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: New Bug description: this is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1878554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876919] Re: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch)
*** This bug is a duplicate of bug 1878045 *** https://bugs.launchpad.net/bugs/1878045 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1878045, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1876919 Title: 6.30.223.271+bdcom-0ubuntu6 fails when building on kernel 5.4.0-28-generic x86_64 (Ubuntu Groovy 20.10 dev.branch) Status in bcmwl package in Ubuntu: Confirmed Bug description: Diagnostics from apt & dkms post-install : Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-28-generic 5.4.0-29-generic Building for architecture x86_64 Building initial module for 5.4.0-28-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. Probably the patch 0028 adding kernel 5.6 support should not be applied during building on kernel 5.4 As I understand, right now Ubuntu Groovy is still at kernel 5.4, not 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1876919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878554] Re: alsa/hdmi: restore the component support patch_nvhdmi
** Description changed: - this is for tracking purpose. + BugLink: https://bugs.launchpad.net/bugs/1878554 + + The reverted patch was introduced by stable-patches, and this SRU + plans to revert the patch, the commit id is from oem-5.6 kernel, + so maybe in the Groovy and unstable kernel, the commit id is not + same as this one. + + [Impact] + On Lenovo P520 with Nvida P4000 grahic card, the hdmi audio doesn't + work. + + [Fix] + revert an existing patch to let patch_nvhdmi support component. + + [Test Case] + boot the system, plug the hdmi/dp monitor, the hdmi audio could work, + wait for 10 mins until the screen become black, wake up the screen and + check the audio, still work well. + + [Regression Risk] + Low, after reverting the patch, it is aligned to mainline 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/1878554 Title: alsa/hdmi: restore the component support patch_nvhdmi Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Bug description: BugLink: https://bugs.launchpad.net/bugs/1878554 The reverted patch was introduced by stable-patches, and this SRU plans to revert the patch, the commit id is from oem-5.6 kernel, so maybe in the Groovy and unstable kernel, the commit id is not same as this one. [Impact] On Lenovo P520 with Nvida P4000 grahic card, the hdmi audio doesn't work. [Fix] revert an existing patch to let patch_nvhdmi support component. [Test Case] boot the system, plug the hdmi/dp monitor, the hdmi audio could work, wait for 10 mins until the screen become black, wake up the screen and check the audio, still work well. [Regression Risk] Low, after reverting the patch, it is aligned to mainline kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1878554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
Another cherry-pick is needed for patch "crypto: hisilicon/sec2 - modify the SEC probe process" /home/ubuntu/focal/drivers/crypto/hisilicon/sec2/sec_main.c: In function ‘sec_qm_init’: /home/ubuntu/focal/drivers/crypto/hisilicon/sec2/sec_main.c:770:5: error: ‘struct hisi_qm’ has no member named ‘qm_list’ qm->qm_list = &sec_devices; ^~ /home/ubuntu/focal/drivers/crypto/hisilicon/sec2/sec_main.c:770:18: error: ‘sec_devices’ undeclared (first use in this function); did you mean ‘sec_dev_ids’? qm->qm_list = &sec_devices; ^~~ sec_dev_ids -- 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/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878554] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1878554 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878554 Title: alsa/hdmi: restore the component support patch_nvhdmi Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Bug description: BugLink: https://bugs.launchpad.net/bugs/1878554 The reverted patch was introduced by stable-patches, and this SRU plans to revert the patch, the commit id is from oem-5.6 kernel, so maybe in the Groovy and unstable kernel, the commit id is not same as this one. [Impact] On Lenovo P520 with Nvida P4000 grahic card, the hdmi audio doesn't work. [Fix] revert an existing patch to let patch_nvhdmi support component. [Test Case] boot the system, plug the hdmi/dp monitor, the hdmi audio could work, wait for 10 mins until the screen become black, wake up the screen and check the audio, still work well. [Regression Risk] Low, after reverting the patch, it is aligned to mainline kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1878554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
** Changed in: linux (Ubuntu Focal) Importance: Undecided => High -- 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/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876066] Re: Support Intel TGL CPU on Focal
This bug was fixed in the package thermald - 1.9.1-1ubuntu0.1 --- thermald (1.9.1-1ubuntu0.1) focal; urgency=medium * Intel Tiger Lake support (LP: #1876066) -- Alex Tu Thu, 30 Apr 2020 18:16:16 +0800 ** Changed in: thermald (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: Support Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Groovy: Fix Released Bug description: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu It can be checked by following command, and the patch works if it return "passed". $ systemctl is-active --quiet thermald && echo passed [regression potential] because TGL is not supported by current thermald, so thermald always inactive on TGL platform. This patch is to activate it. So, there's not potential regression. [scope] needed for F/G [original description] need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1876066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875884] Re: Kernel log flood "ceph: Failed to find inode for 1"
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875884 Title: Kernel log flood "ceph: Failed to find inode for 1" Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux-azure-4.15 source package in Bionic: New Bug description: OS provided by AKS is currently Ubuntu 16.04.6 LTS, kernel 4.15.0-1077-azure. Every block written by a k8s pod to a ceph CSI volume generates 2 warning lines in the node's system logs (kern.log, syslog, messages, warn): "Apr 24 09:37:46 aks- kernel: [242123.654538] ceph: Failed to find inode for 1" Under production load, eventually the node succumbs to DiskPressure as the drive fills up. Also performance is noticeably degraded. Background here: https://tracker.ceph.com/issues/45283 Luis Hernandez indicates 4 commits relating to this issue, just 2 of which have been backported to Ubuntu 16. d557c48db730 ("ceph: quota: add counter for snaprealms with quota") <== e3161f17d926 ("ceph: quota: cache inode pointer in ceph_snap_realm") 0eb6bbe4d9cf ("ceph: fix root quota realm check") <== 2596366907f8 ("ceph: don't check quota for snap inode") Quoth Luis: "I've done a quick test and, after compiling the bionic kernel 4.15.0-96.97 (the latest released), I can reproduce the issue. Cherry-picking the 2 missing commits (2596366907f8 and e3161f17d926) fixes it." In my testing Ubuntu 18 does not exhibit the bug, but Azure support tells me it will be months before they make it GA in AKS. Can we get those commits backported to Ubuntu 16? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-azure (not installed) ProcVersionSignature: Ubuntu 4.15.0-1077.82-azure 4.15.18 Uname: Linux 4.15.0-1077-azure x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Wed Apr 29 12:45:12 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-azure UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux-azure-4.15 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1082-azure root=UUID=026eedeb-bd55-4fe3-9e65-0f5f76c13202 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 ProcVersionSignature: Ubuntu 4.15.0-1082.92~16.04.1-azure 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1082-azure N/A linux-backports-modules-4.15.0-1082-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.15.0-1082-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 2B0B428F-CF5B-3142-8500-028AFD70E74B dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876066] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1876066 Title: Support Intel TGL CPU on Focal Status in OEM Priority Project: Confirmed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Groovy: Fix Released Bug description: [impact] thermald doesn't support Tiger Lake cpus [test case] run thermald on Tiger Lake cpu It can be checked by following command, and the patch works if it return "passed". $ systemctl is-active --quiet thermald && echo passed [regression potential] because TGL is not supported by current thermald, so thermald always inactive on TGL platform. This patch is to activate it. So, there's not potential regression. [scope] needed for F/G [original description] need the patch to support Intel TGL CPU on Focal https://github.com/intel/thermal_daemon/blob/master/src/thd_engine.cpp#L666 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1876066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend
The patch works for me. Many thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
Open LID, press power button, wait for BIOS show logo. close LID. Set Optimized=Enable before load default setting. ThinkPad Thunderbolt 3 Dock Gen 2: https://pcsupport.lenovo.com/us/en/solutions/pd500265 GPU is hybrid, BIOS can't be shown on external monitor. no grub shown, wait enough time, GDM show on external monitor. HDMI directly on laptop, typec monitor on laptop, DP monitor on dock are all OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed Status in linux package in Ubuntu: Confirmed Bug description: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET43W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET43W(1.30):bd03/24/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
** Description changed: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] The commit is from https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal + [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] - Clear cherry pick from below - https://lkml.org/lkml/2020/4/24/635 + Clear cherry pick from linux-next + 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. -- 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/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] The commit is from https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Changed in: linux (Ubuntu Focal) Importance: Undecided => High -- 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_hdmi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine bnep snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm nls_iso8859_1 mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event dell_laptop ledtrig_audio snd_rawmidi x86_pkg_temp_thermal intel_powerclamp coretemp joydev kvm_intel kvm cdc_ether intel_cstate intel_rapl_perf snd_seq usbnet serio_raw iwlmvm r8152 [ 2556.956409] w
[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch
Xinwei has commented that this patchset may also fix bug# 1867900 -- 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/1867591 Title: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver crypto: hisilicon/sec2 - Update IV and MAC operation crypto: hisilicon/sec2 - Add iommu status check crypto: hisilicon/sec2 - Add workqueue for SEC driver. crypto: hisilicon - Use one workqueue per qm instead of per qp crypto: hisilicon - qm depends on UACCE crypto: hisilicon - remove redundant assignment of pointer ctx hisilicon - register zip engine to uacce hisilicon - Remove module_param uacce_mode uacce: add uacce driver uacce: Add documents for uacce crypto: hisilicon - Fix duplicate print when qm occur multiple errors crypto: hisilicon - Unify error detect process into qm crypto: hisilicon - Configure zip RAS error type crypto: hisilicon - Unify hardware error init/uninit into QM To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-14 04:19 EDT--- It's now 12. I included the "s390/pci: Fix zpci_alloc_domain() over allocation" commit but that just landed on master-next. Also I included the one I mentioned in that bugzilla. s390/pci: Improve handling of unset UID Both together allow things to apply more cleanly. Their code is basically replaced by the multi-function series though. As the second wasn't taken I'll include it as part of this series. Then there is an additional documentation only commit: s390/pci: Documentation for zPCI and a one line fixup s390/pci: removes wrong PCI multifunction assignment I'll add all of the patches here as attachments even if they applied clean just so we keep this together. -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: Improve handling of unset UID
--- Comment on attachment From niklas.schne...@ibm.com 2020-05-14 04:33 EDT--- This patch isn't strictly part of the multi-function work and is in fact entirely replaced by it but it allows the latter to apply cleanly and matches upstream. ** Attachment added: "s390/pci: Improve handling of unset UID" https://bugs.launchpad.net/bugs/1874056/+attachment/5371388/+files/0001-s390-pci-Improve-handling-of-unset-UID.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] 390/pci: Expose new port attribute for PCIe functions
--- Comment on attachment From niklas.schne...@ibm.com 2020-05-14 04:38 EDT--- This patch also isn't strictly part of the multi-function patch series but it adds a member to the "struct zpci_dev" that we would otherwise have to declare as reserved which is an unnecessary deviation from upstream and will make thins not apply cleanly in the future. It's ordered after the "s390/pci: embedding hotplug_slot in zdev" patch to match upstream history even though that is already a preparation commit for multi-functions. ** Attachment added: "390/pci: Expose new port attribute for PCIe functions" https://bugs.launchpad.net/bugs/1874056/+attachment/5371390/+files/0003-s390-pci-Expose-new-port-attribute-for-PCIe-function.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: adaptation of iommu to multifunction
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:39 EDT--- ** Attachment added: "s390/pci: adaptation of iommu to multifunction" https://bugs.launchpad.net/bugs/1874056/+attachment/5371391/+files/0004-s390-pci-adaptation-of-iommu-to-multifunction.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: embedding hotplug_slot in zdev
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:34 EDT--- ** Attachment added: "s390/pci: embedding hotplug_slot in zdev" https://bugs.launchpad.net/bugs/1874056/+attachment/5371389/+files/0002-s390-pci-embedding-hotplug_slot-in-zdev.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878296] Re: rtl8723bu wifi issue after being turned off
Skipped Groovy for now and hopefully it will soon be fixed automatically when upgraded to any version newer than 5.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878296 Title: rtl8723bu wifi issue after being turned off Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Confirmed Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: With the rtl8723bu wireless adapter, if the wifi is turned off and then turned on again, the system can't connect to a wireless network until the system is rebooted. The issue is not upstream. With mainline kernel and in other distros, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 19:02:49 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN Adapter 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: Positivo Tecnologia SA N1240 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA dmi.bios.version: V1.09.X dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: N14DP6 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11139547 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: MASTER dmi.product.name: N1240 dmi.product.sku: 3052532 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Positivo Tecnologia SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878296] Re: rtl8723bu wifi issue after being turned off
https://lists.ubuntu.com/archives/kernel-team/2020-May/109920.html ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1878296 Title: rtl8723bu wifi issue after being turned off Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: Confirmed Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: With the rtl8723bu wireless adapter, if the wifi is turned off and then turned on again, the system can't connect to a wireless network until the system is rebooted. The issue is not upstream. With mainline kernel and in other distros, everything works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 19:02:49 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 300k Pixel Camera Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN Adapter 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: Positivo Tecnologia SA N1240 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA dmi.bios.version: V1.09.X dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: N14DP6 dmi.board.vendor: Positivo Tecnologia SA dmi.board.version: 11139547 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Positivo Tecnologia SA dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnDesenvolvidoporPositivoTecnologiaSA:bvrV1.09.X:bd07/15/2019:svnPositivoTecnologiaSA:pnN1240:pvrTobefilledbyO.E.M.:rvnPositivoTecnologiaSA:rnN14DP6:rvr11139547:cvnPositivoTecnologiaSA:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: MASTER dmi.product.name: N1240 dmi.product.sku: 3052532 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Positivo Tecnologia SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876741] Re: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed
I was able to get LightDM (or GDM) with hybrid graphics only by manually specifying an /etc/X11/xorg.conf file like follows (I generated it with nvidia-xconfig and then made manual modifications following this [1]): # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 440.64 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 1650 with Max-Q Design" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "Device1" Driver "intel" VendorName "Intel" BusID "PCI:0@0:2:0" Option "AccelMethod" "SNA" EndSection Section "Screen" Identifier "Screen1" Device "Device1" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "AllowEmptyInitialConfiguration" "True" SubSection "Display" Depth 24 EndSubSection EndSection Are you using a similar configuration for X or it just works for you out of the box? About the BIOS, I checked and "Set Optimized" was Disable for me, turning it to Enable seems to make me able to reboot with a Thunderbolt adapter connected to the port. Many thanks for your help! [1] https://gist.github.com/alexlee-gk/76a409f62a53883971a18a11af93241b -- 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/1876741 Title: Lenovo X1 boot crash with HDMI cable attached and laptop lid closed Status in linux package in Ubuntu: Confirmed Bug description: Hey everyone, just upgraded to 20.04 in my Lenovo X1 Carbon laptop and found myself in really big troubles. I always started my laptop pressing the power button and then closing the laptop lid, because I'm using an external HDMI display. This worked always well with Ubuntu 19.10. With 20.04 the system crash. These are the actions that reproduce the problem: 1 - Boot the system, pressing the power button and closing the laptop lid with an external HDMI display attached to the laptop; 2 - See on the external HDMI display the boot progress: BIOS loading and then grub not appearing; 3 - Listen to the fans that are about to make the laptop lift; 4 - Press the power button to force off the laptop; At this point the only way to have everything back is: 1 - Detach any external device; 2 - Detach the power cable; 3 - Wait 3 seconds or more; 4 - Open the laptop lid; 5 - Attach the power cable; 6 - Press the power button; Without doing exactly as I written the laptop will not boot up, even if I force power off, after starting it again, after the BIOS display, the screen goes blank and the fans lift. NOTE 1: I already disabled secure boot in the BIOS, and also selected discrete graphics for the display (otherwise I'm not able to even start X); NOTE 2: the scenario is exactly the same with nvidia-driver-435 and nvidia-driver-440; NOTE 3: if I leave the laptop lid open, everything is just fine; ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rasca 2750 F pulseaudio /dev/snd/controlC1: rasca 2750 F pulseaudio /dev/snd/controlC0: rasca 2750 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 16:24:47 2020 InstallationDate: Installed on 2019-12-10 (146 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QVCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=c61df9cc-bd36-4ed2-8f52-de114bbf3fc3 ro rd.driver.blacklist=nouveau RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backpor
[Kernel-packages] [Bug 1874056] s390/pci: removes wrong PCI multifunction assignment
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:43 EDT--- ** Attachment added: "s390/pci: removes wrong PCI multifunction assignment" https://bugs.launchpad.net/bugs/1874056/+attachment/5371400/+files/0012-s390-pci-removes-wrong-PCI-multifunction-assignment.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: Do not disable PF when VFs exist
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:42 EDT--- ** Attachment added: "s390/pci: Do not disable PF when VFs exist" https://bugs.launchpad.net/bugs/1874056/+attachment/5371398/+files/0010-s390-pci-Do-not-disable-PF-when-VFs-exist.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: define kernel parameters for PCI multifunction
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:39 EDT--- ** Attachment added: "s390/pci: define kernel parameters for PCI multifunction" https://bugs.launchpad.net/bugs/1874056/+attachment/5371393/+files/0005-s390-pci-define-kernel-parameters-for-PCI-multifunct.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: adapt events for zbus
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:41 EDT--- ** Attachment added: "s390/pci: adapt events for zbus" https://bugs.launchpad.net/bugs/1874056/+attachment/5371396/+files/0008-s390-pci-adapt-events-for-zbus.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: Handling multifunctions
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:42 EDT--- ** Attachment added: "s390/pci: Handling multifunctions" https://bugs.launchpad.net/bugs/1874056/+attachment/5371397/+files/0009-s390-pci-Handling-multifunctions.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: define RID and RID available
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:40 EDT--- ** Attachment added: "s390/pci: define RID and RID available" https://bugs.launchpad.net/bugs/1874056/+attachment/5371394/+files/0006-s390-pci-define-RID-and-RID-available.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: create zPCI bus
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:41 EDT--- ** Attachment added: "s390/pci: create zPCI bus" https://bugs.launchpad.net/bugs/1874056/+attachment/5371395/+files/0007-s390-pci-create-zPCI-bus.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] s390/pci: Documentation for zPCI
--- Comment (attachment only) From niklas.schne...@ibm.com 2020-05-14 04:43 EDT--- ** Attachment added: "s390/pci: Documentation for zPCI" https://bugs.launchpad.net/bugs/1874056/+attachment/5371399/+files/0011-s390-pci-Documentation-for-zPCI.patch -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] [NEW] very slow boot with new kernel 5.3.0-51
Public bug reported: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel-bug-files.tar.gz" https://bugs.launchpad.net/bugs/1878574/+attachment/5371401/+files/kernel-bug-files.tar.gz -- 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/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: New Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
** Changed in: linux (Baltix) Milestone: None => baltix-18.04 ** Changed in: linux (Baltix) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux package in Baltix: In Progress Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 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.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 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-restri
[Kernel-packages] [Bug 1878421] Re: I can see a cursor but no windows on the external monitor
This also looks relevant: [13.791] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support ** Summary changed: - I can see a cursor but no windows on the external monitor + Using two GPUs with one monitor each, one is always black ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/182 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: multigpu -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
https://bugzilla.redhat.com/show_bug.cgi?id=1785972 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/?id=0df9433fcae02215c8fd79690c134d535c7bb905 (landed in v5.7-rc3) ** Bug watch added: Red Hat Bugzilla #1785972 https://bugzilla.redhat.com/show_bug.cgi?id=1785972 -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877461] Re: Bionic update: upstream stable patchset 2020-05-07
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877461 Title: Bionic update: upstream stable patchset 2020-05-07 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-07 Ported from the following upstream stable releases: v4.14.178, v4.19.119 from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files net: ipv4: avoid unused variable warning for sysctl drm/msm: Use the correct dma_sync calls harder crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static vti4: removed duplicate log message. watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement scsi: iscsi: Report unbind session event when the target has been removed ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index s390/cio: avoid duplicated 'ADD' uevents pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address PCI/ASPM: Allow re-enabling Clock PM mm, slub: restore the original intention of prefetch_freepointer() cxgb4: fix large delays in PTP synchronization ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() net: bcmgenet: correct per TX/RX ring statistics net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net/x25: Fix x25_neigh refcnt leak when receiving frame tcp: cache line align MAX_TCP_HEADER team: fix hang in team_mode_get() net: dsa: b53: Fix ARL register definitions xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish vrf: Check skb for XFRM_TRANSFORMED flag KEYS: Avoid false positive ENOMEM error on key read ALSA: hda: Remove ASUS ROG Zenith from the blacklist iio: adc: stm32-adc: fix sleep in atomic context iio: xilinx-xadc: Fix ADC-B powerdown iio: xilinx-xadc: Fix clearing interrupt when enabling trigger iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode fs/namespace.c: fix mountpoint reference counter race USB: sisusbvga: Change port variable from signed to unsigned USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE USB: early: Handle AMD's spec-compliant identifiers, too USB: core: Fix free-while-in-use bug in the USB S-Glibrary USB: hub: Fix handling of connect changes during sleep overflow.h: Add arithmetic shift helper vmalloc: fix remap_vmalloc_range() bounds checks mm/hugetlb: fix a addressing exception caused by huge_pte_offset mm/ksm: fix NULL pointer dereference when KSM zero page is enabled tools/vm: fix cross-compile build ALSA: usx2y: Fix potential NULL dereference ALSA: hda/realtek - Add new codec supported for ALC245 ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices tpm/tpm_tis: Free IRQ if probing fails tpm: ibmvtpm: retry on H_CLOSED in tpm_ibmvtpm_send() KVM: Check validity of resolved slot when searching memslots KVM: VMX: Enable machine check support for 32bit targets tty: hvc: fix buffer overflow during hvc_alloc(). tty: rocket, avoid OOB access usb-storage: Add unusual_devs entry for JMicron JMS566 audit: check the length of userspace generated audit records ASoC: dapm: fixup dapm kcontrol widget iwlwifi: pcie: actually release queue memory in TVQM ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y powerpc/setup_64: Set cache-line-size based on cache-block-size staging: comedi: dt2815: fix writing hi byte of analog output staging: comedi: Fix comedi_device refcnt leak in comedi_open vt: don't hardcode the mem allocation upper bound staging: vt6656: Don't set RCR_MU
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
** Changed in: linux (Ubuntu) Assignee: (unassigned) => koba (kobako) -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878256] Re: Bionic update: upstream stable patchset 2020-05-12
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878256 Title: Bionic update: upstream stable patchset 2020-05-12 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-12 Ported from the following upstream stable releases: v4.14.179, v4.19.120, v4.19.121 from git://git.kernel.org/ drm/edid: Fix off-by-one in DispID DTD pixel clock drm/qxl: qxl_release leak in qxl_draw_dirty_fb() drm/qxl: qxl_release leak in qxl_hw_surface_alloc() drm/qxl: qxl_release use after free btrfs: fix block group leak when removing fails btrfs: fix partial loss of prealloc extent past i_size after fsync mmc: sdhci-xenon: fix annoying 1.8V regulator warning mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter ALSA: hda/hdmi: fix without unlocked before return ALSA: pcm: oss: Place the plugin buffer overflow checks correctly PM: ACPI: Output correct message on target power state PM: hibernate: Freeze kernel threads in software_resume() dm verity fec: fix hash block number in verity_fec_decode RDMA/mlx5: Set GRH fields in query QP on RoCE RDMA/mlx4: Initialize ib_spec on the stack vfio: avoid possible overflow in vfio_iommu_type1_pin_pages vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() iommu/qcom: Fix local_base status check scsi: target/iblock: fix WRITE SAME zeroing iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system ALSA: opti9xx: shut up gcc-10 range warning nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl dmaengine: dmatest: Fix iteration non-stop logic selinux: properly handle multiple messages in selinux_netlink_send() ASoC: tas571x: disable regulators on failed probe ASoC: wm8960: Fix wrong clock after suspend & resume rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket xfs: acquire superblock freeze protection on eofblocks scans cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled net: fec: set GPR bit on suspend by DT configuration. ALSA: hda: Keep the controller initialization even if no codecs found ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported ALSA: hda: call runtime_allow() for all hda controllers scsi: qla2xxx: check UNLOADING before posting async work RDMA/core: Fix race between destroy and release FD object btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info mmc: sdhci-msm: Enable host capabilities pertains to R1b response mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY mmc: meson-mx-sdio: remove the broken ->card_busy() op UBUNTU: upstream stable to v4.14.179, v4.19.121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875506] Re: Bionic update: upstream stable patchset 2020-04-27
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875506 Title: Bionic update: upstream stable patchset 2020-04-27 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-04-27 Ported from the following upstream stable releases: v4.14.177, v4.19.117 v4.19.118 from git://git.kernel.org/ KVM: VMX: fix crash cleanup when KVM wasn't used amd-xgbe: Use __napi_schedule() in BH context hsr: check protocol version in hsr_newlink() net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin net: ipv6: do not consider routes via gateways for anycast address check net: qrtr: send msgs from local of same id as broadcast net: revert default NAPI poll timeout to 2 jiffies net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic jbd2: improve comments about freeing data buffers whose page mapping is NULL pwm: pca9685: Fix PWM/GPIO inter-operation ext4: fix incorrect group count in ext4_fill_super error message ext4: fix incorrect inodes per group in error message ASoC: Intel: mrfld: fix incorrect check on p->sink ASoC: Intel: mrfld: return error codes when an error occurs ALSA: usb-audio: Don't override ignore_ctl_error value from the map tracing: Fix the race between registering 'snapshot' event trigger and triggering 'snapshot' operation btrfs: check commit root generation in should_ignore_root mac80211_hwsim: Use kstrndup() in place of kasprintf() ext4: do not zeroout extents beyond i_disksize dm flakey: check for null arg_name in parse_features() kvm: x86: Host feature SSBD doesn't imply guest feature SPEC_CTRL_SSBD x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE x86/intel_rdt: Add two new resources for L2 Code and Data Prioritization (CDP) x86/intel_rdt: Enable L2 CDP in MSR IA32_L2_QOS_CFG x86/resctrl: Preserve CDP enable over CPU hotplug x86/resctrl: Fix invalid attempt at removing the default resource group mm/vmalloc.c: move 'area->pages' after if statement objtool: Fix switch table detection in .text.unlikely scsi: sg: add sg_remove_request in sg_common_write ext4: use non-movable memory for superblock readahead arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0 netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type irqchip/mbigen: Free msi_desc on device teardown ALSA: hda: Don't release card at firmware loading error lib/raid6: use vdupq_n_u8 to avoid endianness warnings video: fbdev: sis: Remove unnecessary parentheses and commented code drm: NULL pointer dereference [null-pointer-deref] (CWE 476) problem clk: Fix debugfs_create_*() usage Revert "gpio: set up initial state from .get_direction()" wil6210: increase firmware ready timeout wil6210: fix temperature debugfs scsi: ufs: make sure all interrupts are processed scsi: ufs: ufs-qcom: remove broken hci version quirk wil6210: rate limit wil_rx_refill error rpmsg: glink: use put_device() if device_register fail rtc: pm8xxx: Fix issue in RTC write path rpmsg: glink: Fix missing mutex_init() in qcom_glink_alloc_channel() rpmsg: glink: smem: Ensure ordering during tx wil6210: fix PCIe bus mastering in case of interface down wil6210: add block size checks during FW load wil6210: fix length check in __wmi_send wil6210: abort properly in cfg suspend rbd: avoid a deadlock on header_rwsem when flushing notifies rbd: call rbd_dev_unprobe() after unwatching and flushing notifies of: unittest: kmemleak in of_unittest_platform_populate() clk: at91: usb: continue if clk_hw_round_rate() return zero power: supply: bq27xxx_battery: Silence deferred-probe error clk: tegra: Fix Tegra PMC clock out parents soc: imx: gpc: fix power up sequencing rtc: 88pm860x: fix possible race condition NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid() NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails s390/cpuinfo: fix wrong output when CPU0 is offline powerpc/maple: Fix declaration made after definition ext4: do not commit super on read-only bdev include/linux/swapops.h: correct gu
[Kernel-packages] [Bug 1878544] Re: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub)
Aforementioned commit is meant to fix 5f54a85db5df ("usb: typec: Make sure an alt mode exist before getting its partner"), which was landed in v5.2, so this should affects E/F/G/OEM-5.6. -- 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/1878544 Title: kernel NULL pointer dereference when plugging/unpluggin USB-c (power or hub) Status in linux package in Ubuntu: Confirmed Bug description: Asus Zenbook Flip S (UX-370UAR). Intel Core i7-8550U CPU). The X freezes and doesnt even allow to start a console session. Only happening on Ubuntu 18.04 and 20.04. Does not happen in the same computer under Ubuntu 16.04 or Windows 10. Can be replicated easily. Every time I plug/unplug the power USB-C or the USB-c hub. Mostly, on any interaction with the USB-c or I/O ports. If I plug/unplug the USB-c without X in a console session (CTRL+ALT+F3) I get the following: BUG: kernel NULL point dereference, address: 0080 ... Workqueue: events ucsi_connector_change [typec_usci] RIP: 0010:ucsi_displayport_remove_partner+0xe/0x30 [typec_usci] ... Find a picture of the full error attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vks20 1808 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 23:46:49 2020 InstallationDate: Installed on 2020-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. UX370UAR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=acc6d87c-574b-4c1e-8e8f-e75c1e9ff1fc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.311:bd10/15/2019:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX370UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875660] Re: Focal update: v5.4.35 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875660 Title: Focal update: v5.4.35 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.35 upstream stable release from git://git.kernel.org/ ext4: use non-movable memory for superblock readahead watchdog: sp805: fix restart handler xsk: Fix out of boundary write in __xsk_rcv_memcpy arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0 arm, bpf: Fix offset overflow for BPF_MEM BPF_DW objtool: Fix switch table detection in .text.unlikely scsi: sg: add sg_remove_request in sg_common_write ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN. kbuild, btf: Fix dependencies for DEBUG_INFO_BTF netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type irqchip/mbigen: Free msi_desc on device teardown ALSA: hda: Don't release card at firmware loading error xsk: Add missing check on user supplied headroom size of: unittest: kmemleak on changeset destroy of: unittest: kmemleak in of_unittest_platform_populate() of: unittest: kmemleak in of_unittest_overlay_high_level() of: overlay: kmemleak in dup_and_fixup_symbol_prop() x86/Hyper-V: Unload vmbus channel in hv panic callback x86/Hyper-V: Trigger crash enlightenment only once during system crash. x86/Hyper-V: Report crash register data or kmsg before running crash kernel x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not set x86/Hyper-V: Report crash data in die() when panic_on_oops is set afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus() afs: Fix decoding of inline abort codes from version 1 status records afs: Fix rename operation status delivery afs: Fix afs_d_validate() to set the right directory version afs: Fix race between post-modification dir edit and readdir/d_revalidate block, bfq: turn put_queue into release_process_ref in __bfq_bic_change_cgroup block, bfq: make reparent_leaf_entity actually work only on leaf entities block, bfq: invoke flush_idle_tree after reparent_active_queues in pd_offline rbd: avoid a deadlock on header_rwsem when flushing notifies rbd: call rbd_dev_unprobe() after unwatching and flushing notifies x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump drm/ttm: flush the fence on the bo after we individualize the reservation object clk: Don't cache errors from clk_ops::get_phase() clk: at91: usb: continue if clk_hw_round_rate() return zero net/mlx5e: Enforce setting of a single FEC mode f2fs: fix the panic in do_checkpoint() ARM: dts: rockchip: fix vqmmc-supply property name for rk3188-bqedison2qc arm64: dts: allwinner: a64: Fix display clock register range power: supply: bq27xxx_battery: Silence deferred-probe error clk: tegra: Fix Tegra PMC clock out parents arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194 arm64: tegra: Fix Tegra194 PCIe compatible string arm64: dts: clearfog-gt-8k: set gigabit PHY reset deassert delay soc: imx: gpc: fix power up sequencing dma-coherent: fix integer overflow in the reserved-memory dma allocation rtc: 88pm860x: fix possible race condition NFS: alloc_nfs_open_context() must use the file cred when available NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid() NFSv4.2: error out when relink swapfile ARM: dts: rockchip: fix lvds-encoder ports subnode for rk3188-bqedison2qc KVM: PPC: Book3S HV: Fix H_CEDE return code for nested guests f2fs: fix to show norecovery mount option phy: uniphier-usb3ss: Add Pro5 support NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails f2fs: Fix mount failure due to SPO after a successful online resize FS f2fs: Add a new CP flag to help fsck fix resize SPO issues s390/cpuinfo: fix wrong output when CPU0 is offline hibernate: Allow uswsusp to write to swap btrfs: add RCU locks around block group initialization powerpc/prom_init: Pass the "os-term" message to hypervisor powerpc/maple: Fix declaration made after definition s390/cpum_sf: Fix wrong page count in error message ext4: do not commit super on read-only bdev um: ubd: Prevent
[Kernel-packages] [Bug 1876361] Re: Focal update: v5.4.36 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876361 Title: Focal update: v5.4.36 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.36 upstream stable release from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files f2fs: fix to avoid memory leakage in f2fs_listxattr net, ip_tunnel: fix interface lookup with no key UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Silence clang warning on mismatched value/register sizes tools/testing/nvdimm: Fix compilation failure without CONFIG_DEV_DAX_PMEM_COMPAT watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login scsi: lpfc: Fix crash after handling a pci error scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG scsi: libfc: If PRLI rejected, move rport to PLOGI state ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement nvme-tcp: fix possible crash in write_zeroes processing scsi: iscsi: Report unbind session event when the target has been removed tools/test/nvdimm: Fix out of tree build ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() nvme: fix deadlock caused by ANA update wrong locking drm/amd/display: Update stream adjust in dc_stream_adjust_vmin_vmax dma-direct: fix data truncation in dma_direct_get_required_mask() kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index kconfig: qconf: Fix a few alignment issues lib/raid6/test: fix build on distros whose /bin/sh is not bash s390/cio: generate delayed uevent for vfio-ccw subchannels s390/cio: avoid duplicated 'ADD' uevents loop: Better discard support for block devices Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" powerpc/pseries: Fix MCE handling on pseries nvme: fix compat address handling in several ioctls pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address drm/amd/display: Calculate scaling ratios on every medium/full update ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet ALSA: usb-audio: Add Pioneer DJ DJM-250MK2 quirk drm/amd/display: Not doing optimize bandwidth if flip pending. cxgb4: fix adapter crash due to wrong MC size cxgb4: fix large delays in PTP synchronization ipv4: Update fib_select_default to handle nexthop objects ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() mlxsw: Fix some IS_ERR() vs NULL bugs net: bcmgenet: correct per TX/RX ring statistics net/mlx4_en: avoid indirect call in TX completion net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net: openvswitch: ovs_ct_exit to be done under ovs_lock net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array net/x25: Fix x25_neigh refcnt leak when receiving frame sched: etf: do not assume all sockets are full blown selftests: Fix suppress test in fib_tests.sh tcp: cache line align MAX_TCP_HEADER team: fix hang in team_mode_get() vrf: Fix IPv6 with qdisc and xfrm net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled net: dsa: b53: Fix valid setting for MDB entries net: dsa: b53: Fix ARL register definitions net: dsa: b53: Rework ARL bin logic net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL vxlan: use the correct nlattr array in NL_SET_ERR_MSG_ATTR geneve: use the correct nlattr array in NL_SET_ERR_MSG_ATTR xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish vrf: Check skb for XFRM_TRANSFORMED flag KEYS: Avoid false positive ENOMEM error on key read ALSA: hda: Remove ASUS R
[Kernel-packages] [Bug 1878574] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1878574 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Incomplete Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] Re: very slow boot with new kernel 5.3.0-51
apport information ** Tags added: apport-collected bionic ** Description changed: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. - I attach several files, tarred because you do not seem to provide the - facility to attach more then one file. There are a copy of the current - fstab, the output of hwinfo (taken with kernel v.51) and for each of the - two kernels the data asked for on the Ubuntu website. + I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: david 2069 F pulseaudio + /dev/snd/controlC0: david 2069 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-01-05 (129 days ago) + InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + eno1 no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-51-generic N/A + linux-backports-modules-5.3.0-51-generic N/A + linux-firmware1.173.18 + RfKill: + + Tags: bionic + Uname: Linux 5.3.0-51-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/22/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F41 + dmi.board.asset.tag: Default string + dmi.board.name: B450 AORUS M + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: B450 AORUS M + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371411/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will con
[Kernel-packages] [Bug 1878574] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371413/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371424/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371423/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371412/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371421/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371419/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371418/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371417/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371414/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371416/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371422/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878574] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1878574/+attachment/5371420/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878574 Title: very slow boot with new kernel 5.3.0-51 Status in linux package in Ubuntu: Confirmed Bug description: I already reported the but using "ubuntu-bug linux" but could see nowhere to tell you what the problem actually was. In summary it is relatively new system, 18.04.4LTS 64bit and Maté 1.20.1 dual-booting with Windows 10 v.1909, built on a Gigabyte Aorus B450M mainboard, Ryzen 5 3400G with Radeon Vega Graphics × 8, Kingston A2000 M2 main drive and a supplementary 4TB data drive. A wired connexion to BT Hub 6 via BT Powerline is used and gives no trouble on any other system. The system started with kernel 5.3.0-46 generic and was fine for a few months, booting in a few seconds. A couple of days ago the kernel upgraded itself to 5.3.0-51 generic and boot immediately became a minute or more. Reverting to kernel 5.3.0-46 generic restores the fast boot time. I can continue like this for a while but my main fear is that when the LTS update to 20.04 arrives the new kernel will contain the bug and reversion to 5.3.0-46 will no longer be possible. I attach several files, tarred because you do not seem to provide the facility to attach more then one file. There are a copy of the current fstab, the output of hwinfo (taken with kernel v.51) and for each of the two kernels the data asked for on the Ubuntu website. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2069 F pulseaudio /dev/snd/controlC0: david 2069 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-05 (129 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=ea9bdbd1-0964-411e-b2c3-45fad2b77eae ro quiet splash fastboot vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B450 AORUS M dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF41:bd07/22/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 AORUS M dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876765] Re: Focal update: v5.4.37 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876765 Title: Focal update: v5.4.37 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.37 upstream stable release from git://git.kernel.org/ remoteproc: Fix wrong rvring index computation ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() printk: queue wake_up_klogd irq_work only if per-CPU areas are ready ASoC: stm32: sai: fix sai probe usb: dwc3: gadget: Do link recovery for SS and SSP kbuild: fix DT binding schema rule again to avoid needless rebuilds usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete usb: gadget: udc: atmel: Fix vbus disconnect handling afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH iio:ad7797: Use correct attribute_group propagate_one(): mnt_set_mountpoint() needs mount_lock counter: 104-quad-8: Add lock guards - generic interface s390/ftrace: fix potential crashes when switching tracers ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs ASoC: tas571x: disable regulators on failed probe ASoC: wm8960: Fix wrong clock after suspend & resume drivers: soc: xilinx: fix firmware driver Kconfig dependency nfsd: memory corruption in nfsd4_lock() bpf: Forbid XADD on spilled pointers for unprivileged users i2c: altera: use proper variable to hold errno rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket net/cxgb4: Check the return from t4_query_params properly xfs: acquire superblock freeze protection on eofblocks scans svcrdma: Fix trace point use-after-free race svcrdma: Fix leak of svc_rdma_recv_ctxt objects net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns net/mlx5e: Get the latest values from counters in switchdev mode PCI: Add ACS quirk for Zhaoxin multi-function devices PCI: Make ACS quirk implementations more uniform PCI: Unify ACS quirk desired vs provided checking PCI: Add Zhaoxin Vendor ID PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports PCI: Move Apex Edge TPU class quirk to fix BAR assignment ARM: dts: bcm283x: Disable dsi0 node cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled s390/pci: do not set affinity for floating irqs net/mlx5: Fix failing fw tracer allocation on s390 sched/core: Fix reset-on-fork from RT with uclamp perf/core: fix parent pid/tid in task exit events netfilter: nat: fix error handling upon registering inet hook PM: sleep: core: Switch back to async_schedule_dev() blk-iocost: Fix error on iocost_ioc_vrate_adj um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/ bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension bpf, x86_32: Fix clobbering of dst for BPF_JSET bpf, x86_32: Fix logic error in BPF_LDX zero-extension mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path xfs: clear PF_MEMALLOC before exiting xfsaild thread bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B libbpf: Initialize *nl_pid so gcc 10 is happy net: fec: set GPR bit on suspend by DT configuration. x86: hyperv: report value of misc_features signal: check sig before setting info in kill_pid_usb_asyncio afs: Fix length of dump of bad YFSFetchStatus record xfs: fix partially uninitialized structure in xfs_reflink_remap_extent ALSA: hda: Release resources at error in delayed probe ALSA: hda: Keep the controller initialization even if no codecs found ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported scsi: target: fix PR IN / READ FULL STATUS for FC scsi: target: tcmu: reset_ring should reset TCMU_DEV_BIT_BROKEN objtool: Fix CONFIG_UBSAN_TRAP unreachable warnings objtool: Support Clang non-section symbols in ORC dump xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status ALSA: hda: call runtime_allow() for all hda controllers net: stmmac: socfpga: Allow all RGMII modes mac80211: fix channel switch trigger from unknown mesh peer arm64: Delete the space separator in __emit_inst ext4: use matching invalidatepage in ext4_writepage ext4: increase wait time needed before reuse of
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
** Description changed: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] - The commit is from + This commit is derivated from below commit, and then modified and provided + by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. -- 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/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878479] Re: HP-OMEN 17t bc0xxx don't work sound and microphone
*** This bug is a duplicate of bug 1874698 *** https://bugs.launchpad.net/bugs/1874698 for linux-modules-extra-5.4.0-26-generic_5.4.0-26.30+skipv4_amd64.deb sound is worked but not worked second 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/1878479 Title: HP-OMEN 17t bc0xxx don't work sound and microphone Status in linux package in Ubuntu: Incomplete Bug description: This problem has been resolved for kernel 5.7. * https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it because I have more problems with the constant relogin https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193 How to solve this problem with kernel trust supported by ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877592] Re: Focal update: v5.4.39 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877592 Title: Focal update: v5.4.39 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.39 upstream stable release from git://git.kernel.org/ dma-buf: Fix SET_NAME ioctl uapi drm/edid: Fix off-by-one in DispID DTD pixel clock drm/amd/display: Fix green screen issue after suspend drm/qxl: qxl_release leak in qxl_draw_dirty_fb() drm/qxl: qxl_release leak in qxl_hw_surface_alloc() drm/qxl: qxl_release use after free NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION btrfs: fix transaction leak in btrfs_recover_relocation btrfs: fix block group leak when removing fails btrfs: fix partial loss of prealloc extent past i_size after fsync btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info mmc: cqhci: Avoid false "cqhci: CQE stuck on" by not open-coding timeout loop mmc: sdhci-xenon: fix annoying 1.8V regulator warning mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers mmc: sdhci-msm: Enable host capabilities pertains to R1b response mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY mmc: meson-mx-sdio: remove the broken ->card_busy() op crypto: caam - fix the address of the last entry of S/G ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID ALSA: hda/hdmi: fix without unlocked before return ALSA: line6: Fix POD HD500 audio playback ALSA: pcm: oss: Place the plugin buffer overflow checks correctly i2c: amd-mp2-pci: Fix Oops in amd_mp2_pci_init() error handling Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM dlmfs_file_write(): fix the bogosity in handling non-zero *ppos IB/rdmavt: Always return ERR_PTR from rvt_create_mmap_info() PM: ACPI: Output correct message on target power state PM: hibernate: Freeze kernel threads in software_resume() dm verity fec: fix hash block number in verity_fec_decode dm writecache: fix data corruption when reloading the target dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe scsi: qla2xxx: set UNLOADING before waiting for session deletion scsi: qla2xxx: check UNLOADING before posting async work RDMA/mlx5: Set GRH fields in query QP on RoCE RDMA/mlx4: Initialize ib_spec on the stack RDMA/siw: Fix potential siw_mem refcnt leak in siw_fastreg_mr() RDMA/core: Prevent mixed use of FDs between shared ufiles RDMA/core: Fix race between destroy and release FD object RDMA/cm: Fix ordering of xa_alloc_cyclic() in ib_create_cm_id() RDMA/cm: Fix an error check in cm_alloc_id_priv() i2c: iproc: generate stop event for slave writes vfio: avoid possible overflow in vfio_iommu_type1_pin_pages vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() iommu/qcom: Fix local_base status check scsi: target/iblock: fix WRITE SAME zeroing iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system i2c: aspeed: Avoid i2c interrupt status clear race condition. ALSA: opti9xx: shut up gcc-10 range warning Fix use after free in get_tree_bdev() nvme: prevent double free in nvme_alloc_ns() error handling nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl dmaengine: dmatest: Fix iteration non-stop logic dmaengine: dmatest: Fix process hang when reading 'wait' parameter arm64: vdso: Add -fasynchronous-unwind-tables to cflags selinux: properly handle multiple messages in selinux_netlink_send() Linux 5.4.39 UBUNTU: upstream stable to v5.4.39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876767] Re: Focal update: v5.4.38 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876767 Title: Focal update: v5.4.38 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.38 upstream stable release from git://git.kernel.org/ Note: v5.4.38 itself consisted of a single revert (never committed to Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug, really. Linux 5.4.38 UBUNTU: upstream stable to v5.4.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
dmesg looks clean so far, intel card (internal display) is fb0 and nvidia-card for hdmi (external 4k monitor hp 27f) $ dmesg | grep frame [0.882504] efifb: framebuffer at 0x8000, using 8100k, total 8100k [0.882611] Console: switching to colour frame buffer device 240x67 [0.887919] fb0: EFI VGA frame buffer device [1.392526] r8169 :03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [3.605988] Console: switching to colour frame buffer device 240x67 [3.633864] i915 :00:02.0: fb0: i915drmfb frame buffer device [3.718640] nouveau :01:00.0: fb1: nouveaudrmfb frame buffer device see full dmesg in attachment strange is that i have no X.org.log in /var/log, anything i can try to workaround/test for affected Package? noticed, that on login-screen the background of external monitor is purple and switches to black (default color without background-image) ** Attachment added: "dmesg after starting with 2nd gpu enabled" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878421/+attachment/5371457/+files/dmesg_multigpu.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions
[Kernel-packages] [Bug 1878432] Re: rpi3a+ does not boot with core20
dtoverlay=vc4-fkms-v3d,cma-256 Telling the kernel to allocate/reserve 256MB of contiguous memory for DMA operations is not a sensible thing to do on a device that only has 512MB of memory available. ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1878432 Title: rpi3a+ does not boot with core20 Status in pi2-kernel-snap: New Status in snapd: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Invalid Bug description: MMC: mmc@7e202000: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment RPI3a+ on core 20 from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200513.2/ (also tested the previous - 20200512.3) are not booting. This is for both arm64 and armhf. This is the serial log for as far as it gets: In:serial Out: serial Err: serial Net: No ethernet found. starting USB... Bus usb@7e98: scanning bus usb@7e98 for devices... 5 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found ## Warning: Input data exceeds 1048576 bytes - truncated ## Info: input data size = 1048578 = 0x12 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4638 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 0240 4096 bytes read in 3 ms (1.3 MiB/s) 8378005 bytes read in 363 ms (22 MiB/s) Total of 1 halfword(s) were the same Decompressing kernel... Uncompressed size: 25905664 = 0x18B4A00 33637043 bytes read in 1448 ms (22.2 MiB/s) Booting Ubuntu (with booti) from mmc 0:... ## Flattened Device Tree blob at 0260 Booting using the fdt blob at 0x260 Using Device Tree in place at 0260, end 0260a065 Starting kernel ... To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
If you now have "2nd gpu enabled" then please run: journalctl -b0 > journal.txt and attach the resulting text file. -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
** Description changed: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. + + The i2c/smbus currently only support to access data with 8-bit width of + address. In some larger device, such as larger EEPROM, it requires to + access the address large than 0xff, so it needs to extend address space + to 16-bit width. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. + The i2c/smbus currently only support to access data with 8-bit width of + address. In some larger device, such as larger EEPROM, it requires to + access the address large than 0xff, so it needs to extend address space + to 16-bit width. + [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. -- 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/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878098] Re: Xenial update: 4.4.221 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878098 Title: Xenial update: 4.4.221 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.221 upstream stable release from git://git.kernel.org/ The following patches from the 4.4.221 stable release shall be applied: * ext4: fix extent_status fragmentation for plain files * ALSA: hda - Fix incorrect usage of IS_REACHABLE() * net: ipv4: emulate READ_ONCE() on ->hdrincl bit-field in raw_sendmsg() * net: ipv4: avoid unused variable warning for sysctl * crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static * vti4: removed duplicate log message. * scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login * ceph: return ceph_mdsc_do_request() errors from __get_parent() * ceph: don't skip updating wanted caps when cap is stale * pwm: rcar: Fix late Runtime PM enablement * scsi: iscsi: Report unbind session event when the target has been removed * ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() * kernel/gcov/fs.c: gcov_seq_next() should increase position index * ipc/util.c: sysvipc_find_ipc() should increase position index * s390/cio: avoid duplicated 'ADD' uevents * pwm: renesas-tpu: Fix late Runtime PM enablement * pwm: bcm2835: Dynamically allocate base * ipv6: fix restrict IPV6_ADDRFORM operation * macvlan: fix null dereference in macvlan_device_event() * net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node * net/x25: Fix x25_neigh refcnt leak when receiving frame * tcp: cache line align MAX_TCP_HEADER * team: fix hang in team_mode_get() * xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish * ALSA: hda: Remove ASUS ROG Zenith from the blacklist * iio: xilinx-xadc: Fix ADC-B powerdown * iio: xilinx-xadc: Fix clearing interrupt when enabling trigger * iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode * fs/namespace.c: fix mountpoint reference counter race * USB: sisusbvga: Change port variable from signed to unsigned * USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE * drivers: usb: core: Don't disable irqs in usb_sg_wait() during URB submit. * drivers: usb: core: Minimize irq disabling in usb_sg_cancel() * USB: core: Fix free-while-in-use bug in the USB S-Glibrary * USB: hub: Fix handling of connect changes during sleep * ALSA: usx2y: Fix potential NULL dereference * ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif * ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices * KVM: Check validity of resolved slot when searching memslots * KVM: VMX: Enable machine check support for 32bit targets * tty: hvc: fix buffer overflow during hvc_alloc(). * tty: rocket, avoid OOB access * usb-storage: Add unusual_devs entry for JMicron JMS566 * audit: check the length of userspace generated audit records * ASoC: dapm: fixup dapm kcontrol widget * ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y * staging: comedi: dt2815: fix writing hi byte of analog output * staging: comedi: Fix comedi_device refcnt leak in comedi_open * staging: vt6656: Fix drivers TBTT timing counter. * staging: vt6656: Power save stop wake_up_count wrap around. * UAS: no use logging any details in case of ENODEV * UAS: fix deadlock in error handling and PM flushing work * usb: f_fs: Clear OS Extended descriptor counts to zero in ffs_data_reset() * remoteproc: Fix wrong rvring index computation * sctp: use right member as the param of list_for_each_entry * fuse: fix possibly missed wake-up after abort * mtd: cfi: fix deadloop in cfi_cmdset_0002.c do_write_buffer * usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete * net/cxgb4: Check the return from t4_query_params properly * perf/core: fix parent pid/tid in task exit events * bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B * scsi: target: fix PR IN / READ FULL STATUS for FC * xen/xenbus: ensure xenbus_map_ring_valloc() returns proper grant status * ext4: convert BUG_ON's to
[Kernel-packages] [Bug 1875905] Re: Xenial update: 4.4.220 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875905 Title: Xenial update: 4.4.220 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.220 upstream stable release from git://git.kernel.org/ The following patches from the 4.4.220 stable release shall be applied: * bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads * net: vxge: fix wrong __VA_ARGS__ usage * qlcnic: Fix bad kzalloc null test * i2c: st: fix missing struct parameter description * irqchip/versatile-fpga: Handle chained IRQs properly * selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault * libata: Remove extra scsi_host_put() in ata_scsi_add_hosts() * gfs2: Don't demote a glock until its revokes are written * x86/boot: Use unsigned comparison for addresses * locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps() * btrfs: remove a BUG_ON() from merge_reloc_roots() * btrfs: track reloc roots based on their commit root bytenr * misc: rtsx: set correct pcr_ops for rts522A * ASoC: fix regwmask * ASoC: dapm: connect virtual mux with default value * ASoC: dpcm: allow start or stop during pause for backend * ASoC: topology: use name_prefix for new kcontrol * usb: gadget: f_fs: Fix use after free issue as part of queue failure * usb: gadget: composite: Inform controller driver of self-powered * ALSA: usb-audio: Add mixer workaround for TRX40 and co * ALSA: hda: Add driver blacklist * ALSA: hda: Fix potential access overflow in beep helper * ALSA: ice1724: Fix invalid access for enumerated ctl items * ALSA: pcm: oss: Fix regression by buffer overflow fix * acpi/x86: ignore unspecified bit positions in the ACPI global lock field * thermal: devfreq_cooling: inline all stubs for CONFIG_DEVFREQ_THERMAL=n * KEYS: reaching the keys quotas correctly * irqchip/versatile-fpga: Apply clear-mask earlier * MIPS: OCTEON: irq: Fix potential NULL pointer dereference * ath9k: Handle txpower changes even when TPC is disabled * signal: Extend exec_id to 64bits * x86/entry/32: Add missing ASM_CLAC to general_protection entry * KVM: x86: Allocate new rmap and large page tracking when moving memslot * crypto: mxs-dcp - fix scatterlist linearization for hash * futex: futex_wake_op, do not fail on invalid op * xen-netfront: Rework the fix for Rx stall during OOM and network stress * ALSA: hda: Initialize power_state field properly * Btrfs: incremental send, fix invalid memory access * IB/ipoib: Fix lockdep issue found on ipoib_ib_dev_heavy_flush * scsi: zfcp: fix missing erp_lock in port recovery trigger for point-to-point * arm64: armv8_deprecated: Fix undef_hook mask for thumb setend * ext4: fix a data race at inode->i_blocks * ocfs2: no need try to truncate file beyond i_size * s390/diag: fix display of diagnose call statistics * Input: i8042 - add Acer Aspire 5738z to nomux list * kmod: make request_module() return an error when autoloading is disabled * hfsplus: fix crash and filesystem corruption when deleting files * libata: Return correct status in sata_pmp_eh_recover_pm() when ATA_DFLAG_DETACH is set * powerpc/64/tm: Don't let userspace set regs->trap via sigreturn * Btrfs: fix crash during unmount due to race with delayed inode workers * drm/dp_mst: Fix clearing payload state on topology disable * ipmi: fix hung processes in __get_guid() * powerpc/fsl_booke: Avoid creating duplicate tlb1 entry * misc: echo: Remove unnecessary parentheses and simplify check for zero * mfd: dln2: Fix sanity checking for endpoints * net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin * net: ipv6: do not consider routes via gateways for anycast address check * scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic * jbd2: improve comments about freeing data buffers whose page mapping is NULL * ext4: fix incorrect group count in ext4_fill_super error message * ext4: fix incorrect inodes per group in error message * ASoC: Intel: mrfld: fix incorrect check on p->sink * ASoC: Intel: mrfld: return error codes when an error occurs * ALSA: usb-audio: Don't override ignore_ctl_error value f
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
** Attachment added: "journalctl -b0" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1878421/+attachment/5371462/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878246] Re: Xenial update: 4.4.222 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878246 Title: Xenial update: 4.4.222 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.222 upstream stable release from git://git.kernel.org/ The following patches from the 4.4.222 stable release shall be applied: * ext4: fix special inode number checks in __ext4_iget() * drm/qxl: qxl_release leak in qxl_hw_surface_alloc() * ALSA: pcm: oss: Place the plugin buffer overflow checks correctly * PM: ACPI: Output correct message on target power state * RDMA/mlx4: Initialize ib_spec on the stack * vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() * ALSA: opti9xx: shut up gcc-10 range warning * nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl * dmaengine: dmatest: Fix iteration non-stop logic * i2c: designware-pci: use IRQF_COND_SUSPEND flag * perf hists: Fix HISTC_MEM_DCACHELINE width setting * powerpc/perf: Remove PPMU_HAS_SSLOT flag for Power8 * perf/x86: Fix uninitialized value usage * exynos4-is: fix a format string bug * ASoC: wm8960: Fix WM8960_SYSCLK_PLL mode * ASoC: imx-spdif: Fix crash on suspend * ipv6: use READ_ONCE() for inet->hdrincl as in ipv4 * selinux: properly handle multiple messages in selinux_netlink_send() * Linux 4.4.222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
after my laptop-screen goes off (automatic locking of workstation) and i retouched it to go on again, i see some flickering on the external monitor with background-image, but it looks like there was heavy load so that login-screen wasn't displayed (see also background on internal screen)...have now switched off external monitor to get login-window again...maybe this helps to get the issue nailed down -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878232] Re: Xenial update: 4.4.223 upstream stable release
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878232 Title: Xenial update: 4.4.223 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.223 upstream stable release from git://git.kernel.org/ The following patches from the 4.4.223 stable release shall be applied: * mwifiex: fix PCIe register information for 8997 chipset * drm/qxl: qxl_release use after free * drm/qxl: qxl_release leak in qxl_draw_dirty_fb() * staging: rtl8192u: Fix crash due to pointers being "confusing" * usb: gadget: f_acm: Fix configfs attr name * usb: gadged: pch_udc: get rid of redundant assignments * usb: gadget: pch_udc: reorder spin_[un]lock to avoid deadlock * usb: gadget: udc: core: don't starve DMA resources * MIPS: Fix macro typo * MIPS: ptrace: Drop cp0_tcstatus from regoffset_table[] * MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200 * MIPS: smp-cps: Stop printing EJTAG exceptions to UART * MIPS: scall: Handle seccomp filters which redirect syscalls * MIPS: BMIPS: BMIPS5000 has I cache filing from D cache * MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier * MIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache * MIPS: BMIPS: Pretty print BMIPS5200 processor name * MIPS: Fix HTW config on XPA kernel without LPA enabled * MIPS: BMIPS: Adjust mips-hpt-frequency for BCM7435 * MIPS: math-emu: Fix BC1{EQ,NE}Z emulation * MIPS: Fix BC1{EQ,NE}Z return offset calculation * MIPS: perf: Fix I6400 event numbers * MIPS: KVM: Fix translation of MFC0 ErrCtl * MIPS: SMP: Update cpu_foreign_map on CPU disable * MIPS: c-r4k: Fix protected_writeback_scache_line for EVA * MIPS: Octeon: Off by one in octeon_irq_gpio_map() * bpf, mips: fix off-by-one in ctx offset allocation * MIPS: RM7000: Double locking bug in rm7k_tc_disable() * MIPS: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO * mips/panic: replace smp_send_stop() with kdump friendly version in panic path * ARM: dts: armadillo800eva Correct extal1 frequency to 24 MHz * ARM: imx: select SRC for i.MX7 * ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wxl/wsxl * ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wvl/vl * ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wxl/wsxl * ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wvl/vl * ARM: dts: orion5x: gpio pin fixes for linkstation lswtgl * ARM: dts: orion5x: fix the missing mtd flash on linkstation lswtgl * ARM: dts: kirkwood: use unique machine name for ds112 * ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile * ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence * perf/x86: Fix filter_events() bug with event mappings * x86/LDT: Print the real LDT base address * x86/apic/uv: Silence a shift wrapping warning * ALSA: fm801: explicitly free IRQ line * ALSA: fm801: propagate TUNER_ONLY bit when autodetected * ALSA: fm801: detect FM-only card earlier * netfilter: nfnetlink: use original skbuff when acking batches * xfrm: fix crash in XFRM_MSG_GETSA netlink handler * mwifiex: fix IBSS data path issue. * mwifiex: add missing check for PCIe8997 chipset * iwlwifi: set max firmware version of 7265 to 17 * Bluetooth: btmrvl: fix hung task warning dump * dccp: limit sk_filter trim to payload * net/mlx4_core: Do not BUG_ON during reset when PCI is offline * mlxsw: pci: Correctly determine if descriptor queue is full * PCI: Supply CPU physical address (not bus address) to iomem_is_exclusive() * net/mlx4_core: Implement pci_resume callback * alpha/PCI: Call iomem_is_exclusive() for IORESOURCE_MEM, but not IORESOURCE_IO * vfio/pci: Allow VPD short read * brcmfmac: add eth_type_trans back for PCIe full dongle * mlxsw: Treat local port 64 as valid * IB/mlx4: Initialize hop_limit when creating address handle * ovs/gre,geneve: fix error path when creating an iface * GRE: Disable segmentation offloads w/ CSUM and we are encapsulated via FOU * powerpc/pci/of: Parse unassigned resources * firmware: actually return NULL on failed request_firmware_nowait() * c8sectpfe: Rework firmware loading mechanism * net/mlx5: Avoid passing dma address 0 to firmware * IB/mlx5: Fix RC transport send queue overhead computation * net/mlx5: Make comm
[Kernel-packages] [Bug 1876956] Re: Disco update: upstream stable patchset 2020-05-05
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876956 Title: Disco update: upstream stable patchset 2020-05-05 Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-05 Ported from the following upstream stable releases: v4.19.118, v5.4.35 from git://git.kernel.org/ arm, bpf: Fix offset overflow for BPF_MEM BPF_DW objtool: Fix switch table detection in .text.unlikely scsi: sg: add sg_remove_request in sg_common_write ext4: use non-movable memory for superblock readahead watchdog: sp805: fix restart handler arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0 ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN. netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type irqchip/mbigen: Free msi_desc on device teardown ALSA: hda: Don't release card at firmware loading error of: unittest: kmemleak on changeset destroy of: unittest: kmemleak in of_unittest_platform_populate() of: unittest: kmemleak in of_unittest_overlay_high_level() of: overlay: kmemleak in dup_and_fixup_symbol_prop() x86/Hyper-V: Report crash register data or kmsg before running crash kernel lib/raid6: use vdupq_n_u8 to avoid endianness warnings rbd: avoid a deadlock on header_rwsem when flushing notifies rbd: call rbd_dev_unprobe() after unwatching and flushing notifies xsk: Add missing check on user supplied headroom size x86/Hyper-V: Unload vmbus channel in hv panic callback x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump x86/Hyper-V: Trigger crash enlightenment only once during system crash. x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not set x86/Hyper-V: Report crash data in die() when panic_on_oops is set clk: at91: usb: continue if clk_hw_round_rate() return zero power: supply: bq27xxx_battery: Silence deferred-probe error clk: tegra: Fix Tegra PMC clock out parents soc: imx: gpc: fix power up sequencing rtc: 88pm860x: fix possible race condition NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid() NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails s390/cpuinfo: fix wrong output when CPU0 is offline powerpc/maple: Fix declaration made after definition s390/cpum_sf: Fix wrong page count in error message ext4: do not commit super on read-only bdev um: ubd: Prevent buffer overrun on command completion cifs: Allocate encryption header through kmalloc include/linux/swapops.h: correct guards for non_swap_entry() percpu_counter: fix a data race at vm_committed_as compiler.h: fix error in BUILD_BUG_ON() reporting KVM: s390: vsie: Fix possible race when shadowing region 3 tables x86: ACPI: fix CPU hotplug deadlock drm/amdkfd: kfree the wrong pointer NFS: Fix memory leaks in nfs_pageio_stop_mirroring() f2fs: fix NULL pointer dereference in f2fs_write_begin() drm/vc4: Fix HDMI mode validation iommu/vt-d: Fix mm reference leak ext2: fix empty body warnings when -Wextra is used ext2: fix debug reference to ext2_xattr_cache power: supply: axp288_fuel_gauge: Broaden vendor check for Intel Compute Sticks. libnvdimm: Out of bounds read in __nd_ioctl() iommu/amd: Fix the configuration of GCR3 table root pointer f2fs: fix to wait all node page writeback net: dsa: bcm_sf2: Fix overflow checks fbdev: potential information leak in do_fb_ioctl() iio: si1133: read 24-bit signed integer for measurement tty: evh_bytechan: Fix out of bounds accesses locktorture: Print ratio of acquisitions, not failures mtd: spinand: Explicitly use MTD_OPS_RAW to write the bad block marker to OOB mtd: lpddr: Fix a double free in probe() mtd: phram: fix a double free issue in error path KEYS: Don't write out to userspace while holding key semaphore bpf: fix buggy r0 retval refinement for tracing helpers ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus() block, bfq: make reparent_leaf_entity actually work only on leaf entities block, bfq: invoke flush_idle_tree after reparent_active_queues in pd_offline clk: Don't cache errors from clk_ops::get_phase() net/mlx5e: Enforce setting of a single FEC
[Kernel-packages] [Bug 1877677] Re: Disco update: upstream stable patchset 2020-05-08
Skipped: net: ipv6: add net argument to ip6_dst_lookup_flow net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup as those were applied for bug #1876982 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877677 Title: Disco update: upstream stable patchset 2020-05-08 Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-08 Ported from the following upstream stable releases: v4.19.119, v5.4.36 from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files drm/msm: Use the correct dma_sync calls harder bpftool: Fix printing incorrect pointer in btf_dump_ptr vti4: removed duplicate log message. arm64: Add part number for Neoverse N1 UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Silence clang warning on mismatched value/register sizes watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement scsi: iscsi: Report unbind session event when the target has been removed ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() nvme: fix deadlock caused by ANA update wrong locking kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index kconfig: qconf: Fix a few alignment issues s390/cio: avoid duplicated 'ADD' uevents loop: Better discard support for block devices Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet xhci: Ensure link state is U3 after setting USB_SS_PORT_LS_U3 drm/amd/display: Not doing optimize bandwidth if flip pending. virtio-blk: improve virtqueue error to BLK_STS scsi: smartpqi: fix call trace in device discovery PCI/ASPM: Allow re-enabling Clock PM net: ipv6: add net argument to ip6_dst_lookup_flow net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup f2fs: fix to avoid memory leakage in f2fs_listxattr cxgb4: fix adapter crash due to wrong MC size cxgb4: fix large delays in PTP synchronization ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() net: bcmgenet: correct per TX/RX ring statistics net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array net/x25: Fix x25_neigh refcnt leak when receiving frame sched: etf: do not assume all sockets are full blown tcp: cache line align MAX_TCP_HEADER team: fix hang in team_mode_get() vrf: Fix IPv6 with qdisc and xfrm net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled net: dsa: b53: Fix ARL register definitions net: dsa: b53: Rework ARL bin logic net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish vrf: Check skb for XFRM_TRANSFORMED flag mlxsw: Fix some IS_ERR() vs NULL bugs KEYS: Avoid false positive ENOMEM error on key read ALSA: hda: Remove ASUS ROG Zenith from the blacklist ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos ALSA: usb-audio: Add connector notifier delegation iio: core: remove extra semi-colon from devm_iio_device_register() macro iio: st_sensors: rely on odr mask to know if odr can be set iio: adc: stm32-adc: fix sleep in atomic context iio: xilinx-xadc: Fix ADC-B powerdown iio: xilinx-xadc: Fix clearing interrupt when enabling trigger iio: xilinx-xadc: Fix sequencer
[Kernel-packages] [Bug 1876174] Re: Disco update: upstream stable patchset 2020-04-30
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876174 Title: Disco update: upstream stable patchset 2020-04-30 Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-04-30 Ported from the following upstream stable releases: v4.19.117, v5.4.34 from git://git.kernel.org/ amd-xgbe: Use __napi_schedule() in BH context hsr: check protocol version in hsr_newlink() net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin net: ipv6: do not consider routes via gateways for anycast address check net: qrtr: send msgs from local of same id as broadcast net: revert default NAPI poll timeout to 2 jiffies net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode ovl: fix value of i_ino for lower hardlink corner case scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic jbd2: improve comments about freeing data buffers whose page mapping is NULL pwm: pca9685: Fix PWM/GPIO inter-operation ext4: fix incorrect group count in ext4_fill_super error message ext4: fix incorrect inodes per group in error message ASoC: Intel: mrfld: fix incorrect check on p->sink ASoC: Intel: mrfld: return error codes when an error occurs ALSA: usb-audio: Filter error from connector kctl ops, too ALSA: usb-audio: Don't override ignore_ctl_error value from the map ALSA: usb-audio: Don't create jack controls for PCM terminals ALSA: usb-audio: Check mapping at creating connector controls, too keys: Fix proc_keys_next to increase position index tracing: Fix the race between registering 'snapshot' event trigger and triggering 'snapshot' operation btrfs: check commit root generation in should_ignore_root mac80211_hwsim: Use kstrndup() in place of kasprintf() usb: dwc3: gadget: don't enable interrupt when disabling endpoint usb: dwc3: gadget: Don't clear flags before transfer ended drm/amd/powerplay: force the trim of the mclk dpm_levels if OD is enabled ext4: do not zeroout extents beyond i_disksize scsi: target: remove boilerplate code scsi: target: fix hang when multiple threads try to destroy the same iscsi session x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE x86/resctrl: Preserve CDP enable over CPU hotplug x86/resctrl: Fix invalid attempt at removing the default resource group wil6210: check rx_buff_mgmt before accessing it wil6210: ignore HALP ICR if already handled mm/vmalloc.c: move 'area->pages' after if statement l2tp: Allow management of tunnels and session in user namespace net: phy: micrel: use genphy_read_status for KSZ9131 net: tun: record RX queue in skb before do_xdp_generic() acpi/nfit: improve bounds checking for 'func' perf report: Fix no branch type statistics report issue ALSA: hda/realtek - Enable the headset mic on Asus FX505DT mac80211: fix race in ieee80211_register_hw() drm/amdgpu: fix the hw hang during perform system reboot and reset i2c: designware: platdrv: Remove DPM_FLAG_SMART_SUSPEND flag on BYT and CHT UBUNTU: upstream stable to v4.19.117, v5.4.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878232] Re: Xenial update: 4.4.223 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878232 Title: Xenial update: 4.4.223 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.223 upstream stable release from git://git.kernel.org/ The following patches from the 4.4.223 stable release shall be applied: * mwifiex: fix PCIe register information for 8997 chipset * drm/qxl: qxl_release use after free * drm/qxl: qxl_release leak in qxl_draw_dirty_fb() * staging: rtl8192u: Fix crash due to pointers being "confusing" * usb: gadget: f_acm: Fix configfs attr name * usb: gadged: pch_udc: get rid of redundant assignments * usb: gadget: pch_udc: reorder spin_[un]lock to avoid deadlock * usb: gadget: udc: core: don't starve DMA resources * MIPS: Fix macro typo * MIPS: ptrace: Drop cp0_tcstatus from regoffset_table[] * MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200 * MIPS: smp-cps: Stop printing EJTAG exceptions to UART * MIPS: scall: Handle seccomp filters which redirect syscalls * MIPS: BMIPS: BMIPS5000 has I cache filing from D cache * MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier * MIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache * MIPS: BMIPS: Pretty print BMIPS5200 processor name * MIPS: Fix HTW config on XPA kernel without LPA enabled * MIPS: BMIPS: Adjust mips-hpt-frequency for BCM7435 * MIPS: math-emu: Fix BC1{EQ,NE}Z emulation * MIPS: Fix BC1{EQ,NE}Z return offset calculation * MIPS: perf: Fix I6400 event numbers * MIPS: KVM: Fix translation of MFC0 ErrCtl * MIPS: SMP: Update cpu_foreign_map on CPU disable * MIPS: c-r4k: Fix protected_writeback_scache_line for EVA * MIPS: Octeon: Off by one in octeon_irq_gpio_map() * bpf, mips: fix off-by-one in ctx offset allocation * MIPS: RM7000: Double locking bug in rm7k_tc_disable() * MIPS: Define AT_VECTOR_SIZE_ARCH for ARCH_DLINFO * mips/panic: replace smp_send_stop() with kdump friendly version in panic path * ARM: dts: armadillo800eva Correct extal1 frequency to 24 MHz * ARM: imx: select SRC for i.MX7 * ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wxl/wsxl * ARM: dts: kirkwood: gpio pin fixes for linkstation ls-wvl/vl * ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wxl/wsxl * ARM: dts: kirkwood: gpio-leds fixes for linkstation ls-wvl/vl * ARM: dts: orion5x: gpio pin fixes for linkstation lswtgl * ARM: dts: orion5x: fix the missing mtd flash on linkstation lswtgl * ARM: dts: kirkwood: use unique machine name for ds112 * ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile * ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence * perf/x86: Fix filter_events() bug with event mappings * x86/LDT: Print the real LDT base address * x86/apic/uv: Silence a shift wrapping warning * ALSA: fm801: explicitly free IRQ line * ALSA: fm801: propagate TUNER_ONLY bit when autodetected * ALSA: fm801: detect FM-only card earlier * netfilter: nfnetlink: use original skbuff when acking batches * xfrm: fix crash in XFRM_MSG_GETSA netlink handler * mwifiex: fix IBSS data path issue. * mwifiex: add missing check for PCIe8997 chipset * iwlwifi: set max firmware version of 7265 to 17 * Bluetooth: btmrvl: fix hung task warning dump * dccp: limit sk_filter trim to payload * net/mlx4_core: Do not BUG_ON during reset when PCI is offline * mlxsw: pci: Correctly determine if descriptor queue is full * PCI: Supply CPU physical address (not bus address) to iomem_is_exclusive() * net/mlx4_core: Implement pci_resume callback * alpha/PCI: Call iomem_is_exclusive() for IORESOURCE_MEM, but not IORESOURCE_IO * vfio/pci: Allow VPD short read * brcmfmac: add eth_type_trans back for PCIe full dongle * mlxsw: Treat local port 64 as valid * IB/mlx4: Initialize hop_limit when creating address handle * ovs/gre,geneve: fix error path when creating an iface * GRE: Disable segmentation offloads w/ CSUM and we are encapsulated via FOU * powerpc/pci/of: Parse unassigned resources * firmware: actually return NULL on failed request_firmware_nowait() * c8sectpfe: Rework firmware loading mechanism * net/mlx5: Avoid passing dma address 0 to firmware * IB/mlx5: Fix RC transport send queue overhead computation * ne
[Kernel-packages] [Bug 1878596] [NEW] [Ubuntu 20.04] - Install - problem
You have been subscribed to a public bug: Hello, I finally started installing Ubuntu 20.04 and running into a problem. I looked at the available documentation which seem to be similar to previous Ubuntu install on IBM Z. I punch the parmfile, initrd, and kernel into the z/VM rdr and IPL 00C using the exec supplied as I did before but it stop in the middle and went to a "emergency mode" instead of asking me for the network information as in Ubuntu 18.04. Here is the output of both during the installation. Any idea what I'm missing? Ubuntu 20.04 [0.043942] Linux version 5.4.0-26-generic (buildd@bos02-s390x-015) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30) [0.043945] setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode [0.043955] setup.b050d0: The maximum memory size is 65536MB [0.043957] cma: Reserved 4 MiB at 0x000fffc0 [0.043980] numa.196305: NUMA mode: plain [0.044128] cpu.33a262: 4 configured CPUs, 0 standby CPUs [0.044569] Write protected kernel read-only data: 11556k [0.044985] Zone ranges: [0.044986] DMA [mem 0x-0x7fff] [0.044987] Normal [mem 0x8000-0x000f] [0.044988] Movable zone start for each node [0.044989] Early memory node ranges [0.044990] node 0: [mem 0x-0x000f] [0.044995] Initmem setup node 0 [mem 0x-0x000f] [0.709681] percpu: Embedded 34 pages/cpu s98816 r8192 d32256 u139264 [0.709718] Built 1 zonelists, mobility grouping on. Total pages: 16515072 [0.709719] Policy zone: Normal [0.709720] Kernel command line: %@@@ [0.710375] printk: log_buf_len individual max cpu contribution: 4096 bytes [0.710376] printk: log_buf_len total cpu_extra contributions: 258048 bytes [0.710376] printk: log_buf_len min size: 262144 bytes [0.710565] printk: log_buf_len: 524288 bytes [0.710566] printk: early log buf free: 259540(99%) [0.730700] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear) [0.740791] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) [0.740793] mem auto-init: stack:off, heap alloc:on, heap free:off [2.981614] Memory: 65904376K/67108864K available (9076K kernel code, 1708K rwdata, 2476K rodata, 3424K init, 948K bss, 1200392K reserved, 4096K cma-reserved ) [2.981627] random: get_random_u64 called from kmem_cache_open+0x42/0x4a0 with crng_init=001: HCPGSP2627I The virtual machine is placed in CP mode due to a S IGP initial CPU reset from CPU 00. 02: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial CPU reset from CPU 00. 03: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial CPU reset from CPU 00. [2.981826] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=64, Nodes=1 [2.981841] ftrace: allocating 29625 entries in 116 pages [2.986940] rcu: Hierarchical RCU implementation. [2.986941] rcu: RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=64. [2.986942] Tasks RCU enabled. [2.986943] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [2.986943] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=64 [2.989549] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [2.989624] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [2.989710] Console: colour dummy device
[Kernel-packages] [Bug 1878596] [NEW] [Ubuntu 20.04] - Install - problem
Public bug reported: Hello, I finally started installing Ubuntu 20.04 and running into a problem. I looked at the available documentation which seem to be similar to previous Ubuntu install on IBM Z. I punch the parmfile, initrd, and kernel into the z/VM rdr and IPL 00C using the exec supplied as I did before but it stop in the middle and went to a "emergency mode" instead of asking me for the network information as in Ubuntu 18.04. Here is the output of both during the installation. Any idea what I'm missing? Ubuntu 20.04 [0.043942] Linux version 5.4.0-26-generic (buildd@bos02-s390x-015) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30) [0.043945] setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode [0.043955] setup.b050d0: The maximum memory size is 65536MB [0.043957] cma: Reserved 4 MiB at 0x000fffc0 [0.043980] numa.196305: NUMA mode: plain [0.044128] cpu.33a262: 4 configured CPUs, 0 standby CPUs [0.044569] Write protected kernel read-only data: 11556k [0.044985] Zone ranges: [0.044986] DMA [mem 0x-0x7fff] [0.044987] Normal [mem 0x8000-0x000f] [0.044988] Movable zone start for each node [0.044989] Early memory node ranges [0.044990] node 0: [mem 0x-0x000f] [0.044995] Initmem setup node 0 [mem 0x-0x000f] [0.709681] percpu: Embedded 34 pages/cpu s98816 r8192 d32256 u139264 [0.709718] Built 1 zonelists, mobility grouping on. Total pages: 16515072 [0.709719] Policy zone: Normal [0.709720] Kernel command line: %@@@ [0.710375] printk: log_buf_len individual max cpu contribution: 4096 bytes [0.710376] printk: log_buf_len total cpu_extra contributions: 258048 bytes [0.710376] printk: log_buf_len min size: 262144 bytes [0.710565] printk: log_buf_len: 524288 bytes [0.710566] printk: early log buf free: 259540(99%) [0.730700] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear) [0.740791] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) [0.740793] mem auto-init: stack:off, heap alloc:on, heap free:off [2.981614] Memory: 65904376K/67108864K available (9076K kernel code, 1708K rwdata, 2476K rodata, 3424K init, 948K bss, 1200392K reserved, 4096K cma-reserved ) [2.981627] random: get_random_u64 called from kmem_cache_open+0x42/0x4a0 with crng_init=001: HCPGSP2627I The virtual machine is placed in CP mode due to a S IGP initial CPU reset from CPU 00. 02: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial CPU reset from CPU 00. 03: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP initial CPU reset from CPU 00. [2.981826] SLUB: HWalign=256, Order=0-3, MinObjects=0, CPUs=64, Nodes=1 [2.981841] ftrace: allocating 29625 entries in 116 pages [2.986940] rcu: Hierarchical RCU implementation. [2.986941] rcu: RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=64. [2.986942] Tasks RCU enabled. [2.986943] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [2.986943] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=64 [2.989549] NR_IRQS: 3, nr_irqs: 3, preallocated irqs: 3 [2.989624] clocksource: tod: mask: 0x max_cycles: 0x3b0a9be803b0a9, max_idle_ns: 1805497147909793 ns [2.989710] Console: colour dummy device 80x25
[Kernel-packages] [Bug 1876321] Re: Eoan update: upstream stable patchset 2020-05-01
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876321 Title: Eoan update: upstream stable patchset 2020-05-01 Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-01 Ported from the following upstream stable releases: v4.19.117, v5.4.34 from git://git.kernel.org/ amd-xgbe: Use __napi_schedule() in BH context hsr: check protocol version in hsr_newlink() net: ipv4: devinet: Fix crash when add/del multicast IP with autojoin net: ipv6: do not consider routes via gateways for anycast address check net: qrtr: send msgs from local of same id as broadcast net: revert default NAPI poll timeout to 2 jiffies net: stmmac: dwmac-sunxi: Provide TX and RX fifo sizes net: dsa: mt7530: fix tagged frames pass-through in VLAN-unaware mode ovl: fix value of i_ino for lower hardlink corner case scsi: ufs: Fix ufshcd_hold() caused scheduling while atomic jbd2: improve comments about freeing data buffers whose page mapping is NULL pwm: pca9685: Fix PWM/GPIO inter-operation ext4: fix incorrect group count in ext4_fill_super error message ext4: fix incorrect inodes per group in error message ASoC: Intel: mrfld: fix incorrect check on p->sink ASoC: Intel: mrfld: return error codes when an error occurs ALSA: usb-audio: Filter error from connector kctl ops, too ALSA: usb-audio: Don't override ignore_ctl_error value from the map ALSA: usb-audio: Don't create jack controls for PCM terminals ALSA: usb-audio: Check mapping at creating connector controls, too keys: Fix proc_keys_next to increase position index tracing: Fix the race between registering 'snapshot' event trigger and triggering 'snapshot' operation btrfs: check commit root generation in should_ignore_root mac80211_hwsim: Use kstrndup() in place of kasprintf() usb: dwc3: gadget: Don't clear flags before transfer ended drm/amd/powerplay: force the trim of the mclk dpm_levels if OD is enabled ext4: do not zeroout extents beyond i_disksize scsi: target: remove boilerplate code scsi: target: fix hang when multiple threads try to destroy the same iscsi session x86/microcode/AMD: Increase microcode PATCH_MAX_SIZE x86/resctrl: Preserve CDP enable over CPU hotplug x86/resctrl: Fix invalid attempt at removing the default resource group mm/vmalloc.c: move 'area->pages' after if statement l2tp: Allow management of tunnels and session in user namespace net: phy: micrel: use genphy_read_status for KSZ9131 net: tun: record RX queue in skb before do_xdp_generic() net/mlx5: Fix frequent ioread PCI access during recovery net/mlx5e: Add missing release firmware call net/mlx5e: Fix pfnum in devlink port attribute platform/chrome: cros_ec_rpmsg: Fix race with host event acpi/nfit: improve bounds checking for 'func' perf report: Fix no branch type statistics report issue net/bpfilter: remove superfluous testing message clk: at91: sam9x60: fix usb clock parents clk: at91: usb: use proper usbs_mask arm64: dts: librem5-devkit: add a vbus supply to usb0 ALSA: hda/realtek - Enable the headset mic on Asus FX505DT arm64: vdso: don't free unallocated pages nl80211: fix NL80211_ATTR_FTM_RESPONDER policy mac80211: fix race in ieee80211_register_hw() net/mlx5e: Encapsulate updating netdev queues into a function net/mlx5e: Rename hw_modify to preactivate net/mlx5e: Use preactivate hook to set the indirection table drm/amdgpu: fix the hw hang during perform system reboot and reset i2c: designware: platdrv: Remove DPM_FLAG_SMART_SUSPEND flag on BYT and CHT irqchip/ti-sci-inta: Fix processing of masked irqs UBUNTU: upstream stable to v4.19.117, v5.4.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876971] Re: Eoan update: upstream stable patchset 2020-05-05
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876971 Title: Eoan update: upstream stable patchset 2020-05-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-05 Ported from the following upstream stable releases: v4.19.118, v5.4.35 from git://git.kernel.org/ arm, bpf: Fix offset overflow for BPF_MEM BPF_DW objtool: Fix switch table detection in .text.unlikely scsi: sg: add sg_remove_request in sg_common_write ext4: use non-movable memory for superblock readahead watchdog: sp805: fix restart handler arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0 ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN. netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type irqchip/mbigen: Free msi_desc on device teardown ALSA: hda: Don't release card at firmware loading error of: unittest: kmemleak on changeset destroy of: unittest: kmemleak in of_unittest_platform_populate() of: unittest: kmemleak in of_unittest_overlay_high_level() of: overlay: kmemleak in dup_and_fixup_symbol_prop() x86/Hyper-V: Report crash register data or kmsg before running crash kernel rbd: avoid a deadlock on header_rwsem when flushing notifies rbd: call rbd_dev_unprobe() after unwatching and flushing notifies xsk: Add missing check on user supplied headroom size x86/Hyper-V: Unload vmbus channel in hv panic callback x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump x86/Hyper-V: Trigger crash enlightenment only once during system crash. x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not set x86/Hyper-V: Report crash data in die() when panic_on_oops is set clk: at91: usb: continue if clk_hw_round_rate() return zero power: supply: bq27xxx_battery: Silence deferred-probe error clk: tegra: Fix Tegra PMC clock out parents soc: imx: gpc: fix power up sequencing rtc: 88pm860x: fix possible race condition NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid() NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails s390/cpuinfo: fix wrong output when CPU0 is offline powerpc/maple: Fix declaration made after definition s390/cpum_sf: Fix wrong page count in error message ext4: do not commit super on read-only bdev um: ubd: Prevent buffer overrun on command completion cifs: Allocate encryption header through kmalloc include/linux/swapops.h: correct guards for non_swap_entry() percpu_counter: fix a data race at vm_committed_as compiler.h: fix error in BUILD_BUG_ON() reporting KVM: s390: vsie: Fix possible race when shadowing region 3 tables x86: ACPI: fix CPU hotplug deadlock drm/amdkfd: kfree the wrong pointer NFS: Fix memory leaks in nfs_pageio_stop_mirroring() f2fs: fix NULL pointer dereference in f2fs_write_begin() drm/vc4: Fix HDMI mode validation iommu/vt-d: Fix mm reference leak ext2: fix empty body warnings when -Wextra is used ext2: fix debug reference to ext2_xattr_cache power: supply: axp288_fuel_gauge: Broaden vendor check for Intel Compute Sticks. libnvdimm: Out of bounds read in __nd_ioctl() iommu/amd: Fix the configuration of GCR3 table root pointer f2fs: fix to wait all node page writeback net: dsa: bcm_sf2: Fix overflow checks fbdev: potential information leak in do_fb_ioctl() iio: si1133: read 24-bit signed integer for measurement tty: evh_bytechan: Fix out of bounds accesses locktorture: Print ratio of acquisitions, not failures mtd: spinand: Explicitly use MTD_OPS_RAW to write the bad block marker to OOB mtd: lpddr: Fix a double free in probe() mtd: phram: fix a double free issue in error path KEYS: Don't write out to userspace while holding key semaphore bpf: fix buggy r0 retval refinement for tracing helpers ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops kbuild, btf: Fix dependencies for DEBUG_INFO_BTF afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus() afs: Fix decoding of inline abort codes from version 1 status records afs: Fix rename operation status delivery afs: Fix afs_d_vali
[Kernel-packages] [Bug 1878073] Re: Eoan update: upstream stable patchset 2020-05-11
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878073 Title: Eoan update: upstream stable patchset 2020-05-11 Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-05-11 Ported from the following upstream stable releases: v4.19.119, v5.4.36 from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files bpftool: Fix printing incorrect pointer in btf_dump_ptr UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Silence clang warning on mismatched value/register sizes watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement scsi: iscsi: Report unbind session event when the target has been removed ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() nvme: fix deadlock caused by ANA update wrong locking kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index kconfig: qconf: Fix a few alignment issues s390/cio: avoid duplicated 'ADD' uevents loop: Better discard support for block devices Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet drm/amd/display: Not doing optimize bandwidth if flip pending. virtio-blk: improve virtqueue error to BLK_STS scsi: smartpqi: fix call trace in device discovery PCI/ASPM: Allow re-enabling Clock PM f2fs: fix to avoid memory leakage in f2fs_listxattr cxgb4: fix adapter crash due to wrong MC size cxgb4: fix large delays in PTP synchronization ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() net: bcmgenet: correct per TX/RX ring statistics net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array net/x25: Fix x25_neigh refcnt leak when receiving frame sched: etf: do not assume all sockets are full blown tcp: cache line align MAX_TCP_HEADER team: fix hang in team_mode_get() vrf: Fix IPv6 with qdisc and xfrm net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled net: dsa: b53: Fix ARL register definitions net: dsa: b53: Rework ARL bin logic net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish vrf: Check skb for XFRM_TRANSFORMED flag mlxsw: Fix some IS_ERR() vs NULL bugs KEYS: Avoid false positive ENOMEM error on key read ALSA: hda: Remove ASUS ROG Zenith from the blacklist ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos ALSA: usb-audio: Add connector notifier delegation iio: core: remove extra semi-colon from devm_iio_device_register() macro iio: st_sensors: rely on odr mask to know if odr can be set iio: adc: stm32-adc: fix sleep in atomic context iio: xilinx-xadc: Fix ADC-B powerdown iio: xilinx-xadc: Fix clearing interrupt when enabling trigger iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode iio: xilinx-xadc: Make sure not exceed maximum samplerate USB: sisusbvga: Change port variable from signed to unsigned USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE USB: early: Handle AMD's spec-compliant identifiers, too USB: core: Fix free-while-in-u
[Kernel-packages] [Bug 1718897] Re: perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so: cannot open shared object file: No such file or directory
Still broken in 18.04: perf: error while loading shared libraries: libbfd-2.24-system.so: cannot open shared object file: 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/1718897 Title: perf broken on 4.13.0-11-generic (artful): libbfd-2.29-system.so: cannot open shared object file: No such file or directory Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Won't Fix Bug description: perf fails to start on my Artful install. This bug is very similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702056 ... which was marked "fix released" a month ago. I do not have "-proposed" enabled. Full error: faux@astoria:~% perf /usr/lib/linux-tools/4.13.0-11-generic/perf: error while loading shared libraries: libbfd-2.29-system.so: cannot open shared object file: No such file or directory System state: faux@astoria:~% uname -a Linux astoria.goeswhere.com 4.13.0-11-generic #12-Ubuntu SMP Tue Sep 12 16:03:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux faux@astoria:~% dpkg -L binutils|grep bfd|grep so [nothing] faux@astoria:~% ls -1 /usr/lib/x86_64-linux-gnu/*libbfd* /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-multiarch.so /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so /usr/lib/x86_64-linux-gnu/libbfd.a /usr/lib/x86_64-linux-gnu/libbfd.so faux@astoria:~% dpkg -S /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so libbinutils:amd64: /usr/lib/x86_64-linux-gnu/libbfd-2.29.1-system.so faux@astoria:~% apt-cache policy libbinutils libbinutils: Installed: 2.29.1-1ubuntu1 Candidate: 2.29.1-1ubuntu1 Version table: *** 2.29.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status faux@astoria:~% ldd /usr/lib/linux-tools/4.13.0-11-generic/perf | fgrep -2 bfd libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x7ff43e595000) libslang.so.2 => /lib/x86_64-linux-gnu/libslang.so.2 (0x7ff43e0b3000) libbfd-2.29-system.so => not found libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7ff43de96000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff43dc7) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-11-generic 4.13.0-11.12 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: faux 2664 F pulseaudio /dev/snd/pcmC0D0p: faux 2664 F...m pulseaudio /dev/snd/controlC0: faux 2664 F pulseaudio Date: Fri Sep 22 10:33:50 2017 HibernationDevice: RESUME=UUID=a99845b9-8854-43ea-9c9d-c9248cea15ab IwConfig: em1 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=UUID=672510b8-afb9-425f-a58d-bd325f7c987a ro rootflags=subvol=@ nofb RelatedPackageVersions: linux-restricted-modules-4.13.0-11-generic N/A linux-backports-modules-4.13.0-11-generic N/A linux-firmware 1.168 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-09-12 (9 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1718897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878596] Re: [Ubuntu 20.04] - Install - problem
With Ubuntu Server 20.04 a new installer (called "subiquity") was introduced. And subiquity is a bit different compared to d-i. For the transition phase we still have one (last) 20.04 GA image with d-i, available here (but already marked as legacy): http://cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.04/release/ Since d-i is legacy, I of course recommended to use (and to become familiar) with subiquity. And subiquity is available here: http://cdimage.ubuntu.com/releases/20.04/release/ It operates a bit differently and requires (aot) some data that needs to be handed over via the parmfile. Please have a look here for some more details: https://ubuntu-on-big-iron.blogspot.com/2020/03/glimpse-at-subiquity.html On top one may of course also try the 'ready to use' cloud images (for KVM) or container images (LXD) - for their specific use cases. ** Package changed: linux (Ubuntu) => subiquity (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1878596 Title: [Ubuntu 20.04] - Install - problem Status in Ubuntu on IBM z Systems: New Status in subiquity package in Ubuntu: New Bug description: Hello, I finally started installing Ubuntu 20.04 and running into a problem. I looked at the available documentation which seem to be similar to previous Ubuntu install on IBM Z. I punch the parmfile, initrd, and kernel into the z/VM rdr and IPL 00C using the exec supplied as I did before but it stop in the middle and went to a "emergency mode" instead of asking me for the network information as in Ubuntu 18.04. Here is the output of both during the installation. Any idea what I'm missing? Ubuntu 20.04 [0.043942] Linux version 5.4.0-26-generic (buildd@bos02-s390x-015) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 (Ubuntu 5.4.0-26.30-generic 5.4.30) [0.043945] setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode [0.043955] setup.b050d0: The maximum memory size is 65536MB [0.043957] cma: Reserved 4 MiB at 0x000fffc0 [0.043980] numa.196305: NUMA mode: plain [0.044128] cpu.33a262: 4 configured CPUs, 0 standby CPUs [0.044569] Write protected kernel read-only data: 11556k [0.044985] Zone ranges: [0.044986] DMA [mem 0x-0x7fff] [0.044987] Normal [mem 0x8000-0x000f] [0.044988] Movable zone start for each node [0.044989] Early memory node ranges [0.044990] node 0: [mem 0x-0x000f] [0.044995] Initmem setup node 0 [mem 0x-0x000f] [0.709681] percpu: Embedded 34 pages/cpu s98816 r8192 d32256 u139264 [0.709718] Built 1 zonelists, mobility grouping on. Total pages: 16515072 [0.709719] Policy zone: Normal [0.709720] Kernel command line: %@@@ [0.710375] printk: log_buf_len individual max cpu contribution: 4096 bytes [0.710376] printk: log_buf_len total cpu_extra contributions: 258048 bytes [0.710376] printk: log_buf_len min size: 262144 bytes [0.710565] printk: log_buf_len: 524288 bytes [0.710566] printk: early log buf free: 259540(99%) [0.730700] Dentry cache hash table entries: 8388608 (order: 14, 67108864 bytes, linear) [0.740791] Inode-cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear) [0.740793] mem auto-init: stack:off, heap alloc:on, heap free:off [2.981614] Memory: 65904376K/67108864K available (9076K kernel code, 1708K rwdata, 2476K rodata, 3424K init, 948K bss, 1200392K reserved, 4096K cma-reserved ) [2.981627] random: get_random_u64 called from kmem_cache_open+0x42/0x4a0 with crng_init=001: HCPGSP2627I The virtu
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
** Attachment added: "lsusb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+attachment/5371509/+files/lsusb -- 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+attachment/5371507/+files/dmesg -- 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
lspci -vvnn ** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+attachment/5371508/+files/lspci -- 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
firmwares are all up-to-date. ** Attachment added: "fwupdmgr-get-devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+attachment/5371510/+files/fwupdmgr-get-devices -- 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] [NEW] When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
Public bug reported: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
usb1 and usb2 is root hub of "00:0d.0 USB controller [0c03]: Intel Corporation Ice Lake Thunderbolt 3 USB Controller [8086:8a13] (rev 03) (prog-if 30 [XHCI])". ** 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/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877270] Re: Devlink - add RoCE disable kernel support
Hi Jeff, after testing the feature we see that some devlink functionality is missing in our driver and we must add them before adding the ROCE feature. This missing functionality is the implementation of devlink reload and it was introduced upstream by the following two patches: 4383cfcc65e7 ("net/mlx5: Add devlink reload") 32680da71034 ("net/mlx5: Remove unneeded variable in mlx5_unload_one") the above patches applied cleanly over your tree but we have some compiling issue since the following patch are missing: 070c63f20f6c ("net: devlink: allow to change namespaces during reload") these compiling issues can be resolved by aligned mlx5_devlink_reload_down to Focal devlink_ops->reload_down by removing the 'bool netns_change' parameter from mlx5_devlink_reload_down function. Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877270 Title: Devlink - add RoCE disable kernel support Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] RoCE disable feature was added to the kernel v5.5. This feature was requested by Mellanox customers that use Ubuntu 20.04, and it's a very high important to deliver this feature to the customers in one of ubuntu 20.04 SRU. [SHORT DESCRIPTION] RoCE enablement state controls driver support for RoCE traffic. When RoCE is disabled, there is no gid table, only raw ethernet QPs are supported and traffic on the well known UDP RoCE port is handled as raw ethernet traffic. [Test Case] To change RoCE enablement state a user must change the driverinit cmode value and run devlink reload. User command examples: - Disable RoCE:: $ devlink dev param set pci/:06:00.0 name enable_roce value false cmode driverinit $ devlink dev reload pci/:06:00.0 - Read RoCE enablement state:: $ devlink dev param show pci/:06:00.0 name enable_roce pci/:06:00.0: name enable_roce type generic values: cmode driverinit value true [Regression Potential] This feature shouldn't affect the regression because it's only adding support for RoCE enable/disable. Also, This feature was tested internally by Mellanox QA teams those tests logs/results are private unfortunately i can't share it here [Other Info] Feature patchset: 94de879c28d8 IB/mlx5: Load profile according to RoCE enablement state b5a498baf929 IB/mlx5: Rename profile and init methods cc9defcbb8fa net/mlx5: Handle "enable_roce" devlink param e90cde0d76f0 net/mlx5: Document flow_steering_mode devlink param 6c7295e13ffd devlink: Add new "enable_roce" generic device param patctwork: https://patchwork.ozlabs.org/cover/1192314/ userspace: No userspace dependency on this. the feature uses the devlink param functionality which already exists in UB20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
from journal log this looks wrong: Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: xf86EnableIOPort s: failed to set IOPL for I/O (Operation not permitted) Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(0): using drv /dev/dri/card0 Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (WW) Falling bac k to old probe method for fbdev Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) Loading sub module "fbdevhw" Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) LoadModule: "fbdevhw" Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so ... Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (EE) open /dev/f b0: Permission denied Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : using drv /dev/dri/card1 Mai 14 12:12:04 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (WW) VGA arbiter : cannot open kernel arbiter, no multi-card support ... Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (EE) modeset(G0): glamor initialization failed but here it looks like monitor is correctly found (like in gnome-preferences) Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : EDID for output HDMI-1-2 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Manufacturer: HPN Model: 363a Serial#: 16843009 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Year: 2019 Week: 41 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : EDID Version: 1.3 Mai 14 12:12:05 frank-G5-U20 /usr/lib/gdm3/gdm-x-session[1526]: (II) modeset(G0) : Digital Display Input -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.produ