mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Çağlar Kilimci" <ckilimci@gmail.com>
To: barebox <barebox@lists.infradead.org>
Subject: Bootchooser - remaining_attempts
Date: Wed, 5 Jul 2017 15:36:46 +0300	[thread overview]
Message-ID: <CAGUZs0ke=+-Hc+bj0yKcke_W08CPBBq2tb6Pkq=xL2FjrLb-YQ@mail.gmail.com> (raw)

Hi all,

I am using barebox 2017.03.0 and my bootchooser variables are:
  bootchooser.last_chosen: 2
  bootchooser.retry: true
  bootchooser.system1.boot: system1
  bootchooser.system1.default_attempts: 99
  bootchooser.system1.default_priority: 16
  bootchooser.system1.priority: 20
  bootchooser.system1.remaining_attempts: 5
  bootchooser.system2.boot: system2
  bootchooser.system2.default_attempts: 9
  bootchooser.system2.default_priority: 15
  bootchooser.system2.priority: 10
  bootchooser.system2.remaining_attempts: 3
  bootchooser.targets: system1 system2

And "global.bootchooser.reset_attempts" is empty. I assume counters
will never be reset as written in [1].

So, here is the case that I think it has a problem. system1 has a
problem that does not boot. Bootchooser tries system1 and fails a few
times and then chooses system2. After successful boot of system2,
"bootchooser.system1.remaining_attempts" is still 5. Every boot
sequence bootchooser tries system1 and fails and then system2 is
chosen. If I understand correctly from the documentation, it should be
0 and disabled and will never try at all. Right?

Secondly, There is a bug: if bootchooser.system1.remaining_attempts is
big enough like 10, bootchooser tries to boot system1 as usual and
fails as usual again but it could not boot system2. I am sending the
log below, as a summary "could not open /boot/barebox.env: error 24":
booting 'system1'
sorry, no nested mounts
mount: Device or resource busy
could not open /mnt/rootfs1/boot/zImage: No such file or directory
Booting 'system1' failed: No such file or directory
booting 'system1' failed: No such file or directory
could not open /boot/barebox.env: error 24
Nothing bootable found on 'system2'
Nothing bootable found on 'system2'
Nothing bootable found on 'system2'
bootchooser: No valid targets found:
system1
    id: 1
    priority: 20
    default_priority: 16
    remaining attempts: 0
    default attempts: 99
    boot: 'system1'
    disabled due to remaining attempts = 0
system2
    id: 2
    priority: 10
    default_priority: 15
    remaining attempts: 0
    default attempts: 9
    boot: 'system2'
    disabled due to remaining attempts = 0
booting 'bootchooser' failed: No such file or directory


[1] http://barebox.org/doc/latest/user/bootchooser.html?highlight=reset_attempts

Sincerely,
-- 
Çağlar Kilimci

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

             reply	other threads:[~2017-07-05 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 12:36 Çağlar Kilimci [this message]
2017-07-10  6:48 ` Çağlar Kilimci
2017-07-11  9:45   ` AW: " Martin Hollingsworth
2017-07-12  7:08     ` Çağlar Kilimci
2017-07-11 10:48 ` B Gol

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='CAGUZs0ke=+-Hc+bj0yKcke_W08CPBBq2tb6Pkq=xL2FjrLb-YQ@mail.gmail.com' \
    --to=ckilimci@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