Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #730255

Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25

From Elliott Mitchell <ehem+debian@m5p.com>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25
Date 2016-04-10 20:20 +0200
Message-ID <rms7M-CA-11@gated-at.bofh.it> (permalink)
References <rmcw1-5PO-3@gated-at.bofh.it> <rmjHc-2L7-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


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:
> > Between 3.16.7-ctk20 and 3.16.7-ctk25 the kexec functionality of the
> > Linux kernel was damaged.????The system I'm looking at uses a 3.3 kernel
> > to load the "real" kernel off a filesystem and kexec into that.????The 3.3
> > kernel was able to successfully kexec into a 3.16.7-ctk20 kernel, but
> > is unable to kexec into a 3.16.7-ctk25 kernel.????However I found the
> > 3.16.7-ctk20 IS able to successfully kexec the 3.16.7-ctk25 kernel.
> 
> Surely this is a bug in the built-in (3.3) kernel, not the new one? ??If
> there's something simple that can be done in the Debian kernel to work
> around this, we should do that, but otherwise you're stuck with this.

This is certainly a reasonable theory.  Alas, I cannot speak to which of
these theories is correct.  All I can say for certain is that something
changed between ctk20 and ctk25 which made the 3.3 kernel unable to kexec
ctk25.  I'm under the impression as of 3.3 the kexec functionality was
supposed to be stable on MIPS, but that could be incorrect.

I should also note, during the failed kexecs I would see the messages
from the 3.3 kernel saying the kexec was starting, but never see any
messages from the ctk25 kernel.  Unless someone wants to send me a JTAG
decoder that is all I can say.


> > 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.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         EHeM+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Back to linux.debian.bugs.dist | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Elliott Mitchell <ehem+debian@m5p.com> - 2016-04-10 03:40 +0200
  Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Ben Hutchings <ben@decadent.org.uk> - 2016-04-10 11:20 +0200
    Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Elliott Mitchell <ehem+debian@m5p.com> - 2016-04-10 20:20 +0200
      Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Ben Hutchings <ben@decadent.org.uk> - 2016-04-10 21:00 +0200
        Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Elliott Mitchell <ehem+debian@m5p.com> - 2016-04-10 23:40 +0200
          Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Ben Hutchings <ben@decadent.org.uk> - 2016-04-11 02:40 +0200
            Bug#820567: kexec on mipsel partially broken between ckt20 and ckt25 Elliott Mitchell <ehem+debian@m5p.com> - 2016-04-11 08:00 +0200

csiph-web