On Thu, Nov 11, 2021 at 01:42:58PM +0800, Liguang Zhang wrote:
> Both the CCIE and HPIE bits are masked in pcie_disable_notification(),
> when we issue a hotplug command, pcie_wait_cmd() will polling the
> Command Completed bit instead of waiting for an interrupt. But cmd_busy
> bit was not cleared when Command Completed which results in timeouts
> like this in pciehp_power_off_slot() and pcie_init_notification():
>
> pcieport 0000:00:03.0: pciehp: Timeout on hotplug command 0x01c0
> (issued 2264 msec ago)
> pcieport 0000:00:03.0: pciehp: Timeout on hotplug command 0x05c0
> (issued 2288 msec ago)
The first timeout occurs with the following bits set in ctrl->slot_ctrl:
PCI_EXP_SLTCTL_PWR_IND_ON | PCI_EXP_SLTCTL_ATTN_IND_OFF
Those bits are set by:
board_added()
pciehp_set_indicators()
The second timeout occurs with:
PCI_EXP_SLTCTL_PWR_IND_ON | PCI_EXP_SLTCTL_ATTN_IND_OFF |
PCI_EXP_SLTCTL_PWR_OFF
This might be triggered by:
remove_board()
pciehp_power_off_slot()
So it seems Command Completed is not signaled when changing the
Power Indicator, Attention Indicator and Power Controller Control
bits in the Slot Control register. But apparently it works for
the other bits.
We know there are hotplug controllers out there which suffer from
broken Command Completed support. They support it for the bits
mentioned above but not the others. So the inverse behavior from
your hotplug controller. See this code comment in pcie_do_write_cmd():
/*
* Controllers with the Intel CF118 and similar errata advertise
* Command Completed support, but they only set Command Completed
* if we change the "Control" bits for power, power indicator,
* attention indicator, or interlock. If we only change the
* "Enable" bits, they never set the Command Completed bit.
*/
> --- a/drivers/pci/hotplug/pciehp_hpc.c
> +++ b/drivers/pci/hotplug/pciehp_hpc.c
> @@ -98,6 +98,8 @@ static int pcie_poll_cmd(struct controller *ctrl, int timeout)
> if (slot_status & PCI_EXP_SLTSTA_CC) {
> pcie_capability_write_word(pdev, PCI_EXP_SLTSTA,
> PCI_EXP_SLTSTA_CC);
> + ctrl->cmd_busy = 0;
> + smp_mb();
> return 1;
> }
> msleep(10);
I suspect that this patch merely papers over the problem and that
the real solution would be to either apply quirk_cmd_compl or a
similar quirk to your hotplug controller.
Please open a bug on bugzilla.kernel.org and attach full output
of lspci -vv and dmesg. Be sure to add the following to the
command line:
pciehp.pciehp_debug=1 dyndbg="file pciehp* +p"
Once you've done that, please report the bugzilla link here
so that we can analyze the issue properly.
Thanks,
Lukas
