From: Erik Rull <erik.rull@rdsoftware.de>
To: Jim Paris <jim@jtan.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Windows XP Bluescreen when unplugging printer
Date: Wed, 18 Nov 2009 23:02:59 +0100 [thread overview]
Message-ID: <4B046F13.1090507@rdsoftware.de> (raw)
In-Reply-To: <20091118214835.GA6288@psychosis.jim.sh>
Jim Paris wrote:
> Erik Rull wrote:
>> Hi Jim,
>>
>> sorry, still a bluescreen - but another one :-)
>> BUGCODE_USBDRIVER is its name.
>>
>> Any other ideas? With USB 1.1 on the host everything is fine, after
>> enabling USB 2.0 in BIOS on the host, USB is faster within the guest, but
>> I have the given Bluescreen problem.
>>
>> Best regards,
>
> No ideas, sorry. It might be a Windows driver problem triggered by
> qemu timing differences (try reinstalling the printer drivers?) You
> might also try enabling DEBUG in usb-linux.c and compare the output
> you get there with a usbmon capture on the host, and a usbsnoopy
> capture on the guest, to see if there are any discrepencies. Not sure
> what kind of thing you'd be looking for, though.
>
> -jim
Hm, what I forgot to say: Now the bluescreen comes up directly after trying
to print, before it only appeared on unplugging or shutdown. And: It seems
to be a USB 2.0 issue. When I plug in a USB 1.1 printer everything is fine??
Can you recommend a usb sniffer tool? Hope this helps when getting a
bluescreen :-)
Best regards,
Erik
next prev parent reply other threads:[~2009-11-18 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 22:57 Windows XP Bluescreen when unplugging printer Erik Rull
2009-11-16 23:18 ` Jim Paris
2009-11-17 17:58 ` Erik Rull
2009-11-18 21:40 ` Erik Rull
2009-11-18 21:48 ` Jim Paris
2009-11-18 22:02 ` Erik Rull [this message]
2009-11-18 22:14 ` Jim Paris
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=4B046F13.1090507@rdsoftware.de \
--to=erik.rull@rdsoftware.de \
--cc=jim@jtan.com \
--cc=kvm@vger.kernel.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