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

Re: [Xen-devel] Xen + DVB = not working. memory allocation issue?



Hi Konrad,


> >> Apologies if this has been asked before (I wasn't able to find another
> >> patch), but is there a patch to get this (suspected vmalloc_32) fixed
> >> and DVB card working?
> >

It would appear some recent-ish patches to the linux kernel has caused this issue for me; while it did work on 3.2.

I don't think I am the only person in this situation.

> >> I have a winfast DVT 2000H (cx88) DVB card which is not able to
> >> scan/watch digital TV when running under Xen.


Could you post some patches you may think could help (which I can test) / recommendations on using different kernel version, etc?

I'm not too sure what else to try / test at my end here....

FYI Xen 4.3-unstable with linux 3.6.4 (-pf patches applied) for Dom0.

Thank you again for your input! :)

Regards,

John

On 12 October 2012 15:43, John Krstev <john.krstev@xxxxxxxxx> wrote:
Hi Konrad,

I have done some more testing and like to share my findings:


> > Did you first try running it under baremetal Linux (using a Live CD for
> > example?) Did it work there?
I have found that under kernel version 3.2.0 (stock debian kernel) when running on baremetal I get data, with or without kernel parameter "intel_iommu=1"  'cat /dev/video > /tmp/file' produces data there too. However when booting this kernel under Xen (Dom0) cannot get DVB data and get filter timeout with scan utility.

With (custom built vanilla) kernel 3.6 and custom built 3.5 (with -pf patches), when running on baremetal; with intel_iommu=1 I am unable to get any DVB data. I have tried intel_iommu=0 and I still cannot get DVB data. To add to this I now have DMAR messages in dmesg output (06:00.0 is the DVB card) :

[    0.074639] DMAR:[DMA Read] Request device [06:00.0] fault addr 80c6000
[    0.074639] DMAR:[fault reason 02] Present bit in context entry is clear
[    0.422177] DMAR: No ATSR found
[   49.194033] DMAR:[DMA Read] Request device [06:00.0] fault addr fff7f000
[   49.194033] DMAR:[fault reason 02] Present bit in context entry is clear

Also, I'm getting these (with intel_iommu=0 or with intel_iommu=1) under 3.5-pf kernel and 3.6 custom vanilla:

[    0.418811] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[    0.419294]  [<ffffffff81250d01>] ? intel_iommu_device_group+0x64/0xb1
[    0.419330]  [<ffffffff8124c9b0>] ? bus_set_iommu+0x37/0x37
[    0.419364]  [<ffffffff8124c9c2>] ? add_iommu_group+0x12/0x2f
[    0.419399]  [<ffffffff8124c9b0>] ? bus_set_iommu+0x37/0x37
[    0.420778]  [<ffffffff8124c9ac>] ? bus_set_iommu+0x33/0x37
[    0.420813]  [<ffffffff814c39c0>] ? intel_iommu_init+0x9a9/0xac5
[    0.420920]  [<ffffffff8149c7df>] ? pci_iommu_init+0xe/0x37


Now; I did manage to get it it work WITH Xen under the following conditions:

Debian kernel 3.2.0 and Xen (Dom0) and passing "iommu=0" on the xen line.

FYI I'd like to mention that I have had success doing VGA passthrough to Win XP guest (Intel on board graphics) so I'm reasonably confident the BIOS IOMMU code is OK (Asrock Z77 Extreme 4 motherboard - BIOS version 1.30).

What are your thoughts?

Regards,

John



On 26 September 2012 11:02, John Krstev <john.krstev@xxxxxxxxx> wrote:
Hey Konrad,

>Please do not top-post.
Apologies.


>So try also limiting how much memory the hypervisor has to eliminate
>this being a 4GB issue. Meaning on the _hypervisor_ line add 'mem=4G'.

Yes, that was on the hypervisor line which I was specifying mem=3G. I've also tried mem=4G and still having the same problem.


>And I need to know whether you are running this in a domain or in the initial domain?

Running in Dom0.


>If you do it manually (cat /dev/video0 > /tmp/file.mpg)
>does the file increase? Is it full of garbage ?

cat: /dev/video0: Input/output error

The file size is 0 bytes.


>Does the channel selection work? Can you select the proper channel?
Analogue selection works ok and I can also watch analogue TV. When using digital, I get a lock but no video data.


> If you crank up all the debug options do you get anything saying what the problem is

With debug turned on to level 8 (echo 8 > /proc/sys/kernel/printk) I see the following in dmesg which may be useful:
[130009.484098] cx88[0]/0: [ffff8802c03b3400/0] timeout - dma=0x96a7e000

Let me know if there's anything else I can try?

Regards,

John


On 26 September 2012 00:10, Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx> wrote:
On Tue, Sep 25, 2012 at 10:49:38AM +1000, John Krstev wrote:
> Hello Konrad,

Hey John,

Please do not top-post.
>
> Do you have any patches I can try? FYI I've tried booting dom0 with mem=3G and various other options, still does not work. As I mentioned it runs fine on bare metal.

So try also limiting how much memory the hypervisor has to eliminate
this being a 4GB issue. Meaning on the _hypervisor_ line add 'mem=4G'.

The next step is to actually figure out if where in the driver (cx88)
fails. And I need to know whether you are running this in a domain or
in the initial domain? If you crank up all the debug options do you
get anything saying what the problem is? How do you 'capture' the
video output? If you do it manually (cat /dev/video0 > /tmp/file.mpg)
does the file increase? Is it full of garbage ?

Does the channel selection work? Can you select the proper channel?

>
> Last time it did work with xen was Jeremy's kernel + xen 4.0, also kernel 3.0.8 with xen 4.0.4 i believe (cannot reproduce success).
>
> Thank you again for your input.
>
> Regards,
>
> John
>
>
>
> On 22/09/2012, at 3:29, Konrad Rzeszutek Wilk <konrad@xxxxxxxxxx> wrote:
>
> > On Fri, Sep 21, 2012 at 01:02:23PM +1000, John Krstev wrote:
> >> Hi Konrad,
> >
> > Hey John,
> >
> > Please next time also include xen-devel on the To header. I've done that
> > for you.
> >>
> >> I refer to your patch at:
> >> http://lists.xen.org/archives/html/xen-devel/2012-01/msg01927.html
> >> which I found reading
> >> http://www.gossamer-threads.com/lists/xen/devel/256197
> >>
> >> I have a winfast DVT 2000H (cx88) DVB card which is not able to
> >> scan/watch digital TV when running under Xen.
> >
> > Did you first try running it under baremetal Linux (using a Live CD for
> > example?) Did it work there?
> >
> > How does it not work? Can you program it? Is this under a guest or the
> > main kernel? When it wsa not working, did you try all the debug
> > options enable (http://wiki.xen.org/wiki/XenSerialConsole) to
> > see if there is anthing being reported?
> >
> >>
> >> I've tried installing the above patch to the 3.6-rc6 kernel, but did
> >> not seem to help.
> >>
> >> Apologies if this has been asked before (I wasn't able to find another
> >> patch), but is there a patch to get this (suspected vmalloc_32) fixed
> >> and DVB card working?
> >
> > Eventually yes.
> >>
> >> FYI I'm running 64 bit 3.5-rc6 and xen 4.3-unstable.
> >
> > 3.5-rc6 or 3.6-rc6?
> > I presume the latter?
> >>
> >> Thank you! :)
> >>
> >> Regards,
> >>
> >> John
> >>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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