Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 08 Feb 2014 01:24:10 +0200
From:      Jeff Tipton <jeff.t@mail.com>
To:        freebsd-stable@freebsd.org
Subject:   Re: regression: msk0 watchdog timeout and interrupt storm
Message-ID:  <52F56B1A.3020904@mail.com>
In-Reply-To: <20140207051340.GC1369@michelle.cdnetworks.com>
References:  <52E6CB2B.9040208@mail.com> <52E911E8.2090104@mail.com> <20140207051340.GC1369@michelle.cdnetworks.com>

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

On 02/07/2014 07:13, Yonghyeon PYUN wrote:
> On Wed, Jan 29, 2014 at 04:36:24PM +0200, Jeff Tipton wrote:
>> 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.
> Jeff, please try r261577 and let me know how it works.
> As you said, cold-boot is recommended way to test r261577.
> _______________________________________________
> 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"
Ok, I'm working on but it will take some time. Meanwhile I can tell that 
I experimented with PC-BSD 10, and that worked without any flaw. I don't 
know how it relates here but their revision was:

10.0-RELEASE-p5 FreeBSD 10.0-RELEASE-p5 #8 b261212(releng/10.0): Fri Jan 
24 11:21:56 EST 2014 
root@avenger:/usr/obj/root/pcbsd-build10.0/git/freebsd/sys/GENERIC amd64

Then an update reverted it back to p4 which also worked ok.

-Jeff



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52F56B1A.3020904>