On Sun, 2016-04-10 at 14:32 -0700, Elliott Mitchell wrote: > On Sun, Apr 10, 2016 at 07:47:28PM +0100, Ben Hutchings wrote: > > > > On Sun, 2016-04-10 at 11:09 -0700, Elliott Mitchell wrote: > > > > > > On Sun, Apr 10, 2016 at 10:09:38AM +0100, Ben Hutchings wrote: > > > > > > > > > > > > On Sat, 2016-04-09 at 18:31 -0700, Elliott Mitchell wrote: [...] > > > > > Doing a double-kexec does work around the issue, but it means I need > > > > > to > > > > > hold onto that one magic kernel for the moment... > > > > > > > > > > In other news, it appears sometime between 3.3 and 3.10 there started > > > > > being a requirement for GCC 4.8 on mipsel. > > > > Packages in jessie must be buildable using compiler versions in jessie. > > > > That means either gcc-4.8 or gcc-4.9. > > > linux-source-3.16 is available as a backport to wheezy, which does not > > > feature gcc-4.8. > > That in no way contradicts what I said. :-) ??When I backport the linux > > source package from jessie to wheezy I change it to use gcc-4.6. > > > > But the linux-source-X.Y packages (which are a different thing to the > > linux source package!) don't specify any particular compiler version. > > You can choose that with the CC variable; otherwise the default > > compiler (specified by the gcc package) will be used. > For this particular mipsel device I was unable to kexec the kernel unless > it was built with GCC-4.8.
I see. > If the kernel was built with GCC-4.7 or > earlier, I got symptoms identical to the above, messages from the old > kernel on the console serial port that it was going away and kexec'd > kernel never output any messages. I could believe this is a funky > compiler issue. Could it be the kernel image is close to a critical size limit? The kernel typically gets slightly larger with each stable update. Does gcc 4.8 generate a smaller or larger kernel image than older versions? Ben. -- Ben Hutchings Humans are not rational beings; they are rationalising beings.
signature.asc
Description: This is a digitally signed message part
