From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Scharrenberg Subject: Re: out of dma-memory when using usblp-module in driverdomain Date: Tue, 10 Apr 2007 17:01:00 +0200 Message-ID: <461BA6AC.2090107@web.de> References: <46068738.1000802@web.de> <4607910A.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------080804060703020003020501" Return-path: In-Reply-To: <4607910A.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --------------080804060703020003020501 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Jan! I'm sorry for not replying for such a long time after asking questions. :-) >> I figured out, that reducing USBLP_BUF_SIZE (usb/class/usblp.c) form >> 8192 to some smaller value, e.g. 4096 it works fine, but that's just a >> workaround. >> >> USBLP_BUF_SIZE is used to "usb_buffer_alloc" (usb/core/usb.c) dma memory: >> >> >From usb.c: >> usb_buffer_alloc - allocate dma-consistent buffer for >> URB_NO_xxx_DMA_MAP >> >> but here I'm out.. >> > > Probably you're just suffering from domains without any I/O memory ranges > assigned not being permitted to have multi-page contiguous memory ranges > assigned? I added the usb-controllers as quirky devices, like xen told me to do: (usb (pci_ids ('1106:3038') ) (pci_config_space_fields ('000000c0:2:00000000' '000000f0:2:00000000' '000000f8:2:00000000' '00000084:2:00000000') ) ) > If not, do you force swiotlb on in the domain? And what resources > does the USB HC require? > Honestly I have no clue if I'm forcing it! In the kernel-config I have "CONFIG_SWIOTLB=y" Please see attaches "lspci" for resource-view (or is there a better way, to see more information?) I'm just using usb-controllers 0., 0.1 and 0.3 because 0.2 shares its irq with another device and is not working in domU. I hope we can isolate the problem a bit more now. Please contact me for more information. (I'm now online again and can answer much faster! :-) ) Thanks Patrick --------------080804060703020003020501 Content-Type: text/plain; name="lspci.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="lspci.txt" lspci -vvvn 00:10.0 0c03: 1106:3038 (rev a0) (prog-if 00 [UHCI]) Subsystem: 1462:7253 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR-