There is two issues being mixed up here

1) launchpad buildd changes.

notmuch build system appears to be confused by the new enviroment. It
appears ubuntu has chosen "armhf chroot on arm64 machine" approach,
which would mean qemu system call emulation is not involved. if it is -
it a buildd configuration error.

My suspicion is that notmuch testsuite gets confused in armhf-on-arm64
setup. This setup is a bit shoddy and launchpad should really run the
armhf builders with armhf kernel, which kvm on arm64 host can easily do.

2) The "unsupported syscall" errror.

the pbuilder-based cross-build uses qemu linux-user, so the build env is
not equivalent to what is launchpad.

syscall 384 is getrandom, which qemu does support. You may have too old

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  testsuite fails under qemu (SIGILL) works fine on real hw [missing
  getrandom 384 syscall]

Status in launchpad-buildd:
Status in linux package in Ubuntu:
Status in qemu package in Ubuntu:

Bug description:
  Hello, after spending a lot of time debugging notmuch failure under
  armhf, we came to a conclusion:

  it started to fail when the infra moved to a new kernel 3.2 to a 4.2,
  and moved under qemu/kvm environment.

  the latest successful build is here  created on 2016-03-13

  and the first bad is this one:  Started on 2016-08-31

  Kernel version: Linux kishi10 3.2.0-98-highbank #138-Ubuntu SMP PREEMPT Mon 
Jan 11 13:24:41 UTC 2016 armv7l
  Kernel version: Linux bos01-arm64-024 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 
28 21:24:20 UTC 2016 aarch64

  so, in the first case armhf was ran on top of an armv7 kernel, in the other 
case it became an arm64 one
  this might not even be a regression in qemu/kvm, but rather a change in 
buildd system that spot a new bug

  doing a xenial build failed aswell, so I presume this is not a
  toolchain regression (also because it works fine on real HW), but a
  qemu/linux bug.

  I did run the test under strace/valgrind, I can't do much more testing, but I 
hope the logs can be useful for you

  You can see the strace/valgrind outputs between "BEGIN" and "END"

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to