From: Thang Nguyen OS <thang@amperemail.onmicrosoft.com>
To: openbmc@lists.ozlabs.org
Subject: Re: New u-boot-aspeed-sdk runs slow and cause wdt2 timeout on ast2500
Date: Wed, 23 Feb 2022 10:12:13 +0700 [thread overview]
Message-ID: <c34486d6-50c0-761e-7fd2-d6ba3b14ebce@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <CAGm54UE7-QxGBniV3J2jnBiW4ygvRcHxKd=G88PsOiNZP+hBTA@mail.gmail.com>
On 23/02/2022 09:15, Lei Yu wrote:
> On the latest master with u-boot-aspeed v00.04.09 SDK, an issue occurs
> on g220a that it runs slower than before and gets wdt2 timeout.
> We reverted the u-boot to a version before v00.04.09 SDK (b0fe8fd9d)
> and the issue is gone.
>
> Below are some details:
> * Before v00.04.09: u-boot works OK, and it takes about 9~10 seconds
> to load and start the kernel including the 2 seconds timeout for
> autoboot, the kernel starts OK and it kicks the watchdog as long as
> the driver is loaded.
> * With v00.04.09: u-boot runs slower than before, and it takes about
> **16 seconds** to load and start the kernel (including 2s timeout for
> autoboot), then the kernel does not have enough time to run and loads
> the watchdog driver, and the wdt2 times out on about 22s.
>
> Be noted that the issue is observed on g220a that is based on AST2500,
> and could not be reproduced in QEMU. I think it could be reproduced on
> other systems with AST2500.
>
I checked and saw the same issue with Ampere Mt.Jade. If I stop and
u-boot prompt and disable watchdog via "mw 0x1e78502c 0", the command
does not happen.
prev parent reply other threads:[~2022-02-23 3:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 2:15 New u-boot-aspeed-sdk runs slow and cause wdt2 timeout on ast2500 Lei Yu
2022-02-23 2:38 ` ChiaWei Wang
2022-02-23 3:01 ` Lei Yu
2022-02-23 4:36 ` ChiaWei Wang
2022-02-23 5:11 ` Joel Stanley
2022-02-23 10:02 ` Lei Yu
2022-02-24 3:45 ` Joel Stanley
2022-02-23 3:12 ` Thang Nguyen OS [this message]
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=c34486d6-50c0-761e-7fd2-d6ba3b14ebce@amperemail.onmicrosoft.com \
--to=thang@amperemail.onmicrosoft.com \
--cc=openbmc@lists.ozlabs.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).