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


Groups > linux.kernel > #1345114 > unrolled thread

Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

Started bykbuild test robot <fengguang.wu@intel.com>
First post2016-02-28 00:50 +0100
Last post2016-03-01 03:30 +0100
Articles 8 — 5 participants

Back to article view | Back to linux.kernel


Contents

  Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k,  microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64,  blackfin, avr32, nds32, or1k kbuild test robot <fengguang.wu@intel.com> - 2016-02-28 00:50 +0100
    Re: Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k,  microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64,  blackfin, avr32, nds32, or1k Geert Uytterhoeven <geert@linux-m68k.org> - 2016-02-28 09:50 +0100
      Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm,  x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh,  sparc, sparc64, blackfin, avr32, nds32, or1k Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:10 +0100
        Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm,  x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh,  sparc, sparc64, blackfin, avr32, nds32, or1k Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:50 +0100
          Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm,  x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh,  sparc, sparc64, blackfin, avr32, nds32, or1k Michael Ellerman <mpe@ellerman.id.au> - 2016-03-01 04:20 +0100
            Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm,  x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh,  sparc, sparc64, blackfin, avr32, nds32, or1k Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 04:40 +0100
    Re: Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k,  microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64,  blackfin, avr32, nds32, or1k Thomas Gleixner <tglx@linutronix.de> - 2016-02-28 10:30 +0100
      Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm,  x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh,  sparc, sparc64, blackfin, avr32, nds32, or1k Fengguang Wu <fengguang.wu@intel.com> - 2016-03-01 03:30 +0100

#1345114 — Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

Fromkbuild test robot <fengguang.wu@intel.com>
Date2016-02-28 00:50 +0100
SubjectInvalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r6WMx-1YM-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi Thomas,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   691429e13dfaf5b0994b07cc166db41bd608ee3d
commit: dcaab54e348c5b66cca4802815ceebd37059e70c timekeeping: Remove ktime_get_monotonic_offset()
date:   1 year, 7 months ago
config: xtensa-common_defconfig (attached as .config)
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout dcaab54e348c5b66cca4802815ceebd37059e70c
        # save the attached .config to linux build tree
        make.cross ARCH=xtensa 

All errors (new ones prefixed by >>):

>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
   Usage: /usr/bin/mkimage -l image
   -l ==> list image header information
   /usr/bin/mkimage -A arch -O os -T type -C comp -a addr -e ep -n name -d image
   -A ==> set architecture to 'arch'
   -O ==> set operating system to 'os'
   -T ==> set image type to 'type'
   -C ==> set compression type 'comp'
   -a ==> set load address to 'addr' (hex)
   ==> set entry point to 'ep' (hex)
   ==> set image name to 'name'-d ==> use image data from 'datafile'
   -x ==> set XIP (execute in place)
   /usr/bin/mkimage [-D dtc_options] -f fit-image.its fit-image
   /usr/bin/mkimage -V ==> print version information and exit

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[toc] | [next] | [standalone]


#1345187

FromGeert Uytterhoeven <geert@linux-m68k.org>
Date2016-02-28 09:50 +0100
Message-ID<r75d8-89y-7@gated-at.bofh.it>
In reply to#1345114
Hi Fengguang,

On Sun, Feb 28, 2016 at 12:51 AM, kbuild test robot
<fengguang.wu@intel.com> wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   691429e13dfaf5b0994b07cc166db41bd608ee3d
> commit: dcaab54e348c5b66cca4802815ceebd37059e70c timekeeping: Remove ktime_get_monotonic_offset()
> date:   1 year, 7 months ago
> config: xtensa-common_defconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout dcaab54e348c5b66cca4802815ceebd37059e70c
>         # save the attached .config to linux build tree
>         make.cross ARCH=xtensa
>
> All errors (new ones prefixed by >>):
>
>>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
>    Usage: /usr/bin/mkimage -l image

Don't you just need to update mkimage to a version that does have
xtensa support?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

[toc] | [prev] | [next] | [standalone]


#1346293 — Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

FromFengguang Wu <fengguang.wu@intel.com>
Date2016-03-01 03:10 +0100
SubjectRe: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r7HV8-2Mh-3@gated-at.bofh.it>
In reply to#1345187
Hi Geert,

> >         make.cross ARCH=xtensa
> >
> > All errors (new ones prefixed by >>):
> >
> >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> >    Usage: /usr/bin/mkimage -l image
> 
> Don't you just need to update mkimage to a version that does have
> xtensa support?

Yeah, thanks for the suggestion!
I'll upgrade the u-boot-tools package which contains /usr/bin/mkimage.

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]


#1346315 — Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

