Bug 189404 - [msk] msk0:watch dog time out
Summary: [msk] msk0:watch dog time out
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-07 02:10 UTC by Zuyi Hu
Modified: 2018-05-28 19:44 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Zuyi Hu 2014-05-07 02:10:00 UTC 
my pciconf output of msk0 is:

mskc0@pci0:2:0:0:	class=0x020000 card=0x3079103c chip=0x436c11ab rev=0x10 hdr=0x00
    vendor     = 'Marvell Technology Group Ltd.'
    device     = '88E8072 PCI-E Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet
    cap 01[48] = powerspec 3  supports D0 D1 D2 D3  current D0
    cap 03[50] = VPD
    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 18ae73ffffb32500
and the card worked normally before , but it show "watch dog timeout" today,how can I solve it.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-10-17 23:20:00 UTC 
Reclassify.
Comment 2 Roosevelt 2015-03-02 16:54:18 UTC 
I went back to 9.3 work "extremely" well with msk0.
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2015-04-12 18:26:10 UTC 
see

https://lists.freebsd.org/pipermail/freebsd-stable/2015-April/082226.html

for a suggested solution.
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:44:13 UTC 
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.