Here are the error messages from the log files:
Setting up linux-firmware (1.157.23) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-170-generic
E: amd64-microcode: unsupported kernel version!
E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
update-initramfs:
Make this a wildcard, "debian.master*", which
will allow us to build linux-libc-dev for hirsute forward-port kernels.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
--
You received this bug notification because you are a me
: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
option if we want to use
hibernation w/ kernels >= 5.6.
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are
** Tags removed: block-proposed
--
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/1896950
Title:
d2020.09.22 cycle tracker
Status in linux package in Ubuntu:
Confirmed
Status in
Public bug reported:
This bug is a cycle tracking bug for the d2020.09.22 development cycle.
** Affects: linux (Ubuntu)
Importance: Medium
Status: Incomplete
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-azure (Ubuntu)
Looks like you have a corrupted file. Try running the following in a
terminal:
$ sudo apt-cache clean
$ sudo apt install linux-firmware
This should force the file to be redownloaded.
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Looks like a problem generating a new initramfs:
update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic
mv: cannot stat '/boot/initrd.img-5.4.0-47-generic.new': No such file or
directory
I don't see any information about what went wrong though. The disk isn't
full, so that's not the
It's not just about installing different versions of linux-tools. libbfd
has no guarantee of a stable ABI/API, which makes it problematic for
external packages to link against them. Thus it is against policy to
link against libbfd in Ubuntu, and we simply cannot link perf against it
as long as
A fix for this has already been applied.
** Changed in: linux-kvm (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1894972
Title:
I was asked to provide some information about how to mount shiftfs, here
is an example.
$ mkdir lower mark mnt
$ sudo mount -t shiftfs -o mark lower mark
$ unshare -Urm
# mount -t shiftfs mark mnt
mnt will then be a shiftfs mount with ids shifted into the user ns
created by unshare.
--
You
** Changed in: linux (Ubuntu Groovy)
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/1893048
Title:
Groovy update: v5.8.4 upstream stable
The following patch from this stable update had already been applied:
of/address: check for invalid range.cpu_addr
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: M
These messages show up repeatedly in the journal:
Aug 19 21:33:11 ubuntu-x1 systemd[1]: Failed to start Process error reports
when automatic reporting is enabled.
Aug 19 21:33:11 ubuntu-x1 systemd[1]: apport-autoreport.service: Start request
repeated too quickly.
Aug 19 21:33:11 ubuntu-x1
I hadn't seen this bug before today when I noticed that it's blocking my
kernel in groovy-proposed. I upgraded systemd, and I am seeing this
issue. But when I boot back to 5.4.0-37 the problem persists, so it
doesn't seem to have anything to do with the 5.8 kernel.
It seems like a problem with
I should note, I did not update systemd in isolation. I can provide a
complete list of packages installed/upgrade at the same time if that is
helpful.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport (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.
** Changed in: linux (Ubuntu Groovy)
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/1892215
Title:
Groovy update: v5.8.2 upstream stable
** 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
+
ll make subprocess calls
tracepoint: Mark __tracepoint_string's __used
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Groovy)
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/1891647
Title:
Groovy update: v5.8.1 upstream stable
fects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu
5.8.0-16 is in groovy-proposed, please test and see if this fixes your
issues.
--
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/1891020
Title:
No IPv4 iptable kernel module can be loaded
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I saw the "Bad address" errors yesterday too, this problem should be
fixed by the 5.8.0-16 kernel which will appear in groovy-proposed very
soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can you load the modules using insmod? E.g. 'insmod
/lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/iptable_filter.ko'
--
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/1891020
It's been uploaded but is currently in the queue waiting for approval.
Once approved it's usually 7-10 days until it is released, assuming the
verification is done by then.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in
On Thu, Jul 16, 2020 at 02:48:00PM -, Andrew Stachura wrote:
> Is this fixed. I believe this is what is crashing my 20.04 LTS installer
> in during the final stages. Stuck with a non functioning distribution.
> Can you help?
I'm not sure if they've all been eliminated. However, these are only
Tested against -proposed kernels for xenial, bionic, eoan, and focal.
Tested against a suite of tests I wrote to exercise as many of the
interfaces as possible which are restricted by kernel lockdown, and also
tested against the applicable "American Unsigned Language" exploits [1].
Everything
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1886188
Title:
linux-libc-dev broken for
https://lists.ubuntu.com/archives/kernel-team/2020-July/111881.html
https://lists.ubuntu.com/archives/kernel-team/2020-July/111884.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
nee: (unassigned) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: linux-riscv (Ubuntu Focal)
Status: New => In Progr
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification be
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification be
gs mode
net_failover: fixed rollback in net_failover_open()
mlxsw: core: Use different get_trend() callbacks for different thermal zones
ipv6: fix IPV6_ADDRFORM operation logic
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: l
check for cycles (again)
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Tags: kernel-stable
** Description changed:
Impact: The lockdown patches have evolved over time, and part of this
was restricting more areas of the kernel. Not all of these additions
were backported, and some can lead to lockdown bypasses, see [1] and
[2].
Fix: Backport newer lockdown restrictions to
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: linux (Ubuntu Xenial)
Importance: Critical
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Critical
Assignee: Seth Forshee (sforshee
I don't know anything about that package. You should file a new bug
against that package so the maintainers of the package can help.
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
I think the answer here is to stop passing "console=ttyS0". This is
something that is typically only done for debugging.
dmesg shows a 14 second delay between the "console [tty1] enabled" and
"console [ttyS0] enabled" messages. I suspect that because console=ttyS0
is passed the kernel is going to
I confirmed that 5.4.0-29 does not show the problem, and -31 does. Then
I built -31 with these three patches reverted:
UBUNTU: SAUCE: overlayfs: fix shitfs special-casing
UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay
UBUNTU: SAUCE: overlayfs: allow with shiftfs as
On the surface this seems like a reasonable thing to do. However I think
someone from foundations should weigh in on the topic too.
--
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/1879454
Based on the video it looks like the first kernel messages which appear
on the screen have timestamps >20s, so it seems likely at least part of
the delay is in the kernel. If you can supply dmesg we might be able to
get some idea of where this delay is happening.
--
You received this bug
Sorry, I misread something before. I thought you were running 16.04 now.
You are running 14.04, so 3.13 is the correct kernel, it is not an "old"
kernel for that release.
Do you need to have casper installed? If not, the easiest thing to do
would be to uninstall casper, then run the upgrade
** Changed in: linux-firmware (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Changed in: linux-firmware (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I see two problems.
1. You have a very old kernel installed (3.13.0-38), which is causing
this message: "E: amd64-microcode: unsupported kernel version!" I'm not
sure if this is causing update-initramfs to fail, but if you don't need
this kernel you should just remove it.
2. These messages:
** Description changed:
+ SRU Justification
+
+ Impact: amdgpu references firmware files in modinfo which have not been
+ supplied to linux-firmware. This causes update-initramfs to generate
+ "Possible missing firmware" warnings.
+
+ Fix: Since the firmware is not available, all we can do is
AMD has not released this firmware to linux-firmware. For now all we can
do is remove the files from modinfo so that update-initramfs will stop
complaining.
** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status:
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-firmware (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
The firmware load messages are not unusual. The driver will try to load
a range of firmware versions, and often the "newest" version the driver
looks for has not been released by Intel. As long as it finds supported
firmware version (as indicated by the "loaded firmware version" message)
there's
Don't worry too much about what lspci says. It just has a database to
map PCI ids to names, and it currently considers anything with the id
8086:02f0 to be a 9462. The correct driver (iwlwifi) is being used, and
it identifies your wireless correctly, so that is what matters.
Can you please
The mailing list for i915 is intel-...@lists.freedesktop.org.
--
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/1872760
Title:
i915 - after return from suspend display is flickering
** Description changed:
+ 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
signed) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received thi
I think the upstream i915 developers might be able to best help you,
since the issue still exists in 5.7. I checked and this report looks to
be the same problem:
https://gitlab.freedesktop.org/drm/intel/-/issues/347
I'd suggest trying to help the developers debug the problem there.
Looks like
Fix sent: https://lists.ubuntu.com/archives/kernel-
team/2020-April/109405.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873506
Title:
ubuntu/focal64 fails to mount Vagrant
** Description changed:
- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount
- the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here
- is the Vagrant error message:
+ SRU Justification
+
+ Impact: When our kernel packaging was updated to build the
Assignee: (unassigned) => Seth Forshee (sforshee)
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, whic
I'm not sure that it's workload-specific, it could also be an issue with
a specific driver or any number of things. RCU is widely used in the
kernel, so at this point I'm looking for the proverbial needle in the
haystack. I am trying to uncover code paths that you might have been
exercising that I
nee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1872964
Title:
Reliable crash in lowlatency kernel with LXD
Status in linux-signed p
Please disregard comment #2. These warnings are related to preempt rcu,
which is only used in the lowlatency kernel.
This seems likely to be caused by an unbalanced
rcu_read_lock()/rcu_read_unlock() happening somewhere before the task
schedules.
--
You received this bug notification because you
When you see this in -24, is that still the lowlatency kernel or had you
switched it out for generic like you mentioned in the description?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Test build with the vsock options:
https://people.canonical.com/~sforshee/lp1873809/linux-
kvm-5.4.0-1008-kvm/
--
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/1873809
Title:
Make
Progress
** Changed in: linux-kvm (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Description changed:
+ SRU Justification
+
+ Impact: multipath-tools is installed by default in server images. With
+ the linux-kvm kernel, multipathd.service fails to start because we do
+
Because someone has to manually flip it once information has been
provided. Setting it to confirmed, buy you should also be able to do
that for your own bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
Can you try a vanilla 5.4.30 kernel from here, and see if it has the
same problem? That will let us know if any of the fixes we've applied on
top of 5.4 is responsible.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.30/
Note that you will need to disable secure boot to boot into this
Actually there is something in the logs that I missed the first time:
[ 69.108687] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR*
CPU pipe A FIFO underrun
Do you know whether earlier 5.4 kernels in focal also had this same
issue? If not, do you know the last version you used which
Oh, no that is fine then. Sorry, on the other bug you said the system
was unusable after suspend so I assumed that you could not run apport-
collect in that state.
Unfortunately the logs don't show anything strange happening.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
The attached logs are from the current boot, which doesn't show anything
from when the corruption actually happened. Can you get logs from a
previous boot where you did see the corruption? For example, if you know
this happened the last time you booted, you can use 'journalctl -b -1',
or
@arno can you file a new bug for this please? 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/1853044
Title:
5.3.0-23-generic causes fans to spin when idle
Status in linux
I'm not finding much in the logs. There's some i915 splat which could
possibly be related to the corruption, but nothing to explain the hard
lockup.
The current focal-proposed kernel (5.4.0-24) has some fixes for
races/deadlocks in i915, so it's worth trying that out to see if it
helps. You can
@Anmar, I believe this issue should be fixed now. Can you confirm?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1861462
Title:
Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend
Confirmed that I'm no longer seeing the segfault. Thanks!
** Changed in: llvm-toolchain-10 (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-gcp (Ubuntu)
Status: Confirmed => Invalid
--
You
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-oracle (Ubuntu)
Status: Confirmed => Invalid
--
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-azure (Ubuntu)
Status: Confirmed => Invalid
--
You rebuilt the package with a different compiler than what was used to
compute the signatures/checksums in the kernel build, so you get
different objects and mismatching checksums. This is expected.
** Changed in: linux-restricted-modules-aws (Ubuntu)
Status: Confirmed => Invalid
--
You
Thanks for testing. I've applied the patches to focal/master-next.
--
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
Thanks for testing. I've applied the patches to focal/master-next.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
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
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,
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
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
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:
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
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
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
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
This is noted on the other bug, but I'll also note it here. This kernel
is *not* signed with the archive key. The public half of the key pair
used to sign this build can be found in this tarball:
http://ppa.launchpad.net/sforshee/lp1866909/ubuntu/dists/focal/main/signed
Build is done now, version 5.4.0-21.25+lp1866909v202004020814 in
https://launchpad.net/~sforshee/+archive/ubuntu/lp1866909/+packages.
--
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
Patch one is included on the test build for bug 1866909 in
https://launchpad.net/~sforshee/+archive/ubuntu/lp1866909/+packages. I
incorporated the config changes in with those requested for that bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => 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)
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/1867587
Title:
[sas-0316]sync mainline kernel 5.6rc1 roce
** 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/1869947
Title:
Revert "nvme_fc: add module to ops template to
Note that it is still building, should be ready in a few hours. I'll
post an update when it is done.
--
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
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1856900
Title:
stress-ng sysinfo stressor fails on ppc64el with
I don't see that the sysinfo stressor runs at all in the logs for
5.4.0-21:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200331_002447_e28f4@/log.gz
--
You received this bug notification because you are a
101 - 200 of 3458 matches
Mail list logo
