From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lukas Hejtmanek Subject: Re: SWIOTLB allocation failed Date: Tue, 4 Dec 2007 15:26:43 +0100 Message-ID: <20071204142643.GC8704@ics.muni.cz> References: <20071127135301.GI4296@ics.muni.cz> <6bc632150711270603k1c22533dof7574acb0fb83b8f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <6bc632150711270603k1c22533dof7574acb0fb83b8f@mail.gmail.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: pradeep singh rautela Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Nov 27, 2007 at 07:33:40PM +0530, pradeep singh rautela wrote: > Did you try using swiotlb=3DXYZ to solve your problem? XYZ is the amoun= t > of the memory for swiotlb. > Did you get the same crash? I noticed that using swiotlb=3D30000000 probably does not work at all as = I got the following: [ 189.436069] Kernel command line: root=3D/dev/sda1 ro ip=3D147.251.11.44:1.2.3.4:147.251.11.1:255.255.255.128:skirit60-1:eth0:o= ff magrathea=3Deth1:10.0.0.1:10.0.0.101: swiotlb=3D30000000 xencons=3Dtty [ 189.436416] Initializing CPU#0 [ 189.436656] PID hash table entries: 4096 (order: 12, 32768 bytes) [ 189.436695] Xen reported: 2992.498 MHz processor. [ 189.436721] Console: colour dummy device 80x25 [ 189.438468] Dentry cache hash table entries: 524288 (order: 10, 419430= 4 bytes) [ 189.440459] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 189.440825] Software IO TLB disabled --=20 Luk=E1=B9 Hejtm=E1nek