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 config
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
Sta
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 i
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_VIRTI
4 matches
Mail list logo