[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929901] Re: [EHL][TGL] EDAC support
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support Status in intel: New Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: In Progress Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- Mailing list: https://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 1936769] Re: [Braswell] HDMI monitors don't work when powered off and on again
I think this might be a monitor problem. I swapped the VGA and HDMI monitors and the system now comes back up as it should BUT I have done this before and then it went bad again. I think the next thing is to see if the Lenovo monitor has a software upgrade but their website is down, so wait and see I guess. Regards, Graeme. On Tue, Jul 20, 2021 at 11:05 AM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > The first thing we need to do is check to see if this is a Xorg-specific > bug. Please try logging out (or rebooting) and select 'Ubuntu on > Wayland' on the login screen (button in the bottom right corner). After > you do that, does this bug still occur? > > > ** Summary changed: > > - [Braswell] HDMI not working properly > + [Braswell] HDMI monitors don't work when powered off and on again > > ** Changed in: linux-hwe-5.8 (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI monitors don't work when powered off and on again > > Status in linux-hwe-5.8 package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > 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-hwe-5.8/+bug/1936769/+subscriptions > > -- You received this bug notification because you are a member
Re: [Kernel-packages] [Bug 1936769] Re: [Braswell] HDMI monitors don't work when powered off and on again
Thanks again for your reply For some reason I nearly missed your email, Google sent it to Promotions and I only found it because it came up on my phone. Cold reboot does not show the option of Wayland but logging out did but the HDMI still failed to come up. I also tried running both Bionic Beaver and Xubuntu from DVD but the problem still existed. This makes me wonder if somehow it is a computer problem; although HP is said to be maximized for Ubuntu. When it was current BB worked OK. It is only since upgrade the problem has existed. Hope you have some more thoughts on the matter. Thanks again, Graeme On Tue, Jul 20, 2021 at 11:05 AM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > The first thing we need to do is check to see if this is a Xorg-specific > bug. Please try logging out (or rebooting) and select 'Ubuntu on > Wayland' on the login screen (button in the bottom right corner). After > you do that, does this bug still occur? > > > ** Summary changed: > > - [Braswell] HDMI not working properly > + [Braswell] HDMI monitors don't work when powered off and on again > > ** Changed in: linux-hwe-5.8 (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI monitors don't work when powered off and on again > > Status in linux-hwe-5.8 package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > 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
[Kernel-packages] [Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() Status in linux package in Ubuntu: Confirmed Bug description: I'm seeing a non-deterministic panic in the ZFS code. Last boot, this occurred in systemd-udevd, resulting in a failed boot. The boot before that, firefox hit the same thing, and this boot it looks like it's hit an Evolution component. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 4988 F pulseaudio /dev/snd/controlC1: chris 4988 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:49:47 2021 InstallationDate: Installed on 2021-05-13 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.198 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1543919] Re: Remove EISA support from main kernel image and make it M (modular)
I've an emachines®/acer® EL1210-09 (Advance Micro Devices Inc. Athlon LE-1620 (P/N ADH1620IAA5DH); nVIDIA® nForce® 780a SLI with planar C77 a2 GPU; nVIDIA® GF119 a1 GPU on PCIe 2.0 x16 slot). The system DMesg predictably detects no EISA resources on probing platform eisa.0, so EISA.c and related headers can be compiled as a module with no effect on my system's kernel initialization. AFAIK, Intel PCI has replaced EISA on all x86 and x86_64 systems built after 2000. The following redact from /var/log/dmesg.0 on 17 July 2021 illustrates typical info: [0.00] kernel: Linux version 5.8.0-59-generic (buildd@lcy01-amd64-022) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 (Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18) [0.00] kernel: Command line: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=c4248af1-a4cf-49a2-ba18-4de2c65c815c ro acpi_force_32bit_fadt_addr acpi_rev_override check_enable_amd_mmconf pcie_bus_tune=off pcie_aspm=off pci_ports=native intremap=off agp=off nohugeiomap parport=0 hashdist=0 ... [0.212298] kernel: EISA bus registered ... [1.006643] kernel: platform eisa.0: Probing EISA bus 0 [1.006715] kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard [1.006779] kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 [1.006855] kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 [1.006917] kernel: platform eisa.0: EISA: Detected 0 cards I concur on the feasibility of offloading EISA from Kernel core and building a Module EISA.ko. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543919 Title: Remove EISA support from main kernel image and make it M (modular) Status in linux package in Ubuntu: Triaged Bug description: (This is a sort of RfC. ) I have a PC that still has the good old PCI ports, but I am 100% sure that the active use of EISA dates back yet more 10 years. In other words, boards that _only_ support EISA date back 25 years now, while those that provide *one* EISA slot date back roughly 15 years (one of the Elitegroup K7 series comes to mind, from about 2001/02). So the EISA support *should* be provided, as we should even support ancient hardware (Linux principle :)) However, why the EISA support is *compiled in* is beyond me. For instance, it creates lots of totally unnecessary noise in dmesg: [0.08] EISA bus registered [1.598316] platform eisa.0: Probing EISA bus 0 [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1 (repeated 10 times, i=i+1) [1.598368] platform eisa.0: EISA: Detected 0 cards For a 1997 mainboard, this would make perfect sense. But it is very probable that said mainboard would require linux-image-extra nonetheless to support some days-of-yore chipset. So why not leave it as a *module*, while removing its support from main kernel image once and for all? Your turn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
@skidooman Could you try the software configuration you are using in #26, but disable UFW? I am using Precision 5750 from daily basis (it utilizes the same Wi-Fi firmware as yours), but I didn't encounter the firmware crash like yours so frequently, I can finish the meeting with Wi-Fi everyday, and I am using https://www.asus.com/Networking-IoT-Servers/WiFi-Routers/ASUS-WiFi-Routers/RT-AX56U/, which is Wi-Fi 6 too. From the log, the UFW keeps blocking the packet from the AP 192.168.1.1, then the firmware can't handle the request from driver and it is crashed. Sorry that we can't debug the firmware, since it is a pure binary from Intel. By the way, could you attach the Access Point information? I'll try if we can find the same model here in Taiwan. Thanks, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0] Status in Linux Firmware: New Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Bug description: Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost. - If I am on a wire, this problem does NOT occur. - This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom) - This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame. - As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update. - As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information). - I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 Uname: Linux 5.10.0-1029-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:47:58 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0991] InstallationDate: Installed on 2021-04-24 (54 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2021 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.1 dmi.board.name: 08607K dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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:
[Kernel-packages] [Bug 1933707] Re: Many ACPI errors
** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933707 Title: Many ACPI errors Status in linux package in Ubuntu: Won't Fix Bug description: Many ACPI errors in dmesg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-23-generic 5.11.0-23.24 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi1338 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 04:03:56 2021 InstallationDate: Installed on 2021-04-25 (61 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Acer Aspire A515-56 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-23-generic root=UUID=0c5f066e-35cd-4f76-a271-a1c97ba74ee3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-23-generic N/A linux-backports-modules-5.11.0-23-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936448] Re: Elantech touchpad not recognized on Asus K55N laptop
Not happening anymore. ** Changed in: linux (Ubuntu) Status: New => 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/1936448 Title: Elantech touchpad not recognized on Asus K55N laptop Status in linux package in Ubuntu: Invalid Bug description: output from /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=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 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/input3 U: Uniq= H: Handlers=kbd event3 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/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef 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/PNP0A03:00/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=0461 Product=4d81 Version=0111 N: Name="USB Optical Mouse" P: Phys=usb-:00:12.0-1/input0 S: Sysfs=/devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/0003:0461:4D81.0001/input/input8 U: Uniq= H: Handlers=mouse0 event6 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0019 Vendor=1043 Product= Version= N: Name="Asus Wireless Radio Control" P: Phys=asus-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/ATK4001:00/input/input9 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input10 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=100013 B: KEY=10008 0 0 0 0 181606f0090 8280027801701000 e 0 B: MSC=10 I: Bus=0003 Vendor=1bcf Product=2883 Version=0429 N: Name="ASUS USB2.0 Webcam: ASUS USB2.0" P: Phys=usb-:00:13.2-4/button S: Sysfs=/devices/pci:00/:00:13.2/usb2/2-4/2-4:1.0/input/input11 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA ATI HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:14.2/sound/card1/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:14.2/sound/card1/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: perry 837 F pulseaudio /dev/snd/controlC0: perry 837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 15 19:12:00 2021 InstallationDate: Installed on 2021-07-16 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUSTeK COMPUTER INC. K55N ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=1c3c6b9b-6587-47fa-9ade-530961cc9f65 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A
[Kernel-packages] [Bug 1936769] Re: [Braswell] HDMI monitors don't work when powered off and on again
The first thing we need to do is check to see if this is a Xorg-specific bug. Please try logging out (or rebooting) and select 'Ubuntu on Wayland' on the login screen (button in the bottom right corner). After you do that, does this bug still occur? ** Summary changed: - [Braswell] HDMI not working properly + [Braswell] HDMI monitors don't work when powered off and on again ** Changed in: linux-hwe-5.8 (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1936769 Title: [Braswell] HDMI monitors don't work when powered off and on again Status in linux-hwe-5.8 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] InstallationDate: Installed on 2020-11-05 (255 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP 510-a112a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2018 dmi.bios.release: 5.11 dmi.bios.vendor: AMI dmi.bios.version: F.33 dmi.board.asset.tag: CNV7380P8W dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV7380P8W dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-a112a dmi.product.sku: W2S68AA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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-hwe-5.8/+bug/1936769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Thanks for that. It would seem the only common factor is the kernel so this is now a kernel bug. ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work Status in linux package in Ubuntu: New Bug description: The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and ubuntu 20.10). When this occurs all other mouse operations still function - left/right click - scroll wheel - mouse position still moves Just the actual mouse pointer not visible. Only way to resolve is to restart the machine. Tried numerous ways to restart the mouse driver but nothing else successful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 14:45:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2021-07-05 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Apple Inc. iMac10,1 ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 initrd=boot\initrd.img-5.8.0-59-generic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268DC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1935728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936009] Re: [SRU] The internal mic of Dell Precision 5750 can't record sound
** Summary changed: - The internal mic of Dell Precision 5750 can't record sound + [SRU] The internal mic of Dell Precision 5750 can't record sound -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: [SRU] The internal mic of Dell Precision 5750 can't record sound Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: In Progress Status in alsa-ucm-conf source package in Impish: In Progress Bug description: [Impact] After upgrade the linux kernel, the mixer names of rt715 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't record sound from internal mic since the internal mic is routed to the codec rt715. [Fix] Backport 3 upstream commits, after applying these 3 commits, the ucm conf file dosn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] run 'alsactl init 1' on the precision 5750 with old and new kernel, there is no error logs, use the internal mic to record sound, it could record successfully. [Where problems will occur] The change only affects the rt715 codec, so far, that codec only connects to the internal mic on Dell soundwire audio machines, so it could introduce regression on the internal mic like users can't record sound via internal mic anymore on the Dell soundwire audio machines. But this possibility is very low since we already tested these 3 commits on different Dell soundwire audio machines (latitude and precision). We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936868] Re: monitor flickers when input is changed back
To be abundantly clear: There's NO DisplayPort adapter here, the problem happens with the laptop that's connected to the external monitor using an HDMI cable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936868 Title: monitor flickers when input is changed back Status in linux package in Ubuntu: New Bug description: Hi there! I have a Lenovo Carbon X1 and I use an external HP Z27 4K monitor. I have the monitor connected to the Lenovo laptop using a HDMI cable. I also have the same monitor connected to a Dell desktop computer using a DP cable. I can change the selected input on the monitor from HDMI (laptop) to DP (desktop). The problem is that when I change it back, both the external monitor AND the laptop screen flicker as if I had physically plugged in the monitor. Checking dmesg, I'm getting the following messages: ``` [616849.330989] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [616853.593595] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 ``` Sometimes I get back my desktop, but more often then not the external monitor is stuck as 1920*1080 and I have to use `autorandr` to fix that. ``` lsb_release -rd Description:Ubuntu 21.04 Release:21.04 ``` ``` uname -a Linux my-laptop 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936868] Re: monitor flickers when input is changed back
Attached /sys/kernel/debug/dri/0/i915_display_info ** Attachment added: "i915_display_info.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+attachment/5511965/+files/i915_display_info.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/1936868 Title: monitor flickers when input is changed back Status in linux package in Ubuntu: New Bug description: Hi there! I have a Lenovo Carbon X1 and I use an external HP Z27 4K monitor. I have the monitor connected to the Lenovo laptop using a HDMI cable. I also have the same monitor connected to a Dell desktop computer using a DP cable. I can change the selected input on the monitor from HDMI (laptop) to DP (desktop). The problem is that when I change it back, both the external monitor AND the laptop screen flicker as if I had physically plugged in the monitor. Checking dmesg, I'm getting the following messages: ``` [616849.330989] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [616853.593595] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 ``` Sometimes I get back my desktop, but more often then not the external monitor is stuck as 1920*1080 and I have to use `autorandr` to fix that. ``` lsb_release -rd Description:Ubuntu 21.04 Release:21.04 ``` ``` uname -a Linux my-laptop 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936868] Re: monitor flickers when input is changed back
Attached lspci-vnvn.log ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+attachment/5511964/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936868 Title: monitor flickers when input is changed back Status in linux package in Ubuntu: New Bug description: Hi there! I have a Lenovo Carbon X1 and I use an external HP Z27 4K monitor. I have the monitor connected to the Lenovo laptop using a HDMI cable. I also have the same monitor connected to a Dell desktop computer using a DP cable. I can change the selected input on the monitor from HDMI (laptop) to DP (desktop). The problem is that when I change it back, both the external monitor AND the laptop screen flicker as if I had physically plugged in the monitor. Checking dmesg, I'm getting the following messages: ``` [616849.330989] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [616853.593595] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 ``` Sometimes I get back my desktop, but more often then not the external monitor is stuck as 1920*1080 and I have to use `autorandr` to fix that. ``` lsb_release -rd Description:Ubuntu 21.04 Release:21.04 ``` ``` uname -a Linux my-laptop 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936868] [NEW] monitor flickers when input is changed back
Public bug reported: Hi there! I have a Lenovo Carbon X1 and I use an external HP Z27 4K monitor. I have the monitor connected to the Lenovo laptop using a HDMI cable. I also have the same monitor connected to a Dell desktop computer using a DP cable. I can change the selected input on the monitor from HDMI (laptop) to DP (desktop). The problem is that when I change it back, both the external monitor AND the laptop screen flicker as if I had physically plugged in the monitor. Checking dmesg, I'm getting the following messages: ``` [616849.330989] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [616853.593595] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 ``` Sometimes I get back my desktop, but more often then not the external monitor is stuck as 1920*1080 and I have to use `autorandr` to fix that. ``` lsb_release -rd Description:Ubuntu 21.04 Release:21.04 ``` ``` uname -a Linux my-laptop 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1936868/+attachment/5511963/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936868 Title: monitor flickers when input is changed back Status in linux package in Ubuntu: New Bug description: Hi there! I have a Lenovo Carbon X1 and I use an external HP Z27 4K monitor. I have the monitor connected to the Lenovo laptop using a HDMI cable. I also have the same monitor connected to a Dell desktop computer using a DP cable. I can change the selected input on the monitor from HDMI (laptop) to DP (desktop). The problem is that when I change it back, both the external monitor AND the laptop screen flicker as if I had physically plugged in the monitor. Checking dmesg, I'm getting the following messages: ``` [616849.330989] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 [616853.593595] [drm:drm_dp_dual_mode_detect [drm_kms_helper]] *ERROR* Unexpected DP dual mode adaptor ID 50 ``` Sometimes I get back my desktop, but more often then not the external monitor is stuck as 1920*1080 and I have to use `autorandr` to fix that. ``` lsb_release -rd Description:Ubuntu 21.04 Release:21.04 ``` ``` uname -a Linux my-laptop 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890848] Re: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels
Also to be clear, from jjohansen's comment to me last week, all of the necessary patches are available in the 5.4 focal kernel, so kernels for UC20 from canonical snaps should contain this fix on the 20 track. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890848 Title: 'ptrace trace' needed to readlink() /proc/*/ns/* files on older kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: SRU Justification: [Impact] Permission 'ptrace trace' is required to readlink() /proc/*/ns/*, when only 'ptrace read' should be required according to 'man namespaces': "Permission to dereference or read (readlink(2)) these symbolic links is governed by a ptrace access mode PTRACE_MODE_READ_FSCREDS check; see ptrace(2)." [Fix] Upstream commit 338d0be437ef10e247a35aed83dbab182cf406a2 fixes ptrace read check. [Test Plan] BugLink contains the source of a binary that reproduces the issue. In summary, it executes readlink() on /proc/*/ns/*. There's also a policy that has only 'ptrace read' permission. When the bug is fixed, execution is allowed. [Where problems could occur] The regression can be considered as low, since it's lowering the number of permissions required. Existing policies that already contain the permission 'ptrace trace' and 'ptrace read' will have a broader policy than required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
The previous SRU of dahdi-linux was release to -security and -updates. I'd imagine this one also needs to be released to -updates and -security but I don't see that in the description, am I correct in thinking it needs to go to -security? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Does this too need to go to -security and -updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936863] [NEW] Hirsute update: upstream stable patchset 2021-07-19
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-07-19 Ported from the following upstream stable releases: v5.10.47, v5.12.14 from git://git.kernel.org/ linux/bits.h: fix compilation error with GENMASK module: limit enabling module.sig_enforce drm: add a locked version of drm_is_current_master drm/nouveau: wait for moving fence after pinning v2 drm/radeon: wait for moving fence after pinning drm/amdgpu: wait for moving fence after pinning ARM: 9081/1: fix gcc-10 thumb2-kernel regression mmc: meson-gx: use memcpy_to/fromio for dram-access-quirk spi: spi-nxp-fspi: move the register operation after the clock enable Revert "PCI: PM: Do not read power state in pci_enable_device_flags()" drm/vc4: hdmi: Move the HSM clock enable to runtime_pm drm/vc4: hdmi: Make sure the controller is powered in detect x86/entry: Fix noinstr fail in __do_fast_syscall_32() x86/xen: Fix noinstr fail in exc_xen_unknown_trap() locking/lockdep: Improve noinstr vs errors perf/x86/lbr: Remove cpuc->lbr_xsave allocation from atomic context perf/x86/intel/lbr: Zero the xstate buffer on allocation dmaengine: zynqmp_dma: Fix PM reference leak in zynqmp_dma_alloc_chan_resourc() dmaengine: stm32-mdma: fix PM reference leak in stm32_mdma_alloc_chan_resourc() UBUNTU: [Config] update annotations for XILINX_ZYNQMP_DPDMA dmaengine: xilinx: dpdma: Add missing dependencies to Kconfig dmaengine: xilinx: dpdma: Limit descriptor IDs to 16 bits mac80211: remove warning in ieee80211_get_sband() mac80211_hwsim: drop pending frames on stop cfg80211: call cfg80211_leave_ocb when switching away from OCB dmaengine: rcar-dmac: Fix PM reference leak in rcar_dmac_probe() dmaengine: mediatek: free the proper desc in desc_free handler dmaengine: mediatek: do not issue a new desc if one is still current dmaengine: mediatek: use GFP_NOWAIT instead of GFP_ATOMIC in prep_dma net: ipv4: Remove unneed BUG() function mac80211: drop multicast fragments net: ethtool: clear heap allocations for ethtool function inet: annotate data race in inet_send_prepare() and inet_dgram_connect() ping: Check return value of function 'ping_queue_rcv_skb' net: annotate data race in sock_error() inet: annotate date races around sk->sk_txhash net/packet: annotate data race in packet_sendmsg() net: phy: dp83867: perform soft reset and retain established link riscv32: Use medany C model for modules net: caif: fix memory leak in ldisc_open net/packet: annotate accesses to po->bind net/packet: annotate accesses to po->ifindex r8152: Avoid memcpy() over-reading of ETH_SS_STATS sh_eth: Avoid memcpy() over-reading of ETH_SS_STATS r8169: Avoid memcpy() over-reading of ETH_SS_STATS KVM: selftests: Fix kvm_check_cap() assertion net: qed: Fix memcpy() overflow of qed_dcbx_params() mac80211: reset profile_periodicity/ema_ap mac80211: handle various extensible elements correctly recordmcount: Correct st_shndx handling PCI: Add AMD RS690 quirk to enable 64-bit DMA net: ll_temac: Add memory-barriers for TX BD access net: ll_temac: Avoid ndo_start_xmit returning NETDEV_TX_BUSY perf/x86: Track pmu in per-CPU cpu_hw_events pinctrl: stm32: fix the reported number of GPIO lines per bank i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access gpiolib: cdev: zero padding during conversion to gpioline_info_changed scsi: sd: Call sd_revalidate_disk() for ioctl(BLKRRPART) nilfs2: fix memory leak in nilfs_sysfs_delete_device_group s390/stack: fix possible register corruption with stack switch helper KVM: do not allow mapping valid but non-reference-counted pages i2c: robotfuzz-osif: fix control-request directions ceph: must hold snap_rwsem when filling inode for async create kthread_worker: split code for canceling the delayed work timer kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync() x86/fpu: Preserve supervisor states in sanitize_restored_user_xstate() x86/fpu: Make init_fpstate correct with optimized XSAVE mm/rmap: remove unneeded semicolon in page_not_mapped() mm/rmap: use page_not_mapped in try_to_unmap() mm, thp: use head page in __migration_entry_wait() mm/thp: fix __split_huge_pmd_locked() on shmem migration entry mm/thp: make is_huge_zero_pmd() safe and quicker mm/thp: try_to_unmap() use TTU_SYNC for safe splitting mm/thp: fix vma_address() if virtual address below file offset mm/thp: fix page_address_in_vma() on file THP tails mm/thp: unmap_mapping_page() to fix THP truncate_cleanup_page() mm: thp: replace DEBUG_VM BUG with
[Kernel-packages] [Bug 1936858] [NEW] Groovy update: upstream stable patchset 2021-07-19
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-07-19 Ported from the following upstream stable releases: v5.4.129, v5.10.47 from git://git.kernel.org/ module: limit enabling module.sig_enforce drm/nouveau: wait for moving fence after pinning v2 drm/radeon: wait for moving fence after pinning ARM: 9081/1: fix gcc-10 thumb2-kernel regression mmc: meson-gx: use memcpy_to/fromio for dram-access-quirk MIPS: generic: Update node names to avoid unit addresses spi: spi-nxp-fspi: move the register operation after the clock enable Revert "PCI: PM: Do not read power state in pci_enable_device_flags()" dmaengine: zynqmp_dma: Fix PM reference leak in zynqmp_dma_alloc_chan_resourc() mac80211: remove warning in ieee80211_get_sband() mac80211_hwsim: drop pending frames on stop cfg80211: call cfg80211_leave_ocb when switching away from OCB dmaengine: rcar-dmac: Fix PM reference leak in rcar_dmac_probe() dmaengine: mediatek: free the proper desc in desc_free handler dmaengine: mediatek: do not issue a new desc if one is still current dmaengine: mediatek: use GFP_NOWAIT instead of GFP_ATOMIC in prep_dma net: ipv4: Remove unneed BUG() function mac80211: drop multicast fragments net: ethtool: clear heap allocations for ethtool function ping: Check return value of function 'ping_queue_rcv_skb' inet: annotate date races around sk->sk_txhash net: phy: dp83867: perform soft reset and retain established link net: caif: fix memory leak in ldisc_open net/packet: annotate accesses to po->bind net/packet: annotate accesses to po->ifindex r8152: Avoid memcpy() over-reading of ETH_SS_STATS sh_eth: Avoid memcpy() over-reading of ETH_SS_STATS r8169: Avoid memcpy() over-reading of ETH_SS_STATS KVM: selftests: Fix kvm_check_cap() assertion net: qed: Fix memcpy() overflow of qed_dcbx_params() recordmcount: Correct st_shndx handling PCI: Add AMD RS690 quirk to enable 64-bit DMA net: ll_temac: Add memory-barriers for TX BD access net: ll_temac: Avoid ndo_start_xmit returning NETDEV_TX_BUSY pinctrl: stm32: fix the reported number of GPIO lines per bank nilfs2: fix memory leak in nilfs_sysfs_delete_device_group KVM: do not allow mapping valid but non-reference-counted pages i2c: robotfuzz-osif: fix control-request directions kthread_worker: split code for canceling the delayed work timer kthread: prevent deadlock when kthread_mod_delayed_work() races with kthread_cancel_delayed_work_sync() mm: add VM_WARN_ON_ONCE_PAGE() macro mm/rmap: remove unneeded semicolon in page_not_mapped() mm/rmap: use page_not_mapped in try_to_unmap() mm, thp: use head page in __migration_entry_wait() mm/thp: fix __split_huge_pmd_locked() on shmem migration entry mm/thp: make is_huge_zero_pmd() safe and quicker mm/thp: try_to_unmap() use TTU_SYNC for safe splitting mm/thp: fix vma_address() if virtual address below file offset mm/thp: fix page_address_in_vma() on file THP tails mm/thp: unmap_mapping_page() to fix THP truncate_cleanup_page() mm: thp: replace DEBUG_VM BUG with VM_WARN when unmap fails for split mm: page_vma_mapped_walk(): use page for pvmw->page mm: page_vma_mapped_walk(): settle PageHuge on entry mm: page_vma_mapped_walk(): use pmde for *pvmw->pmd mm: page_vma_mapped_walk(): prettify PVMW_MIGRATION block mm: page_vma_mapped_walk(): crossing page table boundary mm: page_vma_mapped_walk(): add a level of indentation mm: page_vma_mapped_walk(): use goto instead of while (1) mm: page_vma_mapped_walk(): get vma_address_end() earlier mm/thp: fix page_vma_mapped_walk() if THP mapped by ptes mm/thp: another PVMW_SYNC fix in page_vma_mapped_walk() mm, futex: fix shared futex pgoff on shmem huge page UBUNTU: [Config] enable CONFIG_SYSTEM_REVOCATION_LIST certs: Add EFI_CERT_X509_GUID support for dbx entries certs: Move load_system_certificate_list to a common function drm/amdgpu: wait for moving fence after pinning arm64: Ignore any DMA offsets in the max_zone_phys() calculation arm64: Force NO_BLOCK_MAPPINGS if crashkernel reservation is required locking/lockdep: Improve noinstr vs errors dmaengine: stm32-mdma: fix PM reference leak in stm32_mdma_alloc_chan_resourc() inet: annotate data race in inet_send_prepare() and inet_dgram_connect() net: annotate data race in sock_error() net/packet: annotate data race in packet_sendmsg() riscv32: Use medany C model for modules mac80211: reset profile_periodicity/ema_ap mac80211: handle various extensible elements correctly i2c: i801: Ensure that SMBHSTSTS_INUSE_STS is cleared when leaving i801_access s390/stack: fix
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
470 just got out of beta today: https://www.nvidia.com/Download/driverResults.aspx/177145/en-us https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470 shows in which repositories including PPAs it is available in. Currently only the beta is listed there. And a bug to track the testing and releases should be listed on https://people.canonical.com/~ubuntu-archive/pending-sru.html soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow
[Kernel-packages] [Bug 1932169] Re: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted rtl8812au into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: rtl8812au (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932169 Title: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in rtl8812au package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Status in rtl8812au source package in Focal: Fix Committed Bug description: [Impact] This is a scripted bug report about ADT failures while running rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz [Test Plan] sudo apt-get install rtl8812au-dkms [Where problems could occur] There could be run time regressions in the functionality of the driver due to the compatibility changes required for successful compilation against linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
New debdiff for the backport from impish to focal in attach. ** Patch added: "lttng-modules-backport-from-impish.debdiff" https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5511922/+files/lttng-modules-backport-from-impish.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385113]
"unknown main tag item 0x0" comes from the HID layer, it has nothing to do with Bluetooth or connection stability. It's usually a stray NUL character at the end of the HID descriptor which the kernel safely ignores but still logs. In my own driver development (xpadneo), I just shorten the HID descriptor by one byte if it ends with NUL because the devices I work with are known to NUL-terminate their HID descriptors. Maybe the kernel should do the same: If the last HID descriptor byte is a NUL-byte, it should simply shorten the HID descriptor by one byte, essentially cutting the offending byte off, and the message would be gone. Other than a log message, it has no consequences in the kernel, it comes from a completely different layer that's not related to Bluetooth at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385113]
The bug is still here in 5.12.13 with asaus m-rbb93 logitech b370 mouse. After some time (unpredictable, can be few hours or few minutes) mouse pointer stops responding, though mouse appears conneceted in the bluetoothctl. > bluetoothctl Agent registered [Bluetooth Travel Mouse]# info Device 00:07:61:68:D2:9E (public) Name: Bluetooth Travel Mouse Alias: Bluetooth Travel Mouse Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes WakeAllowed: yes LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB002d4809 journalctl and dmesg is silent when the mouse stops responding. Is there any other way to debug this? When mouse is first connected, dmesg has the message mentioned as the topic of this bug: [185307.429898] hid-generic 0005:046D:B002.002C: input,hidraw1: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on dc:e9:94:7e:5f:86 [187430.340610] hid-generic 0005:046D:B002.002D: unknown main item tag 0x0 [187430.340668] input: Bluetooth Travel Mouse as /devices/pci:00/:00:08.1/:05:00.4/usb3/3-3/3-3:1.0/bluetooth/hci0/hci0:1/0005:046D:B002.002D/input/input104 (In reply to jbMacAZ from comment #5) > The issue was fixed for the Asus T100 (baytrail) 2-in-1 family. See this > commit. > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ > commit/?id=c4c285da1ee18582ace366f07e56e355c20ebc49 which is in kernel 4.15. Is there a way to enable this system-wide without patching a kernel, for a quick test? I tried to add btusb.enable_autosuspend=n kernel paremeter: # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.12.13-1-default root=UUID=ece1a448-6944-4f34-a61c-1742fde2ac3c splash=silent psi=1 nvidia-drm.modeset=1 btusb.enable_autosuspend=n quiet mitigations=auto # systool -v -m btusb Module = "btusb" Attributes: coresize= "69632" initsize= "0" initstate = "live" refcnt = "0" srcversion = "8EADE2557C147180496F74C" taint = "" uevent = version = "0.8" Parameters: disable_scofix = "N" enable_autosuspend = "N" force_scofix= "N" reset = "Y" But this does not resolve the bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1385113]
Bug still present in 5.10.4-1-default -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1385113]
I have the same issues with my bluetooth keybloard on 5.9.2-1.g4133ad1-default (Tumbleweed). hid-generic 0005:04CA:006C.0009: unknown main item tag 0x0 Very annoying. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1385113 Title: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: Message with Mouse Bluetooth [ 32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-23-generic 3.16.0-23.31 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3344 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 24 05:22:54 2014 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-23-generic N/A linux-backports-modules-3.16.0-23-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1385113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932173] Please test proposed package
Hello Kleber, or anyone else affected, Accepted xtables-addons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xtables- addons/3.9-1ubuntu0.2~20.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932173 Title: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in xtables-addons package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in xtables-addons source package in Focal: Fix Committed Bug description: [Impact] This is a scripted bug report about ADT failures while running xtables-addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210611_210642_1c193@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210612_124839_710ee@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210611_211032_cbce4@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210611_210646_8bf21@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210611_210425_4d74a@/log.gz [Test Plan] sudo apt-get install xtables-addons-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted broadcom-sta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/broadcom- sta/6.30.223.271-12ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: broadcom-sta (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932160 Title: broadcom-sta/6.30.223.271-12 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in broadcom-sta package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in broadcom-sta source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz [Test Plan] sudo apt-get install broadcom-sta-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
@Pierre, can you help me verify the Groovy kernel here? https://people.canonical.com/~mschiu77/lp1915117/G/ I need to know if it's working with the existing firmware and the ucm files. Thanks -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Bad debdiff, ignore it for now, new debdiff incoming. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I've just created a ppa with the latest lttng-modules-dkms from impish recompiled for focal https://launchpad.net/~arighi/+archive/ubuntu/lttng/ And tested (ubuntu_lttng_smoke_test) with the 5.11 hwe and 5.4 kernels. Everything looks good with both kernels. The debdiff in attach (against the impish version) only contains the changelog entry to backport the version from impish to focal. ** Patch added: "lttng-modules-backport-from-impish.debdiff" https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5511895/+files/lttng-modules-backport-from-impish.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935833] Re: linux-azure CIFS DFS oops
Microsoft reports "Engineer confirms, test kernel certainly helps with the oops.". Marking verification done on the basis of MS testing. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1935833 Title: linux-azure CIFS DFS oops Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] A Microsoft customer is reporting a kernel oops when attempting a DFS connection. [Fix] a52930353eaf443489a350a135c5525a4acbbf56 cifs: handle empty list of targets in cifs_reconnect() baf3f08ef4083b76ca67b143e135213a7f941879 cifs: get rid of unused parameter in reconn_setup_dfs_targets() The addition of these 2 patches has been confirmed to prevent the oops. [Test Case] Mount a Windows DFS share [Where problems could occur] Mounts could continue to fail even though the kernel no longer crashes. [Other Info] SF: #00313885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This commit has been released with no regressions detected. Marking
verification done.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1930626
Title:
scsi: storvsc: Parameterize number hardware queues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux-azure source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-azure source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-azure source package in Impish:
Fix Released
Bug description:
Microsoft would like to request inclusion of the following patch in
the 5.4 and later kernels:
a81a38cc6dda ("scsi: storvsc: Parameterize number hardware queues")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?id=a81a38cc6ddaf128c7ca9e3f21c243f33c97
This patch adds the ability to set the number of hardware queues with
new module parameter, storvsc_max_hw_queues.
This functionality is useful in Microsoft Azure) where decreasing the
number of hardware queues has been shown to improve performance.
https://canonical.lightning.force.com/lightning/r/Case/5004K05qB6EQAU/view
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930626/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
Note that bare metal boots also fail the same way w/ the MDS workaround enabled (failing VM boots all had a newer kernel running on the host): EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [0.00] Booting Linux on physical CPU 0x00 [0x503f0002] [0.00] Linux version 4.15.0-147-generic (buildd@bos02-arm64-076) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #151-Ubuntu SMP Fri Jun 18 19:18:37 UTC 2021 (Ubuntu 4.15.0-147.151-generic 4.15.18) [0.00] efi: Getting EFI parameters from FDT: [0.00] efi: EFI v2.70 by American Megatrends [0.00] efi: ACPI 2.0=0xbff596 SMBIOS 3.0=0xbff686fd98 ESRT=0xbff1a3a018 [0.00] esrt: Reserving ESRT space from 0x00bff1a3a018 to 0x00bff1a3a078. [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x00BFF596 24 (v02 ALASKA) [0.00] ACPI: XSDT 0x00BFF5960028 94 (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: FACP 0x00BFF59600C0 000114 (v06 Ampere eMAG 0003 INTL 20190509) [0.00] ACPI: DSDT 0x00BFF59601D8 0077CD (v05 ALASKA A M I 0001 INTL 20190509) [0.00] ACPI: FIDT 0x00BFF59679A8 9C (v01 ALASKA A M I 01072009 AMI 00010013) [0.00] ACPI: DBG2 0x00BFF5967A48 61 (v00 Ampere eMAG INTL 20190509) [0.00] ACPI: GTDT 0x00BFF5967AB0 000108 (v02 Ampere eMAG 0001 INTL 20190509) [0.00] ACPI: IORT 0x00BFF5967BB8 000BCC (v00 Ampere eMAG INTL 20190509) [0.00] ACPI: MCFG 0x00BFF5968788 AC (v01 Ampere eMAG 0001 INTL 20190509) [0.00] ACPI: SSDT 0x00BFF5968838 2D (v02 Ampere eMAG 0001 INTL 20190509) [0.00] ACPI: SPMI 0x00BFF5968868 41 (v05 ALASKA A M I AMI. ) [0.00] ACPI: APIC 0x00BFF59688B0 000A68 (v04 Ampere eMAG AMP. 0113) [0.00] ACPI: PCCT 0x00BFF5969318 0005D0 (v01 Ampere eMAG 0003 0113) [0.00] ACPI: BERT 0x00BFF59698E8 30 (v01 Ampere eMAG 0003 INTL 20190509) [0.00] ACPI: HEST 0x00BFF5969918 000328 (v01 Ampere eMAG 0003 INTL 20190509) [0.00] ACPI: SPCR 0x00BFF5969C40 50 (v02 A M I APTIO V 01072009 AMI. 0005000D) [0.00] ACPI: PPTT 0x00BFF5969C90 000CB8 (v01 Ampere eMAG 0003 0113) [0.00] ACPI: SPCR: console: pl011,mmio32,0x1260,115200 [0.00] ACPI: NUMA: Failed to initialise from firmware [0.00] NUMA: Faking a node at [mem 0x9000-0x00bf] [0.00] NUMA: NODE_DATA [mem 0xbe7d00-0xbeafff] [0.00] Zone ranges: [0.00] DMA [mem 0x9000-0x] [0.00] Normal [mem 0x0001-0x00bf] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x9000-0x91ff] [0.00] node 0: [mem 0x9200-0x928f] [0.00] node 0: [mem 0x9290-0xfffb] [0.00] node 0: [mem 0xfffc-0x] [0.00] node 0: [mem 0x00088000-0x000f] [0.00] node 0: [mem 0x0088-0x00bff5913fff] [0.00] node 0: [mem 0x00bff5914000-0x00bff595] [0.00] node 0: [mem 0x00bff596-0x00bff59d] [0.00] node 0: [mem 0x00bff59e-0x00bff7de] [0.00] node 0: [mem 0x00bff7df-0x00bff7e5] [0.00] node 0: [mem 0x00bff7e6-0x00bff7ff] [0.00] node 0: [mem 0x00bff800-0x00bf] [0.00] Initmem setup node 0 [mem 0x9000-0x00bf] [0.00] psci: probing for conduit method from ACPI. [0.00] psci: PSCIv1.1 detected in firmware. [0.00] psci: Using standard PSCI v0.2 function IDs [0.00] psci: MIGRATE_INFO_TYPE not supported. [0.00] psci: SMC Calling Convention v1.1 [0.00] random: get_random_bytes called from start_kernel+0xa8/0x478 with crng_init=0 [0.00] percpu: Embedded 25 pages/cpu s62232 r8192 d31976 u102400 [0.00] Detected PIPT I-cache on CPU0 [0.00] ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware [0.00] CPU features: enabling workaround for Speculative Store Bypass Disable [0.00] CPU features: detected: Kernel page table isolation (KPTI) [0.00] Built 1 zonelists, mobility grouping on. Total pages: 65995776 [0.00] Policy zone: Normal [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-147-generic
[Kernel-packages] [Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
No regressions have been detected. Marking verification done.
** Tags removed: verification-needed-focal verification-needed-groovy
verification-needed-hirsute
** Tags added: verification-done-focal verification-done-groovy
verification-done-hirsute
--
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/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
Status in linux package in Ubuntu:
In Progress
Status in linux-azure package in Ubuntu:
New
Status in linux source package in Focal:
In Progress
Status in linux-azure source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux-azure source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-azure source package in Impish:
New
Bug description:
[Impact]
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the
kernel block layer in Linux 5.1 changes the way multiple pages are
merged to a single block I/O descriptor, and how contiguous block I/O
descriptors are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined
by the hv_storvsc driver, the new block merge process can create two
pages of block I/O requests (the latter page with an offset) that
refer to the same physical sector on disk. This page list is then
assembled for the SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly
parse the page array from the SCSI generic driver due to this bug in
Linux block layer and creates a potential overflow of offset I/O
requests and corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are
the page aligned in the memory and are not affected by the block I/O
merging algorithm introduced in Linux 5.1. Most modern file systems
use 4k I/O block size by default, thus mitigating this problem.
An upstream patch fixes this bug: commit
c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31 ("block: return the correct
bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
[Test Plan]
stress-ng --sequential 8 --class io -t 5m --times
[Where problems could occur]
Different incorrect pages could be wriiten to disk.
[Other Info]
This patch has already been released in all [FGHI] Azure kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931497/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
Found on B/azure 4.15.0-1120-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != >leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/ With these patches applied, the test can pass without triggering this warning. <<>>
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure (Ubuntu) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-azure package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Invalid Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: Invalid Status in linux-azure source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
autopkgtests completed successfully. * focal/linux - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210719_135442_87652@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210719_135457_6e36a@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/l/lime-forensics/20210719_135407_87652@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210719_135241_6e36a@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210719_135031_6e36a@/log.gz * focal/linux-hwe-5.11 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210719_135154_47661@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210719_135211_df9d6@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/l/lime-forensics/20210719_135326_d1cb7@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210719_135204_d1cb7@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210719_135005_d1cb7@/log.gz ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux (Ubuntu) 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/1935846 Title: Sony Dualshock 4 usb dongle crashes the whole system Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Sony Dualshock 4 controller crashes systems. This is the result of a divide by zero when the driver processes requests from Steam and returns invalid data. More details are in the patch description. [Fix] Check whether data is valid and retry up to 3 times if needed. [Test Case] Tested by the bug reporter of LP:1935846. No more crashes after applying this patch. [Where problems could occur] None. The patch checks whether data is valid and retry 3 times before return -EILSEQ if it still fails. == Original descriptions == The hid-sony driver has custom DS4 connect/disconnect logic for the DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth connected DS4. The connect/disconnect logic works fine generally, however not in conjunction with Steam. Steam implements its own DS4 driver using hidraw. Both hid-sony and Steam are issuing their own HID requests and are racing each other during DS4 dongle connect/disconnect resulting in a kernel crash in hid-sony. The problem is that upon a DS4 connect to the dongle, hid-sony kicks of 'ds4_get_calibration_data' from within its dongle hotplug code. The calibration code issues raw HID feature report for reportID 0x02. When Steam is running, it issues a feature report for reportID 0x12 typically just prior to hid-sony requesting feature reportID 0x02. The result is that 'ds4_get_calibration_data' receives the data Steam requested as that's the HID report returing first. Currently this results in it processing invalid data, which ultimately results in a divide by zero upon a future 'dualshock4_parse_report'. The solution for now is to check within 'ds4_get_calibration_data' to check if we received data for the feature report we issued and if not retry. Please consider to add this patch to Ubuntu LTS kernels. Commit: https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935846/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
autopkgtest completed successfully with dahdi-linux 1:2.11.1~dfsg-1ubuntu6.3. * focal/linux - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210719_133611_b6779@/log.gz * focal/linux-hwe-5.11 - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210719_133526_b778d@/log.gz ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
lime-forensics 1.9-1ubuntu0.3 can be built and loaded on focal with both 5.4 and 5.11 kernels. Waiting for autopkgtests to complete to confirm the verification. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
dahdi-linux 1:2.11.1~dfsg-1ubuntu6.3 can be built and loaded on focal with both 5.4 and 5.11 kernels. Waiting for autopkgtests to complete to confirm the verification. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900951] Re: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B
** Tags added: hinted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900951 Title: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Issue found on B-AWS 4.15.0-1087.92 This is a new test case added a week ago [1]. Test failed with: startup='Wed Oct 21 13:10:37 2020' tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s ptrace10.c:60: TFAIL: The rd0 wasn't set on second PTRACE_POKEUSER HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd14406b78e6 Summary: passed 0 failed 1 skipped 0 warnings 0 tag=ptrace10 stime=1603285837 dur=0 exit=exited stat=1 core=no cu=0 cs=0 [1] https://github.com/linux-test- project/ltp/blob/master/testcases/kernel/syscalls/ptrace/ptrace10.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Tags added: hinted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-5.6 source package in Bionic: New Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900951] Re: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B
Found on xenial/oracle 4.15.0-1077.85~16.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900951 Title: ptrace10 from ubuntu_ltp_syscalls failed on T/X/B Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Issue found on B-AWS 4.15.0-1087.92 This is a new test case added a week ago [1]. Test failed with: startup='Wed Oct 21 13:10:37 2020' tst_test.c:1250: TINFO: Timeout per run is 0h 05m 00s ptrace10.c:60: TFAIL: The rd0 wasn't set on second PTRACE_POKEUSER HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd14406b78e6 Summary: passed 0 failed 1 skipped 0 warnings 0 tag=ptrace10 stime=1603285837 dur=0 exit=exited stat=1 core=no cu=0 cs=0 [1] https://github.com/linux-test- project/ltp/blob/master/testcases/kernel/syscalls/ptrace/ptrace10.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Alex: I gave it a go during Mark's presentation. I am sorry to report it is not solved. Wifi6 is freezing on a regular basis, while non-wife6 connections are just fine. Here's the dmesg appended. Best Regards, Steve On Sun, Jul 18, 2021 at 10:01 AM Steve Barriault wrote: > OK Alex, made it to step 4. > > For step 5, I need to try a Web meeting. I should have a way to attempt > this tomorrow and let you know if it worked or not. > > Best Regards, > > Steve > > On Fri, Jul 16, 2021 at 7:15 AM Alex Tu <1932...@bugs.launchpad.net> > wrote: > >> Hi Steve, >> Looks launchpad does not forward the updated comment through mail. >> I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now: >> >> 3. # to install OEM 5.13 >> # Please manually click on Pre-released updates(focal-proposed) in >> `Software & Updates` UI first. >> $ sudo apt-get install linux-image-oem-20.04c >> >> On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault < >> 1932...@bugs.launchpad.net> >> wrote: >> >> > Hi Alex: >> > >> > I did steps 1 and 2 already. >> > >> > Step 3, I get the following error: could not find >> > >> > (Actual message is in French) >> > >> > Could you check if this has been uploaded to the database? >> > >> > Best Regards, >> > >> > Steve >> > >> > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <1932...@bugs.launchpad.net> >> > wrote: >> > >> > > sorry for confusing, let me break down the steps: >> > > 1. # Add PPA from >> > > >> > >> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2 >> > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging >> > > >> > > 2. # to get linux-firmware from Vicamo's PPA >> > > $ sudo apt-get install linux-firmware >> > > >> > > 3. # to install OEM 5.13 >> > > $ sudo apt-get install linux-image-oem-20.04c >> > > >> > > 4. # reboot, and make sure you are running under oem kernel 5.13 >> > > $ uanme -r >> > > 5.13.0-1007-oem >> > > >> > > 5. # check if the target firmware `-63` loaded >> > > $ dmesg | grep iwlwifi >> > > iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 >> > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm >> > > >> > > 6. # check if the wifi issue can still be reproduced. >> > > - if it is there, please also attach the dmesg here. >> > > >> > > -- >> > > You received this bug notification because you are subscribed to the >> bug >> > > report. >> > > https://bugs.launchpad.net/bugs/1932548 >> > > >> > > Title: >> > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am >> on >> > > wireless [8086:a0f0] >> > > >> > > Status in Linux Firmware: >> > > New >> > > Status in OEM Priority Project: >> > > Confirmed >> > > Status in linux-oem-5.10 package in Ubuntu: >> > > New >> > > >> > > Bug description: >> > > Whenever I am using a wireless connection, the image freezes roughly >> > > every two minutes. Sometimes, email cannot be retrieved / computer >> > > complains the connection was momentarily lost. >> > > >> > > - If I am on a wire, this problem does NOT occur. >> > > - This problems occurs on wireless independent of the platform used >> > > (behavior seen in both Google Hangout and Zoom) >> > > - This problem does NOT occur on Windows. I did a meeting where >> both my >> > > Linux and Windows machines were connected to the same meeting and >> using >> > the >> > > same wifi router, and while the performance on Windows was flawless, >> > > unfortunately it was not so on the Ubuntu box. So I don't think my >> wifi >> > > router or network is to blame. >> > > - As far as I can recall, the problem used not to be there 2 weeks >> ago. >> > > So it may have been introduced by a recent update. >> > > - As communicated before, I am on a certified machine from Dell, >> > > recently purchased with Ubuntu already on board from factory (I assume >> > the >> > > logs there were sent to you would contain the information). >> > > - I tried to generate a log on the wireless, but the process did not >> > let >> > > me do this very easily. I am more than happy to send you additional >> > > information - but please let me know which package you want me to spy >> > upon >> > > exactly, as I am not sure what would be helpful in this matter. >> > > >> > > ProblemType: Bug >> > > DistroRelease: Ubuntu 20.04 >> > > Package: xorg 1:7.7+19ubuntu14 >> > > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 >> > > Uname: Linux 5.10.0-1029-oem x86_64 >> > > ApportVersion: 2.20.11-0ubuntu27.18 >> > > Architecture: amd64 >> > > BootLog: Error: [Errno 13] Permission non accordée: >> '/var/log/boot.log' >> > > CasperMD5CheckResult: skip >> > > CompositorRunning: None >> > > CurrentDesktop: ubuntu:GNOME >> > > Date: Fri Jun 18 09:47:58 2021 >> > > DistUpgraded: Fresh install >> > > DistributionChannelDescriptor: >> > ># This is the distribution channel descriptor for the OEM CDs >> > ># For more information see >> > > http://wiki.ubuntu.com/DistributionChannelDescriptor >> >
[Kernel-packages] [Bug 1936009] Re: The internal mic of Dell Precision 5750 can't record sound
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1936009 Title: The internal mic of Dell Precision 5750 can't record sound Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: In Progress Status in alsa-ucm-conf source package in Impish: In Progress Bug description: [Impact] After upgrade the linux kernel, the mixer names of rt715 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't record sound from internal mic since the internal mic is routed to the codec rt715. [Fix] Backport 3 upstream commits, after applying these 3 commits, the ucm conf file dosn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] run 'alsactl init 1' on the precision 5750 with old and new kernel, there is no error logs, use the internal mic to record sound, it could record successfully. [Where problems will occur] The change only affects the rt715 codec, so far, that codec only connects to the internal mic on Dell soundwire audio machines, so it could introduce regression on the internal mic like users can't record sound via internal mic anymore on the Dell soundwire audio machines. But this possibility is very low since we already tested these 3 commits on different Dell soundwire audio machines (latitude and precision). We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Hello Kleber, thank you very much for your fast reply! I can confirm that Kernel: # cat /proc/version_signature Ubuntu 5.4.0-79.88-generic 5.4.124 fixes my Problem. We can close this bug. Greetings, Lars -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00
[Kernel-packages] [Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Ok - tested all the above an issue occurred on each: Ubuntu on Wayland GNOME on Xorg Ubuntu sudo apt install unity-session sudo apt install xfce4-session sudo apt install cinnamon-session Any next steps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and ubuntu 20.10). When this occurs all other mouse operations still function - left/right click - scroll wheel - mouse position still moves Just the actual mouse pointer not visible. Only way to resolve is to restart the machine. Tried numerous ways to restart the mouse driver but nothing else successful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 14:45:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2021-07-05 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Apple Inc. iMac10,1 ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 initrd=boot\initrd.img-5.8.0-59-generic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268DC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1935728/+subscriptions -- Mailing list: https://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 1936769] Re: [Braswell] HDMI not working properly
Thank you so much for your prompt reply; unfortunately it leaves me no further ahead. To clarify I run my system on solar power - battery/inverter, it's much cleaner than the grid around here, and cheaper. The computer is left turned on all the time but the monitors (2) are turned off to save power. When the monitors are turned back on HDMI does not come up. It used to on older versions of Ubuntu but not now. Hope this makes it a bit clearer. On Mon, Jul 19, 2021 at 1:55 PM Daniel van Vugt <1936...@bugs.launchpad.net> wrote: > Although I don't fully understand the bug description, I do wonder if > there's a Braswell regression given bug 1935901 also. > > ** Summary changed: > > - HDMI not working properly > + [Braswell] HDMI not working properly > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Also affects: xorg-server (Ubuntu) >Importance: Undecided >Status: New > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936769 > > Title: > [Braswell] HDMI not working properly > > Status in linux-hwe-5.8 package in Ubuntu: > New > Status in mutter package in Ubuntu: > New > Status in xorg-server package in Ubuntu: > New > > Bug description: > HP Pavillion desktop 2015 ufei date. Never turned off because boot takes > too long. > Screens (2) turned off system left on when not in use. > Up to Ubuntu 19 and early versions of 20 both screens came back on. > With latest update HDMI does not restart. > If boot from power off both screens, HDMI and VGA are ok. Turn screens > off and HDMI will not display. > > I note that Windows (horrible) has a switch that allows the HDMI to be > controlled but Ubuntu did it automatically but won't now. > > Suspend has always killed the HDMI but there is not much difference in > power consumption between on with suspend and on with screens off. > > Hope you can help, booting from full power off takes too long. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-59-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 19 13:09:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA > controller]) > Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor > x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] > InstallationDate: Installed on 2020-11-05 (255 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: HP 510-a112a > ProcEnviron: >LANGUAGE=en_AU:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_AU.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic > root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/17/2018 > dmi.bios.release: 5.11 > dmi.bios.vendor: AMI > dmi.bios.version: F.33 > dmi.board.asset.tag: CNV7380P8W > dmi.board.name: 821D > dmi.board.vendor: HP > dmi.board.version: 00 > dmi.chassis.asset.tag: CNV7380P8W > dmi.chassis.type: 3 > dmi.chassis.vendor: HP > dmi.modalias: > dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: > dmi.product.family: 103C_53316J G=D > dmi.product.name: 510-a112a > dmi.product.sku: W2S68AA#ABG > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > 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-hwe-5.8/+bug/1936769/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which
[Kernel-packages] [Bug 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Issue also occurred on unity-session and xfce4-session Now testing cinnamon-session (needing to run sudo apt install cinnamon- desktop-environment) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and ubuntu 20.10). When this occurs all other mouse operations still function - left/right click - scroll wheel - mouse position still moves Just the actual mouse pointer not visible. Only way to resolve is to restart the machine. Tried numerous ways to restart the mouse driver but nothing else successful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 14:45:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2021-07-05 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Apple Inc. iMac10,1 ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 initrd=boot\initrd.img-5.8.0-59-generic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268DC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/1935728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936403] Re: A touch pad does not work and does not appear with the command cat /proc/bus/input/devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1936403 Title: A touch pad does not work and does not appear with the command cat /proc/bus/input/devices Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: The surface does not work at all from the moment Ubuntu is installed meir@meir-IdeaPad-5-15IIL05:~$ 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=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 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=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/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=13d3 Product=56ff Version=1917 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-5/3-5:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0003 Vendor=046d Product=4054 Version=0111 N: Name="Logitech Wireless Mouse" P: Phys=usb-:00:14.0-1/input1:2 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.1/0003:046D:C534.0002/0003:046D:4054.0003/input/input16 U: Uniq=4054-00-00-00-00 H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY= 0 0 0 0 B: REL=1943 B: MSC=10 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/input17 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input19 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input20 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp HDMI/DP,pcm=4" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input21 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="sof-hda-dsp HDMI/DP,pcm=5" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input22 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 meir@meir-IdeaPad-5-15IIL05:~$ ubuntu-bug linux - meir@meir-IdeaPad-5-15IIL05:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal - meir@meir-IdeaPad-5-15IIL05:~$ sudo dmidecode -s bios-release-date 11/25/2020 meir@meir-IdeaPad-5-15IIL05:~$ sudo dmidecode -s baseboard-product-name LNVNB161216 meir@meir-IdeaPad-5-15IIL05:~$ sudo dmidecode -s baseboard-manufacturer LENOVO ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
[Kernel-packages] [Bug 1905591] Re: no brightness control in {455, 460} after update from 450
Please list the content of /sys/class/backlight folder.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
Status in OEM Priority Project:
New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-460 package in Ubuntu:
Confirmed
Bug description:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce
GTX 1050 Ti Mobile]:
WORKS FINE:
nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1
NO BRIGHTNESS CONTROL:
nvidia-driver-455: 455.38-0ubuntu0.18.04.1
nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1
nvidia-driver-460: 460.39-0ubuntu0.18.04.1
*WORKAROUND: See comment #11 (add nvidia drivers to initramfs).
*Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but
not for my 18.04.5 Lenovo ThinkPad X1 per comment #5.
Updating to nvidia-driver-455 (or -460) results in loss of brightness
control. On boot, the laptop display brightness is somewhat less than
fully bright and cannot be changed. The brightness up/down keys do
pop up the gnome gui brightness widget, and
/sys/class/backlight/nvidia_0/* values do change, but the actual
display's brightness does not.
Problem occurs with either version of nvidia-driver-455 (the archive
or the ~graphics-drivers/PPA) or any version of -460.
Normal functionality returns if I downgrade to any version of nvidia-
driver-450.
Also observed: 455 and 460 temporarily display some pixel garbage
while mode-switching during the graphic login sequence. Only a minor
glitch, but note that 450 does not exhibit that issue either.
Note also that manually applying this to
/lib/systemd/system/nvidia-persistenced.service has no effect on the problem:
https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic
kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936344] Re: dkms autopkgtest needs to be smarter
That dkms-autopkgtest script carried in backport-iwlwifi-dkms package was a fork from that of dkms package to support modealiases checking. I'm to fix backport-iwlwifi-dkms instead. ** Also affects: backport-iwlwifi-dkms (Ubuntu) Importance: Undecided Status: New ** No longer affects: dkms (Ubuntu) ** Also affects: backport-iwlwifi-dkms (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1936344 Title: dkms autopkgtest needs to be smarter Status in backport-iwlwifi-dkms package in Ubuntu: New Status in backport-iwlwifi-dkms source package in Bionic: New Status in backport-iwlwifi-dkms source package in Focal: New Status in backport-iwlwifi-dkms source package in Hirsute: New Status in backport-iwlwifi-dkms source package in Impish: New Bug description: Over at https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi- dkms/+bug/1932158 you can observe that it was chosen to skip the dkms module for a given kernel, and dkms-autopkgtest did not manage to handle it well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1936344/+subscriptions -- Mailing list: https://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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
OK Alex, made it to step 4. For step 5, I need to try a Web meeting. I should have a way to attempt this tomorrow and let you know if it worked or not. Best Regards, Steve On Fri, Jul 16, 2021 at 7:15 AM Alex Tu <1932...@bugs.launchpad.net> wrote: > Hi Steve, > Looks launchpad does not forward the updated comment through mail. > I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now: > > 3. # to install OEM 5.13 > # Please manually click on Pre-released updates(focal-proposed) in > `Software & Updates` UI first. > $ sudo apt-get install linux-image-oem-20.04c > > On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault < > 1932...@bugs.launchpad.net> > wrote: > > > Hi Alex: > > > > I did steps 1 and 2 already. > > > > Step 3, I get the following error: could not find > > > > (Actual message is in French) > > > > Could you check if this has been uploaded to the database? > > > > Best Regards, > > > > Steve > > > > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <1932...@bugs.launchpad.net> > > wrote: > > > > > sorry for confusing, let me break down the steps: > > > 1. # Add PPA from > > > > > > https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2 > > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging > > > > > > 2. # to get linux-firmware from Vicamo's PPA > > > $ sudo apt-get install linux-firmware > > > > > > 3. # to install OEM 5.13 > > > $ sudo apt-get install linux-image-oem-20.04c > > > > > > 4. # reboot, and make sure you are running under oem kernel 5.13 > > > $ uanme -r > > > 5.13.0-1007-oem > > > > > > 5. # check if the target firmware `-63` loaded > > > $ dmesg | grep iwlwifi > > > iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 > > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm > > > > > > 6. # check if the wifi issue can still be reproduced. > > > - if it is there, please also attach the dmesg here. > > > > > > -- > > > You received this bug notification because you are subscribed to the > bug > > > report. > > > https://bugs.launchpad.net/bugs/1932548 > > > > > > Title: > > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am > on > > > wireless [8086:a0f0] > > > > > > Status in Linux Firmware: > > > New > > > Status in OEM Priority Project: > > > Confirmed > > > Status in linux-oem-5.10 package in Ubuntu: > > > New > > > > > > Bug description: > > > Whenever I am using a wireless connection, the image freezes roughly > > > every two minutes. Sometimes, email cannot be retrieved / computer > > > complains the connection was momentarily lost. > > > > > > - If I am on a wire, this problem does NOT occur. > > > - This problems occurs on wireless independent of the platform used > > > (behavior seen in both Google Hangout and Zoom) > > > - This problem does NOT occur on Windows. I did a meeting where both > my > > > Linux and Windows machines were connected to the same meeting and using > > the > > > same wifi router, and while the performance on Windows was flawless, > > > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > > > router or network is to blame. > > > - As far as I can recall, the problem used not to be there 2 weeks > ago. > > > So it may have been introduced by a recent update. > > > - As communicated before, I am on a certified machine from Dell, > > > recently purchased with Ubuntu already on board from factory (I assume > > the > > > logs there were sent to you would contain the information). > > > - I tried to generate a log on the wireless, but the process did not > > let > > > me do this very easily. I am more than happy to send you additional > > > information - but please let me know which package you want me to spy > > upon > > > exactly, as I am not sure what would be helpful in this matter. > > > > > > ProblemType: Bug > > > DistroRelease: Ubuntu 20.04 > > > Package: xorg 1:7.7+19ubuntu14 > > > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > > > Uname: Linux 5.10.0-1029-oem x86_64 > > > ApportVersion: 2.20.11-0ubuntu27.18 > > > Architecture: amd64 > > > BootLog: Error: [Errno 13] Permission non accordée: > '/var/log/boot.log' > > > CasperMD5CheckResult: skip > > > CompositorRunning: None > > > CurrentDesktop: ubuntu:GNOME > > > Date: Fri Jun 18 09:47:58 2021 > > > DistUpgraded: Fresh install > > > DistributionChannelDescriptor: > > ># This is the distribution channel descriptor for the OEM CDs > > ># For more information see > > > http://wiki.ubuntu.com/DistributionChannelDescriptor > > >canonical-oem-somerville-focal-amd64-20200502-85 > > > DistroCodename: focal > > > DistroVariant: ubuntu > > > EcryptfsInUse: Yes > > > ExtraDebuggingInterest: Yes > > > GraphicsCard: > > >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > > > controller]) > > > Subsystem: Dell Device [1028:0991] > > > InstallationDate: Installed on 2021-04-24 (54 days ago) > > > InstallationMedia:
[Kernel-packages] [Bug 1931044] Re: SynPS/2 Synaptics TouchPad choppy movement after suspend
** Attachment added: "screenshot_181.png" https://bugs.launchpad.net/bugs/1931044/+attachment/5511824/+files/screenshot_181.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/1931044 Title: SynPS/2 Synaptics TouchPad choppy movement after suspend Status in linux package in Ubuntu: New Bug description: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=9[slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=13 [slave keyboard (3)] >> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal >> cat /proc/bus/input/devices ... I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931044/+subscriptions -- Mailing list: https://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 1931044] Re: SynPS/2 Synaptics TouchPad choppy movement after suspend
Hi, it doesn't seem to help: I had an incident, where the choppyness didn't go away even after restart, and also not after adding said option. It improved after suspending the laptop and waking it up again. (my grub config is enclosed in the screenshot, I did update-grub and udpated-grub2) On Mon, Jul 5, 2021 at 6:45 AM Chris Chiu <1931...@bugs.launchpad.net> wrote: > Can you add the "i8042.reset=1" to the kernel boot command line and see > if it helps? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1931044 > > Title: >SynPS/2 Synaptics TouchPad choppy movement after suspend > > Status in linux package in Ubuntu: > New > > Bug description: > Sometimes touchpad input becomes very laggy. > > It seems to be related to suspending the laptop. I think it also has > to do with other mice being plugged in/out. > > Often, suspending and waking up immediately afterwards makes the > pointer fluent again. > > > This is not the only problem I see with this touchpad/driver: > Sometimes the pointer stops moving horizontally as if it got stuck in a > scrolling gesture. > Sometimes the pointer (almost) stops moving completely. Suspending often > but not always helps. > I am not sure whether these problems are related. > > I am happy to debug the problem, but I don't know where to start. > > > >> xinput list > ⎡ Virtual core pointerid=2[master pointer > (3)] > ⎜ ↳ Virtual core XTEST pointer id=4[slave > pointer (2)] > ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave > pointer (2)] > ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave > pointer (2)] > ⎣ Virtual core keyboard id=3[master keyboard > (2)] > ↳ Virtual core XTEST keyboard id=5[slave > keyboard (3)] > ↳ Power Buttonid=6[slave > keyboard (3)] > ↳ Video Bus id=7[slave > keyboard (3)] > ↳ Sleep Buttonid=8[slave > keyboard (3)] > ↳ AT Translated Set 2 keyboardid=9[slave > keyboard (3)] > ↳ ThinkPad Extra Buttons id=12 [slave > keyboard (3)] > ↳ Integrated Camera: Integrated C id=13 [slave > keyboard (3)] > > > >> lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 20.04.2 LTS > Release: 20.04 > Codename: focal > > >> cat /proc/bus/input/devices > ... > I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 > N: Name="SynPS/2 Synaptics TouchPad" > P: Phys=isa0060/serio1/input0 > S: Sysfs=/devices/platform/i8042/serio1/input/input5 > U: Uniq= > H: Handlers=mouse0 event5 > B: PROP=5 > B: EV=b > B: KEY=e520 1 0 0 0 0 > B: ABS=66080001103 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931044/+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/1931044 Title: SynPS/2 Synaptics TouchPad choppy movement after suspend Status in linux package in Ubuntu: New Bug description: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=9[slave keyboard (3)] ↳ ThinkPad Extra Buttons
[Kernel-packages] [Bug 1874309] Re: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned er
Should be fixed in impish #1933248 please drop virtualbox-guest-dkms virtualbox-guest-source ** Changed in: virtualbox-hwe (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1874309 Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Bug description: Steps to reproduce: (In virtualbox) terminal-> sudo apt install virtualbox-guest-utils-hwe virtualbox-guest-dkms-hwe virtualbox-guest-x11-hwe during installation, all kernels and modules are erased, and error screen stating that user will not be able to log in if every kernel is erased is presented. After selecting yes, process is aborted. After that, deleted packages are reinstalled with sudo apt install linux-generic linux-modules-extra-5.4.0-21-generic linux-image-5.4.0-21-generic linux-image-generic linux-modules-extra-5.4.0-25-generic linux-image-5.4.0-25-generic Upon every consequent reboot, error pops up on screen, and asks user to send information. Ubuntu 5.4.0-25.29-generic 5.4.30 Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pixxel 1620 F pulseaudio CasperMD5CheckResult: skip Date: Mon Apr 20 15:04:22 2020 ErrorMessage: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-04-20 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic root=UUID=1e4016f9-5151-41ca-8098-999f643fdf2a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-25-generic 5.4.0-25.29 failed to install/upgrade: installed linux-image-5.4.0-25-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874309/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929194] Re: virtualbox-hwe/6.1.22-dfsg-1ubuntu1.21.10.1 ADT test failure with linux-unstable/5.13.0-3.3
Should be already fixed in impish ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: linux-unstable (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-unstable in Ubuntu. https://bugs.launchpad.net/bugs/1929194 Title: virtualbox-hwe/6.1.22-dfsg-1ubuntu1.21.10.1 ADT test failure with linux-unstable/5.13.0-3.3 Status in linux-unstable package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Bug description: This is a scripted bug report about ADT failures while running virtualbox-hwe tests for linux-unstable/5.13.0-3.3 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/arm64/v/virtualbox-hwe/20210518_211710_937e6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/armhf/v/virtualbox-hwe/20210518_174332_8c208@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/ppc64el/v/virtualbox-hwe/20210518_160609_96694@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish-canonical-kernel-team-unstable/impish/s390x/v/virtualbox-hwe/20210518_144648_96694@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-unstable/+bug/1929194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
Can confirm the workaround does the job, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in linux package in Ubuntu: Confirmed Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv
There is a thread here:
https://lore.kernel.org/linux-riscv/20210520173859.7441aed8@xhacker.debian/T/
Looks like this has landed:
https://github.com/torvalds/linux/commit/8a4102a0cf07cc76a18f373f6b49485258cc6af4#diff-2db30a5588193fbb572fc2b96f3b47ae2e7e83351c5122c368b2b6fa56f38cda
And here is another patch from Alex, another fix to 2bfc6cd
("riscv: Move kernel mapping outside of linear mapping") as well.
https://github.com/torvalds/linux/commit/e5c35fa0401971701dcd7675f471b664698244dd#diff-2db30a5588193fbb572fc2b96f3b47ae2e7e83351c5122c368b2b6fa56f38cda
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1905728
Title:
log_check / tainted_check failed in ubuntu_boot because of warnings
(Found insecure W+X mapping at address) found on F/G/H-riscv
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-riscv package in Ubuntu:
New
Status in linux source package in Groovy:
New
Status in linux-riscv source package in Groovy:
Confirmed
Bug description:
Issue found on 5.8.0-10-generic riscv
Message reported on boot.
[ 13.483103] [ cut here ]
[ 13.483711] riscv/mm: Found insecure W+X mapping at address
(ptrval)/0xffdff800
[ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200
note_page+0x24c/0x252
[ 13.485175] Modules linked in:
[ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic
#12-Ubuntu
[ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp :
ffe1f5bfbb30
[ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 :
ffe00173ed88
[ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 :
ffe1f5bfbb80
[ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 :
0020
[ 13.487633] a2 : ffe1f5bfb870 a3 : a4 :
ffe0016200f8
[ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 :
ffe0006f2806
[ 13.488421] s2 : ffdff8001000 s3 : s4 :
0004
[ 13.488800] s5 : s6 : s7 :
ffe1f5bfbd20
[ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10:
ffdff8002000
[ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 :
0003cec0
[ 13.490119] t5 : t6 : ffe001739462
[ 13.490406] status: 0120 badaddr: cause:
0003
[ 13.490849] ---[ end trace 607c551edff1ef12 ]---
Please find attachment for the boot dmesg log.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905728/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Hello Lars, Thank you for reporting the issue. We have a 20.04 kernel update in focal-proposed (version 5.4.0-79.88) which has the following patch applied which might fix this problem: NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() Could you please try running this kernel version and check whether the bug is really fixed? Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16
[Kernel-packages] [Bug 1936790] [NEW] [SRU][OEM-5.13/U] Fix firmware reload failure of MT7921
Public bug reported: SRU justification: [Impact] MT7921 is supported on 5.13 kernel, mt76 driver failed to work when reboot. SRUed for 5.13+ kernel only. [Fix] MT7921 needs both driver and firmware, firmware is SRUed. When reboot, the firmware is already reloaded, driver probe breaks. Continue to probe if firmware status is OK. [Test] Verified on hardware, After reboot system wifi works fine. [Where problems could occur] The MT7921 wifi may not work. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1928170 sutton ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1928170 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936790 Title: [SRU][OEM-5.13/U] Fix firmware reload failure of MT7921 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Bug description: SRU justification: [Impact] MT7921 is supported on 5.13 kernel, mt76 driver failed to work when reboot. SRUed for 5.13+ kernel only. [Fix] MT7921 needs both driver and firmware, firmware is SRUed. When reboot, the firmware is already reloaded, driver probe breaks. Continue to probe if firmware status is OK. [Test] Verified on hardware, After reboot system wifi works fine. [Where problems could occur] The MT7921 wifi may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv
** Summary changed: - log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on G-riscv + log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905728 Title: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: New Status in linux-riscv source package in Groovy: Confirmed Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934873] Re: ubuntu_aufs_smoke_test fails on Focal cloud v5.11
** Tags added: azure gcp oracle v5.11 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-gcp-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oracle-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oracle-5.11 (Ubuntu) Status: New => In Progress ** Changed in: linux-oracle-5.11 (Ubuntu) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oracle-5.11 (Ubuntu Focal) Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: ubuntu-kernel-tests Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => 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/1934873 Title: ubuntu_aufs_smoke_test fails on Focal cloud v5.11 Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-aws-5.11 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-gcp-5.11 package in Ubuntu: New Status in linux-oracle-5.11 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-aws-5.11 source package in Focal: New Status in linux-azure-5.11 source package in Focal: New Status in linux-gcp-5.11 source package in Focal: New Status in linux-oracle-5.11 source package in Focal: In Progress Bug description: lp:1925407 disabled the test for Hirsute but now we have v5.11 edge kernels on Focal and it fails the same. It's not a regression but test should be hinted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936478] Re: AUFS is missing on Focal v5.11 edge kernels
*** This bug is a duplicate of bug 1934873 *** https://bugs.launchpad.net/bugs/1934873 I added a SRU for this but actually original report lp:1934873 should be enough. ** This bug has been marked a duplicate of bug 1934873 ubuntu_aufs_smoke_test fails on Focal cloud v5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1936478 Title: AUFS is missing on Focal v5.11 edge kernels Status in linux-aws-5.11 package in Ubuntu: New Status in linux-azure-5.11 package in Ubuntu: New Status in linux-gcp-5.11 package in Ubuntu: New Status in linux-oracle-5.11 package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux-aws-5.11 source package in Focal: New Status in linux-azure-5.11 source package in Focal: New Status in linux-gcp-5.11 source package in Focal: New Status in linux-oracle-5.11 source package in Focal: In Progress Bug description: [Impact] * Several Focal v5.11 edge kernels are missing AUFS. * This is a regression against previous Focal kernels (v5.4 and v5.8) because it is expected to support same set of features on v5.11. [Test Plan] * Run ubuntu_aufs_smoke_test autotest. [Where problems could occur] * Mounting AUFS file system could succeed introducing a variety of failures due to bugs in AUFS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.11/+bug/1936478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936678] Re: Samsung Laptop support module doesn't load
Please run "sudo modprobe samsung-laptop force". The "force" parameter will disable DMI check. If you can load samsung-laptop this way, we can try to add your DMI information to this driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936678 Title: Samsung Laptop support module doesn't load Status in linux package in Ubuntu: New Bug description: This is identical to bug # 1170885, which was filed 2013-04-20. The last comment on that bug was by Kai-Heng Feng (kaihengfeng), who requested a new bug report. This is a Samsung laptop NP730QCJ. $ sudo modprobe samsung-laptop modprobe: ERROR: could not insert 'samsung_laptop': No such device About my system: $ sudo dmidecode | grep -A 2 -i 'base board' Base Board Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: NP730QCJ-K01US $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" $ cat /proc/version_signature Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 $ file /sys/firmware/efi/ /sys/firmware/efi/: directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on G-riscv
Found on 5.11.0-1014.14~20.04.1 RISCV
** Tags added: sru-20210621
** Summary changed:
- ubuntu_ftrace_smoke_test timeout on G-riscv
+ ubuntu_ftrace_smoke_test timeout on F/G-riscv
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1909422
Title:
ubuntu_ftrace_smoke_test timeout on F/G-riscv
Status in ubuntu-kernel-tests:
New
Status in linux-riscv package in Ubuntu:
New
Status in linux-riscv source package in Groovy:
New
Bug description:
Issue found on 5.8.0-13.15 RISCV with a KVM instance.
Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START timestamp=1609127175localtime=Dec
28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files
exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of
tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of
tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216
localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
File "/home/ubuntu/autotest/client/parallel.py", line 112, in
fork_waitfor_timed
utils.nuke_pid(pid)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)
AutoservRunError: Could not kill 520
None
03:46:57 INFO | END ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127217
localtime=Dec 28 03:46:57
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1936785] [NEW] Add support for AMD BCL DID
Public bug reported: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1935700 ** Tags added: amd oem-priority originate-from-1935700 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936785 Title: Add support for AMD BCL DID Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] AMD BCL APU shares same code as CZN/RN, but has another DID to be added to kernel. [Fix] Below commit adds the ID. https://lists.freedesktop.org/archives/amd-gfx/2021-July/066502.html [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Upgraded to 20.10 running 5.8.0-1030-kvm and everything is fine again too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 25 80 0d
[Kernel-packages] [Bug 1936673] Re: BUG: kernel NULL pointer dereference, address: 0000000000000000
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1936673 Title: BUG: kernel NULL pointer dereference, address: Status in linux package in Ubuntu: Confirmed Bug description: Hi Kernelguys, after updating my kernel from 5.4.0-74.83-generic to 5.4.0-77.86 I get a kernelpanic when putting load onto my NFSv4.1 mount. About the System: I run a Galera Cluster on a VMWare VM with data stored on a NetApp system with NFSv4.1: # grep nfs4 /proc/mounts server:/GALERANFS_MUC_2_LOG /GALERANFS_MUC_LOG nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_BACKUP /GALERANFS_MUC_BACKUP nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 nfs-server-ip:/GALERANFS_MUC_2_DATA /GALERANFS_MUC_DATA nfs4 rw,noatime,vers=4.1,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=nfs-client-ip,local_lock=none,addr=nfs-server-ip 0 0 The panic I get when I give a little load on the NFS mount with my mariadb-server is: Jul 16 15:26:10 maria2021-muc-2 systemd[1]: Starting MariaDB 10.5.11 database server... Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.549355] BUG: kernel NULL pointer dereference, address: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.551391] #PF: supervisor read access in kernel mode Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.553377] #PF: error_code(0x) - not-present page Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.555350] PGD 0 P4D 0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.557268] Oops: [#7] SMP PTI Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.559186] CPU: 0 PID: 44171 Comm: mysqld Tainted: P DO 5.4.0-77-generic #86-Ubuntu Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.560644] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.562497] RIP: 0010:pnfs_mark_matching_lsegs_return+0x108/0x150 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.563447] Code: 01 f0 80 4b 40 08 49 8b 06 4c 89 f3 4c 39 75 d0 75 9d 8b 45 bc 85 c0 75 3b 48 8b 4d c8 48 8b 41 38 48 8d 51 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 88 e3 ff ff 31 c0 48 83 c4 20 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.565380] RSP: 0018:a6e91c113d68 EFLAGS: 00010283 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.566361] RAX: 95e263669540 RBX: 95e263669268 RCX: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.567364] RDX: 95e263669278 RSI: 95e263669540 RDI: 95e263669240 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.568358] RBP: a6e91c113db0 R08: 0064 R09: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.569356] R10: 95e24b0ed480 R11: 003d R12: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.570355] R13: 95e263669278 R14: 95e263669268 R15: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.571353] FS: 7f5d988cf800() GS:95e277a0() knlGS: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.572340] CS: 0010 DS: ES: CR0: 80050033 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.573317] CR2: CR3: 0002229a2003 CR4: 001606f0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.574289] Call Trace: Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.575260] _pnfs_return_layout+0x118/0x230 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.576272] ? nfs_inode_detach_delegation+0x29/0x70 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.577244] nfs4_evict_inode+0x70/0x80 [nfsv4] Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.578205] evict+0xd2/0x1b0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.579174] iput+0x148/0x210 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.580104] do_unlinkat+0x1c5/0x2d0 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581014] __x64_sys_unlink+0x23/0x30 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.581905] do_syscall_64+0x57/0x190 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.582763] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.583615] RIP: 0033:0x7f5d98b78e3b Jul 16 15:26:10 maria2021-muc-2 kernel: [ 678.584429] Code: f0 ff ff 73 01 c3 48 8b 0d 52 80 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 57 00
