From: helgaas@kernel.org (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: imx6:don't sleep in atomic context
Date: Wed, 6 Jan 2016 16:04:30 -0600 [thread overview]
Message-ID: <20160106220430.GC16231@localhost> (raw)
In-Reply-To: <1447066080-5859-1-git-send-email-sanjeev_sharma@mentor.com>
Hi Sanjeev,
On Mon, Nov 09, 2015 at 04:18:00PM +0530, Sanjeev Sharma wrote:
> If additional PCIe switch get connected between the
> host and the NIC,the kernel crashes with "BUG:
> scheduling while atomic". To handle this we need to
> call mdelay() instead of usleep_range().
>
> For more detail please refer bugzilla.kernel.org, Bug
> 100031
>
> Signed-off-by: Sanjeev Sharma <sanjeev_sharma@mentor.com>
> Signed-off-by: David Mueller <dave.mueller@gmx.ch>
I'm dropping this for now because we've been kicking around the same
solution (with tweaks to the mdelay amount) since June, but no
progress on the *real* issue, which is that imx6_pcie_link_up() should
never wait; it should simply return the link status.
I'm pretty sure the amount of time I've spent looking into this would
have been enough to make some progress on that underlying issue.
Bjorn
> ---
> drivers/pci/host/pci-imx6.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/host/pci-imx6.c b/drivers/pci/host/pci-imx6.c
> index 233a196..9769b13 100644
> --- a/drivers/pci/host/pci-imx6.c
> +++ b/drivers/pci/host/pci-imx6.c
> @@ -499,7 +499,7 @@ static int imx6_pcie_link_up(struct pcie_port *pp)
> * Wait a little bit, then re-check if the link finished
> * the training.
> */
> - usleep_range(1000, 2000);
> + mdelay(1000);
> }
> /*
> * From L0, initiate MAC entry to gen2 if EP/RC supports gen2.
> --
> 1.7.11.7
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-06 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1447066080-5859-1-git-send-email-sanjeev_sharma@mentor.com>
2015-11-10 8:41 ` [PATCH] PCI: imx6:don't sleep in atomic context Lucas Stach
2015-11-10 9:28 ` Arnd Bergmann
2015-11-10 9:35 ` Lucas Stach
2015-11-10 9:45 ` Arnd Bergmann
2015-11-16 9:36 ` Sharma, Sanjeev
2015-11-24 13:57 ` Lucas Stach
[not found] ` <1449042196-25710-1-git-send-email-sanjeev_sharma@mentor.com>
2016-01-06 2:13 ` [PATCH v2] " Bjorn Helgaas
2016-01-06 22:04 ` Bjorn Helgaas [this message]
2016-02-18 7:17 ` [PATCH] " Sharma, Sanjeev
2016-02-18 15:08 ` Bjorn Helgaas
2016-02-19 9:18 ` Sharma, Sanjeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160106220430.GC16231@localhost \
--to=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).