Re: [Xen-devel] xen 2.0 testing / DMA failure with ivtv-driver

["Manuel Bernhardt" <mailinglist@xxxxxxxxxxx>]

Hi Keir,

thank you for your response. Is there a chance, that this errors are
lapsed with xen 3.0? My first try was xen 3.0, but with it, everytime when
i started the xend daemon, the network interface are no longer available
to the network (ifconfig shows me all available interface but ping can't
contact himself or any other host in my network). I can reproduce this
problem on 2 pc's. If you can tell me, how i can solve this problem, i
would try xen 3.0 with my "hardware carousel" and would deliver
bug-reports for this version.

For xen 2.0 i could it maybe made possible, give an trustable person
(developer) remote access to my maschine for collecting more informations
for debugging and bugfixing. If it's an passable to contribute, i would do
this.

Manuel

>
> On 6 Oct 2005, at 09:34, Manuel Bernhardt wrote:
>
>> ok, maybe someone notice my posts ...
>> I deferred the problem with the ivtv-driver and try get fritz!card dsl
>> driver working... and surprise, the next kernel error. Can i do some
>> much wrong with xen or is there maybe an "real" chance that i'm not a
>> fool ?
>
> These kinds of problem are quite hard to debug without having direct
> access to hardware. I got lucky last time round and eyeballed a problem
> in our dma-mapping functions. :-)
>
> You may have to wait for other 3.0-related issues to settle down a bit
> before any core developers have time to look at the problem and suggest
> extra debugging to add....
>
>   -- Keir
>



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