mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Frederick Gotham <cauldwell.thomas@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: Watchdog Timer with x86 processor
Date: Tue, 7 Jan 2020 11:23:16 -0000 (UTC)	[thread overview]
Message-ID: <XnsAB3D73D8140D5fgotham@195.159.176.226> (raw)
In-Reply-To: <ee89e9f9-7ddf-ef42-0ad6-5881c74ebb48@pengutronix.de>

Ahmad Fatoum <a.fatoum@pengutronix.de> wrote in
news:ee89e9f9-7ddf-ef42-0ad6-5881c74ebb48@pengutronix.de: 

> As described in the linked documentation, it's useless for monitoring
> Linux boot, because it's a boot service and these are terminated very
> early in the Linux boot process.
> 
> Only usable x86 watchdog we have at the moment is the Fintek Super I/O
> watchdog. If you have another Super I/O, but your BIOS exports a WDAT
> ACPI table, barebox v2019.01.0 will come with ACPI driver support, so
> you could write an ACPI driver on top. Alternatively, you could turn on
> the watchdog in the BIOS and leave barebox out of it altogether.



Just to be clear about what I'm doing.

I have an embedded Linux device whose CPU is 64-Bit quad-core.

Once the device has successfully booted up, there is a watchdog timer that 
makes sure everything keeps running smoothly. So if my device freezes AFTER 
it boots up successfully, then this eventuality is dealt with.

What I have NOT dealt with though, is the case of the device freezing mid-
boot. So let's say that Barebox tries to load the Linux kernel, and let's say 
the kernel get 15% loaded and then it freezes. If this happens, I need the 
device to reboot.

How would you go about this? Would you use the watchdog timer in the BIOS, or 
would you use the one in Barebox?


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-01-07 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 13:27 Frederick Gotham
2020-01-06 13:47 ` Rouven Czerwinski
2020-01-06 14:13   ` Ahmad Fatoum
2020-01-07 11:23     ` Frederick Gotham [this message]
2020-01-07 15:38       ` Ahmad Fatoum

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=XnsAB3D73D8140D5fgotham@195.159.176.226 \
    --to=cauldwell.thomas@gmail.com \
    --cc=barebox@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