[Kernel-packages] [Bug 1893504] 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/1893504 Title: System froze Status in linux package in Ubuntu: Confirmed Bug description: After of about 8 to 12 hours of use the system simply freezes. No mouse or keyboard response. Even video playing on the page stops responding. There is nothing special to be done to cause the problem, sometimes the system freezes at idle sometimes, sometimes it freezes while I'm using it. Hardware: CPU: Ryzen Threadripper 3970x Memory: 128GB Corsair Vengeance LPX Motherboard: Asus Zenith Extreme 2 NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe System: Ubuntu 5.4.0-42.46-generic 5.4.44 lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pcarrara 2332 F pulseaudio /dev/snd/controlC1: pcarrara 2332 F pulseaudio /dev/snd/controlC0: pcarrara 2332 F pulseaudio /dev/snd/pcmC0D7p: pcarrara 2332 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 02:07:36 2020 InstallationDate: Installed on 2020-08-27 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893504] [NEW] System froze
Public bug reported: After of about 8 to 12 hours of use the system simply freezes. No mouse or keyboard response. Even video playing on the page stops responding. There is nothing special to be done to cause the problem, sometimes the system freezes at idle sometimes, sometimes it freezes while I'm using it. Hardware: CPU: Ryzen Threadripper 3970x Memory: 128GB Corsair Vengeance LPX Motherboard: Asus Zenith Extreme 2 NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe System: Ubuntu 5.4.0-42.46-generic 5.4.44 lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pcarrara 2332 F pulseaudio /dev/snd/controlC1: pcarrara 2332 F pulseaudio /dev/snd/controlC0: pcarrara 2332 F pulseaudio /dev/snd/pcmC0D7p: pcarrara 2332 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 02:07:36 2020 InstallationDate: Installed on 2020-08-27 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1893504/+attachment/5405619/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893504 Title: System froze Status in linux package in Ubuntu: Confirmed Bug description: After of about 8 to 12 hours of use the system simply freezes. No mouse or keyboard response. Even video playing on the page stops responding. There is nothing special to be done to cause the problem, sometimes the system freezes at idle sometimes, sometimes it freezes while I'm using it. Hardware: CPU: Ryzen Threadripper 3970x Memory: 128GB Corsair Vengeance LPX Motherboard: Asus Zenith Extreme 2 NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe System: Ubuntu 5.4.0-42.46-generic 5.4.44 lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pcarrara 2332 F pulseaudio /dev/snd/controlC1: pcarrara 2332 F pulseaudio /dev/snd/controlC0: pcarrara 2332 F pulseaudio /dev/snd/pcmC0D7p: pcarrara 2332 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 02:07:36 2020 InstallationDate: Installed on 2020-08-27 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
Please test this kernel https://people.canonical.com/~hwang4/hpomen/ and upload the dmesg. If it still has the error of loading topology, I guess we have to try with sof-firmware-v1.5.1 with 5.8 kernel or 5.9-rc 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/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881676] Re: HyperX Cloud Alpha microphone not detected
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881676 Title: HyperX Cloud Alpha microphone not detected Status in linux package in Ubuntu: Expired Bug description: When using the HyperX AMP, the microphone is not detected. This is a known issue with the mainline kernel, however was patched in release 5.7.0. This occurs on Ubuntu 20.04 LTS. https://lkml.org/lkml/2020/4/4/197 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jun 1 18:50:04 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-05-23 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881638] Re: touchpad not appearing in list of hardware devices
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881638 Title: touchpad not appearing in list of hardware devices Status in linux package in Ubuntu: Expired Bug description: touchpad has been frozen for ~1 hour. Doesn't appear when checking xinput --list or other lists of hardware connected to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prachi 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 11:06:06 2020 InstallationDate: Installed on 2020-05-18 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 7590 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-33-generic root=UUID=3a384bca-9677-48c8-bd86-3395fc0e3565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879949] Re: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879949 Title: NVIDIA GP104 [GeForce GTX 1070] [10de:1b81] Subsystem [19da:1445] Can not log in: Failed to acquire modesetting permission Status in linux package in Ubuntu: Expired Bug description: I'm on Ubuntu 20.04. After upgrading from linux 5.4.0-26-generic to 5.4.0-31-generic I could not log in anymore. I was stuck in the display manager. Then I rebooted into the old kernel and sent these reports. I'm not sure if this is related but I can't put my display onto the correct resolution anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 3203 F pulseaudio /dev/snd/controlC1: jesko 3203 F pulseaudio /dev/snd/controlC2: jesko 3203 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:07:25 2020 InstallationDate: Installed on 2020-05-20 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp24s0 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=9f451f12-4a89-4dcc-9eca-97df16101efc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PLUS (MS-7B79) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd11/16/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B79 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892239] Re: Audio Problems Ubuntu 20.04
No obvious errors from the log. Did the audio work normally before 20.04? If yes, what was the kernel version at that time? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892239 Title: Audio Problems Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade to Ubuntu 20.04 I started having problems with audio. From the beginning my internal speakers were recognized but no audio came from them, also at first my headphones didn't work. I started to try different things that I found on the Internet and I got my audio "working". I put it between quotes because my speakers only work sometimes, and when my speakers don't work my headphones do (and when the internal speakers work my headphones don't). Although it can happen that sound comes out of my headphones but its internal microphone doesn't work, however the internal microphone of my PC works(or vice versa). It's a Russian roulette every time I turn on my PC Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: 5.4.0-42-generic Architecture: x86_64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: supremequeen 1616 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 16:02:21 2020 InstallationDate: Installed on 2020-05-08 (102 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 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 04f2:b5db Chicony Electronics Co., Ltd HP Webcam Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-bp0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=01607e9d-1b80-42d8-9877-dbc9a338bf89 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 835F dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPLaptop14-bp0xx:pvrType1ProductConfigId:rvnHP:rn835F:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-bp0xx dmi.product.sku: 1GR55LA#AC8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893493] Re: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like
: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4611 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 01:17:01 2020 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard + + this is quite probably a duplicate; experienced before I suspect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893493 Title: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared and became black. On using system, background changes from all BLACK to blocky-low- signal digital-tv like blocks that is unusable for reading detail on screen, but it seems to return to all black in time (or with use) I can change wallpapers and that appears to work correctly at least for a time, the new wallpaper will disappear (again with time or use) and wallpaper goes dead-black again (though primary screen may also have mimimized windows appearing in blocky-low-signal-tv like; not neat and readable but messy & changing.. nice easy black on second monitor) I've been unable to take screen dumps, not sure why. /var/crash/ is empty Minimized windows do not disappear from screen, hitting minimize on a window does nothing (visually). It's these images that appear to become the blocky-blotchety-low-signal background that eventually becomes all black. Once a window was made to minimize, even though image is fully on screen, clicking mouse on visible-window works now like you're clicking background (though minimized window is displayed). If i could get screendumps this effect could be lost. Currently this report is low quality (can't get screencaptures, no photo), but the behavior differs between my screens. My upper screen is a lot less problematic than my-lower (primary) display. Opening the menu blackens (completely) the background on lower display (yeah, the older windows that were minimized can be distracting..) and improves usability. /var/crash now has contents ubuntu@ubuntu:~$ ls -la /var/crash total 168 drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 . drwxr-xr-x 1 root root160 Aug 28 08:15 .. -rw-r- 1 ubuntu whoopsie 164662 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.crash -rw-rw-r-- 1 ubuntu whoopsie 0 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.upload -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.uploaded I haven't worked out a pattern on what causes the strange behavior, it's not all the time -- however I can create the worst of it by just changing the screen orientation (even just a little). Do that and any chosen wallpaper is gone, and my background appears to be filled with detail from possibly prior? pages!?? eg. rather than my two screens directly one above the other, I move to top to be slight left/right a little.. As I type this into firefox window (on lp), I'm getting glitches on the background that is somewhat distracting/annoying. I wouldn't use this system as it is. The issue is likely graphics driver related.. though I've tagged kernel. ProblemType: Bug DistroReleas
[Kernel-packages] [Bug 1893493] Re: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1893493 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893493 Title: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared and became black. On using system, background changes from all BLACK to blocky-low- signal digital-tv like blocks that is unusable for reading detail on screen, but it seems to return to all black in time (or with use) I can change wallpapers and that appears to work correctly at least for a time, the new wallpaper will disappear (again with time or use) and wallpaper goes dead-black again (though primary screen may also have mimimized windows appearing in blocky-low-signal-tv like; not neat and readable but messy & changing.. nice easy black on second monitor) I've been unable to take screen dumps, not sure why. /var/crash/ is empty Minimized windows do not disappear from screen, hitting minimize on a window does nothing (visually). It's these images that appear to become the blocky-blotchety-low-signal background that eventually becomes all black. Once a window was made to minimize, even though image is fully on screen, clicking mouse on visible-window works now like you're clicking background (though minimized window is displayed). If i could get screendumps this effect could be lost. Currently this report is low quality (can't get screencaptures, no photo), but the behavior differs between my screens. My upper screen is a lot less problematic than my-lower (primary) display. Opening the menu blackens (completely) the background on lower display (yeah, the older windows that were minimized can be distracting..) and improves usability. /var/crash now has contents ubuntu@ubuntu:~$ ls -la /var/crash total 168 drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 . drwxr-xr-x 1 root root160 Aug 28 08:15 .. -rw-r- 1 ubuntu whoopsie 164662 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.crash -rw-rw-r-- 1 ubuntu whoopsie 0 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.upload -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.uploaded I haven't worked out a pattern on what causes the strange behavior, it's not all the time -- however I can create the worst of it by just changing the screen orientation (even just a little). Do that and any chosen wallpaper is gone, and my background appears to be filled with detail from possibly prior? pages!?? eg. rather than my two screens directly one above the other, I move to top to be slight left/right a little.. As I type this into firefox window (on lp), I'm getting glitches on the background that is somewhat distracting/annoying. I wouldn't use this system as it is. The issue is likely graphics driver related.. though I've tagged kernel. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4611 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 01:17:01 2020 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.c
[Kernel-packages] [Bug 1893493] 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/1893493 Title: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared and became black. On using system, background changes from all BLACK to blocky-low- signal digital-tv like blocks that is unusable for reading detail on screen, but it seems to return to all black in time (or with use) I can change wallpapers and that appears to work correctly at least for a time, the new wallpaper will disappear (again with time or use) and wallpaper goes dead-black again (though primary screen may also have mimimized windows appearing in blocky-low-signal-tv like; not neat and readable but messy & changing.. nice easy black on second monitor) I've been unable to take screen dumps, not sure why. /var/crash/ is empty Minimized windows do not disappear from screen, hitting minimize on a window does nothing (visually). It's these images that appear to become the blocky-blotchety-low-signal background that eventually becomes all black. Once a window was made to minimize, even though image is fully on screen, clicking mouse on visible-window works now like you're clicking background (though minimized window is displayed). If i could get screendumps this effect could be lost. Currently this report is low quality (can't get screencaptures, no photo), but the behavior differs between my screens. My upper screen is a lot less problematic than my-lower (primary) display. Opening the menu blackens (completely) the background on lower display (yeah, the older windows that were minimized can be distracting..) and improves usability. /var/crash now has contents ubuntu@ubuntu:~$ ls -la /var/crash total 168 drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 . drwxr-xr-x 1 root root160 Aug 28 08:15 .. -rw-r- 1 ubuntu whoopsie 164662 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.crash -rw-rw-r-- 1 ubuntu whoopsie 0 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.upload -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.uploaded I haven't worked out a pattern on what causes the strange behavior, it's not all the time -- however I can create the worst of it by just changing the screen orientation (even just a little). Do that and any chosen wallpaper is gone, and my background appears to be filled with detail from possibly prior? pages!?? eg. rather than my two screens directly one above the other, I move to top to be slight left/right a little.. As I type this into firefox window (on lp), I'm getting glitches on the background that is somewhat distracting/annoying. I wouldn't use this system as it is. The issue is likely graphics driver related.. though I've tagged kernel. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4611 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 01:17:01 2020 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/3
[Kernel-packages] [Bug 1893493] [NEW] ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like
Public bug reported: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared and became black. On using system, background changes from all BLACK to blocky-low-signal digital-tv like blocks that is unusable for reading detail on screen, but it seems to return to all black in time (or with use) I can change wallpapers and that appears to work correctly at least for a time, the new wallpaper will disappear (again with time or use) and wallpaper goes dead-black again (though primary screen may also have mimimized windows appearing in blocky-low-signal-tv like; not neat and readable but messy & changing.. nice easy black on second monitor) I've been unable to take screen dumps, not sure why. /var/crash/ is empty Minimized windows do not disappear from screen, hitting minimize on a window does nothing (visually). It's these images that appear to become the blocky-blotchety-low-signal background that eventually becomes all black. Once a window was made to minimize, even though image is fully on screen, clicking mouse on visible-window works now like you're clicking background (though minimized window is displayed). If i could get screendumps this effect could be lost. Currently this report is low quality (can't get screencaptures, no photo), but the behavior differs between my screens. My upper screen is a lot less problematic than my-lower (primary) display. Opening the menu blackens (completely) the background on lower display (yeah, the older windows that were minimized can be distracting..) and improves usability. /var/crash now has contents ubuntu@ubuntu:~$ ls -la /var/crash total 168 drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 . drwxr-xr-x 1 root root160 Aug 28 08:15 .. -rw-r- 1 ubuntu whoopsie 164662 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.crash -rw-rw-r-- 1 ubuntu whoopsie 0 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.upload -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 _usr_share_apport_dump_acpi_tables.py.999.uploaded I haven't worked out a pattern on what causes the strange behavior, it's not all the time -- however I can create the worst of it by just changing the screen orientation (even just a little). Do that and any chosen wallpaper is gone, and my background appears to be filled with detail from possibly prior? pages!?? eg. rather than my two screens directly one above the other, I move to top to be slight left/right a little.. As I type this into firefox window (on lp), I'm getting glitches on the background that is somewhat distracting/annoying. I wouldn't use this system as it is. The issue is likely graphics driver related.. though I've tagged kernel. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4611 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 01:17:01 2020 IwConfig: lono wireless extensions. enp0s25 no wireless extensions. LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: Ubuntu groovy QA-test (live) I changed screen setup to match my setup (2x 1920x1080 displays one above the other, the default-right got moved to above my other monitor). On doing this screen background disappeared an
[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
drm-tip is unusable (application is slow/doesn't even launch correctly) 5.9.0-rc2: Aug 28 19:39:30 foxglove kernel: [ 77.392548] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! ug 28 19:39:30 foxglove kernel: [ 82.181755] gmc_v9_0_process_interrupt: 2992 callbacks suppressed Aug 28 19:39:30 foxglove kernel: [ 82.181760] amdgpu :0c:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32771, for process WoW.exe pid 4330 thread WoW.exe pid 4330) Aug 28 19:39:30 foxglove kernel: [ 82.181763] amdgpu :0c:00.0: amdgpu: in page starting at address 0x80008000 from client 27 Aug 28 19:39:30 foxglove kernel: [ 82.181765] amdgpu :0c:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601431 Aug 28 19:39:30 foxglove kernel: [ 82.181766] amdgpu :0c:00.0: amdgpu: Faulty UTCL2 client ID: 0xa Aug 28 19:39:30 foxglove kernel: [ 82.181767] amdgpu :0c:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 28 19:39:30 foxglove kernel: [ 82.181767] amdgpu :0c:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.181768] amdgpu :0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 28 19:39:30 foxglove kernel: [ 82.181769] amdgpu :0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.181770] amdgpu :0c:00.0: amdgpu: RW: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.183442] amdgpu :0c:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32771, for process WoW.exe pid 4330 thread WoW.exe pid 4330) Aug 28 19:39:30 foxglove kernel: [ 82.183444] amdgpu :0c:00.0: amdgpu: in page starting at address 0x80008000 from client 27 Aug 28 19:39:30 foxglove kernel: [ 82.183446] amdgpu :0c:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601431 Aug 28 19:39:30 foxglove kernel: [ 82.183446] amdgpu :0c:00.0: amdgpu: Faulty UTCL2 client ID: 0xa Aug 28 19:39:30 foxglove kernel: [ 82.183447] amdgpu :0c:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 28 19:39:30 foxglove kernel: [ 82.183448] amdgpu :0c:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.183449] amdgpu :0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 28 19:39:30 foxglove kernel: [ 82.183450] amdgpu :0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.183450] amdgpu :0c:00.0: amdgpu:: RW: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.185128] amdgpu :0c:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32771, for process WoW.exe pid 4330 thread WoW.exe pid 4330) Aug 28 19:39:30 foxglove kernel: [ 82.185131] amdgpu :0c:00.0: amdgpu: in page starting at address 0x80008000 from client 27 Aug 28 19:39:30 foxglove kernel: [ 82.185132] amdgpu :0c:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601431 Aug 28 19:39:30 foxglove kernel: [ 82.185133] amdgpu :0c:00.0: amdgpu: Faulty UTCL2 client ID: 0xa Aug 28 19:39:30 foxglove kernel: [ 82.185134] amdgpu :0c:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 28 19:39:30 foxglove kernel: [ 82.185135] amdgpu :0c:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.185136] amdgpu :0c:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 28 19:39:30 foxglove kernel: [ 82.185137] amdgpu :0c:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 28 19:39:30 foxglove kernel: [ 82.185138] amdgpu :0c:00.0: amdgpu: [...] Aug 28 19:39:30 foxglove kernel: [ 82.190140] amdgpu :0c:00.0: amdgpu: [gf xhub0] retry page fault (src_id:0 ring:0 vmid:6 pasid:32771, for process WoW.exe pid 4330 thread WoW.exe pid 4330) Aug 28 19:39:30 foxglove kernel: [ 82.190141] amdgpu :0c:00.0: amdgpu: i n page starting at address 0x80008000 from client 27 Aug 28 19:39:30 foxglove kernel: [ 82.190142] amdgpu :0c:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00601431 [...] Aug 28 19:39:31 foxglove kernel: [ 82.225032] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered [...] Aug 28 19:39:41 foxglove kernel: [ 87.852888] [drm:amdgpu_dm_commit_planes [am dgpu]] *ERROR* Waiting for fences timed out! Aug 28 19:39:41 foxglove kernel: [ 92.972903] [drm:amdgpu_dm_commit_planes [am dgpu]] *ERROR* Waiting for fences timed out! Aug 28 19:39:41 foxglove kernel: [ 92.972983] [drm:amdgpu_job_timedout [amdgpu ]] *ERROR* ring gfx timeout, but soft recovered Aug 28 19:39:52 foxglove kernel: [ 98.604891] [drm:amdgpu_dm_commit_planes [am dgpu]] *ERROR* Waiting for fences timed out! Aug 28 19:39:52 foxglove kernel: [ 103.724906] [drm:amdgpu_dm_commit_planes [am dgpu]] *ERROR* Waiting for fences timed out! Aug 28 19:39:52 foxglove kernel: [ 103.725029] [drm:amdgpu_job_timedout [amdgpu ]] *ERROR* ring gfx timeout, but soft recovered Aug 28 19:39:55 foxglove /usr/lib/gdm3/gdm-x-session[2119]: amdgpu: command stre am overflowed Aug 28 19:39:55 foxglove
[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
This issue also seems to be happening for Renoir with 5.4.0 kernel series, when DXVK/vulkan is used. I will try drm-tip and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883493 Title: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted seq=535495 Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 pid 3694 Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled. Mouse pointer still moves, but apart from that the display is frozen. Music keeps playing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 09:09:56 2020 InstallationDate: Installed on 2020-05-28 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893489] 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/1893489 Title: 20.10 gets black screen after login on 5.8.0-16 kernel Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu Budgie base of 20.04 and Virtualbox. Have 20.10 running in VB. With last last kernel update 8.8.0-16 after login in get a black screen. Booting the 5.4 kernel works ok ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Aug 28 15:12:32 2020 InstallationDate: Installed on 2020-04-30 (120 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200429) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8ca86e24-ebcc-44dd-a552-a66c1612724f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892239] Re: Audio Problems Ubuntu 20.04
Hi Seth, I had already tried that but it doesn't work. Anyway thank you very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892239 Title: Audio Problems Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade to Ubuntu 20.04 I started having problems with audio. From the beginning my internal speakers were recognized but no audio came from them, also at first my headphones didn't work. I started to try different things that I found on the Internet and I got my audio "working". I put it between quotes because my speakers only work sometimes, and when my speakers don't work my headphones do (and when the internal speakers work my headphones don't). Although it can happen that sound comes out of my headphones but its internal microphone doesn't work, however the internal microphone of my PC works(or vice versa). It's a Russian roulette every time I turn on my PC Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: 5.4.0-42-generic Architecture: x86_64 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: supremequeen 1616 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 19 16:02:21 2020 InstallationDate: Installed on 2020-05-08 (102 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 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 04f2:b5db Chicony Electronics Co., Ltd HP Webcam Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-bp0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=01607e9d-1b80-42d8-9877-dbc9a338bf89 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 835F dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPLaptop14-bp0xx:pvrType1ProductConfigId:rvnHP:rn835F:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-bp0xx dmi.product.sku: 1GR55LA#AC8 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893489] [NEW] 20.10 gets black screen after login on 5.8.0-16 kernel
Public bug reported: Using Ubuntu Budgie base of 20.04 and Virtualbox. Have 20.10 running in VB. With last last kernel update 8.8.0-16 after login in get a black screen. Booting the 5.4 kernel works ok ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Aug 28 15:12:32 2020 InstallationDate: Installed on 2020-04-30 (120 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200429) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8ca86e24-ebcc-44dd-a552-a66c1612724f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1893489 Title: 20.10 gets black screen after login on 5.8.0-16 kernel Status in linux package in Ubuntu: New Bug description: Using Ubuntu Budgie base of 20.04 and Virtualbox. Have 20.10 running in VB. With last last kernel update 8.8.0-16 after login in get a black screen. Booting the 5.4 kernel works ok ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Aug 28 15:12:32 2020 InstallationDate: Installed on 2020-04-30 (120 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200429) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8ca86e24-ebcc-44dd-a552-a66c1612724f ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about
[Kernel-packages] [Bug 1887703] Re: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller
For what it's worth, this doesn't just affect the X710-TM4 controller. The X710-T2L card is rendered completely useless by this bug as that card only has copper 10 GbE ports. As with the X710-TM4, the latest version of the Intel driver fixes the issue. Are there plans to release a fixed i40e driver for Focal soon? It looks like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890988 is another duplicate of this bug as 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/1887703 Title: [Regression] 5.4 is not identifying all ports on Intel x710-TM4 10GbE controller Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [IMPACT] The Intel x710-TM4 is one of the latest 10GbE controllers from intel using the i40e driver. This particular 4 port comes in a 2x2 arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4 via the inbox version of the i40e driver, and hwinfo does show both sides of the card but the kernel only sees the two SFP+ ports and cannot address or use the two copper ports. This is currently blocking certification for one of our hardware partners. After some investigation we see this works in a more recent version of the driver. Intel suggests the commit in FIXES from 5.5 should make this work. This is a regression from the i40e driver in Bionic (5.3 HWE) that, per the tester, does show all four ports. [FIXES] 3df5b9a6a9ec3c1e4431bf1db3426b54dc92dd91 i40e: enable X710 support I have a branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1887703-i40e-enable-x710 [TESTING] Boot system, verify four ports are visible and can be addressed and pass data. [IMPACT] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893470] Re: Cheese doesn't show image or video
** Also affects: cheese (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893470 Title: Cheese doesn't show image or video Status in cheese package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. But GTK UVC works well without changing that port. Changed the USB port for Cheese. Reinstalled and tried. But in vain. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1893470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893248] Re: Xenial update: v4.4.234 upstream stable release
** Description changed:
+ SRU Justification
- 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:
- 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:
+ v4.4.234 upstream stable release
+ from git://git.kernel.org/
-v4.4.234 upstream stable release
-from git://git.kernel.org/
+ cxl: Fix kobject memleak
+ UBUNTU: upstream stable to v4.4.233
+ drm/imx: imx-ldb: Disable both channels for split mode in enc->disable()
+ perf probe: Fix memory leakage when the probe point is not found
+ net/compat: Add missing sock updates for SCM_RIGHTS
+ watchdog: f71808e_wdt: indicate WDIOF_CARDRESET support in
watchdog_info.options
+ watchdog: f71808e_wdt: remove use of wrong watchdog_info option
+ coredump: fix race condition between collapse_huge_page() and core dumping
+ khugepaged: khugepaged_test_exit() check mmget_still_valid()
+ khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
+ btrfs: export helpers for subvolume name/id resolution
+ btrfs: don't show full path of bind mounts in subvol=
+ romfs: fix uninitialized memory leak in romfs_dev_read()
+ mm: include CMA pages in lowmem_reserve at boot
+ mm, page_alloc: fix core hung in free_pcppages_bulk()
+ ext4: clean up ext4_match() and callers
+ ext4: fix checking of directory entry validity for inline directories
+ media: budget-core: Improve exception handling in budget_register()
+ media: vpss: clean up resources in init
+ Input: psmouse - add a newline when printing 'proto' by sysfs
+ m68knommu: fix overwriting of bits in ColdFire V3 cache control
+ xfs: fix inode quota reservation checks
+ jffs2: fix UAF problem
+ scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
+ virtio_ring: Avoid loop when vq is broken in virtqueue_poll
+ xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
+ alpha: fix annotation of io{read,write}{16,32}be()
+ ext4: fix potential negative array index in do_split()
+ ASoC: intel: Fix memleak in sst_media_open
+ powerpc: Allow 4224 bytes of stack expansion for the signal frame
+ epoll: Keep a reference on files added to the check list
+ do_epoll_ctl(): clean the failure exits up a bit
+ mm/hugetlb: fix calculation of adjust_range_if_pmd_sharing_possible
+ xen: don't reschedule in preemption off sections
+ omapfb: dss: Fix max fclk divider for omap36xx
+ KVM: arm/arm64: Don't reschedule in unmap_stage2_range()
+ Linux 4.4.234
+ UBUNTU: upstream stable to v4.4.234
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893248
Title:
Xenial update: v4.4.234 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
In Progress
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:
v4.4.234 upstream stable release
from git://git.kernel.org/
cxl: Fix kobject memleak
UBUNTU: upstream stable to v4.4.233
drm/imx: imx-ldb: Disable both channels for split mode in enc->disable()
perf probe: Fix memory leakage when the probe point is not found
net/compat: Add missing sock updates for SCM_RIGHTS
watchdog: f71808e_wdt: indicate WDIOF_CARDRESET support in
watchdog_info.options
watchdog: f71808e_wdt: remove use of wrong watchdog_info option
coredump: fix race condition between collapse_huge_page() and core dumping
khugepaged: khugepaged_test_exit() check mmget_still_valid()
khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
btrfs: export helpers for subvolume name/id resolution
btrfs: don't show full path of bind mounts in subvol=
romfs: fix uninitialized memory leak in romfs_dev_read()
mm: include CMA pages in lowmem_reserve at boot
mm, page_alloc: fix core hung in free_pcppages_bulk()
[Kernel-packages] [Bug 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"
Exactly the same problem but my log files are very big (almost 1To and crashing my computer). I am on a Lenovo Yoga 14ARR (with a Ryzen 5) on Ubuntu 20.04LTS. Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810240] wlp1s0: Failed check-sdata-in-driver check, flags: 0x4 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810262] WARNING: CPU: 4 PID: 9350 at net/mac80211/driver-ops.h:17 drv_sta_state+0x254/0x3f0 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810262] Modules linked in: rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm aufs cmac algif_hash algif_skcipher overlay af_alg bnep binfmt_misc nls_iso8859_1 edac_mce_amd kvm_amd ccp kvm crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio uvcvideo snd_hda_codec_hdmi videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb snd_hda_intel btrtl videobuf2_common snd_seq_midi btbcm snd_intel_dspcfg snd_seq_midi_event btintel iwlmvm snd_hda_codec bluetooth aesni_intel mac80211 videodev crypto_simd snd_hda_core amdgpu cryptd ecdh_generic glue_helper mc snd_rawmidi snd_hwdep ecc libarc4 input_leds amd_iommu_v2 hid_sensor_accel_3d snd_pcm serio_raw hid_sensor_trigger industrialio_triggered_buffer gpu_sched kfifo_buf wmi_bmof snd_seq Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810280] iwlwifi hid_sensor_iio_common hid_multitouch joydev industrialio k10temp snd_seq_device ttm snd_timer snd drm_kms_helper cfg80211 i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore ideapad_laptop sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_sensor_custom wacom usbhid hid_sensor_hub hid_generic crc32_pclmul nvme i2c_piix4 nvme_core wmi video i2c_hid i2c_amd_mp2_plat hid i2c_amd_mp2_pci Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810290] CPU: 4 PID: 9350 Comm: kworker/4:5 Tainted: GW OE 5.4.0-42-generic #46-Ubuntu Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810290] Hardware name: LENOVO 81H9/INVALID, BIOS 8MCN57WW 10/10/2019 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810300] Workqueue: events_freezable ieee80211_restart_work [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810311] RIP: 0010:drv_sta_state+0x254/0x3f0 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810312] Code: 00 45 31 ed e9 66 fe ff ff 48 8b 83 78 04 00 00 48 8d b3 98 04 00 00 48 c7 c7 c8 f8 c2 c0 48 85 c0 48 0f 45 f0 e8 57 31 ef ed <0f> 0b 41 bd fb ff ff ff e9 3d fe ff ff 65 8b 05 e8 1c 46 3f 89 c0 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810313] RSP: 0018:b2f2c3f2f840 EFLAGS: 00010286 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810314] RAX: RBX: 92ebc84d88c0 RCX: 0006 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810315] RDX: 0007 RSI: 0092 RDI: 92ebcf1178c0 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810315] RBP: b2f2c3f2f878 R08: 091e4091 R09: 0004 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810316] R10: R11: 0001 R12: 92ebc33487a0 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810316] R13: 92ebc33487a0 R14: 0004 R15: 92ebc3348d68 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810317] FS: () GS:92ebcf10() knlGS: Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810318] CS: 0010 DS: ES: CR0: 80050033 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810319] CR2: 7f86e03fced0 CR3: 1cc0a000 CR4: 003406e0 Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810319] Call Trace: Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810330] sta_info_move_state+0x276/0x370 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810341] __sta_info_destroy_part2+0x2f/0x180 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810352] __sta_info_flush+0x128/0x180 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810365] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810378] ieee80211_mgd_deauth+0x104/0x490 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810391] ieee80211_deauth+0x18/0x20 [mac80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR kernel: [10142.810403] cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211] Aug 28 19:52:26 vincent-LENOVO-Yoga-530-14ARR
[Kernel-packages] [Bug 1893470] Re: Cheese doesn't show image or video
** Description changed: - Cheese image/video disappears within a fraction of a second. Ubuntu - 16.04.7. But GTK UVC works well. + Ubuntu 16.04.7 + + My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. + + But GTK UVC works well without changing that port. Changed the USB port for Cheese. But in vain. + + + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: - cheese3.18.1-2ubuntu3 - cheese-common 3.18.1-2ubuntu3 + cheese3.18.1-2ubuntu3 + cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Description changed: Ubuntu 16.04.7 - My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. - - But GTK UVC works well without changing that port. Changed the USB port for Cheese. But in vain. + My webcam is connected to a USB port. Image/video in Cheese disappears + within a fraction of a second. - - + But GTK UVC works well without changing that port. Changed the USB port + for Cheese. Reinstalled. But in vain. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: ** Description changed: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. But GTK UVC works well without changing that port. Changed the USB port - for Cheese. Reinstalled. But in vain. + for Cheese. Reinstalled and tried. But in vain. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893470 Title: Cheese doesn't show image or video Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. But GTK UVC works well without changing that port. Changed the USB port for Cheese. Reinstalled and tried. But in vain.
[Kernel-packages] [Bug 1893470] [NEW] Cheese doesn't show image or video
Public bug reported: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. But GTK UVC works well without changing that port. Changed the USB port for Cheese. But in vain. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug gstreamer-error i386 xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893470 Title: Cheese doesn't show image or video Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. But GTK UVC works well without changing that port. Changed the USB port for Cheese. But in vain. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@gannon1 Sure. I found I am not getting the consistent output from the new logging that I expected, so I want to try a couple of things this weekend to understand it better. Then I will type up a brief summary and post it in the other thread... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1850776] Re: Kernel NULL pointer dereference on suspend
I am getting this error on Acer Nitro laptop with NVIDIA driver 440. Using GeForce GTX 1650 Mobile / Max Q Not on every suspend, about once per week. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1850776 Title: Kernel NULL pointer dereference on suspend Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Hi, I had a bug every now and then with the Nvidia proprietary driver 435 (installed via the "additionals proprietary drivers" GUI) where I try to suspend my laptop, and the system freezes. It happens from time to time, but so far, I have this issue quite frequently, as I'm often suspending my laptop, so very annoying as you can imagine. Looking at journactl -b 1, the reason is simple: kernel NULL pointer dereference: oct. 31 09:01:51 Strix kernel: BUG: kernel NULL pointer dereference, address: oct. 31 09:01:51 Strix kernel: #PF: supervisor instruction fetch in kernel mode oct. 31 09:01:51 Strix kernel: #PF: error_code(0x0010) - not-present page oct. 31 09:01:51 Strix kernel: PGD 0 P4D 0 oct. 31 09:01:51 Strix kernel: Oops: 0010 [#1] SMP PTI oct. 31 09:01:51 Strix kernel: CPU: 2 PID: 2719 Comm: Xorg Tainted: P O 5.3.0-19-generic #20-Ubuntu oct. 31 09:01:51 Strix kernel: Hardware name: ASUSTeK COMPUTER INC. Strix GL504GV_G515GV/GL504GV, BIOS GL504GV.307 07/11/2019 oct. 31 09:01:51 Strix kernel: RIP: 0010:0x0 oct. 31 09:01:51 Strix kernel: Code: Bad RIP value. oct. 31 09:01:51 Strix kernel: RSP: 0018:afb0c4077920 EFLAGS: 00010286 oct. 31 09:01:51 Strix kernel: RAX: RBX: 8db4a3fff110 RCX: c1c72060 oct. 31 09:01:51 Strix kernel: RDX: 0010 RSI: 8db4a3fff118 RDI: 8db4a3fff150 oct. 31 09:01:51 Strix kernel: RBP: 8db517aaadf0 R08: c1c720b8 R09: oct. 31 09:01:51 Strix kernel: R10: c0f0af14 R11: 8db51dea8820 R12: 8db4a3fff118 oct. 31 09:01:51 Strix kernel: R13: 8db3a87da120 R14: 8db517aaaf10 R15: 8db51ef3d028 oct. 31 09:01:51 Strix kernel: FS: 7faede56ca80() GS:8db52d88() knlGS: oct. 31 09:01:51 Strix kernel: CS: 0010 DS: ES: CR0: 80050033 oct. 31 09:01:51 Strix kernel: CR2: ffd6 CR3: 00045b712002 CR4: 003626e0 oct. 31 09:01:51 Strix kernel: Call Trace: oct. 31 09:01:51 Strix kernel: _nv004359rm+0x45/0x80 [nvidia] oct. 31 09:01:51 Strix kernel: WARNING: kernel stack frame pointer at d844b2ec in Xorg:2719 has bad value deb3a039 oct. 31 09:01:51 Strix kernel: unwind stack type:0 next_sp:93bd32f2 mask:0x2 graph_idx:0 oct. 31 09:01:51 Strix kernel: d844b2ec: 0018 (0x18) oct. 31 09:01:51 Strix kernel: 182c383c: c12f4285 (_nv004359rm+0x45/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 0c257d20: 8db51ef3d010 (0x8db51ef3d010) oct. 31 09:01:51 Strix kernel: 18eb8076: 8db4a3fff110 (0x8db4a3fff110) oct. 31 09:01:51 Strix kernel: 58beaab6: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: d7d391bc: c12f0c9c (_nv034838rm+0x1c/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 3d9d3366: 8db51ef3d218 (0x8db51ef3d218) oct. 31 09:01:51 Strix kernel: eaaf8f98: c12ff249 (_nv003603rm+0x9/0x20 [nvidia]) oct. 31 09:01:51 Strix kernel: 79766f3e: 8db51ef3d028 (0x8db51ef3d028) oct. 31 09:01:51 Strix kernel: fbeb93a1: c12f425b (_nv004359rm+0x1b/0x80 [nvidia]) oct. 31 09:01:51 Strix kernel: 160c8872: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 40aecac9: 8db51949c810 (0x8db51949c810) oct. 31 09:01:51 Strix kernel: 5884ca89: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: f66282ec: c12f1897 (_nv011071rm+0x2d7/0x350 [nvidia]) oct. 31 09:01:51 Strix kernel: c77ee642: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel: f4fcb456: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: ef44b1aa: c1d0 (0xc1d0) oct. 31 09:01:51 Strix kernel: 514af435: 00010049 (0x10049) oct. 31 09:01:51 Strix kernel: b0f4b16c: ... oct. 31 09:01:51 Strix kernel: 03a0e9a9: c0ce4a55 (_nv034837rm+0x1a5/0x1f0 [nvidia]) oct. 31 09:01:51 Strix kernel: 7a9ef523: 8db3a87da030 (0x8db3a87da030) oct. 31 09:01:51 Strix kernel: 27d325ee: c1d3fe20 (_nv000488rm+0x1c/0xff69a1fc [nvidia]) oct. 31 09:01:51 Strix kernel: 4163f071: 8db517aaaf10 (0x8db517aaaf10) oct. 31 09:01:51 Strix kernel:
[Kernel-packages] [Bug 1887487] Re: range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6
** Tags added: sru-20200810 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887487 Title: range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6 Status in ubuntu-kernel-tests: New Status in linux-oem-5.6 package in Ubuntu: New Bug description: Issue found on 5.6.0-1020.20 Focal OEM kernel, this should not be considered as a regression since the test can't be built before this cycle (bug 1879360) #555/p jgt32: range bound deduction, reg op imm FAIL Unexpected success to load! verification time 69 usec stack depth 8 processed 21 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #556/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL Unexpected success to load! verification time 95 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #557/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL Unexpected success to load! verification time 85 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
** Tags added: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878946] Re: Cannot install proprietary NVIDIA driver
No, still no solution. I tried again a few days ago, assuming it might have
been fixed with Kubuntu 20.04.1, but to no avail. There were the same errors
regarding the link from /usr/lib/x86_64-linux-gnu/libGL.so.1 as before.
Maybe this will be solved with Kubuntu 20.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1878946
Title:
Cannot install proprietary NVIDIA driver
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Confirmed
Bug description:
1) Distro: Kubuntu 20.04
2) Package version: nvidia-driver-440 version
"440.82+really.440.64-0ubuntu6"
I have started the driver management from system settings, selected
"Using NVIDIA driver metapackage from nvidia-driver-440 (proprietary,
tested).
3) What I expected to happen: The proprietary driver should be
installed. OpenCL should work (e.g. for darktable).
4) What happened instead: An error window pops up. Title: "Error wh...
changes", content: "pk-client-error-quark: Error while installing package:
>>neues libnidia-gl-440 (313)".
The additional drivers selector still shows "Using X.ORg X server - Nouveau
display driver from xserver-xorg-nouveau (open source)", although this package
is NOT installed.
Checking with muon, it shows that some nvidia 440 related packages have been
installed, but nvidia-driver-440 is shown with status 'corrupt' ('Defekt' in
German). The packages libnvidia-ifr1-440 and libnvidia-ifr1-440 are also shown
with status 'corrupt'.
Discover offers 'libnvidia-gl-440 version 440.82+really.440.64-0ubuntu6', but
that cannot be installed.
Trying to clear up the situation on the commandline results in:
"sudo apt install -f
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Abhängigkeiten werden korrigiert ... Fertig
Die folgenden zusätzlichen Pakete werden installiert:
libnvidia-gl-440 libnvidia-gl-440:i386
Die folgenden NEUEN Pakete werden installiert:
libnvidia-gl-440 libnvidia-gl-440:i386
0 aktualisiert, 2 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
63 nicht vollständig installiert oder entfernt.
Es müssen noch 0 B von 79,6 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 281 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
(Lese Datenbank ... 276127 Dateien und Verzeichnisse sind derzeit
installiert.)
Vorbereitung zum Entpacken von
.../libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb ...
Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 zu
/usr/lib/i386-linux-gnu/libGL.so.1.distrib durch nvidia-340
dpkg-divert: Fehler: Keine Übereinstimmung mit Paket
beim Entfernen von »Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 durch
libnvidia-gl-440«
»Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 zu
/usr/lib/i386-linux-gnu/libGL.so.1.distrib durch nvidia-340« gefunden
dpkg: Fehler beim Bearbeiten des Archivs
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb
(--unpack):
»neues libnvidia-gl-440:i386-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 2 zurück
Vorbereitung zum Entpacken von
.../libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb ...
Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1 zu
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib durch nvidia-340
dpkg-divert: Fehler: Keine Übereinstimmung mit Paket
beim Entfernen von »Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1
durch libnvidia-gl-440«
»Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1 zu
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib durch nvidia-340« gefunden
dpkg: Fehler beim Bearbeiten des Archivs
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb
(--unpack):
»neues libnvidia-gl-440:amd64-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)"
[Sorry for this being partially in German]
darktable shows OpenCL as being unavailable, even if the nvidia kernel
modules (nvidia, nvidia_uvm, nvidia_modeset, nvidia_drm modeset=1) have been
loaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878946/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
An investigation is currently underway for the issue with the 4.15
kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1883261
Title:
[linux-azure] Two Fixes For kdump Over Network
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
Microsoft would like to request two kdump related fixes in all
releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release
resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible
symptom is that the network is not functional in the kdump kernel, so
the dump file must be stored on the local disk and cannot be written
over the network.
The problem only occurs when Accelerated Networking is enabled. It’s
a relatively obscure scenario, which is why the problem has not
surfaced before now. But we have an important customer who wants the
“dump-file-over-the-network” functionality to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849348] Re: Greater than linux 5.4-rc4 headers -- Unable to build simple kernel module
kernel 5.4, gcc 8.4 still same error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849348
Title:
Greater than linux 5.4-rc4 headers -- Unable to build simple kernel
module
Status in linux package in Ubuntu:
Confirmed
Bug description:
Cannot build a kernel module, errors in Linux headers using the
current RC4 (also tried RC3, and daily) mainline kernel packages from
http://kernel.ubuntu.com/~kernel-ppa/mainline
Am able to build against a 5.4-rc4 kernel level directly from upstream kernel
git repo (on a different platform).
To recreate error:
Install linux headers, etc from current 5.4 RC. (used 5.4.0-050400rc4
dated 10/20 for this test)
--[/tmp/builderr/Makefile]--
EXTRA_CFLAGS +=
obj-m += conftest.o
-- [EOF] --
--[/tmp/builderr/conftest.c]--
#include
void conftest(void)
{
}
MODULE_LICENSE("GPL-2");
-- [EOF] --
Command:
make -C /lib/modules/5.4.0-050400rc4-generic/build M=/tmp/builderr/
V=2 &> make_err.log
make.log is attached.
Expected output (using above Makefile and conftest.c, performed a build on a
system with 4.15.0-66 linux packages installed):
-- [expected output] --
make -C /lib/modules/4.15.0-66-generic/build/ M=/tmp/builderr
make: Entering directory '/usr/src/linux-headers-4.15.0-66-generic'
CC [M] /tmp/builderr/conftest.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/builderr/conftest.mod.o
LD [M] /tmp/builderr/conftest.ko
make: Leaving directory '/usr/src/linux-headers-4.15.0-66-generic'
=
lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
uname -a
Linux ubuntu_base 5.4.0-050400rc4-generic #201910202130 SMP Sun Oct 20
21:32:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
dpkg -l | grep "linux\-[a-z]*\-"
ii linux-headers-5.4.0-050400rc45.4.0-050400rc4.201910202130
all Header files related to Linux kernel version 5.4.0
ii linux-headers-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii linux-image-unsigned-5.4.0-050400rc4-generic 5.4.0-050400rc4.201910202130
amd64Linux kernel image for version 5.4.0 on 64 bit x86 SMP
ri linux-libc-dev:amd64 4.15.0-65.74
amd64Linux Kernel Headers for development
ii linux-modules-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86
SMP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849348/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
I've been testing with the 4.15 kernel and using the following wiki for
guidance of using kdump/ssh:
https://ubuntu.com/server/docs/kernel-crash-dump
I first confirmed I could kdump to local disk. Next, I configured kdump per the
wiki to use ssh.
However, everytime I cause a crash, the kexec kernel hangs and seems like it
cannot reach the network to write the crash file to. Here is the error I see:
[ 387.778745] kdump-tools[735]: Starting kdump-tools:
[ 387.790249] kdump-tools[763]: Connection closed by 13.77.154.182 port 22
[ 387.794756] kdump-tools[744]: * Network not reachable; will try 15 more times
I'm not sure if this is due to a config error on my part or because of
the test kernel. Is there any information you could provide to confirm
my configration is correct? I'll attach my /etc/default/kexec file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1883261
Title:
[linux-azure] Two Fixes For kdump Over Network
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
Microsoft would like to request two kdump related fixes in all
releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release
resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible
symptom is that the network is not functional in the kdump kernel, so
the dump file must be stored on the local disk and cannot be written
over the network.
The problem only occurs when Accelerated Networking is enabled. It’s
a relatively obscure scenario, which is why the problem has not
surfaced before now. But we have an important customer who wants the
“dump-file-over-the-network” functionality to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849348] Re: Greater than linux 5.4-rc4 headers -- Unable to build simple kernel module
sorry kernels 5.4 ... Launchpad does not allow to edit/delete posts?
unbelievable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849348
Title:
Greater than linux 5.4-rc4 headers -- Unable to build simple kernel
module
Status in linux package in Ubuntu:
Confirmed
Bug description:
Cannot build a kernel module, errors in Linux headers using the
current RC4 (also tried RC3, and daily) mainline kernel packages from
http://kernel.ubuntu.com/~kernel-ppa/mainline
Am able to build against a 5.4-rc4 kernel level directly from upstream kernel
git repo (on a different platform).
To recreate error:
Install linux headers, etc from current 5.4 RC. (used 5.4.0-050400rc4
dated 10/20 for this test)
--[/tmp/builderr/Makefile]--
EXTRA_CFLAGS +=
obj-m += conftest.o
-- [EOF] --
--[/tmp/builderr/conftest.c]--
#include
void conftest(void)
{
}
MODULE_LICENSE("GPL-2");
-- [EOF] --
Command:
make -C /lib/modules/5.4.0-050400rc4-generic/build M=/tmp/builderr/
V=2 &> make_err.log
make.log is attached.
Expected output (using above Makefile and conftest.c, performed a build on a
system with 4.15.0-66 linux packages installed):
-- [expected output] --
make -C /lib/modules/4.15.0-66-generic/build/ M=/tmp/builderr
make: Entering directory '/usr/src/linux-headers-4.15.0-66-generic'
CC [M] /tmp/builderr/conftest.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/builderr/conftest.mod.o
LD [M] /tmp/builderr/conftest.ko
make: Leaving directory '/usr/src/linux-headers-4.15.0-66-generic'
=
lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
uname -a
Linux ubuntu_base 5.4.0-050400rc4-generic #201910202130 SMP Sun Oct 20
21:32:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
dpkg -l | grep "linux\-[a-z]*\-"
ii linux-headers-5.4.0-050400rc45.4.0-050400rc4.201910202130
all Header files related to Linux kernel version 5.4.0
ii linux-headers-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii linux-image-unsigned-5.4.0-050400rc4-generic 5.4.0-050400rc4.201910202130
amd64Linux kernel image for version 5.4.0 on 64 bit x86 SMP
ri linux-libc-dev:amd64 4.15.0-65.74
amd64Linux Kernel Headers for development
ii linux-modules-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86
SMP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849348/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849348] Re: Greater than linux 5.4-rc4 headers -- Unable to build simple kernel module
AFAIK this is an issue with kernels 5.3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849348
Title:
Greater than linux 5.4-rc4 headers -- Unable to build simple kernel
module
Status in linux package in Ubuntu:
Confirmed
Bug description:
Cannot build a kernel module, errors in Linux headers using the
current RC4 (also tried RC3, and daily) mainline kernel packages from
http://kernel.ubuntu.com/~kernel-ppa/mainline
Am able to build against a 5.4-rc4 kernel level directly from upstream kernel
git repo (on a different platform).
To recreate error:
Install linux headers, etc from current 5.4 RC. (used 5.4.0-050400rc4
dated 10/20 for this test)
--[/tmp/builderr/Makefile]--
EXTRA_CFLAGS +=
obj-m += conftest.o
-- [EOF] --
--[/tmp/builderr/conftest.c]--
#include
void conftest(void)
{
}
MODULE_LICENSE("GPL-2");
-- [EOF] --
Command:
make -C /lib/modules/5.4.0-050400rc4-generic/build M=/tmp/builderr/
V=2 &> make_err.log
make.log is attached.
Expected output (using above Makefile and conftest.c, performed a build on a
system with 4.15.0-66 linux packages installed):
-- [expected output] --
make -C /lib/modules/4.15.0-66-generic/build/ M=/tmp/builderr
make: Entering directory '/usr/src/linux-headers-4.15.0-66-generic'
CC [M] /tmp/builderr/conftest.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/builderr/conftest.mod.o
LD [M] /tmp/builderr/conftest.ko
make: Leaving directory '/usr/src/linux-headers-4.15.0-66-generic'
=
lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
uname -a
Linux ubuntu_base 5.4.0-050400rc4-generic #201910202130 SMP Sun Oct 20
21:32:54 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
dpkg -l | grep "linux\-[a-z]*\-"
ii linux-headers-5.4.0-050400rc45.4.0-050400rc4.201910202130
all Header files related to Linux kernel version 5.4.0
ii linux-headers-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii linux-image-unsigned-5.4.0-050400rc4-generic 5.4.0-050400rc4.201910202130
amd64Linux kernel image for version 5.4.0 on 64 bit x86 SMP
ri linux-libc-dev:amd64 4.15.0-65.74
amd64Linux Kernel Headers for development
ii linux-modules-5.4.0-050400rc4-generic5.4.0-050400rc4.201910202130
amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86
SMP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849348/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
The following link holds test kernels for 5.4, 5.3, and 4.15:
https://kernel.ubuntu.com/~kms/azure/lp1883261/
5.4 was a clean apply, though 5.3 and 4.15 required some changes. Please
test to verify the added patches resolve the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1883261
Title:
[linux-azure] Two Fixes For kdump Over Network
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
Microsoft would like to request two kdump related fixes in all
releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release
resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible
symptom is that the network is not functional in the kdump kernel, so
the dump file must be stored on the local disk and cannot be written
over the network.
The problem only occurs when Accelerated Networking is enabled. It’s
a relatively obscure scenario, which is why the problem has not
surfaced before now. But we have an important customer who wants the
“dump-file-over-the-network” functionality to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
A fix mentioning this bug report has been applied upstream and to
mainline stable linux-5.4.y and backported to focal/linux as part of our
regular stable backports (bug 1892417):
SUNRPC: Fix ("SUNRPC: Add "@len" parameter to gss_unwrap()")
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=0ed4abf7a4dceb99ed2dd2a3d593bb17409c8df9
This patch is committed for the next kernel SRU.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
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/1886277
Title:
Regression on NFS: unable to handle page fault in mempool_alloc_slab
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Bug description:
On kernel 5.4.0-40-generic in focal I'm getting errors like this on
several machines with different hardware in the first hour after boot:
Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for
address: 9083e222e632
Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode
Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page
Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0
Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI
Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted:
G OE 5.4.0-40-generic #44-Ubuntu
Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW,
BIOS N2IET88W (1.66 ) 04/22/2020
Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc]
Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230
Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65
4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f
4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb
Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282
Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX:
RCX: 0002
Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800
RDI: 00031fb0
Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0
R09: c1436a94
Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018
R12: 9083e222e632
Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140
R15: 908367ca6140
Jul 04 16:58:32 hostname kernel: FS: ()
GS:90836c30() knlGS:
Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0:
80050033
Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003
CR4: 003606e0
Jul 04 16:58:32 hostname kernel: Call Trace:
Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20
Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20
Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180
Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc]
Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc]
Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc]
Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc]
Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc]
Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0
Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400
Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140
Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0
Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90
Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40
Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5
auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE)
vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay
nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s>
Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei
processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common
intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd
int3403_thermal soundcore int340x_thermal_zone i>
Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel
Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632
Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]---
Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230
Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65
4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f
4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01
[Kernel-packages] [Bug 1887674] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.51.06-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887674] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.51.06-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1887674 Title: Introduce the new NVIDIA 450-server and the 450 UDA series Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450 source package in Bionic: In Progress Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450 source package in Focal: In Progress Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886827] Re: Machine hangs when doing a normal reboot
Ok, I finally got commit b292b50b0efcc7095d8bf15505fba6909bb35dce to build successfully. Result is also success! Normal reboot works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
5.4 does NOT boot with nouveau (i have to disable them), but 5.8 does boot with nouveau. (after uninstalling nvidia drivers I cannot install them again as per https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-440/+bug/1878946 but this is another story) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
Sure. I attach dmesg with 5.8 kernel without dmic_detect=0. Note that this is with nvidia with nouveau drivers. ~$ sudo lshw -C video *-display description: VGA compatible controller product: TU104BM [GeForce RTX 2080 Mobile] vendor: NVIDIA Corporation ... configuration: driver=nouveau latency=0 resources: ... Output device: Dummy output Input device: ** Attachment added: "dmesg_5_8" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+attachment/5405440/+files/dmesg_5_8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891451] Re: Add TGL+ SAGV display support
Verified focal-proposed 5.6.0-1022-oem and 5.6.0-1023-oem. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1891451 Title: Add TGL+ SAGV display support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [SRU Justification] [Impact] On platforms with UHD panel, massive drawing area updates may cause screen to flash as half-baked render buffers with black areas being renedered. [Fix] This turns out to be the lack of full support to Intel System Agent Geyserville (SAGV), which has been landed to kernel v5.8. The required fix resides in https://patchwork.freedesktop.org/series/75129/, which seems a rolling set that its early parts have been committed separatedly several times. This patchset also depends on https://patchwork.freedesktop.org/series/72301/, which attempts to make global state handling more standardized. [Test Case] 1. Trigger massive rect updates, e.g. cat a lengthy file in xterm, dump kernel git history, etc. 2. Observe if screen flashes with half black panes, sometimes black stripes, etc. [Regression Potential] Medium. This is to backport a new feature landed to kernel early this year, even there is no later fixes patch found so far, it could still introduce incompatibility to older kernels. So far it behaves on both UHD and other lower resolutions. == Original Bug Description == On platforms with UHD panel, massive drawing area updates may cause screen to flash as half-baked render buffers with black areas being renedered. [Reproduce Steps] 1. boot to GUI 2. generate massive screen updates by `while true; do dmesg; done` or so [Results] Expected Result: Text output correctly rendered on xterm smoothly Actual Result: Screen flashes with black strides, etc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1855 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X35 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-07 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem root=UUID=00ec17d2-a1e3-4363-a67b-a7c380cc9189 ro drm.debug=0x1ff log_buf_len=32M ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.6.0-1020-oem N/A linux-backports-modules-5.6.0-1020-oem N/A linux-firmware 1.187.2 RfKill: Tags: focal Uname: Linux 5.6.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.9 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 202007-28063 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.9:bd07/30/2020:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1891451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892010] Re: [SRU] Fix acpi backlight issue on some thinkpads
Tested on 5.6.0-1023-oem, works as expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1892010 Title: [SRU] Fix acpi backlight issue on some thinkpads Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Bug description: [Impact] On some ThinkPads, the BIOS reported invalid acpi backlight implement . Then backlight can't be changed because OS use acpi backlight by default. [Fix] Check acpi backlight mode, disable it if invalid. [Test Case] Verified on 3 models of thinkpad include Intel/NV/AMD GPU with positive results. [Regression Potential] Low Most ThinkPads now use native backlight control by default. Check the false acpi mode correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1892010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
Moving to "Incomplete" while waiting for the test results from the test kernel referenced in comment #5. ** Changed in: ubuntu-power-systems Status: In Progress => Incomplete ** 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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: -- Problem Description -- drmgr command is failing while trying to open console for IBMi. Log snap shot: Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 Validating I/O DLPAR capability...yes. failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory failed to disable hotplug children Isolation failed for 3008 with -9001 Valid outstanding translations exist. ---Steps to Reproduce--- Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced == I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. Patch submitted upstream: https://lore.kernel.org/linuxppc- dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886827] Re: Machine hangs when doing a normal reboot
Hi, Since I wasn't able to build this commit, I used the deb's provided in Comment #36 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/comments/36) Result is success! Soft rebooting works normally with this build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
Possibly related to this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405 That bug focuses on the soft lockup but nouveau has come up as a factor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
Just upgraded to 16.04 LTS and that works as well. To be clear, for both 14.04 and 16.04, the proprietary NVIDIA drivers are available via the nvidia-304 package, but I'm not using those. The nouveau driver itself works on 14.04 and 16.04. FWIW, back when I tried running 18.04/20.04, when programs were hanging I checked dmesg and saw errors of the form "watchdog: BUG: soft lockup - CPU#3 stuck for 22s" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892714] Re: Microphone not working on HP Omen 17
Could you upload the dmesg of 5.8 kernel without dmic_detect=0? thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892714 Title: Microphone not working on HP Omen 17 Status in linux package in Ubuntu: Incomplete Bug description: I have the following laptop https://support.hp.com/us-en/product/omen- by-hp-17-cb-laptop-pc/26122176/document/c06411586 I cannot make the internal microphone to work. Sound->Input device gives no device list. Jack plug (pink) mic works. (The link says: HP Wide Vision HD Camera with integrated dual array digital microphone. So I guess this is the one and only internal microphone.) cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC285 cat /proc/asound/card1/codec* | grep Codec Codec: Nvidia GPU 92 HDMI/DP I guess the internal microphone is related to this "Realtek ALC285" codec. In alsa-base.conf I had to add "options snd-hda-intel dmic_detect=0" or otherwise my screen freezes soon after boot. I tried "options snd-hda-intel model=laptop-amic" and "model=laptop- dmic" and "model=auto". The "model=laptop-dmic" shows the device in "Sound->Input device" but it loops laptop's sound output into the input. OS: Ubuntu 20.04 uname -a: 5.4.0-42-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: croraf 1940 F pulseaudio /dev/snd/controlC0: croraf 1940 F pulseaudio /dev/snd/pcmC0D0p: croraf 1940 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-16 (281 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP OMEN by HP Laptop 17-cb0xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=685e7294-a202-48c4-b8a9-ec45d45bfd01 ro quiet splash pci=nommconf vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-07-13 (42 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8603 dmi.board.vendor: HP dmi.board.version: 45.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd09/05/2019:svnHP:pnOMENbyHPLaptop17-cb0xxx:pvr:rvnHP:rn8603:rvr45.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-cb0xxx dmi.product.sku: 7NG00EA#BED dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878946] Re: Cannot install proprietary NVIDIA driver
Did you manage to solve this. I have the same issue now.
Before it was working on my 5.4 kernel (Ubuntu 20.04), but then I
installed the 5.8 kernel to test something, and purged nvidia.
Now when I return to 5.4 kernel and want to switch to the same nvidia
that was working ("Using nvidia driver metapackage from nvidia-
driver-440 (proprietary, tested)") I get the error as in the attachment.
** Attachment added: "c2d81c46-3625-490a-8e39-4c345c642d96"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878946/+attachment/5405426/+files/c2d81c46-3625-490a-8e39-4c345c642d96
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1878946
Title:
Cannot install proprietary NVIDIA driver
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Confirmed
Bug description:
1) Distro: Kubuntu 20.04
2) Package version: nvidia-driver-440 version
"440.82+really.440.64-0ubuntu6"
I have started the driver management from system settings, selected
"Using NVIDIA driver metapackage from nvidia-driver-440 (proprietary,
tested).
3) What I expected to happen: The proprietary driver should be
installed. OpenCL should work (e.g. for darktable).
4) What happened instead: An error window pops up. Title: "Error wh...
changes", content: "pk-client-error-quark: Error while installing package:
>>neues libnidia-gl-440 (313)".
The additional drivers selector still shows "Using X.ORg X server - Nouveau
display driver from xserver-xorg-nouveau (open source)", although this package
is NOT installed.
Checking with muon, it shows that some nvidia 440 related packages have been
installed, but nvidia-driver-440 is shown with status 'corrupt' ('Defekt' in
German). The packages libnvidia-ifr1-440 and libnvidia-ifr1-440 are also shown
with status 'corrupt'.
Discover offers 'libnvidia-gl-440 version 440.82+really.440.64-0ubuntu6', but
that cannot be installed.
Trying to clear up the situation on the commandline results in:
"sudo apt install -f
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Abhängigkeiten werden korrigiert ... Fertig
Die folgenden zusätzlichen Pakete werden installiert:
libnvidia-gl-440 libnvidia-gl-440:i386
Die folgenden NEUEN Pakete werden installiert:
libnvidia-gl-440 libnvidia-gl-440:i386
0 aktualisiert, 2 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
63 nicht vollständig installiert oder entfernt.
Es müssen noch 0 B von 79,6 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 281 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
(Lese Datenbank ... 276127 Dateien und Verzeichnisse sind derzeit
installiert.)
Vorbereitung zum Entpacken von
.../libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb ...
Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 zu
/usr/lib/i386-linux-gnu/libGL.so.1.distrib durch nvidia-340
dpkg-divert: Fehler: Keine Übereinstimmung mit Paket
beim Entfernen von »Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 durch
libnvidia-gl-440«
»Umleitung von /usr/lib/i386-linux-gnu/libGL.so.1 zu
/usr/lib/i386-linux-gnu/libGL.so.1.distrib durch nvidia-340« gefunden
dpkg: Fehler beim Bearbeiten des Archivs
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb
(--unpack):
»neues libnvidia-gl-440:i386-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 2 zurück
Vorbereitung zum Entpacken von
.../libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb ...
Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1 zu
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib durch nvidia-340
dpkg-divert: Fehler: Keine Übereinstimmung mit Paket
beim Entfernen von »Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1
durch libnvidia-gl-440«
»Umleitung von /usr/lib/x86_64-linux-gnu/libGL.so.1 zu
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib durch nvidia-340« gefunden
dpkg: Fehler beim Bearbeiten des Archivs
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb
(--unpack):
»neues libnvidia-gl-440:amd64-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 2 zurück
Fehler traten auf beim Bearbeiten von:
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_i386.deb
/var/cache/apt/archives/libnvidia-gl-440_440.82+really.440.64-0ubuntu6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)"
[Sorry for this being partially in German]
darktable shows OpenCL as being unavailable, even if the nvidia kernel
modules (nvidia, nvidia_uvm, nvidia_modeset, nvidia_drm modeset=1) have been
loaded.
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1857271 Title: Focal 440.44-0ubuntu1 PRIME Sync not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 (Disco) Linux 5.4.6-050406-generic linux-firmware-1.184 mutter-3.32.2+git20190711-2ubuntu1~19.04.1 nvidia-driver-440: Installed: 440.44-0ubuntu1 Candidate: 440.44-0ubuntu1 Version table: *** 440.44-0ubuntu1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I've noticed screen tearing with the nvidia 440 driver on 5.4.x kernels. Typically, this is resolved by setting the xrandr option 'PRIME Synchronization' to '1', however, doing so with the above combination results in never being enabled. $ xrandr --output eDP-1-1 --set 'PRIME Synchronization' '1' $ xrandr --verbose | grep PRIME PRIME Synchronization: 0 PRIME Synchronization: 1 PRIME Synchronization: 1 PRIME Synchronization: 1 Reverting to Linux 5.0.0-37-generic resolve the issue, so I figured I'd raise it here first, however, it seems like a potential kernel regression issue if the only thing I'm changing is indeed the kernel version. Your input would be appreciated. I tried to figure out how to post a bug on the PPA, however, it seems bug creation is disabled on that PPA, so I ended up here. I've been testing newer kernel versions to get fixes for other problems with my hardware. Due to another package dependency, I'm stuck on disco for some pulseaudio bluetooth codec support, so I've been pushing forward the kernel, firmware and nvidia driver versions to get the other driver fixes. I realise this is not ideal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1857271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
It does affect linux 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] s390/cpum_cf, perf: change/add DFLT_CCERROR counter name
** Summary changed:
- [UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
+ [UBUNTU 20.04] s390/cpum_cf,perf: change/add DFLT_CCERROR counter name
** Summary changed:
- [UBUNTU 20.04] s390/cpum_cf,perf: change/add DFLT_CCERROR counter name
+ [UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter name
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hi, we have discovered the exact same issue using an HP Zbook 15 G6 and an up-to-date Ubuntu 20.04 installation. - With standard settings, the laptop freezes at the login screen - nomodeset does not stop the freezes from being happening - when using snd-hda-intel dmic_detect=0 as a kernel parameter, there are no freezes any more, but the mic isn't working A complete fix for this problem would be great. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861395] Re: system hang: i915 Resetting rcs0 for hang on rcs0
I'm a bit hesitant to mention this as it may be a red herring - and my
system has been stable and not hung due to pure coincidence - but I
installed an OEM kernel yesterday and haven't experienced my regularly
scheduled daily hang since:
sudo apt install linux-oem-20.04 linux-tools-oem-20.04
https://wiki.kubuntu.org/Kernel/OEMKernel explains more - they are
officially supported kernels apparently, and not prelaunch/beta in any
way.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861395
Title:
system hang: i915 Resetting rcs0 for hang on rcs0
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
System hangs, unknown cause, When this happens, the mouse pointer
still moves, but I can't do anything else with the keys or clicking in
the UI. Only recover I have found is a hard power-off
Last bit of kern.log below:
Jan 30 12:43:51 aries kernel: [ 6649.263031] i915 :00:02.0: GPU HANG:
ecode 9:1:0x, hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.263032] GPU hangs can indicate a bug
anywhere in the entire gfx stack, including userspace.
Jan 30 12:43:51 aries kernel: [ 6649.263033] Please file a _new_ bug report
on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 30 12:43:51 aries kernel: [ 6649.263033] drm/i915 developers can then
reassign to the right component if it's not a kernel issue.
Jan 30 12:43:51 aries kernel: [ 6649.263034] The GPU crash dump is required
to analyze GPU hangs, so please always attach it.
Jan 30 12:43:51 aries kernel: [ 6649.263034] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 30 12:43:51 aries kernel: [ 6649.264039] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.264778] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.265046] i915 :00:02.0: Resetting
chip for hang on rcs0
Jan 30 12:43:51 aries kernel: [ 6649.267018] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:51 aries kernel: [ 6649.267764] [drm:gen8_reset_engines [i915]]
*ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 0001}
Jan 30 12:43:59 aries kernel: [ 6657.262680] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:01 aries kernel: [ 6659.246609] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.246324] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:09 aries kernel: [ 6667.494008] show_signal_msg: 20 callbacks
suppressed
Jan 30 12:44:09 aries kernel: [ 6667.494011] GpuWatchdog[6827]: segfault at 0
ip 55fd01917ded sp 7f63043cc480 error 6 in chrome[55fcfd9dc000+7171000]
Jan 30 12:44:09 aries kernel: [ 6667.494017] Code: 48 c1 c9 03 48 81 f9 af 00
00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be
01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d a4 03 01 80
7d 8f 00
Jan 30 12:44:23 aries kernel: [ 6681.265885] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:25 aries kernel: [ 6683.245838] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:27 aries kernel: [ 6685.261749] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:29 aries kernel: [ 6687.245641] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:31 aries kernel: [ 6689.261618] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
Jan 30 12:44:51 aries kernel: [ 6709.260901] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 30 12:51:24 2020
InstallationDate: Installed on 2018-06-18 (591 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: Upgraded to focal on 2020-01-22 (8 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpb 115653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-06-18 (604 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same problem on Lenovo T480. Laptop wont boot when monitors are connected (I have 1 monitor over hdmi and 1 monitor over usbc-hdmi adapter). When i disconnect external monitors then everything works. Also same problem for Log out/Switch user. It cannot open login screen and freezes on loading. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886827] Re: Machine hangs when doing a normal reboot
Can't seem to compile this commit. Here are the commands I used: sudo apt-get -y install libncurses-dev flex bison openssl libssl-dev dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf sudo apt-get -y build-dep linux git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git cd linux git checkout -f b292b50b0efcc7095d8bf15505fba6909bb35dce cp /boot/config-$(uname -r) .config yes '' | make oldconfig make -j 17 deb-pkg LOCALVERSION=-custom Build fails with the following messages: --- dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i.git -b . subprocess returned exit status 1 make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 1 make: *** [Makefile:1495: deb-pkg] Error 2 --- Build environment: Ubuntu 20.04, 48GB RAM, 16 CPU's. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886827 Title: Machine hangs when doing a normal reboot Status in linux package in Ubuntu: Incomplete Bug description: Hi, When booting into kernel 4.15.0-99-generic or higher and also kernel 5.3.0-53-generic or higher, the system hangs when issuing the reboot command or CTRL-ALT-DEL from console with the following console messages: -- snip Reached target Final Step. Starting Reboot... < following message repeats indefinetely every 120 seconds > INFO: task systemd-shutdow:1 blocked for more than 120 seconds. Not tainted 4.15.0-99-generic #100 " echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. -- snip I did a git bisect procedure between kernels 4.15.0-96-generic and 4.15.0-99 and it reported the following: -- snip b52be79f3c6cc89bb3834c5174843e34f945f386 is the first bad commit commit b52be79f3c6cc89bb3834c5174843e34f945f386 -- snip Ubuntu version affected: Ubuntu 4.15.0-99.100-generic 4.15.18 First kernel package affected: linux-image-4.15.0-99-generic Necessary debug files will be attached as soon as possible. Quinn --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 09:55 seq crw-rw 1 root audio 116, 33 Jul 9 09:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/system-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/system-root ro rootflags=subvol=@ biosdevname=0 net.ifnames=0 nomodeset "dyndbg=file drivers/base/* +p" ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.18 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip disk plugdev sudo _MarkForUpload: True dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd05/05/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886827/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1888623] Re: Comet Lake-S requires new PCI id's for SATA/AHCI RAID
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888623 Title: Comet Lake-S requires new PCI id's for SATA/AHCI RAID Status in linux package in Ubuntu: Invalid Bug description: [Impact] Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers. [Fix] Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers. [test] [Regression Potential] Low. Just a PCI id for the sata/ahci raid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ---
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Description changed:
+ [Impact]
+ Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
+
+ [Fix]
+ Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
+
+ [test]
+
+ [Regression Potential]
+ Low. Just add a PCI id for the sata/ahci raid.
+
+ == Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Bug description:
[Impact]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[Fix]
Add Intel Comet Lake PCH-H PCI ID to the list of supported controllers.
[test]
[Regression Potential]
Low. Just add a PCI id for the sata/ahci raid.
== Original ==
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: change DFLT_CCERROR counter name
I just submitted a v2 SRU request for bionic only:
https://lists.ubuntu.com/archives/kernel-team/2020-August/thread.html#113072
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04
** Tags added: originate-from-1888311
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892288
Title:
Comet Lake PCH-H RAID not support on Ubuntu20.04
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
{ PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */
If Thinkstation P340 configured as RAID mode, It can not find any RAID volume
disk.
please update such support. Thanks.
Regards,
Jiqi.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892288/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
I need help! The solution from comment #66 and #96 doesn't work for me. I see elan0634 in acpidump, but elan_i2c or i2c_hid don't show up in lsmod. cat /sys/bus/acpi/devices has ELAN0634:00, but modalias is empty. No reaction on the touchpad. Ubuntu 20.04.1, latest BIOS update (DJCN18WW). Any suggestions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Changed in: pulseaudio (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890136] Re: Fix false-negative return value for rtnetlink.sh in kselftests/net
Eoan is no longer around, so the patches were applied to Bionic/hwe
instead. updated the targets to match this.
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Bionic)
Status: New => Fix Committed
** No longer affects: linux-hwe (Ubuntu Eoan)
** No longer affects: linux-hwe (Ubuntu Focal)
** No longer affects: linux-hwe (Ubuntu Groovy)
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => 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/1890136
Title:
Fix false-negative return value for rtnetlink.sh in kselftests/net
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-hwe package in Ubuntu:
New
Status in linux source package in Bionic:
Fix Committed
Status in linux-hwe source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
== Justification ==
All the sub test cases in rtnetlink.sh from kselftests/net were using
the same variable "ret" to store the return value of their test result,
and it will be reset to 0 in the beginning of each test.
This will cause false-negative result if the last case has passed.
Also, the kci_test_encap() test in rtnetlink.sh is actually composed by
two different sub-tests, kci_test_encap_vxlan() and kci_test_encap_fou()
Therefore we should check the test result of these two to avoid
false-negative result for this test case.
== Fixes ==
* c2a4d2747996 ("selftests: rtnetlink: correct the final return value for the
test")
* 72f70c159b53 ("selftests: rtnetlink: make kci_test_encap() return sub-test
result")
This issue is affecting our kernels from B to G, there is no such test
in X thus it can be skipped.
The first patch can be cherry-picked for E/F/G, but needs to be
backported for B/D as they're missing some tests.
The second patch can be cherry-picked for all affected kernels.
== Test ==
Manually tested. The test will fail as expected:
$ sudo ./rtnetlink.sh
PASS: policy routing
PASS: route get
echo $?
PASS: preferred_lft addresses have expired
PASS: promote_secondaries complete
PASS: tc htb hierarchy
PASS: gre tunnel endpoint
PASS: gretap
PASS: ip6gretap
PASS: erspan
PASS: ip6erspan
PASS: bridge setup
PASS: ipv6 addrlabel
PASS: set ifalias a28e0b75-bcc7-4b62-8f5a-381215796229 for test-dummy0
PASS: vrf
PASS: vxlan
FAIL: can't add fou port , skipping test
PASS: macsec
PASS: ipsec
PASS: ipsec_offload
PASS: bridge fdb get
PASS: neigh get
$ echo $?
1
== Regression Potential ==
Low, changes limited to testing tools. It's expected to see this test
failing after applying these patches, since it is reflecting the actual
test result.
== Original Bug Report ==
In this test, it uses ret to store the return value of each test.
However, this value will be reset to 0 in the beginning of each test.
In the end of this test, it will judge PASS/FAIL base on this value.
Thus this will cause false-negative in some cases.
Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan",
"erspan", "ip6gretap" failed with return value 255, but the return value will
soon be overridden with 0 if following test passed without any issue (I made
the test to print === RET $ret === line for debugging purpose):
PASS: policy routing
=== RET 0 ===
PASS: route get
=== RET 0 ===
PASS: preferred_lft addresses have expired
=== RET 0 ===
PASS: tc htb hierarchy
=== RET 0 ===
PASS: gre tunnel endpoint
=== RET 0 ===
PASS: gretap
=== RET 0 ===
Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ hoplimit TTL ]
[ encaplimit ELIM ]
[ tclass TCLASS ]
[ flowlabel FLOWLABEL ]
[ dscp inherit ]
[ fwmark MARK ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ erspan IDX ]
Where: ADDR
[Kernel-packages] [Bug 1892814] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1892814 Title: [Cambridge Silicon Radio] Bluetooth has multiple connectivity issues Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
