[Kernel-packages] [Bug 1875467] [NEW] Enable Invariant TSC Support
Public bug reported:
Microsoft would like to request two commits in all releases supported on
Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux
guest VMs. The invariant TSC means that the TSC continues at a fixed
rate regardless of the C-state or frequency of the processor (as long as
the processor remains in the ACPI S0 state).
These patches will allow guests to access the
HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR,
which then enables the InvariantTSC feature. After setting the
synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/
InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1875467
Title:
Enable Invariant TSC Support
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request two commits in all releases supported
on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux
guest VMs. The invariant TSC means that the TSC continues at a fixed
rate regardless of the C-state or frequency of the processor (as long
as the processor remains in the ACPI S0 state).
These patches will allow guests to access the
HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic
MSR, which then enables the InvariantTSC feature. After setting the
synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/
InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875467/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875236] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1875236 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875236 Title: Different kernel gives different RAM results Status in linux package in Ubuntu: Incomplete Bug description: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875236] Re: Different kernel gives different RAM results
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875236 Title: Different kernel gives different RAM results Status in linux package in Ubuntu: New Bug description: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874713] Re: Instabilities when returning from idle mode and delay when detecting Intel bluetooth [8087:07da] peripherals
Unfortunately the problem has not been completely solved, if I can put it that way. First (before) of all, I had already installed the Slimboot Battery 3 (an application for controlling battery consumption that uses tlp). So I used its configuration interfaces to define the USB blacklist and I also disabled the "Bluetooth device deactivation" ... after that I noticed that the reconnection time of the peripherals decreased a little ... However the return of the idle mode continued keeping erratic mouse behavior. So I uninstalled Slimboot and then removed all remnants of it manually, only the TLP was maintained, with the suggested configuration changes (I installed TLPGUI to check it out) ... Well, in the end, even so the problems continued. Finally I decided to remove all the TLP, TLPGUI and all its configuration traces, restarted the computer and, as in other times, continued the slight improvement of the keyboard and mouse connection time (in the login interface), but in the execution of the system, when returning from idle mode, mouse pointer continues to have a problem, slow and heavy locomotion, keyboard taking time to reconnect and failing in the first seconds after connection. For now I keep turning off and on again the bluetooth to return to normal. As the changes I made affected the initial behavior, I think the problem may be related, in fact, to the TLP. Perhaps a new installation of ubuntu can guarantee that this will resolve itself ... but I can't do that right now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874713 Title: Instabilities when returning from idle mode and delay when detecting Intel bluetooth [8087:07da] peripherals Status in linux package in Ubuntu: Confirmed Bug description: I have noticed instabilities in my bluetooth, mouse and keyboard, whenever I return to my desk I go back to using my notebook that went into idle mode. In addition, I realize that when turning on the computer and entering the Ubuntu login interface, there is a relevant delay before the bluetooth peripherals (mouse and keyboard) are detected. The time difference is very relevant compared to what happened at Eoan. Whenever I leave the idle mode, the mouse pointer became slow, with unstable and heavy movements. The keyboard also has erratic and strange functioning. I have an old sony vaio notebook and use a wireless keyboard and mouse communicating directly with the notebook's bluetooth without the need for adapters (dongle). The Mouse is an original sony vaio that I bought with the notebook, the keyboard, unlike, was recently purchased. For now the workaround solution I've been applying is to turn bluetooth off and on again, through the gnome configuration panel. In fact, whenever I do this, there is again a long delay before the peripherals are detected. I need to keep moving the mouse for about 10 to 20 seconds for detection to occur. I need to type on the keyboard many times until detection occurs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-bluetooth 3.34.1-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 08:46:37 2020 InstallationDate: Installed on 2020-01-28 (86 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: etm2253 F pulseaudio /dev/snd/pcmC0D0p: etm2253 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-28 (86 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: Sony Corporation SVS151290X NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=094e5e98-5bdc-4b9d-8345-a9ce693d8bc6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip firebird lp lpadmin lxd plugdev sambashare sudo tty uuidd video voice _MarkForUpload: True dmi.bios.date: 03/13/2013
[Kernel-packages] [Bug 1875459] 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/1875459 Title: System hangs when loading google maps on chrome with navi AMD GPU Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro quiet splash vt.handoff=1 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: X570 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875126] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1875126 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875126 Title: live iso 20.04 no wired network Status in linux package in Ubuntu: Incomplete Bug description: Booting from live cd could not establish network connection with wired network. Installing live CD (minimal install) had same result. Version 19.10 live CD wired network OK using motherboard network adapter tardis description: Desktop Computer product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 configuration: boot=normal chassis=desktop uuid=31433646-3635-3932-4541-4539 *-core description: Motherboard product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. physical id: 0 version: x.x *-firmware description: BIOS vendor: Award Software International, Inc. physical id: 0 version: FD date: 07/23/2010 size: 128KiB capacity: 1MiB capabilities: isa pci pnp apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification *-cpu description: CPU product: AMD Athlon(tm) II X4 645 Processor vendor: Advanced Micro Devices [AMD] physical id: 4 bus info: cpu@0 version: AMD Athlon(tm) II X4 645 Processor slot: Socket M2 size: 3100MHz capacity: 3100MHz width: 64 bits clock: 200MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save cpufreq *-cache:0 description: L1 cache physical id: a slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-cache:1 description: L3 cache physical id: c slot: External Cache size: 512KiB capacity: 512KiB capabilities: synchronous internal write-back configuration: level=3 *-cache description: L1 cache physical id: b slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-memory description: System Memory physical id: 2a slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 0 serial: None slot: A0 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:1 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 1 serial: None slot: A1 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:2 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 2 serial: None slot: A2 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:3 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 3 serial: None
[Kernel-packages] [Bug 1875126] Re: live iso 20.04 no wired network
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875126 Title: live iso 20.04 no wired network Status in linux package in Ubuntu: Incomplete Bug description: Booting from live cd could not establish network connection with wired network. Installing live CD (minimal install) had same result. Version 19.10 live CD wired network OK using motherboard network adapter tardis description: Desktop Computer product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 configuration: boot=normal chassis=desktop uuid=31433646-3635-3932-4541-4539 *-core description: Motherboard product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. physical id: 0 version: x.x *-firmware description: BIOS vendor: Award Software International, Inc. physical id: 0 version: FD date: 07/23/2010 size: 128KiB capacity: 1MiB capabilities: isa pci pnp apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification *-cpu description: CPU product: AMD Athlon(tm) II X4 645 Processor vendor: Advanced Micro Devices [AMD] physical id: 4 bus info: cpu@0 version: AMD Athlon(tm) II X4 645 Processor slot: Socket M2 size: 3100MHz capacity: 3100MHz width: 64 bits clock: 200MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save cpufreq *-cache:0 description: L1 cache physical id: a slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-cache:1 description: L3 cache physical id: c slot: External Cache size: 512KiB capacity: 512KiB capabilities: synchronous internal write-back configuration: level=3 *-cache description: L1 cache physical id: b slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-memory description: System Memory physical id: 2a slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 0 serial: None slot: A0 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:1 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 1 serial: None slot: A1 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:2 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 2 serial: None slot: A2 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:3 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 3 serial: None slot: A3 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-pci:0 description: Host bridge product: RS880 Host Bridge vendor: Advanced Micro Devices, Inc. [AMD] physical id: 100 bus info: pci@:00:00.0 version: 00 width: 64 bits clock: 66MHz configuration: latency=32 *-pci:0 description: PCI bridge product: RS780 PCI to PCI bridge (ext gfx port 0)
[Kernel-packages] [Bug 1875459] [NEW] System hangs when loading google maps on chrome with navi AMD GPU
Public bug reported: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro quiet splash vt.handoff=1 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: X570 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875459 Title: System hangs when loading google maps on chrome with navi AMD GPU Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro
[Kernel-packages] [Bug 1875456] [NEW] Azure diagnostic/serviceability improvement
Public bug reported:
Microsoft would like to request the inclusion of commits in all releases
supported on Azure. These commits will enable reporting 4 Kbytes of
dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information, so
that we can automatically get a rich picture of Linux panics in Azure.
This will limit the need get serial console logs or other steps to
manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during system
crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg get
dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1875456
Title:
Azure diagnostic/serviceability improvement
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request the inclusion of commits in all
releases supported on Azure. These commits will enable reporting 4
Kbytes of dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information,
so that we can automatically get a rich picture of Linux panics in
Azure. This will limit the need get serial console logs or other
steps to manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during
system crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg
dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg
get dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875126] [NEW] live iso 20.04 no wired network
You have been subscribed to a public bug: Booting from live cd could not establish network connection with wired network. Installing live CD (minimal install) had same result. Version 19.10 live CD wired network OK using motherboard network adapter tardis description: Desktop Computer product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 configuration: boot=normal chassis=desktop uuid=31433646-3635-3932-4541-4539 *-core description: Motherboard product: GA-890GPA-UD3H vendor: Gigabyte Technology Co., Ltd. physical id: 0 version: x.x *-firmware description: BIOS vendor: Award Software International, Inc. physical id: 0 version: FD date: 07/23/2010 size: 128KiB capacity: 1MiB capabilities: isa pci pnp apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification *-cpu description: CPU product: AMD Athlon(tm) II X4 645 Processor vendor: Advanced Micro Devices [AMD] physical id: 4 bus info: cpu@0 version: AMD Athlon(tm) II X4 645 Processor slot: Socket M2 size: 3100MHz capacity: 3100MHz width: 64 bits clock: 200MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save cpufreq *-cache:0 description: L1 cache physical id: a slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-cache:1 description: L3 cache physical id: c slot: External Cache size: 512KiB capacity: 512KiB capabilities: synchronous internal write-back configuration: level=3 *-cache description: L1 cache physical id: b slot: Internal Cache size: 128KiB capacity: 128KiB capabilities: synchronous internal write-back configuration: level=1 *-memory description: System Memory physical id: 2a slot: System board or motherboard size: 16GiB *-bank:0 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 0 serial: None slot: A0 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:1 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 1 serial: None slot: A1 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:2 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 2 serial: None slot: A2 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-bank:3 description: DIMM 1333 MHz (0.8 ns) product: None vendor: None physical id: 3 serial: None slot: A3 size: 4GiB width: 64 bits clock: 1333MHz (0.8ns) *-pci:0 description: Host bridge product: RS880 Host Bridge vendor: Advanced Micro Devices, Inc. [AMD] physical id: 100 bus info: pci@:00:00.0 version: 00 width: 64 bits clock: 66MHz configuration: latency=32 *-pci:0 description: PCI bridge product: RS780 PCI to PCI bridge (ext gfx port 0) vendor: Advanced Micro Devices, Inc. [AMD] physical id: 2 bus info: pci@:00:02.0 version: 00 width: 32 bits clock: 33MHz capabilities: pci pm pciexpress msi ht normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:24 ioport:e000(size=4096) memory:fdd0-fdef ioport:c000(size=536870912) *-pci description: PCI bridge product: Navi
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: Triaged Status in linux-raspi2-5.3 package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in netplan.io source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in netplan.io source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: Triaged Status in linux-raspi2-5.3 source package in Focal: New Status in netplan.io source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
(But if you use any kernel version < 5.4, you don't get the sweet ability to set the battery charge threshold: https://www.reddit.com/r/linuxhardware/comments/g8kpee/psa_kernel_54_added_the_ability_to_set_a_battery/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
@rewihaar: I'm glad to kow this workaround worked for you. Apparently
the problem affecting the UX{3,4,5}33 and UX{3,4,5}34 have a different
root cause and should be reported separately. You can find more info on
the issue affecting your model in the following bugs:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852 è
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485 or even
this AskUbuntu question: https://askubuntu.com/questions/1032543/no-
sound-in-ubuntu-18-04-after-rebooting-from-windows-10. Kernel 4.19 and
5.0 are known to work well with those models.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1850439
Title:
No sound on ASUS UX534FT
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hi,
after instal Ubuntu in dual boot alongside Windows 10, I've realised
there is no sound coming out of mine new ASUS Zenbook 15 UX534FT-
AA024R in Ubuntu. In Windows there is no problem. Found this topic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had
the same problem with driver for Realtek ALC294 which is also mine
sound card. But even with this fix it is not working on UX534FT. Can
you please add fix also for this newer model?
Description: Ubuntu 18.04.3 LTS
Release: 18.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 15:11:25 2019
InstallationDate: Installed on 2019-10-29 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1509717] [lvm2/bionic] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for bionic for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Committed Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to VM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874519] Re: ZFS installation on Raspberry Pi is problematic
Just to clarify: I'm not suggesting ZFS be included by default on the Raspberry Pi. I'm saying that it should be possible to install ZFS on the Raspberry Pi without jumping through so many hoops. I appreciate this is a tricky one though, since presumably there are other arm64 platforms that have more RAM. Perhaps a note in the release notes about the required workaround, i.e. manually install zfs-dkms using apt? (In 19.10 it was a dependency of zfsutils-linux). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: New Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875437] Re: WIFI stops working and system breaks
This is the output of 'dmesg | grep ath10' when the problem happens [4.511597] ath10k_pci :3b:00.0: enabling device ( -> 0002) [4.515050] ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [4.794546] ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 [4.794548] ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [4.794952] ath10k_pci :3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [4.859617] ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [4.957186] ath10k_pci :3b:00.0: unsupported HTC service id: 1536 [4.976154] ath10k_pci :3b:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [5.067954] ath10k_pci :3b:00.0 wlp59s0: renamed from wlan0 [ 645.565783] ath10k_pci :3b:00.0: unsupported HTC service id: 1536 [ 7807.422028] ath10k_pci :3b:00.0: failed to receive scan abortion completion: timed out [ 7807.422035] ath10k_pci :3b:00.0: failed to stop scan: -110 [ 7807.422038] ath10k_pci :3b:00.0: failed to start hw scan: -110 [ 7810.497976] ath10k_pci :3b:00.0: wmi command 20482 timeout, restarting hardware [ 7810.497993] ath10k_pci :3b:00.0: failed to delete WMI vdev 1: -11 [ 7810.498194] ath10k_pci :3b:00.0: failed to set 2g txpower 26: -108 [ 7810.498199] ath10k_pci :3b:00.0: failed to setup tx power 26: -108 [ 7810.498202] ath10k_pci :3b:00.0: failed to recalc tx power: -108 [ 7810.498231] ath10k_pci :3b:00.0: failed to set inactivity time for vdev 0: -108 [ 7810.498234] ath10k_pci :3b:00.0: failed to setup powersave: -108 [ 7813.553447] ath10k_pci :3b:00.0: failed to receive initialized event from target: [ 7816.577730] ath10k_pci :3b:00.0: failed to receive initialized event from target: [ 7816.577732] ath10k_warn: 1 callbacks suppressed [ 7816.577733] ath10k_pci :3b:00.0: failed to wait for target init: -110 [ 7816.578915] ath10k_pci :3b:00.0: failed to set inactivity time for vdev 0: -108 [ 7816.578916] ath10k_pci :3b:00.0: failed to setup powersave: -108 [ 7816.578918] ath10k_pci :3b:00.0: failed to set PS Mode 0 for vdev 0: -108 [ 7816.578919] ath10k_pci :3b:00.0: failed to setup powersave: -108 [ 7816.578920] ath10k_pci :3b:00.0: failed to setup ps on vdev 0: -108 [ 7816.579115] ath10k_pci :3b:00.0: failed to flush transmit queue (skip 1 ar-state 2): 1250 [ 7816.579245] ath10k_pci :3b:00.0: failed to delete peer c6:b4:22:66:7d:b6 for vdev 0: -108 [ 7816.579289] Modules linked in: msr ccm thunderbolt rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common ecdh_generic ecc videodev mc x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi nvidia_uvm(OE) crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core nls_iso8859_1 snd_soc_acpi_intel_match aesni_intel snd_soc_acpi joydev snd_soc_core crypto_simd cryptd glue_helper snd_compress ac97_bus snd_pcm_dmaengine mei_hdcp nvidia_drm(POE) intel_rapl_msr nvidia_modeset(POE) intel_cstate dell_laptop ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_perf snd_rawmidi ath10k_pci ath10k_core snd_seq dell_wmi [ 7816.579614] ath10k_pci :3b:00.0: failed to recalculate rts/cts prot for vdev 0: -108 [ 7816.579615] ath10k_pci :3b:00.0: failed to set cts protection for vdev 0: -108 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875437 Title: WIFI stops working and system breaks Status in linux package in Ubuntu: Confirmed Bug description: I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and 20) for the last two years. Everything work fine except for the wifi, which randomly stops working. Sometimes I can just turn off and on the wifi and it comes to work until next random crash. However, other times, when it happens, I cannot turn off wifi, it seems like the system breaks, I have to hard shutdown the laptop and after boot it works again. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrolarben 1800 F pulseaudio
[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel
same dummy output to laptop speaker problem here as well. manipulated alsa mixer, force reloaded alsa, purged and reinstalled alsa as well. nothing happened. it started after the network upgrade from 19.10. it was working well before upgrade. still working fine in earphones though. i an on Toshiba Satellite L500 machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Incomplete Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@arighi Unfortunately hard crashes still occur with the test kernel you posed in #57. dmesg: [ 1955.974958] i915 :00:02.0: GPU HANG: ecode 11:1:0xfffe, in Xorg [1073], hang on rcs0 [ 1955.976105] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 1991.965817] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 1999.965828] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 2007.965803] i915 :00:02.0: Resetting rcs0 for hang on rcs0 i915 error log attached. ** Attachment added: "i915.error.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5361777/+files/i915.error.txt ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1875437] 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/1875437 Title: WIFI stops working and system breaks Status in linux package in Ubuntu: Confirmed Bug description: I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and 20) for the last two years. Everything work fine except for the wifi, which randomly stops working. Sometimes I can just turn off and on the wifi and it comes to work until next random crash. However, other times, when it happens, I cannot turn off wifi, it seems like the system breaks, I have to hard shutdown the laptop and after boot it works again. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrolarben 1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:19:56 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=UUID=1a07689c-3362-41b2-b2e1-ae28e49f5384 ro quiet splash acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep mitigations=off 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875437] [NEW] WIFI stops working and system breaks
Public bug reported: I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and 20) for the last two years. Everything work fine except for the wifi, which randomly stops working. Sometimes I can just turn off and on the wifi and it comes to work until next random crash. However, other times, when it happens, I cannot turn off wifi, it seems like the system breaks, I have to hard shutdown the laptop and after boot it works again. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrolarben 1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:19:56 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=UUID=1a07689c-3362-41b2-b2e1-ae28e49f5384 ro quiet splash acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep mitigations=off 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug drivers focal wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875437 Title: WIFI stops working and system breaks Status in linux package in Ubuntu: Confirmed Bug description: I have a dell XPS 15 9570 laptop. I have been using Ubuntu (18, 19 and 20) for the last two years. Everything work fine except for the wifi, which randomly stops working. Sometimes I can just turn off and on the wifi and it comes to work until next random crash. However, other times, when it happens, I cannot turn off wifi, it seems like the system breaks, I have to hard shutdown the laptop and after boot it works again. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrolarben 1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:19:56 2020 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=UUID=1a07689c-3362-41b2-b2e1-ae28e49f5384 ro quiet splash acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep mitigations=off 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1873384] Re: Headphone has no sound out
Maybe OP can do a similar thing on his audio selection KDE settings or similar? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873384 Title: Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
Hi Hui, Thank you for reviewing my bug report so quickly. When I gathered the original information in my bug report, standard analog stereo speakers were connected to the host system's 3.5mm analog audio output jack. The first test tone played by the bug report generator was heard via these speakers, however the second test tone was not. The test tone was the first and only time I have had successful audio output while using Ubuntu on this system. I do not know if it helps, but prior to installing Ubuntu I had Windows 10 installed and the audio output worked properly with the same external speakers. This would appear to confirm that host system hardware and external speakers are working properly. The problem only occurs when trying to use any version of Ubuntu (18.04, 19.10 and 20.20) Please let me know if I can provide any additional information or logs to investigate the problem further, and thank you for your help! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails
Hello Thadeu, or anyone else affected, Accepted systemd into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.8 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- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. 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. ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873384] Re: Headphone has no sound out
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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/1873384 Title: Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873384] Re: Headphone has no sound out
On Ubuntu 20.04 I experience similar issue as diagnosed by @prayerholmes . Selecting on the pop-up headset breaks the audio (but the microphone works!). After changing on settings->audio the input from `headset microphone - built-in audio` to `Internal microphone - built-in audio` and then back to `headset microphone - built-in audio` it works ok. My computer is a Dell XPS 9550. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873384 Title: Headphone has no sound out Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Computer: Dell inspiron 15 5577 Gaming intel i5 7300HQ version System: Kubuntu 20.04 Bug: Plug-in headphone has no sound out, meanwhile computer's speaker is okay when unplugged the headphone. Additional information: Headphone is okay when kubuntu 18.04.3 is installed on the computer. Alsamixer is checked and headphone are not mute. Headphone plugin state can be correctly detected, and speaker can automatically mute until headphone unplugged. External usb soundcard is usable with headphone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.12 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 11:14:43 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sherlockholmes 1242 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416) MachineType: Dell Inc. Inspiron 5577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 090HMC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874543] Re: Artifacts when connected to an external 4K display
Reconfiguring X made this go away ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874543 Title: Artifacts when connected to an external 4K display Status in linux package in Ubuntu: Invalid Bug description: I get artifacts when I connect my laptop (Lenovo X1 7th Gen) to an external 4k monitor via usb-c->DP. See the attached screenshot. This happened after I upgraded to ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 22:35:27 2020 DistUpgraded: 2020-04-23 22:04:58,240 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-48-generic, x86_64: installed nvidia, 440.64, 5.4.0-26-generic, x86_64: installed v4l2loopback, 0.12.3, 5.3.0-48-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2019-10-07 (199 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
** Tags added: hwe-networking-ethernet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX: 8a758ee6ad00 RBX: b4d69160 RCX:
[Kernel-packages] [Bug 1871812] Re: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871812 Title: Can not see the storage with Intel RAID On mode enabled on Intel Comet Lake Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: === SRU Justification === [Impact] ID is missing so the devcie isn't bound to AHCI driver. Without the driver, we can't check the existence of remapped NVMe. [Fix] Add one missing ID. [Test] Use lspci to see if the device is bound to ahci driver. Test positive after applying the patch. [Regression Potential] Low. This is a trivial fix which limits to one specific device. === Original Bug Report === Can not see the storage on Dell Latitude 5310 with Intel RAID On mode enabled in the BIOS. The Dell Latitude 5310 is an Intel Comet Lake platform, which missing the ID[1] in the kernel. [1] https://lore.kernel.org/lkml/20191128081041.6948-1-jian- h...@endlessm.com/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1536 F pulseaudio CasperVersion: 1.442 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 09:55:02 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. Latitude 5310 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- toram RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.12:bd01/09/2020:svnDellInc.:pnLatitude5310:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5310 dmi.product.sku: 099F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1871812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I'd be happy to assist in debugging this, is there anything I can do to help track it down? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX:
[Kernel-packages] [Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
The workaround is to blacklist hid_logitech_hidpp and hid_logitech_dj modules by adding /etc/modprobe.d/blacklist-hid_logitech.conf with this content: ``` blacklist hid_logitech_hidpp blacklist hid_logitech_dj ``` and running `update-initramfs -u -k all`. After reboot, the buttons start working as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode Status in linux package in Ubuntu: Confirmed Bug description: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-lowlatency N/A linux-backports-modules-5.4.0-26-lowlatency N/A linux-firmware 1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1875408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Hi Michal, on my Zenbook I stopped using the open source drivers but using the 5.3.0-26-generic kernel and the Nvidia 435 driver both Ubuntu and the Microphone work well. Il giorno lun 27 apr 2020 alle ore 16:13 Michal <1850...@bugs.launchpad.net> ha scritto: > Thanks for the tip on the Nvidia drivers. I can confirm that switching > to the open source driver for GeForce MX250 (on my Asus UX334F) helped > and my mic and headphones are working. > > The sounds is indeed 'metallic' without the headphones. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1856460). > https://bugs.launchpad.net/bugs/1850439 > > Title: > No sound on ASUS UX534FT > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, > > after instal Ubuntu in dual boot alongside Windows 10, I've realised > there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- > AA024R in Ubuntu. In Windows there is no problem. Found this topic > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had > the same problem with driver for Realtek ALC294 which is also mine > sound card. But even with this fix it is not working on UX534FT. Can > you please add fix also for this newer model? > > Description: Ubuntu 18.04.3 LTS > Release: 18.04 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 > ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 29 15:11:25 2019 > InstallationDate: Installed on 2019-10-29 (0 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: linux-signed-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875408] 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/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode Status in linux package in Ubuntu: Confirmed Bug description: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-lowlatency N/A linux-backports-modules-5.4.0-26-lowlatency N/A linux-firmware 1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1875408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Thanks for the tip on the Nvidia drivers. I can confirm that switching to the open source driver for GeForce MX250 (on my Asus UX334F) helped and my mic and headphones are working. The sounds is indeed 'metallic' without the headphones. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Also affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Eoan: Confirmed Status in linux-raspi2 source package in Focal: New Bug description: Desciption changed: Raspberry Pi 3 network partially dies (transmission doesn't work, reception still does) shortly after a burst of network load over IPv6, when IPv6 connectivity is provided by a tunnel from tunnelbroker.net. The triggering load is typically an HTTP(S) download, and replication can be done without actually saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 GB, usually withinthe first 1 GB of traffic) Replication is 100% as long as _all_ of the following conditions are met - 6in4 tunnel to HE.net set up with netplan - ipv6 rules applied (netfilter-persistent) - ipv6 forwarding enabled (edit /etc/sysctl.conf) kern.log message that appears after a while: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_domain_irq+0x70/0xc0
[Kernel-packages] [Bug 1875408] [NEW] Logitech G700s extra G buttons don't work in wireless mode
Public bug reported: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-lowlatency N/A linux-backports-modules-5.4.0-26-lowlatency N/A linux-firmware 1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode Status in linux package in Ubuntu: New Bug description: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine:
[Kernel-packages] [Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
** Attachment added: "Output of `libinput list-devices` when the mouse is wired" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+attachment/5361704/+files/libinput_wired.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode Status in linux package in Ubuntu: New Bug description: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lastique 2015 F pulseaudio /dev/snd/controlC0: lastique 2015 F pulseaudio /dev/snd/controlC2: lastique 2015 F pulseaudio /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: # Prevents "gave up waiting for suspend/resume device" timeout on boot RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-lowlatency N/A linux-backports-modules-5.4.0-26-lowlatency N/A linux-firmware 1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1875408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875408] Re: Logitech G700s extra G buttons don't work in wireless mode
** Attachment added: "Output of `libinput list-devices` when the mouse is wireless" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875408/+attachment/5361705/+files/libinput_wireless.txt ** Description changed: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. + + This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not + present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC3: lastique 2015 F pulseaudio - /dev/snd/controlC0: lastique 2015 F pulseaudio - /dev/snd/controlC2: lastique 2015 F pulseaudio - /dev/snd/controlC1: lastique 2015 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC3: lastique 2015 F pulseaudio + /dev/snd/controlC0: lastique 2015 F pulseaudio + /dev/snd/controlC2: lastique 2015 F pulseaudio + /dev/snd/controlC1: lastique 2015 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 27 17:09:22 2020 HibernationDevice: - # Prevents "gave up waiting for suspend/resume device" timeout on boot - RESUME=none + # Prevents "gave up waiting for suspend/resume device" timeout on boot + RESUME=none InstallationDate: Installed on 2015-05-01 (1822 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-lowlatency root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-lowlatency N/A - linux-backports-modules-5.4.0-26-lowlatency N/A - linux-firmware 1.187 + linux-restricted-modules-5.4.0-26-lowlatency N/A + linux-backports-modules-5.4.0-26-lowlatency N/A + linux-firmware 1.187 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875408 Title: Logitech G700s extra G buttons don't work in wireless mode Status in linux package in Ubuntu: New Bug description: Starting with Linux kernel 5.4.0, extra buttons G4-G10 on the side and top of the Logitech G700s mouse don't work when the mouse is connected over the wireless dongle. The buttons do work in wired connection. The problem is not present with kernel 5.3.18. It is present with 5.4.28, 5.5.19, 5.6.7. In wireless mode, the `libinput list-devices` command does not show additional input devices, including the keyboard device, associated with the mouse. Only the "Logitech G700s" pointer device is shown. This problem appeared after upgrading Kubuntu 19.10 to 20.04. It was not present on 19.10. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=207465 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.26.32 ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30 Uname: Linux 5.4.0-26-lowlatency x86_64 NonfreeKernelModules:
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
Looks like the ssid_scan= is being addressed upstream https://github.com/CanonicalLtd/netplan/pull/132 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: Triaged Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware-raspi2 source package in Eoan: New Status in linux-raspi2-5.3 source package in Eoan: New Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: Triaged Status in linux-raspi2-5.3 source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874519] Re: ZFS installation on Raspberry Pi is problematic
Adding zfs to the pi kernel was discussed and rejected in the past: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852119 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: New Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875355] Re: Internet is being slow after todays upgrade
Thanks You-Sheng but looks like some issue with my wifi provider. I've rebooted the procs and it's fixed. My bad. ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361635/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361634/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361633/+files/PulseList.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361632/+files/ProcModules.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361619/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361620/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361621/+files/Dependencies.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361622/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361623/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361625/+files/Lsusb.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361627/+files/Lsusb-v.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361624/+files/Lspci-vt.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361626/+files/Lsusb-t.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361628/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361629/+files/ProcCpuinfoMinimal.txt ** Description changed: Hello, I've ran update / upgrade this morning. My internet has been locked to 1.5MBPS after that. I'm getting 55 MBPS on my other devices but not on Ubuntu machine. - - 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 - NonfreeKernelModules: nvidia_modeset nvidia - ApportVersion: 2.20.11-0ubuntu27 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: vinayakm 1873 F pulseaudio - /dev/snd/controlC0: vinayakm 1873 F pulseaudio - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - Date: Mon Apr 27 13:41:56 2020 - InstallationDate: Installed on 2020-02-27 (59 days ago) - InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) - MachineType: LENOVO 20QVS0KL00 - ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=11044477-feb2-49bb-9ef1-0ddacca9a362 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 - SourcePackage: linux - UpgradeStatus: Upgraded to focal on 2020-03-27 (30 days ago) - dmi.bios.date: 01/20/2020 - dmi.bios.vendor: LENOVO - dmi.bios.version: N2OET42W (1.29 ) - dmi.board.asset.tag: Not Available - dmi.board.name: 20QVS0KL00 - dmi.board.vendor: LENOVO - dmi.board.version: SDK0J40697 WIN - dmi.chassis.asset.tag: No Asset Information - dmi.chassis.type: 10 - dmi.chassis.vendor: LENOVO - dmi.chassis.version: None - dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVS0KL00:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVS0KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: - dmi.product.family: ThinkPad X1 Extreme 2nd - dmi.product.name: 20QVS0KL00 - dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd - dmi.product.version: ThinkPad X1 Extreme 2nd - dmi.sys.vendor: LENOVO ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361630/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875355 Title: Internet is being slow after todays upgrade Status in linux package in Ubuntu: Invalid Bug description: Hello, I've
[Kernel-packages] [Bug 1875355] Re: Internet is being slow after todays upgrade
Please find in your /var/log/apt/history.log, what have been updated actually? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875355 Title: Internet is being slow after todays upgrade Status in linux package in Ubuntu: Invalid Bug description: Hello, I've ran update / upgrade this morning. My internet has been locked to 1.5MBPS after that. I'm getting 55 MBPS on my other devices but not on Ubuntu machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875355] Re: Internet is being slow after todays upgrade
** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361618/+files/AlsaInfo.txt ** Changed in: linux (Ubuntu) Status: New => Invalid ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+attachment/5361636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875355 Title: Internet is being slow after todays upgrade Status in linux package in Ubuntu: Invalid Bug description: Hello, I've ran update / upgrade this morning. My internet has been locked to 1.5MBPS after that. I'm getting 55 MBPS on my other devices but not on Ubuntu machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875355] [NEW] Internet is being slow after todays upgrade
Public bug reported: Hello, I've ran update / upgrade this morning. My internet has been locked to 1.5MBPS after that. I'm getting 55 MBPS on my other devices but not on Ubuntu machine. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vinayakm 1873 F pulseaudio /dev/snd/controlC0: vinayakm 1873 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 13:41:56 2020 InstallationDate: Installed on 2020-02-27 (59 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QVS0KL00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=11044477-feb2-49bb-9ef1-0ddacca9a362 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-27 (30 days ago) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVS0KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVS0KL00:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVS0KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVS0KL00 dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875355 Title: Internet is being slow after todays upgrade Status in linux package in Ubuntu: New Bug description: Hello, I've ran update / upgrade this morning. My internet has been locked to 1.5MBPS after that. I'm getting 55 MBPS on my other devices but not on Ubuntu machine. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vinayakm 1873 F pulseaudio /dev/snd/controlC0: vinayakm 1873 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 13:41:56 2020 InstallationDate: Installed on 2020-02-27 (59 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: LENOVO 20QVS0KL00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=11044477-feb2-49bb-9ef1-0ddacca9a362 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-27 (30 days ago) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVS0KL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QVS0KL00:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVS0KL00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QVS0KL00 dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452318] Re: Faulty behavior when resuming from suspend
I still have this bug raising up after 10~20 suspend/resume same session (16.04.6 XPS13-L322X) since Trusty. ** Attachment added: "Capture du 2020-04-27 11-39-58.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452318/+attachment/5361604/+files/Capture%20du%202020-04-27%2011-39-58.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452318 Title: Faulty behavior when resuming from suspend Status in linux package in Ubuntu: Fix Released Bug description: Waking from suspend, everything seems normal, except the graphical elements and text on my desktop are not drawn properly. Sometimes, moving the mouse over icons can cause them to be redrawn, sometimes not. It appears not to matter how I initiate the suspend (e.g. by closing laptop lid, or by calling pm-suspend explicitly) and it appears not to matter whether I am using an external display or the laptop's own screen. All other hardware appears to be working, and I can restart the laptop by clicking where the icons ought to be. The only symptom seems to be that the drawing does not happen correctly. I'm not sure what additional information I should provide to help diagnose the problem, so please advise me. Also, if this is more likely to be a xfce issue, then please change the package on the bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 6 17:17:51 2015 InstallationDate: Installed on 2015-05-04 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
If you increase the volume the sound is not as clean as on windows, but the mic is working fine. Il giorno lun 27 apr 2020 alle ore 13:01 Taha Soomro < 1850...@bugs.launchpad.net> ha scritto: > Interesting comment soulsacrifice. Is your mic working? and what do you > mean by 'metallic' sound? > > I wonder if this will work on UX534. Can someone test it? I dont want to > reinstall :) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1856460). > https://bugs.launchpad.net/bugs/1850439 > > Title: > No sound on ASUS UX534FT > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, > > after instal Ubuntu in dual boot alongside Windows 10, I've realised > there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- > AA024R in Ubuntu. In Windows there is no problem. Found this topic > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had > the same problem with driver for Realtek ALC294 which is also mine > sound card. But even with this fix it is not working on UX534FT. Can > you please add fix also for this newer model? > > Description: Ubuntu 18.04.3 LTS > Release: 18.04 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 > ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 29 15:11:25 2019 > InstallationDate: Installed on 2019-10-29 (0 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: linux-signed-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
With clarifications from IHV, Killer 1650s is now correctly enabled with perfect performance. Will continue to try all the versions in the PPA once they're built. ** Tags added: oem-priority originate-from-1872037 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (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/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: New Status in linux-oem-osp1 source package in Focal: New Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration [ 11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid [ 11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match [ 11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel [ 11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp [ 11.489555] iwlwifi :00:14.3: 0x1AFE14FD | flow_handler [ 11.489635] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489643] iwlwifi :00:14.3: Status: 0x, count: 7 [ 11.489652] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 11.489659] iwlwifi :00:14.3: 0x | umac branchlink1 [ 11.489666] iwlwifi :00:14.3: 0x80465E6A | umac branchlink2 [ 11.489674] iwlwifi :00:14.3: 0x | umac interruptlink1 [ 11.489681] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 11.489688] iwlwifi
[Kernel-packages] [Bug 1867220] Re: Assignment of VDEV Somtimes Fails using Intel QAT
** Also affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure-4.15 (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux-azure-4.15 (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1867220 Title: Assignment of VDEV Somtimes Fails using Intel QAT Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-azure source package in Eoan: In Progress Status in linux-azure-4.15 source package in Eoan: Invalid Bug description: The QAT is a PCIe device which supports SR-IOV. It is used to accelerate the crypto and compression operations by hardware. There is additional info for this hardware on the Intel website: https://www.intel.com/content/www/us/en/products/docs/network-io/ethernet/10-25-40-gigabit-adapters/quickassist-adapter-for-servers.html https://01.org/intel-quick-assist-technology On Ubuntu, when the QAT device is enabled with SR-IOV, one device will have 16 VFs. When we assign the VDEV to Linux VM, sometimes, it will fail but sometimes it will not. This issue was debugged and is resolved by applying three patches and removing some buggy code that was added as SAUCE. The following three patches are needed: f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers be700103efd1 PCI: hv: Detect and fix Hyper-V PCI domain number collision 6ae91579061c PCI: hv: Add __aligned(8) to struct retarget_msi_interrupt Also, revert the patch Revert "PCI: hv: Make sure the bus domain is really unique", i.e. the line "if (list_empty(>children)) hbus->sysdata.domain = desc->ser" in new_pcichild_device() should be completely removed. The patch “UBUNTU: SAUCE: pci-hyperv: Use only 16 bit integer for PCI domai” is also pointless now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1867220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
That is because there is no available output device on your machine, please plug sth into the lineout jack, and choose the lineout from gnome-sound-setting, then it will not show dummy audio. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Interesting comment soulsacrifice. Is your mic working? and what do you mean by 'metallic' sound? I wonder if this will work on UX534. Can someone test it? I dont want to reinstall :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1875199 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: New Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875328] 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/1875328 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: package is not updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumik 1605 F pulseaudio /dev/snd/controlC0: soumik 1605 F pulseaudio Date: Mon Apr 27 14:56:52 2020 DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=a9130fd4-73a5-4712-978c-1722c4e7915c InstallationDate: Installed on 2016-07-06 (1391 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bc2:2100 Seagate RSS LLC FreeAgent Go Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H310M S2 2.0 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=UUID=42b2ccfe-e263-4ec6-90ba-50fb0225cae1 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.21 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: H310M S2 2.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd03/08/2019:svnGigabyteTechnologyCo.,Ltd.:pnH310MS22.0:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH310MS22.0:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: H310M S2 2.0 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
You have been subscribed to a public bug: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 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: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [HDA-Intel - HDA Intel PCH, playback] No sound at all https://bugs.launchpad.net/bugs/1875199 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875328] [NEW] package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: package is not updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumik 1605 F pulseaudio /dev/snd/controlC0: soumik 1605 F pulseaudio Date: Mon Apr 27 14:56:52 2020 DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=a9130fd4-73a5-4712-978c-1722c4e7915c InstallationDate: Installed on 2016-07-06 (1391 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bc2:2100 Seagate RSS LLC FreeAgent Go Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H310M S2 2.0 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=UUID=42b2ccfe-e263-4ec6-90ba-50fb0225cae1 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.21 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: H310M S2 2.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd03/08/2019:svnGigabyteTechnologyCo.,Ltd.:pnH310MS22.0:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH310MS22.0:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: H310M S2 2.0 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1875328 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: package is not updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumik 1605 F pulseaudio /dev/snd/controlC0: soumik 1605 F pulseaudio Date: Mon Apr 27 14:56:52 2020 DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=a9130fd4-73a5-4712-978c-1722c4e7915c InstallationDate: Installed on 2016-07-06 (1391 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bc2:2100 Seagate RSS LLC FreeAgent Go Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte
[Kernel-packages] [Bug 1875328] Re: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875328 Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: New Bug description: package is not updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic 4.4.0-87.110 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: soumik 1605 F pulseaudio /dev/snd/controlC0: soumik 1605 F pulseaudio Date: Mon Apr 27 14:56:52 2020 DuplicateSignature: package:linux-image-4.4.0-87-generic:4.4.0-87.110 Setting up linux-image-4.4.0-87-generic (4.4.0-87.110) ... Internal Error: Could not find image (/boot/vmlinuz-4.4.0-87-generic) dpkg: error processing package linux-image-4.4.0-87-generic (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=a9130fd4-73a5-4712-978c-1722c4e7915c InstallationDate: Installed on 2016-07-06 (1391 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bc2:2100 Seagate RSS LLC FreeAgent Go Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H310M S2 2.0 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=UUID=42b2ccfe-e263-4ec6-90ba-50fb0225cae1 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.21 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-87-generic 4.4.0-87.110 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: H310M S2 2.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd03/08/2019:svnGigabyteTechnologyCo.,Ltd.:pnH310MS22.0:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH310MS22.0:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: H310M S2 2.0 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875328/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875200] 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/1875200 Title: Entire computer freezes shortly after bootup Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure if this bug was filed completely; I used the "ubuntu-bug" command which gathered a lot of information and files, but then the bugs.launchpad.net site timeouted and I'm not sure if the information I entered before and the files that were gathered have actually been submitted. Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes some seconds after bootup. It does not even reply to pings anymore and remote logins stop working as well. When booting it in recovery mode and then immediately using the menu option to continue booting, it appears to work reliably, but it only detects one monitor and there is no 3d acceleration. I've seen freezes happening at the following points: a) at the stage of a black screnen saying "lenovo" in the middle and "ubuntu" at the bottom (of both monitors) b) when asking for username and password to login c) after login When I was using the same computer with Ubuntu 19.10, there was no such problem. The computer is a Lenovo ThinkCentre M920x, the graphics card used is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef) with two monitors (3840x2160) connected via MiniDisplayPort ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 14:29:19 2020 DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon RX 550 640SP / RX 560/560X] [1642:1725] InstallationDate: Installed on 2020-03-29 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 10S1002NMZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) XorgLogOld: dmi.bios.date: 02/17/2020 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 3135 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305220985042 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M920x dmi.product.name: 10S1002NMZ dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x dmi.product.version: ThinkCentre M920x dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875200] Re: Entire computer freezes shortly after bootup
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875200 Title: Entire computer freezes shortly after bootup Status in linux package in Ubuntu: New Bug description: I'm not sure if this bug was filed completely; I used the "ubuntu-bug" command which gathered a lot of information and files, but then the bugs.launchpad.net site timeouted and I'm not sure if the information I entered before and the files that were gathered have actually been submitted. Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes some seconds after bootup. It does not even reply to pings anymore and remote logins stop working as well. When booting it in recovery mode and then immediately using the menu option to continue booting, it appears to work reliably, but it only detects one monitor and there is no 3d acceleration. I've seen freezes happening at the following points: a) at the stage of a black screnen saying "lenovo" in the middle and "ubuntu" at the bottom (of both monitors) b) when asking for username and password to login c) after login When I was using the same computer with Ubuntu 19.10, there was no such problem. The computer is a Lenovo ThinkCentre M920x, the graphics card used is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef) with two monitors (3840x2160) connected via MiniDisplayPort ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 14:29:19 2020 DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon RX 550 640SP / RX 560/560X] [1642:1725] InstallationDate: Installed on 2020-03-29 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 10S1002NMZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) XorgLogOld: dmi.bios.date: 02/17/2020 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 3135 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305220985042 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M920x dmi.product.name: 10S1002NMZ dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x dmi.product.version: ThinkCentre M920x dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874846] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874846 Title: Xorg or more likely kernel/driver freeze Status in linux package in Ubuntu: Confirmed Bug description: The symptoms are that I am working normally, often with a remmina remote session open and suddenly everything stops. The keyboard will no longer response (caps-lock and Alt/SysRQ/reisub both have no effect. This started with kernel vmlinuz-5.3.0-46-generic and my current workaround is tu drop back to the previous -45 kernel which has been solid for about 4 weeks of fairly intense remote working. I think it is possibly another instance of existing bug 1872292 and I'm keen to help get you any diagnostic information I reasonably can. Description: Ubuntu 18.04.4 LTS Release: 18.04 Chris Ritson ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None Date: Fri Apr 24 16:43:08 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-03-23 (32 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=/dev/mapper/ubuntu--mate--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0031.2015.0601.1712 dmi.board.name: NUC5PPYB dmi.board.vendor: Intel Corporation dmi.board.version: H76558-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0031.2015.0601.1712:bd06/01/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5PPYB:rvrH76558-102:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875193] Re: Screenshot does copy the wrong monitor
Thank you for your bug report. Do you use wayland? It sounds similar to bug #1873942 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875193 Title: Screenshot does copy the wrong monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 up to date, gnome session, no extensions. Dual FHD monitor setup : joined, monitor (2) on top of the laptop screen (1) : |2| --- |1| When I hit Ctrl-Shift-PrintScreen to copy a part of the monitor (2), no sound happens and the image copied gets the right coordinates... but in laptop screen (1) ! So it's a part of the wrong display which is copied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1875193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875254] Re: Intermittent display blackouts on event
Could you try below command to see if it fixes your issue echo on | sudo tee /sys/bus/pci/devices/:00:1f.3/power/control ** Also affects: linux (Ubuntu Focal) 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/1875254 Title: Intermittent display blackouts on event Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Bug description: Issues with the screen going black for a second on certain events on a dell XPS 9370 2 in 1, especially when on battery. Seems to be a known bug in arch (https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)). Last 5.6.7 kernel tested and the issues has disappears but pb with sound card. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lucie 2232 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 7390 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/02/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875200] [NEW] Entire computer freezes shortly after bootup
You have been subscribed to a public bug: I'm not sure if this bug was filed completely; I used the "ubuntu-bug" command which gathered a lot of information and files, but then the bugs.launchpad.net site timeouted and I'm not sure if the information I entered before and the files that were gathered have actually been submitted. Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes some seconds after bootup. It does not even reply to pings anymore and remote logins stop working as well. When booting it in recovery mode and then immediately using the menu option to continue booting, it appears to work reliably, but it only detects one monitor and there is no 3d acceleration. I've seen freezes happening at the following points: a) at the stage of a black screnen saying "lenovo" in the middle and "ubuntu" at the bottom (of both monitors) b) when asking for username and password to login c) after login When I was using the same computer with Ubuntu 19.10, there was no such problem. The computer is a Lenovo ThinkCentre M920x, the graphics card used is 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef) with two monitors (3840x2160) connected via MiniDisplayPort ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 14:29:19 2020 DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon RX 550 640SP / RX 560/560X] [1642:1725] InstallationDate: Installed on 2020-03-29 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 10S1002NMZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) XorgLogOld: dmi.bios.date: 02/17/2020 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 3135 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305220985042 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone: dmi.product.family: ThinkCentre M920x dmi.product.name: 10S1002NMZ dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x dmi.product.version: ThinkCentre M920x dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- Entire computer freezes shortly after bootup https://bugs.launchpad.net/bugs/1875200 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874058] Re: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874058 Title: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Using the mlx5 device driver on Ubuntu 20.04 (beta), the alloc_pages_nodemask code generates a stack trace when initializing a device. The driver tries to allocate more contiguous memory than is allowed by the platform specific FORCE_MAX_ZONEORDER setting. FORCE_MAX_ZONEORDER on s390x: 9 FORCE_MAX_ZONEORDER on other platforms: 11 or more This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer code is only used for physical functions. A fix for this has recently been pulled into David Miller's net tree as part of a series of Mellanox fixes: https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/ It hasn't landed in Linus' tree yet though To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874058/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872726] Re: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872726 Title: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: Issue found in the Mellanox mlx5 device driver: The mask value is provided as 64 bit and has to be casted in either 32 or 16 bit. On big endian systems the wrong half was casted which resulted in an all zero mask. We need to get the upstream commit picked up for the Ubuntu 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1872726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874846] Re: Xorg or more likely kernel/driver freeze
Thank, if the issue is due to a kernel update and isn't happening with an old kernel then it's likely a kernel bug, reassining ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874846 Title: Xorg or more likely kernel/driver freeze Status in linux package in Ubuntu: New Bug description: The symptoms are that I am working normally, often with a remmina remote session open and suddenly everything stops. The keyboard will no longer response (caps-lock and Alt/SysRQ/reisub both have no effect. This started with kernel vmlinuz-5.3.0-46-generic and my current workaround is tu drop back to the previous -45 kernel which has been solid for about 4 weeks of fairly intense remote working. I think it is possibly another instance of existing bug 1872292 and I'm keen to help get you any diagnostic information I reasonably can. Description: Ubuntu 18.04.4 LTS Release: 18.04 Chris Ritson ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None Date: Fri Apr 24 16:43:08 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-03-23 (32 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=/dev/mapper/ubuntu--mate--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0031.2015.0601.1712 dmi.board.name: NUC5PPYB dmi.board.vendor: Intel Corporation dmi.board.version: H76558-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0031.2015.0601.1712:bd06/01/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5PPYB:rvrH76558-102:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874062] Re: [UBUNTU 20.04] Performance floating interrupt
** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874062 Title: [UBUNTU 20.04] Performance floating interrupt Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: With the introduction of CPU directed interrupts the kernel parameter pci=force_floating was introduced to fall back to the previous behavior using floating irqs. Furthermore this fallback is used on machines lacking support for directed interrupts. However we were still setting the affinity in that case, both in __irq_alloc_descs() and via the irq_set_affinity callback in struct irq_chip. This setting of the affinity leads to a performance regression in streaming workloads which can be seen with e.g. by an iperf streaming test between two LPARs using ConnectX-5 based nics. In some tests the performance would drop to 20% of the performance with older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels
** Changed in: linux-kvm (Ubuntu Disco)
Status: Won't Fix => In Progress
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-kvm (Ubuntu Xenial)
Status: New => In Progress
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** No longer affects: linux-kvm (Ubuntu)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812176
Title:
psock_tpacket from the net test in ubuntu_kernel_selftests failed on
KVM kernels
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux-kvm source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux-kvm source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with
B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused
by the attempt to access /proc/kallsyms in test_kernel_bit_width():
static int test_kernel_bit_width(void)
{
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;
fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 08:05:47 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812176/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874846] [NEW] Xorg or more likely kernel/driver freeze
You have been subscribed to a public bug: The symptoms are that I am working normally, often with a remmina remote session open and suddenly everything stops. The keyboard will no longer response (caps-lock and Alt/SysRQ/reisub both have no effect. This started with kernel vmlinuz-5.3.0-46-generic and my current workaround is tu drop back to the previous -45 kernel which has been solid for about 4 weeks of fairly intense remote working. I think it is possibly another instance of existing bug 1872292 and I'm keen to help get you any diagnostic information I reasonably can. Description:Ubuntu 18.04.4 LTS Release:18.04 Chris Ritson ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None Date: Fri Apr 24 16:43:08 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-03-23 (32 days ago) InstallationMedia: Ubuntu-MATE 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=/dev/mapper/ubuntu--mate--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0031.2015.0601.1712 dmi.board.name: NUC5PPYB dmi.board.vendor: Intel Corporation dmi.board.version: H76558-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0031.2015.0601.1712:bd06/01/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5PPYB:rvrH76558-102:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- Xorg or more likely kernel/driver freeze https://bugs.launchpad.net/bugs/1874846 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
Hello, This is an issue with VPN MTU configuration. May I know the root cause why this is causing the issue? After adjusted the MTU , this is fixed. As the same time putty works without any modification. Why ssh client not negotiating properly with the default MTU It could be a noisy or unreliable connection to the server. Probably that data corruption is happening to the packet when it is sent, which is my assumption https://en.wikipedia.org/wiki/Maximum_transmission_unit https://en.wikipedia.org/wiki/Forward_error_correction >From ubuntu community point of view any suggestions> thanks Jay ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc:
[Kernel-packages] [Bug 1874058] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-27 04:31 EDT---
The commit has landed upstream in v5.7-rc3 as:
a019b36123aec9700b21ae0724710f62928a8bc1 ("net/mlx5: Fix failing fw
tracer allocation on s390")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874058
Title:
[UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
New
Bug description:
Using the mlx5 device driver on Ubuntu 20.04 (beta), the
alloc_pages_nodemask code generates a stack trace when initializing a
device. The driver tries to allocate more contiguous memory than is
allowed by the platform specific FORCE_MAX_ZONEORDER setting.
FORCE_MAX_ZONEORDER on s390x: 9
FORCE_MAX_ZONEORDER on other platforms: 11 or more
This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer
code is only used for physical functions.
A fix for this has recently been pulled into David Miller's net tree as part
of a series of Mellanox fixes:
https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/
It hasn't landed in Linus' tree yet though
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874058/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
I'm to SRU https://lkml.org/lkml/2019/12/1/179 to B/E/F/OEM- OSP1-B/OEM-5.6 in bug 1861610. ** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875309] Re: [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place
** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875309 Title: [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place Status in subiquity: New Status in Ubuntu on IBM z Systems: New Bug description: Compared to d-i - where parmfile modifications are not necessarily needed, the question is, if this can be again the same for subiquity? At the very least, the current state definitely needs documentation - otherwise customers will try to install and it will fail without any indication what went wrong. On top of that, it would be nice if the installer could at least give a helpful message pointing out that the user will have to modify their parmfile for the installation to work. Of course the best solution would be to add code to the installer to prompt for the necessary information like before. Addl reference information: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1854513 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873194] Re: clipit interface not working in 20.04
On Ubuntu 20.04 stable, the Clipit interface does not work on Xorg either. The hotekeys do not work, the preferences do not open and the program does not shut down properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873194 Title: clipit interface not working in 20.04 Status in clipit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When running clipit in focal fossa beta the interface will crash when opening the history list via shortcut (ctr + alt + h). Starting it from cli shows this error message: (clipit:7248): Gdk-CRITICAL **: 10:42:40.873: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed Clipit version is 1.4.4+git20190202-1 from https://launchpad.net/ubuntu/focal/+package/clipit Ubuntu version is Ubuntu Focal Fossa (development branch) from 15.4.2020 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-04-29 (1447 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal third-party-packages Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-15 (0 days ago) UserGroups: adm cdrom dip docker kismet kvm lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/1873194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874374] Re: thinkbook 14-iil elan touchpad does not work
@Brian, basically "_HIDELAN0634" is an illegal name according to ACPI specification, so there won't be a overriding fix in kernel because kernel would enforce the names to follow standard. It follows this platform would have to be patch in the ACPI tables as detailed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/comments/15. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874374 Title: thinkbook 14-iil elan touchpad does not work Status in linux package in Ubuntu: Confirmed Bug description: Here is the output of cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.0/0003:062A:4C01.0001/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse Consumer Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse System Control" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=c000 10 0 B: MSC=10 I: Bus=0003 Vendor=062a Product=4c01 Version=0110 N: Name="MOSART Semi. 2.4G Keyboard Mouse" P: Phys=usb-:00:14.0-4/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.1/0003:062A:4C01.0002/input/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=9 B: ABS=100 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input10 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B:
[Kernel-packages] [Bug 1875309] [NEW] [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place
Public bug reported: Compared to d-i - where parmfile modifications are not necessarily needed, the question is, if this can be again the same for subiquity? At the very least, the current state definitely needs documentation - otherwise customers will try to install and it will fail without any indication what went wrong. On top of that, it would be nice if the installer could at least give a helpful message pointing out that the user will have to modify their parmfile for the installation to work. Of course the best solution would be to add code to the installer to prompt for the necessary information like before. Addl reference information: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1854513 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185593 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-185593 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875309 Title: [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place Status in linux package in Ubuntu: New Bug description: Compared to d-i - where parmfile modifications are not necessarily needed, the question is, if this can be again the same for subiquity? At the very least, the current state definitely needs documentation - otherwise customers will try to install and it will fail without any indication what went wrong. On top of that, it would be nice if the installer could at least give a helpful message pointing out that the user will have to modify their parmfile for the installation to work. Of course the best solution would be to add code to the installer to prompt for the necessary information like before. Addl reference information: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1854513 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875309] [NEW] [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place
You have been subscribed to a public bug: Compared to d-i - where parmfile modifications are not necessarily needed, the question is, if this can be again the same for subiquity? At the very least, the current state definitely needs documentation - otherwise customers will try to install and it will fail without any indication what went wrong. On top of that, it would be nice if the installer could at least give a helpful message pointing out that the user will have to modify their parmfile for the installation to work. Of course the best solution would be to add code to the installer to prompt for the necessary information like before. Addl reference information: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1854513 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185593 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place https://bugs.launchpad.net/bugs/1875309 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
https://lists.ubuntu.com/archives/kernel-team/2020-April/109386.html ** Description changed: + [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/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Eoan: New Status in linux source package in Focal: In Progress 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 1875300] Re: [Ubuntu 20.04 s390] Failed to install os from CD
** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** No longer affects: linux (Ubuntu) ** Also affects: ubuntu-z-systems 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/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in subiquity: New Status in Ubuntu on IBM z Systems: New Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875300] [NEW] [Ubuntu 20.04 s390] Failed to install os from CD
Public bug reported: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185591 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-185591 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in linux package in Ubuntu: New Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875300] [NEW] [Ubuntu 20.04 s390] Failed to install os from CD
You have been subscribed to a public bug: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185591 severity-high targetmilestone-inin2004 -- [Ubuntu 20.04 s390] Failed to install os from CD https://bugs.launchpad.net/bugs/1875300 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859744] Re: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859744 Title: [spi-0115]spi: dw: use "smp_mb()" to avoid sending spi data error Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Sometimes, TPM fails because SPI data error [Fix] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error [Test] Reboot system few times and no TPM error message [Regression Potential] Only on SPI function. Already tested on focal kernel [Bug Description] Because of out-of-order execution about some CPU architecture, In this debug stage we find Completing spi interrupt enable -> prodrucing TXEI interrupt -> running "interrupt_transfer" function will prior to set "dw->rx and dws->rx_end" data, so this patch add memory barrier to enable dw->rx and dw->rx_end to be visible and solve to send SPI data error. eg: it will fix to this following low possibility error in testing environment which using SPI control to connect TPM Modules kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Steps to Reproduce] 1) enable ima and tpm 2)reboot this system 3) [Actual Results] kernel: tpm tpm0: Operation Timed out kernel: tpm tpm0: tpm_relinquish_locality: : error -1 [Expected Results] ok [Reproducibility] low probabilities [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] bfda044533b2 spi: dw: use "smp_mb()" to avoid sending spi data error To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859743] Re: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859743 Title: [tpm-0115]EFI/stub: tpm: enable tpm eventlog function for ARM64 platform Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] No TPM eventlog information in sysfs [Fix] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform [Test] ls -l /sys/kernel/security/tpm0/binary_bios_measurements [Regression Potential] Only affect arm64 system with TPM. Lowest risk for other platform. [Bug Description] this patch gets tpm eventlog information such as device boot status,event guid and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog" functions to get it for ARM64 platorm. [Steps to Reproduce] 1) ls -l /sys/kernel/security/tpm0/binary_bios_measurements 2) 3) [Actual Results] '/sys/kernel/security/tpm0/binary_bios_measurements' no such file or directory [Expected Results] ok [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] d99c1ba6a73b EFI/stub: tpm: enable tpm eventlog function for ARM64 platform To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
** Also affects: openssh (Ubuntu) Importance: Undecided Status: New ** Also affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Incomplete Status in openssh package in Ubuntu: New Status in openvpn package in Ubuntu: New Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc:
[Kernel-packages] [Bug 1859569] Re: [hns3-0114]net: hns3: fix ETS bandwidth validation bug
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859569 Title: [hns3-0114]net: hns3: fix ETS bandwidth validation bug Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Impact] The corresponding ethernet interface could not be up again. [Fix] cherry picked from commit c2d56897819338eb0ba8b93184f7d10329b36653 net: hns3: fix ETS bandwidth validation bug [Test Case] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Regression Risk] Low, the patch is only specific to the hns3 driver. == Original Bug Description == [Bug Description] When a TC's PFC is disabled or enabled, the RX private buffer for this TC need to be changed too, otherwise this may cause packet dropped problem. [Steps to Reproduce] 1.lldpad -d 2.lldptool -L -i eth0 adminStatus=rxtx 3.lldptool -T -i eth0 -V ETS-CFG tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets up2tc=0:0,1:0,2:1,3:1,4:2,5:2,6:3,7:3 tcbw=25,25,50,0,0,0,0,0 4.down device 5.up [Actual Results] up fail [Expected Results] up ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] This patch fixes it by calling hclge_buffer_alloc to reallocate buffer when pfc_en changes. c2d568978193 net: hns3: fix ETS bandwidth validation bug To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875236] Re: Different kernel gives different RAM results
Suppose that this bug related to linux kernel configuration, but can't put package name (linux-image-5.4.0-26-generic) in appropriate field of form (not listed). ** Package changed: ubuntu => linux-signed (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1875236 Title: Different kernel gives different RAM results Status in linux-signed package in Ubuntu: New Bug description: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1875236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875236] [NEW] Different kernel gives different RAM results
You have been subscribed to a public bug: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Different kernel gives different RAM results https://bugs.launchpad.net/bugs/1875236 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854547] Re: 【sas-1130】scsi: sd: define variable dif as unsigned int instead of bool
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854547 Title: 【sas-1130】scsi: sd: define variable dif as unsigned int instead of bool Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Invalid Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Bug Description] DIF3 WILL not work when run fio test 【Steps to Reproduce] 1. Enable DIF/DIX for DIF3 disk 2. fio test [Actual Results] IO error when running IO; [ 781.032816] sd 5:0:0:0: [sdd] Disabling DIF Type 3 protection [ 781.112250] sd 5:0:0:0: [sdd] tag#72 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.112287] sd 5:0:0:0: [sdd] tag#72 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.112305] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.118429] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.204243] sd 5:0:0:0: [sdd] tag#77 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.204252] sd 5:0:0:0: [sdd] tag#77 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.204257] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.210365] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.296238] sd 5:0:0:0: [sdd] tag#82 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.296266] sd 5:0:0:0: [sdd] tag#82 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.296276] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.302384] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.309207] ldm_validate_partition_table(): Disk read failed. [ 781.392239] sd 5:0:0:0: [sdd] tag#87 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.392267] sd 5:0:0:0: [sdd] tag#87 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.392278] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.398386] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.484250] sd 5:0:0:0: [sdd] tag#92 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.484260] sd 5:0:0:0: [sdd] tag#92 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.484264] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.490371] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.576249] sd 5:0:0:0: [sdd] tag#97 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.576278] sd 5:0:0:0: [sdd] tag#97 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.576293] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.582399] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.668236] sd 5:0:0:0: [sdd] tag#102 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.668245] sd 5:0:0:0: [sdd] tag#102 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.668249] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.674354] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.681184] Dev sdd: unable to read RDB block 0 [ 781.764241] sd 5:0:0:0: [sdd] tag#121 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.764267] sd 5:0:0:0: [sdd] tag#121 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.764278] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.770386] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.856240] sd 5:0:0:0: [sdd] tag#126 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.856248] sd 5:0:0:0: [sdd] tag#126 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.856253] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.862362] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.948238] sd 5:0:0:0: [sdd] tag#131 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.948264] sd 5:0:0:0: [sdd] tag#131 CDB: Read(10) 28 00 00 00 00 18 00 00 08 00 [ 781.948272] print_req_error: I/O error, dev sdd, sector 24 flags 0 [ 781.954467] Buffer I/O error on dev sdd, logical block 3, async page read [ 782.120252] sdd: unable to read partition table [Expected Results] IO running normally [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] Variable dif in function sd_setup_read_write_cmnd() is the return value of function scsi_host_dif_capable() which returns dif capability of disks. If define it
[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854000] Re: [sas-1126]scsi: hisi_sas: Replace in_softirq() check in hisi_sas_task_exec()
In 5.3 HWE kernel already. ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: ubuntu-18.04.5 => ubuntu-18.04.4-sru-2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854000 Title: [sas-1126]scsi: hisi_sas: Replace in_softirq() check in hisi_sas_task_exec() Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: "[Steps to Reproduce] 1. run fio 2“echo 1 > /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump” [Actual Results] [ 448.405504] CPU: 27 PID: 13560 Comm: fio Tainted: GW 5.3.0-rc4-gae89c9a3-dirty #1 [ 448.405506] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B080.01 09/19/2019 [ 448.405507] Call trace: [ 448.405512] dump_backtrace+0x0/0x150 [ 448.405513] show_stack+0x24/0x30 [ 448.405516] dump_stack+0xa0/0xc4 [ 448.405518] __schedule_bug+0x68/0x88 [ 448.405520] __schedule+0x4b8/0x548 [ 448.405521] schedule+0x40/0xd0 [ 448.405523] schedule_timeout+0x200/0x378 [ 448.405524] __down+0x78/0xc8 [ 448.405526] down+0x54/0x70 [ 448.405533] hisi_sas_task_exec.isra.10+0x598/0x8d8 [hisi_sas_main] f=11): [M(11)][1[ 448.405535] hisi_sas_queue_command+0x28/0x38 [hisi_sas_main] [ 448.405541] sas_queuecommand+0x168/0x1b0 [libsas] [ 448.405544] scsi_queue_rq+0x2ac/0x980 [ 448.405547] blk_mq_dispatch_rq_list+0xb0/0x550 [ 448.405548] blk_mq_do_dispatch_sched+0x6c/0x110 [ 448.405550] blk_mq_sched_dispatch_requests+0x114/0x1d8 [ 448.405551] __blk_mq_run_hw_queue+0xb8/0x130 [ 448.405552] __blk_mq_delay_run_hw_queue+0x1c0/0x220 [ 448.405553] blk_mq_run_hw_queue+0xb0/0x128 [ 448.405554] blk_mq_sched_insert_requests+0xdc/0x208 [ 448.40] blk_mq_flush_plug_list+0x1b4/0x3a0 [ 448.405557] blk_flush_plug_list+0xdc/0x110 [ 448.405558] blk_finish_plug+0x3c/0x50 [ 448.405560] blkdev_write_iter+0xc0/0x130 [ 448.405562] aio_write+0xec/0x1a0 [ 448.405563] io_submit_one+0x4f4/0x8d8 [ 448.405564] __arm64_sys_io_submit+0xdc/0x280 [ 448.405566] el0_svc_common.constprop.0+0xe0/0x1e0 [ 448.405567] el0_svc_handler+0x34/0x90 [ 448.405569] el0_svc+0x10/0x14 [ 448.405571] CPU: 26 PID: 13559 Comm: fio Tainted: GW 5.3.0-rc4-gae89c9a3-dirty #1 [ 448.405572] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B080.01 09/19/2019 [ 448.405572] Call trace: [ 448.405574] dump_backtrace+0x0/0x150 [ 448.405575] show_stack+0x24/0x30 [ 448.405577] dump_stack+0xa0/0xc4 [ 448.405578] __schedule_bug+0x68/0x88 [ 448.405580] __schedule+0x4b8/0x548 [ 448.405581] schedule+0x40/0xd0 [ 448.405582] schedule_timeout+0x200/0x378 [ 448.405583] __down+0x78/0xc8 [ 448.405584] down+0x54/0x70 [ 448.405587] hisi_sas_task_exec.isra.10+0x598/0x8d8 [hisi_sas_main] [ 448.405590] hisi_sas_queue_command+0x28/0x38 [hisi_sas_main] [ 448.405594] sas_queuecommand+0x168/0x1b0 [libsas] [ 448.405595] scsi_queue_rq+0x2ac/0x980 [ 448.405596] blk_mq_dispatch_rq_list+0xb0/0x550 [ 448.405598] blk_mq_do_dispatch_sched+0x6c/0x110 [ 448.405599] blk_mq_sched_dispatch_requests+0x114/0x1d8 [ 448.405600] __blk_mq_run_hw_queue+0xb8/0x130 [ 448.405601] __blk_mq_delay_run_hw_queue+0x1c0/0x220 [ 448.405602] blk_mq_run_hw_queue+0xb0/0x128 [ 448.405603] blk_mq_sched_insert_requests+0xdc/0x208 [ 448.405605] blk_mq_flush_plug_list+0x1b4/0x3a0 [ 448.405606] blk_flush_plug_list+0xdc/0x110 [ 448.405607] blk_finish_plug+0x3c/0x50 [ 448.405608] blkdev_write_iter+0xc0/0x130 [ 448.405610] aio_write+0xec/0x1a0 [ 448.405611] io_submit_one+0x4f4/0x8d8 [ 448.405612] __arm64_sys_io_submit+0xdc/0x280 [ 448.405614] el0_svc_common.constprop.0+0xe0/0x1e0 [ 448.405615] el0_svc_handler+0x34/0x90 [ 448.405616] el0_svc+0x10/0x14 [ 448.405620] CPU: 86 PID: 13534 Comm: fio Tainted: GW 5.3.0-rc4-gae89c9a3-dirty #1 1.7%][r=1163MiB/[ 448.405621] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B080.01 09/19/2019 [ 448.405622] Call trace: [ 448.405625] dump_backtrace+0x0/0x150 [ 448.405626] show_stack+0x24/0x30 [ 448.405631] dump_stack+0xa0/0xc4 [ 448.405635] __schedule_bug+0x68/0x88 [ 448.405636] __schedule+0x4b8/0x548 [ 448.405637] schedule+0x40/0xd0 [
[Kernel-packages] [Bug 1854550] Re: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices
Already in HWE 5.3 kernel ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: ubuntu-18.04.5 => ubuntu-18.04.4-sru-2 ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854550 Title: [scsi-1130]scsi: scsi_transport_sas: Fix memory leak when removing devices Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Won't Fix Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Impact] kmemleak detects potential leaks and this is the fix [Test Case] Not known case, regression test on system with SAS host is needed. [Fix] 82ea3e0e12 scsi: scsi_transport_sas: Fix memory leak when removing devices [Regression Risk] Patch is simple and reviewed on upstream. Since modification is for scsi subsystem not on a single driver, applying on focal gives us enough time for test. "[Steps to reproduce] Enable memleak, and do as follows: root@(none)$ echo 0 > /sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:10/phy-0:0:10/sas_phy/phy-0:0:10/enable [ 79.857888] hisi_sas_v2_hw HISI0162:01: dev[7:1] is gone root@(none)$ echo scan > /sys/kernel/debug/kmemleak [ 131.656603] kmemleak: 3 new suspected memory leaks (see /sys/kernel/debug/kmemleak) root@(none)$ more /sys/kernel/debug/kmemleak unreferenced object 0x041da5c66000 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 5e c6 a5 1d 04 ff ff 01 00 00 00 00 00 00 00 .^.. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] kmem_cache_alloc+0x188/0x260 [<(ptrval)>] bsg_setup_queue+0x48/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041d8c075400 (size 128): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 40 25 97 1d 00 ff ff 00 00 00 00 00 00 00 00 .@%. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_realloc_tag_set_tags.part.70+0x48/0xd8 [<(ptrval)>] blk_mq_alloc_tag_set+0x1dc/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 unreferenced object 0x041da5c65e00 (size 256): comm ""kworker/u128:1"", pid 549, jiffies 4294898543 (age 113.728s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 backtrace: [<(ptrval)>] __kmalloc_node+0x1a8/0x2c8 [<(ptrval)>] blk_mq_alloc_tag_set+0x254/0x530 [<(ptrval)>] bsg_setup_queue+0xe8/0x1a8 [<(ptrval)>] sas_rphy_add+0x108/0x2d0 [<(ptrval)>] sas_probe_devices+0x168/0x208 [<(ptrval)>] sas_discover_domain+0x660/0x9c8 [<(ptrval)>] process_one_work+0x3f8/0x690 [<(ptrval)>] worker_thread+0x70/0x6a0 [<(ptrval)>] kthread+0x1b8/0x1c0 [<(ptrval)>] ret_from_fork+0x10/0x18 root@(none)$ [solution] Fix by doing the queue removal in one place - in sas_rphy_remove() - instead of unregistering the queue in sas_rphy_remove() and finally cleaning up the queue in calling blk_cleanup_queue() from sas_end_device_release() or sas_expander_release(). Function bsg_remove_queue() can handle a NULL pointer q, so remove the precheck in sas_rphy_remove(). " scsi: scsi_transport_sas: Fix memory leak when removing devices To manage notifications about this bug go to:
Re: [Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Hi, I'm working on a Zenbook UX334 using a dual boot system. Initially I've installed Ubuntu 19.10 with nvidia drivers experiencing the audio problem. After that I installed Ubuntu 19.10 but without the Nvidia drivers and the sound started working again. In the second phase I installed the nvidia drivers. The sound is metallic but it works fine. Il giorno lun 27 apr 2020 alle ore 08:10 Rewi Haar < 1850...@bugs.launchpad.net> ha scritto: > I have the same issue on a ZenBook UX433FLC. The internal speakers work > at least some of the time, but whenever I plug in headphones I just hear > a loud irregular clicking sound. The headphones work fine in Windows > 10. > > As I recall, when I initially ran Ubuntu off a live USB before > installation, I checked the audio using headphones and it seemed to work > just fine. (In case it turns out to be relevant, this would have been > before I switched the SATA mode to AHCI.) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1856460). > https://bugs.launchpad.net/bugs/1850439 > > Title: > No sound on ASUS UX534FT > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, > > after instal Ubuntu in dual boot alongside Windows 10, I've realised > there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- > AA024R in Ubuntu. In Windows there is no problem. Found this topic > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had > the same problem with driver for Realtek ALC294 which is also mine > sound card. But even with this fix it is not working on UX534FT. Can > you please add fix also for this newer model? > > Description: Ubuntu 18.04.3 LTS > Release: 18.04 > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 > ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 29 15:11:25 2019 > InstallationDate: Installed on 2019-10-29 (0 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > SourcePackage: linux-signed-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
Still got the same error with that patch applied. Replied on mailing list. ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration [ 11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid [ 11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match [ 11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel [ 11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp [ 11.489555] iwlwifi :00:14.3: 0x1AFE14FD | flow_handler [ 11.489635] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489643] iwlwifi :00:14.3: Status: 0x, count: 7 [ 11.489652] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 11.489659] iwlwifi :00:14.3: 0x | umac branchlink1 [ 11.489666] iwlwifi :00:14.3: 0x80465E6A | umac branchlink2 [ 11.489674] iwlwifi :00:14.3: 0x | umac interruptlink1 [ 11.489681] iwlwifi :00:14.3: 0x | umac interruptlink2 [ 11.489688] iwlwifi :00:14.3: 0x0003 | umac data1 [ 11.489695] iwlwifi :00:14.3: 0x2302 | umac data2 [ 11.489702] iwlwifi :00:14.3: 0x01300504 | umac data3 [ 11.489710] iwlwifi :00:14.3: 0x0032 | umac major [ 11.489717] iwlwifi :00:14.3: 0x3E391D3E | umac minor [ 11.489732] iwlwifi :00:14.3: 0x5D89 | frame pointer [ 11.489743] iwlwifi :00:14.3: 0xC0887F58 | stack pointer [ 11.489755] iwlwifi :00:14.3: 0x | last host cmd [ 11.489763] iwlwifi :00:14.3: 0x | isr status reg [ 11.489822] iwlwifi :00:14.3: Fseq Registers: [ 11.489846] iwlwifi :00:14.3: 0x0003 | FSEQ_ERROR_CODE [ 11.489870] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [
[Kernel-packages] [Bug 1875225] Re: /tmp sticky bit do not permit writing fifo file inside
Cannot run apport-collect becouse "linux" package doesn't exist. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875225 Title: /tmp sticky bit do not permit writing fifo file inside Status in linux package in Ubuntu: Confirmed Bug description: Trying to write into a fifo pipe inside /tmp (echo "hello" > /tmp/fifo) whit normal permissions (drwxrwxrwt, sticky bit) and the fifo with prw-rw-rw- permissions and with "other" user than user and group owner ends in this error: bash: /tmp/fifo: Permission denied. It occurs since upgrading to Ubuntu 20.04, in 19.04 it worked as expected. When I remove the sticky bit (drwxrwxrwx) from tmp it works normally. I think it is a misbehaviour, with sticky bit you cannot rename or remove files inside that folder, but could be able to write into them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853984] Re: [hns-1126]net: hns3: fix port setting handle for fibre port
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853984 Title: [hns-1126]net: hns3: fix port setting handle for fibre port Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Test Case] `sudo ethtool -s eno1 autoneg off speed 10 duplex full` `sudo ethtool -s eno1 autoneg on` commands shall return 0 [Fix] 24283ece5a0f net: hns3: fix port setting handle for fibre port [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] For hardware doesn't support use specified speed and duplex to negotiate, it's unnecessary to check and modify the port speed and duplex for fibre port when autoneg is on. [Steps to Reproduce] 1.ethtool -s eth* autoneg off speed 10 duplex full 2.ethtool -s eth* autoneg on [Actual Results] set autoneg on fail [Expected Results] set autoneg on ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Not check and modify the port speed and duplex for fibre port when autoneg on." net: hns3: fix port setting handle for fibre port To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853983] Re: [hns-1126]net: hns3: revert to old channel when setting new channel num fail
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853983 Title: [hns-1126]net: hns3: revert to old channel when setting new channel num fail Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] With specific ethtool commands, ethernet does not work [Test Case] run VF on VM with 3G memory and load VF driver ethtool -G eth0 tx 3 rx 3 ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 ethtool -G eth0 tx 32760 rx 32760 ethtool -L eth0 combined 32 ethernet shall still be functional after these commands [Fix] 3a5a5f06d4d2 net: hns3: revert to old channel when setting new channel num fail [Regression Risk] Patch restricted to hns3 driver. "[Bug Description] After setting new channel num, it needs free old ring memory and allocate new ring memory. If there is no enough memory and allocate new ring memory fail, the ring may initialize fail. To make sure the network interface can work normally, driver should revert the channel to the old configuration. [Steps to Reproduce] 1.run VF on VM with 3G memory 2.load VF driver 3.ethtool -G eth0 tx 3 rx 3 4.ethtool -G eth0 tx 24 rx 24；ethtool -L eth0 combined 1 5.ethtool -G eth0 tx 32760 rx 32760 6.ethtool -L eth0 combined 32 7.ping [Actual Results] netdevice can not work [Expected Results] ping ok [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA [Resolution] Revert the channel to the old configuration when allocate new ring memory fail." To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853992] Re: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853992 Title: [sas-1126]scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset() [Regression Risk] Patch restricted to hisi_sas driver. [Bug Description] sas kasan test will produce this out bounds in sas module [Steps to Reproduce] 1) enbale this kasn 2) 3) [Actual Results] 30293.504016] sas: ata464: end_device-2:2:6: dev error handler [30293.504041] sas: ata465: end_device-2:2:7: dev error handler [30293.504059] sas: ata466: end_device-2:2:8: dev error handler [30293.538746] == [30293.550672] BUG: KASAN: slab-out-of-bounds in hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.558642] Read of size 8 at addr b72e47233540 by task kworker/u193:3/79165 [30293.566004] [30293.567498] CPU: 14 PID: 79165 Comm: kworker/u193:3 Tainted: GB O 5.1.0-rc1-g7a3fab8-dirty #1 [30293.577196] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B010.01 06/21/2019 [30293.586037] Workqueue: events_unbound async_run_entry_fn [30293.591331] Call trace: [30293.593770] dump_backtrace+0x0/0x1f8 [30293.597419] show_stack+0x14/0x20 [30293.600726] dump_stack+0xc4/0xfc [30293.604032] print_address_description+0x60/0x258 [30293.608716] kasan_report+0x164/0x1b8 [30293.612366] __asan_load8+0x84/0xa8 [30293.615842] hisi_sas_debug_I_T_nexus_reset+0xcc/0x250 [30293.620961] hisi_sas_I_T_nexus_reset+0xc4/0x170 [30293.625562] sas_ata_hard_reset+0x88/0x178 [30293.629646] ata_do_reset.constprop.6+0x80/0x90 [30293.634160] ata_eh_reset+0x71c/0x10e8 [30293.637897] ata_eh_recover+0x3d0/0x1a80 [30293.641804] ata_do_eh+0x50/0xd0 [30293.645020] ata_std_error_handler+0x78/0xa8 [30293.649273] ata_scsi_port_error_handler+0x288/0x930 [30293.654216] async_sas_ata_eh+0x68/0x90 [30293.658040] async_run_entry_fn+0x7c/0x1c0 [30293.662121] process_one_work+0x3c0/0x878 [30293.666115] worker_thread+0x70/0x670 [30293.669762] kthread+0x1b0/0x1b8 [30293.672978] ret_from_fork+0x10/0x18 [30293.676541] [30293.678027] Allocated by task 16690: [30293.681593] __kasan_kmalloc.isra.0+0xd4/0x188 [30293.686018] kasan_kmalloc+0xc/0x18 [30293.689496] __kmalloc_node_track_caller+0x5c/0x98 [30293.694270] devm_kmalloc+0x44/0xb8 [30293.697746] hisi_sas_v3_probe+0x2ec/0x698 [30293.701828] local_pci_probe+0x74/0xf0 [30293.705562] work_for_cpu_fn+0x2c/0x48 [30293.709300] process_one_work+0x3c0/0x878 [30293.713294] worker_thread+0x400/0x670 [30293.717027] kthread+0x1b0/0x1b8 [30293.720241] ret_from_fork+0x10/0x18 [30293.723801] [30293.725287] Freed by task 16227: [30293.728503] __kasan_slab_free+0x108/0x210 [30293.732583] kasan_slab_free+0x10/0x18 [30293.736318] kfree+0x74/0x150 [30293.739276] devres_free+0x34/0x48 [30293.742665] devres_release+0x38/0x60 [30293.746313] devm_pinctrl_put+0x34/0x58 [30293.750136] pinctrl_bind_pins+0x164/0x248 [30293.754214] really_probe+0xc0/0x3b0 [30293.75] driver_probe_device+0x70/0x138 [30293.761944] __device_attach_driver+0xc0/0xe0 [30293.766285] bus_for_each_drv+0xcc/0x150 [30293.770194] __device_attach+0x154/0x1c0 [30293.774101] device_initial_probe+0x10/0x18 [30293.778270] bus_probe_device+0xec/0x100 [30293.782178] device_add+0x5f8/0x9b8 [30293.785658] scsi_sysfs_add_sdev+0xa4/0x310 [30293.789825] scsi_probe_and_add_lun+0xe60/0x1240 [30293.794425] __scsi_scan_target+0x1ac/0x780 [30293.798591] scsi_scan_target+0x134/0x140 [30293.802586] sas_rphy_add+0x1fc/0x2c8 [30293.806234] sas_probe_devices+0x10c/0x1e8 [30293.810313] sas_discover_domain+0x754/0x998 [30293.814567] process_one_work+0x3c0/0x878 [30293.818560] worker_thread+0x70/0x670 [30293.822207] kthread+0x1b0/0x1b8 [30293.825423] ret_from_fork+0x10/0x18 [30293.828983]
[Kernel-packages] [Bug 1853989] Re: [roce-1126]RDMA/hns: bugfix for slab-out-of-bounds when loading hip08 driver
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853989 Title: [roce-1126]RDMA/hns: bugfix for slab-out-of-bounds when loading hip08 driver Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] KASAN reports slab-out-of-bounds in RDMA/hns driver [Testcase] Enable KASAN and modprobe RDMA/hns driver [Regression Risk] Only RDMA/hns driver modified. lowest risk to other drivers/platforms [Bug Description] KASAN: slab-out-of-bounds in hns_roce_table_mhop_put+0x584/0x828 [hns_roce] Read of size 8 at addr 802185e08300 by task rmmod/270 Call trace: dump_backtrace+0x0/0x1e8 show_stack+0x14/0x20 dump_stack+0xc4/0xfc print_address_description+0x60/0x270 __kasan_report+0x164/0x1b8 kasan_report+0xc/0x18 __asan_load8+0x84/0xa8 hns_roce_table_mhop_put+0x584/0x828 [hns_roce] hns_roce_table_put+0x174/0x1a0 [hns_roce] hns_roce_mr_free+0x124/0x210 [hns_roce] hns_roce_dereg_mr+0x90/0xb8 [hns_roce] ib_dealloc_pd_user+0x60/0xf0 ib_mad_port_close+0x128/0x1d8 ib_mad_remove_device+0x94/0x118 remove_client_context+0xa0/0xe0 disable_device+0xfc/0x1c0 __ib_unregister_device+0x60/0xe0 ib_unregister_device+0x24/0x38 hns_roce_exit+0x3c/0x138 [hns_roce] __hns_roce_hw_v2_uninit_instance.isra.30+0x28/0x50 [hns_roce_hw_v2] hns_roce_hw_v2_uninit_instance+0x44/0x60 [hns_roce_hw_v2] hclge_uninit_client_instance+0x15c/0x238 [hclge] hnae3_uninit_client_instance+0x84/0xa8 [hnae3] hnae3_unregister_client+0x84/0x158 [hnae3] hns_roce_hw_v2_exit+0x14/0x20 [hns_roce_hw_v2] __arm64_sys_delete_module+0x20c/0x308 el0_svc_handler+0xbc/0x210 el0_svc+0x8/0xc Allocated by task 255: __kasan_kmalloc.isra.0+0xd0/0x180 kasan_kmalloc+0xc/0x18 __kmalloc+0x16c/0x328 hns_roce_init_hem_table+0x20c/0x428 [hns_roce] hns_roce_init+0x214/0xfe0 [hns_roce] __hns_roce_hw_v2_init_instance+0x284/0x330 [hns_roce_hw_v2] hns_roce_hw_v2_init_instance+0xd0/0x1b8 [hns_roce_hw_v2] hclge_init_roce_client_instance+0x180/0x310 [hclge] hclge_init_client_instance+0xcc/0x508 [hclge] hnae3_init_client_instance.part.3+0x3c/0x80 [hnae3] hnae3_register_client+0x134/0x1a8 [hnae3] 0x29c00014 do_one_initcall+0x9c/0x3e0 do_init_module+0xd4/0x2d8 load_module+0x3284/0x3690 __se_sys_init_module+0x274/0x308 __arm64_sys_init_module+0x40/0x50 el0_svc_handler+0xbc/0x210 el0_svc+0x8/0xc Freed by task 0: (stack is not available) The buggy address belongs to the object at 802185e06300 which belongs to the cache kmalloc-8k of size 8192 The buggy address is located 0 bytes to the right of 8192-byte region [802185e06300, 802185e08300) The buggy address belongs to the page: page:7fe008617800 refcount:1 mapcount:0 mapping:802340020e00 index:0x0 compound_mapcount: 0 flags: 0x5fffe0010200(slab|head) raw: 5fffe0010200 dead0100 dead0200 802340020e00 raw: 803e003e 0001 page dumped because: kasan: bad access detected Memory state around the buggy address: 802185e08200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 802185e08280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >802185e08300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ 802185e08380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc 802185e08400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 == Disabling lock debugging due to kernel taint [Steps to Reproduce] Enable KASAN and configure PAGE_SIZE to 64K, insmod hns roce driver and then rmmod it. [Actual Results] Call trace because of slab-out-of-bound. [Expected Results] Success [Reproducibility] Inevitably [Additional information] Hardware: D06 CS Firmware: NA Kernel: NA [Resolution] Not configure eq->next when number of eq_buf is 1 in eq_mhop_alloc().
[Kernel-packages] [Bug 1853993] Re: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853993 Title: [hns-1126]scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Won't Fix Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Disks will be lost on SAS interface reset [Fix] scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device [Test] Resetting SAS interfaces shall not lose any disks [Regression Potential] Patch only for hisi_sas. Lowest risk for other platform/driver. "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Retry 3 times TMF IO for SAS disks when init device To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853995] Re: [sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853995
Title:
[sas-1126]scsi: hisi_sas: Assign NCQ tag for all NCQ commands
Status in kunpeng920:
Fix Released
Status in kunpeng920 ubuntu-18.04 series:
Fix Released
Status in kunpeng920 ubuntu-18.04-hwe series:
Fix Released
Status in kunpeng920 ubuntu-19.04 series:
Fix Released
Status in kunpeng920 ubuntu-19.10 series:
Fix Released
Status in kunpeng920 ubuntu-20.04 series:
Fix Released
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
I/O error on blank Samsung SSD
[Test Case]
mkfs.ext4 on SSDs generates no I/O error
[Fix]
435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
[Regression Risk]
Patch restricted to hisi_sas driver.
"[Steps to Reproduce]
mkfs.ext4 to the special SAMSUNG M27LH960, and some IO error
[Actual Results]
Io error when the first time of mkfs.ext4
[ 745.809462] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=8
task=975f5cdf dev id=1 CQ hdr: 0x41d03 0x10008 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 776.028794] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 776.034612] sas: trying to find task 0x9656953a
[ 776.034613] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 776.042785] sas: sas_scsi_find_task: task 0x9656953a is done
[ 776.042786] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 776.049635] sas: trying to find task 0x975f5cdf
[ 776.049636] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 776.056053] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 776.056054] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 776.062900] sas: ata5: end_device-4:0: cmd error handler
[ 776.062914] sas: ata5: end_device-4:0: dev error handler
[ 776.062918] sas: ata6: end_device-4:1: dev error handler
[ 776.062920] ata5.00: exception Emask 0x0 SAct 0xc000 SErr 0x0 action
0x6 frozen
[ 776.062924] sas: ata7: end_device-4:2: dev error handler
[ 776.062926] sas: ata8: end_device-4:3: dev error handler
[ 776.070548] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.075669] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 30 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.090638] ata5.00: status: { DRDY }
[ 776.094290] ata5.00: failed command: SEND FPDMA QUEUED
[ 776.099410] ata5.00: cmd 64/01:00:00:00:00/00:00:00:00:00/a0 tag 31 ncq
dma 512 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 776.114399] ata5.00: status: { DRDY }
[ 776.118051] ata5: hard resetting link
[ 776.123198] hisi_sas_v3_hw :74:02.0: phydown: phy0 phy_state=0xfe
[ 776.129609] hisi_sas_v3_hw :74:02.0: ignore flutter phy0 down
[ 776.282642] hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=10(sata)
[ 776.289236] sas: sas_form_port: phy0 belongs to port0 already(1)!
[ 776.451784] ata5.00: configured for UDMA/133
[ 776.456043] ata5.00: device reported invalid CHS sector 0
[ 776.461423] ata5.00: device reported invalid CHS sector 0
[ 776.466807] ata5: EH complete
[ 776.469773] sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 2 tries: 1
[ 776.498528] hisi_sas_v3_hw :74:02.0: erroneous completion iptt=15
task=9656953a dev id=1 CQ hdr: 0x41d03 0x1000f 0x1 0x446 Error
info: 0x0 0x0 0x1 0x0
[ 806.740789] sas: Enter sas_scsi_recover_host busy: 2 failed: 2
[ 806.746604] sas: trying to find task 0x975f5cdf
[ 806.746605] sas: sas_scsi_find_task: aborting task 0x975f5cdf
[ 806.754732] sas: sas_scsi_find_task: task 0x975f5cdf is done
[ 806.754733] sas: sas_eh_handle_sas_errors: task 0x975f5cdf is done
[ 806.761582] sas: trying to find task 0x9656953a
[ 806.761584] sas: sas_scsi_find_task: aborting task 0x9656953a
[ 806.768002] sas: sas_scsi_find_task: task 0x9656953a is done
[ 806.768003] sas: sas_eh_handle_sas_errors: task 0x9656953a is done
[ 806.774852] sas: ata5: end_device-4:0: cmd error handler
[ 806.774864] sas: ata5: end_device-4:0: dev error handler
[ 806.774868] sas: ata6: end_device-4:1: dev error handler
[ 806.774870] ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6
frozen
[ 806.774873] ata5.00: failed command: SEND FPDMA QUEUED
[ 806.774875] sas: ata7: end_device-4:2: dev error handler
[ 806.774878]
[Kernel-packages] [Bug 1853997] Re: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset
** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853997 Title: [sas-1126]scsi: hisi_sas: Fix the conflict between device gone and host reset Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04 series: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-19.04 series: Fix Released Status in kunpeng920 ubuntu-19.10 series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Some SAS devices is gone when recovering [Test Case] No known test case, stress test on SAS deivce. [Fix] e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone and host reset [Regression Risk] Patch restricted to hisi_sas driver. "[Steps to Reproduce] 1. Close all the PHYS; 2. Inject error; 3. Open one PHY; [Actual Results] Some disk will be lost [Expected Results] No disk will be lost [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] When init device for SAS disks, it will send TMF IO to clear disks. At that time TMF IO is broken by some operations such as injecting controller reset from HW RAs event, the TMF IO will be timeout, and at last device will be gone. Print is as followed: hisi_sas_v3_hw :74:02.0: dev[240:1] found ... hisi_sas_v3_hw :74:02.0: controller resetting... hisi_sas_v3_hw :74:02.0: phyup: phy7 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy0 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy1 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy2 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy3 link_rate=9(sata) hisi_sas_v3_hw :74:02.0: phyup: phy6 link_rate=10(sata) hisi_sas_v3_hw :74:02.0: phyup: phy5 link_rate=11 hisi_sas_v3_hw :74:02.0: phyup: phy4 link_rate=11 hisi_sas_v3_hw :74:02.0: controller reset complete hisi_sas_v3_hw :74:02.0: abort tmf: TMF task timeout and not done hisi_sas_v3_hw :74:02.0: dev[240:1] is gone sas: driver on host :74:02.0 cannot handle device 5000c500a75a860d, error:5 To improve the reliability, retry TMF IO max of 3 times for SAS disks which is the same as softreset does." scsi: hisi_sas: Fix the conflict between device gone and host reset To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1853997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853964] Re: [hns-1126]net: hns3: make hclge_service use delayed workqueue
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853964
Title:
[hns-1126]net: hns3: make hclge_service use delayed workqueue
Status in kunpeng920:
Fix Released
Status in kunpeng920 ubuntu-18.04 series:
Won't Fix
Status in kunpeng920 ubuntu-18.04-hwe series:
Fix Released
Status in kunpeng920 ubuntu-19.10 series:
Fix Released
Status in kunpeng920 ubuntu-20.04 series:
Fix Released
Status in kunpeng920 upstream-kernel series:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
System crashes when setting irq affinity and turning on/off on the interfaces
[Fix]
net: hns3: make hclge_service use delayed workqueue
[Test]
Writing smp_affinity_list and turning on/off in loop
[Regression Potential]
This patch only for hns3. Lowest risk for other platform/driver
"[Bug Description]
Currently, up/down port process may concurrently operate
timer(del_timer_sync/add_timer_on) with setting IRQ affinity, and cause system
breaking down.
[Steps to Reproduce]
set misc irp affinity of PF during up/down port by follow script:
while((1))
do
for i in {0..31}; do echo $i > /proc/irq/678/smp_affinity_list; done
done
while((1))
do
ifconfig eth4 down
ifconfig eth4 up
done
[Actual Results]
System break down.
kernel call trace
[Expected Results]
System run normally.
[Reproducibility]
Inevitably
[Additional information]
Hardware: D06
Firmware: NA
Kernel: NA
[Resolution]
This patch uses delayed work instead of using timers to trigger the
hclge_serive."
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1853964/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
