Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Aug 2015 17:07:55 +0200 (CEST)
From:      Christian Kratzer <ck-lists@cksoft.de>
To:        jungle Boogie <jungleboogie0@gmail.com>
Cc:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,  Maurizio Vairani <maurizio.vairani@cloverinformatica.it>,  FreeBSD stable <freebsd-stable@freebsd.org>
Subject:   Re: Error upgrading from 10.1-RELEASE to 10.2-RELEASE
Message-ID:  <alpine.BSF.2.20.1508241705500.95266@noc1.cksoft.de>
In-Reply-To: <CAKE2PDuRvVsx=Lft0T5siHoJxE-%2BUDCtSvGR5xc_idcE-G657g@mail.gmail.com>
References:  <55DAEA43.7020804@cloverinformatica.it> <7A2955B8-82A4-4F9E-A9C2-BEDFDACEA121@lists.zabbadoz.net> <CAKE2PDuRvVsx=Lft0T5siHoJxE-%2BUDCtSvGR5xc_idcE-G657g@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On Mon, 24 Aug 2015, jungle Boogie wrote:
> On 24 August 2015 at 05:14, Bjoern A. Zeeb
> <bzeeb-lists@lists.zabbadoz.net> wrote:
>> please see the thread “freebsd-update to 10.2-RELEASE broken ?” on this mailing list from this month;  I think there is no solution yet.
>
> The solution for me was to use a different DNS server on one of my
> machines. Others with a sensible DNS resolver fetched the files fine.

that is most propably just pure luck.

I tried using google dns (8.8.8.8) as resolver which worked sometimes and also failed sometimes.

The only way I have been able to upgrade systems is by repeatedly running freebsd-update.

Greetings
Christian

-- 
Christian Kratzer                   CK Software GmbH
Email:   ck@cksoft.de               Wildberger Weg 24/2
Phone:   +49 7032 893 997 - 0       D-71126 Gaeufelden
Fax:     +49 7032 893 997 - 9       HRB 245288, Amtsgericht Stuttgart
Mobile:  +49 171 1947 843           Geschaeftsfuehrer: Christian Kratzer
Web:     http://www.cksoft.de/
From owner-freebsd-stable@freebsd.org  Mon Aug 24 15:53:54 2015
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D04549C1386
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Mon, 24 Aug 2015 15:53:54 +0000 (UTC)
 (envelope-from hiren@strugglingcoder.info)
Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BF0661F0D
 for <freebsd-stable@freebsd.org>; Mon, 24 Aug 2015 15:53:54 +0000 (UTC)
 (envelope-from hiren@strugglingcoder.info)
Received: from localhost (unknown [10.1.1.3])
 (Authenticated sender: hiren@strugglingcoder.info)
 by mail.strugglingcoder.info (Postfix) with ESMTPSA id 7D608EB8E;
 Mon, 24 Aug 2015 08:53:53 -0700 (PDT)
Date: Mon, 24 Aug 2015 08:53:53 -0700
From: hiren panchasara <hiren@strugglingcoder.info>
To: KOT MATPOCKuH <matpockuh@gmail.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: Silent data corruption on em(4) interfaces
Message-ID: <20150824155353.GI71346@strugglingcoder.info>
References: <CALmdT0UC_gg6oSix_HSxLoJF_JDaqVbqen52trfcJGT2vKskgQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="tSiBuZsJmMXpnp7T"
Content-Disposition: inline
In-Reply-To: <CALmdT0UC_gg6oSix_HSxLoJF_JDaqVbqen52trfcJGT2vKskgQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>;
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2015 15:53:54 -0000


--tSiBuZsJmMXpnp7T
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 08/20/15 at 12:57P, KOT MATPOCKuH wrote:
> Hello!
>=20
> I got silent data corruption when transferring data via em(4) interface on
> 10.2-STABLE r286912.
> 1. I got broken large file transferred via ftp (MD5 checksum mismatched);
> 2. I got disconnects when transferring large data via ssh with messages:
> Corrupted MAC on input.
> Disconnecting: Packet corrupt
>=20
> Problem occurs only after few hours of uptime. Immediately after reboot I
> transferred same file via ftp without any errors.
>=20
> I tried to use:
> - em0 and em2 interfaces in link aggregation
> - em1 as "clean" interface
> But I got same problem in both cases.
>=20
> Also one time when transferring file I got this messages:
> em0: Interface stopped DISTRIBUTING, possible flapping
> em0: Watchdog timeout -- resetting
> em2: Interface stopped DISTRIBUTING, possible flapping
> em2: Watchdog timeout -- resetting
>=20
> netstat -in does not see any problems:
> Name    Mtu Network       Address              Ipkts Ierrs Idrop    Opkts
> Oerrs  Coll
> em0    1500 <Link#1>      00:14:4f:01:3f:7a  6689452     0     0
> 146720     0     0
> em1    1500 <Link#2>      00:14:4f:01:3f:7b  5732168     0     0
> 2865912     0     0
> em2    1500 <Link#3>      00:14:4f:01:3f:7c   501817     0     0
> 3392333     0     0
>=20
> Network adapters is build in to the Sun Fire X4100 mother board:
> em0@pci0:1:1:0: class=3D0x020000 card=3D0x10118086 chip=3D0x10108086 rev=
=3D0x03
> hdr=3D0x00
>     vendor     =3D 'Intel Corporation'
>     device     =3D '82546EB Gigabit Ethernet Controller (Copper)'
>     class      =3D network
>     subclass   =3D ethernet
>=20
> TCP_OFFLOAD disabled in kernel's config.

See if disabling TSO helps. You can disable on the interface with
'-tso'.

Cheers,
Hiren

--tSiBuZsJmMXpnp7T
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQF8BAEBCgBmBQJV2z4RXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4
QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/l1ekH/AojMWLtttRGlUAGuW4GWyg+
qzAN/EaWtenRCRqibOUDeuGb2qt4L5tuUluenCBcCv2UXOpet/3jS2Rdn/jWbyMP
+3UEIC8q5gBicKdZfnenpiq1mjUmxxAS2fetgKg0iOITTeF9uTkyzVAg5Wu2vJA7
D3r+6l95f1+2xXCvBQxJ6sgzD2Di1FL29fd+ftGCtgCqB/WjIw1sbIiZ5iVC111a
v26Pr/8gJ84ump99q3NSsFt7fKeHLjNw148ZyIDjDMcIIEScxO7mOitelG5CYvsh
HLy6XxFt5QwvlAsybZsUlPR+5tJYqg4QCRyduAPjjy3Vx1ARAsh6HBBwOa5Hcrw=
=dGjA
-----END PGP SIGNATURE-----

--tSiBuZsJmMXpnp7T--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1508241705500.95266>