[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
For focal, ftrace test in kernel-selftests passed even with unresolved
test case present.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877958
Title:
Do not treat unresolved test case in ftrace from
ubuntu_kernel_selftests as failure
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
== SRU Justification ==
There are some test cases in ftrace from ubuntu_kernel_selftests that
would need some kernel configs to be enabled or have some special HW
requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1
If the requirement was not met, these test will fail with "unresolved"
and return 1. So even these is no failed test case, the ftrace test
will still be marked as "failed" with the presence of unresolved test:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
not ok 1 selftests: ftrace: ftracetest # exit=1
== Fix ==
* b730d668138c ("ftrace/selftest: make unresolved cases cause failure if
--fail-unresolved set")
This patch will only make unresolved test case return 1 if we ask it
to fail with unresolved test case.
It can be cherry-picked to kernels starting from Disco.
For Bionic and Xenial it needs to be backported with some context
adjustment as they're missing some other patches to the testing tool.
== Test ==
With the patch applied, the ftrace test will not be marked as failed
with the presence of unresolved test case:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
ok 1 selftests: ftrace: ftracetest
== Regression Potential ==
Low, changes limited to testing tools, no actual impacts to our kernels.
The worst case is to cause false negative in test reports, but in that
case it's probably a test case issue since a failed case should be
treated as a failed one, instead of unresolved.
== Original Bug Report ==
There are some test cases in ftrace from ubuntu_kernel_selftests that would
need some kernel configs to be enabled.
bug 1869347
bug 1869349
We should not treat unresolved test case as a failure, as it's
expected to fail with no correlated configs enabeled.
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
#diff-33d74da785cbc5da20f71eb1af106d68
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
This fact applies to other releases too.
** Tags removed: verification-needed-bionic verification-needed-eoan
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-eoan
verification-done-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/1877958
Title:
Do not treat unresolved test case in ftrace from
ubuntu_kernel_selftests as failure
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
== SRU Justification ==
There are some test cases in ftrace from ubuntu_kernel_selftests that
would need some kernel configs to be enabled or have some special HW
requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1
If the requirement was not met, these test will fail with "unresolved"
and return 1. So even these is no failed test case, the ftrace test
will still be marked as "failed" with the presence of unresolved test:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
not ok 1 selftests: ftrace: ftracetest # exit=1
== Fix ==
* b730d668138c ("ftrace/selftest: make unresolved cases cause failure if
--fail-unresolved set")
This patch will only make unresolved test case return 1 if we ask it
to fail with unresolved test case.
It can be cherry-picked to kernels starting from Disco.
For Bionic and Xenial it needs to be backported with some context
adjustment as they're missing some other patches to the testing tool.
== Test ==
With the patch applied, the ftrace test will not be marked as failed
with the presence of unresolved test case:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
ok 1 selftests: ftrace: ftracetest
== Regression Potential ==
Low, changes limited to testing tools, no actual impacts to our kernels.
The worst case is to cause false negative in test reports, but in that
case it's probably a test case issue since a failed case should be
treated as a failed one, instead of unresolved.
== Original Bug Report ==
There are some test cases in ftrace from ubuntu_kernel_selftests that would
need some kernel configs to be enabled.
bug 1869347
bug 1869349
We should not treat unresolved test case as a failure, as it's
expected to fail with no correlated configs enabeled.
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
#diff-33d74da785cbc5da20f71eb1af106d68
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels
X-kvm:
---
running psock_tpacket test
[SKIP] CONFIG_KALLSYMS not enabled
B-kvm:
[SKIP] CONFIG_KALLSYMS not enabled
** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-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/1812176
Title:
psock_tpacket from the net test in ubuntu_kernel_selftests failed on
KVM kernels
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux-kvm source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Committed
Status in linux-kvm source package in Bionic:
In Progress
Status in linux source package in Disco:
Fix Committed
Status in linux-kvm source package in Disco:
In Progress
Bug description:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with
B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused
by the attempt to access /proc/kallsyms in test_kernel_bit_width():
static int test_kernel_bit_width(void)
{
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;
fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 08:05:47 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812176/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877415] Re: Add crda dependency
** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1877415 Title: Add crda dependency Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Bionic: New Status in linux-raspi source package in Focal: New Bug description: We need to add the "iw" package to the pi images (for configuration of the wifi region upon boot). However, as we don't have per-device seeds this can't be placed directly in the seed for the images (without affecting other images which don't need it). Hence, adding it as a "fake" dependency of the pi-specific kernel package is a reasonably clean solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1877415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882525] Re: [amdgpu] Display is corrupted upon login on Ryzen APU
Now this is where it gets weird. Since I have Ubuntu MATE, I installed the ubuntu-desktop package to get the default GNOME environment. I kept my display manager as LightDM in case that's relevant. Then I rebooted and tested all 3 desktop modes with default kernel options. As expected, MATE is still broken. I rebooted and tried "Ubuntu (Default)" and there were no issues whatsoever. I opened a few apps and all of them displayed OK, and used inxi -G to verify that the display server was indeed X. I rebooted again to test "Ubuntu on Wayland" and it behaved as expected too. Whatever's going wrong, it's limited to MATE, as even GNOME on X is fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] Display is corrupted upon login on Ryzen APU Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots normally to the display manager (login screen) as expected. But once I log in, everything on the screen is cut up into horizontal slices, with each slice offset farther right than the slice above, and squares of random colors running diagonally across the screen. I've attached a picture of my monitor showing the issue for reference. My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 2200G APU, and using that APU's integrated graphics. In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems fixed in the new kernel. I don't believe they're related but I figure it's worth mentioning. I tried adding the nomodeset kernel option at boot, and it's an effective workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if this was caused by some quirk of my particular software setup, and successfully reproduced the bug, proving it wasn't. If you'd like me to, I can provide log files, system information, etc. or help narrow it down by testing workarounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Jun 8 06:41:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043:876b] InstallationDate: Installed on 2019-10-20 (231 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1882525/+subscriptions -- Mailing
[Kernel-packages] [Bug 1882525] Re: [amdgpu] Display is corrupted upon login on Ryzen APU
Maybe it's the 'marco' window manager then? ** No longer affects: linux (Ubuntu) ** Also affects: marco (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New ** Summary changed: - [amdgpu] Display is corrupted upon login on Ryzen APU + [amdgpu] MATE desktop is corrupted upon login on Ryzen APU ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882525 Title: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU Status in marco package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu boots normally to the display manager (login screen) as expected. But once I log in, everything on the screen is cut up into horizontal slices, with each slice offset farther right than the slice above, and squares of random colors running diagonally across the screen. I've attached a picture of my monitor showing the issue for reference. My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 3 2200G APU, and using that APU's integrated graphics. In terms of software I'm running Ubuntu 20.04, which I just upgraded to and did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems fixed in the new kernel. I don't believe they're related but I figure it's worth mentioning. I tried adding the nomodeset kernel option at boot, and it's an effective workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if this was caused by some quirk of my particular software setup, and successfully reproduced the bug, proving it wasn't. If you'd like me to, I can provide log files, system information, etc. or help narrow it down by testing workarounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Jun 8 06:41:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1043:876b] InstallationDate: Installed on 2019-10-20 (231 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/marco/+bug/1882525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages Mo
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861636] Re: Lenovo ThinkBook 14-IML Touchpad not detected
*** This bug is a duplicate of bug 1853277 *** https://bugs.launchpad.net/bugs/1853277 Same issue here, In windows synaptic driver is being used and its working properly. In Ubuntu 18.04, Kernel 5.3.0-53-generic hardware is not listed in /proc/bus/input/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861636 Title: Lenovo ThinkBook 14-IML Touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: Hi, i have a new Lenovo ThinkBook 14-IML. It shiped with Win10 preinstalled. I booted once into Windows to check all devices. Everyting worked including the touchpad. Then I've installed Ubuntu 18.04. Unfortunately, the touchpad is not working. xinput list does not show a touchpad device. Other users seem to have the same problem, like this new question on askubuntu: https://askubuntu.com/questions/1205382/elan-touchpad-not-working-on-lenovo-thinkbook-with-ubuntu-18-04?noredirect=1 Upgraded to Ubuntu 19.10 but the problem remains. I've attached the output of: cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1925 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 23:12:21 2020 InstallationDate: Installed on 2020-01-31 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-01-31 (2 days ago) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN23WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN23WW:bd11/12/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: Lenovo ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
The shutdown is caused by the commit of https://bugzilla.gnome.org/show_bug.cgi?id=688076. gnome-session-bin handle the first shutdown request, and change to QUERY_END_SESSION_PHASE, but the second shutdown request arrive before it open the endSessionDialog, and user not yet confirm to shutdown. The second shutdown request is handled in QUERY_END_SESSION_PHASE, which goes to prepare shutdown by the commit mentioned above. Therefore, I create a patch to check if the shutdown has been confirmed by the user then process the prepare shutdown. It seems can fix this issue. ** Bug watch added: bugzilla.gnome.org/ #688076 https://bugzilla.gnome.org/show_bug.cgi?id=688076 ** Patch added: "Patch which verified OK on the platform has 2 key event with single press" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1878351/+attachment/5381991/+files/check-if-logout-forced-before-perform-shutdown.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Re: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures
Hello! Yes, I do have the Sophos Antivirus software installed. However, your commands failed to work on my machine. Previously, I had done the same with a different command. sudo systemctl stop sav-protect.service This usually does the trick (stops the antivirus), then I proceeded to your code of... sudo apt-get install -f ...which did nothing. I did try to update the linux image/kernel again... And these new packages were installed... frederick@frederickpina:~$ sudo apt-get upgrade linux-image-generic Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: amd64-microcode intel-microcode iucode-tool linux-image-generic linux-modules-extra-5.4.0-33-generic thermald 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/41.2 MB of archives. After this operation, 193 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously unselected package iucode-tool. (Reading database ... 236417 files and directories currently installed.) Preparing to unpack .../0-iucode-tool_2.3.1-1_amd64.deb ... Unpacking iucode-tool (2.3.1-1) ... Selecting previously unselected package linux-modules-extra-5.4.0-33-generic. Preparing to unpack .../1-linux-modules-extra-5.4.0-33-generic_5.4.0-33.37_amd64.deb ... Unpacking linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ... Selecting previously unselected package intel-microcode. Preparing to unpack .../2-intel-microcode_3.20191115.1ubuntu3_amd64.deb ... Unpacking intel-microcode (3.20191115.1ubuntu3) ... Selecting previously unselected package amd64-microcode. Preparing to unpack .../3-amd64-microcode_3.20191218.1ubuntu1_amd64.deb ... Unpacking amd64-microcode (3.20191218.1ubuntu1) ... Selecting previously unselected package linux-image-generic. Preparing to unpack .../4-linux-image-generic_5.4.0.33.38_amd64.deb ... Unpacking linux-image-generic (5.4.0.33.38) ... Selecting previously unselected package thermald. Preparing to unpack .../5-thermald_1.9.1-1ubuntu0.1_amd64.deb ... Unpacking thermald (1.9.1-1ubuntu0.1) ... Setting up iucode-tool (2.3.1-1) ... Setting up intel-microcode (3.20191115.1ubuntu3) ... update-initramfs: deferring update (trigger activated) intel-microcode: microcode will be updated at next boot Setting up amd64-microcode (3.20191218.1ubuntu1) ... update-initramfs: deferring update (trigger activated) amd64-microcode: microcode will be updated at next boot Setting up linux-modules-extra-5.4.0-33-generic (5.4.0-33.37) ... Setting up thermald (1.9.1-1ubuntu0.1) ... Setting up linux-image-generic (5.4.0.33.38) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic Processing triggers for linux-image-5.4.0-33-generic (5.4.0-33.37) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-33-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-33-generic Found initrd image: /boot/initrd.img-5.4.0-33-generic Found linux image: /boot/vmlinuz-5.4.0-29-generic Found initrd image: /boot/initrd.img-5.4.0-29-generic Adding boot menu entry for UEFI Firmware Settings done frederick@frederickpina:~$ ^C After this, I restarted the machine and thought the Wifi drivers would work again; but in actuality did not. I then tried to reinstall the wifi drivers directly, via this method... But again, ran into another stumbling block: frederick@frederickpina:~$ sudo apt update && apt install firmware-iwlwifi Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu focal InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:5 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease Ign:6 https://packages.erlang-solutions.com/ubuntu focal InRelease Hit:7 https://packages.erlang-solutions.com/ubuntu focal Release Hit:8 http://archive.ubuntu.com/ubuntu focal-security InRelease Hit:9 http://ppa.launchpad.net/libreoffice/ppa/ubuntu focal InRelease Hit:10 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Hit:11 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease Hit:12 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu focal InRelease Hit:14 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease Hit:15 http://ppa.launchpad.net/utappia/stable/ubuntu focal InRelease Reading package lists...
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
I worked with Claire and the wpasupplicant in the above PPA (#31) can fix the issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin 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/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD
By installing an OLDER mainline kernel 5.3.18-050318-generic x86_64, the behaviour has reverted to what I had before Ubuntu 20.04, meaning: if the router switches the canal for the 5 Ghz band, connection is lost and then a new connection is set on the 2.4 Ghz band. Interestingly, what can be seen in attachments in message #4 and #5 is happening too but is not reproduced endlessly, just a few attempts. ** Attachment added: "syslog (older kernel)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+attachment/5382011/+files/syslog%20%28older%20kernel%29 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881214 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. edit: see comment #14 So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. edit: not true actually, this happened again using this upstream kernel. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. edit: and when the event starts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD
** Attachment added: "kern (older kernel).log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+attachment/5382012/+files/kern%20%28older%20kernel%29.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881214 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Mate 20.04, with all supplied kernels up to 5.4.0.33 I occasionally see a message on my screen that disk space is low. I try rebooting since my computer is unresponsive. Normal reboot does not work, sudo reboot does not work. I have to power off the machine using power button. Machine boots but hangs because its trying to repair journal info. I can't see what causes that since I was not using my computer at the time. edit: see comment #14 So with a live session, I can see that syslog and kern.log files have grown to several GB until the drive is full. When using an upstream kernel 5.4.43-050443-generic x86_64, I haven't had any problem so far. edit: not true actually, this happened again using this upstream kernel. Never had this issue with previous Ubuntu versions with the very same hardware configuration, since 16.04. Included: partial syslog and kern.log with the same message repeated over and over. edit: and when the event starts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882194] Re: Intel Wireless 7265 [8086:095a] Subsystem [8086:5010] not probed after kernel packages upgrade failures
Was just tinkering with this... What do you think? frederick@frederickpina:~$ sudo add-apt-repository ppa:canonical-hwe-team/backport-iwlwifi [sudo] password for frederick: Bleeding-edge backport-iwlwifi DKMS packages built from https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git. See https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi for device/firmware compatibility. A few notes for this PPA: 1. it is not intended for landing new proposed releases into Ubuntu archive, 2. it's not related to the official packages in the Ubuntu archive in any way, 3. it is only for experiments during hardware enablement, More info: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/backport-iwlwifi Press [ENTER] to continue or Ctrl-c to cancel adding it. Ign:1 https://packages.erlang-solutions.com/ubuntu focal InRelease Hit:2 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu focal InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [107 kB] Hit:5 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease Hit:6 https://packages.erlang-solutions.com/ubuntu focal Release Hit:7 http://ppa.launchpad.net/libreoffice/ppa/ubuntu focal InRelease Get:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Hit:9 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Get:11 http://archive.ubuntu.com/ubuntu focal-security InRelease [107 kB] Hit:12 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease Hit:13 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu focal InRelease Hit:14 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease Hit:15 http://ppa.launchpad.net/utappia/stable/ubuntu focal InRelease Fetched 312 kB in 3s (120 kB/s) Reading package lists... Done frederick@frederickpina:~$ sudo apt-get update Ign:1 https://packages.erlang-solutions.com/ubuntu focal InRelease Hit:2 http://ppa.launchpad.net/canonical-hwe-team/backport-iwlwifi/ubuntu focal InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [107 kB] Hit:5 https://packages.erlang-solutions.com/ubuntu focal Release Hit:6 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease Hit:7 http://ppa.launchpad.net/libreoffice/ppa/ubuntu focal InRelease Get:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Hit:10 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Get:11 http://archive.ubuntu.com/ubuntu focal-security InRelease [107 kB] Hit:12 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease Hit:13 http://ppa.launchpad.net/transmissionbt/ppa/ubuntu focal InRelease Hit:14 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu focal InRelease Hit:15 http://ppa.launchpad.net/utappia/stable/ubuntu focal InRelease Fetched 312 kB in 3s (121 kB/s) Reading package lists... Done frederick@frederickpina:~$ sudo apt install backport-iwlwifi-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: backport-iwlwifi-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,567 kB of archives. After this operation, 10.0 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal/universe amd64 backport-iwlwifi-dkms all 8324-0ubuntu1 [1,567 kB] Fetched 1,567 kB in 4s (445 kB/s) Selecting previously unselected package backport-iwlwifi-dkms. (Reading database ... 241906 files and directories currently installed.) Preparing to unpack .../backport-iwlwifi-dkms_8324-0ubuntu1_all.deb ... Unpacking backport-iwlwifi-dkms (8324-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/backport-iwlwifi-dkms_832 4-0ubuntu1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/backport-iwlwifi-dkms.list-new': Operation not permitted dpkg: error: unable to create new file '/var/lib/dpkg/status-new': Operation not permitted E: Sub-process /usr/bin/dpkg returned an error code (2) frederick@frederickpina:~$ frederick@frederickpina:~$ sudo backport-iwlwifi-dkms sudo: backport-iwlwifi-dkms: command not found frederick@frederickpina:~$ sudo backport-iwlwifi-dkms sudo: backport-iwlwifi-dkms: command not found frederick@frederickpina:~$ sudo install backport-iwlwifi-dkms install: missing destination file operand after 'backport-iwlwifi-dkms' Try 'install --help' for more information. frederick@frederickpina:~$ sudo apt install backport-iwlwifi-dkms E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. frederick@frederickpina:~$ sudo dpkg --configure -a frederick@frederickpina:~$ sudo apt install backport-iwlwifi-dkms Reading package l
[Kernel-packages] [Bug 1882717] [NEW] fanotify10 test case 16 failed on focal
Public bug reported: This is a new test cases added recently: https://github.com/linux-test-project/ltp/commit/997d87d544042ded4b858377c95a90e1c12036b8 fanotify10.c:347: INFO: Test #16: ignore child exec events created on a specific mount point fanotify10.c:306: PASS: group 0 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 1 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 2 got event: mask 1020 pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 5.4 focal kqa-blocker sru-20200518 ubuntu-ltp-syscalls ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: 5.4 focal kqa-blocker sru-20200518 ubuntu-ltp-syscalls -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882717 Title: fanotify10 test case 16 failed on focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a new test cases added recently: https://github.com/linux-test-project/ltp/commit/997d87d544042ded4b858377c95a90e1c12036b8 fanotify10.c:347: INFO: Test #16: ignore child exec events created on a specific mount point fanotify10.c:306: PASS: group 0 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 1 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 2 got event: mask 1020 pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882717] 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 1882717 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/1882717 Title: fanotify10 test case 16 failed on focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a new test cases added recently: https://github.com/linux-test-project/ltp/commit/997d87d544042ded4b858377c95a90e1c12036b8 fanotify10.c:347: INFO: Test #16: ignore child exec events created on a specific mount point fanotify10.c:306: PASS: group 0 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 1 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 2 got event: mask 1020 pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
The attachment "Patch which verified OK on the platform has 2 key event with single press" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878602] Re: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail
I don't know much about xHCI so Mathias can comment on that. I do remember seeing messages like: usb usb2-port1: Cannot enable. Maybe the USB cable is bad? in the past but not sure if it is only with ICL. It is also weird that the TCSS xHCI is doing anything if you plug TBT 3 device since USB is not tunneled. Might be something related to Type-C or PD. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878602 Title: When TBT dock is plugged into ICL TBT xHCI, port without device is in CAS state, causes many warm reset fail Status in linux package in Ubuntu: Confirmed Bug description: Since we can't use bugzilla for USB bugs, let's use Launchpad so we can attach dmesg :) System: XPS 9300 ICL Dock: Dell WD19TB Thunderbolt dock Linux: 5.7-rc5 Right after the dock is plugged, [ 127.205823] xhci_hcd :00:0d.0: Get port status 2-1 read: 0x10202a0, return 0x10341 [ 127.205832] usb usb2-port1: status 0341 change 0001 CAS is flagged so warm-reset ensues: [ 127.313467] usb usb2-port1: do warm reset However, it seems nothing is connected to usb2-port1, causes many warm-reset fail, hence this error message: [ 132.158968] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? This issue doesn't happen on CML system with AR/TR TBT controller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
🎉 glad that I could help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin 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/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Just a thought. Since we have list of commands in here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/132 and more commands/debugging here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/134 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/135 (how to is here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/133) Can someone try out those commands to see if they solve no audio bug after rebooting from Windows to Linux? Note that this bug can be solved by suspending & resuming laptop (on linux) as well as performing full shutdown when switching from Windows to 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
@Taha Soomro (suryaya) - I assume you have UX533FTC laptop (and not UX534* laptop). 1. Disable all commands that are performed on boot. 2. Reboot laptop - sound is not working 3. Apply only these manually: hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 4. Listen to some audio and realize if sound sounds OK or if some frequencies are distorted. 5. Reboot 6. Apply only these manually: hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 7. Listen to some audio and realize if sound is any different when compared to 2 commands only. My point is - on UX533FTC you don't need 4 commands. 2 are enough, because to me audio sounds exactly identical. The remaining issue is microphone on this particular model. @Sergey - I already tried attaching IOMMU group, but without success. I got error code 10 (or 11 - don't remember) in Windows for unknown reason when enabling/using the audio device. I used VM in legacy mode. The overall process is pretty complex to get it working correctly, and I don't have any experience with in the first place. Might give it another try at some time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
Thanks for the reply. TinyUSB runs on the microcontroller board; it is the USB stack implementation used by the software on the board. So it doesn't touch the kernel, by definition. It is behaving in some way that is unexpected to the Linux driver, and causing bad behavior on the part of the driver. It is possible this is a timing or kernel driver state machine. These crashes occur when I reset the board. So the USB device is forcibly disconnected, and then immediately tries to re-enumerate. This is much faster than the usual unplug/replug time you might see, if say, you unplugged a replugged a USB keyboard or USB flash drive. Would a USB trace be helpful to you? I can use a Beagle and get a trace file. Is this the right place to continue discussing this bug, or should it be in some Linux kernel bug system? 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/1871143 Title: Kernel crash during USB device enumeration or mounting Status in linux package in Ubuntu: Incomplete Bug description: Device is an Adafruit microcontroller board running https://github.com/adafruit/circuitpython, using the TinyUSB USB stack: https://github.com/hathach/tinyusb. Device presents a composite USB device that includes MSC, CDC, HID, and MIDI Device was commanded to forcibly reformat its MSC FAT12 filesystem and then reset, which causes a USB reset and re-enumeration. This causes some USB kernel code to crash, much of the time, though not quite all the time. I work for Adafruit and the maintainer of TinyUSB also works for Adafruit, so we can provide further help to track this down. Attached is the dmesg file for the crash. I tried uploading the dump file from kdump, but launchpad is timing out. The dump file is available at: https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halbert1857 F pulseaudio /dev/snd/controlC2: halbert1857 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Apr 6 11:09:43 2020 HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85 InstallationDate: Installed on 2017-09-19 (929 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
** No longer affects: ubuntu-drivers-common (Ubuntu Focal) ** No longer affects: ubuntu-drivers-common (Ubuntu 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/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440-server source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: In Progress Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in nvidia-graphics-drivers-440-server source package in Focal: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'jiffies_to_timespec'". - Fixed driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "passing argument 4 of 'proc_create_data' from incompatible pointer type". 440.64.00: * Initial release. 418.126.02 * Initial release. nvidia-settings (440.82): * New upstream release (LP: #1881137). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packa
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
Open a upstream bug for this issue. https://gitlab.gnome.org/GNOME/gnome-session/-/issues/67 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/-/issues #67 https://gitlab.gnome.org/GNOME/gnome-session/-/issues/67 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Confirmed Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867686] Re: FC hosts become unresponsive during array upgrade
I am attempting to install Ubuntu 20.04 LTS to my SANboot LUN before upgrading to the kernel provided, but it appears that the installation fails at the "updating initramfs configuration step". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867686] Re: FC hosts become unresponsive during array upgrade
** Attachment added: "Ubuntu-20-04-LTS-SANboot-Fail.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+attachment/5382025/+files/Ubuntu-20-04-LTS-SANboot-Fail.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Hi Jo, Eric, Eric, thanks for uploading to Groovy! (Sorry, I had made similar changes to groovy v2 debdiff -- no worries, but just wanted to let you know I checked those for groovy too, to not give you more trouble in helping here! :-) The changes have landed in Groovy, so I just uploaded to Focal/Eoan/Bionic/Xenial. cheers, Mauricio ** Changed in: makedumpfile (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: New Status in makedumpfile source package in Bionic: New Status in makedumpfile source package in Eoan: New Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't not work
Hi, Do you know if the same issue also occurs on Xenial? -- 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/1882624 Title: nested kvm doesn't not work Status in linux-azure package in Ubuntu: New Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard E4s v3 Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Install qemu-kvm, download https://eosgnestedstorage.blob.core.windows.net/images/nested- ubuntu-4.15.0-23-generic.qcow2 Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize Expected ssh -p 60022 nesteduser@localhost will ask password to login We can't connect to it, see below call trace in dmesg qemu-kvm version doesn't change after kernel upgraded. 2.0.0+dfsg-2ubuntu1.46 [ 53.420589] hv_balloon: Max. dynamic memory size: 32768 MB [ 60.928772] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. [ 60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable [ 60.967454] BUG: unable to handle kernel paging request at 56b8 [ 60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] PGD 0 P4D 0 [ 60.971140] Oops: [#1] SMP PTI [ 60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils [ 60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 4.15.0-1084-azure #94~14.04.1-Ubuntu [ 60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002 [ 60.971140] RAX: RBX: RCX: [ 61.020070] RDX: 6c14 RSI: RDI: [ 61.020070] RBP: a44847a53d10 R08: R09: [ 61.020070] R10: R11: R12: [ 61.020070] R13: R14: R15: [ 61.020070] FS: 7f753bba4700() GS:8fefdd68() knlGS: [ 61.020070] CS: 0010 DS: ES: CR0: 80050033 [ 61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 003726e0 [ 61.020070] Call Trace: [ 61.020070] vcpu_enter_guest+0x909/0x12a0 [kvm] [ 61.020070] kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm] [ 61.020070] kvm_vcpu_ioctl+0x2a8/0x630 [kvm] [ 61.020070] ? dequeue_signal+0x3e/0x160 [ 61.020070] ? do_sigtimedwait+0xbd/0x210 [ 61.020070] ? copy_siginfo_to_user+0x12e/0x2d0 [ 61.020070] do_vfs_ioctl+0x9b/0x5f0 [ 61.020070] ? SyS_futex+0x71/0x150 [ 61.020070] SyS_ioctl+0x79/0x90 [ 61.020070] ? _copy_to_user+0x26/0x40 [ 61.020070] do_syscall_64+0x80/0x1e0 [ 61.020070] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 61.020070] RIP: 0033:0x7f7545f34ea7 [ 61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 0010 [ 61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 7f7545f34ea7 [ 61.020070] RDX: RSI: ae80 RDI: 000c [ 61.020070] RBP: 55c68fd7f160 R08: R09: 0002 [ 61.020070] R10: 0008 R11: 0246 R12: [ 61.020070] R13: R14: 7f753bba49c0 R15: 55c68ee809a0 [ 61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01 [ 61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0 [ 61.020070] CR2: 56b8 [ 61.020070] ---[ end trace ab52be3a09d557f5 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packa
[Kernel-packages] [Bug 1882802] [NEW] Focal update: v5.4.45 upstream stable release
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: v5.4.45 upstream stable release from git://git.kernel.org/ Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race window" mm: Fix mremap not considering huge pmd devmap HID: sony: Fix for broken buttons on DS3 USB dongles HID: multitouch: enable multi-input as a quirk for some devices HID: i2c-hid: add Schneider SCL142ALM to descriptor override p54usb: add AirVasT USB stick device-id mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter kernel/relay.c: handle alloc_percpu returning NULL in relay_open mmc: fix compilation of user API media: Revert "staging: imgu: Address a compiler warning on alignment" media: staging: ipu3-imgu: Move alignment attribute to field scsi: ufs: Release clock if DMA map fails net: dsa: mt7530: set CPU port to fallback mode airo: Fix read overflows sending packets RDMA/qedr: Fix qpids xarray api used RDMA/qedr: Fix synchronization methods and memory leaks in qedr ARC: Fix ICCM & DCCM runtime size checks ARC: [plat-eznps]: Restrict to CONFIG_ISA_ARCOMPACT evm: Fix RCU list related warnings scsi: pm: Balance pm_only counter of request queue during system resume i2c: altera: Fix race between xfer_msg and isr thread io_uring: initialize ctx->sqo_wait earlier x86/mmiotrace: Use cpumask_available() for cpumask_var_t variables net: bmac: Fix read of MAC address from ROM drm/edid: Add Oculus Rift S to non-desktop list s390/mm: fix set_huge_pte_at() for empty ptes null_blk: return error for invalid zone size net/ethernet/freescale: rework quiesce/activate for ucc_geth net: ethernet: stmmac: Enable interface clocks on probe for IPQ806x selftests: mlxsw: qos_mc_aware: Specify arping timeout as an integer net: smsc911x: Fix runtime PM imbalance on error Linux 5.4.45 UBUNTU: upstream stable to v5.4.45 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.45 upstream stable release + from git://git.kernel.org/ -v5.4.45 upstream stable release -from git://git.kernel.org/ + Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race window" + mm: Fix mremap not considering huge pmd devmap + HID: sony: Fix for broken buttons on DS3 USB dongles + HID: multitouch: enable multi-input as a quirk for some devices + HID: i2c-hid: add Schneider SCL142ALM to descriptor override + p54usb: add AirVasT USB stick device-id + mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter + kernel/relay.c: handle alloc_percpu returning NULL in relay_open + mmc: fix compilation of user API + media: Revert "staging: imgu: Address a compiler warning on alignment" + media: staging: ipu3-imgu: Move alignment attribute to field + scsi: ufs: Release clock if DMA map fails + net: dsa: mt7530: set CPU port to fallback mode + airo: Fix read overflows sending packets + RDMA/qedr: Fix qpids xarray api used + RDMA/qedr: Fix synchronization methods and memory leaks in qedr + ARC: Fix ICCM & DCCM runtime size checks + ARC: [plat-eznps]: Restrict to CONFIG_ISA_AR
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
I don't see a null pointer message but the b44 driver is still broken in 5.4.0-33-generic on my Dell Inspiron 6400: [ 3148.539194] ssb: Found chip with id 0x4401, rev 0x02 and package 0x00 [ 3148.599317] b44 :03:00.0: Sonics Silicon Backplane found on PCI device :03:00.0 [ 3148.599414] b44: Broadcom 44xx/47xx 10/100 PCI ethernet driver version 2.0 [ 3148.627839] b44 ssb1:0 eth0: Broadcom 44xx/47xx 10/100 PCI ethernet driver 00:15:c5:b3:8a:ba [ 3148.684246] swiotlb_tbl_map_single: 14 callbacks suppressed [ 3148.684251] b44 :03:00.0: swiotlb buffer is full (sz: 1566 bytes), total 0 (slots), used 0 (slots) [ 3148.684261] [ cut here ] [ 3148.684267] WARNING: CPU: 0 PID: 36638 at kernel/dma/direct.c:35 report_addr+0x37/0x60 [ 3148.684268] Modules linked in: b44 mii iptable_filter bpfilter ccm b43 dell_laptop dell_smm_hwmon snd_hda_codec_hdmi cordic kvm snd_hda_codec_idt snd_hda_codec_generic bcma ledtrig_audio radeon dell_wmi snd_hda_intel snd_intel_dspcfg dell_smbios dcdbas input_leds joydev mac80211 snd_hda_codec r852 sparse_keymap wmi_bmof serio_raw dell_wmi_descriptor ttm sm_common snd_hda_core nand snd_hwdep drm_kms_helper nand_ecc snd_pcm cfg80211 bch i2c_algo_bit snd_timer fb_sys_fops r592 nandcore mtd memstick syscopyarea sysfillrect snd libarc4 sysimgblt soundcore mac_hid sch_fq_codel coretemp parport_pc ppdev lp parport drm ip_tables x_tables autofs4 ssb_hcd gpio_ich pata_acpi i2c_i801 psmouse lpc_ich firewire_ohci sdhci_pci cqhci firewire_core sdhci crc_itu_t ssb wmi video [ 3148.684314] CPU: 0 PID: 36638 Comm: NetworkManager Not tainted 5.4.0-33-generic #37-Ubuntu [ 3148.684315] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 [ 3148.684318] RIP: 0010:report_addr+0x37/0x60 [ 3148.684320] Code: 48 8b 87 28 02 00 00 48 89 75 f8 48 85 c0 74 2a 4c 8b 00 b8 fe ff ff ff 49 39 c0 76 11 80 3d db c3 71 01 00 0f 84 7d 07 00 00 <0f> 0b c9 c3 48 83 bf 38 02 00 00 00 74 f2 eb e3 80 3d bf c3 71 01 [ 3148.684321] RSP: 0018:9ae68055b450 EFLAGS: 00010246 [ 3148.684323] RAX: fffe RBX: RCX: [ 3148.684324] RDX: 061e RSI: 6b440a80 RDI: 8cb34b4db0b0 [ 3148.684325] RBP: 9ae68055b458 R08: 3fff R09: 0004 [ 3148.684327] R10: R11: 0001 R12: 8cb2f8b0c000 [ 3148.684328] R13: 061e R14: 8cb2f45cef00 R15: 8cb2f96ac8c0 [ 3148.684330] FS: 7f02e05ca240() GS:8cb34c60() knlGS: [ 3148.684331] CS: 0010 DS: ES: CR0: 80050033 [ 3148.684333] CR2: 7f5935e43f28 CR3: c6128000 CR4: 06f0 [ 3148.684334] Call Trace: [ 3148.684340] dma_direct_map_page+0xdc/0xf0 [ 3148.684347] b44_alloc_rx_skb+0x1bb/0x4a0 [b44] [ 3148.684348] ? dma_direct_alloc_pages+0x93/0x130 [ 3148.684351] b44_init_rings+0xb8/0x190 [b44] [ 3148.684354] b44_open+0xfc/0x470 [b44] [ 3148.684357] __dev_open+0xd4/0x170 [ 3148.684359] __dev_change_flags+0x191/0x1f0 [ 3148.684361] dev_change_flags+0x26/0x60 [ 3148.684364] do_setlink+0x82e/0x980 [ 3148.684368] ? cpumask_next+0x1b/0x20 [ 3148.684371] ? __snmp6_fill_stats64.isra.0+0xe7/0x110 [ 3148.684375] ? __nla_validate_parse+0x42/0x140 [ 3148.684377] __rtnl_newlink+0x580/0x970 [ 3148.684380] ? __nla_put+0x20/0x30 [ 3148.684383] ? __kmalloc_node_track_caller+0x205/0x320 [ 3148.684385] ? pskb_expand_head+0x75/0x2d0 [ 3148.684387] ? __kmalloc_reserve.isra.0+0x31/0x90 [ 3148.684391] ? security_sock_rcv_skb+0x2f/0x50 [ 3148.684393] ? sk_filter_trim_cap+0x48/0x220 [ 3148.684395] ? skb_queue_tail+0x43/0x50 [ 3148.684397] ? __netlink_sendskb+0x42/0x50 [ 3148.684401] ? security_capable+0x3d/0x60 [ 3148.684404] ? _cond_resched+0x19/0x30 [ 3148.684406] ? kmem_cache_alloc_trace+0x16c/0x240 [ 3148.684408] rtnl_newlink+0x49/0x70 [ 3148.684410] rtnetlink_rcv_msg+0x2c0/0x380 [ 3148.684413] ? vsnprintf+0x35d/0x4e0 [ 3148.684414] ? rtnl_calcit.isra.0+0x100/0x100 [ 3148.684416] netlink_rcv_skb+0x50/0x120 [ 3148.684418] rtnetlink_rcv+0x15/0x20 [ 3148.684420] netlink_unicast+0x187/0x220 [ 3148.684422] netlink_sendmsg+0x222/0x3e0 [ 3148.684425] sock_sendmsg+0x65/0x70 [ 3148.684426] sys_sendmsg+0x212/0x280 [ 3148.684429] ___sys_sendmsg+0x88/0xd0 [ 3148.684431] ? rtnl_unlock+0xe/0x10 [ 3148.684433] ? addrconf_sysctl_forward+0x111/0x280 [ 3148.684436] ? get_max_files+0x20/0x20 [ 3148.684439] ? __fget_light+0x57/0x70 [ 3148.684441] __sys_sendmsg+0x5c/0xa0 [ 3148.68] __x64_sys_sendmsg+0x1f/0x30 [ 3148.684447] do_syscall_64+0x57/0x190 [ 3148.684450] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3148.684452] RIP: 0033:0x7f02e1a3b12d [ 3148.684454] Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 ca ee ff ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 48 89 44 24 08 e8 fe ee ff ff 48 [ 3148.684455] RSP: 002b:7fffaac61a40 EFLAGS:
[Kernel-packages] [Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
Since the system is upgraded from 16.04, have you tried any older kernel? This could be a regression. Also, please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.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/1871143 Title: Kernel crash during USB device enumeration or mounting Status in linux package in Ubuntu: Incomplete Bug description: Device is an Adafruit microcontroller board running https://github.com/adafruit/circuitpython, using the TinyUSB USB stack: https://github.com/hathach/tinyusb. Device presents a composite USB device that includes MSC, CDC, HID, and MIDI Device was commanded to forcibly reformat its MSC FAT12 filesystem and then reset, which causes a USB reset and re-enumeration. This causes some USB kernel code to crash, much of the time, though not quite all the time. I work for Adafruit and the maintainer of TinyUSB also works for Adafruit, so we can provide further help to track this down. Attached is the dmesg file for the crash. I tried uploading the dump file from kdump, but launchpad is timing out. The dump file is available at: https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halbert1857 F pulseaudio /dev/snd/controlC2: halbert1857 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Apr 6 11:09:43 2020 HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85 InstallationDate: Installed on 2017-09-19 (929 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850744] Re: amdgpu_device_ip_resume_phase2 errors
I haven't experienced this hang since 2020-01-12 (as far back as my logs go), so I think the upstream fix probably made it into the 19.10 and 20.04 kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850744 Title: amdgpu_device_ip_resume_phase2 errors Status in linux package in Ubuntu: Confirmed Bug description: I am using a Radeon RX 580. This setup was stable with Ubuntu 19.04. Since upgrading to 19.10 it's failed to resume from S3 sleep 3 times out of 15. The console will be unresponsive, but the machine is still accessible over the network. Here are some of the errors from dmesg (the second block happened on two boots). Complete kernel logs from all three boots are attached. -- amdgpu :07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110) [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110 PM: Device :07:00.0 failed to resume async: error -110 -- amdgpu :07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110). PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110 PM: Device :07:00.0 failed to resume async: error -110 -- The kernel is based on the Ubuntu-5.3.0-20.21 tag of the eoan kernel repo with the below listed patches applied. [v2,1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 70h [v2,2/2] hwmon/k10temp: Add support for AMD family 17h, model 70h CPUs https://patchwork.kernel.org/patch/11053205/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: kai3355 F pulseaudio /dev/snd/controlC1: kai3355 F pulseaudio /dev/snd/controlC2: kai3355 F pulseaudio /dev/snd/controlC0: kai3355 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 23:21:52 2019 InstallationDate: Installed on 2019-06-18 (135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. enp5s0no wireless extensions. lxdbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend 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.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881338] Re: linux-azure: Update SGX version to version LD_1.33
https://lists.ubuntu.com/archives/kernel-team/2020-June/110932.html -- 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/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure source package in Eoan: New Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: New Status in linux-azure-4.15 source package in Focal: Invalid Bug description: We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882818] [NEW] kernel panic when running `blkid -o full` on eoan
Public bug reported: In the curtin integration tests, we have seen this kernel panic in the last of our three daily runs (unfortunately we don't have history before that): [ 94.443649] cloud-init[1011]: Running command ['blkid', '-o', 'full'] with allowed return codes [0] (capture=True) [ 244.975645] INFO: task blkid:4126 blocked for more than 120 seconds. [ 244.976904] Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 244.977997] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 244.979367] blkid D0 4126 2165 0x4000 [ 244.980331] Call Trace: [ 244.980810] __schedule+0x2b9/0x6c0 [ 244.981384] ? __switch_to_asm+0x40/0x70 [ 244.982038] ? __switch_to_asm+0x40/0x70 [ 244.982766] schedule+0x42/0xb0 [ 244.983284] schedule_timeout+0x203/0x2f0 [ 244.983977] wait_for_completion+0xb1/0x120 [ 244.984696] ? wake_up_q+0x70/0x70 [ 244.985272] __floppy_read_block_0+0x140/0x190 [floppy] [ 244.986115] ? floppy_cmos_show+0x30/0x30 [floppy] [ 244.986951] floppy_revalidate+0xfc/0x240 [floppy] [ 244.987773] check_disk_change+0x62/0x70 [ 244.988438] floppy_open+0x28e/0x360 [floppy] [ 244.989154] ? disk_block_events+0x5c/0x80 [ 244.989823] __blkdev_get+0xe1/0x550 [ 244.990443] blkdev_get+0x3d/0x140 [ 244.991026] ? blkdev_get_by_dev+0x50/0x50 [ 244.991711] blkdev_open+0x97/0xf0 [ 244.992305] do_dentry_open+0x143/0x3a0 [ 244.992934] vfs_open+0x2d/0x30 [ 244.993485] do_last+0x194/0x8f0 [ 244.994014] path_openat+0x8d/0x270 [ 244.994632] do_filp_open+0x91/0x100 [ 244.995231] ? __alloc_fd+0x46/0x150 [ 244.995847] do_sys_open+0x17e/0x290 [ 244.996457] __x64_sys_openat+0x20/0x30 [ 244.997091] do_syscall_64+0x5a/0x130 [ 244.997691] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 244.998552] RIP: 0033:0x7f9eb1c71fdb [ 244.999162] Code: Bad RIP value. [ 244.999708] RSP: 002b:7b8305e0 EFLAGS: 0246 ORIG_RAX: 0101 [ 245.000985] RAX: ffda RBX: 55e7daa0c500 RCX: 7f9eb1c71fdb [ 245.002139] RDX: 0008 RSI: 55e7daa0d680 RDI: ff9c [ 245.003332] RBP: 55e7daa0d680 R08: R09: 7f9eb1d4bc10 [ 245.004486] R10: R11: 0246 R12: 0008 [ 245.005660] R13: 7f9eb1da83c4 R14: dededefa R15: [ 245.006859] NMI backtrace for cpu 1 [ 245.007430] CPU: 1 PID: 25 Comm: khungtaskd Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 245.008870] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 245.010326] Call Trace: [ 245.010794] dump_stack+0x6d/0x9a [ 245.011344] ? lapic_can_unplug_cpu.cold+0x40/0x40 [ 245.012151] nmi_cpu_backtrace.cold+0x14/0x53 [ 245.012856] nmi_trigger_cpumask_backtrace+0xe8/0xea [ 245.013657] arch_trigger_cpumask_backtrace+0x19/0x20 [ 245.014552] watchdog+0x32e/0x390 [ 245.015111] kthread+0x104/0x140 [ 245.015638] ? hungtask_pm_notify+0x40/0x40 [ 245.016316] ? kthread_park+0x80/0x80 [ 245.016911] ret_from_fork+0x35/0x40 [ 245.017527] Sending NMI from CPU 1 to CPUs 0: [ 245.018311] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0x10 [ 245.019262] Kernel panic - not syncing: hung_task: blocked tasks [ 245.020616] CPU: 1 PID: 25 Comm: khungtaskd Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 245.022109] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 245.023603] Call Trace: [ 245.024021] dump_stack+0x6d/0x9a [ 245.024554] panic+0x101/0x2d7 [ 245.025070] watchdog+0x33a/0x390 [ 245.025616] kthread+0x104/0x140 [ 245.026135] ? hungtask_pm_notify+0x40/0x40 [ 245.026851] ? kthread_park+0x80/0x80 [ 245.027470] ret_from_fork+0x35/0x40 [ 245.028131] Kernel Offset: 0x20e0 from 0x8100 (relocation range: 0x8000-0xbfff) ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1882818 Title: kernel panic when running `blkid -o full` on eoan Status in linux-meta package in Ubuntu: New Bug description: In the curtin integration tests, we have seen this kernel panic in the last of our three daily runs (unfortunately we don't have history before that): [ 94.443649] cloud-init[1011]: Running command ['blkid', '-o', 'full'] with allowed return codes [0] (capture=True) [ 244.975645] INFO: task blkid:4126 blocked for more than 120 seconds. [ 244.976904] Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 244.977997] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 244.979367] blkid D0 4126 2165 0x4000 [ 244.980331] Call Trace: [ 244.980810] __schedule+0x2b9/0x6c0 [ 244.981384] ? __switch_to_asm+0x40/0x
[Kernel-packages] [Bug 1881338] Re: linux-azure: Update SGX version to version LD_1.33
** Description changed: + [Impact] + We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux + + [Test Case] + + - Install the new kernel on an ACC azure instance. + - Ensure the module loads properly. + - Check if ECL (provided on the azure images) is working properly. + + [Regression Potential] + + The changes are extensive, but both Canonical and Microsoft perform + validation tests on SGX. Besides that, the change is restricted to + linux-azure running on specific instances. -- 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/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure source package in Eoan: New Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: New Status in linux-azure-4.15 source package in Focal: Invalid Bug description: [Impact] We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux [Test Case] - Install the new kernel on an ACC azure instance. - Ensure the module loads properly. - Check if ECL (provided on the azure images) is working properly. [Regression Potential] The changes are extensive, but both Canonical and Microsoft perform validation tests on SGX. Besides that, the change is restricted to linux-azure running on specific instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Hello Wittawat, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:r
[Kernel-packages] [Bug 1836858] Re: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background
Just throwing this into the ring... try replacing $vt_handoff in the grub kernel line with vt.handoff=1 (from 18.04 to 20.04 it seems to have been changed from 1 to 7 to make the handoff to plymouth more fluid as it loads its own copy of the firmware splash to draw on). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836858 Title: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background Status in Plymouth: Unknown Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: I am trying flickerfree boot in 19.10 [1], but find it actually flickers part way through: 1. BIOS logo on a black background. 2. Display mode resets, no image on a black background briefly. 3. BIOS logo on a black background. The flicker occurs seemingly during kernel startup since my peripherals are lit up before the problem occurs. Suspecting this might be related to FB handover: [2.751028] fb0: switching to inteldrmfb from EFI VGA I tried disabling that with a big hammer: i915.modeset=0 so it stays in efifb, and that works -- no more flickering, providing I don't let i915 take over the framebuffer. [1] https://discourse.ubuntu.com/t/testing-flickerfree-boot/11854 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 17 16:34:36 2019 InstallationDate: Installed on 2019-05-02 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) MachineType: LENOVO 10M7CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=9bfb5f01-bdd4-4854-bfce-1c28e2f2f3bc ro quiet splash i915.fastboot=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M16KT47A dmi.board.name: 3102 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259627060530 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710s dmi.product.name: 10M7CTO1WW dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s dmi.product.version: ThinkCentre M710s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1836858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
I was able to reproduce the problem after a few tries with the 5.7.0-050700-generic kernel. I then started trying older kernels. It appears the problem started somewhere between 4.10.0 an 4.18.0. But sometimes it takes several tries to reproduce, so I'll continue some ad- hoc bisecting to see if I can narrow it down. For posterity, here is how I'm reproducing. It may take several tries, but it seems to happen about 1/3 of the time. I don't expect you to need to follow all of this for now: Using CircuitPython 5.3.0 on Adafruit Metro M0 board. Connect to REPL and do: >>> import storage >>> storage.erase_filesystem() can cause an immediate kernel crash, or it might be delayed by several seconds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871143 Title: Kernel crash during USB device enumeration or mounting Status in linux package in Ubuntu: Incomplete Bug description: Device is an Adafruit microcontroller board running https://github.com/adafruit/circuitpython, using the TinyUSB USB stack: https://github.com/hathach/tinyusb. Device presents a composite USB device that includes MSC, CDC, HID, and MIDI Device was commanded to forcibly reformat its MSC FAT12 filesystem and then reset, which causes a USB reset and re-enumeration. This causes some USB kernel code to crash, much of the time, though not quite all the time. I work for Adafruit and the maintainer of TinyUSB also works for Adafruit, so we can provide further help to track this down. Attached is the dmesg file for the crash. I tried uploading the dump file from kdump, but launchpad is timing out. The dump file is available at: https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halbert1857 F pulseaudio /dev/snd/controlC2: halbert1857 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Apr 6 11:09:43 2020 HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85 InstallationDate: Installed on 2017-09-19 (929 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876089] Re: Kernel NULL pointer dereference
Oke i tried, to get something that makes sense. But the system basically goes completely random in failures, sometimes green screen only fixable by enabling proprietary driver and then disabling. _If_ i get to a gui login it fails between seconds to minutes crashing apps left and right even background daemons failing randomly. After some digging it turns out that my model TU116 may not yet be properly supported. https://nouveau.freedesktop.org/wiki/CodeNames/#nv160familyturing https://nouveau.freedesktop.org/wiki/FeatureMatrix/ I would recommend that the kernel does not attempt to load the nouveau driver for NV140/NV160 at all since they are not supported. it's imo better to have a crappy low res display by default, then completely random behavior. And the low res can be fixed by enabling the proprietary driver. It may also be best to have the ubuntu installer of the next point release automatically install and activate the nvidia proprietary driver for these models so new users don't get a low res display by default. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876089 Title: Kernel NULL pointer dereference Status in linux package in Ubuntu: Incomplete Bug description: Firefox got stuck opening a page and i was unable to dismiss the application in any way. I attempted to kill through the standard force quit oupup that gnome gives. I attempted to kill through the system monitor to suspend, kill, end etc. the process nothing worked. it was keeping one core 100% load. Checking the logs i found something off in the _kern.log_ see attachment. 'lsb_release -rd': Description: Ubuntu 20.04 LTS Release: 20.04 'uname -a': Linux dust 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthijs 1964 F pulseaudio /dev/snd/controlC1: matthijs 1964 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 RfKill: Tags: wayland-session focal Uname: Linux 5.4.0-28-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: 05/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F31 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF31:bd05/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882831] [NEW] Eoan update: upstream stable patchset 2020-06-09
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 2020-06-09 Ported from the following upstream stable releases: v4.19.126, v5.4.44 from git://git.kernel.org/ ax25: fix setsockopt(SO_BINDTODEVICE) dpaa_eth: fix usage as DSA master, try 3 net: dsa: mt7530: fix roaming from DSA user ports __netif_receive_skb_core: pass skb by reference net: inet_csk: Fix so_reuseport bind-address cache in tb->fast* net: ipip: fix wrong address family in init error path net/mlx5: Add command entry handling completion net: qrtr: Fix passing invalid reference to qrtr_local_enqueue() net: revert "net: get rid of an signed integer overflow in ip_idents_reserve()" net sched: fix reporting the first-time use timestamp r8152: support additional Microsoft Surface Ethernet Adapter variant sctp: Don't add the shutdown timer if its already been added sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and socket is closed net/mlx5e: Update netdev txq on completions during closure net/mlx5: Annotate mutex destroy for root ns net: sun: fix missing release regions in cas_init_one(). net/mlx4_core: fix a memory leak bug. mlxsw: spectrum: Fix use-after-free of split/unsplit/type_set in case reload fails ARM: dts: rockchip: fix phy nodename for rk3228-evb arm64: dts: rockchip: fix status for &gmac2phy in rk3328-evb.dts arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node ARM: dts: rockchip: swap clock-names of gpu nodes ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi gpio: tegra: mask GPIO IRQs during IRQ shutdown ALSA: usb-audio: add mapping for ASRock TRX40 Creator net: microchip: encx24j600: add missed kthread_stop gfs2: move privileged user check to gfs2_quota_lock_check cachefiles: Fix race between read_waiter and read_copier involving op->to_do usb: dwc3: pci: Enable extcon driver for Intel Merrifield usb: gadget: legacy: fix redundant initialization warnings net: freescale: select CONFIG_FIXED_PHY where needed IB/i40iw: Remove bogus call to netdev_master_upper_dev_get() riscv: stacktrace: Fix undefined reference to `walk_stackframe' cifs: Fix null pointer check in cifs_read samples: bpf: Fix build error Input: usbtouchscreen - add support for BonXeon TP Input: evdev - call input_flush_device() on release(), not flush() Input: xpad - add custom init packet for Xbox One S controllers Input: dlink-dir685-touchkeys - fix a typo in driver name Input: i8042 - add ThinkPad S230u to i8042 reset list Input: synaptics-rmi4 - really fix attn_data use-after-free Input: synaptics-rmi4 - fix error return code in rmi_driver_probe() ARM: 8970/1: decompressor: increase tag size ARM: uaccess: consolidate uaccess asm to asm/uaccess-asm.h ARM: uaccess: integrate uaccess_save and uaccess_restore ARM: uaccess: fix DACR mismatch with nested exceptions gpio: exar: Fix bad handling for ida_simple_get error path IB/qib: Call kobject_put() when kobject_init_and_add() fails ARM: dts/imx6q-bx50v3: Set display interface clock parents ARM: dts: bcm2835-rpi-zero-w: Fix led polarity ARM: dts: bcm: HR2: Fix PPI interrupt types mmc: block: Fix use-after-free issue for rpmb RDMA/pvrdma: Fix missing pci disable in pvrdma_pci_probe() ALSA: hwdep: fix a left shifting 1 by 31 UB bug ALSA: hda/realtek - Add a model for Thinkpad T570 without DAC workaround ALSA: usb-audio: mixer: volume quirk for ESS Technology Asus USB DAC exec: Always set cap_ambient in cap_bprm_set_creds ALSA: usb-audio: Quirks for Gigabyte TRX40 Aorus Master onboard audio ALSA: hda/realtek - Add new codec supported for ALC287 libceph: ignore pool overlay and cache logic on redirects IB/ipoib: Fix double free of skb in case of multicast traffic in CM mode mm: remove VM_BUG_ON(PageSlab()) from page_mapcount() fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info() include/asm-generic/topology.h: guard cpumask_of_node() macro argument iommu: Fix reference count leak in iommu_group_alloc. parisc: Fix kernel panic in mem_init() RDMA/core: Fix double destruction of uobject mac80211: mesh: fix discovery timer re-arming issue / crash x86/dma: Fix max PFN arithmetic overflow on 32 bit systems copy_xstate_to_kernel(): don't leave parts of destination uninitialized xfrm: allow to accept packets with ipv6 NEXTHDR_HOP in xfrm_input xfrm: call xfrm_output_gso when inner_protocol is set in xfrm_output xfrm interface: fix oops when deleting a x-netns interface xfrm: fix a warning in xfrm_policy_insert_list xfrm: fix a NULL-ptr deref in xfrm_local_error xfrm:
[Kernel-packages] [Bug 1882834] [NEW] vmxnet3: update to latest ToT
Public bug reported: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882834 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: New Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882834] 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 1882834 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/1882834 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: Incomplete Bug description: This request is to port vmxnet3 patches to Ubuntu kernel. Below are the commits in order: vmxnet3: prepare for version 4 changes https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1 vmxnet3: add support to get/set rx flow hash https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d3a8a9e5c3b334d443e97daa59bb95c0b69f4794 vmxnet3: add geneve and vxlan tunnel offload support https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dacce2be33124df3c71f979ac47e3d6354a41125 vmxnet3: update to version 4 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=a31135e36eccd0d16e500d3041f23c3ece62096f vmxnet3: use correct hdr reference when packet is encapsulated https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=36432797641ff0013be9252eecf7ad1ba73171a2 vmxnet3: allow rx flow hash ops only when rss is enabled https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=11e877b2a8cfd282a1b81f9d4c594b900889a5d8 This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you apply these patches to ongoing releases? Also, could you help verify if the below commits are present in vmxnet3 of ubuntu kernel? If not, then please apply these patches before above ones. vmxnet3: set the DMA mask before the first DMA map operation https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=61aeecea40afb2b89933e27cd4adb10fc2e75cfd vmxnet3: use DMA memory barriers where required https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=f3002c1374fb2367c9d8dbb28852791ef90d2bac vmxnet3: turn off lro when rxcsum is disabled https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/drivers/net/vmxnet3?id=3dd7400b419409b1551f7f01764b1f3160feda90 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882818] Re: kernel panic when running `blkid -o full` on eoan
*** This bug is a duplicate of bug 1825413 *** https://bugs.launchpad.net/bugs/1825413 ** This bug has been marked a duplicate of bug 1825413 mdadm, mkfs, other io commands hang, stuck task, bad rip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1882818 Title: kernel panic when running `blkid -o full` on eoan Status in linux-meta package in Ubuntu: New Bug description: In the curtin integration tests, we have seen this kernel panic in the last of our three daily runs (unfortunately we don't have history before that): [ 94.443649] cloud-init[1011]: Running command ['blkid', '-o', 'full'] with allowed return codes [0] (capture=True) [ 244.975645] INFO: task blkid:4126 blocked for more than 120 seconds. [ 244.976904] Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 244.977997] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 244.979367] blkid D0 4126 2165 0x4000 [ 244.980331] Call Trace: [ 244.980810] __schedule+0x2b9/0x6c0 [ 244.981384] ? __switch_to_asm+0x40/0x70 [ 244.982038] ? __switch_to_asm+0x40/0x70 [ 244.982766] schedule+0x42/0xb0 [ 244.983284] schedule_timeout+0x203/0x2f0 [ 244.983977] wait_for_completion+0xb1/0x120 [ 244.984696] ? wake_up_q+0x70/0x70 [ 244.985272] __floppy_read_block_0+0x140/0x190 [floppy] [ 244.986115] ? floppy_cmos_show+0x30/0x30 [floppy] [ 244.986951] floppy_revalidate+0xfc/0x240 [floppy] [ 244.987773] check_disk_change+0x62/0x70 [ 244.988438] floppy_open+0x28e/0x360 [floppy] [ 244.989154] ? disk_block_events+0x5c/0x80 [ 244.989823] __blkdev_get+0xe1/0x550 [ 244.990443] blkdev_get+0x3d/0x140 [ 244.991026] ? blkdev_get_by_dev+0x50/0x50 [ 244.991711] blkdev_open+0x97/0xf0 [ 244.992305] do_dentry_open+0x143/0x3a0 [ 244.992934] vfs_open+0x2d/0x30 [ 244.993485] do_last+0x194/0x8f0 [ 244.994014] path_openat+0x8d/0x270 [ 244.994632] do_filp_open+0x91/0x100 [ 244.995231] ? __alloc_fd+0x46/0x150 [ 244.995847] do_sys_open+0x17e/0x290 [ 244.996457] __x64_sys_openat+0x20/0x30 [ 244.997091] do_syscall_64+0x5a/0x130 [ 244.997691] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 244.998552] RIP: 0033:0x7f9eb1c71fdb [ 244.999162] Code: Bad RIP value. [ 244.999708] RSP: 002b:7b8305e0 EFLAGS: 0246 ORIG_RAX: 0101 [ 245.000985] RAX: ffda RBX: 55e7daa0c500 RCX: 7f9eb1c71fdb [ 245.002139] RDX: 0008 RSI: 55e7daa0d680 RDI: ff9c [ 245.003332] RBP: 55e7daa0d680 R08: R09: 7f9eb1d4bc10 [ 245.004486] R10: R11: 0246 R12: 0008 [ 245.005660] R13: 7f9eb1da83c4 R14: dededefa R15: [ 245.006859] NMI backtrace for cpu 1 [ 245.007430] CPU: 1 PID: 25 Comm: khungtaskd Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 245.008870] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 245.010326] Call Trace: [ 245.010794] dump_stack+0x6d/0x9a [ 245.011344] ? lapic_can_unplug_cpu.cold+0x40/0x40 [ 245.012151] nmi_cpu_backtrace.cold+0x14/0x53 [ 245.012856] nmi_trigger_cpumask_backtrace+0xe8/0xea [ 245.013657] arch_trigger_cpumask_backtrace+0x19/0x20 [ 245.014552] watchdog+0x32e/0x390 [ 245.015111] kthread+0x104/0x140 [ 245.015638] ? hungtask_pm_notify+0x40/0x40 [ 245.016316] ? kthread_park+0x80/0x80 [ 245.016911] ret_from_fork+0x35/0x40 [ 245.017527] Sending NMI from CPU 1 to CPUs 0: [ 245.018311] NMI backtrace for cpu 0 skipped: idling at native_safe_halt+0xe/0x10 [ 245.019262] Kernel panic - not syncing: hung_task: blocked tasks [ 245.020616] CPU: 1 PID: 25 Comm: khungtaskd Tainted: P O 5.3.0-55-generic #49-Ubuntu [ 245.022109] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 245.023603] Call Trace: [ 245.024021] dump_stack+0x6d/0x9a [ 245.024554] panic+0x101/0x2d7 [ 245.025070] watchdog+0x33a/0x390 [ 245.025616] kthread+0x104/0x140 [ 245.026135] ? hungtask_pm_notify+0x40/0x40 [ 245.026851] ? kthread_park+0x80/0x80 [ 245.027470] ret_from_fork+0x35/0x40 [ 245.028131] Kernel Offset: 0x20e0 from 0x8100 (relocation range: 0x8000-0xbfff) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1882818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871143] Re: Kernel crash during USB device enumeration or mounting
I'm wrong, I got this to happen on 4.10, which is quite old, so I'm not sure if it's worth going back much further in time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871143 Title: Kernel crash during USB device enumeration or mounting Status in linux package in Ubuntu: Incomplete Bug description: Device is an Adafruit microcontroller board running https://github.com/adafruit/circuitpython, using the TinyUSB USB stack: https://github.com/hathach/tinyusb. Device presents a composite USB device that includes MSC, CDC, HID, and MIDI Device was commanded to forcibly reformat its MSC FAT12 filesystem and then reset, which causes a USB reset and re-enumeration. This causes some USB kernel code to crash, much of the time, though not quite all the time. I work for Adafruit and the maintainer of TinyUSB also works for Adafruit, so we can provide further help to track this down. Attached is the dmesg file for the crash. I tried uploading the dump file from kdump, but launchpad is timing out. The dump file is available at: https://drive.google.com/open?id=1ka3ySSccEMRSmnYgI9X16IndPDmIKTD6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: halbert1857 F pulseaudio /dev/snd/controlC2: halbert1857 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Apr 6 11:09:43 2020 HibernationDevice: RESUME=UUID=55694d39-bafe-45f8-ba05-ea5d54a93a85 InstallationDate: Installed on 2017-09-19 (929 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 7010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=b3868153-c620-4efe-9dfc-8059dc6288a8 ro quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (28 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0WR7PY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd06/28/2018:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0WR7PY:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7010 dmi.product.sku: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881390] Re: amdgpu.dc=0 required for gui display
Yes, I have my gui back without amdgpu.dc=0. Thanks! ** 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/1881390 Title: amdgpu.dc=0 required for gui display Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 18.04 on my system. When I boot, I get a black screen once mode switching happens. Rescue mode (aka nomodeswitch) would bring me to a gui screen correctly. I tried backing off to X.org from Wayland, but that didn't help. I eventually found an obscure post suggesting adding amdgpu.dc=0 to the command line. With this added, I have the GUI I expect. Originally the system worked as expected, but something changed which required this setting. The graphics card is an AMD RX480. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 30 02:26:41 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] [NEW] int3403 thermal INT3403:00
You have been subscribed to a public bug: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- int3403 thermal INT3403:00 https://bugs.launchpad.net/bugs/1882823 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 1881390] 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 1881390 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/1881390 Title: amdgpu.dc=0 required for gui display Status in linux package in Ubuntu: Incomplete Bug description: I have Ubuntu 18.04 on my system. When I boot, I get a black screen once mode switching happens. Rescue mode (aka nomodeswitch) would bring me to a gui screen correctly. I tried backing off to X.org from Wayland, but that didn't help. I eventually found an obscure post suggesting adding amdgpu.dc=0 to the command line. With this added, I have the GUI I expect. Originally the system worked as expected, but something changed which required this setting. The graphics card is an AMD RX480. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic-hwe-18.04 5.3.0.53.110 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 30 02:26:41 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
** Package changed: evince (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870014] Re: task blocked too long
I tested with the latest kernel image I saw, which appears to be 5.7.1: ii linux-image-unsigned-5.7.1-050701-generi 5.7.1-050701.202006071230 amd64 Linux kernel image for version 5.7.1 on 64 bit x86 SMP jlquinn@cerberus:~$ uname -a Linux cerberus 5.7.1-050701-generic #202006071230 SMP Sun Jun 7 12:32:55 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux When I first plug in the device, /dev/video0 appears as expected. I then start vlc and attempt to input from capture device /dev/video0 and audio hw3,0. After several seconds, I get kernel warnings and /dev/video0 disappears. I've attached the segment of kernel log from the time I plug in the capture device to the time things blow up. I've also attached lsusb -v taken after I plug in the device and before I attempt to use it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long Status in linux package in Ubuntu: Incomplete Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0
[Kernel-packages] [Bug 1870014] Re: task blocked too long
** Attachment added: "Log showing kernel failure" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+attachment/5382115/+files/kernel.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long Status in linux package in Ubuntu: Incomplete Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0003 Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX: RBX: 0064 RCX: 7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX: RSI: 7f63da9bd930 RDI: 0064 Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP: R08: R09: Mar 31 23:55:36 cerberus kernel: [50024.968642] R10: R11: 0293 R12: 7f628d4c5fa0 Mar 31 23:55:36 cerberus kernel: [50024.968644] R13: R14: 7f640422d381 R15: 7f63da9bd930 Mar 31 23:55:36 cerberus kernel: [50024.968915] INFO
[Kernel-packages] [Bug 1870014] Re: task blocked too long
** Attachment added: "Taken after I plug in the device" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870014/+attachment/5382114/+files/lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870014 Title: task blocked too long Status in linux package in Ubuntu: Incomplete Bug description: I plugged in the EasyCap device, then started VLC to read from it. Nothing worked, and I saw the following call traces from the kernel: Mar 31 23:48:30 cerberus kernel: [49598.934870] usb 3-6: new full-speed USB device number 41 using xhci_hcd Mar 31 23:48:30 cerberus kernel: [49599.062914] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:30 cerberus kernel: [49599.574905] usb 3-6: device descriptor read/64, error -71 Mar 31 23:48:31 cerberus kernel: [49599.682966] usb usb3-port6: attempt power cycle Mar 31 23:48:32 cerberus kernel: [49600.974908] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946905] usb usb3-port6: Cannot enable. Maybe the USB cable is bad? Mar 31 23:48:33 cerberus kernel: [49601.946975] usb usb3-port6: unable to enumerate USB device Mar 31 23:48:45 cerberus kernel: [49614.418840] usb 3-6: new high-speed USB device number 44 using xhci_hcd Mar 31 23:48:45 cerberus kernel: [49614.570267] usb 3-6: config 1 interface 0 altsetting 1 bulk endpoint 0x83 has invalid maxpa cket 256 Mar 31 23:48:45 cerberus kernel: [49614.573126] usb 3-6: New USB device found, idVendor=1b71, idProduct=3002 Mar 31 23:48:45 cerberus kernel: [49614.573130] usb 3-6: New USB device strings: Mfr=3, Product=4, SerialNumber=2 Mar 31 23:48:45 cerberus kernel: [49614.573132] usb 3-6: Product: usbtv007 Mar 31 23:48:45 cerberus kernel: [49614.573135] usb 3-6: Manufacturer: fushicai Mar 31 23:48:45 cerberus kernel: [49614.573136] usb 3-6: SerialNumber: 3002 Mar 31 23:48:45 cerberus kernel: [49614.574491] usbtv 3-6:1.0: Fushicai USBTV007 Audio-Video Grabber Mar 31 23:52:29 cerberus kernel: [49838.118469] usb 3-6: USB disconnect, device number 44 Mar 31 23:52:44 cerberus kernel: [49853.203903] perf: interrupt took too long (3978 > 3967), lowering kernel.perf_event_max_sam ple_rate to 50250 Mar 31 23:55:36 cerberus kernel: [50024.968505] INFO: task VideoCapture:11251 blocked for more than 120 seconds. Mar 31 23:55:36 cerberus kernel: [50024.968512] Tainted: G IOE 4.15.0-94-generic #95-Ubuntu Mar 31 23:55:36 cerberus kernel: [50024.968514] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Mar 31 23:55:36 cerberus kernel: [50024.968517] VideoCaptureD0 11251 1 0x Mar 31 23:55:36 cerberus kernel: [50024.968521] Call Trace: Mar 31 23:55:36 cerberus kernel: [50024.968535] __schedule+0x24e/0x880 Mar 31 23:55:36 cerberus kernel: [50024.968539] schedule+0x2c/0x80 Mar 31 23:55:36 cerberus kernel: [50024.968542] schedule_preempt_disabled+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968547] __mutex_lock.isra.5+0x276/0x4e0 Mar 31 23:55:36 cerberus kernel: [50024.968551] __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968554] ? __mutex_lock_slowpath+0x13/0x20 Mar 31 23:55:36 cerberus kernel: [50024.968557] mutex_lock+0x2f/0x40 Mar 31 23:55:36 cerberus kernel: [50024.968569] _vb2_fop_release+0x29/0xa0 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968573] vb2_fop_release+0x31/0x40 [videobuf2_v4l2] Mar 31 23:55:36 cerberus kernel: [50024.968593] v4l2_release+0x38/0x80 [videodev] Mar 31 23:55:36 cerberus kernel: [50024.968600] __fput+0xea/0x220 Mar 31 23:55:36 cerberus kernel: [50024.968604] fput+0xe/0x10 Mar 31 23:55:36 cerberus kernel: [50024.968611] task_work_run+0x9d/0xc0 Mar 31 23:55:36 cerberus kernel: [50024.968620] exit_to_usermode_loop+0xc0/0xd0 Mar 31 23:55:36 cerberus kernel: [50024.968623] do_syscall_64+0x121/0x130 Mar 31 23:55:36 cerberus kernel: [50024.968630] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Mar 31 23:55:36 cerberus kernel: [50024.968633] RIP: 0033:0x7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968635] RSP: 002b:7f63da9bd900 EFLAGS: 0293 ORIG_RAX: 0003 Mar 31 23:55:36 cerberus kernel: [50024.968638] RAX: RBX: 0064 RCX: 7f6411c26447 Mar 31 23:55:36 cerberus kernel: [50024.968639] RDX: RSI: 7f63da9bd930 RDI: 0064 Mar 31 23:55:36 cerberus kernel: [50024.968641] RBP: R08: R09: Mar 31 23:55:36 cerberus kernel: [50024.968642] R10: R11: 0293 R12: 7f628d4c5fa0 Mar 31 23:55:36 cerberus kernel: [50024.968644] R13: R14: 7f640422d381 R15: 7f63da9bd930 Mar 31 23:55:36 cerberus kernel: [50024.968915]
[Kernel-packages] [Bug 1881549] Re: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke
Kai, Anthony, François, is anyone wanting to get that uploaded? If so I can help with the that part, note that there is already a SRU in the focal queue so it would need merging if we want to include this change in the next upload -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: BCM43602 [14e4:43ba] Subsystem [1028:0020]: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Invalid Status in wpa package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1438 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-09 (329 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=f73bcd37-31c3-4314-81cf-102bfd94a03e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-21 (12 days ago) UserGroups: adm cdrom dip lpadmin 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/1881549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878897] Re: debian/scripts/file-downloader does not handle positive failures correctly
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
Re: [Kernel-packages] [Bug 1882483] Re: ThinkPad P1 Gen 2 does not boot
Hi, Reinstall did not help. Thank you, Igor uto, 9. lip 2020. u 06:55 AaronMa <1882...@bugs.launchpad.net> napisao je: > >From your dmesg, no nvidia driver is loaded. > > Please try re-install on your expected kernel: > $ sudo apt install --reinstall nvidia-driver-440 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1882483 > > Title: > ThinkPad P1 Gen 2 does not boot > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Hi, > > Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor > plugged. > > Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. > > There is also a separate problem: > No wake up after hibernation, only repeated sound without screen image - > physical shutdown is only workaround I have. > > Thank you, > Igor > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 > ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 > Uname: Linux 5.4.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: igor 2358 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Mon Jun 8 05:37:59 2020 > Dependencies: > > InstallationDate: Installed on 2020-04-01 (67 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) > MachineType: LENOVO 20QTCTO1WW > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic > root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-28-generic N/A >linux-backports-modules-5.4.0-28-generic N/A >linux-firmware1.187 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 01/20/2020 > dmi.bios.vendor: LENOVO > dmi.bios.version: N2OET42W (1.29 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20QTCTO1WW > dmi.board.vendor: LENOVO > dmi.board.version: SDK0R32862 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad P1 Gen 2 > dmi.product.name: 20QTCTO1WW > dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 > dmi.product.version: ThinkPad P1 Gen 2 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882483/+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/1882483 Title: ThinkPad P1 Gen 2 does not boot Status in linux package in Ubuntu: Confirmed Bug description: Hi, Kernels > 5.4.0-28 can not boot Ubuntu 20.04 when *NO* HDMI monitor plugged. Kernels > 5.4.0-28 can boot Ubuntu 20.04 when HDMI monitor plugged. There is also a separate problem: No wake up after hibernation, only repeated sound without screen image - physical shutdown is only workaround I have. Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: igor 2358 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 05:37:59 2020 Dependencies: InstallationDate: Installed on 2020-04-01 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLEN
[Kernel-packages] [Bug 1881072] Re: "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1878897] Re: debian/scripts/file-downloader does not handle positive failures correctly
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12114 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878897 Title: debian/scripts/file-downloader does not handle positive failures correctly Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: Somehow we are not really correctly handling positive failures, 404 for example. Sigh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878897] Re: debian/scripts/file-downloader does not handle positive failures correctly
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1878649] Re: Focal update: v5.4.41 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878649 Title: Focal update: v5.4.41 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.41 upstream stable release from git://git.kernel.org/ USB: serial: qcserial: Add DW5816e support nvme: refactor nvme_identify_ns_descs error handling nvme: fix possible hang when ns scanning fails during error recovery tracing/kprobes: Fix a double initialization typo net: macb: Fix runtime PM refcounting drm/amdgpu: move kfd suspend after ip_suspend_phase1 drm/amdgpu: drop redundant cg/pg ungate on runpm enter vt: fix unicode console freeing with a common interface tty: xilinx_uartps: Fix missing id assignment to the console devlink: fix return value after hitting end in region read dp83640: reverse arguments to list_add_tail fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks ipv6: Use global sernum for dst validation with nexthop objects mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly neigh: send protocol value in neighbor create notification net: dsa: Do not leave DSA master with NULL netdev_ops net: macb: fix an issue about leak related system resources net: macsec: preserve ingress frame ordering net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() net_sched: sch_skbprio: add message validation to skbprio_change() net: stricter validation of untrusted gso packets net: tc35815: Fix phydev supported/advertising mask net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() net/tls: Fix sk_psock refcnt leak when in tls_data_ready() net: usb: qmi_wwan: add support for DW5816e nfp: abm: fix a memory leak bug sch_choke: avoid potential panic in choke_reset() sch_sfq: validate silly quantum values tipc: fix partial topology connection closure tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 bnxt_en: Fix VF anti-spoof filter setup. bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. bnxt_en: Improve AER slot reset. bnxt_en: Return error when allocating zero size context memory. bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). net/mlx5: DR, On creation set CQ's arm_db member to right value net/mlx5: Fix forced completion access non initialized command entry net/mlx5: Fix command entry leak in Internal Error State net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices sctp: Fix bundling of SHUTDOWN with COOKIE-ACK Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" HID: usbhid: Fix race between usbhid_close() and usbhid_stop() HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT USB: uas: add quirk for LaCie 2Big Quadra usb: chipidea: msm: Ensure proper controller reset using role switch API USB: serial: garmin_gps: add sanity checking for data length tracing: Add a vmalloc_sync_mappings() for safe measure crypto: arch/nhpoly1305 - process in explicit 4k chunks KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER KVM: arm64: Fix 32bit PC wrap-around arm64: hugetlb: avoid potential NULL dereference drm: ingenic-drm: add MODULE_DEVICE_TABLE ipc/mqueue.c: change __do_notify() to bypas
[Kernel-packages] [Bug 1877858] Re: Improve TSC refinement (and calibration) reliability
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1878073] Re: Eoan update: upstream stable patchset 2020-05-11
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1878040] Re: Focal update: v5.4.40 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878040 Title: Focal update: v5.4.40 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.40 upstream stable release from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started drm/bridge: analogix_dp: Split bind() into probe() and real bind() ASoC: topology: Check return value of soc_tplg_create_tlv ASoC: topology: Check return value of soc_tplg_*_create ASoC: topology: Check soc_tplg_add_route return value ASoC: topology: Check return value of pcm_new_ver ASoC: topology: Check return value of soc_tplg_dai_config selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling ASoC: topology: Fix endianness issue usb: dwc3: gadget: Properly set maxpacket limit ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry remoteproc: qcom_q6v5_mss: fix a bug in q6v5_probe() drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam for multi-SSI cifs: protect updating server->dstaddr with a spinlock scripts/config: allow colons in option strings for sed cifs: do not share tcons with DFS tracing: Fix memory leaks in trace_events_hist.c lib/mpi: Fix building for powerpc with clang mac80211: sta_info: Add lockdep condition for RCU list usage net: bcmgenet: suppress warnings on failed Rx SKB allocations net: systemport: suppress warnings on failed Rx SKB allocations drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl sctp: Fix SHUTDOWN CTSN Ack in the peer restart case Revert "software node: Simplify software_node_release() function" hexagon: clean up ioremap hexagon: define ioremap_uc ALSA: hda: Match both PCI ID and SSID for driver blacklist x86/kvm: fix a missing-prototypes "vmread_error" platform/x86: GPD pocket fan: Fix error message when temp-limits are out of range ACPI: PM: s2idle: Fix comment in acpi_s2idle_prepare_late() mac80211: add ieee80211_is_any_nullfunc() cgroup, netclassid: remove double cond_resched libbpf: Fix readelf output parsing for Fedora mm/mremap: Add comment explaining the untagging behaviour of mremap() Revert "drm/amd/display: setting the DIG_MODE to the correct value." tools headers UAPI: Sync copy of arm64's asm/unistd.h with the kernel sources udp: document udp_rcv_segment special case for looped packets PM / devfreq: Add missing locking while setting suspend_freq Linux 5.4.40 UBUNTU: upstream stable to v5.4.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876859] Re: Support DMIC micmute LED on HP platforms
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876859 Title: Support DMIC micmute LED on HP platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] DMIC micmute LED on HP platforms doesn't work. [Fix] Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to control micmute. [Test] After applying the fix, micmute LED can correctly indicate the status of micmute. [Regression Potential] Low. For now it only affects one platform, and it doesn't touch any core part of the subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876859/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
This bug was fixed in the package linux - 5.4.0-37.41
---
linux (5.4.0-37.41) focal; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
-- Marcelo Henrique Cerri Wed, 03 Jun
2020 11:24:23 -0300
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12114
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877958
Title:
Do not treat unresolved test case in ftrace from
ubuntu_kernel_selftests as failure
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
== SRU Justification ==
There are some test cases in ftrace from ubuntu_kernel_selftests that
would need some kernel configs to be enabled or have some special HW
requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1
If the requirement was not met, these test will fail with "unresolved"
and return 1. So even these is no failed test case, the ftrace test
will still be marked as "failed" with the presence of unresolved test:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
not ok 1 selftests: ftrace: ftracetest # exit=1
== Fix ==
* b730d668138c ("ftrace/selftest: make unresolved cases cause failure if
--fail-unresolved set")
This patch will only make unresolved test case return 1 if we ask it
to fail with unresolved test case.
It can be cherry-picked to kernels starting from Disco.
For Bionic and Xenial it needs to be backported with some context
adjustment as they're missing some other patches to the testing tool.
== Test ==
With the patch applied, the ftrace test will not be marked as failed
with the presence of unresolved test case:
# # of passed: 28
# # of failed: 0
# # of unresolved: 1
# # of untested: 0
# # of unsupported: 58
# # of xfailed: 0
# # of undefined(test bug): 0
ok 1 selftests: ftrace: ftracetest
== Regression Potential ==
Low, changes limited to testing tools, no actual impacts to our kernels.
The worst case is to cause false negative in test reports, but in that
case it's probably a test case issue since a failed case should be
treated as a failed one, instead of unresolved.
== Original Bug Report ==
There are some test cases in ftrace from ubuntu_kernel_selftests that would
need some kernel configs to be enabled.
bug 1869347
bug 1869349
We should not treat unresolved test case as a failure, as it's
expected to fail with no correlated configs enabeled.
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
#diff-33d74da785cbc5da20f71eb1af106d68
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876971] Re: Eoan update: upstream stable patchset 2020-05-05
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1876767] Re: Focal update: v5.4.38 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876767 Title: Focal update: v5.4.38 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.38 upstream stable release from git://git.kernel.org/ Note: v5.4.38 itself consisted of a single revert (never committed to Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug, really. Linux 5.4.38 UBUNTU: upstream stable to v5.4.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877013] Re: Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877013 Title: Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] Connect HDMI monitor on WD19TB dock and connect WD19TB to Dell XPS 13 9300, toggling the display mode to mirror sometimes got a blank screen on external monitor. [Fix] After bisect kernel and found below commit(from v5.7-rc2) improves the stability bcad588dea53 drm/i915/perf: Do not clear pollin for small user read buffers [Test] Verified on Dell XPS 13 9300 with WD19TB docking station, the fail rate becomes from 1/2 to 1/30 [Regression Potential] Low, this commit has been CC'd to stable, so we will have this soon. [Misc] OEM-5.6 has this commit from v5.6.6 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1877013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877461] Re: Bionic update: upstream stable patchset 2020-05-07
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1877592] Re: Focal update: v5.4.39 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877592 Title: Focal update: v5.4.39 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.39 upstream stable release from git://git.kernel.org/ dma-buf: Fix SET_NAME ioctl uapi drm/edid: Fix off-by-one in DispID DTD pixel clock drm/amd/display: Fix green screen issue after suspend drm/qxl: qxl_release leak in qxl_draw_dirty_fb() drm/qxl: qxl_release leak in qxl_hw_surface_alloc() drm/qxl: qxl_release use after free NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION btrfs: fix transaction leak in btrfs_recover_relocation btrfs: fix block group leak when removing fails btrfs: fix partial loss of prealloc extent past i_size after fsync btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info mmc: cqhci: Avoid false "cqhci: CQE stuck on" by not open-coding timeout loop mmc: sdhci-xenon: fix annoying 1.8V regulator warning mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers mmc: sdhci-msm: Enable host capabilities pertains to R1b response mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY mmc: meson-mx-sdio: remove the broken ->card_busy() op crypto: caam - fix the address of the last entry of S/G ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID ALSA: hda/hdmi: fix without unlocked before return ALSA: line6: Fix POD HD500 audio playback ALSA: pcm: oss: Place the plugin buffer overflow checks correctly i2c: amd-mp2-pci: Fix Oops in amd_mp2_pci_init() error handling Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM dlmfs_file_write(): fix the bogosity in handling non-zero *ppos IB/rdmavt: Always return ERR_PTR from rvt_create_mmap_info() PM: ACPI: Output correct message on target power state PM: hibernate: Freeze kernel threads in software_resume() dm verity fec: fix hash block number in verity_fec_decode dm writecache: fix data corruption when reloading the target dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe scsi: qla2xxx: set UNLOADING before waiting for session deletion scsi: qla2xxx: check UNLOADING before posting async work RDMA/mlx5: Set GRH fields in query QP on RoCE RDMA/mlx4: Initialize ib_spec on the stack RDMA/siw: Fix potential siw_mem refcnt leak in siw_fastreg_mr() RDMA/core: Prevent mixed use of FDs between shared ufiles RDMA/core: Fix race between destroy and release FD object RDMA/cm: Fix ordering of xa_alloc_cyclic() in ib_create_cm_id() RDMA/cm: Fix an error check in cm_alloc_id_priv() i2c: iproc: generate stop event for slave writes vfio: avoid possible overflow in vfio_iommu_type1_pin_pages vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() iommu/qcom: Fix local_base status check scsi: target/iblock: fix WRITE SAME zeroing iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system i2c: aspeed: Avoid i2c interrupt status clear race condition. ALSA: opti9xx: shut up gcc-10 range warning Fix use after free in get_tree_bdev() nvme: prevent double free in nvme_alloc_ns() error handling nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl dmaengine: dmatest: Fix iteration non-stop logic dmaengine: dmatest: Fix process hang when reading 'wait' parameter arm64: vdso: Add -fasynchronous-unwind-tables to cflags selinux: pro
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1877394] Re: Kernel panic due to NULL ringbuffer vaddr dereference in i915
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877394 Title: Kernel panic due to NULL ringbuffer vaddr dereference in i915 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] A sauce fix for a kernel panic in i915 that I frequently experienced was fixed by upstream. [Fix] The sauce patch I made should be dropped in exchange for the proper upstream fix. [Test] I tested the upstream fix and can confirm it fixes the crashes I experienced. [Regression Potential] Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce patch. --- This is what the crash looks like: BUG: unable to handle page fault for address: 3448 RIP: 0010:gen8_emit_flush_render+0x163/0x190 Call Trace: execlists_request_alloc+0x25/0x40 __i915_request_create+0x1f4/0x2c0 i915_request_create+0x71/0xc0 i915_gem_do_execbuffer+0xb98/0x1a80 ? preempt_count_add+0x68/0xa0 ? _raw_spin_lock+0x13/0x30 ? _raw_spin_unlock+0x16/0x30 i915_gem_execbuffer2_ioctl+0x1de/0x3c0 ? i915_gem_busy_ioctl+0x7f/0x1d0 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 drm_ioctl_kernel+0xb2/0x100 drm_ioctl+0x209/0x360 ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 ksys_ioctl+0x87/0xc0 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x4e/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and retire callbacks" but there is an upstream fix for it, "drm/i915/gt: Make intel_ring_unpin() safe for concurrent pint". Let's replace the sauce patch with the upstream fix. More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878256] Re: Bionic update: upstream stable patchset 2020-05-12
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1876361] Re: Focal update: v5.4.36 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876361 Title: Focal update: v5.4.36 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.36 upstream stable release from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files f2fs: fix to avoid memory leakage in f2fs_listxattr net, ip_tunnel: fix interface lookup with no key UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Silence clang warning on mismatched value/register sizes tools/testing/nvdimm: Fix compilation failure without CONFIG_DEV_DAX_PMEM_COMPAT watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login scsi: lpfc: Fix crash after handling a pci error scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG scsi: libfc: If PRLI rejected, move rport to PLOGI state ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement nvme-tcp: fix possible crash in write_zeroes processing scsi: iscsi: Report unbind session event when the target has been removed tools/test/nvdimm: Fix out of tree build ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() nvme: fix deadlock caused by ANA update wrong locking drm/amd/display: Update stream adjust in dc_stream_adjust_vmin_vmax dma-direct: fix data truncation in dma_direct_get_required_mask() kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index kconfig: qconf: Fix a few alignment issues lib/raid6/test: fix build on distros whose /bin/sh is not bash s390/cio: generate delayed uevent for vfio-ccw subchannels s390/cio: avoid duplicated 'ADD' uevents loop: Better discard support for block devices Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" powerpc/pseries: Fix MCE handling on pseries nvme: fix compat address handling in several ioctls pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address drm/amd/display: Calculate scaling ratios on every medium/full update ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet ALSA: usb-audio: Add Pioneer DJ DJM-250MK2 quirk drm/amd/display: Not doing optimize bandwidth if flip pending. cxgb4: fix adapter crash due to wrong MC size cxgb4: fix large delays in PTP synchronization ipv4: Update fib_select_default to handle nexthop objects ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() mlxsw: Fix some IS_ERR() vs NULL bugs net: bcmgenet: correct per TX/RX ring statistics net/mlx4_en: avoid indirect call in TX completion net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net: openvswitch: ovs_ct_exit to be done under ovs_lock net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array net/x25: Fix x25_neigh refcnt leak when receiving frame sched: etf: do not assume all sockets are full blown selftests: F
[Kernel-packages] [Bug 1876765] Re: Focal update: v5.4.37 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876765 Title: Focal update: v5.4.37 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.37 upstream stable release from git://git.kernel.org/ remoteproc: Fix wrong rvring index computation ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans() printk: queue wake_up_klogd irq_work only if per-CPU areas are ready ASoC: stm32: sai: fix sai probe usb: dwc3: gadget: Do link recovery for SS and SSP kbuild: fix DT binding schema rule again to avoid needless rebuilds usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete usb: gadget: udc: atmel: Fix vbus disconnect handling afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH iio:ad7797: Use correct attribute_group propagate_one(): mnt_set_mountpoint() needs mount_lock counter: 104-quad-8: Add lock guards - generic interface s390/ftrace: fix potential crashes when switching tracers ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs ASoC: tas571x: disable regulators on failed probe ASoC: wm8960: Fix wrong clock after suspend & resume drivers: soc: xilinx: fix firmware driver Kconfig dependency nfsd: memory corruption in nfsd4_lock() bpf: Forbid XADD on spilled pointers for unprivileged users i2c: altera: use proper variable to hold errno rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket net/cxgb4: Check the return from t4_query_params properly xfs: acquire superblock freeze protection on eofblocks scans svcrdma: Fix trace point use-after-free race svcrdma: Fix leak of svc_rdma_recv_ctxt objects net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns net/mlx5e: Get the latest values from counters in switchdev mode PCI: Add ACS quirk for Zhaoxin multi-function devices PCI: Make ACS quirk implementations more uniform PCI: Unify ACS quirk desired vs provided checking PCI: Add Zhaoxin Vendor ID PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports PCI: Move Apex Edge TPU class quirk to fix BAR assignment ARM: dts: bcm283x: Disable dsi0 node cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled s390/pci: do not set affinity for floating irqs net/mlx5: Fix failing fw tracer allocation on s390 sched/core: Fix reset-on-fork from RT with uclamp perf/core: fix parent pid/tid in task exit events netfilter: nat: fix error handling upon registering inet hook PM: sleep: core: Switch back to async_schedule_dev() blk-iocost: Fix error on iocost_ioc_vrate_adj um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/ bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension bpf, x86_32: Fix clobbering of dst for BPF_JSET bpf, x86_32: Fix logic error in BPF_LDX zero-extension mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy path xfs: clear PF_MEMALLOC before exiting xfsaild thread bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B libbpf: Initialize *nl_pid so gcc 10 is happy net: fec: set GPR bit on suspend by DT configuration. x86: hyperv: report value of misc_features signal: check sig before setting info in kill_pid_usb_asyncio afs: Fix length of dump of bad YFSFetchStatus record xfs: fix partially uninitialized structure in xfs_reflink_remap_extent ALSA: hda: Release resources at error in delayed probe ALSA: hda: Keep the controller initialization even if no
[Kernel-packages] [Bug 1876885] Re: linux: riscv: set max_pfn to the PFN of the last page
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876885 Title: linux: riscv: set max_pfn to the PFN of the last page Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Bug description: == SRU Justification Focal/Groovy == The current max_pfn equals to zero. In this case, I found it caused users cannot get some page information through /proc such as kpagecount in v5.6 kernel because of new sanity checks. The following message is displayed by stress-ng test suite with the command "stress-ng --verbose --physpage 1 -t 1" on HiFive unleashed board. # stress-ng --verbose --physpage 1 -t 1 stress-ng: debug: [109] 4 processors online, 4 processors configured stress-ng: info: [109] dispatching hogs: 1 physpage stress-ng: debug: [109] cache allocate: reducing cache level from L3 (too high) to L0 stress-ng: debug: [109] get_cpu_cache: invalid cache_level: 0 stress-ng: info: [109] cache allocate: using built-in defaults as no suitable cache found stress-ng: debug: [109] cache allocate: default cache size: 2048K stress-ng: debug: [109] starting stressors stress-ng: debug: [109] 1 stressor spawned stress-ng: debug: [110] stress-ng-physpage: started [110] (instance 0) stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd34de000 in /proc/kpagecount, errno=0 (Success) stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success) ... stress-ng: error: [110] stress-ng-physpage: cannot read page count for address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success) stress-ng: debug: [110] stress-ng-physpage: exited [110] (instance 0) stress-ng: debug: [109] process [110] terminated stress-ng: info: [109] successful run completed in 1.00s # == Fix == Upstream commit in linux-next: commit c749bb2d554825e007cbc43b791f54e124dadfce Author: Vincent Chen Date: Mon Apr 27 14:59:24 2020 +0800 riscv: set max_pfn to the PFN of the last page == Test Case == Without the patch, running stress-ng --verbose --physpage 1 -t 1 on HiFive unleashed board will trip the bug. With the patch, the test passes as follows: # stress-ng --verbose --physpage 1 -t 1 stress-ng: debug: [104] 4 processors online, 4 processors configured stress-ng: info: [104] dispatching hogs: 1 physpage stress-ng: info: [104] cache allocate: using defaults, can't determine cache details from sysfs stress-ng: debug: [104] cache allocate: default cache size: 2048K stress-ng: debug: [104] starting stressors stress-ng: debug: [104] 1 stressor spawned stress-ng: debug: [105] stress-ng-physpage: started [105] (instance 0) stress-ng: debug: [105] stress-ng-physpage: exited [105] (instance 0) stress-ng: debug: [104] process [105] terminated stress-ng: info: [104] successful run completed in 1.01s == Regression Potential == Small, this correctly fixes the max_pfn and max_low_pfn to the correct end of DRAM location. The fix now can be shown to set these appropriately because stress-ng no longer triggers this corner case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876667] Re: Add support for Ambiq micro AM1805 RTC chip
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1876667] Re: Add support for Ambiq micro AM1805 RTC chip
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1876667 Title: Add support for Ambiq micro AM1805 RTC chip Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] To enable Ambiq micro AM1805 RTC chip [Fix] The patch is provided by Eurotech. Eurotech doesn't want to upstream this driver, because there are some functions are used by Eurotech's platforms only. [Test] Verified on Eurotech's machine and it works well. [Regression Potential] Low, it's a standalone file/driver, so no regression could be introduced. [Misc] We only need this driver in Bionic kernel, but for future possible projects, SRU this to Focal kernel, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876699] Re: add 16-bit width registers support for EEPROM at24 device
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876699 Title: add 16-bit width registers support for EEPROM at24 device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Bug description: SRU For Bionic [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] This commit is derivated from below commit, and then modified and provided by customer https://patchwork.ozlabs.org/patch/545292/ Unfortunately, this commit doesn't get into mainline in the end, so I migrate the commit to latest kernel and finally get it merged. https://lkml.org/lkml/2020/4/24/635 [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch only changes the behavior of the device which has AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 24c256. = SRU For Focal [Impact] Larger EEPROM devices that use 16-bit addresses couldn't be accessed. The i2c/smbus currently only support to access data with 8-bit width of address. In some larger device, such as larger EEPROM, it requires to access the address large than 0xff, so it needs to extend address space to 16-bit width. [Fix] Clear cherry pick from linux-next 82f25bd73c0b regmap-i2c: add 16-bit width registers support [Test] Verified on Eurotech's platforms. [Regression Potential] Low, this patch provides new access functions for 16-bit registers, shouldn't affect any other devices which are already working well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-gcp - 5.4.0-1015.15 --- linux-gcp (5.4.0-1015.15) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-gcp (5.4.0-1012.12) focal; urgency=medium * focal/linux-gcp: 5.4.0-1012.12 -proposed tracker (LP: #1878794) * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zone_contiguou
[Kernel-packages] [Bug 1874359] Re: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1869672] Re: Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
This bug was fixed in the package linux - 5.4.0-37.41
---
linux (5.4.0-37.41) focal; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
-- Marcelo Henrique Cerri Wed, 03 Jun
2020 11:24:23 -0300
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* PCI Functions with UIDs >128 are currently not accounted correctly
in the s390x/pci (zPCI) code.
* Furthermore, the code allows that more than CONFIG_PCI_NR_FUNCTIONS
are created.
* This can lead to issues with data structures which were only
allocated for CONFIG_PCI_NR_FUNCTIONS.
[Fix]
* https://launchpadlibrarian.net/478235080/0001-s390-pci-Fix-
zpci_alloc_domain-over-allocation.patch
[Test Case]
* Set the kernel parameter CONFIG_PCI_NR_FUNCTIONS to a specific
(reasonablly low) number.
* And check if more PCI functions can be created than specified by
CONFIG_PCI_NR_FUNCTIONS (e.g. using a RoCE adapter) and watch for
kernel message 'Adding PCI function ... failed'
[Regression Potential]
* There is regression potential can be considered as low, since:
* the zPCI cards are less wide spread than for example ccw adapters on
s390x
* the fix got already upstream accepted in 5.7, hence upstream
reviewed, too
* the modifications span just two files and both are s390x arch
specific
[Other Info]
* the above patch-file is based on commit
969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
zpci_alloc_domain() over allocation"), but this backport was needed
for getting this applied to focal master-next
* and this patch got upstream accepted with kernel v5.7-rc1, hence on
the long term it should be in 'gorilla'
__
PCI Functions with UIDs >128 are currently not accounted correctly in
the s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac
("s390/pci: Fix zpci_alloc_domain() over allocation")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12114 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Fix Released Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14
[Kernel-packages] [Bug 1874359] Re: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver)
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12114 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874359 Title: alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a regression in the asoc machine driver) Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Please apply the fix for #1872569 first, then apply this patch. [Impact] The fix for #1872569 introduces a regression, the driver access a NULL pointer on the machiens without Intel hdmi audio codec. [Fix] pick a fixing patch from alsa/asoc repo, the patch doesn't assume the first rtd is for hda codec, it will look for that rtd through strstr() [Test Case] Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses this driver, the audio could work. disable the intel hdmi audio codec through bios, the analogue audio still works [Regression Risk] Low, I have tested this patch Lenovo / Dell machines, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-oracle - 5.4.0-1015.15 --- linux-oracle (5.4.0-1015.15) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-oracle (5.4.0-1012.12) focal; urgency=medium * focal/linux-oracle: 5.4.0-1012.12 -proposed tracker (LP: #1878796) * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zo
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-azure - 5.4.0-1016.16 --- linux-azure (5.4.0-1016.16) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-azure (5.4.0-1013.13) focal; urgency=medium * focal/linux-azure: 5.4.0-1013.13 -proposed tracker (LP: #1878793) * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667) - SAUCE: rtc: add am-1805 RTC driver * linux-azure: Enable FSGSBASE instructions to support SGX (LP: #1877425) - SAUCE: x86/ptrace: Prevent ptrace from clearing the FS/GS selector - SAUCE: selftests/x86/fsgsbase: Test GS selector on ptracer-induced GS base write - SAUCE: x86/cpu: Add 'unsafe_fsgsbase' to enable CR4.FSGSBASE - SAUCE: x86/entry/64: Clean up paranoid exit - SAUCE: x86/entry/64: Switch CR3 before SWAPGS in paranoid entry - SAUCE: x86/entry/64: Introduce the FIND_PERCPU_BASE macro - SAUCE: x86/entry/64: Handle FSGSBASE enabled paranoid entry/exit - SAUCE: x86/entry/64: Document GSBASE handling in the paranoid path - SAUCE: x86/fsgsbase/64: Add intrinsics for FSGSBASE instructions - SAUCE: x86/fsgsbase/64: Enable FSGSBASE instructions in helper functions - SAUCE: x86/fsgsbase/64: Use FSGSBASE in switch_to() if available - SAUCE: x86/fsgsbase/64: Use FSGSBASE instructions on thread copy and ptrace - SAUCE: x86/speculation/swapgs: Check FSGSBASE in enabling SWAPGS mitigation - SAUCE: selftests/x86/fsgsbase: Test ptracer-induced GS base write with FSGSBASE - SAUCE: x86/fsgsbase/64: Enable FSGSBASE on 64bit by default and add a chicken bit - SAUCE: x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2 - SAUCE: Documentation/x86/64: Add documentation for GS/FS addressing mode * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error
[Kernel-packages] [Bug 1875863] Re: ceph -- Unable to mount ceph volume on s390x
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875863 Title: ceph -- Unable to mount ceph volume on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Unable to mount ceph volumes on big endian systems, like s390x. * The mount operation always fails with an IO error. * This is caused by an endiness issue in function handle_session where variable features is always little endian. * But test_bit assumes the host order of bytes, hence causes a problem on big endian systems. [Fix] * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix endianness bug when handling MDS session feature bits" [Test Case] * Setup ceph on s390x. * Try to mount a ceph volume. * If it mounts correctly the patch is applied and working. * Without the patch a mount always fails on big endian / s390x. [Regression Potential] * There is regression potential with having code changes in ceph's session handler, which is common code. * However, the patch was accepted (slightly changed) by the ceph maintainers and with that got upstream accepted, too. * The patch is fairly limited (5 lines removed, 3 added), hence the changes are quite traceable. __ When mounting a ceph volume, mount operation fails with an IO error. The problem is always reproducible. Identified potential root cause as kernel endian bug: In the function handle_session() variable @features always contains little endian order of bytes. Just because The feature mask sent by the MDS is little-endian (bits are packed bytewise from left to right in encode_supported_features()). However, test_bit(), called to check features availability, assumes the host order of bytes in that variable. This leads to problems on big endian architectures. Specifically it is impossible to mount ceph volume on s390. A fixup was proposed to convert little-endian order of bytes to the host one. That fixup was modified by ceph maintainers to use existing unpacking means for the conversion. The resulted patch attached. Related discussion in the ceph-development mailing list: https://marc.info/?l=ceph-devel&m=158815357301332&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870320] Re: [UBUNTU 18.04] zpcictl --reset - contribution for kernel
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-kvm - 5.4.0-1015.15 --- linux-kvm (5.4.0-1015.15) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-kvm (5.4.0-1012.12) focal; urgency=medium * focal/linux-kvm: 5.4.0-1012.12 -proposed tracker (LP: #1878795) * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zone_contiguou
[Kernel-packages] [Bug 1872726] Re: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872726 Title: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * An issue with the endianess handling in the Mellanox mlx5 driver was found. * The mask value is provided as 64 bit and has to be casted in either 32 or 16 bit. * On big endian systems the wrong half was casted which resulted in an all zero mask. [Fix] * Backport: https://launchpadlibrarian.net/476243025/0001-net-mlx5 -fix-endianness-handling-in-pedit-mask.patch [Test Case] * An s390x system with RoCE Express 2(.1) system is needed and the driver loaded. * Check whether the mask value stays zero, or if it also get's non- zero values. * Functional testing is currently only doable by IBM, since we only have RoCE (1) hardware that uses the mlx4 driver. [Regression Potential] * There is regression potential is moderate, since: * the RoCE 2(.1) cards are pretty new and not very wide spread, yet * the fix got already upstream accepted with 5.6 * However, at the end the patch modifies Mellanox common code (drivers/net/ethernet/mellanox/mlx5/core/en_tc.c) to make the driver work correctly on s390x. * but the changes were reviewed, signed off by Mellanox engineers and are very limited. [Other Info] * The above backport (patch-file) is based on commit 404402abd5f90aa90a134eb9604b1750c1941529 404402abd5f9 "net/mlx5e: Fix endianness handling in pedit mask" - the backport was needed for getting it applied to focal master-next. * The commit itself got upstream accepted with kernel v5.6, hence should automatically land in 'gorilla', but since gorilla is still based on 5.4, I'm adding 'G' to this SRU. __ Issue found in the Mellanox mlx5 device driver: The mask value is provided as 64 bit and has to be casted in either 32 or 16 bit. On big endian systems the wrong half was casted which resulted in an all zero mask. We need to get the upstream commit picked up for the Ubuntu 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1872726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861284] Re: Build and ship a signed wireguard.ko
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
This bug was fixed in the package linux - 5.3.0-59.53
---
linux (5.3.0-59.53) eoan; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
linux (5.3.0-56.50) eoan; urgency=medium
* eoan/linux: 5.3.0-56.50 -proposed tracker (LP: #1880111)
* Build and ship a signed wireguard.ko (LP: #1861284)
- [Packaging] wireguard -- add support for building signed .ko
- [Config] wireguard -- enable on all architectures
* Packaging resync (LP: #1786013)
- update dkms package versions
* debian/scripts/file-downloader does not handle positive failures correctly
(LP: #1878897)
- [Packaging] file-downloader not handling positive failures correctly
* Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found
due to firmware crash (LP: #1874685)
- iwlwifi: pcie: handle QuZ configs with killer NICs as well
* CVE-2020-12114
- propagate_one(): mnt_set_mountpoint() needs mount_lock
* Eoan update: upstream stable patchset 2020-05-11 (LP: #1878073)
- ext4: fix extent_status fragmentation for plain files
- bpftool: Fix printing incorrect pointer in btf_dump_ptr
- [Config] updateconfigs for ARM64_ERRATUM_1542419
- arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
- arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
- arm64: Silence clang warning on mismatched value/register sizes
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- pwm: rcar: Fix late Runtime PM enablement
- scsi: iscsi: Report unbind session event when the target has been removed
- ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- kernel/gcov/fs.c: gcov_seq_next() should increase position index
- selftests: kmod: fix handling test numbers above 9
- ipc/util.c: sysvipc_find_ipc() should increase position index
- kconfig: qconf: Fix a few alignment issues
- s390/cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- Revert "powerpc/64: irq_work avoid interrupt when called with hardware
irqs
enabled"
- pwm: renesas-tpu: Fix late Runtime PM enablement
- pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- drm/amd/display: Not doing optimize bandwidth if flip pending.
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- f2fs: fix to avoid memory leakage in f2fs_listxattr
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: bcmgenet: correct per TX/RX ring statistics
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
- net/x25: Fix x25_neigh refcnt leak when receiving frame
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- net: dsa: b53: Fix ARL register definitions
- net: dsa: b53: Rework ARL bin logic
- net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- mlxsw: Fix some IS_ERR() vs NULL bugs
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- iio: core: remove extra semi-colon from devm_iio_device_register() macro
- iio: st_se
[Kernel-packages] [Bug 1875506] Re: Bionic update: upstream stable patchset 2020-04-27
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1875660] Re: Focal update: v5.4.35 upstream stable release
This bug was fixed in the package linux - 5.4.0-37.41
---
linux (5.4.0-37.41) focal; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
- SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
mitigation
- SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation
documentation
- SAUCE: x86/speculation: Add Ivy Bridge to affected list
-- Marcelo Henrique Cerri Wed, 03 Jun
2020 11:24:23 -0300
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875660
Title:
Focal update: v5.4.35 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.35 upstream stable release
from git://git.kernel.org/
ext4: use non-movable memory for superblock readahead
watchdog: sp805: fix restart handler
xsk: Fix out of boundary write in __xsk_rcv_memcpy
arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0
arm, bpf: Fix offset overflow for BPF_MEM BPF_DW
objtool: Fix switch table detection in .text.unlikely
scsi: sg: add sg_remove_request in sg_common_write
ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops
ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN.
kbuild, btf: Fix dependencies for DEBUG_INFO_BTF
netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type
irqchip/mbigen: Free msi_desc on device teardown
ALSA: hda: Don't release card at firmware loading error
xsk: Add missing check on user supplied headroom size
of: unittest: kmemleak on changeset destroy
of: unittest: kmemleak in of_unittest_platform_populate()
of: unittest: kmemleak in of_unittest_overlay_high_level()
of: overlay: kmemleak in dup_and_fixup_symbol_prop()
x86/Hyper-V: Unload vmbus channel in hv panic callback
x86/Hyper-V: Trigger crash enlightenment only once during system crash.
x86/Hyper-V: Report crash register data or kmsg before running crash kernel
x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not
set
x86/Hyper-V: Report crash data in die() when panic_on_oops is set
afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus()
afs: Fix decoding of inline abort codes from version 1 status records
afs: Fix rename operation status delivery
afs: Fix afs_d_validate() to set the right directory version
afs: Fix race between post-modification dir edit and readdir/d_revalidate
block, bfq: turn put_queue into release_process_ref in __bfq_bic_change_cgroup
block, bfq: make reparent_leaf_entity actually work only on leaf entities
block, bfq: invoke flush_idle_tree after reparent_active_queues in pd_offline
rbd: avoid a deadlock on header_rwsem when flushing notifies
rbd: call rbd_dev_unprobe() after unwatching and flushing notifies
x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump
drm/ttm: flush the fence on the bo after we individualize the reservation
object
clk: Don't cache errors from clk_ops::get_phase()
clk: at91: usb: continue if clk_hw_round_rate() return zero
net/mlx5e: Enforce setting of a single FEC mode
f2fs: fix the panic in do_checkpoint()
ARM: dts: rockchip: fix vqmmc-supply property name for rk3188-bqedison2qc
arm64: dts: allwinner: a64: Fix display clock register range
power: supply: bq27xxx_battery: Silence deferred-probe error
clk: tegra: Fix Tegra PMC clock out parents
arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194
arm64: tegra: Fix Tegra194 PCIe compatible string
arm64: dts: clearfog-gt-8k: set gigabit PHY reset deassert delay
soc: imx: gpc: fix power up sequencing
dma-coherent: fix integer overflow in the reserved-memory dma allocation
rtc: 88pm860x: fix possible race condition
NFS: alloc_nfs_open_context() must use the file cred when available
NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid()
NFSv4.2: error out when relink swapfile
ARM: dts: rockchip: fix lvds-encoder ports subnode for rk3188-bqedison2qc
KVM: PPC: Book3S HV: Fix H_CEDE
[Kernel-packages] [Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
This bug was fixed in the package linux - 4.15.0-106.107 --- linux (4.15.0-106.107) bionic; urgency=medium * CVE-2020-0543 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux (4.15.0-103.104) bionic; urgency=medium * bionic/linux: 4.15.0-103.104 -proposed tracker (LP: #1881272) * "BUG: unable to handle kernel paging request" when testing ubuntu_kvm_smoke_test.kvm_smoke_test with B-KVM in proposed (LP: #1881072) - KVM: VMX: Explicitly reference RCX as the vmx_vcpu pointer in asm blobs - KVM: VMX: Mark RCX, RDX and RSI as clobbered in vmx_vcpu_run()'s asm blob linux (4.15.0-102.103) bionic; urgency=medium * bionic/linux: 4.15.0-102.103 -proposed tracker (LP: #1878856) * Packaging resync (LP: #1786013) - update dkms package versions * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Kernel log flood "ceph: Failed to find inode for 1" (LP: #1875884) - ceph: don't check quota for snap inode - ceph: quota: cache inode pointer in ceph_snap_realm * [UBUNTU 18.04] zpcictl --reset - contribution for kernel (LP: #1870320) - s390/pci: Recover handle in clp_set_pci_fn() - s390/pci: Fix possible deadlock in recover_store() * Bionic update: upstream stable patchset 2020-05-12 (LP: #1878256) - drm/edid: Fix off-by-one in DispID DTD pixel clock - drm/qxl: qxl_release leak in qxl_draw_dirty_fb() - drm/qxl: qxl_release leak in qxl_hw_surface_alloc() - drm/qxl: qxl_release use after free - btrfs: fix block group leak when removing fails - btrfs: fix partial loss of prealloc extent past i_size after fsync - mmc: sdhci-xenon: fix annoying 1.8V regulator warning - mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers - ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter - ALSA: hda/hdmi: fix without unlocked before return - ALSA: pcm: oss: Place the plugin buffer overflow checks correctly - PM: ACPI: Output correct message on target power state - PM: hibernate: Freeze kernel threads in software_resume() - dm verity fec: fix hash block number in verity_fec_decode - RDMA/mlx5: Set GRH fields in query QP on RoCE - RDMA/mlx4: Initialize ib_spec on the stack - vfio: avoid possible overflow in vfio_iommu_type1_pin_pages - vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn() - iommu/qcom: Fix local_base status check - scsi: target/iblock: fix WRITE SAME zeroing - iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system - ALSA: opti9xx: shut up gcc-10 range warning - nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl - dmaengine: dmatest: Fix iteration non-stop logic - selinux: properly handle multiple messages in selinux_netlink_send() - ASoC: tas571x: disable regulators on failed probe - ASoC: wm8960: Fix wrong clock after suspend & resume - rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket - xfs: acquire superblock freeze protection on eofblocks scans - cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled - net: fec: set GPR bit on suspend by DT configuration. - ALSA: hda: Keep the controller initialization even if no codecs found - ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported - ALSA: hda: call runtime_allow() for all hda controllers - scsi: qla2xxx: check UNLOADING before posting async work - RDMA/core: Fix race between destroy and release FD object - btrfs: transaction: Avoid deadlock due to bad initialization timing of fs_info::journal_info - mmc: sdhci-msm: Enable host capabilities pertains to R1b response - mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY - mmc: meson-mx-sdio: remove the broken ->card_busy() op * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - ext4: fix extent_status fragmentation for plain files - net: ipv4: avoid unused variable warning for sysctl - crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static - vti4: removed duplicate log message. - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - pwm: rcar: Fix late Runtime PM enablement - scsi: iscsi: Report unbind session event when the target has been removed - ASoC: Intel: atom: Take the drv->lock mute
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-riscv source package in Focal: Fix Committed Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
This bug was fixed in the package linux - 5.4.0-37.41 --- linux (5.4.0-37.41) focal; urgency=medium * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list -- Marcelo Henrique Cerri Wed, 03 Jun 2020 11:24:23 -0300 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-0543 ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12114 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
