diff options
| -rw-r--r-- | 0001-PCI-tegra-Revert-raw_violation_fixup-for-tegra124.patch | 65 | ||||
| -rw-r--r-- | kernel.spec | 6 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 5 insertions, 67 deletions
diff --git a/0001-PCI-tegra-Revert-raw_violation_fixup-for-tegra124.patch b/0001-PCI-tegra-Revert-raw_violation_fixup-for-tegra124.patch deleted file mode 100644 index 0af11db2d..000000000 --- a/0001-PCI-tegra-Revert-raw_violation_fixup-for-tegra124.patch +++ /dev/null @@ -1,65 +0,0 @@ -From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 -From: Nicolas Chauvet <kwizart@gmail.com> -Date: Mon, 20 Apr 2020 18:43:04 +0200 -Subject: [PATCH] PCI: tegra: Revert raw_violation_fixup for tegra124 - -As reported in https://bugzilla.kernel.org/206217 , raw_violation_fixup -is causing more harm than good in some common use-cases. - -This patch as RFC is a partial revert of the 191cd6fb5 commit: - "PCI: tegra: Add SW fixup for RAW violations" -that was first introduced in 5.3 kernel. -This fix the following regression since then. - -When using both the network NIC and I/O on MMC this can lead to the -following message on jetson-tk1: - - NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out - -and - - pcieport 0000:00:02.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0 - r8169 0000:01:00.0: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) - r8169 0000:01:00.0: AER: device [10ec:8168] error status/mask=00004000/00400000 - r8169 0000:01:00.0: AER: [14] CmpltTO (First) - r8169 0000:01:00.0: AER: can't recover (no error_detected callback) - pcieport 0000:00:02.0: AER: device recovery failed - -After that, the ethernet NIC isn't functional anymore even after reloading -the module. -After a reboot, this is reproducible by copying a large file over the -ethernet NIC to the MMC. -For some reasons this cannot be reproduced when the same file is copied -to a tmpfs. - -This patch is RFC because it requires more understanding from Nvidia. - - Is the fixup (available in l4t downstrem) still needed for upstream ? - - Is there a need to update the fixup values for upstream ? - - If the fixup is reverted, does the hw bug can still be seen with - upstream ? - -Others can also provides more understanding: - - Conditions to reproduce the bug (or not)... - -Signed-off-by: Nicolas Chauvet <kwizart@gmail.com> -Reviewed-by: Manikanta Maddireddy <mmaddireddy@nvidia.com> ---- - drivers/pci/controller/pci-tegra.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/drivers/pci/controller/pci-tegra.c b/drivers/pci/controller/pci-tegra.c -index 235b456698fc..d5a4a167ffa1 100644 ---- a/drivers/pci/controller/pci-tegra.c -+++ b/drivers/pci/controller/pci-tegra.c -@@ -2470,7 +2470,7 @@ static const struct tegra_pcie_soc tegra124_pcie = { - .program_uphy = true, - .update_clamp_threshold = true, - .program_deskew_time = false, -- .raw_violation_fixup = true, -+ .raw_violation_fixup = false, - .update_fc_timer = false, - .has_cache_bars = false, - .ectl.enable = false, --- -2.26.2 - diff --git a/kernel.spec b/kernel.spec index 457f36101..407e2fd91 100644 --- a/kernel.spec +++ b/kernel.spec @@ -92,7 +92,7 @@ Summary: The Linux kernel %if 0%{?released_kernel} # Do we have a -stable update to apply? -%define stable_update 0 +%define stable_update 1 # Set rpm version accordingly %if 0%{?stable_update} %define stablerev %{stable_update} @@ -837,7 +837,6 @@ Patch73: 0001-virt-vbox-Add-vbg_set_host_capabilities-helper-funct.patch Patch74: 0001-virt-vbox-Add-support-for-the-new-VBG_IOCTL_ACQUIRE_.patch Patch75: 0001-virt-vbox-Add-a-few-new-vmmdev-request-types-to-the-.patch Patch76: 0001-virt-vbox-Log-unknown-ioctl-requests-as-error.patch -Patch77: 0001-PCI-tegra-Revert-raw_violation_fixup-for-tegra124.patch Patch82: 0001-selinux-allow-reading-labels-before-policy-is-loaded.patch Patch83: 0001-Revert-dt-bindings-panel-add-binding-for-Xingbangda-.patch Patch84: 0001-Revert-drm-panel-add-Xingbangda-XBD599-panel.patch @@ -2965,6 +2964,9 @@ fi # # %changelog +* Tue Aug 11 2020 Justin M. Forbes <jforbes@fedoraproject.org> - 5.8.1-200 +- Linux v5.8.1 + * Sat Aug 01 2020 Justin M. Forbes <jforbes@fedoraproject.org> - 5.7.12-200 - Linux v5.7.12 @@ -1 +1,2 @@ SHA512 (linux-5.8.tar.xz) = 45a53ecf351096ef6e98242cca4228b8da9b9139ecc6963695791ea6fb7a9484a4e1c19dcca7ce7cbfdfa49de0451b70973bb078f12bdae9cbaddbc3f8092556 +SHA512 (patch-5.8.1.xz) = 36073168fe7478f93e5b9dc7f4214891f1eabb9b908c0282032770be21bd49adb51040037dd7a901b24910dfbbc65d507c75d71153b746021e0558d5e9aa30ae |