[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
I reproduce this with: sudo qemu-debootstrap --arch armel natty natty-armel http://ports.ubuntu.com/ubuntu-ports sudo chroot natty-armel /bin/bash echo 'deb http://ports.ubuntu.com/ubuntu-ports natty main' > /etc/apt/sources.list apt-get update apt-get install --reinstall console-setup [...] Unpacking replacement console-setup ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up console-setup (1.57ubuntu5) ... qemu: Unsupported syscall: 250 plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed. qemu: uncaught target signal 6 (Aborted) - core dumped Aborted (core dumped) Unknown name $sun_t6_custom I think plymouth does some epoll_create, that returns ENOSYS or fails or another reason, so it aborts. I'm moving this to qemu-linaro as to implement epoll_create -- I think we do have this on ARM nowadays. ** Package changed: qemu-kvm (Ubuntu) => qemu-linaro (Ubuntu) ** Summary changed: - qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) + Missing emulation for epoll_create syscall ** Also affects: qemu-linaro Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/644961 Title: Missing emulation for epoll_create syscall -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
This occurred while configuring the same package using linaro headless 20110208 with identical error messages: qemu: Unsupported syscall: 250 plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed. qemu: uncaught target signal 6 (Aborted) - core dumped Aborted ** Changed in: qemu-kvm (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/644961 Title: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/644961 Title: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
This is the rootstock command I use:
sudo ./rootstock \
--fqdn NGP \
--login myuser \
--password mypassword \
--imagesize 1G \
--serial ttyS2 \
--doswap \
--swapsize 256 \
--script ${HOME}/rootstock/setup.sh \
--mirror http://localhost/ubuntu-armel \
--manifest ${HOME}/rootstock/manifest.txt \
--extra-mirror http://localhost/my-custom-packages \
--locale en_US.UTF-8
where:
setup.sh is a file with my customization
http://localhost/ubuntu-armel is my local repository (mirrored with
apt-mirror to the ubuntu official one)
http://localhost/my-custom-packages is a local repository with some custom
packages
The final images is generated w/o problem during the output (attached)
but in the bootstrap.log (it is attached too) I see some errors:
Unsupported ioctl: cmd=0xc020660b < repeted more times
and
Setting up console-setup (1.34ubuntu15) ...
qemu: Unsupported syscall: 250
plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd
>= 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted
update-initramfs: deferring update (trigger activated)
Anyway, I have never started up the image using qemu... I only need the
ubuntu archive image to install in my board but looking in
/var/log/bootstrap.log I saw those errors...
Again, using my generated built image, sometimes I experience a lot of
"Segmentation fault" or "Illegal instruction" running some common tools
like "top, grep, ps, ls etc...", should it be related to the error
above?
** Attachment added: "rootstock flow and bootstrap.txt"
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/644961/+attachment/1626094/+files/rootstock-logs.zip
--
qemu crash in rootstock second step during "Setting up console-setup
(1.34ubuntu15)" (log reported in bootstrap.log)
https://bugs.launchpad.net/bugs/644961
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
Thanks for reporting this bug and helping to make Ubuntu better. Could you tell us the precise rootstock command you used, how you subsequently started up the image (full kvm commandline), and attach the bootstrap.log? ** Changed in: qemu-kvm (Ubuntu) Status: New => Incomplete -- qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) https://bugs.launchpad.net/bugs/644961 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621358/+files/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621359/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621360/+files/Dependencies.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621361/+files/Lspci.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621362/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621363/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621364/+files/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621365/+files/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621366/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/644961/+attachment/1621367/+files/UdevLog.txt -- qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) https://bugs.launchpad.net/bugs/644961 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
