WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] USB printer not working in a Linux domU

To: Patrick Scharrenberg <pittipatti@xxxxxx>
Subject: Re: [Xen-users] USB printer not working in a Linux domU
From: Craig Metz <cmetz@xxxxxxxxx>
Date: Mon, 26 Mar 2007 14:38:51 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Comments: In-reply-to Patrick Scharrenberg <pittipatti@xxxxxx> message dated "Mon, 26 Mar 2007 18:56:00 +0200."
Delivery-date: Tue, 27 Mar 2007 01:24:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4607FB20.2020309@xxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20070324024716.EFF19582C@xxxxxxxxxxxxxxx> <4607FB20.2020309@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
In message <4607FB20.2020309@xxxxxx>, you write:
>Hi
>>   I am trying to get a USB printer to work in a Linux domU. 
>I got the same error and am discussing this in xen-devel.
>
>Right now there's a workaround:
>in "drivers/usb/class/usblp.c" lower the value of "USBLP_BUF_SIZE" from 
>8192 to 4096, remove the .o-files and rebuild.
>This should work.

  Thanks - I found the same work-around myself doing some debugging.

  Why is Xen unable to correctly do the order=1 allocation behind this code
path?

  I also tried a USB scanner (sane-backends w/libusb) in this domU. When you
try to actually scan, it throws up a DMA error and kernel oops. Much more
seriously broken than the print problem.

  It looks to me like there are some real Xen problems behind these two, and
the Xen developers could improve the code's quality by debugging these cases.

  I tried to file a bug report with XenSource, but their new account sign-up
never got back to me.

                                                                        -Craig

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>