[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] swiotlb settings in domU config


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ben Holt" <beanjammin@xxxxxxxxx>
  • Date: Thu, 27 Sep 2007 00:22:11 -0700
  • Delivery-date: Thu, 27 Sep 2007 00:22:57 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hfKUCI6i1qYIuZaqgBQNls5LlL5h+QCeL7mTOu4AwPM3fv0PNhCvCnwh8xVIhDyIjXVd1SKEeWxt8XSCf8tp4Iqr4J0gscBVSpTFbblLkb5TQdPa89+222U4kZEcYSPacAYKKd24FNGWaND3AEv1kbexdQ2FD2l7DShe1jiv7/o=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

While trying to trouble-shoot an issue with ivtv in a domU I have been
attempting to force an swiotlb setting with 'extra="swiotlb=64,force"'
in the domU config.  I have found that any swiotlb sizes (I have tried
from 32-512MB) cause a kernel panic (see below).  Should I be using
another method to set the swiotlb for a domU?

My specifics:
- dom0 - stock debian etch, 2.6.18-5-xen-686, xen-hypervisor 3.0.3-1
- domU - stock debian etch, same kernel as dom0

- Ben



Started domain mythtv
Linux version 2.6.18-5-xen-686 (Debian 2.6.18.dfsg.1-13etch2)
(dannf@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Thu Aug 30 06:00:04 UTC 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000040800000 (usable)
304MB HIGHMEM available.
727MB LOWMEM available.
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 264192
Kernel command line:  root=/dev/sda4 ro swiotlb=64,force
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 1913.180 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
------------[ cut here ]------------
kernel BUG at lib/../arch/i386/kernel/swiotlb.c:162!
invalid opcode: 0000 [#1]
SMP
Modules linked in:
CPU:    0
EIP:    e019:[<c01bec75>]    Not tainted VLI
EFLAGS: 00010282   (2.6.18-5-xen-686 #1)
EIP is at swiotlb_init_with_default_size+0x88/0x14e
eax: fffffff4   ebx: 00000000   ecx: f55f6000   edx: c031e000
esi: c0347404   edi: 04000000   ebp: c031ffc0   esp: c031ffb4
ds: e021   es: e021   ss: e021
Process swapper (pid: 0, ti=c031e000 task=c02cf660 task.ti=c031e000)
Stack: c197a000 c0347404 c0ee7b07 00000020 c032d57c 0000000e 00000002 c197a000
       c0347404 c1974364 00000020 c032357f 00008000 c034b280 00000000 c0fe0000
       00000000 00000000 c010006f
Call Trace:
 [<c032d57c>] mem_init+0x58/0x392
 [<c032357f>] start_kernel+0x1fb/0x37f
Code: 44 be f5 ff 83 c8 ff 40 83 f8 06 75 fa 89 d8 b9 1f 00 00 00 c1
e0 0b ba 06 00 00 00 03 05 14 45 37 c0 e8 c2 4d f5 ff 85 c0 74 08 <0f>
0b a2 00 fc 76 2a c0 83 eb 80 a1 18 45 37 c0 39 c3 72 c5 b9
EIP: [<c01bec75>] swiotlb_init_with_default_size+0x88/0x14e SS:ESP e021:c031ffb4
 <0>Kernel panic - not syncing: Attempted to kill the idle task!

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.