Public bug reported:
Freshly deployed equal machines with flat disk layout as configured by
MAAS, performance governor changed from ondemand to performance.
Bionic (4.15.0-101-generic) fio ext4 on spinning rust:
Run status group 0 (all jobs):
WRITE: bw=1441MiB/s (1511MB/s), 1441MiB/s-1441MiB/s
Note that to rule out any hardware configuration/malfunction issue
between the two hosts I have re-run the tests on the exact same machine
used for the non-performant Focal tests with good performance for
Bionic.
--
You received this bug notification because you are a member of Kernel
Packages, w
Thank you for the suggestion to test mainline.
Regarding the kernel parameters: The test is run on the host and not in
a virtual machine, for completeness I have removed the iommu and vf
related kernel parameters and they do not affect the outcome of the
test.
Unfortunately using the mainline ker
That is an excellent idea.
Before embarking on that endeavor I did a last control test which
involved deploying Bionic and then installing the Focal 5.4 kernel
packages, and lo and behold the system is still performant.
Redeploying Focal (with the Focal kernel obviously) makes it non-
performant
For any future travelers this issue was caused by the much debated
ext4lazyinit "feature".
# iotop
Total DISK READ: 0.00 B/s | Total DISK WRITE: 0.00 B/s
Current DISK READ: 0.00 B/s | Current DISK WRITE: 7.38 M/s
TID PRIO USER DISK READ DISK WRITE SWAPIN
We have been using the ext4lazyinit for quite some time, so I guess this
must be a combination of multiple things.
I see that the 5.4 kernel brings a change of io scheduler to mq-
deadline.
Could the combination of ext4lazyinit+mq-deadline+rotational drives be a
problem?
--
You received this bu
Playing around with the now available IO schedulers does not appear to
help much and looking at iotop while the test runs does show
ext4lazyinit consuming much of the IO most of the time while the test
runs.
I wonder if this is a more ominous change of behavior after all
Total DISK READ:
I'm seeing this too, so far it has not rendered my system unbootable
though.
I have been running with ZFS as root filesystem since Bionic and have
upgraded through Disco and the issue first appeared in an update
arriving after upgrading to Eoan.
Setting up zfsutils-linux (0.8.1-1ubuntu10) ...
zfs
A workaround to get the dependencies installed on upgrade would be:
$ sudo systemctl mask zfs-mount
$ sudo apt -f install
$ sudo systemctl unmask zfs-mount
After a reboot the ``zfs-mount`` service stays in a failed state, I wonder if
something else has taken on its duties and there is a conflic
Public bug reported:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would like
to put a Optane
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/1910201
Title:
bcache: overflow in stripe number calculations fo
** Description changed:
Ubuntu Focal
ga kernel
This problem was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
Using the linux-generic-hwe-20.04-edge packages resolves the issue.
We hit this while exploring storage options for PS5 where we would
Marking as fix released for MAAS as artifacts to deploy Focal with
hwe-20.04-edge kernel are now available.
** Changed in: maas
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://bu
I can confirm that the proposed ubuntu-fan package resolves the issue.
If you are deploying with Juju and MaaS the Ubuntu proposed repository
can be installed automatically on the nodes deployed by MaaS. This could
be used as a temporary workaround for the issue.
Example for how it could be set u
As much as I want the -22 to fix all problems, it does not.
However, my crashes does currently not leave a trace in the logs.
Sticking to -13 keeps my workhorse running riddled of any crash or
freeze problems.
The simplest way to describe what is going on is that all I/O gets stuck
and that my di
This problem has surfaced again with recent MAAS Ubuntu images. One
report in bug 1701297. I have information about at least two other end
users hit by the problem.
Adding a workaround by setting apparmor=0 kernel parameter in MAAS 2.2
will not help users that are running previous versions.
@jdst
@andreserl
There are severe security implications of doing 2) from now until all
future, and unfortunately I have seen that this is being done in the
wild.
I would be much more comfortable by actually finding the root cause of
the issue at hand and fixing that.
This is what I am currently pursui
Public bug reported:
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311]
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30
kHz
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0:
DRM: native mode from largest: 1920x1080@60
Jan 10 18:56:
In my case setting hdmimhz=297 did the trick.
Hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M
Mac Edition] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition]
Flags: bus master, fast devsel, late
apport information
** Package changed: linux (Ubuntu) => linux-lts-xenial (Ubuntu)
** Tags added: apport-collected xenial
** Description changed:
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311]
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30
kHz
Jan
Thank you!
Having built a test kernel there does seem to miss something to make
everything work right on my system. I suspect EDID decode issues. Will
try to hunt down what the missing piece is and see if we can include
that as well. Failing that I do believe this would be useful in its own
right,
This patch is already in Yakkety kernel. It will also be released as a
part of the Xenial HWE kernel in Ubuntu Xenial 16.04.2.
Marking this bug as Invalid for Yakkety and Xenial and direct interested
parties to the Xenial HWE kernel.
Prior to its release in February 2017 it can be tested by insta
Public bug reported:
During high traffic these messages appear in dmesg.
I believe this has been fixed with this patch:
https://patchwork.ozlabs.org/patch/477200/
Backport potential?
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "apport.linux-i
The logs you request was attached manually to the original bug report.
I am unable to have the automatic tools do this for me as we are running
a IPv6-only DC and the endpoints used have no IPv6 address.
Please let me know what, if anything, is missing from the attached
log/report.
** Changed in
Thank you for your prompt response! I will put this kernel on one of the
servers displaying the behaviour and run through operations we know
triggers the message. I will report back to you after the weekend.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Long story short there is a regression that affects the datapath of Open
vSwitch based systems starting with the 6.2 kernel which is fixed by
[0].
0:
https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/
** Affects: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Expired => 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/1987269
Title:
[5.18.0 mainline] mlx5 deadlock
Status in linux package
Thanks a lot for checking, Itai!
As discussed offline, we made another attempt with 5.19.0-28-generic
kernel and 22.35.2302 firmware on a different system, and also did not
run into this issue there.
Will set this to incomplete until we regain access to the system where
this was first observed so
** Changed in: linux (Ubuntu)
Status: Expired => 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/1987618
Title:
[jammy mlx5] Slow outbound N/S TCP connections for instances
** Changed in: linux (Ubuntu)
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.
https://bugs.launchpad.net/bugs/2009063
Title:
Consistent autopkgtest failures in xdp-tools luna
Public bug reported:
System running 5.13.0 kernel, OFED 5.4.3, OVS 2.16 and OVN 21.09.
ConnectX-5 with firmware=16.31.2006
Hardware offload enabled.
Ports bonded (VF LAG enabled).
Security Groups enabled (i.e. CT offload).
When the system is the active gateway chassis for a logical OVN router,
i.
** Attachment added: "br-int-flows.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537900/+files/br-int-flows.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537898/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537897/+files/version.log
--
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/194
** Attachment added: "dpctl-dump-flows.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949609/+attachment/5537899/+files/dpctl-dump-flows.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
** Changed in: openvswitch (Ubuntu Impish)
Status: New => Won't Fix
** Changed in: ovn (Ubuntu Impish)
Status: New => Won't Fix
--
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
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename: jammy
$ uname -a
Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun
May 22 20:33:46 UTC 2022 x86_64 x86_64
Public bug reported:
Charmed OpenStack on Jammy.
Hardware offloaded instances that reside on the hypervisor which is also
the active OVN gateway for their network have degraded connectivity.
$ time wget --debug -O /dev/null http://nova.clouds.archive.ubuntu.com/ubuntu/
Setting --output-document
fwiw; the fix is somewhere to be found in these mainline commits:
b070e70381ee343dc10d2b1f0f3a6b1f940f0ae5
7843bd604081b5f005b31343cde1bb680bcc1776
2a829fe25d2809a33a6842359323bb139556c03d
a81283263bb0c38b52fce6d599c2434a8d232dd6
8300f225268be9ee2c0daf5a3f23929fcdcbf213
314e1105831b45a0fe3045411d7f
The fix for the issue boils down to these commits:
314e1105831b net/mlx5e: Add post act offload/unoffload API
8300f225268b net/mlx5e: Create new flow attr for multi table actions
a81283263bb0 net/mlx5e: Use multi table support for CT and sample actions
2a829fe25d28 net/mlx5e: TC, Clean redundant co
Public bug reported:
During system initialization there is a specific sequence that must be
followed to enable the use of hardware offload and VF-LAG.
Intermittently one may see that VF-LAG initialization fails:
[Thu Jul 21 10:54:58 2022] mlx5_core :08:00.0: lag map port 1:1 port 2:2
shared_
Public bug reported:
# sudo lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename: jammy
# mlxfwmanager
Querying Mellanox devices firmware ...
Device #1:
--
Device Type: ConnectX6DX
Part Numb
** Attachment added: "syslog-kernel.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+attachment/5635244/+files/syslog-kernel.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Attachment added: "apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999229/+attachment/5635245/+files/apport
--
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/1999229
Titl
Looks like there are two issues here, after removing the bond, we still
see the syndrome message, and traffic to instances is impacted:
[Fri Dec 9 10:28:37 2022] mlx5_core :41:00.1: mlx5_cmd_out_err:778:(pid
3334): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad
resource(0x5), sy
Attaching the kern.log from previous boot which shows the issues.
** Attachment added: "kern.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513187/+files/kern.log.1
--
You received this bug notification because you are a member of Kernel
Packages, w
Public bug reported:
After upgrading from linux-firmware 1.198 to 1.199 my connectivity
became unstable and I could see repeating hardware resets in `dmesg`
output.
Downgrading to linux-firmware 1.198 again resolved the issue.
Note: this bug was filed after downgrading the package, but hopefully
Apparently the kern.log just shows boot, adding syslog excerpt with the
kernel messages
** Attachment added: "syslog-excerpt.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1937415/+attachment/5513209/+files/syslog-excerpt.txt
--
You received this bug notification because
Circling back to this, I did make an attempt with linux-firmware 1.198
as base and then copying in just the firmwares that appeared relevant to
the hardware in question from 1.199. However I was no longer able to
reproduce the issue.
Now I have installed the 1.199 package again and I have had no i
Public bug reported:
Originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1783075
The problem is fixed in the 5.8 kernel, but we would need this fixed for
the 5.4 kernel as well.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: ps5
** Tags a
On further diagnosis we discovered that this is probably already in our
packages.
** Changed in: linux (Ubuntu)
Status: New => 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
*** This bug is a duplicate of bug 1908351 ***
https://bugs.launchpad.net/bugs/1908351
** This bug has been marked a duplicate of bug 1908351
SR-IOV, don't do runtime reconfiguration and make use of PCI address matching
--
You received this bug notification because you are a member of Ker
Note that for the log references where the autopkgtest runs using a 6.1
kernel, there appears to be a regression in the kernel. I can reproduce
those locally and the problem goes away when upgrading to a mainline
6.2.0-060200.202302191831 kernel.
** Also affects: linux (Ubuntu)
Importance: Unde
** Attachment added: "apport-bug output as per linux kernel bug procedure
requirements"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+attachment/5651265/+files/2009063.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
** 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/2009063
Title:
Inconsistent autopkgtest failures in xdp-tools lunar am
** 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/2009594
Title:
Mlx5 kworker blocked Kernel 5.19 (Jammy HWE)
Status in
This does indeed appear to be a serious issue, but it is unfortunately
not a charm issue.
It appears to me to be an issue with the mlx5 driver in the kernel which
is visible in this specific environment for yet to be uncovered reasons.
** Changed in: charm-ovn-chassis
Status: New => Invali
Excellent work on finding more information about the cause and a
workaround, thank you for that!
I think it would be appropriate to tackle this as part of the resolution
of netplan.io bug 1988018 though, so the charm task would still be
invalid unfortunately.
--
You received this bug notificatio
However, it will probably take some time to resolve bug 1988018 so we
should probably look into what interim solutions the charm could provide
until we get there.
** Changed in: charm-ovn-chassis
Status: New => Triaged
** Changed in: charm-ovn-chassis
Importance: Undecided => High
--
)
Status: Confirmed => Fix Committed
** Changed in: xdp-tools (Ubuntu)
Status: Triaged => Invalid
** Changed in: xdp-tools (Ubuntu)
Assignee: Frode Nordahl (fnordahl) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages,
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2040524
Title:
openvswitch fails on raspberry pi 4
Public bug reported:
The linux-tools-common package appears to provide a shell script with a
wrapper that will execute the actual bpftool binary located in a
location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool
This causes problems for Lunar builds of xdp-tools on Launchpad [0]
because the
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647157/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647158/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647159/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647161/+files/Lspci-vt.txt
--
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/20
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647160/+files/Lspci.txt
--
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/2007308
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647162/+files/Lsusb-v.txt
--
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/2007
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647164/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647166/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647165/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "NonfreeKernelModules.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647163/+files/NonfreeKernelModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647167/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2007308/+attachment/5647168/+files/UdevDb.txt
** Description changed:
The linux-tools-common package appears to provide a shell script with a
wrapper that will execute the actual bpftool binary located in
** Also affects: xdp-tools (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.
https://bugs.launchpad.net/bugs/2007308
Title:
linux-tools-common: bpftool wrapper causes b
@cjwatson thanks alot for chiming in on the issue. I added Launchpad,
because I was unsure what part Launchpad has in the massaging of
dependencies on the Debian import, and if something could be done there.
Unfortunately even if the host had a 5.15 kernel, there is no 5.15
package in Lunar.
The l
** Patch added: "xdp-tools_1.3.0-2ubuntu1.patch"
https://bugs.launchpad.net/ubuntu/+source/xdp-tools/+bug/2007308/+attachment/5649048/+files/xdp-tools_1.3.0-2ubuntu1.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
I think they are two distinct problems, and hopefully we would get a
comment from NVIDIA/Mellanox as the statements in bug 2020409
contradicts the documentation [0] the current Netplan implementation is
based on.
Martin may have more details, but wanted to mention that one of our suspected
culpri
Public bug reported:
$ uname -a
Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Kinetic Kudu (development branch)
Rel
apport information
** Tags added: apport-collected kinetic
** Description changed:
$ uname -a
Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distrib
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623315/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623316/+files/IwConfig.txt
--
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/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623317/+files/Lspci.txt
--
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/1992564
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623314/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623323/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623325/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623318/+files/Lspci-vt.txt
--
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/19
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623320/+files/Lsusb-t.txt
--
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/1992
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623321/+files/Lsusb-v.txt
--
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/1992
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623322/+files/PaInfo.txt
--
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/1992564
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623324/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623328/+files/RfKill.txt
--
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/1992564
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623329/+files/UdevDb.txt
--
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/1992564
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623331/+files/acpidump.txt
--
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/19
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623330/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623327/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623326/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1992564/+attachment/5623319/+files/Lsusb.txt
--
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/1992564
For completeness, I can confirm this also happens with the 5.19.0-20
kernel currently in -proposed.
** Summary changed:
- [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working
+ [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block
device not working
*** This bug is a duplicate of bug 1991691 ***
https://bugs.launchpad.net/bugs/1991691
** This bug has been marked a duplicate of bug 1991691
cannot change mount namespace
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
1 - 100 of 121 matches
Mail list logo
