All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Wunderlich <frank-w@public-files.de>
To: u-boot@lists.denx.de
Subject: Aw: Re: [PATCH] board: mediatek: disable watchdog on BananaPi R2
Date: Mon, 11 Jan 2021 11:24:18 +0100	[thread overview]
Message-ID: <trinity-61c25538-af2e-4a82-9dc8-edda2c779948-1610360658293@3c-app-gmx-bap07> (raw)
In-Reply-To: <ffc645d4-f14b-d620-0bf4-18a2b0eca482@gmx.de>


> Gesendet: Montag, 11. Januar 2021 um 09:57 Uhr
> Von: "Heinrich Schuchardt" <xypron.glpk@gmx.de>

> I observed that on some recent version Linux before 5.10 booting seemed
> to be delayed by dozens of seconds on many boards. On which Linux
> version did you see the problem?
>
> >>>
> >>> I've not much experience (yet) with the "EFI stub". But if it takes
> >>> this
> >>> long, wouldn't it make sense that this stub also supports the WDT?
> >>
> >> efi_timer_check() calls WATCHDOG_RESET() trying to avoid that the
> >> hardware watchdog is triggered.

> > So efi_timer_check() is called quite frequently and should be enough
> > to reset the U-Boot WDT while residing in EFI? Not sure, why the reset
> > occurs in Matthias's case then.

Matthias could you check if/when/how often efi_timer_check is called in you bootprocess?

> efi_timer_check() is only invoked, if the UEFI API is invoked.
> Especially if the problem occurs after ExitBootServices() it is not
> called anymore.
>
> >
> >> There is a software watchdog
> >> defaulting to 5 minutes in efi_watchdog.c which can be modified
> >> via the EFI API.

> It would be interesting to understand if your problem occurs before or
> after efi_exit_boot_services() is called. You could you add printf()
> statements after EFI_ENTRY() and before EFI_EXIT() to see if it is reached.
>
> Could you further, please, test if adding wdt_stop() to the start of
> do_bootefi() in cmd/bootefi.c solves your problem.

should efi_timer_check not be called there to reset WDT-timer a last time to leave the
maximum time for booting linux kernel? maybe a wdt_stop is not neccessary anymore then

regards Frank

  reply	other threads:[~2021-01-11 10:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 15:36 [PATCH] board: mediatek: disable watchdog on BananaPi R2 matthias.bgg at kernel.org
2021-01-08  7:39 ` Stefan Roese
2021-01-09  2:32   ` Matthias Brugger
2021-01-09 14:57     ` Stefan Roese
2021-01-10 18:44       ` Matthias Brugger
2021-01-10 18:55         ` Matthias Brugger
2021-01-11  7:02         ` Stefan Roese
2021-01-11  7:17           ` Heinrich Schuchardt
2021-01-11  7:48             ` Stefan Roese
2021-01-11  8:57               ` Heinrich Schuchardt
2021-01-11 10:24                 ` Frank Wunderlich [this message]
2021-01-11 10:50                   ` Aw: " Heinrich Schuchardt
2021-01-11 15:44                 ` Matthias Brugger

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=trinity-61c25538-af2e-4a82-9dc8-edda2c779948-1610360658293@3c-app-gmx-bap07 \
    --to=frank-w@public-files.de \
    --cc=u-boot@lists.denx.de \
    /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.