All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: "Mohit P. Tahiliani" <tahiliani@nitk.edu.in>
Cc: Dhaval Khandla <dhavaljkhandla26@gmail.com>,
	Manish Kumar B <bmanish15597@gmail.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"David S. Miller" <davem@davemloft.net>,
	Dave Taht <dave.taht@gmail.com>,
	Leslie Monis <lesliemonis@gmail.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	"Sachin D. Patil" <sdp.sachin@gmail.com>,
	broonie@kernel.org,
	Hrishikesh Hiraskar <hrishihiraskar@gmail.com>,
	Arnd Bergmann <arnd@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: [BUG] Linux-next fails to link on ARM in allmodconfig and allyesconfig
Date: Thu, 28 Feb 2019 10:29:42 +0300	[thread overview]
Message-ID: <0B49A364-A5EC-4E23-BA39-9946523A1BAA@linaro.org> (raw)

Hi Mohit,

It seems that your commit 3f7ae5f3dc5295ac17d6521130ed8a8f8a723fbf causes a link failure for ARM in allmodconfig and allyesconfig.  This happens for at least gcc-8 compiler.
===
ERROR: "__aeabi_uldivmod" [net/sched/sch_pie.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
===

Would you please investigate?  Below are diagnostics from Linaro's automated bisection job.

===
Culprit:
<cut>
commit 3f7ae5f3dc5295ac17d6521130ed8a8f8a723fbf
Author: Mohit P. Tahiliani <tahiliani@nitk.edu.in>
Date:   Tue Feb 26 00:39:59 2019 +0530

   net: sched: pie: add more cases to auto-tune alpha and beta

   The current implementation scales the local alpha and beta
   variables in the calculate_probability function by the same
   amount for all values of drop probability below 1%.

   RFC 8033 suggests using additional cases for auto-tuning
   alpha and beta when the drop probability is less than 1%.

   In order to add more auto-tuning cases, MAX_PROB must be
   scaled by u64 instead of u32 to prevent underflow when
   scaling the local alpha and beta variables in the
   calculate_probability function.

   Signed-off-by: Mohit P. Tahiliani <tahiliani@nitk.edu.in>
   Signed-off-by: Dhaval Khandla <dhavaljkhandla26@gmail.com>
   Signed-off-by: Hrishikesh Hiraskar <hrishihiraskar@gmail.com>
   Signed-off-by: Manish Kumar B <bmanish15597@gmail.com>
   Signed-off-by: Sachin D. Patil <sdp.sachin@gmail.com>
   Signed-off-by: Leslie Monis <lesliemonis@gmail.com>
   Acked-by: Dave Taht <dave.taht@gmail.com>
   Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
   Signed-off-by: David S. Miller <davem@davemloft.net>
</cut>

Results regressed from (for last_good == 30a92ad703b93a96588e05b5bcd7247d7350c673)
reset_artifacts:
-10
build_abe binutils:
-9
build_abe stage1:
-8
linux_n_obj:
26184
linux build successful:
all

to (for first_bad == 3f7ae5f3dc5295ac17d6521130ed8a8f8a723fbf)
reset_artifacts:
-10
build_abe binutils:
-9
build_abe stage1:
-8
linux_n_obj:
19184

First few errors in logs of first_bad:
ERROR: "__aeabi_uldivmod" [net/sched/sch_pie.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

Artifacts of last_good build: https://ci.linaro.org/job/tcwg_kernel-bisect-gnu-release-arm-next-allmodconfig/18/artifact/artifacts/build-30a92ad703b93a96588e05b5bcd7247d7350c673/
Artifacts of first_bad build: https://ci.linaro.org/job/tcwg_kernel-bisect-gnu-release-arm-next-allmodconfig/18/artifact/artifacts/build-3f7ae5f3dc5295ac17d6521130ed8a8f8a723fbf/
===

--
Maxim Kuvyrkov
www.linaro.org




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-02-28  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28  7:29 Maxim Kuvyrkov [this message]
2019-02-28  7:38 ` [BUG] Linux-next fails to link on ARM in allmodconfig and allyesconfig Leslie Monis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0B49A364-A5EC-4E23-BA39-9946523A1BAA@linaro.org \
    --to=maxim.kuvyrkov@linaro.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@linaro.org \
    --cc=bmanish15597@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dave.taht@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dhavaljkhandla26@gmail.com \
    --cc=hrishihiraskar@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=lesliemonis@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sdp.sachin@gmail.com \
    --cc=tahiliani@nitk.edu.in \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.