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

["Manuel Bernhardt" <mailinglist@xxxxxxxxxxx>]

Hi,

the first pc have an davicom 10/100 (PCI Card) nic:

0000:02:07.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet
100/10 MBit (rev 31)
        Subsystem: Unknown device 4554:434e
        Flags: bus master, medium devsel, latency 64, IRQ 16
        I/O ports at ec00 [size=fe200000]
        Memory at fe1ffc00 (32-bit, non-prefetchable) [size=256]
        Expansion ROM at 00040000 [disabled]
        Capabilities: [50] Power Management version 2

This PC runs with SuSE 9.1. The second PC have an Realtek (PCI Card) nic:

0000:00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RT8139
        Flags: bus master, medium devsel, latency 32, IRQ 18
        I/O ports at ec00 [size=256]
        Memory at df5fff00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2

and runs with gentoo. Current xen 3.0 in gentoo portage is
xen-3.0.0_pre20050929, on SuSE i tried xen 3.0 release downloaded last
friday.
In my post there was one error: I can ping the himself but not the ip's
outside of the pc. I notice only this messages after starting xend:

Oct  6 13:14:31 linux kernel: eth0: Promiscuous mode enabled.
Oct  6 13:14:31 linux kernel: device eth0 entered promiscuous mode

In some rarely cases the nic stay alive so that i can ping ip's outside
but mostly (in 9 of 10 cases) the connection failed

>
> This is interesting. Do you have more than one NIC? The scripts should
> work out of the box for systems with one nic, called eth0.
>
>   -- Keir
>



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