Windows XP Bluescreen when unplugging printer

Windows XP Bluescreen when unplugging printer

[Erik Rull]

Hi all,

I want to run an epson inkjet within my windows xp guest. my host has 
enabled usb 2.0, the USB flashdrive works without any problems. When I plug 
in the printer (works with the same drivers on a native windows xp!), it is 
recognized and the status monitor shows also the ink levels. Until I start 
printing. Then the ink level disappears and the status monitor hangs. The 
printer itself doesn't do anything, no LED blinks, no printing starts. When 
I shut down windows or unplug the printer I get a bluescreen in XP on 
usbuhci.sys

Interesting: When I switch off USB 2.0 and enable only USB 1.x in the host 
BIOS, everything related to USB is SLOW (usb flash drive, too!) but the 
printer works (also slow, but it prints).

Any ideas what could cause that behaviour? Comes up with kvm-88 and kvm-77 
as well.

I tested it on two different systems both the same behaviour.

Best regards,

Erik

Re: Windows XP Bluescreen when unplugging printer

[Jim Paris]

Erik Rull wrote:
> Hi all,
>
> I want to run an epson inkjet within my windows xp guest. my host has  
> enabled usb 2.0, the USB flashdrive works without any problems. When I 
> plug in the printer (works with the same drivers on a native windows 
> xp!), it is recognized and the status monitor shows also the ink levels. 
> Until I start printing. Then the ink level disappears and the status 
> monitor hangs. The printer itself doesn't do anything, no LED blinks, no 
> printing starts. When I shut down windows or unplug the printer I get a 
> bluescreen in XP on usbuhci.sys
>
> Interesting: When I switch off USB 2.0 and enable only USB 1.x in the 
> host BIOS, everything related to USB is SLOW (usb flash drive, too!) but 
> the printer works (also slow, but it prints).
>
> Any ideas what could cause that behaviour? Comes up with kvm-88 and 
> kvm-77 as well.
>
> I tested it on two different systems both the same behaviour.

You might try this usb fix:
  http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=c4c0e236beabb9de5ff472f77aeb811ec5484615

It's been around for a while but hasn't made it into any qemu or kvm
releases yet.

-jim

Re: Windows XP Bluescreen when unplugging printer

[Erik Rull]

Jim Paris wrote:
> Erik Rull wrote:
>> Hi all,
>>
>> I want to run an epson inkjet within my windows xp guest. my host has  
>> enabled usb 2.0, the USB flashdrive works without any problems. When I 
>> plug in the printer (works with the same drivers on a native windows 
>> xp!), it is recognized and the status monitor shows also the ink levels. 
>> Until I start printing. Then the ink level disappears and the status 
>> monitor hangs. The printer itself doesn't do anything, no LED blinks, no 
>> printing starts. When I shut down windows or unplug the printer I get a 
>> bluescreen in XP on usbuhci.sys
>>
>> Interesting: When I switch off USB 2.0 and enable only USB 1.x in the 
>> host BIOS, everything related to USB is SLOW (usb flash drive, too!) but 
>> the printer works (also slow, but it prints).
>>
>> Any ideas what could cause that behaviour? Comes up with kvm-88 and 
>> kvm-77 as well.
>>
>> I tested it on two different systems both the same behaviour.
> 
> You might try this usb fix:
>   http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=c4c0e236beabb9de5ff472f77aeb811ec5484615
> 
> It's been around for a while but hasn't made it into any qemu or kvm
> releases yet.
> 
> -jim
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi Jim,

thanks - I will try that tomorrow.

- Erik

Re: Windows XP Bluescreen when unplugging printer

[Erik Rull]

Jim Paris wrote:
> Erik Rull wrote:
>> Hi all,
>>
>> I want to run an epson inkjet within my windows xp guest. my host has  
>> enabled usb 2.0, the USB flashdrive works without any problems. When I 
>> plug in the printer (works with the same drivers on a native windows 
>> xp!), it is recognized and the status monitor shows also the ink levels. 
>> Until I start printing. Then the ink level disappears and the status 
>> monitor hangs. The printer itself doesn't do anything, no LED blinks, no 
>> printing starts. When I shut down windows or unplug the printer I get a 
>> bluescreen in XP on usbuhci.sys
>>
>> Interesting: When I switch off USB 2.0 and enable only USB 1.x in the 
>> host BIOS, everything related to USB is SLOW (usb flash drive, too!) but 
>> the printer works (also slow, but it prints).
>>
>> Any ideas what could cause that behaviour? Comes up with kvm-88 and 
>> kvm-77 as well.
>>
>> I tested it on two different systems both the same behaviour.
> 
> You might try this usb fix:
>   http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=c4c0e236beabb9de5ff472f77aeb811ec5484615
> 
> It's been around for a while but hasn't made it into any qemu or kvm
> releases yet.
> 
> -jim
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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,

Erik

Re: Windows XP Bluescreen when unplugging printer

[Jim Paris]

Erik Rull wrote:
> Jim Paris wrote:
>> Erik Rull wrote:
>>> Hi all,
>>>
>>> I want to run an epson inkjet within my windows xp guest. my host has 
>>>  enabled usb 2.0, the USB flashdrive works without any problems. When 
>>> I plug in the printer (works with the same drivers on a native 
>>> windows xp!), it is recognized and the status monitor shows also the 
>>> ink levels. Until I start printing. Then the ink level disappears and 
>>> the status monitor hangs. The printer itself doesn't do anything, no 
>>> LED blinks, no printing starts. When I shut down windows or unplug 
>>> the printer I get a bluescreen in XP on usbuhci.sys
>>>
>>> Interesting: When I switch off USB 2.0 and enable only USB 1.x in the 
>>> host BIOS, everything related to USB is SLOW (usb flash drive, too!) 
>>> but the printer works (also slow, but it prints).
>>>
>>> Any ideas what could cause that behaviour? Comes up with kvm-88 and  
>>> kvm-77 as well.
>>>
>>> I tested it on two different systems both the same behaviour.
>>
>> You might try this usb fix:
>>   http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=c4c0e236beabb9de5ff472f77aeb811ec5484615
>>
>> It's been around for a while but hasn't made it into any qemu or kvm
>> releases yet.
>>
>> -jim
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> 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

Re: Windows XP Bluescreen when unplugging printer

[Erik Rull]

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

Re: Windows XP Bluescreen when unplugging printer

[Jim Paris]

Erik Rull wrote:
> 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 :-)

usbmon (e.g. with wireshark) on the Linux host should work.  usbsnoopy
is a tool you can use on the Windows guest side.  Of course, if the
guest OS is crashing it's going to be hard to get any useful data out
of that after the crash.

-jim