[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2018-06-27 Thread  Christian Ehrhardt 
Setting qemu task to invalid per Colins explanation that the LP case
doesn't use it.

** Changed in: qemu (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

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

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-09-06 Thread LocutusOfBorg
Interesting, so somewhat the system is triggering an illegal arm64
instruction? Can be that gdb needs somebody telling it to use armhf
platform?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-09-06 Thread Colin Watson
qemu isn't involved.  We intentionally run armhf builds on an arm64
kernel (with an appropriate personality set) because this allows us to
make denser use of our build resources; I don't expect this to change.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-08-10 Thread LocutusOfBorg
Well, LP builders have qemu 2.5, so this might be true for the syscall.

However, I appreciate the first point, this is in-line with my
expectations and might be solvable by launchpad buildd team admins.

Can you please have a deeper look now?

thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-08-10 Thread LocutusOfBorg
** Changed in: launchpad-buildd
   Status: Invalid => New

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-08-10 Thread Riku Voipio
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
qemu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-08-09 Thread LocutusOfBorg
>I agree on 384 being getrandom and there are other cases like [1].

I did the same research :)

>I don't know details but would consider the pure lack of the system call 
>support a feature request to >upstream qemu.
>We could add a qemu upstream task here for that FR - in the worst case we are 
>told why we are wrong - >opinions?

yes please!

>On the case itself for now I'd recommend to get back the section:
>ifeq ($(DEB_HOST_ARCH),armhf)
>TERM=vt100 dh_auto_test || true
>
>Which maybe was there for similar reasons.

I think this used to hang the builders, IIRC, but seems to pass now
https://launchpadlibrarian.net/332584378/buildlog_ubuntu-artful-armhf.notmuch_0.25-4ubuntu1_BUILDING.txt.gz

uploaded in artful

G.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]

2017-08-09 Thread ChristianEhrhardt
I agree on 384 being getrandom and there are other cases like [1].
I don't know details but would consider the pure lack of the system call 
support a feature request to upstream qemu.
We could add a qemu upstream task here for that FR - in the worst case we are 
told why we are wrong - opinions?

On the case itself for now I'd recommend to get back the section:
ifeq ($(DEB_HOST_ARCH),armhf)
TERM=vt100 dh_auto_test || true

Which maybe was there for similar reasons.

[1]: https://users.rust-lang.org/t/missing-system-calls-when-running-
tests-under-qemu-arm-at-travisci/5013

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1707409

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

Status in launchpad-buildd:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Confirmed

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
  https://launchpad.net/ubuntu/+source/notmuch/0.21-3ubuntu2/+build/9344826

  and the first bad is this one:  Started on 2016-08-31
  https://launchpad.net/ubuntu/+source/notmuch/0.22.1-2ubuntu1/+build/1062

  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
  
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/13169431
  
https://launchpadlibrarian.net/331134898/buildlog_ubuntu-artful-armhf.notmuch_0.25-2ubuntu1_BUILDING.txt.gz

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1707409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp