Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 11:00 PM, Fengguang Wuwrote: > > Ah the root cause is these reminding reports for old errors Thanks for looking into it, the report looked a bit scary ;) Linus
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 11:00 PM, Fengguang Wu wrote: > > Ah the root cause is these reminding reports for old errors Thanks for looking into it, the report looked a bit scary ;) Linus
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Mon, Oct 31, 2016 at 12:58:14PM +0800, Fengguang Wu wrote: Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robotwrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. This "BUILD REGRESSION" report lists errors in all commits of a branch -- ie. not only the showed HEAD commit. Sure "all commits" will be too huge for the mainline kernel, so there will be limits applied. Did perhaps something change in the kbuild test robot? Recently we lowered the threshold to 2 before sending unsolicited reports like this. That threshold means when we find >= 3 errors in a tree, only the first 2 will be reported in the regular way (reporting to the first bad commit). The more errors will be send in a summary "BUILD REGRESSION" email listing all the triggered errors. That's a trick to avoid flooding possibly large number of duplicate error reports to LKML while avoiding hiding possibly non-duplicate errors. It works well for normal branches, however looks less effective for linus/master because here we have less clue about the origin of errors. So sorry -- this report is a noise. The fix could be to raise the reporting threshold significantly for linus/master. It's also possible some bug in the 0day-bot triggered this report unexpectedly. Ah the root cause is these reminding reports for old errors https://lists.01.org/pipermail/kbuild-all/2016-October/026922.html https://lists.01.org/pipermail/kbuild-all/2016-October/025857.html https://lists.01.org/pipermail/kbuild-all/2016-October/026677.html ... There are some few of them, which triggered the threshold logic. Regards, Fengguang
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Mon, Oct 31, 2016 at 12:58:14PM +0800, Fengguang Wu wrote: Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. This "BUILD REGRESSION" report lists errors in all commits of a branch -- ie. not only the showed HEAD commit. Sure "all commits" will be too huge for the mainline kernel, so there will be limits applied. Did perhaps something change in the kbuild test robot? Recently we lowered the threshold to 2 before sending unsolicited reports like this. That threshold means when we find >= 3 errors in a tree, only the first 2 will be reported in the regular way (reporting to the first bad commit). The more errors will be send in a summary "BUILD REGRESSION" email listing all the triggered errors. That's a trick to avoid flooding possibly large number of duplicate error reports to LKML while avoiding hiding possibly non-duplicate errors. It works well for normal branches, however looks less effective for linus/master because here we have less clue about the origin of errors. So sorry -- this report is a noise. The fix could be to raise the reporting threshold significantly for linus/master. It's also possible some bug in the 0day-bot triggered this report unexpectedly. Ah the root cause is these reminding reports for old errors https://lists.01.org/pipermail/kbuild-all/2016-October/026922.html https://lists.01.org/pipermail/kbuild-all/2016-October/025857.html https://lists.01.org/pipermail/kbuild-all/2016-October/026677.html ... There are some few of them, which triggered the threshold logic. Regards, Fengguang
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robotwrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. This "BUILD REGRESSION" report lists errors in all commits of a branch -- ie. not only the showed HEAD commit. Sure "all commits" will be too huge for the mainline kernel, so there will be limits applied. Did perhaps something change in the kbuild test robot? Recently we lowered the threshold to 2 before sending unsolicited reports like this. That threshold means when we find >= 3 errors in a tree, only the first 2 will be reported in the regular way (reporting to the first bad commit). The more errors will be send in a summary "BUILD REGRESSION" email listing all the triggered errors. That's a trick to avoid flooding possibly large number of duplicate error reports to LKML while avoiding hiding possibly non-duplicate errors. It works well for normal branches, however looks less effective for linus/master because here we have less clue about the origin of errors. So sorry -- this report is a noise. The fix could be to raise the reporting threshold significantly for linus/master. It's also possible some bug in the 0day-bot triggered this report unexpectedly. Regards, Fengguang
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
Hi Linus, On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. This "BUILD REGRESSION" report lists errors in all commits of a branch -- ie. not only the showed HEAD commit. Sure "all commits" will be too huge for the mainline kernel, so there will be limits applied. Did perhaps something change in the kbuild test robot? Recently we lowered the threshold to 2 before sending unsolicited reports like this. That threshold means when we find >= 3 errors in a tree, only the first 2 will be reported in the regular way (reporting to the first bad commit). The more errors will be send in a summary "BUILD REGRESSION" email listing all the triggered errors. That's a trick to avoid flooding possibly large number of duplicate error reports to LKML while avoiding hiding possibly non-duplicate errors. It works well for normal branches, however looks less effective for linus/master because here we have less clue about the origin of errors. So sorry -- this report is a noise. The fix could be to raise the reporting threshold significantly for linus/master. It's also possible some bug in the 0day-bot triggered this report unexpectedly. Regards, Fengguang
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: > On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot >wrote: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net > > Hmm. The build errors seem to be pretty independent of that merge, > including internal compiler errors etc. > > Did perhaps something change in the kbuild test robot? thanks Linus, we will double check this, and provide info. > > Linus >
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 01:25:50PM -0700, Linus Torvalds wrote: > On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot > wrote: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net > > Hmm. The build errors seem to be pretty independent of that merge, > including internal compiler errors etc. > > Did perhaps something change in the kbuild test robot? thanks Linus, we will double check this, and provide info. > > Linus >
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robotwrote: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. Did perhaps something change in the kbuild test robot? Linus
Re: [linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
On Sun, Oct 30, 2016 at 11:03 AM, kbuild test robot wrote: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net Hmm. The build errors seem to be pretty independent of that merge, including internal compiler errors etc. Did perhaps something change in the kbuild test robot? Linus
[linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net arch/ia64/kernel/entry.S:622: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191) arch/ia64/kernel/fsys.S:67: Error: Operand 3 of `add' should be a general register r0-r3 arch/ia64/kernel/ivt.S:761: Error: Operand 3 of `add' should be a general register r0-r3 arch/mips/kernel/mips-cpc.c:47: undefined reference to `mips_cpc_default_phys_base' arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32' arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32' arch/mips/vdso/sigreturn.S:1:0: error: '-march=r3000' requires '-mfp32' arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction cc1: error: '-march=r3000' requires '-mfp32' collect2: error: ld returned 1 exit status drivers/auxdisplay/img-ascii-lcd.c:384: undefined reference to `devm_ioremap_resource' drivers/bluetooth/hci_intel.c:1199: undefined reference to `devm_gpiod_get' drivers/extcon/extcon-gpio.c:69: undefined reference to `devm_gpio_request_one' drivers/extcon/extcon-max3355.c:68: undefined reference to `devm_gpiod_get' drivers/extcon/extcon-usb-gpio.c:104: undefined reference to `devm_gpiod_get' drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function drivers/iio/accel/mma9551.c:421: undefined reference to `devm_gpiod_get_index' drivers/iio/dac/ad5592r-base.c:163: undefined reference to `devm_gpiod_get_optional' drivers/iio/magnetometer/ak8975.c:886: undefined reference to `devm_gpio_request_one' drivers/iio/pressure/bmp280-core.c:985: undefined reference to `devm_gpiod_get' drivers/iio/pressure/hp03.c:238: undefined reference to `devm_gpiod_get_index' drivers/iio/proximity/sx9500.c:877: undefined reference to `devm_gpiod_get_index' drivers/leds/leds-gpio.c:101: undefined reference to `devm_gpio_request_one' drivers/leds/leds-gpio.c:172: undefined reference to `devm_get_gpiod_from_child' drivers/leds/leds-ktd2692.c:272: undefined reference to `devm_gpiod_get' drivers/leds/leds-lp55xx-common.c:402: undefined reference to `devm_gpio_request_one' drivers/leds/leds-lp8860.c:383: undefined reference to `devm_gpiod_get_optional' drivers/leds/leds-lt3593.c:98: undefined reference to `devm_gpio_request_one' drivers/net/dsa/mv88e6xxx/chip.c:4022: undefined reference to `devm_gpiod_get_optional' drivers/net/phy/at803x.c:283: undefined reference to `devm_gpiod_get_optional' drivers/net/phy/mdio-gpio.c:177: undefined reference to `devm_gpio_request' drivers/nfc/fdp/i2c.c:326: undefined reference to `devm_gpiod_get' drivers/nfc/nfcmrvl/main.c:127: undefined reference to `devm_gpio_request_one' drivers/nfc/nfcmrvl/main.c:198: undefined reference to `devm_gpio_free' drivers/nfc/nxp-nci/i2c.c:361: undefined reference to `devm_gpio_request_one' drivers/nfc/st21nfca/i2c.c:597: undefined reference to `devm_gpio_request_one' drivers/nfc/st-nci/i2c.c:300: undefined reference to `devm_gpio_request_one' drivers/power/supply/bq24257_charger.c:876: undefined reference to `devm_gpiod_get_optional' drivers/power/supply/bq24735-charger.c:389: undefined reference to `devm_gpiod_get_optional' drivers/power/supply/bq25890_charger.c:726: undefined reference to `devm_gpiod_get_index' drivers/power/supply/max8903_charger.c:248: undefined reference to `devm_gpio_request' drivers/power/supply/sbs-battery.c:803: undefined reference to `devm_gpiod_get_optional' drivers/pps/clients/pps-gpio.c:125: undefined reference to `devm_gpio_request' drivers/regulator/lp872x.c:773: undefined reference to `devm_gpio_request_one' drivers/regulator/max8952.c:249: undefined reference to `devm_gpio_request_one' drivers/regulator/max8973-regulator.c:715: undefined reference to `devm_gpio_request_one' drivers/regulator/pwm-regulator.c:387: undefined reference to `devm_gpiod_get_optional' drivers/regulator/tps62360-regulator.c:433: undefined reference to `devm_gpio_request_one' ERROR: "bad_dma_ops" [sound/core/snd-pcm.ko] undefined! ERROR: "bad_dma_ops" [sound/soc/bcm/snd-soc-cygnus.ko] undefined! ERROR: "devm_get_gpiod_from_child" [drivers/leds/leds-gpio.ko] undefined! ERROR: "devm_gpiod_get" [drivers/bluetooth/hci_uart.ko] undefined! ERROR: "devm_gpiod_get" [drivers/extcon/extcon-max3355.ko] undefined! ERROR: "devm_gpiod_get" [drivers/extcon/extcon-usb-gpio.ko] undefined! ERROR: "devm_gpiod_get" [drivers/iio/pressure/bmp280.ko] undefined! ERROR: "devm_gpiod_get" [drivers/leds/leds-ktd2692.ko] undefined! ERROR: "devm_gpiod_get" [drivers/nfc/fdp/fdp_i2c.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/accel/mma9551.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/pressure/hp03.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/proximity/sx9500.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/power/supply/bq25890_charger.ko] undefined! ERROR:
[linus:master] BUILD REGRESSION 2a26d99b251b8625d27aed14e97fc10707a3a81f
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master 2a26d99b251b8625d27aed14e97fc10707a3a81f Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net arch/ia64/kernel/entry.S:622: Error: Operand 2 of `adds' should be a 14-bit integer (-8192-8191) arch/ia64/kernel/fsys.S:67: Error: Operand 3 of `add' should be a general register r0-r3 arch/ia64/kernel/ivt.S:761: Error: Operand 3 of `add' should be a general register r0-r3 arch/mips/kernel/mips-cpc.c:47: undefined reference to `mips_cpc_default_phys_base' arch/mips/vdso/elf.S:1:0: error: '-march=r3000' requires '-mfp32' arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3000' requires '-mfp32' arch/mips/vdso/sigreturn.S:1:0: error: '-march=r3000' requires '-mfp32' arch/xtensa/include/asm/initialize_mmu.h:41: Error: invalid register 'atomctl' for 'wsr' instruction cc1: error: '-march=r3000' requires '-mfp32' collect2: error: ld returned 1 exit status drivers/auxdisplay/img-ascii-lcd.c:384: undefined reference to `devm_ioremap_resource' drivers/bluetooth/hci_intel.c:1199: undefined reference to `devm_gpiod_get' drivers/extcon/extcon-gpio.c:69: undefined reference to `devm_gpio_request_one' drivers/extcon/extcon-max3355.c:68: undefined reference to `devm_gpiod_get' drivers/extcon/extcon-usb-gpio.c:104: undefined reference to `devm_gpiod_get' drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function drivers/iio/accel/mma9551.c:421: undefined reference to `devm_gpiod_get_index' drivers/iio/dac/ad5592r-base.c:163: undefined reference to `devm_gpiod_get_optional' drivers/iio/magnetometer/ak8975.c:886: undefined reference to `devm_gpio_request_one' drivers/iio/pressure/bmp280-core.c:985: undefined reference to `devm_gpiod_get' drivers/iio/pressure/hp03.c:238: undefined reference to `devm_gpiod_get_index' drivers/iio/proximity/sx9500.c:877: undefined reference to `devm_gpiod_get_index' drivers/leds/leds-gpio.c:101: undefined reference to `devm_gpio_request_one' drivers/leds/leds-gpio.c:172: undefined reference to `devm_get_gpiod_from_child' drivers/leds/leds-ktd2692.c:272: undefined reference to `devm_gpiod_get' drivers/leds/leds-lp55xx-common.c:402: undefined reference to `devm_gpio_request_one' drivers/leds/leds-lp8860.c:383: undefined reference to `devm_gpiod_get_optional' drivers/leds/leds-lt3593.c:98: undefined reference to `devm_gpio_request_one' drivers/net/dsa/mv88e6xxx/chip.c:4022: undefined reference to `devm_gpiod_get_optional' drivers/net/phy/at803x.c:283: undefined reference to `devm_gpiod_get_optional' drivers/net/phy/mdio-gpio.c:177: undefined reference to `devm_gpio_request' drivers/nfc/fdp/i2c.c:326: undefined reference to `devm_gpiod_get' drivers/nfc/nfcmrvl/main.c:127: undefined reference to `devm_gpio_request_one' drivers/nfc/nfcmrvl/main.c:198: undefined reference to `devm_gpio_free' drivers/nfc/nxp-nci/i2c.c:361: undefined reference to `devm_gpio_request_one' drivers/nfc/st21nfca/i2c.c:597: undefined reference to `devm_gpio_request_one' drivers/nfc/st-nci/i2c.c:300: undefined reference to `devm_gpio_request_one' drivers/power/supply/bq24257_charger.c:876: undefined reference to `devm_gpiod_get_optional' drivers/power/supply/bq24735-charger.c:389: undefined reference to `devm_gpiod_get_optional' drivers/power/supply/bq25890_charger.c:726: undefined reference to `devm_gpiod_get_index' drivers/power/supply/max8903_charger.c:248: undefined reference to `devm_gpio_request' drivers/power/supply/sbs-battery.c:803: undefined reference to `devm_gpiod_get_optional' drivers/pps/clients/pps-gpio.c:125: undefined reference to `devm_gpio_request' drivers/regulator/lp872x.c:773: undefined reference to `devm_gpio_request_one' drivers/regulator/max8952.c:249: undefined reference to `devm_gpio_request_one' drivers/regulator/max8973-regulator.c:715: undefined reference to `devm_gpio_request_one' drivers/regulator/pwm-regulator.c:387: undefined reference to `devm_gpiod_get_optional' drivers/regulator/tps62360-regulator.c:433: undefined reference to `devm_gpio_request_one' ERROR: "bad_dma_ops" [sound/core/snd-pcm.ko] undefined! ERROR: "bad_dma_ops" [sound/soc/bcm/snd-soc-cygnus.ko] undefined! ERROR: "devm_get_gpiod_from_child" [drivers/leds/leds-gpio.ko] undefined! ERROR: "devm_gpiod_get" [drivers/bluetooth/hci_uart.ko] undefined! ERROR: "devm_gpiod_get" [drivers/extcon/extcon-max3355.ko] undefined! ERROR: "devm_gpiod_get" [drivers/extcon/extcon-usb-gpio.ko] undefined! ERROR: "devm_gpiod_get" [drivers/iio/pressure/bmp280.ko] undefined! ERROR: "devm_gpiod_get" [drivers/leds/leds-ktd2692.ko] undefined! ERROR: "devm_gpiod_get" [drivers/nfc/fdp/fdp_i2c.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/accel/mma9551.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/pressure/hp03.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/iio/proximity/sx9500.ko] undefined! ERROR: "devm_gpiod_get_index" [drivers/power/supply/bq25890_charger.ko] undefined! ERROR: