qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: thierry bultel <1056668@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1056668] Re: qemu-system-arm crash at startup with -usbdevice
Date: Thu, 27 Sep 2012 09:34:31 -0000	[thread overview]
Message-ID: <50641DA7.9050200@wanadoo.fr> (raw)
In-Reply-To: 20120927084723.31310.41369.malone@gac.canonical.com

Le 27/09/2012 10:47, Peter Maydell a écrit :
> Well, it's certainly a bug that we crash (and I'll look into that).
> However, the vexpress-a9 model does not have any USB controller, so a
> fix for this bug would just make us print a nicer error message instead
> of crashing...
>
Yes indeed, is there supported a9 board with a USB controller ? I would 
make the test as well
Many thanks
Thierry

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1056668

Title:
  qemu-system-arm crash at startup with -usbdevice

Status in QEMU:
  New

Bug description:
  This happens with official 1.2.0 version, but I reproduce the same
  issue with the main git branch

  On my host:
  :~$ lsusb | grep Logi
  Bus 004 Device 002: ID 046d:c219 Logitech, Inc. Cordless RumblePad 2

  :~$ qemu/arm-softmmu/qemu-system-arm
  -kernel output/images/uImage -initrd output/images/rootfs.cpio -M vexpress-a9 -serial stdio -append "console=ttyAMA0" -net nic -net tap,script=$SCRIPTS/qemu-ifup,downscript=$SCRIPTS/qemu-ifdown -m 1024 -usbdevice host:046d:c219

  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1056668/+subscriptions

  reply	other threads:[~2012-09-27  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  7:49 [Qemu-devel] [Bug 1056668] [NEW] qemu-system-arm crash at startup with -usbdevice thierry bultel
2012-09-27  8:47 ` [Qemu-devel] [Bug 1056668] " Peter Maydell
2012-09-27  9:34   ` thierry bultel [this message]
2012-09-27 10:32 ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50641DA7.9050200@wanadoo.fr \
    --to=1056668@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).