just tried swiotlb=16,force with the same kernel panic :(

I wonder what happened, i am sure i have seen mention of people  
running ivtv in domU's on the web.

thanks,
-guil

Quoting Ian Campbell <[EMAIL PROTECTED]>:

> On Tue, 2007-05-01 at 13:01 -0500, Guil Barros wrote:
>> I tried, below are my results:
>
> I'm afraid that's all my suggestions. You could try swiotlb=16,force
> just for kicks (google seems to suggest that is the most common value)
> but I bet the result is the same as below.
>
> It may be that the ivtv driver needs updating to work in a domU :-(
>
> Ian.
>
>> ====swiotlb=32,force====
>> [EMAIL PROTECTED] ~]# xm create -c slurp
>> Using config file "/etc/xen/slurp".
>> Going to boot Fedora Core (2.6.20-1.2944.fc6xen)
>>    kernel: /vmlinuz-2.6.20-1.2944.fc6xen
>>    initrd: /initrd-2.6.20-1.2944.fc6xen.img
>> Started domain slurp
>> Linux version 2.6.20-1.2944.fc6xen
>> ([EMAIL PROTECTED]) (gcc version 4.1.1 20070105
>> (Red Hat 4.1.1-51)) #1 SMP Tue Apr 10 19:12:19 EDT 2007
>> BIOS-provided physical RAM map:
>> sanitize start
>> sanitize bail 0
>> copy_e820_map() start: 0000000000000000 size: 0000000030800000 end:
>> 0000000030800000 type: 1
>>   Xen: 0000000000000000 - 0000000030800000 (usable)
>> 48MB HIGHMEM available.
>> 727MB LOWMEM available.
>> NX (Execute Disable) protection: active
>> Zone PFN ranges:
>>    DMA             0 ->   186366
>>    Normal     186366 ->   186366
>>    HighMem    186366 ->   198656
>> early_node_map[1] active PFN ranges
>>      0:        0 ->   198656
>> ACPI in unprivileged domain disabled
>> Built 1 zonelists.  Total pages: 197105
>> Kernel command line:  ro root=/dev/VolGroup00/lv00_root console=xvc0
>> selinux=0 swiotlb=32,force
>> Enabling fast FPU save and restore... done.
>> Enabling unmasked SIMD FPU exception support... done.
>> Initializing CPU#0
>> CPU 0 irqstacks, hard=c0784000 soft=c0764000
>> PID hash table entries: 4096 (order: 12, 16384 bytes)
>> Xen reported: 2394.000 MHz processor.
>> Console: colour dummy device 80x25
>> 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:160!
>> invalid opcode: 0000 [#1]
>> SMP
>> last sysfs file:
>> Modules linked in:
>> CPU:    0
>> EIP:    e019:[<c04e5848>]    Not tainted VLI
>> EFLAGS: 00010282   (2.6.20-1.2944.fc6xen #1)
>> EIP is at swiotlb_init_with_default_size+0x8a/0x153
>> eax: fffffff4   ebx: 00000300   ecx: 00000040   edx: f5416000
>> esi: c075fae4   edi: 02000000   ebp: 00000020   esp: c0730f44
>> ds: e021   es: e021   ss: e021
>> Process swapper (pid: 0, ti=c0730000 task=c06e3280 task.ti=c0730000)
>> Stack: c074173e 00000000 ffffffff c161f000 c161f000 c075fae4   
>> c0231b07 c073e778
>>         00000042 00000004 c0730f88 00010000 c16a6200 00000004   
>> 00000010 c0742676
>>         c069b0b1 c069c864 00010000 00000006 00040000 00c07c40   
>> 00000000 0301f100
>> Call Trace:
>>   [<c074173e>] __alloc_bootmem_low+0x2b/0x67
>>   [<c073e778>] mem_init+0x54/0x4d6
>>   [<c0742676>] alloc_large_system_hash+0x18d/0x1b4
>>   [<c0743153>] inode_init_early+0x49/0x72
>>   [<c0734686>] start_kernel+0x22a/0x3c3
>>   [<c073425a>] unknown_bootoption+0x0/0x202
>>   =======================
>> Code: 59 7a f3 ff 83 c8 ff 40 83 f8 06 75 fa 89 d8 b9 1e 00 00 00 c1
>> e0 0b ba 06 00 00 00 03 05 54 65 7e c0 e8 2a 02 f3 ff 85 c0 74 04 <0f>
>> 0b eb fe 83 eb 80 a1 58 65 7e c0 39 c3 72 c9 b9 00 00 00 01
>> EIP: [<c04e5848>] swiotlb_init_with_default_size+0x8a/0x153 SS:ESP
>> e021:c0730f44
>>   <0>Kernel panic - not syncing: Attempted to kill the idle task!
>
> --
> Ian Campbell
>
> petribar:
>       Any sun-bleached prehistoric candy that has been sitting in
>       the window of a vending machine too long.
>               -- Rich Hall, "Sniglets"
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>





_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to