** Description changed:
[Impact]
- * On MGLRU-enabled systems, high memory pressure on NUMA nodes will cause
page
-allocation failures
- * This happens due to page reclaim not waking up flusher threads
- * OOM can be triggered even if the system has enough available memory
+ * On MGLRU-
* According to the upstream patch, increased SSD/disk wearing is possible due
to waking up flusher threads, although these have not been noted in testing
** Affects: linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
** Affects: linux
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/2095529
Title:
Please merge 2.2.7-2 into plucky
Status i
** Merge proposal linked:
https://code.launchpad.net/~halves/ubuntu/+source/zfs-linux/+git/zfs-linux/+merge/480162
--
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/2095529
Title:
P
Public bug reported:
tracking bug
** Affects: zfs-linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you ar
I've validated this with the test case from the description. A local run
of the ZFS test suite with the package from -proposed also points to
this issue being fixed, so I'm marking this as verified.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a me
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
** Changed in: linux (Ubuntu Noble)
Status: Fix Released => 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/bu
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Noble)
Status: Triaged => Fix Released
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
** Changed in: zfs-linux (Ubuntu Noble)
Status: New => In Progress
** Changed i
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: zfs-linux (Ubuntu)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
** Changed in: zfs-linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: zfs-linux (Ubu
** Description changed:
[ Impact ]
Upgrading from 20.04 to 22.04 causes encrypted pools to become unmountable.
This
is due to broken accounting metadata causing checksum errors on decrypt, which
makes ZFS error out early with ECKSUM.
+
+ To fix this, we test specifically against this bro
jammy on 2022-08-20 (0 days ago)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission
denied: '/etc/sudoers.d/zfs']
** Also affects: zfs-linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: zfs-linux (Ubuntu Jammy)
Assignee: (unassigned) => He
- d/p/lp2077176/0008-test-fs-util-don-t-validate-mode-of-symlinks.patch
-- Heitor Alves de Siqueira Fri, 16 Aug 2024
14:54:17 +
** Changed in: ubuntu-pro/18.04
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packa
Hi jasimoni,
thanks for the testing effort! And thanks for amending the description
with the regression information as requested. I've reviewed your PPA
builds, and things look good. I've also double-checked them against
mfo's requests, and we seem to have covered everything.
Testing looks good,
This regressed again on Jammy with the 6.5/6.8 HWE kernels. Ghadi, since
you worked on the patch for Jammy, I've assigned the series to you.
Given this is something quite unique to Ubuntu that comes from running
"old" zfsutils against a "new" ZFS kmod, it's likely going to end up as
a COMPAT patch
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification be
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification becaus
Fixed in 1:1.7.5-2, so already merged for Oracular.
** Also affects: makedumpfile (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Oracular)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: In Progress
I can see this now builds correctly for riscv64, and I was able to
install it on a local VM. Basic testing looks good, so I'm marking this
one as verified.
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1919154
Title:
Enable CONFIG_NO_HZ_FULL on supported architectures
Bionic is EoL, if RISC-V support is needed there we'll need to target
Pro 18.04.
** Tags removed: patch se-sponsor-halves
** Description changed:
- Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
- patch missing:
- https://github.com/openzfs/zfs/commit/4254e407294b211f339
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
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/1987052
Title:
Running MySQL8 in Docker on ZFS only works if you h
signee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided =&g
Marking Ubuntu as "Fix Released" according to parent description, as fix
was introduced upstream in v5.16.
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notificatio
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2061986
Title:
Mount CIFS fails with Permission denied
Status in linux pa
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Medium => Low
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug not
Yes, HWE kernels based on the Jammy/Mantic/Noble kernels should get this
fix automatically when the GA versions get 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/2036239
Title:
@christian-rhomann "Fix committed" here means that the patches have been merged
into Ubuntu's kernel tree for that specific release. The patch Robert submitted
is the one from upstream, not the test patch from the comments here.
E.g. for Jammy:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+sou
** Also affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Robert Malz (rmalz)
Status: In Progress
--
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/2036239
Title:
In
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Changed in
I've successfully confirmed that the mount issues seem to be fixed using
systemd from focal-proposed. Using the 'rep-tmpfs.sh' script, all
variants ran without any issues for multiple rounds. Basic testing on a
VM also looks good. Below are the versions used for this test:
$ dpkg -l systemd
...
||
As this will need fixing in the development release, I'll re-subscribe
the ubuntu-sponsors team. After this has been fixed there, we can take a
look at the SRU for the other stable releases.
Thanks, Chengen!
--
You received this bug notification because you are a member of Kernel
Packages, which
I've tested the kernel from focal-proposed, with the systemd packages
from my personal PPA (as the systemd patches aren't yet available in
focal-proposed).
All test variants from the rep-tmpfs.sh script ran succesfully, and
general smoke testing revealed no further issues.
ubuntu@z-rotomvm35:~$ u
Fix Committed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Focal)
Importance: Medium => High
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: linux (Ubu
Thank you for the patch, xypron! A few comments on your debdiff:
I don't see the Bug-Ubuntu: tag in the patch, could you please add it so it's
DEP-3 compliant?
Looking at the Origin: tag, it's also not clear whether the patch is a clean
cherry-pick or needed to be backported with some changes. C
** Tags added: se-sponsor-halves
--
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/2016881
Title:
Building for Focal fails on riscv64
Status in zfs-linux package in Ubuntu:
Fix Relea
Note that the riscv64 patch is also missing from Focal (20.04), and the
package also fails to build there. Upstream included initial support in
zfs-2.0.0, so newer Ubuntu releases should have it by default:
$ git describe --contains 4254e407294b211f3399da2ee131b45fe9f4ac80
zfs-2.0.0-rc1~665
** Al
zfs-linux FTBS on riscv64, but that's been the case for the versions
from -updates for some time now. It's not related to this upload, but
rather to the ZFS version in focal not supporting riscv64:
In file included from ../../lib/libspl/include/sys/types.h:36,
from ../../module/av
** Tags added: verification-needed-focal
** Tags added: se-sponsor-halves
--
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/1964992
Title:
ZFS ignores ARC sizes below allmem/32
Status
Thank you for the v2, Ghadi! I made some minor modifications to your
changelog entry (added "d/p/" before the patch files), and included a
"backport-notes:" tag in your second patch mentioning the FreeBSD-
specific sections were dropped from upstream.
With the v2, I ran the regression tests again
)
Status: New => Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Heit
Thanks, Dimitri! I've tested Ghadi's patches and confirmed they work and
don't trigger any regressions in the ZFS test suite.
I've asked Ghadi to rework some portions of his backport in order to be closer
to the upstream patches though, so we should have a v2 soon. We'll make sure
that previous
** Patch removed: "lp1964992-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+attachment/5571326/+files/lp1964992-focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https:
No worries, thank you for the patience, Robie!
With further testing, we've found out that there's an additional upstream
patch required for Focal, which fixes the "inversion" when setting the ARC
limits.
I'll amend the description and re-spin this SRU to include the proper
fixes. I'll then re-upl
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1978333
Title:
Remove "ata_piix.prefer_ms_hyperv=0" parameter
Hi Robie,
You're right, the patch does essentially invert the problem. This is
still the behavior upstream, and it currently works like you mentioned:
if the user tries to set a min above the default max (ramsize/2), it
fails.
I'm working on a patch to propose upstream that should fix this. We
sh
Failed autopkgtest result for i386 seemed to be due to a flaky test, not an
actual regression. Test passed after another run, and no further autopkgtest
regressions have been reported.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedu
** Tags removed: sts-sponsor-halves
** Tags added: se-sponsor-halves
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1978333
Title:
Remove "ata_piix.prefer_ms_hyperv=0" parameter
** Tags added: sts sts-sponsor-halves
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1978333
Title:
Remove "ata_piix.prefer_ms_hyperv=0" parameter
Status in kdump-tools package i
** Description changed:
[Impact]
* Specific NVMe devices fail to probe and become unusable after boot
* Caused by an ACPI regression that doesn't correctly handle power states
* Upstream regression commit:
7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally
* Re
** Summary changed:
- NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
+ NVMe devices fail to probe due to ACPI power state change
** Description changed:
+ [Impact]
+ * Specific NVMe devices fail to probe and become unusable after boot
+ * Caused by an ACPI regressi
Validated for Ubuntu Impish with the current kernel from impish-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer Bit
In addition to my own validations above, impacted users that have 40G
NICs have also confirmed the patch behaves as expected without major
regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Validated for Ubuntu Bionic with the current HWE kernel from bionic-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer
Validated for Ubuntu Focal with the current kernel from focal-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer Bitra
Hi all,
This seems to be related to a regression introduced by the following commit:
* 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally
The fix seems to indeed be the commit @sclarkson mentioned:
* bc2836859643 ACPI: PM: Do not turn off power resources in unknown state
L
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
buntu Impish)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status:
** Patch added: "lp1964992-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+attachment/5571326/+files/lp1964992-focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://
This doesn't seem to be reproducible in Bionic, marking it as fixed
accordingly.
** Changed in: zfs-linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https:
Status: Fix Released
** Affects: zfs-linux (Ubuntu Bionic)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
** Affects: zfs-linux (Ubuntu Focal)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: Confi
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Focal)
ffic
* It's possible to see increased calls to alloc_pages if ring sizes
aren't being set correctly
* We should look out for excessive memory usage in the sfc driver due to
the increased ring sizes
** Affects: linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siq
@dgatwood would you be able to upload kernel logs and lsusb output from
the -44 kernel? From what you're describing it seems like a possible
issue with host controllers, but it's hard to tell without looking at
what is going in the kernel.
You can use `apport-collect 1956849` to upload relevant da
Verified for Focal according to test case from description. A standard
multipass VM with 8 vCPUs configured was able to capture a kernel dump
without errors.
Additionally, since the 5.4 kernel doesn't hit the MMU/reset bug
directly, I've done some additional testing to ensure we didn't
introduce a
For future reference, this bug has been reported in Ubuntu KVM hosts
outside of the specific kdump test scenario (i.e. when running actual
VMs in production-like setups). The "kdump with multiple CPUs" case was
discovered as an alternative that hits the same MMU context bug, without
needing complex
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
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/194
cided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple enabl
** Description changed:
[Impact]
- When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM
- emulation failure. This will cause the VM to go into the "paused" state, and
- prevents it from being restored without a full VM restart.
+ When kexec'ing into a crash kernel with ncpus
^2~58
v5.15-rc1~65^2~119
v5.15-rc1~65^2~120
** Affects: linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Validated with ZFS from focal-proposed, according to test case from description:
ubuntu@z-rotomvm34:~$ dpkg -l | grep zfsutils
ii zfsutils-linux 0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@z-rotomvm34:~$ zfs list
** Description changed:
[Impact]
Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
[Test Plan]
1. Install Ubuntu 20.04 using ZFS-on-root
2. Add encrypted partition to /etc/crypttab:
-swap/dev/nvme0n1p1 /dev/urandom
** Description changed:
+ [Impact]
+ Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
+
+ [Test Plan]
+ 1. Install Ubuntu 20.04 using ZFS-on-root
+ 2. Add encrypted partition to /etc/crypttab:
+swap/dev/nvme0n1p1 /dev/urandom
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs
Verified for Bionic following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~$ uname -rv
4.15.0-141-generic #145-Ubuntu SMP Wed Mar 24 18:08:07 UTC 2021
I had to adjust the tx_desc_addr probes, subtracting 0x4 from both offsets and
changing the
Verified for Xenial following the same test procedure from comment #13, running
on the current -proposed kernel:
ubuntu@snorlax:~/kprobe$ uname -rv
4.4.0-207-generic #239-Ubuntu SMP Thu Mar 25 02:59:26 UTC 2021
The offsets don't seem to have changed on any of the probes, so I've
used the same set
There's a build failure for zfs-linux on riscv64/focal, but that should
be safe to ignore for this patch. The riscv64 builds seem to have failed
since they were enabled in 0.8.3-1ubuntu11, and are related to an
"Unsupported ISA type" error in the libspl header files. It's likely
that we're missing
Verified for Xenial, using the ZFS test suite. I don't think Xenial
ships zfs-test, so I pulled it from upstream and ran it against the DKMS
drivers. No new regressions were reported.
ubuntu@z-rotomvm27:~$ dpkg -l | grep zfs-dkms
ii zfs-dkms 0.6.5.6-0ubuntu29
Verified for Groovy, through the ZFS test suite. No new regressions were
reported.
ubuntu@racah:/usr/share/zfs$ dpkg -l | grep zfs-dkms
ii zfs-dkms 0.8.4-1ubuntu11.2
all OpenZFS filesystem kernel modules for Linux
** Tags added: verificati
Verified for Focal, through the ZFS test suite. No new regressions were
reported.
ubuntu@z-rotomvm29:/usr/share/zfs$ dpkg -l | rg zfs-dkms
ii zfs-dkms 0.8.3-1ubuntu12.7
all OpenZFS filesystem kernel modules for Linux
** Tags added: verif
Verified for Bionic, through the ZFS test suite. No new regressions were
reported, and results of the test suite are the same as for the previous
version.
ubuntu@z-rotomvm28:/usr/share/zfs$ dpkg -l |grep zfs-dkms
ii zfs-dkms 0.7.5-1ubuntu16.11
** Description changed:
[Impact]
The i40e driver sometimes causes a "malicious device" event that the firmware
detects, which causes the firmware to reset the NIC, causing an interruption in
the network connection - which can cause further problems, e.g. if the
interface is in a bond; the r
I'm attaching kprobes for the Xenial kernels. These are based on the
4.4.0-203/204 versions.
I followed the same test setup for Bionic, as described in the previous
comment, and also had similar results. The netdev watchdog seems to take good
care of any hung queues, so in the end PF resets will
Given that we're could be changing reset behavior that might be expected
from the firmware, I wrote a quick set of kprobes to force the firmware
to raise MDD events and test out the patched kernel from the PPA.
I tried to force faulty TX descriptors according to "Table 7-138. Tx
Descriptor Validit
** Summary changed:
- Intel i40e PF reset due to incorrect MDD detection (continues...again...)
+ Intel i40e PF reset due to incorrect MDD detection
** Summary changed:
- Intel i40e PF reset due to incorrect MDD detection
+ i40e PF reset due to incorrect MDD event
--
You received this bug noti
** Description changed:
[Impact]
The i40e driver sometimes causes a "malicious device" event that the firmware
detects, which causes the firmware to reset the NIC, causing an interruption in
the network connection - which can cause further problems, e.g. if the
interface is in a bond; the r
** Description changed:
- [impact]
+ [Impact]
+ The i40e driver sometimes causes a "malicious device" event that the firmware
detects, which causes the firmware to reset the NIC, causing an interruption in
the network connection - which can cause further problems, e.g. if the
interface is in a
** Description changed:
[Impact]
TXG sync stalls, causing ZFS workloads to hang indefinitely
[Description]
For certain ZFS workloads, we can see hung task timeouts in the kernel logs
due to a transaction group deadlock. Userspace process will hang and display
stack traces similar to t
** Patch added: "lp1916486-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471918/+files/lp1916486-xenial.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https:
** Patch added: "lp1916486-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471921/+files/lp1916486-groovy.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https:
** Patch added: "lp1916486-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471920/+files/lp1916486-focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://
** Patch added: "lp1916486-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1916486/+attachment/5471919/+files/lp1916486-bionic.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https:
--
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/1916486
Title:
zfs_zrele_async can cause txg sync deadlocks
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux s
I've pushed some test kernels for X/B to a public PPA assigned to this
bug [0], hopefully it'll make validating the upstream patch a bit
easier.
[0] https://launchpad.net/~halves/+archive/ubuntu/lp1772675
** Changed in: linux (Ubuntu Xenial)
Importance: Low => High
** Changed in: linux (Ubunt
** Changed in: zfs-linux (Ubuntu Hirsute)
Status: In Progress => Fix Released
** Changed in: zfs-linux (Ubuntu Hirsute)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
** Description changed:
[Impact]
TXG sync stalls, causing ZFS workloads to hang indefi
** Changed in: zfs-linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Groovy)
Status: New => In Progre
rther regressions should be fairly controlled. Potential
regressions might arise in the ZFS writeback path, so we should monitor heavy
I/O workloads that put a lot of stress in the sync and evict paths.
** Affects: zfs-linux (Ubuntu)
Importance: Critical
Assignee: Heitor Alves de Siq
on PF in response to MDD event
$ git describe --contains a1df906c5be7
v5.2-rc1~133^2~57^2~9
[0] https://git.kernel.org/linus/a1df906c5be7
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Xenial)
Assignee: (un
@pponnuvel stat(2) doesn't perform a read(2) on the file, so it won't
call the show() method for priority_stats (which was the problematic
call for this specific sysfs attribute).
In any case, this should be fixed in all supported Ubuntu series, so
even read(2) shouldn't be an issue anymore. Pleas
Patches sent to the kernel-team list:
https://lists.ubuntu.com/archives/kernel-team/2020-December/115633.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1908264
Title:
Disable At
1 - 100 of 139 matches
Mail list logo
