[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is fixed in Disco as well via linux-stable
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
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/1864005
*** This bug is a duplicate of bug 1850654 ***
https://bugs.launchpad.net/bugs/1850654
** This bug has been marked a duplicate of bug 1850654
update-initramfs complains of missing amdgpu firmware files
--
You received this bug notification because you are a member of Kernel
Packages,
Hi Hai Heng Feng,
How are you? Hope you're fine.
I saw it's already release kernel v5.6
Should I try with this kernel?
--
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/1860754
Title:
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
Kernel Version: 5.4.0-21-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM
Apr 02 17:53:55 buntu kernel: platform eisa.0: Probing EISA
--- Comment From cborn...@de.ibm.com 2020-04-03 02:46 EDT---
For reference (in case Canoninical wants to track upstream commit IDs)
Linus Torvalds has finally pulled the KVM/Kernel changes scheduled for 5.7-rc1.
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: In Progress => Fix Committed
** Changed in: kunpeng920
Status: In Progress => Fix Committed
--
You received this bug notification because you are
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: New => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5
** Changed in: kunpeng920
Status: New => Fix
--- Comment on attachment From daniel.axte...@ibm.com 2020-04-03 03:05
EDT---
Hi Seth,
Thanks, that was extremely helpful.
Nayna noticed that I was overly keen to lock things down - I should only
lock down in Secure mode: if a system is in Trusted mode only I
shouldn't lock it down.
Hi Mauricio,
there is the problem that this tarball contains an awful lot of
sensitive data, some of that personal data that is protected under the
GDPR.
Maybe you could tell me which specific parts / sections you are
interested in, so that I can anonymize and upload them.
Thanks,
Sebastian
--
@schmit,
Could you please test this kernel
https://people.canonical.com/~hwang4/testdsp/, remove the dmic_detect=0
workaround, and download all deb and sudo apt install *.deb;reboot
thx.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This crash seems to be easy to reproduce. I made an Apitrace of the part
of Gurumin with the scene that caused the first crash and let it
replaying endlessly. After 1h30min, the system crashed again.
The apitrace can be obtained from:
https://mega.nz/file/8thHlYpa#_HBCUsIifUnD8R3K2U6v--
Marking 'Fix Released' after the lockdown changes.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862708
Title:
Our policy is to require module signatures only under lockdown.
CONFIG_MODULE_SIG_FORCE requires modules to be signed unconditionally,
which makes dkms impossible on systems which have no mechanism for
importing keys from firmware.
--
You received this bug notification because you are a member
not seen anymore with 1:10.0.0-1ubuntu2
** Changed in: llvm-toolchain-10 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1866882
Title:
If we understood you correctly you want to have CONFIG_MODULE_SIG_FORCE
set (for Power only) - so we are considering that ...
--
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/1866909
Title:
The revised patch looks indeed less strict - we are considering that one
...
--
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/1855668
Title:
lockdown on power
Status in The
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
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/1870538
Title:
ryzen 5 3600x hard lockup
Public bug reported:
System randomly freezes and requires a hard reset. Very frequently it
happens when trying to wake it up from a period of inactivity. (after
the screen has turned off). Almost daily occurrence.
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
Linux
Afaict the ppc ima arch policy is about ensuring that signature
verification is done for module loading and kexec, which in our kernel
will be enforced by automatically turning on lockdown integrity mode
under secure boot. So my conclusion is that CONFIG_MODULE_SIG_FORCE
should stay off and
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1863574
Title:
Update mpt3sas Driver to 33.100.00.00 for
** Also affects: linux (Ubuntu Focal)
Importance: High
Assignee: Andrea Righi (arighi)
Status: Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Handled by #1867677
--
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/1862888
Title:
Boot hang on ASUS WS X299 SAGE
Status in linux package in Ubuntu:
Confirmed
Bug description:
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1863581
Title:
Ubuntu 20.04: megaraid_sas driver update to
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1867586
Title:
[hns3-0316]sync mainline kernel 5.6rc4 hns3
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a
Damn sorry about that, I didn't notice the kernel moved from .43 to .45.
I'll try with 46
--
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/1845678
Title:
Lenovo ThinkPad X1 Carbon 7th
Hi Marcus,
Since 20.04 is not yet released, and the logs attached do not show the stack
trace
(it seems like an apport behavior, in OopsText.txt, not your/human's fault
AFAIK)
it seems there's little investigation that can be done in this error.
I'd suggest that if you can reproduce this
Public bug reported:
Filesystems ordinarily mounted beneath /sys, particularly /sys/fs/cgroup, are
not mounted within network namespaces created by ip-netns(8), as
lib/namespace.c:netns_switch() explicitly remounts /sys.
The patch enclosed removes the offending calls to umount2(2) and mount(2),
Hi!
Sound still not working on -45, confirmed working on -40. Running Ubuntu
18.04.4 on Lenovo X1C 7th gen (just like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868165).
cheers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1867803 ***
https://bugs.launchpad.net/bugs/1867803
This issue is still broken with -43 and -45 kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
This is a generic (catch-all) bug for tracking various changes to
improve the built-in kernel selftests.
** Affects: linux (Ubuntu)
Importance: Low
Status: Fix Committed
** Tags: focal
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
I'm suddenly having a major sense of deja vu about this. I think we hit
very similar issues on x86, and after discussions with Mimi we decided
that CONFIG_IMA_ARCH_POLICY should be disabled for us. I think this may
be the right solution here too.
--
You received this bug notification because you
Reporter hasn't confirmed that it's corrected yet... "Fix committed"
seems premature.
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Landed in focal master:
96225dde40a6 s390/dasd: fix data corruption for thin provisioned devices
and also in the current kernel.
Hence updating ticket to Fix Released.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix
FWIW, bug 1870553 reported for apport, about the lack of the kernel
stack traces.
--
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/1868388
Title:
watchdog: BUG: soft lockup - CPU#11 stuck
Fresh install with proprietary driver’s installation check box ticked
worked fine till I rebooted again and then I could not get into the
desktop. All drivers installed fine but one reboot later things were
back to being unable to login. So I did a chroot and removed splash from
grub command line
Public bug reported:
I was transferring my zfs snapshots to the backup server, when suddenly
it stalled. I checked dmesg on the server and found a "kernel bug"
entry.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu
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/1870559
Title:
Kernel NULL pointer
I'm still seeing this same behaviour for the 5.3 kernel.
I'm just now getting back to this, and I think I'm going to need some
hand holding...
> Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and
i2c-designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).
I copied the 4.13.0
** Patch added: "iproute2-4.3.0+no-remount-sysfs.patch"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1870554/+attachment/5345648/+files/iproute2-4.3.0+no-remount-sysfs.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
--- Comment From mranw...@us.ibm.com 2020-04-03 10:30 EDT---
Sorry, we don't know if we want CONFIG_MODULE_SIG_FORCE set. The modules
aren't loading, and we weren't sure what needed to change. We're happy to try
a kernel with IMA_ARCH_POLICY if that fixed it on x86.
--
You received
I'll get a test kernel uploaded with IMA_ARCH_POLICY up, will let you
know when it's ready for testing.
--
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/1866909
Title:
Ubuntu Kernel
Um, off rather.
--
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/1866909
Title:
Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot
Status in The Ubuntu-power-systems project:
Oh but PPC_SECURE_BOOT depends on IMA_ARCH_POLICY. For now I'm going to
make it depend on that or LOCK_DOWN_IN_SECURE_BOOT to get the test build
going. I think this makes sense because lockdown enforces signatures for
module loading and kexec (plus a number of other restrictions), which I
think is
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1870571
Title:
Focal update: v5.4.30 upstream stable
--- Comment From mranw...@us.ibm.com 2020-04-03 12:45 EDT---
We've been working with Mimi and I think that what we need now aren't config
option changes, but this patch:
diff --git a/arch/powerpc/kernel/ima_arch.c b/arch/powerpc/kernel/ima_arch.c
index e341162..c1ea55d 100644
---
Edit initramfs.conf as su.
Rem out COMPRESS-lz4 line
Run update-initramfs -u - System will return with "COMPRESS parameter
not set".
Now edit initramfs.conf again. Remove the # on COMPRESS=lz4, run again
update-initramfs -u.
It will close without any error. Reboot.
I just did and no more
Follow-up on my previous post - Unpacking failed, Decoding failed is
back on second boot. Please do not waste your time trying the above.
Sorry.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
Hi Sebastian,
Sure, that's certainly understandable.
For starters, the topology of the block/bcache devices would do it:
(set -x; lsblk; sudo dmsetup table; grep -r ^ /sys/block/bcache*/bcache)
> lp1867916.1.out 2>&1
Then please upload the output file (or copy/paste, if file access is
though.)
Stefan, while recent kernels seem happier than previous kernels (I think
-14 era was terrible), I don't think this problem is fixed yet:
sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Milestone: None => ubuntu-18.04.5
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: In Progress => Fix Committed
** Changed in: kunpeng920/upstream-kernel
sorry, this needs testing
** Changed in: llvm-toolchain-10 (Ubuntu)
Status: Fix Released => 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/1866882
Title:
segfault in
Generally speaking we don't know what country a device is operating in,
so we default to the world domain which should be safe throughout the
world. The AP may send a hint to the client as to what regulatory domain
to use, but many APs do not do this.
Also note that on many desktop systems now
Hi Jeff,
I went back to check if those patches in comment #5 are pulled from the
MKP tree into the Mainline tree and I noticed that those are landed now.
The SHA IDs of those commits in the Mainline kernel are as follows,
df3fe76658ed scsi: lpfc: add RDF registration and Link Integrity FPIN
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-osp1 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just to be clear, not *all* tracing tools work, but this is much better:
sarnold@millbarge:/tmp$ uname -a
Linux millbarge 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
sarnold@millbarge:/tmp$ sudo zfsslower-bpfcc
Traceback (most recent call last):
I tried the current Ubuntu Studio ISO, dated 4/3/2020, and this ZFS boot
issue is still there. Are there any post-install commands that can be
run to fix it or do I need to wait for a subsequent spin of the ISO
file?
--
You received this bug notification because you are a member of Kernel
I as the thread starter fully agree with Borislav and set this bug
report to status resolved. Thank you all very much for the interesting
discussion!
Having started with massive stability problems on my new Ryzen build, I
reported this issue to address a potential problem in the Linux kernel.
In
** Changed in: linux
Status: Confirmed => Expired
--
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/1690085
Title:
Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Is https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869481
possibly connected to this too?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1859754
Title:
[SRU] add ucm to
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
You have been subscribed to a public bug:
Had terminal and firefox open.
Then atemmepted to see if i could hibernate with
pm-hibernate
just to see if it worked
ProblemType: KernelOops
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-21-generic 5.4.0-21.25
ProcVersionSignature: Ubuntu
** Package changed: ubuntu => linux (Ubuntu)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870616
Title:
[MEDION E122X] hibernate/resume failure
*** This bug is a duplicate of bug 1806242 ***
https://bugs.launchpad.net/bugs/1806242
i have the same issue on ubuntu 19.10
cat /etc/modprobe.d/i915.conf
options i915 enable_psr=0
options i915 enable_guc=2
5.3.0-45-generic
followed by one of the eight cores going crazy ~100% usage and i
i have the same issue on ubuntu 19.10
Apr 3 22:43:21 HP-15-cs3xxx kernel: [ 8867.271966]
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe
A (start=532823 end=532824) time 143 us, min 1073, max 1079, scanline
start 1072, end 1081
cat /etc/modprobe.d/i915.conf
options
Oh thanks!
I got some guidance from the kernel team that everything was mostly
ok, but I needed to update the commits so the cherry pick showed the
source it came from since it was not mainline. I had started working
on updating all the commits, but, let me check what you've just
provided and I
Just to be clear this is what iw reg get shows on Rasbian:
pi@raspberrypi:~$ iw reg get
global
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @
Based on some quick googling, I think there's some localization set up
on raspbian that must also cause it to set the regulatory domain.
https://www.raspberrypi.org/documentation/configuration/wireless/desktop.md
--
You received this bug notification because you are a member of Kernel
Packages,
under the following configuration the sound and microphone work as
described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/comments/28
ii libasound2:amd64 1.1.9-0ubuntu1.3
amd64shared library for ALSA applications
ii
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/1870616
Title:
[MEDION E122X]
I went ahead and ran through the Raspbian setup again and this time I
said I was in the UK. After that and rebooting I ran 'iw reg get' and
the results showed "country GB: DFS-ETSI".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi yamato, thank you for the report and prompt test!
So, I need to setup a guest with secureboot, I don't have it at hand.
Meanwhile, can you test the in-between kernel versions, so we can narrow down
when the problem was introduced?
The versions we had released in Bionic between -64 and -76
** Changed in: linux-restricted-modules (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
20.04 beta still has this issue for me
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins
I'm also getting the above errors when trying to read from a 1080p60
USB3 webcam. It seems I have some information not mentioned above.
[8.822044] usb 4-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[8.851879] usb 4-2: New USB device found, idVendor=15aa, idProduct=1555,
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
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/1850238
Title:
ucsi_ccg 50 second hang while resuming from
Sorry for the late response
Do you want me to run that command when the lid is close?
--
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/1859380
Title:
Sleep doesn't work on my ThinkPad X1
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Fix Committed
--
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/1868217
Title:
Make Dell WD19 dock more reliable after
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1768452
Title:
Insert test_bpf module will report 4
Beyond all of that, does anyone happen to know of a USB3 card that does work
(on 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/1749961
Title:
xhci_hcd: TRB DMA errors reported
--- Comment From mranw...@us.ibm.com 2020-04-03 16:36 EDT---
We did some testing with that patch (previous comment) on top of the
5.4.0-21.25+lp1866909v202004020814 source/config file. We signed the
kernel/modules and securely booted it. That fixed the module loading issue we
were
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1812638
Title:
reuseport_bpf_numa in net from
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1869642
Title:
No audio output from Dell WD19 HDMI/DP
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Test build is done now, in the same location. It has the above patch and
also the updated patch from bug 1855668.
--
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/1866909
Title:
Ubuntu
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
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/1869694
Title:
Support SMO8840 as LIS2DH12
Status in HWE
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1870604
Title:
Bionic update: upstream stable patchset
New test build with the updated patch in the same ppa.
--
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/1855668
Title:
lockdown on power
Status in The Ubuntu-power-systems project:
Fix
Applied to Eoan.
@You-Sheng: Note that this was NOT applied to Bionic. It's not clear if
it should be applied to Bionic or not (see the responses on the email
thread)
** Changed in: linux (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a
This bug was fixed in the package linux-azure - 5.4.0-1008.8
---
linux-azure (5.4.0-1008.8) focal; urgency=medium
[ Ubuntu: 5.4.0-21.25 ]
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Fri, 27 Mar
2020 17:57:04
This bug was fixed in the package linux-azure - 5.4.0-1008.8
---
linux-azure (5.4.0-1008.8) focal; urgency=medium
[ Ubuntu: 5.4.0-21.25 ]
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Fri, 27 Mar
2020 17:57:04
This bug was fixed in the package linux-aws - 5.4.0-1007.7
---
linux-aws (5.4.0-1007.7) focal; urgency=medium
[ Ubuntu: 5.4.0-21.25 ]
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Fri, 27 Mar
2020 17:06:08
This bug was fixed in the package linux-azure - 5.4.0-1008.8
---
linux-azure (5.4.0-1008.8) focal; urgency=medium
[ Ubuntu: 5.4.0-21.25 ]
* CVE-2020-8835
- SAUCE: bpf: undo incorrect __reg_bound_offset32 handling
-- Thadeu Lima de Souza Cascardo Fri, 27 Mar
2020 17:57:04
1 - 100 of 102 matches
Mail list logo
