On Wed, Jan 15, 2020 at 9:17 AM Deepa Dinamani <deepa.kernel@xxxxxxxxx> wrote: > > On Mon, Jan 13, 2020 at 9:07 AM Kairui Song <kasong@xxxxxxxxxx> wrote: > > > > On Sun, Jan 12, 2020 at 2:33 AM Deepa Dinamani <deepa.kernel@xxxxxxxxx> wrote: > > > > > > > Hi, there are some previous works about this issue, reset PCI devices > > > > in kdump kernel to stop ongoing DMA: > > > > > > > > [v7,0/5] Reset PCIe devices to address DMA problem on kdump with iommu > > > > https://lore.kernel.org/patchwork/cover/343767/ > > > > > > > > [v2] PCI: Reset PCIe devices to stop ongoing DMA > > > > https://lore.kernel.org/patchwork/patch/379191/ > > > > > > > > And didn't get merged, that patch are trying to fix some DMAR error > > > > problem, but resetting devices is a bit too destructive, and the > > > > problem is later fixed in IOMMU side. And in most case the DMA seems > > > > harmless, as they targets first kernel's memory and kdump kernel only > > > > live in crash memory. > > > > > > I was going to ask the same. If the kdump kernel had IOMMU on, would > > > that still be a problem? > > > > It will still fail, doing DMA is not a problem, it only go wrong when > > a device's upstream bridge is mistakenly shutdown before the device > > shutdown. > > > > > > > > > Also, by the time kdump kernel is able to scan and reset devices, > > > > there are already a very large time window where things could go > > > > wrong. > > > > > > > > The currently problem observed only happens upon kdump kernel > > > > shutdown, as the upper bridge is disabled before the device is > > > > disabledm so DMA will raise error. It's more like a problem of wrong > > > > device shutting down order. > > > > > > The way it was described earlier "During this time, the SUT sometimes > > > gets a PCI error that raises an NMI." suggests that it isn't really > > > restricted to kexec/kdump. > > > Any attached device without an active driver might attempt spurious or > > > malicious DMA and trigger the same during normal operation. > > > Do you have available some more reporting of what happens during the > > > PCIe error handling? > > > > Let me add more info about this: > > > > On the machine where I can reproduce this issue, the first kernel > > always runs fine, and kdump kernel works fine during dumping the > > vmcore, even if I keep the kdump kernel running for hours, nothing > > goes wrong. If there are DMA during normal operation that will cause > > problem, this should have exposed it. > > > > The problem only occur when kdump kernel try to reboot, no matter how > > long the kdump kernel have been running (few minutes or hours). The > > machine is dead after printing: > > [ 101.438300] reboot: Restarting system^M > > [ 101.455360] reboot: machine restart^M > > > > And I can find following logs happend just at that time, in the > > "Integrated Management Log" from the iLO web interface: > > 1254 OS 12/25/2019 09:08 12/25/2019 09:08 1 User Remotely Initiated NMI Switch > > 1253 System Error 12/25/2019 09:08 12/25/2019 09:08 1 An Unrecoverable > > System Error (NMI) has occurred (Service Information: 0x00000000, > > 0x00000000) > > 1252 PCI Bus 12/25/2019 09:07 12/25/2019 09:07 1 Uncorrectable PCI > > Express Error (Embedded device, Bus 0, Device 2, Function 2, Error > > status 0x00100000) > > 1251 System Error 12/25/2019 09:07 12/25/2019 09:07 1 Unrecoverable > > System Error (NMI) has occurred. System Firmware will log additional > > details in a separate IML entry if possible > > 1250 PCI Bus 12/25/2019 09:07 12/25/2019 09:07 1 PCI Bus Error (Slot > > 0, Bus 0, Device 2, Function 2) > > > > And the topology is: > > [0000:00]-+-00.0 Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 > > +-01.0-[02]-- > > +-01.1-[05]-- > > +-02.0-[06]--+-00.0 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.1 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.2 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.3 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.4 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.5 Emulex Corporation OneConnect NIC (Skyhawk) > > | +-00.6 Emulex Corporation OneConnect NIC (Skyhawk) > > | \-00.7 Emulex Corporation OneConnect NIC (Skyhawk) > > +-02.1-[0f]-- > > +-02.2-[07]----00.0 Hewlett-Packard Company Smart Array > > Gen9 Controllers > > > > It's a bridge reporting the error. It should be an unsupported request > > error, bacause downstream device is still alive and sending request, > > but the port have bus mastering off. If I manually shutdown the "Smart > > Array" (HPSA) device before kdump reboot, it will always reboot just > > fine. > > > > And as the patch descriptions said, the HPSA is used in first kernel, > > but didn't get reset in kdump kernel because driver is not loaded. > > When shutting down a bridge, kernel should shutdown downstream device > > first, and then shutdown and clear bus master bit of the bridge. But > > in kdump case, kernel skipped some device shutdown due to driver not > > loaded issue, and kernel don't know they are enabled. > > > > This problem is not limited to HPSA, the NIC listed in above topology > > maybe also make the bridge error out, if HPSA get loaded in kdump > > kernel and NIC get ignored. > > It looks like the right answer is for the kernel to handle such cases > gracefully. From what I recall, we can only trust the bus mastering at > root ports. So, it is possible that the endpoint devices can always > try to DMA, but it can be blocked by the root port. So the right fix > seems to teach kernel how to handle these insted of hacking the > shutdown code. > -Deepa > Kexec have been disabling bus mastering on endpoints to prevent memory corruption since commit b566a22c2332 ("PCI: disable Bus Master on PCI device shutdown"), later improved by 4fc9bbf98fd6 ("PCI: Disable Bus Master only on kexec reboot") and 6e0eda3c3898 ("PCI: Don't try to disable Bus Master on disconnected PCI devices"). That's done before 2014, it worked for kexec reboot, so I think disable bus mastering on endpoints should work in most cases. It's true that on some machine disabling bus mastering doesn't work well, but I guess kexec/kdump will also not work well on such machine? And for kdump, the hardware is already in an unstable status, and kernel don't know how to shutdown/reset some device due to driver not loaded. And loading all drivers in kdump kernel is usually not practical. So I think disable bus mastering bit is the best effort kernel could do at that time (upon shutdown, at least ensure device shutdown is in right order)? And about the UR error and Bus Mastering bit, from the spec: "Endpoints:When this bit is Set, the PCI Express Function is allowed to issue Memory or I/O Requests. When this bit is Clear, the PCI Express Function is not allowed to issue any Memory or I/O Requests." "Root and Switch Ports: This bit controls forwarding of Memory or I/O Requests by a Switch or Root Port in the Upstream direction. When this bit is 0b, Memory and I/O Requests received at a Root Port or the Downstream side of a Switch Port must be handled as Unsupported Requests (UR), and for Non-Posted Requests a Completion with UR completion status must be returned." Hardware is supposed to report UR error, but this hanging problem is only observed on some HPE machines, the firmware will send NMI (and supposed to panic the kernel) when it happened. So maybe this could be fixed with the firmware or apply some workaround for HPE (eg in hpwdt)? -- Best Regards, Kairui Song
