@MasterCATZ, please check this with the 20.04 5.4 kernel. If it's still
an issue could you please file a separate kernel bug for your corruption
issue?
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
seems I finally found the real issue
in the bios of my Gigabyte x570 UD , when I have 4G encode option enabled I
have silent data corruption
( or at least if its enabled along side with IOMMU )
I need to make another array that I can kill to keep testing with , but
I can literally go into the
Running Ubuntu 19.10 5.4.3-050403-generic
Ryzen 3900x GA x570 UD mainboard DDR 3200 ,
I have been getting data corruption on my 4x SSD on Sata ports ( btrfs/ext4)
disks running from my LSI / Avago SAS Raid 9302-16e 12Gb/s PCIe 3.0 controller
(btrfs/EXT4)
and all my disks running from my HBA
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Cosmic)
Status: Fix Committed => 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/1823037
Title:
amd_iommu possible data corruption
Status in
** Tags added: cscc
--
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/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux
This bug was fixed in the package linux - 5.0.0-21.22
---
linux (5.0.0-21.22) disco; urgency=medium
* linux: 5.0.0-21.22 -proposed tracker (LP: #1834902)
* Disco update: 5.0.15 upstream stable release (LP: #1834529)
- net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-
This bug was fixed in the package linux - 4.15.0-55.60
---
linux (4.15.0-55.60) bionic; urgency=medium
* linux: 4.15.0-55.60 -proposed tracker (LP: #1834954)
* Request backport of ceph commits into bionic (LP: #1834235)
- ceph: use atomic_t for ceph_inode_info::i_shared_gen
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you
SRU Request submitted
--
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/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux
** Description changed:
[Impact]
- iommu/amd: Reserve exclusion range in iova-domain
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't
** Description changed:
[Impact]
iommu/amd: Reserve exclusion range in iova-domain
BugLink: https://bugs.launchpad.net/bugs/1823037
If a device has an exclusion range specified in the IVRS
table, this region needs to be reserved in the iova-domain
of that device. This hasn't
** Description changed:
[Impact]
- iommu/amd: Set exclusion range correctly
-
- BugLink: https://bugs.launchpad.net/bugs/1823037
-
- The exlcusion range limit register needs to contain the
- base-address of the last page that is part of the range, as
- bits 0-11 of this register are treated
** Description changed:
[Impact]
iommu/amd: Set exclusion range correctly
-
+
BugLink: https://bugs.launchpad.net/bugs/1823037
-
+
The exlcusion range limit register needs to contain the
base-address of the last page that is part of the range, as
bits 0-11 of this register
** Description changed:
[Impact]
+ iommu/amd: Reserve exclusion range in iova-domain
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data
** Description changed:
[Impact]
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
Treat exclusion
** Description changed:
[Impact]
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
-
- Treat exclusion
** Tags added: verification-done-bionic verification-done-disco
--
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/1823037
Title:
amd_iommu possible data corruption
Status in linux package
All three test kernels have passed 24+ hour testing.
** Tags added: verification-done-bionic
** Tags removed: verification-done-bionic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi Jerry,
The test kernels are located here and have "1" appended to them.
https://people.canonical.com/~jlane/testkernels/
--
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/1823037
Title:
Jeff, The second patch improves the fix against the amount of memory in
the system. We still need both patches.
--
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/1823037
Title:
amd_iommu
So I'm a bit confused because I've been told that A: additional patches
are necessary to solve the issue, and B: that the issue is solved
without those additional patches.
When you did the test, were you using the older, failing firmware
levels, or have you updated to the patched firmware that is
Confirming that I was unable to reproduce the issue on linux-
image-4.15.0-46-generic (4.15.0-46.49) from the test kernels repository
with my test setup.
Previously I was able to cause filesystem corruption within 1 hour of
testing under a test load (verified by btrfs checksums) across all disks
An additional patch has been identified that will be needed to solve
this issue.
https://github.com/torvalds/linux/commit/3c677d206210f53a4be972211066c0f1cd47fe12
#diff-083bf3d2f128b616e730b7f9f8fc65c4
--
You received this bug notification because you are a member of Kernel
Packages, which is
Test kernels are up here:
https://people.canonical.com/~jlane/testkernels/
Please test each and report back
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
related branch
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee:
28 matches
Mail list logo
