reading old modules...
MISS: vboxguest (ignored)
MISS: vboxsf (ignored)
In the current kerenl. So it appears that building with a dkms module got
dropped, and yet the guest modules from upstream code have not been built
either.
And i am able to reproduce
linux (5.4.0-87.98) focal; urgency=medium
* please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248)
- [Config] Disable virtualbox dkms build
Disabled do_dkms_vbox, because src:virtualbox got srued into Focal which no
longer provides virtualbox-guest-dkms
I fear/wonder
I was not expecting for focal/linux to change. This change was expected
to be done in impish/linux only.
How can I figure out why this was done in focal/linux?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Uploaded new dwarves-dfsg SRUs that use embeded libbpf (which in turn is
updated to the same source as used in impish).
This makes dwarves-dfsg SRU stand-alone, without introducing or
upgrading the system-wide libbpf.
** Changed in: libbpf (Ubuntu Focal)
Status: Confirmed => Won't Fix
**
** Changed in: linux-hwe-5.13 (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux-hwe-5.13 (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Description changed:
+ [Impact]
+
+ * Due to disk space constraints previously hwe-5.11 disabled building
+ dbgsyms packages
+
+ * This has been resolved in hwe-5.13, thus builds with debug symbols
+ can be re-enabled
+
+ [Test Plan]
+
+ * Build new kernel, check that dbgsyms packages
** Also affects: linux-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939287
Title:
dbgsym package is missing for
** Description changed:
[Impact]
* Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
* Unable to use LED colors
* Unable to mmap PCI resources
* Cherrypick dtb changes from meta-sifive 2021.08 release
** Description changed:
[Impact]
- * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
- * Unable to use LED colors
- * Unable to mmap PCI resources
+ * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
+ * Unable to use LED colors
+ *
extensions, which is a step backwards.
OpenSBI v0.1 will not be available in the future.
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Dimitri J
The security PPA where 5.11.0-27 was built has "build dbgsyms" checked
but not "publish dbgsyms" this seems odd, cause i would think it is
useful to have access to published security ppa dbgsymbols.
Removing debug symbols is not nice. However, surely we can make disk
space savings the other way.
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: linux-hwe-5.11 (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages,
Imho we must enabled it, especially for Oracle, since compute nodes may
be shared between multiple tenants.
It would be also interesting to check if the hardware used with this
kernel does not have errata / issues discussed in
https://www.spinics.net/lists/arm-kernel/msg788470.html i.e. that it
# grep CODENAME /etc/os-release
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
# uname -r
5.11.0-34-generic
dmesg:
[0.797134] blacklist: Loading compiled-in revocation X.509 certificates
[0.797696] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/7
** 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.
Public bug reported:
When booting with UEFI, mokvar table and %:.platform keyring must be
available
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm
# uname -r
5.11.0-34-generic
# sudo keyctl list %:.platform
3 keys in keyring:
149920180: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA
2011: a92902398e16c49778cd90f99e4f9ae17c55af53
434591909: ---lswrv 0 0 asymmetric: Canonical Ltd. Master Certificate
Authority:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/6
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Verifying using hirsute:
# uname -r
5.11.0-1014-kvm
# grep CODENAME /etc/os-release
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
# keyctl list %:.blacklist
Can't find 'keyring:.blacklist'
Upgraded kernel:
# uname -r
5.11.0-1015-kvm
# keyctl list %:.blacklist
1 key in keyring:
330780907:
Disabled initrd less boot, and installing linux-generic kernel from
proposed.
--
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/1928679
Title:
Support importing mokx keys into revocation
for failed results, in artifacts, all make.logs are stored and available
for download and inspection.
** Changed in: dkms (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: apport-collected
--
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/1936237
Title:
use the upstream
** No longer affects: linux-riscv (Ubuntu)
--
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/1941622
Title:
Bump unmatched CPU clock rate to 1.5GHz
Status in u-boot package in
Public bug reported:
[Impact]
Bump unmatched CPU clock rate to 1.5GHz
Multiple users report that running unmatched at 1.5GHz is stable, and
gives one performance.
Lets bump clock speed to 1.5GHz in u-boot and kernel.
[Test Plan]
* System with these patches boots, operates normally without
** Changed in: linux-restricted-modules-gcp-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-gcp-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941610
Title:
** Changed in: linux-restricted-modules-oracle-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-oracle-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941612
** Changed in: linux-restricted-modules-aws-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-aws-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941608
Title:
Public bug reported:
oracle 5.11.0-1015 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
oracle-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64
linux-modules-nvidia-390-5.11.0-1015-oracle
Public bug reported:
gcp 5.11.0-1016 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
gcp-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64:
linux-modules-nvidia-390-5.11.0-1016-gcp
Public bug reported:
aws 5.11.0-1015 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
aws-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64:
linux-modules-nvidia-390-5.11.0-1015-aws
[10052.121189] rcu: INFO: rcu_sched self-detected stall on CPU
[10052.126125] rcu: 1-: (14995 ticks this GP)
idle=a3a/1/0x4002 softirq=116019/116019 fqs=7426
[10080.057250] watchdog: BUG: soft lockup - CPU#1 stuck for 82s!
[ftracetest:30662]
[10124.057368] watchdog: BUG:
** Description changed:
$ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests
...
# [32] ftrace - Max stack tracer [FAIL]
...
+ Testing using 5.13.0-1002.2
- Testing using 5.13.0-1002.2
+ the full ftrace suite takes just over 2 hours on unmatched.
--
You received
Public bug reported:
$ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests
...
# [32] ftrace - Max stack tracer[FAIL]
...
Testing using 5.13.0-1002.2
the full ftrace suite takes just over 2 hours on unmatched.
** Affects: ubuntu-kernel-tests
Importance: Undecided
** Also affects: linux-riscv-5.11 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-riscv-5.11 (Ubuntu Hirsute)
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: New => Invalid
** Changed in: linux-riscv-5.11 (Ubuntu Focal)
Status: New => Confirmed
** Also affects: linux-riscv (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-riscv-5.11 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-riscv (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: linux-riscv-5.11 (Ubuntu
Public bug reported:
[Impact]
* A kernel build can fail to boot with Oops and illegal instruction as
seen at https://bugs.launchpad.net/ubuntu/+source/linux-
riscv-5.11/+bug/1934548 on Unmatched board.
* One cannot frace functions, used in frace setup. On RISC-V these are
sbi calls to
backports is no good, as it needs to be kernel's build-dep. and most
kernels are built in -security only pocket.
also, nothing else really uses these, apart from kernel. And kernels
have stop using these, because they are too old in focal.
** Changed in: dwarves-dfsg (Ubuntu Focal)
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks
** Tags added: hirsute impish patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load
Public bug reported:
08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
08/12 22:10:51 DEBUG|
*** This bug is a duplicate of bug 1900644 ***
https://bugs.launchpad.net/bugs/1900644
** Summary changed:
- ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
+ ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
mailing multi_check_sendfile
--
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/1939887
Title:
ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute &
focal
Status in ubuntu-kernel-tests:
New
v5.13 in impish-proposed has this fixed on riscv.
it will not be backported to earlier series, hence marking hirsute as
wontfix.
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in:
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: focal riscv64
** Summary changed:
- selftests net times out
+ ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
--
You received this bug notification because you are a
Focal
ubuntu@ubuntu:~$ dmesg | grep gcc
[0.00] Linux version 5.11.0-1017-generic
(buildd@riscv64-qemu-lcy01-062) (gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0,
GNU ld (GNU Binutils for Ubuntu) 2.34) #18~20.04.1-Ubuntu SMP Thu Aug 12
00:38:00 UTC 2021 (Ubuntu
Public bug reported:
872621:59:37 INFO | Timer expired (1800 sec.),
nuking pid 10418
872721:59:38 INFO | ERROR
ubuntu_kernel_selftests.netubuntu_kernel_selftests.net
timestamp=1628805578localtime=Aug 12 21:59:38
Hirsute:
$ uname -a
Linux ubuntu 5.11.0-1017-generic #18-Ubuntu SMP Wed Aug 11 18:02:14 UTC 2021
riscv64 riscv64 riscv64 GNU/Linux
$ systemctl is-system-running
running
$ sudo dmesg | grep gcc
[0.00] Linux version 5.11.0-1017-generic
(buildd@riscv64-qemu-lcy01-065) (gcc (Ubuntu
** Changed in: linux-riscv (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: linux-riscv (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-riscv-5.11
@cascardo it works
https://lists.ubuntu.com/archives/kernel-team/2021-August/123090.html
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-riscv (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-riscv-5.11 (Ubuntu)
Public bug reported:
[ 15.446646] fu740-pcie e.pcie: invalid resource
[ 15.792898] L2CACHE: DataError @ 0x0008.04B0
[ 16.630923] da9063 0-0058: Chip variant not supported for DA9063
[ 16.746772] macb 1009.ethernet: GEM doesn't support hardware ptp.
[FAILED] Failed to
https://people.canonical.com/~xnox/lp1934548/
findings published at above location. I am giving up at this point and
need to handover to someone else.
Is there a way to attach gdb over jtag to unmatched board whilst it is
attempting to boot?
Is there a way to analyze the vmlinuz image to figure
*** This bug is a duplicate of bug 1934548 ***
https://bugs.launchpad.net/bugs/1934548
** This bug has been marked a duplicate of bug 1934548
RISC-V: Illegal instruction
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Something like this https://github.com/snapcore/core-
initrd/pull/34/files should do it. Plus respinning the pc-kernel arm64 &
armhf kernel snaps.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
$ git grep virtio_blk
features/server/usr/lib/modules-load.d/ubuntu-core-server.conf:virtio_blk
When building initrd into the generic arm64 kernel snap, we should
enable feature "server" like we do on x86.
--
You received this bug notification because you are a member of Kernel
Packages, which
Doing this in "kernel-snaps-uc20" git repo would be tricky, as at the
moment we don't pass any option when making kernel snaps.
Otherwise core-initd itself defaults to "main server" on x86, but just
"main" on all other arches. Maybe we should enable "server" features for
"generic" kernel flavours
added more pr_info calls inside ftrace_update_code.. and things boot
now for me. =
--
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/1934548
Title:
RISC-V: Illegal
[0.00] XNOX kernel/trace/ftrace.c(6255) ftrace_process_locs:
[0.00] XNOX kernel/trace/ftrace.c(6272) ftrace_process_locs:
[0.00] Oops - illegal instruction [#1]
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1015-generic
I am failing to reliably reproduce this issue.
At first I have experienced this too. When I tried to bisect it and install
multiple kernel abis they are all booting fine.
So I was able to fail booting 1014 1015 1016 abis. And then they started
to boot fine.
I wonder if there is some
** Package changed: ubuntu => linux-riscv-5.11 (Ubuntu)
--
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/1934548
Title:
RISC-V: Illegal instruction
Status in linux-riscv package in
Public bug reported:
linux-riscv-5.11 1015 panics on unmatched
[0.00] SBI specification v0.2 detected
[0.00] SBI implementation ID=0x1 Version=0x9
[0.00] SBI v0.2 TIME extension detected
[0.00] SBI v0.2 IPI extension detected
[0.00] SBI v0.2 RFENCE
insecure W+X mapping is fixed in v5.13 series and in impish.
the changes to fix those will not be backported to hirsute, hence marking this
bug as fix released.
The kernel panics that is shown in the pastebin is unrelated to the
insecure W+X mapping.
** Changed in: linux-riscv (Ubuntu)
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Patch removed: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
** Patch added: "chmod-reference.patch"
** Patch added: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: bash (Ubuntu)
Status: New => Invalid
** Changed in: dash (Ubuntu)
Status: New => Invalid
** Changed in: debhelper (Ubuntu)
Status: New => Triaged
** Changed in: debugedit (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New
Based on https://elixir.bootlin.com/linux/latest/source/fs/inode.c#L1928
it seems that setuid and capabilities will be stipped, thus currently
our implementation of dh_strip causes to loose setuid and capabilities.
No idea why this is working with fakeroot when Rules-Requires-Root is set to
separately I'm not sure who/what/why stips setuid bits on file creation
through redirect.
is it like some kind of a CVE in bash/dash? kernel protection?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
- objcopy/strip changed in 2.36.1, not keeping file attributes of the
original file. Work around that in dh_strip to write to a temporary
file and cat'ing this to the original file to keep the original
attributes.
which is broken for setuid files.
** Also affects: dash (Ubuntu)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
lttng-modules 2.12.5-1ubuntu2~21.04.1 in hirsute-proposed unapproved
queue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
lttng-modules/2.12.2-1ubuntu1~20.04.2
$ dpkg-query -W wireless-regdb
wireless-regdb 2021.07.14-0ubuntu1~18.04.1
$ sudo iw reg set 00
$ sudo iw reg get
global
country 00: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20),
It's pure datafiles arch:all package without any runtime deps, thus it
is safe to copy to -security as is.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1936255
Title:
New
I wonder if we should really just do binary copies of it, just like we
do with shim. If we set it to be compressed with xz.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1936255
On Tue, 27 Jul 2021, 05:45 Brian Murray, <1923...@bugs.launchpad.net>
wrote:
> I'm sorry to be a bother here but I don't understand how u-boot failed
> verification for hirsute but passed for focal when what are presumably
> the same patches exist in both versions of the package. How could this
>
** Changed in: broadcom-sta (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932160
Ti
** Changed in: lttng-modules (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: lttng-modules (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: lttng-modules (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received
** Changed in: bcmwl (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1932159
Title:
bcmwl/6.30.223.
** Changed in: rtl8812au (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932169
Ti
** Changed in: xtables-addons (Ubuntu Focal)
Assignee: Tim Gardner (timg-tpi) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932173
Ti
** Changed in: bcmwl (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: bcmwl (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
** Changed in: broadcom-sta (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: broadcom-sta (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
** Changed in: rtl8812au (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: rtl8812au (Ubuntu Focal)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
** Changed in: xtables-addons (Ubuntu Focal)
Milestone: None => ubuntu-20.04.3
** Changed in: xtables-addons (Ubuntu Focal)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
1.9.1-1ubuntu4~21.04.1 supersedes 1.9.1-1ubuntu3~21.04.1 to fix adt
failure on s390x.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932163
Title:
Please provide SRU paperwork as per
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
** Attachment added: "lttng-modules_2.12.5-1ubuntu1~20.04.2_source.changes"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5512591/+files/lttng-modules_2.12.5-1ubuntu1~20.04.2_source.changes
--
You received this bug notification because you are a member of
** Patch added: "corrected.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5512590/+files/corrected.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
Sponsored evdi_1.9.1-1ubuntu4_source.changes to impish.
** Changed in: evdi (Ubuntu Focal)
Status: Fix Committed => Confirmed
** Changed in: evdi (Ubuntu Focal)
Assignee: Thadeu Lima de Souza Cascardo (cascardo) => (unassigned)
** Changed in: linux-hwe-5.11 (Ubuntu)
Status:
evdi debdiff is good, but it must go into other series too.
https://autopkgtest.ubuntu.com/packages/evdi
Looks like that change is needed in impish, hirsute and focal.
One cannot introduce brand new change in a focal SRU with a version
number higher than all future series.
** Changed in: evdi
Changelog entries in the #3 debdiff are in the wrong order.
The 2.12.2-1ubuntu1~20.04* entreis should be just above the other 2.12.2
entries.
Such that when build is done with -v2.12.5-1ubuntu1~20.04.2 all
changelog entries since 2.12.2 are included, i.e. all the v2.12.5 from
impish and etc.
Impish is not affected, as it still skips fdtdir under qemu completely.
--
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/1923162
Title:
riscv64 images fail to boot in qemu
Status
Oh https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu9.1
is an orphan, as it did not make it into impish.
--
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/1923162
Title:
$ dpkg-query -W u-boot-qemu
u-boot-qemu 2021.01+dfsg-3ubuntu9.1
$ qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
device,netdev=eth0 -netdev
Trying to see if impish u-boot is also broken at the moment.
--
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/1923162
Title:
riscv64 images fail to boot in qemu
Status in
Public bug reported:
Over at https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1932158
you can observe that it was chosen to skip the dkms module for a given
kernel, and dkms-autopkgtest did not manage to handle it well.
** Affects: dkms (Ubuntu)
Importance: Undecided
** Description changed:
[Impact]
BTF is an extremely useful tool for BPF developers. Enabling BTF support
- in the kernel requires pahole 1.16 or later, but in focal we have only
- 1.15. The simplest path for us to get a sufficiently updated version of
- pahole is to backport dwarves-dfsg
@jawn-smith https://paste.ubuntu.com/p/hjqFz46frm/ is what i'm
sponsoring, after fix ups.
--
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/1923162
Title:
riscv64 images fail to boot
re: u-boot-menu backport, imho the debian/changelog should be merged and
focal entries should not be lost.
--
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/1923162
Title:
riscv64
Re: u-boot-menu backport, imho debian/changelog should have documented
that debhelper-compat version is lowered from 13 to 12, to make it build
on focal. But also it is self-explanatory (i did try to get debhelper 13
into focal before it released, but that upload got rejected).
Otherwise no
701 - 800 of 1812 matches
Mail list logo
