From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: reset / watchdog on an imx7d soc
Date: Mon, 29 Jun 2020 12:53:07 +0200 (CEST) [thread overview]
Message-ID: <517310923.70062.1593427992397@mail.vodafone.de> (raw)
In-Reply-To: <d999acb9-ed34-7b02-42cf-675a152ddee3@pengutronix.de>
Hi,
> On June 29, 2020 at 10:44 AM Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
>
>
> Hello Giorgio,
>
> On 6/23/20 5:11 PM, Giorgio Dal Molin wrote:
> > Hi Fabio,
> >
> > thank you for your quick reply.
> >
> > I've already found the errata you linked in your mail but I had no success
> > applying the suggestion there; maybe I'm doing it wrong.
> > Let's take the Option 3 there:
>
> Does reset within Linux (with say the imx_v6_v7_defconfg) work?
No. I see the same behavior also with the kernel: after a 'shutdown -r'
the system 'goes down' but doesn't reboot, it just hang:
~ # shutdown -r
system is going down for reboot NOW
...
[ 46.248222] 000: ci_hdrc ci_hdrc.0: remove, state 1
[ 46.248253] 000: usb usb1: USB disconnect, device number 1
[ 46.248263] 000: usb 1-1: USB disconnect, device number 2
The same happens if I kill the 'watchdog' process: after ~2 seconds
the system just hangs.
I'm sure there must be a solution because the original u-boot bootloader
for the cpu module I'm using reboots the system as expected, through the wdog1;
unfortunately it's not so trivial to find what makes the difference.
giorgio
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-06-29 10:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 13:45 Giorgio Dal Molin
2020-06-23 13:53 ` Fabio Estevam
2020-06-23 15:11 ` Giorgio Dal Molin
2020-06-29 8:44 ` Ahmad Fatoum
2020-06-29 10:53 ` Giorgio Dal Molin [this message]
2020-06-29 13:30 ` Ahmad Fatoum
2020-06-29 15:30 ` Giorgio Dal Molin
2020-06-29 15:35 ` Ahmad Fatoum
2020-06-29 16:03 ` Giorgio Dal Molin
2020-06-29 16:11 ` Ahmad Fatoum
2020-06-29 16:33 ` Giorgio Dal Molin
2020-06-29 16:39 ` Fabio Estevam
2020-07-01 9:52 ` Giorgio Dal Molin
2020-07-02 9:25 ` Ahmad Fatoum
2020-07-02 14:51 ` Giorgio Dal Molin
2020-07-02 15:28 ` Giorgio Dal Molin
2020-07-02 16:05 ` Lucas Stach
2020-07-03 14:13 ` Giorgio Dal Molin
2020-07-02 16:24 ` Fabio Estevam
2020-07-07 5:52 ` Giorgio Dal Molin
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=517310923.70062.1593427992397@mail.vodafone.de \
--to=giorgio.nicole@arcor.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=festevam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox