Many thanks for your answer!!
I tried the noirqdebug opton on both dom0 and domU but didn't help.
It's strange that i'm able to use other two cards (one of them with cx24116
frontend!) without problem.
My systems aren't hanging but domU, simply, procuces corrupted dvb streams. If
streams are mpeg encoded the image is corrupted and audio is noisy otherwise if
streams are h264 they couldn't be decoded (and frontends hangs ...)
I've noted that domU complains about 'rtc: IRQ 8 is not free'
and Dom0 complains about:
-------------------------------------------------------------
[ 1.014241]
/build/buildd/linux-2.6.24/debian/build/custom-source-xen/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[ 1.014406] Freeing unused kernel memory: 220k freed
[ 1.342867] fuse init (API version 7.9)
[ 1.122614] Unable to handle kernel paging request at ffffffff80613134 RIP:
[ 1.122754] [<ffffffff80371f93>] acpi_get_table+0x37/0x94
[ 1.123158] PGD 203067 PUD 205067 PMD 1cab067 PTE 613000
[ 1.123782] Oops: 0000 [1] SMP
[ 1.124161] CPU 1
[ 1.124416] Modules linked in: processor fuse
[ 1.124918] Pid: 1100, comm: modprobe Not tainted 2.6.24-23-xen #1
[ 1.125058] RIP: e030:[<ffffffff80371f93>] [<ffffffff80371f93>]
acpi_get_table+0x37/0x94
[ 1.125333] RSP: e02b:ffff8800204f7df8 EFLAGS: 00010297
[ 1.125471] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 1.125611] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff80613120
[ 1.125751] RBP: ffffffff8801abd0 R08: ffffffff80613120 R09: ffffffff88014d07
[ 1.125890] R10: 0000000000000007 R11: 0000000000000001 R12: ffffffff8801a500
[ 1.126031] R13: 0000000000000001 R14: ffffffff8801a500 R15: ffffc200000373e0
[ 1.126199] FS: 00007fb8fd73e6e0(0000) GS:ffffffff805c7080(0000)
knlGS:0000000000000000
[ 1.126352] CS: e033 DS: 0000 ES: 0000
[ 1.126489] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 1.126630] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 1.126770] Process modprobe (pid: 1100, threadinfo ffff8800204f6000, task
ffff88001e05c800)
[ 1.126921] Stack: 0000000000000001 ffffffff8801a500 0000000000000001
ffffffff8801c03d
[ 1.127680] 0000000000000001 ffffffff8801a500 ffffffff8801a500
ffffffff8025a46e
[ 1.128322] ffff88001df54330 ffff88001df8a160 ffffc20000036c70
ffffc20000036c68
[ 1.128827] Call Trace:
[ 1.129099] [<ffffffff8801c03d>] :processor:acpi_processor_init+0x3d/0x107
[ 1.129244] [<ffffffff8025a46e>] sys_init_module+0x18e/0x1a90
[ 1.129385] [<ffffffff80257f80>] cpu_down+0x0/0x60
[ 1.129525] [<ffffffff8020c698>] system_call+0x68/0x6d
[ 1.129665] [<ffffffff8020c630>] system_call+0x0/0x6d
[ 1.129802]
[ 1.129936]
[ 1.129937] Code: 8b 47 14 41 3b 01 75 3f 48 ff c1 48 39 f1 72 37 e8 8a 08 00
[ 1.132776] RIP [<ffffffff80371f93>] acpi_get_table+0x37/0x94
[ 1.133038] RSP <ffff8800204f7df8>
[ 1.133174] CR2: ffffffff80613134
[ 1.133311] ---[ end trace 78ad8dd956620320 ]---
---------------------------------------------------------------
Could be there the problem?
Thanks again
PS: i can try to compile the kernel ... but i' quite scared about it.
---------- Initial Header -----------
>From : xen-users-bounces@xxxxxxxxxxxxxxxxxxx
To : "xen-users" xen-users@xxxxxxxxxxxxxxxxxxx
Cc :
Date : Sun, 26 Apr 2009 17:46:16 +0100
Subject : Re: [Xen-users] Nova-s2 pci-passthrough not properly working
> 2009/4/22 ferrarir@xxxxxxxxx <ferrarir@xxxxxxxxx>:
>
> > i'm having problems passing a Hauppage Nova-S2 card to my DomU (Mythtv
> > Backend).
>
> I have similar setup, xen 3.3.1 from gitco, centOS 2.6.18 64bit dom0
> and mythTV backend in centOS 2.6.18 32bit domU, PCI passthrough of 2 x
> SAA7134 DVB-T cards, mySQL in a separate domU.
>
> > I'm able to configure and setup the Nova card inside mythtv. I can watch tv
> > but after few channel changes the picture is being corrupted and frontends,
> > that are remote, stop working.
> > I think it's a XEN ISSUE (OR AN HW ISSUE) because i tried to use that card
> > on another systems (3 other systems) but without virtualizing it and works
> > nicely.
>
> I tried various swiotlb configs but none of them helped much, I don't
> have that option on my command line anymore, what did help was the
> noirqdebug on both the dom0 and domU command lines
>
> module /vmlinuz-2.6.18-92.1.22.el5.centos.plus.jab.xen ro
> root=/dev/vgr1/vgcentos52 console=ttyS0,115200 noirqdebug
> reassign_resources reassigndev=08:00.0,08:01.0,08:03.0
>
> What also helped was building a dom0 kernel with the Yuji's PCI
> re-alignment patches applied
>
> http://markmail.org/message/sclz6hkaif4sqx4e?q=yuji+pci+reassign+patch&page=1&refer=6bzqnwn5qkmd5w3u
>
> I get a crash about once every 10-14 days, usually with a totally
> different backtrace each time, so assume it's some random corruption
> happening, while it's running I can hammer the backend heavily
> recording three concurrent streams from each tuner for 24 hours on
> end, and playing back another stream on my (hardware) myth frontend,
> but then something simple like viewing the mythweb pages or SSHing to
> the domU will kill the dom0 (occasionally it just kills the domU)
>
> I figure I have to live with that until ..
>
> 1) pvops dom0 is allowed into mainline kernel
>
> and
>
> 2) pciback/pcifront work is re-done for pvops.
>
> and make sure all my other domUs start up cleanly after a crash, and
> hope it happens at about 3am ;-)
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home