This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-aws - 5.8.0-1014.15
---
linux-aws (5.8.0-1014.15) groovy; urgency=medium
* groovy/linux-aws: 5.8.0-1014.15 -proposed tracker (LP: #1903182)
* Groovy update: v5.8.15 upstream stable release (LP: #1902130)
- [Packaging] [aws] module
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux-aws - 5.8.0-1014.15
---
linux-aws (5.8.0-1014.15) groovy; urgency=medium
* groovy/linux-aws: 5.8.0-1014.15 -proposed tracker (LP: #1903182)
* Groovy update: v5.8.15 upstream stable release (LP: #1902130)
- [Packaging] [aws] module
This bug was fixed in the package linux-aws - 5.8.0-1014.15
---
linux-aws (5.8.0-1014.15) groovy; urgency=medium
* groovy/linux-aws: 5.8.0-1014.15 -proposed tracker (LP: #1903182)
* Groovy update: v5.8.15 upstream stable release (LP: #1902130)
- [Packaging] [aws] module
This bug was fixed in the package linux-oem-5.6 - 5.6.0-1035.37
---
linux-oem-5.6 (5.6.0-1035.37) focal; urgency=medium
* focal/linux-oem-5.6: 5.6.0-1035.37 -proposed tracker (LP: #1903149)
* Packaging resync (LP: #1786013)
- update dkms package versions
* drm/i915/dp_mst
This bug was fixed in the package linux-aws - 5.8.0-1014.15
---
linux-aws (5.8.0-1014.15) groovy; urgency=medium
* groovy/linux-aws: 5.8.0-1014.15 -proposed tracker (LP: #1903182)
* Groovy update: v5.8.15 upstream stable release (LP: #1902130)
- [Packaging] [aws] module
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
This bug was fixed in the package linux - 5.8.0-31.33
---
linux (5.8.0-31.33) groovy; urgency=medium
* groovy/linux: 5.8.0-31.33 -proposed tracker (LP: #1905299)
* Groovy 5.8 kernel hangs on boot on CPUs with eLLC (LP: #1903397)
- drm/i915: Mark ininitial fb obj as WT on
You have been subscribed to a public bug:
This is occurring on Ubuntu 20.04 with kernel 5.4.0-56-generic.
To demonstrate, run
$ sudo tcpdump -nv -ienp4s0 igmp
(adjusting the interface name appropriately).
The result will be 0 packets captured, even though all other Ubuntu systems on
the same
** Description changed:
Add the nitro_enclaves driver from mainline to linux-
aws/{focal,bionic-5.4} and linux-aws/{groovy,hirsute}. The driver is
supplied by the following mainline commits, which are all clean cherry
picks for groovy with a couple of trivial backports for focal:
I had to reinstall Ubuntu 20.04 with kernel 5.4.0-56 because on 20.10
with kernel 5.8.0-28 the wifi was very unstable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1871794
Title:
--- Comment From jjhe...@us.ibm.com 2020-12-01 08:05 EDT---
(In reply to comment #74)
> @Jason, seems to be some build failures. Can you please have a look.
It looks like there are two versions of this patch applied:
[PATCH] s390-tools: zipl: Fix NVMe partition and base device detection
Found on Groovy 5.8.0-31.33 lowlatency & generic. Only failing on one
node (lagalla) and passes on the other (rizzo)
12/01 05:19:36 DEBUG| utils:0116| Running './test_maps'
12/01 05:19:36 DEBUG| utils:0153| [stdout] Fork 1024 tasks to
'test_update_delete'
12/01 05:19:37 DEBUG|
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906413
Title:
My touchpad is not detected.
Any movement on this?
--
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/1904922
Title:
External monitor undetected over hdmi
Status in linux package in Ubuntu:
Confirmed
Bug
Public bug reported:
I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10 0
I: Bus=0019 Vendor=
** Patch added: "libevdev-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5440023/+files/libevdev-focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Patch added: "libevdev-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5440024/+files/libevdev-groovy.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Patch removed: "libevdev.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5439889/+files/libevdev.debdiff
** Patch removed: "libevdev-focal.debdiff"
Posted a patch for this on https://lists.ubuntu.com/archives/kernel-
team/2020-November/115178.html targeting both G and H.
--
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/1905975
Title:
Thx Gerald, adjusting tags accordingly ...
** 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/1904884
Title:
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1905627
Title:
Bluetooth stops working on Raspberry Pi
#7 worked for me. 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/1883905
Title:
Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL
Status in linux package in
--- Comment From geral...@de.ibm.com 2020-12-01 09:14 EDT---
Verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904884
Title:
s390: dbginfo.sh triggers kernel panic,
Public bug reported:
New upstream version, bringing in updated regulatory rules for various
jurisdictions.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: wireless-regdb (Ubuntu Xenial)
Do you remember what happened just prior to the reboot - have you been
upgrading the system with a new kernel and/or updated packages?
(Btw. the kernel 4.15.0-91 is a bit outdated, current is 4.15.0-124.)
There's maybe a file /etc/lvm/lvm.conf.dpkg-dist available from a previous
upgrade.
Or
--- Comment From niklas.schne...@ibm.com 2020-12-01 08:55 EDT---
(In reply to comment #19)
> Well, that's a pity, because it means that a manual kernel SRU is needed now.
> It's needed to make sure that someone who has the fix in focal and upgrades
> to groovy will not run into a
is working, thanks.
erkan@erkan-HP-635-Notebook-PC:~$ uname -a
Linux erkan-HP-635-Notebook-PC 5.4.0-57-generic #63-Ubuntu SMP Fri Nov 27
14:31:47 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
erkan@erkan-HP-635-Notebook-PC:~$ ls /sys/class/backlight/
acpi_video0 radeon_bl0
reply #32
@seb128
Thanks for review, actually, it is not a kernel bug, it is because the touchpad
report descriptor doesn't config correctly, please refer to the windows
document "Device capabilities feature report" part.
Reading the description is also sounds like it's a kernel bug if the
device is wrongly tagged no? if so why not fix the kernel instead of
workaround in userland?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thank Kai, some questions and notes
- lidevdev is in hirsute now and include the change
- the libevdev debdiff
- the version '+lp1906341~rc1' was ok for a ppa but should be changed for the
archive
- the patch should include a description, a reference to the upstream commit
would be enough
Well, that's a pity, because it means that a manual kernel SRU is needed now.
It's needed to make sure that someone who has the fix in focal and upgrades to
groovy will not run into a regression situation.
I think the 'plan' for hirsute is still 5.11 - but it of course depends a lot
on
@khan.sharukh
1. I have VIOS update DJCN15WW (laptop model 14-IIL)
2. Ubuntu 20.04.1 LTS
3. I first got it to work with the kernel from
https://people.canonical.com/~khfeng/lp1853277-final/
Now I am on 5.4.0-54-generic and it works.
--
You received this bug notification because you are a
--- Comment From niklas.schne...@ibm.com 2020-12-01 06:51 EDT---
Ahh, got it 5.8 stable is already EOL according to https://www.kernel.org/
By the way, is the plan for 21.04 LTS still to go with v5.11,
seeing as Greg announced that v5.10 will be the next long term
stable kernel, picking
Hi Guys,
I can see there are number of people who are lucky to get the touchpad working.
But it still not working for me.
I am a Ubuntu User and Stuck with Windows from Last 6 months.
Please help me in running ubuntu with touchpad.
I have installed Ubuntu 20.04 using keyboard but it still not
--- Comment From niklas.schne...@ibm.com 2020-12-01 06:43 EDT---
(In reply to comment #16)
> Hi Niklas,
> I found the ticket upstream accepted with hash 0b2ca2c7d0c9
> and the provenance in 'git show 0b2ca2c7d0c9' mentions:
> Cc: # 5.8
> So I'm expecting that in 5.8 (rather than in 5.9)
marking verified since it's a system specific workaround
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
marking verified on the basis that the patch is trivial and already in
groovy and focal
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906384
Title:
[UBUNTU 18.04] lvm boot failure
Status in
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux-kvm - 4.4.0-1084.93
---
linux-kvm (4.4.0-1084.93) xenial; urgency=medium
* xenial/linux-kvm: 4.4.0-1084.93 -proposed tracker (LP: #1905657)
* CONFIG options for (ipip, sit) should not be built-in to the KVM kernels
(LP: #1899832)
-
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
Verified done on focal.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1901971
Title:
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
Hi Niklas,
I found the ticket upstream accepted with hash 0b2ca2c7d0c9
and the provenance in 'git show 0b2ca2c7d0c9' mentions:
Cc: # 5.8
So I'm expecting that in 5.8 (rather than in 5.9) stable - and 5.8 is the
kernel used in groovy/20.10.
So I was looking - and couldn't find the patch - in
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
This bug was fixed in the package linux - 4.4.0-197.229
---
linux (4.4.0-197.229) xenial; urgency=medium
* xenial/linux: 4.4.0-197.229 -proposed tracker (LP: #1905489)
* sha1_ce and sha2_ce modules no longer load on arm64 (LP: #1905336)
- SAUCE: Revert "crypto: arm64/sha -
** Tags removed: verification-needed-focal verification-needed-groovy
** Tags added: verification-done-focal verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
** Summary changed:
- pmtu.sh net selftest fail with PMTU dst likely leaked
+ pmtu.sh net selftest fail with PMTU dst likely leaked (ipv6: cleanup of
cached exceptions - nexthop objects [FAIL])
** Summary changed:
- pmtu.sh net selftest fail with PMTU dst likely leaked (ipv6: cleanup of
Failed on Hirsute with:
# selftests: net: reuseport_bpf_numa
# IPv4 UDP
# send node 0, receive socket 0
# libnuma: Warning: Cannot read node cpumask from sysfs
# ./reuseport_bpf_numa: failed to pin to node: No such file or directory
not ok 3 selftests: net: reuseport_bpf_numa #
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 05:26 EDT---
IBM Bugzilla status->closed, Fix Released by all requested distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Found on Hirsute
** Tags added: hirsute
** Summary changed:
- icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
G-AWS
+ icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G
/ H
--
You received this bug notification because you are a member
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 05:27 EDT---
IBM Bugzilla status->closed, Fix Released by all requested distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Steps used to verify the fix (both in focal and groovy):
$ fallocate -l 8G /home/ubuntu/disk.img
$ sudo zpool create pool /home/ubuntu/disk.img
$ for i in {1..20}; do sudo zfs create pool/ds$i; done
$ sudo zfs unmount pool/ds20
$ sudo zfs mount -a & sudo zfs mount -a &
[1] 1964
[2] 1965
The upstream has the fix already
https://gitlab.freedesktop.org/libinput/libinput/-/commit/69959c8a3b0612fb2bea015713f630a896188529
Will hirsute libinput sync the latest commit for it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- lvm boot failure
+ [UBUNTU 18.04] lvm boot failure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906384
Title:
[UBUNTU 18.04] lvm boot failure
Status in linux
Default Comment by Bridge
** Attachment added: "lvm.conf file"
https://bugs.launchpad.net/bugs/1906384/+attachment/5439973/+files/lvm.conf.1120
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
** Summary changed:
- ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 kernels
+ ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
** Description changed:
[Impact]
* The touchpad's right button become no function after update to 5.4
kernel
* The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that
libinput regard it as clickpad.
* Add a model quirk to unset the bit can make touchpad's right
You have been subscribed to a public bug:
---Problem Description---
boot failure with LVM root disk
---uname output---
4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:07:52 UTC 2020 s390x s390x s390x
GNU/Linux
Machine Type = 8561 LT1
---System Hang---
Boot failure with LVM root disk and
--- Comment From niklas.schne...@ibm.com 2020-12-01 04:45 EDT---
@Frank Heinz-Werner said you had trouble finding the upstream stable commit for
this.
The original upstream commit is
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
This was
Upload libinput devdiff for groovy.
** Patch added: "libinput-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5439967/+files/libinput-groovy.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
Upload libevdev debdiff for groovy.
** Patch added: "libevdev-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1906341/+attachment/5439966/+files/libevdev-groovy.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 04:29 EDT---
IBM Bugzilla status->closed, Fix Released by all requested Distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From heinz-werner_se...@de.ibm.com 2020-12-01 04:31 EDT---
IBM Buzgilla status->closed, Fix Released by all requested distros
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-meta-hwe-5.4 -
5.4.0.56.62~18.04.50
---
linux-meta-hwe-5.4 (5.4.0.56.62~18.04.50) bionic; urgency=medium
* Bump ABI 5.4.0-56.62~18.04
linux-meta-hwe-5.4 (5.4.0.55.61~18.04.49) bionic; urgency=medium
* Bump ABI 5.4.0-55.61~18.04
*
This bug was fixed in the package linux-hwe-5.4 - 5.4.0-56.62~18.04.1
---
linux-hwe-5.4 (5.4.0-56.62~18.04.1) bionic; urgency=medium
* bionic/linux-hwe-5.4: 5.4.0-56.62~18.04.1 -proposed tracker (LP:
#1905312)
[ Ubuntu: 5.4.0-56.62 ]
* focal/linux: 5.4.0-56.62 -proposed
** Tags added: verification-failed-groovy verification-needed-focal
** Tags removed: verification-failed-groovy
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
101 - 200 of 209 matches
Mail list logo