FromFengguang Wu <fengguang.wu@intel.com>
Date2016-03-01 03:50 +0100
SubjectRe: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r7IxP-2Zx-1@gated-at.bofh.it>
In reply to#1346293
On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote:
> Hi Geert,
> 
> > >         make.cross ARCH=xtensa
> > >
> > > All errors (new ones prefixed by >>):
> > >
> > >>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> > >    Usage: /usr/bin/mkimage -l image
> > 
> > Don't you just need to update mkimage to a version that does have
> > xtensa support?
> 
> Yeah, thanks for the suggestion!
> I'll upgrade the u-boot-tools package which contains /usr/bin/mkimage.

Hi Geert,

I've upgraded the Debian u-boot-tools to 2016.01+dfsg1-2:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version                 Architecture            Description
+++-====================================-=======================-=======================-=============================================================================
ii  u-boot-tools                         2016.01+dfsg1-2         amd64                   companion tools for Das U-Boot bootloader

But still find it not support xtensa..

$ strings /usr/bin/mkimage|g xtensa
<EMPTY>

I do see there is an xtensa patch 2 years ago:

http://lists.denx.de/pipermail/u-boot/2014-April/178467.html

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]


#1346341 — Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

FromMichael Ellerman <mpe@ellerman.id.au>
Date2016-03-01 04:20 +0100
SubjectRe: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r7J0S-3vn-9@gated-at.bofh.it>
In reply to#1346315
On Tue, 2016-03-01 at 10:48 +0800, Fengguang Wu wrote:
> On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote:
> > Hi Geert,
> > 
> > > >         make.cross ARCH=xtensa
> > > > 
> > > > All errors (new ones prefixed by >>):
> > > > 
> > > > > > Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> > > >    Usage: /usr/bin/mkimage -l image
> > > 
> > > Don't you just need to update mkimage to a version that does have
> > > xtensa support?
> > 
> > Yeah, thanks for the suggestion!
> > I'll upgrade the u-boot-tools package which contains /usr/bin/mkimage.
> 
> Hi Geert,
> 
> I've upgraded the Debian u-boot-tools to 2016.01+dfsg1-2:
> 
> Desired=Unknown/Install/Remove/Purge/Hold

> > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

> > > / Name                                 Version                 Architecture            Description
> +++-====================================-=======================-=======================-=============================================================================
> ii  u-boot-tools                         2016.01+dfsg1-2         amd64                   companion tools for Das U-Boot bootloader
> 
> But still find it not support xtensa..
> 
> $ strings /usr/bin/mkimage|g xtensa
> <EMPTY>

Hmm, true, same here.

Kisskb is building xtensa happily, there must be something in .config which
controls whether it uses mkimage?

  http://kisskb.ellerman.id.au/kisskb/buildresult/12621125/
  http://kisskb.ellerman.id.au/kisskb/target/2029/

cheers

[toc] | [prev] | [next] | [standalone]


#1346347 — Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

FromFengguang Wu <fengguang.wu@intel.com>
Date2016-03-01 04:40 +0100
SubjectRe: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r7Jke-3EW-9@gated-at.bofh.it>
In reply to#1346341

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 01, 2016 at 02:15:27PM +1100, Michael Ellerman wrote:
> On Tue, 2016-03-01 at 10:48 +0800, Fengguang Wu wrote:
> > On Tue, Mar 01, 2016 at 10:06:19AM +0800, Fengguang Wu wrote:
> > > Hi Geert,
> > > 
> > > > >         make.cross ARCH=xtensa
> > > > > 
> > > > > All errors (new ones prefixed by >>):
> > > > > 
> > > > > > > Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> > > > >    Usage: /usr/bin/mkimage -l image
> > > > 
> > > > Don't you just need to update mkimage to a version that does have
> > > > xtensa support?
> > > 
> > > Yeah, thanks for the suggestion!
> > > I'll upgrade the u-boot-tools package which contains /usr/bin/mkimage.
> > 
> > Hi Geert,
> > 
> > I've upgraded the Debian u-boot-tools to 2016.01+dfsg1-2:
> > 
> > Desired=Unknown/Install/Remove/Purge/Hold
> 
> > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> > > / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> 
> > > > / Name                                 Version                 Architecture            Description
> > +++-====================================-=======================-=======================-=============================================================================
> > ii  u-boot-tools                         2016.01+dfsg1-2         amd64                   companion tools for Das U-Boot bootloader
> > 
> > But still find it not support xtensa..
> > 
> > $ strings /usr/bin/mkimage|g xtensa
> > <EMPTY>
> 
> Hmm, true, same here.
> 
> Kisskb is building xtensa happily, there must be something in .config which
> controls whether it uses mkimage?
> 
>   http://kisskb.ellerman.id.au/kisskb/buildresult/12621125/
>   http://kisskb.ellerman.id.au/kisskb/target/2029/

