From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Marek Vasut <marek.vasut@gmail.com>
Subject: RE: [PATCH/RFC v4 0/4] treewide: add regulator condition on _mmc_suspend()
Date: Fri, 3 Jul 2020 11:10:09 +0000 [thread overview]
Message-ID: <TY2PR01MB36922D383DD83EB2DE22F84FD86A0@TY2PR01MB3692.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdX93Q9WhKLqv_wNPzArbc68NcbVN8jJ9MDKxAcicpBQ5Q@mail.gmail.com>
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Tuesday, June 30, 2020 10:19 PM
>
> Hi Shimoda-san,
>
> On Mon, Jun 29, 2020 at 1:49 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Mon, Jun 29, 2020 at 12:04 PM Yoshihiro Shimoda
> > <yoshihiro.shimoda.uh@renesas.com> wrote:
> > > > From: Geert Uytterhoeven, Sent: Friday, June 26, 2020 7:13 PM
> > > > On Fri, Jun 26, 2020 at 11:32 AM Yoshihiro Shimoda
> > > > <yoshihiro.shimoda.uh@renesas.com> wrote:
> > > > > Note that v5.8-rc2 with r8a77951-salvator-xs seems to cause panic from
> > > > > PCI driver when the system is suspended. So, I disabled the PCI
> > > > > devices when I tested this patch series.
> > > >
> > > > Does this happen with current renesas-devel and renesas_defconfig?
> > > > (it doesn't for me)
> > >
> > > Yes. I enabled PM_DEBUG and E1000E though.
> > >
> > > > Do you have any PCIe devices attached? (I haven't)
> > >
> > > Yes. (Intel Ethernet card is connected to the PCI slot.)
> > >
> > > < my environment >
> > > - r8a77961-salvator-xs
> > > - renesas-devel-2020-06-26-v5.8-rc2
> > > + renesas_defconfig + PM_DEBUG + E1000E
> > > - initramfs
> >
> > Doesn't fail for me on R-Car H3 ES2.0, so it needs the presence of a
> > PCIe card. Unfortunately I haven't any (added to shopping wishlist).
>
> [...]
>
> > The failure mode looks like the PCI card is accessed while the PCI host
> > bridge has been suspended.
>
> Does "[PATCH v1] driver core: Fix suspend/resume order issue with
> deferred probe"[1] help?
>
> [1] https://lore.kernel.org/lkml/20200625032430.152447-1-saravanak@google.com/
Even if I applied this patch, the issue still happened unfortunately.
By the way, I'm guessing the issue is related to my environment which uses BSP's ATF.
According to the commit log of upstream ATF [1], PCIe hardware is possible to causes SError.
Unfortunately, I cannot try to update the firmware for some reasons now... I'll prepare
updated firmware somehow...
[1]
https://github.com/ARM-software/arm-trusted-firmware/commit/0969397f295621aa26b3d14b76dd397d22be58bf
Best regards,
Yoshihiro Shimoda
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
next prev parent reply other threads:[~2020-07-03 11:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 9:32 [PATCH/RFC v4 0/4] treewide: add regulator condition on _mmc_suspend() Yoshihiro Shimoda
2020-06-26 9:32 ` [PATCH/RFC v4 1/4] regulator: core: add prepare and resume_early Yoshihiro Shimoda
2020-06-26 13:51 ` kernel test robot
2020-06-26 14:30 ` Mark Brown
2020-06-29 2:12 ` Yoshihiro Shimoda
2020-06-26 9:32 ` [PATCH/RFC v4 2/4] regulator: fixed: add regulator_ops members for suspend/resume Yoshihiro Shimoda
2020-06-26 14:39 ` Mark Brown
2020-06-29 2:42 ` Yoshihiro Shimoda
2020-06-29 12:57 ` Mark Brown
2020-06-29 13:40 ` Sudeep Holla
2020-06-29 14:15 ` Geert Uytterhoeven
2020-06-29 15:07 ` Sudeep Holla
2020-06-29 16:14 ` Mark Brown
2020-06-29 16:42 ` Sudeep Holla
2020-06-29 17:26 ` Mark Brown
2020-06-29 17:42 ` Sudeep Holla
2020-06-30 8:29 ` Yoshihiro Shimoda
2020-06-26 9:32 ` [PATCH/RFC v4 3/4] mmc: core: Call mmc_poweroff_nofity() if regulators are disabled Yoshihiro Shimoda
2020-06-26 15:13 ` Mark Brown
2020-06-29 2:49 ` Yoshihiro Shimoda
2020-06-26 15:53 ` Sergei Shtylyov
2020-06-29 5:16 ` Yoshihiro Shimoda
2020-06-26 9:32 ` [PATCH/RFC v4 4/4] arm64: dts: renesas: add regulator-off-in-suspend property for eMMC Yoshihiro Shimoda
2020-06-26 10:13 ` [PATCH/RFC v4 0/4] treewide: add regulator condition on _mmc_suspend() Geert Uytterhoeven
2020-06-29 10:04 ` Yoshihiro Shimoda
2020-06-29 11:49 ` Geert Uytterhoeven
2020-06-30 13:19 ` Geert Uytterhoeven
2020-07-03 11:10 ` Yoshihiro Shimoda [this message]
2020-07-06 11:14 ` Geert Uytterhoeven
2020-08-11 13:50 ` E1000 s2idle crash (was: Re: [PATCH/RFC v4 0/4] treewide: add regulator condition on _mmc_suspend()) Geert Uytterhoeven
2020-08-17 12:00 ` Yoshihiro Shimoda
2020-08-27 9:15 ` Geert Uytterhoeven
2020-08-27 9:16 ` Geert Uytterhoeven
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=TY2PR01MB36922D383DD83EB2DE22F84FD86A0@TY2PR01MB3692.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.