[Kernel-packages] [Bug 1707409] Re: testsuite fails under qemu (SIGILL) works fine on real hw [missing getrandom 384 syscall]
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 1440536] Re: Oops __d_lookup+0x88/0x194
This has also been reproduced on wilu 4.2.0-16-generic #19-Ubuntu -- 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/1440536 Title: Oops __d_lookup+0x88/0x194 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Vivid: Triaged Bug description: This started happening on a Mustang board after upgrading to 3.19.0-9.9 and persists in 3.19.0-11. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-11-generic 3.19.0-11.11 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 31 1969 seq crw-rw 1 root audio 116, 33 Dec 31 1969 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.17-0ubuntu1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Sun Apr 5 08:32:28 2015 HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,115200n8 ro earlyprintk=uart8250-32bit,0x1c02 RelatedPackageVersions: linux-restricted-modules-3.19.0-11-generic N/A linux-backports-modules-3.19.0-11-generic N/A linux-firmware 1.143 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux SystemImageInfo: current build number: 0 device name: ? channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1440536/+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
Re: [Kernel-packages] [Bug 1396470] Re: please enable CONFIG_VIRTIO_MMIO on armmp
Hi Paolo, Thanks for quick update. previous boot time (with SD emulation): Up 113.00 seconds. with your kernel and virtio disk:Up 78.19 seconds. So yes, works perfectly! On 2 December 2014 at 13:08, Paolo Pisati 1396...@bugs.launchpad.net wrote: can you try one of these kernels and report if it solves the problem for you? http://people.canonical.com/~ppisati/lp1396470/ thanks! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1396470 Title: please enable CONFIG_VIRTIO_MMIO on armmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396470/+subscriptions -- 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/1396470 Title: please enable CONFIG_VIRTIO_MMIO on armmp Status in linux package in Ubuntu: Triaged Bug description: Hi, The current armmp (linux- image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio enabled for faster vm guests. Currenlty it seems to have: CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y # CONFIG_VIRTIO_BALLOON is not set # CONFIG_VIRTIO_MMIO is not set Now using virtio net and block is not possible, and you have to revert to emulated devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396470/+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 1396470] [NEW] please enable CONFIG_VIRTIO_MMIO on armmp
Public bug reported: Hi, The current armmp (linux-image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio enabled for faster vm guests. Currenlty it seems to have: CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y # CONFIG_VIRTIO_BALLOON is not set # CONFIG_VIRTIO_MMIO is not set Now using virtio net and block is not possible, and you have to revert to emulated devices. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1396470 Title: please enable CONFIG_VIRTIO_MMIO on armmp Status in “linux” package in Ubuntu: New Bug description: Hi, The current armmp (linux- image-3.16.0-26-generic_3.16.0-26.34_armhf.deb) could have virtio-mmio enabled for faster vm guests. Currenlty it seems to have: CONFIG_NET_9P_VIRTIO=m CONFIG_VIRTIO_BLK=y CONFIG_SCSI_VIRTIO=m CONFIG_VIRTIO_NET=y CONFIG_CAIF_VIRTIO=m CONFIG_VIRTIO_CONSOLE=y CONFIG_HW_RANDOM_VIRTIO=m CONFIG_VIRTIO=y CONFIG_VIRTIO_PCI=y # CONFIG_VIRTIO_BALLOON is not set # CONFIG_VIRTIO_MMIO is not set Now using virtio net and block is not possible, and you have to revert to emulated devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396470/+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