It looks you are using xtensa-defconfig, while the error here is
caught only in xtensa-common_defconfig (attached).

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]


#1345196

FromThomas Gleixner <tglx@linutronix.de>
Date2016-02-28 10:30 +0100
Message-ID<r75PQ-db-11@gated-at.bofh.it>
In reply to#1345114
On Sun, 28 Feb 2016, kbuild test robot wrote:

> Hi Thomas,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   691429e13dfaf5b0994b07cc166db41bd608ee3d
> commit: dcaab54e348c5b66cca4802815ceebd37059e70c timekeeping: Remove ktime_get_monotonic_offset()
> date:   1 year, 7 months ago
> config: xtensa-common_defconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout dcaab54e348c5b66cca4802815ceebd37059e70c
>         # save the attached .config to linux build tree
>         make.cross ARCH=xtensa 
> 
> All errors (new ones prefixed by >>):
> 
> >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
>    Usage: /usr/bin/mkimage -l image
>    -l ==> list image header information
>    /usr/bin/mkimage -A arch -O os -T type -C comp -a addr -e ep -n name -d image
>    -A ==> set architecture to 'arch'
>    -O ==> set operating system to 'os'
>    -T ==> set image type to 'type'
>    -C ==> set compression type 'comp'
>    -a ==> set load address to 'addr' (hex)
>    ==> set entry point to 'ep' (hex)
>    ==> set image name to 'name'-d ==> use image data from 'datafile'
>    -x ==> set XIP (execute in place)
>    /usr/bin/mkimage [-D dtc_options] -f fit-image.its fit-image
>    /usr/bin/mkimage -V ==> print version information and exit

How is removing a unused function related to a tool problem?

Hint:

>> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips,\
    mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

Your mkimage does not support xtensa .....

Thanks,

	tglx

[toc] | [prev] | [next] | [standalone]


#1346304 — Re: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k

FromFengguang Wu <fengguang.wu@intel.com>
Date2016-03-01 03:30 +0100
SubjectRe: [kbuild-all] Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
Message-ID<r7Ieu-2Sw-7@gated-at.bofh.it>
In reply to#1345196
On Sun, Feb 28, 2016 at 10:24:42AM +0100, Thomas Gleixner wrote:
> On Sun, 28 Feb 2016, kbuild test robot wrote:
> 
> > Hi Thomas,
> > 
> > FYI, the error/warning still remains.
> > 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   691429e13dfaf5b0994b07cc166db41bd608ee3d
> > commit: dcaab54e348c5b66cca4802815ceebd37059e70c timekeeping: Remove ktime_get_monotonic_offset()
> > date:   1 year, 7 months ago
> > config: xtensa-common_defconfig (attached as .config)
> > reproduce:
> >         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         git checkout dcaab54e348c5b66cca4802815ceebd37059e70c
> >         # save the attached .config to linux build tree
> >         make.cross ARCH=xtensa 
> > 
> > All errors (new ones prefixed by >>):
> > 
> > >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips, mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> >    Usage: /usr/bin/mkimage -l image
> >    -l ==> list image header information
> >    /usr/bin/mkimage -A arch -O os -T type -C comp -a addr -e ep -n name -d image
> >    -A ==> set architecture to 'arch'
> >    -O ==> set operating system to 'os'
> >    -T ==> set image type to 'type'
> >    -C ==> set compression type 'comp'
> >    -a ==> set load address to 'addr' (hex)
> >    ==> set entry point to 'ep' (hex)
> >    ==> set image name to 'name'-d ==> use image data from 'datafile'
> >    -x ==> set XIP (execute in place)
> >    /usr/bin/mkimage [-D dtc_options] -f fit-image.its fit-image
> >    /usr/bin/mkimage -V ==> print version information and exit
> 
> How is removing a unused function related to a tool problem?

Sorry, I triggered a batch of bisects for aged errors. This one looks
a problem with the tool rather than regression by some kernel commit.
Which confused the bisect.

> Hint:
> 
> >> Invalid CPU Type - valid names are: alpha, arm, x86, ia64, m68k, microblaze, mips,\
>     mips64, nios2, powerpc, ppc, s390, sh, sparc, sparc64, blackfin, avr32, nds32, or1k
> 
> Your mkimage does not support xtensa .....

Yeah, just upgraded the mkimage tool!

Thanks,
Fengguang

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web