Skip to contentSkip to conversation

Grub fails to boot bzImage after upgrade to 2019.05

Buildroot bugzilla at busybox.net 1 participant 4 messages Jul 8, 2019 – Jul 29, 2019 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

bugzilla at busybox.net

author
#1 lore raw

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

Wojciech Ziniewicz <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

          Component|Bugzilla                    |Other
   Target Milestone|---                         |2019.05
                 CC|                            |buildroot at uclibc.org
            Product|Infrastructure              |buildroot
            Version|unspecified                 |2019.05
Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
author
#3 lore raw
In reply to a message not in the archive

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

Carlos Santos <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

           Assignee|unassigned at buildroot.uclibc |unixmania at gmail.com
                   |.org                        |
             Status|NEW                         |ASSIGNED

--- Comment #1 from Carlos Santos <[email protected]> --- I'm taking this one.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
author
#4 lore raw
In reply to a message not in the archive

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

Wojciech Ziniewicz <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Wojciech Ziniewicz <[email protected]> --- 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.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.