From owner-freebsd-stable@freebsd.org Sun Jul 26 11:15:22 2015 Return-Path: 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 54E199AB4ED for ; Sun, 26 Jul 2015 11:15:22 +0000 (UTC) (envelope-from alnis.m@mail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15F6976D for ; Sun, 26 Jul 2015 11:15:22 +0000 (UTC) (envelope-from alnis.m@mail.com) Received: from [192.168.2.192] ([78.84.244.14]) by mail.gmx.com (mrgmxus002) with ESMTPSA (Nemesis) id 0LdZEi-1YbhCn2VsY-00ilfR for ; Sun, 26 Jul 2015 13:02:24 +0200 Message-ID: <55B4BE3C.2030801@mail.com> Date: Sun, 26 Jul 2015 14:02:20 +0300 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem References: <20150413081348.GA965@michelle.fasterthan.com> <55B36E1A.3040806@gmail.com> <20150726104039.GA1034@michelle.fasterthan.com> In-Reply-To: <20150726104039.GA1034@michelle.fasterthan.com> X-Provags-ID: V03:K0:B4K06E3JxrEaClqfC5WYvJln6RVp7J6cv49ei9xuUUkkRB8YGMZ Re5tYemQMlMNYICtiX+ppGWX5kEd0jTFEkdxgR64bYSLV/Dr8/o+AI39VfK7eVJGE/TWJBi obUCmuK9d2bMw9fTH10I1UR4wSANTcCRUlWoeUOjxvyJKjcMdiYAj6RlmAmfL24qgEqMdRF iovc927d6dApJrhXB5oLA== X-UI-Out-Filterresults: notjunk:1;V01:K0:CjZTx+f6k9w=:Oe6dA8DldDWAJH/Kqyhm4H c1VrBuCWaZ5alEOKsbb9o/PTnmNtYce7IYGA4vmLNAz0CNnzwq+votBd+G/5VUpk6xSvpCZ+F nX/1aGKAQO21Pfu/dvI3hYb9KfKTMTG8l9zBMoswCNKGKjsYwrwj0m0e1ypwpZ3h/u0JHWEoI 7DYmLvyrfSSJtR7dFmG5SJs8YXJPAIEOAUpgpfr5bDHziTCWaq69qHgvISRcAUcK0q/fHJJyZ rCyYyXABUc2bE1Qt/hQhUkaaKRN/j6zF/OhAzKKiJhijqY/xXRKH2pDOsNaeBiDYZwOg1PGGq uRzctdP3I1wgu+SSwO4+/8Ea2HC42p0jCWesmuWgLhc/yGn/XJ4GJaIwKBezQ1Kjpy8COyHxX oZcQzaM1f/JopBjVt48wpS5wkt5B3QiLtPg0qZ6dR2P+1haITSZhl1Qjr3QetKswzyWh0Y3jj Sc4b7cWm045sZhp7he8RYAyLkuHaYw3KG81ujesDBvhxaZK67HYar1gdyrWtufigkYro2OB5n EZ16fsUPsUukKFRko3QzsYwkmVyxSHB2GdjX7UKIOX7Pj0R/xzlPGv4R4D8VF7BIgJaQqlJJ0 AGhdAps/cIaJyeppQV4knCUEGoDjlh+iyeI1HaTmgGcvEwzOdhtzbfxJqYfO0NB1GZvYMwVZb gEg8Y7vsXqxA5xU/LqPngk+l+PPN71K73yNepWZ3sy+Ry2x2PK4Fkswe8O2Piv7m8zRU= Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2015 11:15:22 -0000 On 07/26/2015 01:40 PM, Yonghyeon PYUN wrote: > On Sat, Jul 25, 2015 at 02:08:10PM +0300, Alnis Morics wrote: > >> Just tried 10.2-RC1 amd64 GENERIC, and the problem seems to be gone. I >> was even able to scp a 500 MB file. Could it be related to this fix in >> BETA2, as mentioned in the announcement, "The watchdog(4) device has >> been fixed to print to the correct buffer."? >> > msk(4) will show watchdog timeouts when it detects driver TX path > is in stuck condition but I believe this has nothing to do with > watchdog(4). > > There was no msk(4) code change in 10.2-RC1. If you happen to see > the watchdog timeouts again, please try attached patch and let me > know whether it makes any difference for you. I didn't get much > feedbacks on the patch so I'm not sure whether it really fixes the > root cause. > >> pciconf -lv >> [..] >> mskc0@pci0:9:0:0: class=0x020000 card=0xc072144d chip=0x435411ab >> rev=0x00 hdr=0x00 >> vendor = 'Marvell Technology Group Ltd.' >> device = '88E8040 PCI-E Fast Ethernet Controller' >> class = network >> subclass = ethernet >> >> >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Thanks, Pyun. If the watchdog timeouts reappear, I'll try the patch and give notice about the results. -Alnis