From owner-freebsd-current@freebsd.org Wed Apr 26 02:18:30 2017 Return-Path: Delivered-To: freebsd-current@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 24EC6D4F9CC for ; Wed, 26 Apr 2017 02:18:30 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5m.cmail.yandex.net (forward5m.cmail.yandex.net [IPv6:2a02:6b8:b030::1c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A1D12385 for ; Wed, 26 Apr 2017 02:18:29 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [77.88.61.132]) by forward5m.cmail.yandex.net (Yandex) with ESMTP id 5923E2116A; Wed, 26 Apr 2017 05:18:26 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id B837A63C0C33; Wed, 26 Apr 2017 05:18:25 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id M5wUYELpPp-IOiSAijw; Wed, 26 Apr 2017 05:18:24 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1493173104; bh=ir5UoGG5mG/xm+LHkZHiehaOC3D9fFZMqv1SR4VVTIE=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=gQlTRi81c11BDofBAmqO/8hYyi0Ul2vm5yhy1Ux+wY0hTdOw/4XM6Xd/TvtSURIHZ KYbrgl+Bcal2aF11ScT/ZcM21LSIc476TYIxlwf/cEhTh1ZyBLUjzAKBfFnNgKp+dK z+7Rux25CW/LPq5agRoNd1aHumrx0p42P6vbtAzI= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: panics in network stack in 12-current To: Tom Uffner , freebsd-current References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <92a10822-3fde-f839-1836-92e8d936f2b6@yandex.ru> Date: Wed, 26 Apr 2017 05:17:26 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Xu0QmwpP4jAu47MX9CuRD42LK5Qv2frBS" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 02:18:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Xu0QmwpP4jAu47MX9CuRD42LK5Qv2frBS Content-Type: multipart/mixed; boundary="gbRFTKvL5wG0IOfbNltxN3RcSNiJ16DDt"; protected-headers="v1" From: "Andrey V. Elsukov" To: Tom Uffner , freebsd-current Message-ID: <92a10822-3fde-f839-1836-92e8d936f2b6@yandex.ru> Subject: Re: panics in network stack in 12-current References: In-Reply-To: --gbRFTKvL5wG0IOfbNltxN3RcSNiJ16DDt Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 26.04.2017 04:03, Tom Uffner wrote: > Since updating my -current box to 12 several months ago, I have been > trying to pin down several elusive and probably related panics. >=20 > they always manifest a a trap out of rw_wlock_hard() >=20 > i am fairly certain that r302409 was stable, revs up through r306792 ma= y be > stable, or perhaps I just didn't wait long enough for my system to pani= c. I > don't know of anything that I can reproducably poke at to trigger this.= > r306807 is definitely bad, as is everything up through r309124. I > haven't seen anything on the mailing lists or in the SVN logs that look= s > like it is related to my problem. >=20 > my hardware is an Asus M4A77TD MB, AMD Phenom 2 X6 1100T CPU (for some = of > this time I had an Athlon 2 X2, but upgraded recently), and RealTek 816= 8 > PCIe Gigabit NIC. >=20 > FreeBSD discordia.uffner.com 12.0-CURRENT FreeBSD 12.0-CURRENT #33 > r306807M: Tue Apr 18 17:09:55 EDT 2017 > tom@discordia.uffner.com:/usr/obj/usr/src/sys/DISCORDIA amd64 >=20 > in revs between 306807-307125, the panics have been in flowcleaner, in > more recent ones, they happen in arbitrary userspace processes that mak= e > heavy use > of the network. >=20 > I know I should try the latest rev to see if it went away. aside from > that, any thoughts on how I should proceed? I think the most of these panics should be fixed in r315956. --=20 WBR, Andrey V. Elsukov --gbRFTKvL5wG0IOfbNltxN3RcSNiJ16DDt-- --Xu0QmwpP4jAu47MX9CuRD42LK5Qv2frBS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlkAAz0ACgkQAcXqBBDI oXrwnAf/fGkIsxHYGjfDhRlm7W378jHWbPR2QS4/PMEPJNts/hhGWs+xm8ZAb4vY ZqPRomQCrLUmQVyPI7E91OeAns/ctMEdTZN4mgMl6ub2nuPvKPj5tTKOB8VC9WOc CkDihLv6z9hS2XFUXGqKYdXGi8UcqQrDFX5KqHFxyDG2Rtqb1pgyUnnC2ebIxy2h EP2fGLPXXTyFqm6iewBy54tby8w16m1lGwhuwKiff4JGIum0QQ6T6S3eEnVJ1I9o mX4UoZ9uzLg5gE924aznBKFl11B6ZkOqZAU7uLQpQVvTaEya2h4zBlhWcNVhdn4F DzLVajitQKGEKw2V95SOonZHN3KesQ== =lqmv -----END PGP SIGNATURE----- --Xu0QmwpP4jAu47MX9CuRD42LK5Qv2frBS--