In article <42b497160611151637o6fd608aex1156c6065f4dbd72@mail.gmail.com>,
Kimi Ostro <kimimeister@gmail.com> wrote:
>Hi,
>
>recently I posted this to port-xen thinking it might have been a Xen
>issue, but it seems to be more down to hardware issues. Manuel Bouyer
>said I might have more luck on this list.
>
>I keep getting:
>fxp0: device timeout
>
>Now, I have tried various kernel configs, even read fxp man page as
>per Steven M. Bellovin suggestion to no avail.
>
>At first I thought the fxp was dead, but seems I was wrong and
>dhclient works for a bit, I can also sit there with tcpdump watching
>packets flowing, but most of the time the device is just "dead"
>transmitting packets. I even I bridged it for my Xen DomUs, which is
>my goal.
>
>Yet it works fine under Windows XP. I have not tried other OS's yet.
>
>here is a dmesg:

>fxp0 at pci0 dev 10 function 0: i82550 Ethernet, rev 13
>fxp0: interrupting at ioapic0 pin 16, event channel 3
>fxp0: Ethernet address 00:02:b3:b4:e1:9d
>inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
>inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

I have this one, and it does not work when set to "auto", only
works when setting the media manually.

fxp0 at pci2 dev 6 function 0: i82550 Ethernet, rev 12
fxp0: interrupting at ioapic0 pin 17 (irq 10)
fxp0: Ethernet address 00:02:b3:64:55:44
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

christos