@Henrik,
forget to reset the patch that disables d3cold_allowed and please try this
again. thanks
the d3cold_allowed shoube 1.
https://drive.google.com/drive/folders/17qeSGLKz8hR8TLsr35qS_4RSDUZcpaLu?usp=sharing
--
You received this bug notification because you are a member of Kernel
Packages,
root@ubuntu:~# cat /etc/apt/sources.list.d/ubuntu-focal-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse
universe
root@ubuntu:~# apt policy linux-image-kvm
linux-image-kvm:
Installed: 5.4.0.1033.31
Candidate:
I am trying to do the security review of flashrom for this MIR but
currently it FTBFS with the attached debdiff in comment 9 - the build
log is attached. Can this please be resolved (along with removing the
'WILLIAM we're doing tests!' part of the output :)
** Attachment added:
This patch may help, please give it a try:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8bf7111b4bda00ae82e2de0cd871af997c3f2e9b
--
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.
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-aws (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926999
Title:
Hirsute update: v5.11.16
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-aws (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1923415
Title:
Hirsute update: v5.11.13
This was fixed with linux 4.4.0-211.243 in Ubuntu 16.04 ESM (Infra).
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux (Ubuntu Impish)
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Confirmed
--
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/1879341
Title:
test_350_retpolined_modules from
Unable to run apport-collect 1928744 command.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1928744
Title:
Disk IO
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 192
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1928890
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1928889
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
** Summary changed:
- test_utils_testsuite linux ADT test failure with linux/5.11.0-18.19 (ERROR:
capability CAP_CHECKPOINT_RESTORE not found in severity.db)
+ test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with
linux/5.11.0-18.19
** Description changed:
This is a
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
Public bug reported:
This is a scripted bug report about ADT failures while running linux
tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Not a regression. Found to occur previously on hirsute/linux
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1885271
Title:
kernel oops xr-usb-serial
Status in linux package in
@piotr (peterq94)
refer comments #22 & #24 on this report.
I've written about this (work-around) on Lubuntu's discourse I believe
too (https://discourse.lubuntu.me/t/login-screen-flashes/1634/7 and
maybe elsewhere too). I've lost access to the d990 (which wasn't my
box) so I can't test further
Thanks. Not all logs will show the problem since a full lockup might
prevent pending log messages from reaching the disk. The log in comment
#10 however looks related and ends with some problems in the 'amdgpu'
kernel driver, which is what I expected.
So this bug is now assigned to the correct
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 1928744
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1928600
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package lttng-modules -
2.12.2-1ubuntu1~20.04.2
---
lttng-modules (2.12.2-1ubuntu1~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:09
+0100
** Changed in:
The verification of the Stable Release Update for rtl8812au has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package nvidia-graphics-drivers-340 -
340.108-0ubuntu5.20.04.2
---
nvidia-graphics-drivers-340 (340.108-0ubuntu5.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:47
+0100
This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg-
0ubuntu13~20.04.2
---
rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:52
This bug was fixed in the package backport-iwlwifi-dkms -
8324-0ubuntu3~20.04.3
---
backport-iwlwifi-dkms (8324-0ubuntu3~20.04.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:04
+0100
** Changed in:
This bug was fixed in the package liblzf - 3.6-2~ubuntu1.20.04.2
---
liblzf (3.6-2~ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 17:11:50
+0100
** Changed in: lime-forensics (Ubuntu Focal)
This bug was fixed in the package virtualbox-hwe - 6.1.16-dfsg-
6ubuntu1.20.04.2
---
virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:25
+0100
** Changed in:
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.4
---
v4l2loopback (0.12.3-1ubuntu0.4) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:12
+0100
** Changed in: virtualbox (Ubuntu Focal)
This bug was fixed in the package virtualbox -
6.1.16-dfsg-6~ubuntu1.20.04.2
---
virtualbox (6.1.16-dfsg-6~ubuntu1.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:42:15
+0100
** Changed in:
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.9
---
zfs-linux (0.8.3-1ubuntu12.9) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:45
+0100
--
You received this bug notification because
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu6~20.04.2
---
oss4 (4.2-build2010-5ubuntu6~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:32
+0100
** Changed in: r8168 (Ubuntu
This bug was fixed in the package sysdig - 0.26.4-1ubuntu0.3
---
sysdig (0.26.4-1ubuntu0.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:03
+0100
** Changed in: v4l2loopback (Ubuntu Focal)
This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1.2
---
dm-writeboost (2.2.9-1ubuntu1.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:23
+0100
** Changed in: evdi (Ubuntu Focal)
This bug was fixed in the package r8168 - 8.048.00-1ubuntu0.20.04.2
---
r8168 (8.048.00-1ubuntu0.20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:42
+0100
** Changed in: rtl8812au (Ubuntu Focal)
This bug was fixed in the package lime-forensics - 1.9-1ubuntu0.2
---
lime-forensics (1.9-1ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:00
+0100
** Changed in: lttng-modules (Ubuntu Focal)
This bug was fixed in the package evdi - 1.7.0+dfsg-1ubuntu1~20.04.3
---
evdi (1.7.0+dfsg-1ubuntu1~20.04.3) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:32
+0100
** Changed in: gost-crypto (Ubuntu
This bug was fixed in the package acpi-call - 1.1.0-5ubuntu0.2
---
acpi-call (1.1.0-5ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:55
+0100
** Changed in: acpi-call (Ubuntu Focal)
This bug was fixed in the package iptables-netflow - 2.4-2ubuntu0.4
---
iptables-netflow (2.4-2ubuntu0.4) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:51
+0100
** Changed in: liblzf (Ubuntu Focal)
This bug was fixed in the package gost-crypto - 0.3.2-2ubuntu0.2
---
gost-crypto (0.3.2-2ubuntu0.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:41
+0100
** Changed in: iptables-netflow (Ubuntu Focal)
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom-
0ubuntu7~20.04.2
---
bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:27
+0100
** Changed in:
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu6.2
---
dahdi-linux (1:2.11.1~dfsg-1ubuntu6.2) focal; urgency=medium
* No change rebuild in security pocket. LP: #1914279.
-- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:14
+0100
** Changed in: dm-writeboost
changed HWE to linux as I see no reference to a HWE (5.4) kernel
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
4.15.0-142-generic disk IOs (writes) are suffering from terrible delay.
Time required to write 1GB of data to the dist is ~12 minutes.
1GB in 12 minutes:
strace -ttvvff -o mel.strace
** Description changed:
After leaving my laptop on sleep mode for a while, then bringing it up
again causes the touchpad to stop responding completely. Checked for it
in the bus/input/devices folder and didn't see it.
Laptop model: ASUS X450L
Touchpad manufacturer: I presume to also
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/1928878
Title:
Touchpad suddenly not
Public bug reported:
After leaving my laptop on sleep mode for a while, then bringing it up
again causes the touchpad to stop responding completely. Checked for it
in the bus/input/devices folder and didn't see it.
Laptop model: ASUS X450L
Touchpad manufacturer: I presume to also be ASUS
Em sábado, 15 de maio de 2021, às 11:24:17 -03, Thiago Jung Bauermann
escreveu:
> Unexpectedly, 1.197 is now reliable too! I have been running it for about
> half a day (which is more than what was possible before) and it is fine.
After 4 days of stability I just had the retry page fault problem
I will ping you guys also here, since it seems to be more popular bug
report. I've send a patch for speaker amp. You can find it here
https://bugzilla.kernel.org/show_bug.cgi?id=207423#c40 and test if you'd
like.
--
You received this bug notification because you are a member of Kernel
Packages,
@guiverc If I will install LightDM this will be works with no issues
with LXQt environment? sddm is unusable for me so this is important
question.
Or maybe is a way to eliminate Display Manager and log in with terminal
and next start LXQt? Can you answer me?
--
You received this bug
@gjolly There were networking-related changes in systemd which could have
caused this but I also see that the kernel packages also changed between the
Azure images:
-ii linux-image-azure 5.8.0.1017.19+21.04.14
...
+ii linux-image-5.8.0-1022-azure 5.8.0-1022.24+21.04.2
#VERIFICATION GROOVY - kernel part
Installed kernel from -proposed, triggered a crash and opened dump with crash.
Crash opens dump successfully (patched version of crash required with commit
from description).
# crash usr/lib/debug/boot/vmlinux-5.8.0-1034-aws
** 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 crash in Ubuntu.
https://bugs.launchpad.net/bugs/1919275
Title:
crash utility fails on arm64 with cannot
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Caio Brandolim Rovetta (caiorovetta)
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Also affects: linux-oracle-5.4 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-oracle-5.4 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in:
#VERIFICATION FOCAL - kernel part
Installed kernel from -proposed, triggered a crash and opened dump with crash.
Crash opens dump successfully (patched version of crash required with commit
from description).
# crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws
** 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
+
Patches tested by Microsoft CIFS team.
** 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 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
*** This bug is a duplicate of bug 1928788 ***
https://bugs.launchpad.net/bugs/1928788
** This bug has been marked a duplicate of bug 1928788
linux-azure: Add Mana network driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
uploaded to b/f/g, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1919275
Title:
crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Status in crash package in
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
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
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
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 1928842
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
I am using a Dell SP2309W connected via HDMI to a Plugable UD-CA1A
docking station. The docking station is connected to my System76 Lemur
pro (lemp9) via USB-C. The highest resolution the external monitor can
run on is 1920x1080i and its native resolution of 2048x1152 is not
Public bug reported:
[Impact]
Kernel panic when doing rfkill block on Intel Bluetooth controller.
[Fix]
Ensure everything is stopped before calling the shutdown callback.
[Test]
Keep pressing the airplane mode button. High chance that a kernel splat
is shown and Bluetooth becomes unusable.
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
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
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
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
SAUCE patch:
"UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
- It looks like we can replace this
This grab wasn't as per the instructions, but was taken as soon as I saw
the request out of personal interest. I'm including it in case it is of
use. It did lead me to the following interesting links, but I've not had
time to see if there is anything useful to try that I haven't already
done yet:
Hi there,
Is there any update on this issue? I would like to understand who owns
the investigation/debugging process? Please tell us if you need any help
from the CPC team.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
This one was taken as per instructions on the next lock up. Having taken
it, when I was about to attach to this bug report the screen went again.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498494/+files/prevboot.txt
--
You
Another capture following the lock up immediately after the last.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5498495/+files/prevboot.txt
--
You received this bug notification because you are a member of Kernel
Packages, which
** No longer affects: amd
--
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/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
display not working,
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1923415
Title:
Hirsute update: v5.11.13 upstream
it's actually enough to test that a kernel installs on a clean chroot,
and I've tested bionic/focal/hirsute that they're fine now with the new
version
** Tags added: verification-done-hirsute
** Tags added: verification-done-focal
** Tags added: verification-done-bionic
--
You received this
The proposed package version is linux-kvm 5.4.0-1040.41
--
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/1925008
Title:
no memory hot-plugging in cloud-images
Status in cloud-images:
** Changed in: amd
Status: New => 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/1758364
Title:
add audio kernel patches for Raven
Status in amd:
Fix Released
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: amd
Status: New => Fix Released
--
You received
** Changed in: amd
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770271
Title:
VegaM support
Status in amd:
Fix Released
Status in linux package
Patches submitted https://lists.ubuntu.com/archives/kernel-
team/2021-May/120313.html
** Description changed:
SRU Justification
[Impact]
- Microsoft has requested the addition of the "mana" driver from Linux
- v5.11
+ Microsoft has requested the addition of the "mana" driver from Linux
(oh, and libnvidia-nscq-450 also has 460 .install file, this needs
cleanup)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1925522
Title:
Introduce the 465 driver series,
Public bug reported:
SRU Justification
[Impact]
Microsoft has requested the addition of the "mana" driver from Linux
v5.11
[Fix]
This patch set consists of 5 patches that are now in mainline.
The patches add the VF driver for Microsoft Azure Network Adapter
(MANA), and also changes the
updated kernel:
...
Setting up linux-image-5.4.0-1039-kvm (5.4.0-1039.40) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-5.4.0-1039-kvm
I: /boot/initrd.img is now a symlink to initrd.img-5.4.0-1039-kvm
...
unfortunately the kernel config is still not set:
root@ubuntu:~# grep -i
All autopkgtests for the newly accepted linux-base (4.5ubuntu3.3) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-oem-5.6/5.6.0-1057.61 (amd64)
Please visit the excuses page listed below and investigate the failures,
** Attachment added: "opal.esl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498450/+files/opal.esl
--
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/1903288
We should not add opal keys to the built_trusted_keys_keyring as that's
not the purpose of these keys. We could add them direct to .platform or
.ima keyrings, but it would be best to load them from firmware direct.
Are the above attached keys & ESL available from the "powerpc:db"?
--
You
** Attachment added: "opal-2019-ppc64el.pem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498449/+files/opal-2019-ppc64el.pem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "opal-2017-ppc64el.pem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903288/+attachment/5498448/+files/opal-2017-ppc64el.pem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Nayna Jain @Daniel
Hm but we have CONFIG_LOAD_PPC_KEYS=y already which I would expect
to be the only thing that loads keys into .platform keyring which was
enabled as part of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866909 LTC-184073
. Which keys are present in firmware / get
** 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1925008
Title:
no memory hot-plugging in
--- Comment From heinz-werner_se...@de.ibm.com 2021-05-18 06:27 EDT---
IBM bugzilla status->closed, Fix Released with 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-base - 4.5ubuntu7
---
linux-base (4.5ubuntu7) impish; urgency=medium
* Check for update-initramfs being installed before running the postinst
hook which updates the softlinks (LP: #1928700).
-- Stefan Bader Mon, 17 May 2021 17:55:34
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.4) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.4/5.4.0-74.83~18.04.1 (amd64)
makedumpfile/1:1.6.5-1ubuntu1~18.04.6 (i386)
Please visit the excuses
Still present on 5.12.4 as well
--
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/1926938
Title:
Recent mainline packages are built with Hirsuite 21.04, not Focal
20.04 LTS
Status in
1 - 100 of 124 matches
Mail list logo
