Il giorno 27/mag/08, alle ore 16:52, Gerrit Kühn ha scritto:

Hi folks,

I have four identical ITX boards from Jetway here, each having two re(4)
onboard nics:

[EMAIL PROTECTED]:0:9:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec rev=0x10
hdr=0x00 vendor     = 'Realtek Semiconductor'
    device     = 'RTL8169/8110 Family Gigabit Ethernet NIC'
    class      = network
    subclass   = ethernet
[EMAIL PROTECTED]:0:11:0:        class=0x020000 card=0x10ec16f3 chip=0x816710ec
rev=0x10 hdr=0x00 vendor     = 'Realtek Semiconductor'
    device     = 'RTL8169/8110 Family Gigabit Ethernet NIC'
    class      = network
    subclass   = ethernet
[EMAIL PROTECTED]:0:15:0:    class=0x01018f card=0x31491106 chip=0x31491106
rev=0x80


I run FreeBSD 7-stable from early March 08 on three of these
machines and noticed no problems with networking with that so far.
Some days ago I installed a fourth machine with 7-stable from early May
(and some days later -because of the problems described below- to May
17th). With this new machine I see several networking problems. The most
prominent are these two:

- heavy networking traffic (in this case backup via tar & NFS) causes hangs
for about 10s-30s and sometimes also leads to watchdog timeouts:
May 27 09:04:07 protoserve kernel: re0: watchdog timeout
May 27 09:04:07 protoserve kernel: re0: link state changed to DOWN
May 27 09:04:10 protoserve kernel: re0: link state changed to UP

- copying large files (more than some 100MB) via ssh/scp drops the
connection due to "corrupted MAC on input":
Disconnecting: Corrupted MAC on input.
lost connection

I had the same problem.
I fixed it (for now) making a buildworld with
*default date=2008.03.01.00.00.00 in my src csup configuration.

I'm not so skilled to investigate in the sources but the problem is after this date.

Regards
  Daniele Bastianini_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to