I looked into this a few months ago for slightly different reasons
(juju/maas getting confused and not identifying a disk, due to differing
kernels used for install vs boot), I can confirm I found at the time
that the nvme by-id symlinks change due to backporting of the
NVME_QUIRK_BOGUS_NID quirk.
*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281
** This bug has been marked a duplicate of bug 1823281
perf-archive is not shipped in the linux-tools package
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/203409
Submitted upstream for review:
https://lore.kernel.org/all/20230927075713.1253681-1-trent.ll...@canonical.com/T/#u
--
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/2034099
Title:
Bridge MT
eth2 configuration exists in the other files, if so, remove
that.
grep eth2 /etc/netplan/ -Ri
cat >> /etc/netplan/60-br0.yaml < Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a
A bunch of fixes for this card have gone in. I'd make sure you are using
the 5.15 HWE kernel on focal if anyone has issues with this card.
--
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/199
** Description changed:
Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
no traffic flow and produce error messages in both the host and guest
during network configuration.
Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04
** Description changed:
Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get
no traffic flow and produce error messages in both the host and guest
during network configuration.
Environment: Ubuntu OpenStack Focal-Ussuri with OVN
Host Kernel: v5.15.0-41-generic 20.04
For users of i40e, seems this depends on the following host patch where the
max_mtu from the host PF that is now used was not set on i40e (but was for ice).
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc
It's also queued for stable. We may want to pull this at t
The patch has now made it upstream into the v6.0-rc7 release:
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
It has also been pushed to the stable-queue for the upstream 5.4 and 5.15
kernels:
https://www.spinics.net/lists/stable-commits/msg266383.html
https://ww
It would be great if you can do the following:
(1) Upload a copy of /etc/netplan
(2) Find out where it's stuck. Preferably generate and attach a kernel
crashdump (https://ubuntu.com/server/docs/kernel-crash-dump) or perhaps
the hung_task_panic=1 kernel option will cause it to print out where
it's
Updaet: We found that this bug was only triggering when you try to
change the MTU to anything other than 1500. With MTU=1500 the VMs work
fine even with the current 5.15 kernel.
With MTU=1550 or MTU=9000 it fails even with the upstream 5.19 kernel
and these patches. So seems we need to report and
many significant
SR-IOV related fixes have landed in each of the recent kernel releases and we
may need to consider pro-actively backporting more fixes.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Trent Lloyd (lathiat)
Status: Confirmed
** Tags: sts
** Chang
With regards to the patch here:
https://lists.linuxfoundation.org/pipermail/iommu/2021-October/060115.html
It is mentioned this issue can occur if you are passing through a PCI
device to a virtual machine guest. This patch seems like it never made
it into the kernel. So I am curious if you are usi
Re-installing from scratch should resolve the issue. I suspect in most
cases if you install with the 21.10 installer (even though it has the
old kernel) as long as you install updates during the install this issue
probably won't hit you. It mostly seems to occur after a reboot and it's
loading data
This looks like a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476
--
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/1931660
Title:
PANIC at zfs_znode.c:3
In a related way say you wanted to recover a system from a boot disk,
and copy all the data off to another disk. If you use a sequential file
copy like from tar/cp in verbose mode and watch it, eventaully it will
hang on the file triggering the issue (watch dmesg/kern.log). Once that
happens, move
So to be clear this patch revert fixes the issue being caused new, but,
if the issue already happened on your filesystem it will continue to
occur because the exception is reporting corruption on disk. I don't
currently have a good fix for this other than to move the affected files
to a directory y
Have created a 100% reliable reproducer test case and also determined
the Ubuntu-specific patch 4701-enable-ARC-FILL-LOCKED-flag.patch to fix
Bug #1900889 is likely the cause.
[Test Case]
The important parts are:
- Use encryption
- rsync the zfs git tree
- Use parallel I/O from silversearcher-ag
While trying to setup a reproducer that would excercise chrome or wine
or something I stumbled across the following reproducer that worked
twice in a row in a libvirt VM on my machine today.
The general gist is to
(1) Create a zfs filesystem with "-o encryption=aes-256-gcm -o compression=zstd
-o
34 more user reports on the upstream bug of people hitting it on Ubuntu 5.13.0:
https://github.com/openzfs/zfs/issues/10971
I think this needs some priority. It doesn't seem like it's hitting
upstream, for some reason only really hitting on Ubuntu.
--
You received this bug notification because y
@Colin To be clear this is the same bug I originally hit and opened the
launchpad for, it just doesn't quite match with what most people saw in
the upstream bugs. But it seemed to get fixed anyway for a while, and
has regressed again somehow.
Same exception as from the original description and oth
I traced the call failure. I found the failing code is in
sa.c:1291#sa_build_index()
if (BSWAP_32(sa_hdr_phys->sa_magic) != SA_MAGIC) {
This code prints debug info to /proc/spl/kstat/zfs/dbgmsg, which for me is:
1629791353 sa.c:1293:sa_build_index(): Buffer Header: cb872954 !=
This has re-appeared for me today after upgrading to 5.13.0-14 on
Impish. Same call stack, and same chrome-based applications (Mattermost
was hit first) affected.
Not currently running DKMS, so:
Today:
5.13.0-14-lowlat Tue Aug 24 10:59 still running (zfs module is 2.0.3-8ubuntu6)
Yesterday:
5.
Try the zfs_recover step from Colin's comment above. And then look for
invalid files and try to move them out of the way.
I'm not aware of encrypted pools being specifically implicated (no such
mention in the bug and it doesn't seem like it), having said that, I am
using encryption on the dataset
Are you confident that the issue is a new issue? Unfortunately as best I
can tell, the corruption can occur and then will still appear on a fixed
system if it's reading corruption created in the past that unfortunately
scrub doesn't seem to detect.
I've still had no re-occurance here after a few w
I got another couple of days out of it without issue - so I think it's
likely fixed.
It seems like this issue looks very similar to the following upstream bug, same
behaviour but a different error, and so I wonder if it was ultimately the same
bug. Looks like this patch from 2.0.3 was pulled int
It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs, et
I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using th
Using 2.0.1 from hirsute-proposed it seems like I'm still hitting this.
Move and replace .config/google-chrome and seems after using it for a
day, shutdown, boot up, same issue again.
Going to see if I can somehow try to reproduce this on a different disk
or in a VM with xfstests or something.
--
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
Accidentally posted the above comment in the wrong bug, sorry, was meant
for https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -
where I suspect this bug as having caused a regression.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Another user report here:
https://github.com/openzfs/zfs/issues/10971
Curiously I found a 2016(??) report of similar here:
https://bbs.archlinux.org/viewtopic.php?id=217204
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubun
I hit this problem again today, but now without zfs-dkms. After
upgrading my kernel from initrd.img-5.8.0-29-generic to 5.8.0-36-generic
my Google Chrome Cache directory is broken again, had to rename it and
then reboot to get out of the problem.
** Changed in: zfs-linux (Ubuntu)
Importance: Un
I can reproduce this on a Google Cloud n1-standard-16 using 2x Local
NVMe disks. Then partition nvme0n1 and nvne0n2 with only an 8GB
partition, then format directly with ext4 (skip LVM).
In this setup each 'check' takes <1 min so speeds up testing
considerably. Example details - seems pre-emptible
** Attachment added: "blktrace-lp1907262.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+attachment/5442212/+files/blktrace-lp1907262.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Should mention that Chrome itself always showed "waiting for cache" part
of backing up the story around the cache files.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906476
Title:
Public bug reported:
Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
panic in the kernel log which was also hanging Disk I/O for all
Chrome/Electron Apps.
I have narrowed down a few important notes:
- It does not happen with module version 0.8.4-1ubuntu11 built and included
Logs are not required for this issue
** 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/1891269
Title:
perf is not built
Public bug reported:
The "perf" tool supports python scripting to process events, this
support is currently not enabled.
$ sudo perf script -g python
Python scripting not supported. Install libpython and rebuild perf to enable
it.
For example:
# apt-get install python-dev (ubuntu)
# yum ins
*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281
** This bug has been marked a duplicate of bug 1823281
perf-archive is not shipped in the linux-tools package
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have been running into this (curtin 18.1-17-gae48e86f-
0ubuntu1~16.04.1)
I think this commit basically agrees with my thoughts but I just wanted
to share them explicitly in case they are interesting
(1) If you *unregister* the cache device from the backing device, it
first has to purge all the
** Tags added: sts
** 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/1823281
Title:
perf-archive is not shipped in the
Public bug reported:
The perf-archive tool is not shipped in the linux-tools package. This
causes the command 'perf archive' to fail despite there being a manpage
for it.
This tool is used to help ship debug info to analyse perf data remotely.
This is a shell script in the kernel tree (tools/per
You can potentially use numactl to launch the process and set a policy
of interleaving allocations between NUMA nodes to avoid these 1 sided
allocations. Tends to happen with servers that make big allocations
from a single thread during startup, as commonly seen on mysqld servers
and the innodb_bu
This is resolved now.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Title:
perf broken on 4.11.0-9-generi
Same problem with the new 4.11.0-12 upload, i'm assuming since binutils
is still in -proposed it wasn't built against?
linux-tools-4.11.0-12 : Depends: binutils (< 2.29) but 2.29-2ubuntu1 is
to be installed
--
You received this bug notification because you are a member of Kernel
Packages, which
New binutils upload today of 2.29, which conflicts with linux-tools as
it turns out it Depends binutils (>= 2.28), binutils (<< 2.29)
--
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/1702056
I rebuilt both binutils and linux-4.11.0-11 locally to see if anything
changed.
binutils still has the same libbfd-2.28.90-system.20170718.so soname in
the package
however perf in linux-tools is now linked against the new soname. So a
rebuild may solve it however I am not entirely sure if this s
** Changed in: binutils (Ubuntu)
Importance: Undecided => High
--
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/1702056
Title:
perf broken on 4.11.0-9-generic (artful): /usr/lib/linux-
Doing a quick google, it seems third party binaries can get linked
against this shared library as well possibly. Ran apport-collect for
the extra logs; and both today's binutils and kernel upgrade haven't
fixed it.
Thinking we might need to propose for affecting binutils?
** Also affects: binuti
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909534/+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/17
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909543/+files/PulseList.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/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909540/+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.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909536/+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/1702056
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909539/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909533/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909546/+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/1702056/+attachment/4909542/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909544/+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/1702056
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909545/+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/1702056
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909532/+files/CRDA.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/1702056
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909541/+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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909535/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909537/+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/1702056
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909538/+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
** Tags added: apport-collected
** Description changed:
I am unable to launch perf on 4.11.0-9-generic (artful) running on
artful-proposed
/usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
libraries: libbfd-2.28-system.so: cannot open shared obj
lathiat@ubuntu:~$ apt-cache policy binutils
binutils:
Installed: 2.28.51.20170627-1ubuntu1
Candidate: 2.28.51.20170627-1ubuntu1
Version table:
*** 2.28.51.20170627-1ubuntu1 500
500 http://mirror.tcc.wa.edu.au/ubuntu artful-proposed/main amd64
Packages
100 /var/lib/dpkg/statu
Public bug reported:
I am unable to launch perf on 4.11.0-9-generic (artful) running on
artful-proposed
/usr/lib/linux-tools/4.11.0-9-generic/perf: error while loading shared
libraries: libbfd-2.28-system.so: cannot open shared object file: No
such file or directory
It seems this library is prov
Upstream bug had a patch posted today:
https://bugzilla.kernel.org/show_bug.cgi?id=110941#c90
** Bug watch added: Linux Kernel Bug Tracker #110941
http://bugzilla.kernel.org/show_bug.cgi?id=110941
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=110941
Importance: Un
Public bug reported:
My btrfs filesystem will not mount almost every boot for a few weeks
now. The only way I can currently fix this is to network boot into
rescue mode to clear the log, would be great to import this into vivid.
It appears to be this issue:
https://git.kernel.org/cgit/linux/kern
I keep seeing this as well, my use case is a mail server (dovecot). It
always seems to happen for less than a second, the times don't seem
predictable and two 14.04 servers accessing the same share report the
issues and different times, so I'm not sure it's really related to the
remote end.
I am
** Package changed: ubuntu => linux-meta (Ubuntu)
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1358226
Title:
kernel and
Just ran into this here. I set use_tempaddr=0 in my sysctl.conf, and
was very confused why my IPv6 wasn't coming up on boot. Can confirm
this is why.
This really needs to be fixed as it breaks IPv6 on boot.
--
You received this bug notification because you are a member of Kernel
Packages, whic
We are hitting this issue at the moment on our 12.04 domU guests.
It happened 4 times over the course of a couple of days.. it'd be nice
to see the fix for this backported into 12.04 domU kernels.
Our dom0 is CentOS 5.9.. might chase them up separately about perhaps
merging 03393fd5cc2b6cdeec32b
76 matches
Mail list logo
