Public bug reported:

Host: Ubuntu Precise amd64
Guest: Debian Sid (ports) sh4

While running a debootstrap for a Debian Sid sh4 guest, the process
stops when attempting to run the second stage with a Segmentation Fault.

# qemu-debootstrap --no-check-gpg --arch=sh4 sid sh4 
http://ftp.debian-ports.org/debian
I: Running command: debootstrap --arch sh4 --foreign --no-check-gpg sid sh4 
http://ftp.debian-ports.org/debian
[...]
I: Running command: chroot sh4 /debootstrap/debootstrap --second-stage
Segmentation fault (core dumped)

Running "chroot sh4" starts a shell and running a command that requires
a fork successfully completes but then the whole thing stops responding
and has to be kill -9ed.

The exact same process on Precise i386 works fine (it fails much later
on but is probably unrelated).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-user-static 1.0.50-2012.03-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon Nov 25 17:31:36 2013
Dependencies:
 
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: qemu-linaro
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu-linaro (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254824

Title:
  qemu-sh4-static: segmentation fault during debootstrap second stage on
  amd64 but not i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/1254824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to