From owner-freebsd-stable@FreeBSD.ORG Wed Jan 29 14:35:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EFA0BD9 for ; Wed, 29 Jan 2014 14:35:19 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F3E7B1FE4 for ; Wed, 29 Jan 2014 14:35:18 +0000 (UTC) Received: from blazon-pc.rw.local ([78.84.244.14]) by mail.gmx.com (mrgmxus001) with ESMTPSA (Nemesis) id 0MMSxU-1WCMm92vHi-008Jav for ; Wed, 29 Jan 2014 15:35:11 +0100 Message-ID: <52E911E8.2090104@mail.com> Date: Wed, 29 Jan 2014 16:36:24 +0200 From: Jeff Tipton User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20121030 Thunderbird/16.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: regression: msk0 watchdog timeout and interrupt storm References: <52E6CB2B.9040208@mail.com> In-Reply-To: <52E6CB2B.9040208@mail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:qZ5U5kqVABg8RcoOv/VsVNWT3KDDDUro8CqDZ+cS9PDJGDuFm3z Ze5NjADv0RQ6SiCDxzGN/3wX2/y9scvfP5ccHXyDlI+0zOlKGwbMcrd9bidEvKfCkhQV8et mcTTGhJgyEXQlDVS/+szYC3UUjSeItI3P7/O1kk1ZnXHyDuw4bgyXTWkAe5YXOBQ+qtEqB+ SOAH0hAVSxovQflpHvkxQ== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 14:35:19 -0000 On 01/27/2014 23:10, Jeff Tipton wrote: > Hi, > > I also have this problem on Samsung N220 netbook, except I don't have > any "interrupt storm" messages. When it boots up, it works a couple of > minutes, and then "msk0: watchdog timeout" message appears. And, yes, > the fastest way to reproduce the error is to try to copy a file via > scp (even a 6MB file is enough). > > uname -a > > FreeBSD [..] 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 > 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > pciconf -lcv > [..] > > 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 > cap 01[48] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 05[5c] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[c0] = PCI-Express 2 legacy endpoint max data 128(128) link > x1(x1) > speed 2.5(2.5) ASPM L0s/L1(L0s/L1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0003[130] = Serial 1 f0d173ffff542400 > > I have FreeBSD 9.2-RELEASE on another partition, and msk0 works just > fine there. > > I also tried to change if_mskreg.h as Curtis suggested, recompiled the > kernel but it didn't help; nothing changed :( > > Jeff > _______________________________________________ > 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" And, yes, I also found out that after having been booted into 10.0, if I immediately reboot into 9.2, msk0 doesn't work there either; no "watchdof timeout" messages, though; but ifconfig shows "no carrier"; restarting interface or netif service doesn't help. I had to switch the netbook off completely and take the battery out for some minutes, and only then it finally worked in 9.2 again.