qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik Rull <erik.rull@rdsoftware.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu assertion failed with usb on current git master!
Date: Tue, 28 Feb 2012 14:38:53 +0100 (CET)	[thread overview]
Message-ID: <637752100.510344.1330436333566.JavaMail.open-xchange@email.1und1.de> (raw)
In-Reply-To: <4F4BB4FE.8070800@rdsoftware.de>

[-- Attachment #1: Type: text/plain, Size: 2082 bytes --]




On February 27, 2012 at 5:53 PM Erik Rull <erik.rull@rdsoftware.de> wrote:

> Gerd Hoffmann wrote:
> >    Hi,
> >
> >> I'm really sorry, but I don't understand what's happening - I copied
the
> >> qemu executable on my target system before executing it, but gdb
complains
> >> that the core file does not match the executable! But except the file
paths
> >> they are identical.
> >
> >> warning: core file may not match specified executable file.
> >> Core was generated by `/disc/qemu-system-x86_64 -machine
kernel_irqchip=on
> >> -serial /dev/ttyS2 -usb -de'.
> >> Program terminated with signal 6, Aborted.
> >> #0  0xffffe424 in __kernel_vsyscall ()
> >
> > Strange.  The backtrace is bogus too.
> >
> >> I don't know how to proceed here.
> >
> > Lets try plan b: add a printf right before the assert:
> >
> > --- a/hw/usb.c
> > +++ b/hw/usb.c
> > @@ -356,6 +356,7 @@ void usb_packet_complete(USBDevice *dev, USBPacket
*p)
> >
> >       while (!QTAILQ_EMPTY(&ep->queue)) {
> >           p = QTAILQ_FIRST(&ep->queue);
> > +        fprintf(stderr, "%s: packet %p\n", __func__, p);
> >           assert(p->state == USB_PACKET_QUEUED);
> >           ret = usb_process_one(p);
> >           if (ret == USB_RET_ASYNC) {
> >
> >
> >> Don't you run into this problem (crash on USB plug in) on your system?
> >> I tested it with a Linux guest, there it does not crash! Only with a
> >> Windows XP guest!
> >
> > I test with Linux most of the time, but even with windows xp guest it
> > doesn't reproduce here.
> >
> > cheers,
> >    Gerd
> >
>
> That's a good idea - will test that tomorrow and send the new result
file.
> Have you ever tested a USB CD or DVD drive attached to your guests? I
have
> issues with Windows XP (I get everything running and detected beside the
> drive letter in Windows Explorer) but it works fine for Linux.
>
> Best regards,
>
> Erik
>


Find attached the usb.txt => I gzip'ed it to reduce the transfer size.
I added the p->state to the fprintf, maybe this helps.
fprintf(stderr, "%s: packet: %p %d\n", __func__, p,p?p->state:-1);

Best regards,

Erik


[-- Attachment #2: usb.txt.gz --]
[-- Type: application/x-gzip, Size: 11195 bytes --]

      reply	other threads:[~2012-02-28 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 11:38 [Qemu-devel] qemu assertion failed with usb on current git master! Erik Rull
2012-02-23 12:24 ` [Qemu-devel] git bisect results was: " Erik Rull
2012-02-23 15:12 ` [Qemu-devel] " Gerd Hoffmann
2012-02-23 18:33   ` Erik Rull
2012-02-27  9:22   ` Erik Rull
2012-02-27 12:48     ` Gerd Hoffmann
2012-02-27 14:52       ` Erik Rull
2012-02-27 15:54         ` Gerd Hoffmann
2012-02-27 16:53           ` Erik Rull
2012-02-28 13:38             ` Erik Rull [this message]

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=637752100.510344.1330436333566.JavaMail.open-xchange@email.1und1.de \
    --to=erik.rull@rdsoftware.de \
    --cc=kraxel@redhat.com \
    --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).