[REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[Marcel Ziswiler]

Hi there

I noticed that at least today's and yesterdays -next won't build with
the imx_v6_v7_defconfig giving the following error:

  LD      arch/arm/boot/compressed/vmlinux
arch/arm/boot/compressed/head.o: In function `restart':
(.text+0xa8): undefined reference to `__hyp_stub_vectors'
(.text+0xac): undefined reference to `__hyp_stub_vectors'

Has anybody seen that as well and knows what is going on?

Thanks!

Cheers

Marcel

Re: [REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[Daniel Baluta]

On Wed, 2018-12-19 at 12:42 +0000, Marcel Ziswiler wrote:
> Hi there
> 
> I noticed that at least today's and yesterdays -next won't build with
> the imx_v6_v7_defconfig giving the following error:
> 
>   LD      arch/arm/boot/compressed/vmlinux
> arch/arm/boot/compressed/head.o: In function `restart':
> (.text+0xa8): undefined reference to `__hyp_stub_vectors'
> (.text+0xac): undefined reference to `__hyp_stub_vectors'
> 
> Has anybody seen that as well and knows what is going on?

Hmm, works for me.

Using linux-next, master branch. HEAD commit:

commit 02fc169594e96f7c51c4f23114e12b7a18e85a0a (HEAD -> master, tag:
next-20181219, origin/master, origin/HEAD)
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date:   Wed Dec 19 18:42:46 2018 +1100

    Add linux-next specific files for 20181219
    
    Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>


Using gcc version 7.3.0 (GCC).

Re: [REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[Daniel Baluta]

On Wed, Dec 19, 2018 at 3:17 PM Daniel Baluta <daniel.baluta@nxp.com> wrote:
>
>
> On Wed, 2018-12-19 at 12:42 +0000, Marcel Ziswiler wrote:
> > Hi there
> >
> > I noticed that at least today's and yesterdays -next won't build with
> > the imx_v6_v7_defconfig giving the following error:
> >
> >   LD      arch/arm/boot/compressed/vmlinux
> > arch/arm/boot/compressed/head.o: In function `restart':
> > (.text+0xa8): undefined reference to `__hyp_stub_vectors'
> > (.text+0xac): undefined reference to `__hyp_stub_vectors'
> >
> > Has anybody seen that as well and knows what is going on?
>
> Hmm, works for me.
>
> Using linux-next, master branch. HEAD commit:
>
> commit 02fc169594e96f7c51c4f23114e12b7a18e85a0a (HEAD -> master, tag:
> next-20181219, origin/master, origin/HEAD)
> Author: Stephen Rothwell <sfr@canb.auug.org.au>
> Date:   Wed Dec 19 18:42:46 2018 +1100
>
>     Add linux-next specific files for 20181219
>
>     Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
>
> Using gcc version 7.3.0 (GCC).


On the other hand I'm getting this warning:

arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning (spi_bus_bridge):
/soc/aips-bus@40080000/spi@400ad000: incorrect #address-cells for SPI
bus
  also defined at arch/arm/boot/dts/vf610-bk4.dts:107.8-119.3
arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
prerequisite 'spi_bus_bridge'


Maybe Rob can jump in?

thanks,
Daniel.

Re: [REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[Fabio Estevam]

Hi Daniel,

On Wed, Dec 19, 2018 at 11:32 AM Daniel Baluta <daniel.baluta@gmail.com> wrote:
>
> On Wed, Dec 19, 2018 at 3:17 PM Daniel Baluta <daniel.baluta@nxp.com> wrote:
> >
> >
> > On Wed, 2018-12-19 at 12:42 +0000, Marcel Ziswiler wrote:
> > > Hi there
> > >
> > > I noticed that at least today's and yesterdays -next won't build with
> > > the imx_v6_v7_defconfig giving the following error:
> > >
> > >   LD      arch/arm/boot/compressed/vmlinux
> > > arch/arm/boot/compressed/head.o: In function `restart':
> > > (.text+0xa8): undefined reference to `__hyp_stub_vectors'
> > > (.text+0xac): undefined reference to `__hyp_stub_vectors'
> > >
> > > Has anybody seen that as well and knows what is going on?
> >
> > Hmm, works for me.

Yes, I haven't seen build failures reported by the autobuilders:
http://kisskb.ellerman.id.au/kisskb/target/7464/

> On the other hand I'm getting this warning:
>
> arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning (spi_bus_bridge):
> /soc/aips-bus@40080000/spi@400ad000: incorrect #address-cells for SPI
> bus
>   also defined at arch/arm/boot/dts/vf610-bk4.dts:107.8-119.3
> arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> prerequisite 'spi_bus_bridge'
>
>
> Maybe Rob can jump in?

Yes, I have already reported this warning to Rob and Lukasz. Hopefully
they could help fixing it.

Re: [REGRESSION] imx_v6_v7_defconfig: undefined reference to `__hyp_stub_vectors'

[Marcel Ziswiler]

On Wed, 2018-12-19 at 12:20 -0200, Fabio Estevam wrote:
> Hi Daniel,
> 
> On Wed, Dec 19, 2018 at 11:32 AM Daniel Baluta <
> daniel.baluta@gmail.com> wrote:
> > On Wed, Dec 19, 2018 at 3:17 PM Daniel Baluta <
> > daniel.baluta@nxp.com> wrote:
> > > 
> > > On Wed, 2018-12-19 at 12:42 +0000, Marcel Ziswiler wrote:
> > > > Hi there
> > > > 
> > > > I noticed that at least today's and yesterdays -next won't
> > > > build with
> > > > the imx_v6_v7_defconfig giving the following error:
> > > > 
> > > >   LD      arch/arm/boot/compressed/vmlinux
> > > > arch/arm/boot/compressed/head.o: In function `restart':
> > > > (.text+0xa8): undefined reference to `__hyp_stub_vectors'
> > > > (.text+0xac): undefined reference to `__hyp_stub_vectors'
> > > > 
> > > > Has anybody seen that as well and knows what is going on?
> > > 
> > > Hmm, works for me.
> 
> Yes, I haven't seen build failures reported by the autobuilders:
> http://kisskb.ellerman.id.au/kisskb/target/7464/

Hm, strange. A clean re-build using ARM's latest gcc 8.2.1 now worked
fine as well. Sorry, for the noise.

> > On the other hand I'm getting this warning:
> > 
> > arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning
> > (spi_bus_bridge):
> > /soc/aips-bus@40080000/spi@400ad000: incorrect #address-cells for
> > SPI
> > bus
> >   also defined at arch/arm/boot/dts/vf610-bk4.dts:107.8-119.3
> > arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> > prerequisite 'spi_bus_bridge'
> > 
> > 
> > Maybe Rob can jump in?
> 
> Yes, I have already reported this warning to Rob and Lukasz.
> Hopefully
> they could help fixing it.