{standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

{standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

[kernel test robot]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   27bbf45eae9ca98877a2d52a92a188147cd61b07
commit: 481461f5109919babbb393d6f68002936b8e2493 linux/export.h: make <linux/export.h> independent of CONFIG_MODULES
date:   9 weeks ago
config: m68k-randconfig-r025-20230123 (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309222350.hCUFrIQ1-lkp@intel.com/

All errors (new ones prefixed by >>):

   {standard input}: Assembler messages:
   {standard input}:1198: Error: value -148 out of range
>> {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

Re: {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

[Geert Uytterhoeven]

Dear robot,

On Fri, Sep 22, 2023 at 5:23 PM kernel test robot <lkp@intel.com> wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   27bbf45eae9ca98877a2d52a92a188147cd61b07
> commit: 481461f5109919babbb393d6f68002936b8e2493 linux/export.h: make <linux/export.h> independent of CONFIG_MODULES
> date:   9 weeks ago
> config: m68k-randconfig-r025-20230123 (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202309222350.hCUFrIQ1-lkp@intel.com/

Thanks for your report!

> All errors (new ones prefixed by >>):
>
>    {standard input}: Assembler messages:
>    {standard input}:1198: Error: value -148 out of range
> >> {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

Do you have more context (e.g. which source file is being compiled)?
Thanks!

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

Re: {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

[Yujie Liu]

Hi Geert,

On Mon, Sep 25, 2023 at 02:07:07PM +0200, Geert Uytterhoeven wrote:
> Dear robot,
> 
> On Fri, Sep 22, 2023 at 5:23 PM kernel test robot <lkp@intel.com> wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   27bbf45eae9ca98877a2d52a92a188147cd61b07
> > commit: 481461f5109919babbb393d6f68002936b8e2493 linux/export.h: make <linux/export.h> independent of CONFIG_MODULES
> > date:   9 weeks ago
> > config: m68k-randconfig-r025-20230123 (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/config)
> > compiler: m68k-linux-gcc (GCC) 13.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202309222350.hCUFrIQ1-lkp@intel.com/
> 
> Thanks for your report!
> 
> > All errors (new ones prefixed by >>):
> >
> >    {standard input}: Assembler messages:
> >    {standard input}:1198: Error: value -148 out of range
> > >> {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533
> 
> Do you have more context (e.g. which source file is being compiled)?
> Thanks!

Sorry for our late reply. It is sound/soc/codecs/tas2781-fmwlib.o that
is being compiled.

{standard input}: Assembler messages:
{standard input}:1198: Error: value -148 out of range
{standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533
make[6]: *** [scripts/Makefile.build:243: sound/soc/codecs/tas2781-fmwlib.o] Error 1

We rechecked the bisection process and found that this was a false
positive report. The error also happens on the parent of this commit.

{standard input}: Assembler messages:
{standard input}:992: Error: value -148 out of range
{standard input}:992: Error: value of ffffff6c too large for field of 1 byte at 0000045f
make[6]: *** [scripts/Makefile.build:243: sound/soc/codecs/tas2781-fmwlib.o] Error 1

The error message has some minor changes that our bot didn't recognize
that it is the same error on both commits. We will fix this soon. Sorry
for making the noise.

Best Regards,
Yujie

Re: {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533

[Geert Uytterhoeven]

Hi Yujie,

On Thu, Oct 12, 2023 at 6:18 PM Yujie Liu <yujie.liu@intel.com> wrote:
> On Mon, Sep 25, 2023 at 02:07:07PM +0200, Geert Uytterhoeven wrote:
> > On Fri, Sep 22, 2023 at 5:23 PM kernel test robot <lkp@intel.com> wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head:   27bbf45eae9ca98877a2d52a92a188147cd61b07
> > > commit: 481461f5109919babbb393d6f68002936b8e2493 linux/export.h: make <linux/export.h> independent of CONFIG_MODULES
> > > date:   9 weeks ago
> > > config: m68k-randconfig-r025-20230123 (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/config)
> > > compiler: m68k-linux-gcc (GCC) 13.2.0
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230922/202309222350.hCUFrIQ1-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202309222350.hCUFrIQ1-lkp@intel.com/
> >
> > Thanks for your report!
> >
> > > All errors (new ones prefixed by >>):
> > >
> > >    {standard input}: Assembler messages:
> > >    {standard input}:1198: Error: value -148 out of range
> > > >> {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533
> >
> > Do you have more context (e.g. which source file is being compiled)?
> > Thanks!
>
> Sorry for our late reply. It is sound/soc/codecs/tas2781-fmwlib.o that
> is being compiled.
>
> {standard input}: Assembler messages:
> {standard input}:1198: Error: value -148 out of range
> {standard input}:1198: Error: value of ffffff6c too large for field of 1 byte at 00000533
> make[6]: *** [scripts/Makefile.build:243: sound/soc/codecs/tas2781-fmwlib.o] Error 1
>
> We rechecked the bisection process and found that this was a false
> positive report. The error also happens on the parent of this commit.
>
> {standard input}: Assembler messages:
> {standard input}:992: Error: value -148 out of range
> {standard input}:992: Error: value of ffffff6c too large for field of 1 byte at 0000045f
> make[6]: *** [scripts/Makefile.build:243: sound/soc/codecs/tas2781-fmwlib.o] Error 1
>
> The error message has some minor changes that our bot didn't recognize
> that it is the same error on both commits. We will fix this soon. Sorry
> for making the noise.

Thanks for the information!

In the mean time, I found out which file was the culprit when someone
posted a patch.

The real issue seems to be a compile bug, though, cfr.
https://lore.kernel.org/all/CAMuHMdXRGxnGpVHiB+Zvxq+G4K-BL8JsJGbG+7CNtJiqGwHOsQ@mail.gmail.com
https://lore.kernel.org/all/87v8bn3cae.fsf@igel.home

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