From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Evgeniy Dushistov <dushistov@mail.ru>
Cc: <xen-devel@lists.xensource.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jonathan Cameron <jic23@kernel.org>, "Jens Axboe" <axboe@fb.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92)
Date: Mon, 19 Jun 2017 15:36:47 +0100 [thread overview]
Message-ID: <22855.57727.390987.969954@mariner.uk.xensource.com> (raw)
In-Reply-To: <E1dMx2x-0007xW-D8@osstest.test-lab.xenproject.org>
osstest service owner writes ("[linux-linus bisection] complete build-i386-pvops"):
> branch xen-unstable
> xenbranch xen-unstable
> job build-i386-pvops
> testid kernel-build
>
> Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> Bug introduced: edf9364d3f924aff6f77176b8e52a4b68e5c30d6
> Bug not present: 791a9a666d1afe2603bcb2c6a4852d684e879252
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/110566/
This is a merge commit, so the bisection result is not very useful:
git-log --pretty=oneline 791a9a666d1afe2603bcb2c6a4852d684e879252..edf9364d3f924aff6f77176b8e52a4b68e5c30d6 | wc -l
2233
The error message is this:
ERROR: "__udivdi3" [fs/ufs/ufs.ko] undefined!
scripts/Makefile.modpost:91: recipe for target '__modpost' failed
make[1]: *** [__modpost] Error 1
I searched the commit log and CC'd a couple of people who have fixed
similar bugs elsewhere.
Ian.
next parent reply other threads:[~2017-06-19 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dMx2x-0007xW-D8@osstest.test-lab.xenproject.org>
2017-06-19 14:36 ` Ian Jackson [this message]
2017-06-19 15:08 ` Al Viro
2017-06-19 17:22 ` Geert Uytterhoeven
2017-06-19 17:34 ` Al Viro
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=22855.57727.390987.969954@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=axboe@fb.com \
--cc=dushistov@mail.ru \
--cc=jic23@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome