[Kernel-packages] [Bug 1907266] Re: Missing module nfsv4 in linux-kvm
** Changed in: linux-kvm (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1907266 Title: Missing module nfsv4 in linux-kvm Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Focal: Fix Committed Status in linux-kvm source package in Groovy: Fix Committed Status in linux-kvm source package in Hirsute: Fix Committed Bug description: [Impact] The nfsv4 module is not enabled in the linux-kvm kernel. There are customers and users of linux-kvm that want/need to use NFS version 4. [Test Case] $ modinfo nfsv4 modinfo: ERROR: Module nfsv4 not found. [Where problems could occur] It's a new module and loading it could crash a system (if the module is buggy). In addition, the kernel now provides its own DNS resolver for CIFS, NFS and AFS (and potentially others) and those lookups might fail if that particular code is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1907266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911359] Re: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22
Thanks @spacefish! I was currently testing a fix that looks exactly like that, but at this point I'll just apply that patch and upload a new unstable kernel. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911359 Title: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22 Status in linux package in Ubuntu: Confirmed Bug description: I just updated to an unstable kernel build from the kernels team Repo it´s the 5.11-2.3 package (5.11 RC3) The mount of /dev/boot fails with a message: IO charset iso8859-1 not found this is probably due to the kernel being unable to load the nls_iso8859-1 module. I see multiple messages with BPF:No data and for the nls_iso8859-1 module a message: failed to validate module [nls_iso8859_1] BTF: -22 this is probably introduced by this patch: https://lkml.org/lkml/2020/11/6/1143 I don´t undestand what BTF validation is and whether this is an issue with linux 5.11-rc3 or with how the kernel modules are packaged in Ubuntu. My machine is a Renoir (zen2) based Acer Laptop running in UEFI mode, with a fat32 /boot partition and a ext4 / root partition. The root partition gets mounted, but once the /boot should be mounted, this fails with the mentioned error.. Other modules seem to load fine, things like "amdgpu" are already loaded! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910840] Re: [nvidia] Xorg freeze
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Invalid ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Invalid => Opinion ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Opinion => Incomplete ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910840 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After login the screen freezes with mouse pointer duplicating. No operations can be performed .Need to do hard reboot.This started happening after upgrade(5.0.58) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:46:45 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-58-generic, x86_64: installed nvidia, 390.138, 5.4.0-59-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2020-11-02 (68 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Same issue with me. Asus Zenbook 14 UX425E, i7 11th gen 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
When I run kosson's command, I get an error: dpkg: error: cannot access archive 'bcmwl-kernel-source_6.30.223.271 +bdcom-0ubuntu7_amd64.deb': No such file or directory -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] Re: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
As requested by 'Ubuntu Kernel Bot', I am changing the status of this request to 'Confirmed' as both ran the requested command and was unable to run the command (it failed). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] Re: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
Hi Chris / Steve. Thanks you for your quick response. Chris - I had left the install window open and ran 'apport-collect 1911578' within a terminal as requested and authorized it. The window appeared indicating that it was collecting data and then the python job crashed: dpkg-query: no packages found matching linux Traceback ... AttributeError: ConfigParser instance has no attribute 'read_string' I am not sure if any meaningful information was gathered and uploaded. Steve - NVME appears to be a storage device connected directly to the PCI bus (https://www.howtogeek.com/404627/what-are-nvme-drives-and-should-you-buy-one/). This desktop has a standard 1TB drive that is SATA-connected. If it is likely that Ubuntu 16.04 is too old to recognize my new hardware then I can give Ubuntu 18.xx LTS a try. I have 8 other systems running Ubuntu 16.04 and have not had any reason to upgrade to date. 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/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Incomplete Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1911578 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Incomplete Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] Re: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
If your laptop has an nvme drive in it, the kernel in Ubuntu 16.04 may be too old to recognize it. This is not something that will be fixed. There are two newer LTS releases of Ubuntu available if you need support for newer hardware in the installer. Regardless, hardware detection is a kernel function, not a ubiquity function, so reassigning to the correct package. ** Package changed: ubiquity (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: New Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] [NEW] Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
You have been subscribed to a public bug: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 16.04 acer aspire tc-895 ubuntu -- Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 https://bugs.launchpad.net/bugs/1911578 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883840] Re: Double free in DCCP module causing kernel panic
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883840
Title:
Double free in DCCP module causing kernel panic
Status in linux package in Ubuntu:
Fix Released
Bug description:
The problem is when the sock object gets cloned via
dccp_create_openreq_child(),
it gives all its attributes to the child sock object, and no reference counter
is taken for the object dccps_hc_tx_ccid.
If one of the sock objects (the parent or the cahild) is closes or
disconnected,
it frees the target objects dccps_hc_tx_ccid and provides us a dagling
pointer in the other sock object.
This causes an exploitable double free for an object contains function
pointers.
We can free dccps_hc_tx_ccid by calling connect(AF_UNSPEC),then spray the
heap with other allocations,
then call close() we'll potentially have a RIP control.
This chunk of code is the responsible of freeing dccps_hc_tx_ccid, if called
again it will call
ccid_hc_tx_exit() from a freed object
void ccid_hc_tx_delete(struct ccid *ccid, struct sock *sk)
{
if (ccid != NULL) {
if (ccid->ccid_ops->ccid_hc_tx_exit != NULL)
ccid->ccid_ops->ccid_hc_tx_exit(sk); // <-- Calling a function
pointer
kmem_cache_free(ccid->ccid_ops->ccid_hc_tx_slab, ccid);
}
}
disassembly :
(gdb) disas ccid_hc_tx_delete
Dump of assembler code for function ccid_hc_tx_delete:
0x81a7a3a0 <+0>: test rdi,rdi
0x81a7a3a3 <+3>: je 0x81a7a3cd
0x81a7a3a5 <+5>: push rbx
0x81a7a3a6 <+6>: movrbx,rdi
0x81a7a3a9 <+9>: movrdi,rsi
0x81a7a3ac <+12>:movrax,QWORD PTR [rbx]
0x81a7a3af <+15>:movrdx,QWORD PTR [rax+0x80]<—
rax points to a freed object
0x81a7a3b6 <+22>:test rdx,rdx
0x81a7a3b9 <+25>:je 0x81a7a3c0
0x81a7a3bb <+27>:call rdx // <-- arbitrary call
0x81a7a3bd <+29>:movrax,QWORD PTR [rbx]
0x81a7a3c0 <+32>:movrsi,rbx
0x81a7a3c3 <+35>:movrdi,QWORD PTR [rax+0x18]
0x81a7a3c7 <+39>:poprbx
0x81a7a3c8 <+40>:jmp0x811fb980
0x81a7a3cd <+45>:repz ret
End of assembler dump.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883840/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
Worked for me. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- Mailing list: https://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 1835660] Missing required logs.
I want to sincerely thank you for your information. I assume that you are referring to my ubuntu based Linux Mint 20.04 problem. Since yesterday, I have removed and installed Mint 20.1 and find a little error with my initramfs but I have nothing to worry about. I will file this in my archive of Mint/Ubuntu remedies. Thank you for your input. On Wed, Jan 13, 2021, 3:41 PM Ubuntu Kernel Bot <1835...@bugs.launchpad.net> wrote: > This bug is missing log files that will aid in diagnosing the problem. > While running an Ubuntu kernel (not a mainline or third-party kernel) > please enter the following command in a terminal window: > > apport-collect 1835660 > > and then change the status of the bug to 'Confirmed'. > > If, due to the nature of the issue you have encountered, you are unable > to run this command, please add a comment stating that fact and change > the bug status to 'Confirmed'. > > This change has been made by an automated script, maintained by the > Ubuntu Kernel Team. > > ** Changed in: linux (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1870260). > https://bugs.launchpad.net/bugs/1835660 > > Title: > initramfs unpacking failed > > Status in OEM Priority Project: > New > Status in grub2 package in Ubuntu: > Invalid > Status in initramfs-tools package in Ubuntu: > Invalid > Status in linux package in Ubuntu: > Incomplete > > Bug description: > "initramfs unpacking failed: Decoding failed", message appears on > boot up. > > If I "update-initramfs" using gzip instead of lz, then boot up passes > without decoding failed message. > > --- > > However, we currently believe that the decoding error reported in > dmesg is actually harmless and has no impact on usability on the > system. > > Switching from lz4 to gzip compression, simply papers over the > warning, without any benefits, and slows down boot. > > Kernel should be fixed to correctly parse lz4 compressed initrds, or > at least lower the warning, to not be user visible as an error. > > [Impact] > >* Decoding failure messages in dmsg with a single lz4 initrd > >* Multiple lz4 compressed initrds cannot be decompressed by kernel, > when loaded by grub > >* Multiple lz4 compressed initrds cannot be decompressed by kernel, > when there is padding between them > > [Test Case] > >* Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 > >* Create an lz4 compressed initrd with a single test-file in it with > some content. I.e. echo "second-initrd" > test-file, and then pack > that with cpio hewc owned by root & lz4 -l. > >* Create a combined padded initrd of stock initrd, pad4, and the > test-marker initrd created above. > >* Boot above with "break=top" kernel command line. > >* With broken kernels, there should be dmesg error message that > decoding failed, and one will observe that /test-file does not exist > in the shell. > >* With fixed kernel, /test-file in the initrd shell should exist, and > should have the expected content "second-initrd". > >* The alignment and padding in the above test case depends on the > size of the first initrd => if a given padded initrd does not > reproduce the problem, try varying the size of the first initrd or > that of the padding between 0..4. > > > [Where problems could occur] > >* This changes compatible lz4 decompressor in the kernel, which can > also be used by other kernel modules such as cryptography, squashfs, > zram, f2fs, comprssed kernel image, pstore. For example, previously > rejected files with "bogus" length and extra padding may now be > accepted, whereas they were previously getting rejected by the > decompressor. > >* Ideally kernel should switch to the stable lz4 format which has > better specification of end of stream. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1835660/+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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Good data point, thanks. It looks like there are some significant differences between the 9550 and the 9560 that could explain that: 1) Next generation CPU: i7-6700HQ on the 9550 vs i7-7700HQ on the 9560 2) Intel HD graphics 530 on the 9550 vs 630 on the 9560 3) NVIDIA GTX 960M on the 9550 vs NVIDIA GTX 1050 on the 9560 Reference: https://www.windowscentral.com/dell-xps-15-9550-vs- xps-15-9560-whats-different-and-should-you-upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
Marco's workaround in #7 works for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
Happens to me in up to date GG using amdgpu for xorg session with fractional scaling. The mouse pointer in gdm gets stuck at the beginning of the session. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Thank you very mach. You are my HERO ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Fix Released Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911476] [NEW] Groovy update: upstream stable patchset 2021-01-13
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-01-13 Ported from the following upstream stable releases: v5.4.84, v5.9.15, v5.4.85, v5.9.16 from git://git.kernel.org/ Kbuild: do not emit debug info for assembly with LLVM_IAS=1 mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING kprobes: Remove NMI context check kprobes: Tell lockdep about kprobe nesting ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks tools/bootconfig: Fix to check the write failure correctly net, xsk: Avoid taking multiple skbuff references bpftool: Fix error return value in build_btf_type_table vhost-vdpa: fix page pinning leakage in error path (rework) powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation batman-adv: Consider fragmentation for needed_headroom batman-adv: Reserve needed_*room for fragments batman-adv: Don't always reallocate the fragmentation skb head ipvs: fix possible memory leak in ip_vs_control_net_init ibmvnic: handle inconsistent login with reset ibmvnic: stop free_all_rwi on failed reset ibmvnic: avoid memset null scrq msgs ibmvnic: delay next reset if hard reset fails ibmvnic: track pending login ibmvnic: send_login should check for crq errors ibmvnic: reduce wait for completion time drm/rockchip: Avoid uninitialized use of endpoint id in LVDS drm/panel: sony-acx565akm: Fix race condition in probe can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous clk_disable_unprepare() can: sja1000: sja1000_err(): don't count arbitration lose as an error can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error can: c_can: c_can_power_up(): fix error handling can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling samples/ftrace: Mark my_tramp[12]? global scsi: storvsc: Fix error return in storvsc_probe() net: broadcom CNIC: requires MMU iwlwifi: pcie: invert values of NO_160 device config entries perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS zlib: export S390 symbols for zlib modules phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211 arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go Advance iwlwifi: pcie: limit memory read spin time arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards. arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc. iwlwifi: sta: set max HE max A-MPDU according to HE capa iwlwifi: pcie: set LTR to avoid completion timeout iwlwifi: mvm: fix kernel panic in case of assert during CSA powerpc: Drop -me200 addition to build flags arm64: dts: broadcom: clear the warnings caused by empty dma-ranges ARC: stack unwinding: don't assume non-current task is sleeping scsi: ufs: Fix unexpected values from ufshcd_read_desc_param() scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes interconnect: qcom: qcs404: Remove GPU and display RPM IDs ibmvnic: skip tx timeout reset while in resetting irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend drm/exynos: depend on COMMON_CLK to fix compile tests spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts arm-smmu-qcom: Ensure the qcom_scm driver has finished probing btrfs: do nofs allocations when adding and removing qgroup relations btrfs: fix lockdep splat when enabling and disabling qgroups soc: fsl: dpio: Get the cpumask through cpumask_of(cpu) intel_idle: Fix intel_idle() vs tracing arm64: tegra: Disable the ACONNECT for Jetson TX2 platform/x86: thinkpad_acpi: add P1 gen3 second fan support platform/x86: thinkpad_acpi: Do not report SW_TABLET_MODE on Yoga 11e platform/x86: thinkpad_acpi: Add BAT1 is primary battery quirk for Thinkpad Yoga 11e 4th gen platform/x86: thinkpad_acpi: Whitelist P15 firmware for dual fan control platform/x86: acer-wmi: add automatic keyboard background light toggle key as KEY_LIGHTS_TOGGLE platform/x86: intel-vbtn: Support for tablet mode on HP Pavilion 13 x360 PC platform/x86: touchscreen_dmi: Add info for the Predia Basic tablet platform/x86: touchscreen_dmi: Add info for the Irbis TW118 tablet can: m_can: m_can_dev_setup(): add support for bosch mcan version 3.3.0 s390: fix irq state tracing intel_idle: Build fix media: pulse8-cec: fix duplicate free at disconnect or probe error media: pulse8-cec: add support for FW v10 and up mmc: mediatek: Extend recheck_sdio_irq fix to more variants
[Kernel-packages] [Bug 1911204] Re: i dont know what is error , but i ubuntu-bug linux did this and found bug
sorry for bothering you , but this is fixed after upgrade ubuntu 18.04 into 20.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911204 Title: i dont know what is error , but i ubuntu-bug linux did this and found bug Status in linux package in Ubuntu: Incomplete Bug description: please help me!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-130-generic 4.15.0-130.134 ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18 Uname: Linux 4.15.0-130-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: savan 4355 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 19:21:45 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=8dbf6066-6d7b-4bce-9ec6-89ada4a8303b InstallationDate: Installed on 2021-01-11 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic root=UUID=d4896985-94f8-4b04-a057-8a1e74d2b55e ro acpi_rev_override locale=en_IN alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-130-generic N/A linux-backports-modules-4.15.0-130-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2021-01-11 (0 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 06XGVW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1835660 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901885] Re: [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot
now it works with linux-image-5.8.0-38-generic ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901885 Title: [ASRock H270M-ITX/ac] Line output device unavailable on KDE after reboot Status in linux package in Ubuntu: Incomplete Bug description: This is happening since I upgraded from kubuntu 20.04 to 20.10 Every time I reboot, I cannot find the default "line out" output in the list of available sound output in kmixer, it has disappeared. The only workaround is to retrieve it is launching the following script : #!/bin/bash killall pulseaudio pulseaudio -k rm -r ~/.config/pulse/* rm -r ~/.pulse* sleep 15 pulseaudio --start ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 13:57:02 2020 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy package-from-proposed Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-02 (514 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:13.99.2-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Tags: groovy package-from-proposed Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (4 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: H270M-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd03/16/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH270M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications
[Kernel-packages] [Bug 1909782] Re: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2, 1
This bugreport can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909782 Title: kernel linux-image-5.8.0-33-generic crashes on boot with low memory corruption, Apple MacBookPro 2,1 Status in linux package in Ubuntu: Confirmed Bug description: booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-31-generic works properly. booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel 5.8.0-33-generic crashes with error indicating low memory corruption. Release: 20.10 Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: src/main.c:parse_controller_config() Key file does not have group “Controller” Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times: [ src/main.c:parse_controller_config() Key file does not have group “Controller”] Dec 20 09:08:36 ken-macbookpro21 dbus-daemon[464]: dbus[464]: Unknown group "power" in message bus configuration file Dec 20 09:08:36 ken-macbookpro21 systemd[1]: Started CUPS Scheduler. Dec 20 09:08:37 ken-macbookpro21 systemd[1]: systemd-rfkill.service: Succeeded. Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400078] check: Corrupted low memory at 4f63a8a7 (1258 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400108] check: Corrupted low memory at 9e8bc546 (c248 phys) = 8200 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400118] [ cut here ] Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400120] Memory corruption detected in low memory Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400138] WARNING: CPU: 1 PID: 177 at arch/x86/kernel/check.c:161 check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400139] Modules linked in: btusb btrtl btbcm btintel bluetooth ecdh_generic ecc joydev snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg radeon snd_hda_codec snd_hda_core ttm snd_hwdep drm_kms_helper snd_pcm snd_seq_midi cec ath9k rc_core appletouch snd_seq_midi_event ath9k_common applesmc ath9k_hw snd_rawmidi input_leds ath i2c_algo_bit snd_seq mac80211 fb_sys_fops coretemp apple_mfi_fastcharge syscopyarea kvm_intel snd_seq_device sysfillrect snd_timer cfg80211 sysimgblt snd kvm soundcore acpi_als kfifo_buf libarc4 industrialio sbs sbshc mac_hid apple_bl binfmt_misc sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_appleir hid_apple hid_generic usbhid hid firewire_ohci firewire_core i2c_i801 i2c_smbus lpc_ich pata_acpi crc_itu_t sky2 video Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400223] CPU: 1 PID: 177 Comm: kworker/1:3 Not tainted 5.8.0-33-generic #36-Ubuntu Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400226] Hardware name: Apple Computer, Inc. MacBookPro2,1/Mac-F42189C8, BIOS MBP21.88Z.00A5.B08.0802291403 02/29/08 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400232] Workqueue: events check_corruption Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400238] RIP: 0010:check_for_bios_corruption+0xb1/0xc0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400243] Code: 85 f6 75 0a 5b 41 5c 41 5d 41 5e 5d c3 c3 80 3d dc 3a bb 01 00 75 ed 48 c7 c7 f0 90 d9 98 c6 05 cc 3a bb 01 01 e8 94 7b 02 00 <0f> 0b eb d6 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 15 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400246] RSP: 0018:b489c0207e48 EFLAGS: 00010286 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400250] RAX: RBX: 0001 RCX: 97047bd18cd8 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400253] RDX: ffd8 RSI: 0027 RDI: 97047bd18cd0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400256] RBP: b489c0207e68 R08: 0001 R09: 03ac Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400258] R10: 999b69a8 R11: b489c0207c90 R12: 9703c001 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400261] R13: 9703c001 R14: 8000 R15: 970479bcd900 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400265] FS: () GS:97047bd0() knlGS: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400268] CS: 0010 DS: ES: CR0: 80050033 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400271] CR2: 7f86e4b62748 CR3: b011e000 CR4: 06e0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400274] Call Trace: Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400284] check_corruption+0xe/0x3a Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400291] process_one_work+0x1e8/0x3b0 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400295] worker_thread+0x50/0x370 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400300] kthread+0x12f/0x150 Dec 20 09:08:40 ken-macbookpro21 kernel: [ 62.400305]
[Kernel-packages] [Bug 1910920] Re: no soundcard present with linux-image-5.8.0-37-generic
The fix identified by https://askubuntu.com/a/1307216/1168625 works (tested on two workstations). Quoting: The snd-intel-dspcfg module ... had been moved to the linux- modules-extra- package. So I had to install that package, since it hasn't been installed by default since 5.4.0-60.67 sudo apt install linux-modules-extra-5.8.0-36-generic (or use pkcon) I believe there are some duplicates to this issue that have popped up since the release of 5.8.0-37-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910920 Title: no soundcard present with linux-image-5.8.0-37-generic Status in linux package in Ubuntu: Confirmed Bug description: With linux-image-5.8.0-34-generic, all on-board soundcards work flawlessly. After update of kernel to linux-image-5.8.0-37-generic durign this week no soundcards are detected. I am happy to provide more information. But I will not sent automatic apport reports because it includes private local data. !!DMI Information !!--- Manufacturer: LENOVO Product Name: 20BUS23M00 Product Version: ThinkPad T450 Firmware Version: JBET54WW (1.19 ) Board Vendor: LENOVO Board Name:20BUS23M00 !!Kernel Information !!-- Kernel release:5.8.0-34-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.8.0-34-generic Library version:1.2.3.2 Utilities version: 1.2.3 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xe123 irq 51 1 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe1234000 irq 52 !!PCI Soundcards installed in the system !!-- 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) Subsystem: Lenovo Broadwell-U Audio Controller [17aa:5034] 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) Subsystem: Lenovo Wildcat Point-LP High Definition Audio Controller [17aa:5034] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911240] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returne
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1911240 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post- installation script subprocess returned error exit status 10 Status in bcmwl package in Ubuntu: Confirmed Bug description: dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 12 13:53:08 2021 ErrorMessage: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-01-12 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1911240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906384] Re: [UBUNTU 18.04] lvm boot failure
** Changed in: ubuntu-z-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906384 Title: [UBUNTU 18.04] lvm boot failure Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: ---Problem Description--- boot failure with LVM root disk ---uname output--- 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = 8561 LT1 ---System Hang--- Boot failure with LVM root disk and enter emergency shell ---Debugger--- A debugger is not configured ---Steps to Reproduce--- boot the system *Additional Instructions for Chee Ye/y...@cn.ibm.com: -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version During boot, got below error message and then entered emergency shell. I am attaching part of the console log from HMC. "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV UbKGJN-sLdU-PeZu-p2hF-ca1W-Gd74-WUISRc prefers device /dev/sdah be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV 3wBaLS-TaW1-IJAI-Akmo-k90H-uT6G-j7XEX3 prefers device /dev/sdh5 be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "WARNING: PV Ksjsai-Hw03-r9x9-n2Kv-4tqe-GyP9-qVWc2c prefers device /dev/sdcn be" "cause device was seen first." "Cannot activate LVs in VG ISVCL1-vg while PVs appear on duplicate devices." done. "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: error opening /dev/md?*: No such file or directory" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" "mdadm: No arrays found in config file or automatically" done. "Gave up waiting for root file system device. Common problems:" "- Boot args (cat /proc/cmdline)" "- Check rootdelay= (did the system wait long enough?)" "- Missing modules (cat /proc/modules; ls /dev)" "chvt: can't open console" "ALERT! /dev/mapper/ISVCL1--vg-root does not exist. Dropping to a shell!" "Couldn't get a file descriptor referring to the console" "/scripts/panic/console_setup: line 133: can't create /dev/tty1: No such device o" "r address" "/scripts/panic/console_setup: line 1: can't open /dev/tty1: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty2: No such device or" address "/scripts/panic/console_setup: line 1: can't open /dev/tty2: No such device or ad" dress "/scripts/panic/console_setup: line 1: can't create /dev/tty3: No such device or" address
[Kernel-packages] [Bug 1911449] Re: Calibre fails on ubuntu 20.04
** Package changed: linux (Ubuntu) => calibre (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/1911449 Title: Calibre fails on ubuntu 20.04 Status in calibre package in Ubuntu: Confirmed Bug description: Hi, On the repository server of Ubuntu / Xubuntu 20.04, the version of "Calibre" (to read ebooks) proposed is 4.99.4 but it doesn't launch. On Calibre website (https://calibre-ebook.com/download_linux), it's written : The latest release of calibre is 5.9.0. Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below. Could a more recent version of Calibre, which should work better, be proposed on the repository server ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1911449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910588] Re: rsync backup hang
Hi Jack. I discussed this with other kernel engineers this morning and we also felt this was looking more like a FW or hardware issue. I am anxious to hear your results. Thanks for the detailed response. Terry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910588 Title: rsync backup hang Status in linux package in Ubuntu: Confirmed Bug description: I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs requiring machine reset; no response from mouse or keyboard. No response to ping from a windows machine. All drive activity stops. The hang occurs with the backup drive connected via sata and via usb3 (adapter) The source directories are ext4 (boot drive ssd) and zfs (raidz1 four x 4TB drives). The destination is a single 3TB drive formatted with zfs (drive is about 20% full). The hang occurred about 6 times before I decided to go back to kernel 5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel -33 (sata and usb3 connect). The install is 20.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jcw06245100 F pulseaudio /dev/snd/pcmC0D0p: jcw06245100 F...m pulseaudio /dev/snd/controlC1: jcw06245100 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 12:07:11 2021 InstallationDate: Installed on 2020-10-03 (96 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic N/A linux-firmware1.190.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago) dmi.bios.date: 10/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911449] Re: Calibre fails on ubuntu 20.04
Here is for sudo lspci -vnvn > lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: Toshiba Corporation 3rd Gen Core processor DRAM Controller [1179:0001] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ivb_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 3rd Gen Core processor Graphics Controller [1179:0003] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <16us ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x1 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range BC, TimeoutDis+, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd- AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee04004 Data: 4021 Capabilities: [90] Subsystem: Toshiba Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 [1179:0001] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes
[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation
Affected series adjusted accordingly. ** Changed in: linux (Ubuntu Focal) Status: Invalid => In Progress ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Fix Committed ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910561 Title: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 Mobile Workstation when muting corresponding audio devices. * The right channel of internal speaker has not sound. [Fix] Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling LEDs and initialing AMP. [Test] Built a test kernel with applying this patch, the mute/micmute LEDs are work as expected. The internal speaker could play the sounds from left and right channels. [Where problems could occur] This quirk is specific for these two platforms. It should not cause the regression to other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1910561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911204] Re: i dont know what is error , but i ubuntu-bug linux did this and found bug
Marked as Incomplete for Alex's question. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911204 Title: i dont know what is error , but i ubuntu-bug linux did this and found bug Status in linux package in Ubuntu: Incomplete Bug description: please help me!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-130-generic 4.15.0-130.134 ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18 Uname: Linux 4.15.0-130-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: savan 4355 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 19:21:45 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=8dbf6066-6d7b-4bce-9ec6-89ada4a8303b InstallationDate: Installed on 2021-01-11 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic root=UUID=d4896985-94f8-4b04-a057-8a1e74d2b55e ro acpi_rev_override locale=en_IN alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-130-generic N/A linux-backports-modules-4.15.0-130-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2021-01-11 (0 days ago) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 06XGVW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn06XGVW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911449] Re: Calibre fails on ubuntu 20.04
Ubuntu 5.4.0-56.62-generic 5.4.73 sudo lspci -vnvn > lspci-vnvn.log returns nothing ** 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/1911449 Title: Calibre fails on ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, On the repository server of Ubuntu / Xubuntu 20.04, the version of "Calibre" (to read ebooks) proposed is 4.99.4 but it doesn't launch. On Calibre website (https://calibre-ebook.com/download_linux), it's written : The latest release of calibre is 5.9.0. Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below. Could a more recent version of Calibre, which should work better, be proposed on the repository server ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911449] [NEW] Calibre fails on ubuntu 20.04
Public bug reported: Hi, On the repository server of Ubuntu / Xubuntu 20.04, the version of "Calibre" (to read ebooks) proposed is 4.99.4 but it doesn't launch. On Calibre website (https://calibre-ebook.com/download_linux), it's written : The latest release of calibre is 5.9.0. Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below. Could a more recent version of Calibre, which should work better, be proposed on the repository server ? ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911449 Title: Calibre fails on ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, On the repository server of Ubuntu / Xubuntu 20.04, the version of "Calibre" (to read ebooks) proposed is 4.99.4 but it doesn't launch. On Calibre website (https://calibre-ebook.com/download_linux), it's written : The latest release of calibre is 5.9.0. Please do not use your distribution provided calibre package, as those are often buggy/outdated. Instead use the Binary install described below. Could a more recent version of Calibre, which should work better, be proposed on the repository server ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908569] Re: video: hyperv_fb: Fix the cache type when mapping the VRAM
** Description changed:
We identified a problem that is causing slow logging to the console for
customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
+
+ (marcelo.cerri: it's actually commit id
+ 5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
-
Microsoft would like to request this patch in all supported releases.
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Groovy)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-4.15 (Ubuntu)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
--
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/1908569
Title:
video: hyperv_fb: Fix the cache type when mapping the VRAM
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
New
Status in linux-azure source package in Focal:
New
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Groovy:
New
Status in linux-azure-4.15 source package in Groovy:
Invalid
Bug description:
We identified a problem that is causing slow logging to the console
for customers.
The following commit resolves this issue as well as other cache relates
issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
(marcelo.cerri: it's actually commit id
5f1251a48c17b54939d7477305e39679a565382c in the mainline kernel)
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908569/+subscriptions
--
[Kernel-packages] [Bug 1881109] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-13 09:51 EDT--- IBM Bugzilla -> closed, 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/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866] ([<01d3cbce944a>] __vcpu_run+0x27a/0xc30) [20832.901870] [<01d3cbcf29a8>] kvm_arch_vcpu_ioctl_run+0x2d8/0x840 [20832.901875] [<01d3cbcdd242>] kvm_vcpu_ioctl+0x282/0x770 [20832.901880] [<01d3cbf85f66>] do_vfs_ioctl+0x376/0x690 [20832.901881] [<01d3cbf86304>] ksys_ioctl+0x84/0xb0 [20832.901883] [<01d3cbf8639a>] __s390x_sys_ioctl+0x2a/0x40 [20832.901885] [<01d3cc57d5f2>] system_call+0x2a6/0x2c8 [20832.901885] Last
[Kernel-packages] [Bug 1911369] Re: [radeon] Horizontal lines of screen corruption after last update.
tried an older kernel. No change. 5.4.0-42-generic ** Attachment added: "screen_corruption.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911369/+attachment/5452713/+files/screen_corruption.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/1911369 Title: [radeon] Horizontal lines of screen corruption after last update. Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: A clean install is fine if I don't take updates. If I do take the updates and reboot then I get heavy video corruption. This just started today. This is a dual boot system. The windows system has no issues. Appears to be software and not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 12 21:18:27 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 7950 Boost] [1002:3000] InstallationDate: Installed on 2021-01-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.release: 3.96 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.96 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: D8N02UC#ABA dmi.sys.vendor: Hewlett-Packard 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.1~20.04.1 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/1911369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
** Changed in: iproute2 (Ubuntu) Assignee: Kernel Packages (kernel-packages) => (unassigned) ** Changed in: libbpf (Ubuntu) Assignee: Kernel Packages (kernel-packages) => Christian Ehrhardt (paelzer) ** Changed in: iproute2 (Ubuntu) Status: New => Invalid ** Changed in: libbpf (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: Invalid Status in libbpf package in Ubuntu: New Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] Since the code is taken out of the Linux kernel, this should be treated similar to the kernel for security. Research uncovered no records about security issues. [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel source and claims static analysis via LGTM and Coverty. Also has CI via Travis (https://travis-ci.com/github/libbpf/libbpf). Right now there are no dep-8 tests. Though potentially it should be possible to create those, would this really add additional benefit beyond having upstream CI? A test build on hirsute was showing no warnings beyond lintian complaining about things which would be changed if we had delta (unstable as series for example). Otherwise was clean. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] As this is only taking out code from the kernel into a separate library package, the maintenance effort should be minimal. Packaging is done in Debian and is synced into Ubuntu (no delta). [Background information] A discourse about why this is packaged outside the kernel can be found at https://lwn.net/Articles/836911/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
Hello, Sorry for stupid question (I'm new in linux) but how can I change kernel parameter? My google search have no success... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it Status in linux package in Ubuntu: Confirmed Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
** Description changed: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] + Since the code is taken out of the Linux kernel, this should be treated similar to the kernel for security. Research uncovered no records about security issues. [Quality assurance] - At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. + At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel source and claims static analysis via LGTM and Coverty. Also has CI via Travis (https://travis-ci.com/github/libbpf/libbpf). + Right now there are no dep-8 tests. Though potentially it should be possible to create those, would this really add additional benefit beyond having upstream CI? + A test build on hirsute was showing no warnings beyond lintian complaining about things which would be changed if we had delta (unstable as series for example). Otherwise was clean. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] + As this is only taking out code from the kernel into a separate library package, the maintenance effort should be minimal. Packaging is done in Debian and is synced into Ubuntu (no delta). [Background information] + A discourse about why this is packaged outside the kernel can be found at https://lwn.net/Articles/836911/. -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: Invalid Status in libbpf package in Ubuntu: New Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] Since the code is taken out of the Linux kernel, this should be treated similar to the kernel for security. Research uncovered no records about security issues. [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel source and claims static analysis via LGTM and Coverty. Also has CI via Travis (https://travis-ci.com/github/libbpf/libbpf). Right now there are no dep-8 tests. Though potentially it should be possible to create those, would this really add additional benefit beyond having upstream CI? A test build on hirsute was showing no warnings beyond lintian complaining about things which would be changed if we had delta (unstable as series for example). Otherwise was clean. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] As this is only taking out code from the kernel into a separate library package, the maintenance effort should be minimal. Packaging is done in Debian and is synced into Ubuntu (no delta). [Background information] A discourse about why this is packaged outside the kernel can be found at https://lwn.net/Articles/836911/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911438] [NEW] CIFS: Request for backport
Public bug reported: CIFS team requested below patch to be backported (it was marked for stable last month) to Ubuntu 18.04. Patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs/transport.c?id=6988a619f5b79e4efadea6e19dcfe75fbcd350b5 "cifs: allow syscalls to be restarted in __smb_send_rqst()" Since 6988a619f5b79e4efadea6e19dcfe75fbcd350b5 hasn't been picked up for 5.4.0-1031-azure (the current 18.04 kernel version for Azure image), I would like make a request for backport. Please let me know, if you have any questions. ** Affects: linux-azure (Ubuntu) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: linux-azure (Ubuntu Groovy) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Also affects: linux-azure (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Groovy) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1911438 Title: CIFS: Request for backport Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Groovy: New Bug description: CIFS team requested below patch to be backported (it was marked for stable last month) to Ubuntu 18.04. Patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/cifs/transport.c?id=6988a619f5b79e4efadea6e19dcfe75fbcd350b5 "cifs: allow syscalls to be restarted in __smb_send_rqst()" Since 6988a619f5b79e4efadea6e19dcfe75fbcd350b5 hasn't been picked up for 5.4.0-1031-azure (the current 18.04 kernel version for Azure image), I would like make a request for backport. Please let me know, if you have any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1911438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1906370] Re: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option
It's tagged with Ubuntu-5.10.0-12.13 in hirsute master-next, hence will come once 5.10 has landed in hirsute. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906370 Title: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: OSN devices' final shipment was as part of the IBM z13 release. The primary exploiter was the IBM Communication Controller, which was pulled out of marketing in March 2015 and should be out of service now. Therefore, we pull the support from all Linux distros going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908219] Re: [drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors config:
I have tested this in a VM with kernel 4.15.0-131.135 installed and I
can confirm the issue is gone.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908219
Title:
[drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing
monitors config:
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Ubuntu 18.04 used as a guest in KVM with Spice/QXL in use may lead to a DRM
error displayed during xorg launch:
[drm:qxl_enc_commit [qxl]] *ERROR* head number too large or missing monitors
config: (ptrval), 0
[Fix]
* 00e5d217fa19bcbec13135898e1b9ca2c1c3e89b qxl: hook monitors_config
updates into crtc, not encoder.
[Test Case]
* Ubuntu 18.04 desktop guest with 4.15-series kernel with Spice/QXL.
* I used Ubuntu 20.04 as the host, but I was reported that the issue is
similar also on Centos 7.8 used as a host.
[Regression Potential]
* Fix is limited to the QXL driver, so any regressions will be related
to graphics (either potential drm errors or graphical artifacts).
[Other]
* This has been fixed in HWE kernels and in later Ubuntu releases. Only
Bionic is affected.
* According to the description in drivers/gpu/drm/qxl/qxl_dev.h:
struct qxl_monitors_config {
(...)
uint16_t max_allowed; /* If it is 0 no fixed limit is given by the
driver */
(...)
};
In the message this value is 0 which should be a completely correct situation
in that context. However, it is incorrectly compared against current qxl_output.
This has been fixed soon after Bionic release and in Bionic is marked with:
/* TODO: ugly, do better */
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911433] Re: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1911433 Title: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 Status in wireless-regdb package in Ubuntu: New Bug description: I was trying to update ubuntu, but this bug showed up. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: wireless-regdb 2018.05.09-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 13 18:39:07 2021 Dependencies: DuplicateSignature: package:wireless-regdb:2018.05.09-0ubuntu1 Unpacking wireless-regdb (2020.11.20-0ubuntu1~16.04.2) over (2018.05.09-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-JSsjie/57-wireless-regdb_2020.11.20-0ubuntu1~16.04.2_all.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 InstallationDate: Installed on 2020-11-02 (72 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: wireless-regdb Title: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1911433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911433] [NEW] package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda
Public bug reported: I was trying to update ubuntu, but this bug showed up. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: wireless-regdb 2018.05.09-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 13 18:39:07 2021 Dependencies: DuplicateSignature: package:wireless-regdb:2018.05.09-0ubuntu1 Unpacking wireless-regdb (2020.11.20-0ubuntu1~16.04.2) over (2018.05.09-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-JSsjie/57-wireless-regdb_2020.11.20-0ubuntu1~16.04.2_all.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 InstallationDate: Installed on 2020-11-02 (72 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: wireless-regdb Title: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1911433 Title: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 Status in wireless-regdb package in Ubuntu: New Bug description: I was trying to update ubuntu, but this bug showed up. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: wireless-regdb 2018.05.09-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 13 18:39:07 2021 Dependencies: DuplicateSignature: package:wireless-regdb:2018.05.09-0ubuntu1 Unpacking wireless-regdb (2020.11.20-0ubuntu1~16.04.2) over (2018.05.09-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-JSsjie/57-wireless-regdb_2020.11.20-0ubuntu1~16.04.2_all.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 InstallationDate: Installed on 2020-11-02 (72 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: wireless-regdb Title: package wireless-regdb 2018.05.09-0ubuntu1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package crda 3.18-1build1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1911433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911359] Re: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22
Can´t pull the log, as i am unable to boot. Probably fixed by: https://patchwork.kernel.org/project/netdevbpf/patch/20210110070341.1380086-1-and...@kernel.org/ (not yet merged by torvalds) The issue happens if a kernel module has an empty BTF ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911359 Title: Boot fails: failed to validate module [nls_iso8859_1] BTF: -22 Status in linux package in Ubuntu: Confirmed Bug description: I just updated to an unstable kernel build from the kernels team Repo it´s the 5.11-2.3 package (5.11 RC3) The mount of /dev/boot fails with a message: IO charset iso8859-1 not found this is probably due to the kernel being unable to load the nls_iso8859-1 module. I see multiple messages with BPF:No data and for the nls_iso8859-1 module a message: failed to validate module [nls_iso8859_1] BTF: -22 this is probably introduced by this patch: https://lkml.org/lkml/2020/11/6/1143 I don´t undestand what BTF validation is and whether this is an issue with linux 5.11-rc3 or with how the kernel modules are packaged in Ubuntu. My machine is a Renoir (zen2) based Acer Laptop running in UEFI mode, with a fat32 /boot partition and a ext4 / root partition. The root partition gets mounted, but once the /boot should be mounted, this fails with the mentioned error.. Other modules seem to load fine, things like "amdgpu" are already loaded! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
@kaihengfeng Same problem with mainline kernel 5.11.0-051100rc3 (build binaries verified). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
@alexhung Deep is already selected "s2idle [deep]". If I select s2idle, it looks like the same problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882503] Re: eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 / P9
https://lists.ubuntu.com/archives/kernel-team/2020-December/115803.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882503
Title:
eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4
P8 / P9
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
The breakable devices test is hardware-dependent. In our test pool
it will take about:
* 30 seconds to run on a Power8 system that with 5 breakable devices,
* 60 seconds to run on a Power9 system that with 4 breakable devices.
The default 45 seconds kselftest framework timeout is not enough to
allow this test to finish on some nodes. Thus causing this test to
fail with TIMEOUT error.
[Fix]
* f5eca0b279117f ("selftests/powerpc/eeh: disable kselftest timeout
setting for eeh-basic")
We have this testcase since Focal, and this patch can be cherry-picked
into all affected releases.
[Test case]
Run this test on P9 node baltar, on which this timeout issue can be
100% reproduced. With this patch applied, the test can finish without
being terminated by the default timeout.
[Where problems could occur]
This will make test takes longer to finish, but it's still being
controlled by the timeout mechanism both in the test case and
kselftest framework. It's unlikely to make the test hang forever.
== Original Bug Report ==
Issue found on 5.4.0-34.38, Focal P9 "baltar"
# selftests: powerpc/eeh: eeh-basic.sh
# :00:00.0, Skipped: bridge
# 0001:00:00.0, Skipped: bridge
# 0002:00:00.0, Skipped: bridge
# 0002:01:00.0, Added
# 0003:00:00.0, Skipped: bridge
# 0003:01:00.0, Added
# 0004:00:00.0, Skipped: bridge
# 0004:01:00.0, Skipped: bridge
# 0004:02:00.0, Added
# 0005:00:00.0, Skipped: bridge
# 0005:01:00.0, Added
# 0030:00:00.0, Skipped: bridge
# 0031:00:00.0, Skipped: bridge
# 0032:00:00.0, Skipped: bridge
# 0033:00:00.0, Skipped: bridge
# Found 4 breakable devices...
# Breaking 0002:01:00.0...
# 0002:01:00.0, waited 0/60
# 0002:01:00.0, waited 1/60
# 0002:01:00.0, waited 2/60
# 0002:01:00.0, waited 3/60
# 0002:01:00.0, waited 4/60
# 0002:01:00.0, waited 5/60
# 0002:01:00.0, waited 6/60
# 0002:01:00.0, Recovered after 7 seconds
# Breaking 0003:01:00.0...
# 0003:01:00.0, waited 0/60
# 0003:01:00.0, waited 1/60
# 0003:01:00.0, waited 2/60
# 0003:01:00.0, waited 3/60
# 0003:01:00.0, waited 4/60
# 0003:01:00.0, waited 5/60
# 0003:01:00.0, waited 6/60
# 0003:01:00.0, waited 7/60
# 0003:01:00.0, waited 8/60
# 0003:01:00.0, waited 9/60
# 0003:01:00.0, waited 10/60
# 0003:01:00.0, waited 11/60
# 0003:01:00.0, waited 12/60
# 0003:01:00.0, waited 13/60
# 0003:01:00.0, waited 14/60
# 0003:01:00.0, waited 15/60
# 0003:01:00.0, waited 16/60
# 0003:01:00.0, waited 17/60
# 0003:01:00.0, waited 18/60
# 0003:01:00.0, waited 19/60
# 0003:01:00.0, waited 20/60
# 0003:01:00.0, waited 21/60
# 0003:01:00.0, waited 22/60
# 0003:01:00.0, waited 23/60
# 0003:01:00.0, waited 24/60
# 0003:01:00.0, waited 25/60
# 0003:01:00.0, waited 26/60
# 0003:01:00.0, waited 27/60
# 0003:01:00.0, waited 28/60
# 0003:01:00.0, waited 29/60
# 0003:01:00.0, waited 30/60
# 0003:01:00.0, waited 31/60
# 0003:01:00.0, waited 32/60
# 0003:01:00.0, waited 33/60
# 0003:01:00.0, waited 34/60
# 0003:01:00.0, waited 35/60
# 0003:01:00.0, Recovered after 36 seconds
# Breaking 0004:02:00.0...
# 0004:02:00.0, Recovered after 0 seconds
# Breaking 0005:01:00.0...
# 0005:01:00.0, waited 0/60
# 0005:01:00.0, waited 1/60
#
not ok 1 selftests: powerpc/eeh: eeh-basic.sh # TIMEOUT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882503/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
https://lists.ubuntu.com/archives/kernel-team/2021-January/116415.html
--
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/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub
test cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
We have this test since Focal.
This patch can be cherry-picked into all the affected kernels.
[Test]
Run this test with:
sudo ./udpgro.sh
And check its final return value with:
echo $?
If there is any failure, the return value should not be 0.
[Where problems could occur]
If this fix is incorrect it might affect the test execution, but it
should be fine as this is just affecting the test tool. Also, with
this patch, we are expecting to see this test case to fail until
bug 1908501 got fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1908499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
I'm still having this issue on Ubuntu 20.04, even though it seems it was supposed to be fixed. Kernel: 5.8.0-36-generic linux-firmware: 1.187.7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: amdgpu references firmware files in modinfo which have not been supplied to linux-firmware. This causes update-initramfs to generate "Possible missing firmware" warnings. Fix: Since the firmware is not available, all we can do is remove the files from modinfo. Test Case: Confirm that update-initramfs no longer produces the warnings. Regression Potential: Low. If someone had managed to obtain these files they will no longer be added to the initramfs, potentially causing regressions for these users. This would be an atypical situation. --- Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
** Description changed:
[Impact]
- In udpgro.sh, the exit value is 0 even if there are some failed sub test
cases:
+ In udpgro.sh, the exit value is 0 even if there are some failed sub
+ test cases:
$ sudo ./udpgro.sh
ipv4
- no GRO
+ no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- - Length: 568
+ - Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
- data type_id=3 bits_offset=0
- data_end type_id=3 bits_offset=32
- data_meta type_id=3 bits_offset=64
- ingress_ifindex type_id=3 bits_offset=96
- rx_queue_index type_id=3 bits_offset=128
+ data type_id=3 bits_offset=0
+ data_end type_id=3 bits_offset=32
+ data_meta type_id=3 bits_offset=64
+ ingress_ifindex type_id=3 bits_offset=96
+ rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
- multiple GRO socks
+ multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- - Length: 568
+ - Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
- data type_id=3 bits_offset=0
- data_end type_id=3 bits_offset=32
- data_meta type_id=3 bits_offset=64
- ingress_ifindex type_id=3 bits_offset=96
- rx_queue_index type_id=3 bits_offset=128
+ data type_id=3 bits_offset=0
+ data_end type_id=3 bits_offset=32
+ data_meta type_id=3 bits_offset=64
+ ingress_ifindex type_id=3 bits_offset=96
+ rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
- We have this test since Focal. This patch can be cherry-picked into all
- the affected kernels.
+ We have this test since Focal.
+ This patch can be cherry-picked into all the affected kernels.
[Test]
Run this test with:
- sudo ./udpgro.sh
+ sudo ./udpgro.sh
And check its final return value with:
- echo $?
+ echo $?
- If there is any failure, the return value should not be 0
+ If there is any failure, the return value should not be 0.
[Where problems could occur]
- If this fix is incorrect it might affect the test execution, but it should be
fine as this is just affecting the testing tool. Also, with this patch, we are
expecting to see this test case to fail until bug 1908501 got fixed.
+ If this fix is incorrect it might affect the test execution, but it
+ should be fine as this is just affecting the test tool. Also, with
+ this patch, we are expecting to see this test case to fail until
+ bug 1908501 got fixed.
--
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/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub
test cases:
$ sudo ./udpgro.sh
ipv4
no GRO
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
** Description changed: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] + $ lintian --pedantic libbpf_0.3-2.dsc + P: libbpf source: no-homepage-field + P: libbpf source: silent-on-rules-requiring-root [Maintenance] [Background information] -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: New Status in libbpf package in Ubuntu: Incomplete Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] [Background information] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
** Description changed: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] [Quality assurance] + At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. [Dependencies] + libc6: main + libelf1: main + zlib1g: main [Standards compliance] [Maintenance] [Background information] -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: New Status in libbpf package in Ubuntu: Incomplete Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] [Maintenance] [Background information] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
** Description changed:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub test
cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
We have this test since Focal. This patch can be cherry-picked into all
the affected kernels.
[Test]
Run this test with:
sudo ./udpgro.sh
And check its final return value with:
echo $?
If there is any failure, the return value should not be 0
[Where problems could occur]
- With this patch, we are expecting to see this test case to fail before bug
1908501 got fixed.
+ If this fix is incorrect it might affect the test execution, but it should be
fine as this is just affecting the testing tool. Also, with this patch, we are
expecting to see this test case to fail until bug 1908501 got fixed.
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Invalid
--
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/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub
test cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc3/amd64/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
In udpgro.sh, the exit value is 0 even if there are some failed sub test
cases:
$ sudo ./udpgro.sh
ipv4
no GRO
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
./udpgso_bench_tx: write: Connection refused
...
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
$ echo $?
0
[Fix]
* 3503ee6c0bec5f ("selftests: fix the return value for UDP GRO test")
+ We have this test since Focal. This patch can be cherry-picked into all
+ the affected kernels.
+
[Test]
Run this test with:
- sudo ./udpgro.sh
+ sudo ./udpgro.sh
And check its final return value with:
- echo $?
+ echo $?
If there is any failure, the return value should not be 0
[Where problems could occur]
With this patch, we are expecting to see this test case to fail before bug
1908501 got fixed.
** Also affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.6 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.6 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.6 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** No longer affects: linux-oem-5.10 (Ubuntu Groovy)
** No longer affects: linux-oem-5.10 (Ubuntu Hirsute)
** No longer affects: linux-oem-5.6 (Ubuntu Groovy)
** No longer affects: linux-oem-5.6 (Ubuntu Hirsute)
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908499
Title:
udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
sub-test result
Status in ubuntu-kernel-tests:
[Kernel-packages] [Bug 1910555] Re: Driver build error on kernel 5.8, but works on 5.4
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb Worked its magic for me. Thank you all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1910555 Title: Driver build error on kernel 5.8, but works on 5.4 Status in bcmwl package in Ubuntu: Confirmed Bug description: Recently kernel was updated on Focal from 5.4 to 5.8. From that moment on WiFi doesn't work anymore. After a try rebuild (reconfigure) the result is: --- # dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.4.0-59-generic 5.8.0-34-generic Building for architecture x86_64 Building initial module for 5.4.0-59-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-59-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. --- As could be seen, the build for 5.4 completes successfully (and works on same kernel), but for 5.8 fails. Seems something is going wrong with missing function declaration - function "ioremap_nocache", as could be seen in attached make.log. I'm guessing, driver code may need be updated according to the new kernel headers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 17:13:05 2021 InstallationDate: Installed on 2020-06-22 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910576] Re: [MIR] libbpf (dependency of iproute2)
** Description changed: - [MIR] libbpf (dependency of iproute2) + [Availability] + libbpf | 0.1.0-1 | groovy/universe | source + libbpf | 0.3-2 | hirsute/universe | source + + [Rationale] + Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) + + [Security] + + [Quality assurance] + + [Dependencies] + + [Standards compliance] + + [Maintenance] + + [Background information] -- You received this bug notification because you are a member of Kernel Packages, which is a bug assignee. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: New Status in libbpf package in Ubuntu: Incomplete Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] [Quality assurance] [Dependencies] [Standards compliance] [Maintenance] [Background information] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result
** Description changed: - In udpgro.sh, the exit value is 0 even if there are some failed sub test - cases: + [Impact] + In udpgro.sh, the exit value is 0 even if there are some failed sub test cases: $ sudo ./udpgro.sh ipv4 - no GRO + no GRO BTF debug data section '.BTF' rejected: Invalid argument (22)! - - Length: 568 + - Length: 568 Verifier analysis: magic: 0xeb9f version: 1 flags: 0x0 hdr_len: 24 type_off: 0 type_len: 256 str_off: 256 str_len: 288 btf_total_size: 568 [1] PTR (anon) type_id=2 [2] STRUCT xdp_md size=20 vlen=5 - data type_id=3 bits_offset=0 - data_end type_id=3 bits_offset=32 - data_meta type_id=3 bits_offset=64 - ingress_ifindex type_id=3 bits_offset=96 - rx_queue_index type_id=3 bits_offset=128 + data type_id=3 bits_offset=0 + data_end type_id=3 bits_offset=32 + data_meta type_id=3 bits_offset=64 + ingress_ifindex type_id=3 bits_offset=96 + rx_queue_index type_id=3 bits_offset=128 [3] TYPEDEF __u32 type_id=4 [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none) [5] FUNC_PROTO (anon) return=6 args=(1 ctx) [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED [7] FUNC xdp_dummy_prog type_id=5 [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4 [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none) [11] VAR _license type_id=9 linkage=1 [12] DATASEC license size=0 vlen=1 size == 0 ./udpgso_bench_rx: poll: 0x0 expected 0x1 failed ./udpgso_bench_tx: write: Connection refused - no GRO chk cmsg + + ... + + multiple GRO socks BTF debug data section '.BTF' rejected: Invalid argument (22)! - - Length: 568 + - Length: 568 Verifier analysis: magic: 0xeb9f version: 1 flags: 0x0 hdr_len: 24 type_off: 0 type_len: 256 str_off: 256 str_len: 288 btf_total_size: 568 [1] PTR (anon) type_id=2 [2] STRUCT xdp_md size=20 vlen=5 - data type_id=3 bits_offset=0 - data_end type_id=3 bits_offset=32 - data_meta type_id=3 bits_offset=64 - ingress_ifindex type_id=3 bits_offset=96 - rx_queue_index type_id=3 bits_offset=128 - [3] TYPEDEF __u32 type_id=4 - [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none) - [5] FUNC_PROTO (anon) return=6 args=(1 ctx) - [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED - [7] FUNC xdp_dummy_prog type_id=5 - [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED - [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4 - [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none) - [11] VAR _license type_id=9 linkage=1 - [12] DATASEC license size=0 vlen=1 size == 0 - - ./udpgso_bench_rx: poll: 0x0 expected 0x1 - - failed - ./udpgso_bench_tx: write: Connection refused - GRO - BTF debug data section '.BTF' rejected: Invalid argument (22)! - - Length: 568 - Verifier analysis: - - magic: 0xeb9f - version: 1 - flags: 0x0 - hdr_len: 24 - type_off: 0 - type_len: 256 - str_off: 256 - str_len: 288 - btf_total_size: 568 - [1] PTR (anon) type_id=2 - [2] STRUCT xdp_md size=20 vlen=5 - data type_id=3 bits_offset=0 - data_end type_id=3 bits_offset=32 - data_meta type_id=3 bits_offset=64 - ingress_ifindex type_id=3 bits_offset=96 - rx_queue_index type_id=3 bits_offset=128 - [3] TYPEDEF __u32 type_id=4 - [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none) - [5] FUNC_PROTO (anon) return=6 args=(1 ctx) - [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED - [7] FUNC xdp_dummy_prog type_id=5 - [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED - [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4 - [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none) - [11] VAR _license type_id=9 linkage=1 - [12] DATASEC license size=0 vlen=1 size == 0 - - ./udpgso_bench_rx: poll: 0x0 expected 0x1 - - failed - GRO chk cmsg - BTF debug data section '.BTF' rejected: Invalid argument (22)! - - Length: 568 - Verifier analysis: - - magic: 0xeb9f - version: 1 - flags: 0x0 - hdr_len: 24 - type_off: 0 - type_len: 256 - str_off: 256 - str_len: 288 - btf_total_size: 568 - [1] PTR (anon) type_id=2 - [2] STRUCT xdp_md size=20 vlen=5 - data type_id=3 bits_offset=0 - data_end type_id=3 bits_offset=32 - data_meta type_id=3 bits_offset=64 - ingress_ifindex type_id=3 bits_offset=96 - rx_queue_index type_id=3 bits_offset=128 - [3] TYPEDEF __u32 type_id=4 - [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none) - [5] FUNC_PROTO (anon) return=6 args=(1 ctx) - [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED - [7] FUNC xdp_dummy_prog type_id=5 - [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED - [9]
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Can't reproduce this on XPS 15 9560 BIOS Information Vendor: Dell Inc. Version: 1.20.0 Release Date: 07/21/2020 Linux acelan-xps15-9560 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux nvidia, 460.32.03, 5.8.0-36-generic, x86_64: installed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910664] Re: Need a new firmware to support RTL8821ce Wifi
** Tags added: oem-priority originate-from-1910492 somerville -- 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/1910664 Title: Need a new firmware to support RTL8821ce Wifi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Bug description: [Impact] It shows below messages and fails to enable the wifi [ 3.965229] u kernel: rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.965403] u kernel: rtw_8821ce :04:00.0: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2 [ 3.965405] u kernel: rtw_8821ce :04:00.0: failed to request firmware [ 3.967613] u kernel: rtw_8821ce :04:00.0: failed to load firmware [Fix] There is a new firmware need to cherry pick 401bd6de rtw88: RTL8821C: add firmware file v24.5 [Test] After add the firmware, it shows [ 3.930187] rtw_8821ce :04:00.0: enabling device ( -> 0003) [ 3.931104] rtw_8821ce :04:00.0: Firmware version 24.5.0, H2C version 12 [ 3.999271] rtw_8821ce :04:00.0 wlp4s0: renamed from wlan0 [Where problems could occur] No problems could occur since it enables a new device. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1910664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
