Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12016] Grub fails to boot bzImage after upgrade to 2019.05
Date: Mon, 29 Jul 2019 14:38:44 +0000	[thread overview]
Message-ID: <bug-12016-163-P1O1LF6pLh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12016-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12016

Wojciech Ziniewicz <wojciech.ziniewicz@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Wojciech Ziniewicz <wojciech.ziniewicz@gmail.com> ---
Hey,

After more and more testing we've found out what was the issue. We were using
cache in our build system and with enough many changes to the configuration we
ended up with some sort of cache-polluted unbootable state. Removing the cache
and switching back from -O3 to -O2 fixed the issue once and for all.

This can be safely closed now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2019-07-29 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12016-163@https.bugs.busybox.net/>
2019-07-08 13:39 ` [Buildroot] [Bug 12016] Grub fails to boot bzImage after upgrade to 2019.05 bugzilla at busybox.net
2019-07-08 13:39 ` bugzilla at busybox.net
2019-07-18 19:02 ` bugzilla at busybox.net
2019-07-29 14:38 ` bugzilla at busybox.net [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=bug-12016-163-P1O1LF6pLh@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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