Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

msk0 watchdog timeout and interrupt storm

1 view
Skip to first unread message

Denis D

unread,
Jul 7, 2013, 3:58:43 PM7/7/13
to
Hello Community,
I hope someone could help me with this problem. The last days I have tried to find a solution, but haven't found one.
The watchdog timeout happens, when I'm going to download something or copy a file on my FTP server. When I start the transfer of the file, I wait a moment and then my down-/upload freezes at something around 500[ ]KB. After waiting a little while or press a key like "return", it comes to the interrupt storm.

interrupt storm detected on "irq51:"; throttling interrupt source

Here is some information about my system:
ifconfig msk0
msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=c009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE> ether bc:ae:c5:5a:ef:ec inet 192.168.2.30 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>) status: active

pciconf -lv
mskc0@pci0:3:0:0: class=0x020000 card=0x84391043 chip=0x438111ab rev=0x11 hdr=0x00 vendor = 'Marvell Technology Group Ltd.' device = 'Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB]' class = network subclass = ethernet

vmstat -i
interrupt total rateirq1: atkbd0 916 2irq16: hdac1 97 0irq17: ehci0 ehci1+ 8729 21irq18: ohci0 ohci1* 67 0irq19: ahci1 2883 7irq25: hdac0 4 0irq51: mskc0 90 0irq256: hpet0:t0 30332 75Total 43118 107

loader.conf
hw.msk.msi_disable=1hw.pci.enable_msi=0hw.pci.enable_msix=0rc.confCode:hostname="FreeBSD.local.domain"keymap="german.iso.acc.kbd"ifconfig_msk0="DHCP"
sshd_enable="YES"moused_enable="YES"powerd_enable="YES"# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disabledumpdev="AUTO"

I have also tried to change ifconfig_msk0="DHCP" to ifconfig_msk0="SYNCDHCP" but nothing changed.
If nothing helps, I will buy a new network card.

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
Too many newsletters? You can unsubscribe or better yet, schedule automatic cleanup.ActionsDenis D8:33 PMTo: freebsd...@freebsd.orgtrying to fix my format ;)


Hello Community,I hope someone could help me with this problem. The last days I have tried to find a solution, but haven't found one.The watchdog timeout happens, when I'm going to download something or copy a file on my FTP server. When I start the transfer of the file, I wait a moment and then my down-/upload freezes at something around 500 KB. After waiting a little while or press a key like "return", it comes to the interrupt storm.interrupt storm detected on "irq51:"; throttling interrupt sourceHere is some information about my system:ifconfig msk0msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether bc:ae:c5:5a:ef:ec
inet 192.168.2.30 netmask 0xffffff00 broadcast 192.168.2.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
status: activepciconf -lvmskc0@pci0:3:0:0: class=0x020000 card=0x84391043 chip=0x438111ab rev=0x11 hdr=0x00
vendor = 'Marvell Technology Group Ltd.'
device = 'Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB]'
class = network
subclass = ethernetvmstat -iinterrupt total rate
irq1: atkbd0 916 2
irq16: hdac1 97 0
irq17: ehci0 ehci1+ 8729 21
irq18: ohci0 ohci1* 67 0
irq19: ahci1 2883 7
irq25: hdac0 4 0
irq51: mskc0 90 0
irq256: hpet0:t0 30332 75
Total 43118 107loader.confhw.msk.msi_disable=1
hw.pci.enable_msi=0
hw.pci.enable_msix=0
rc.conf
hostname="FreeBSD.local.domain"
keymap="german.iso.acc.kbd"
ifconfig_msk0="DHCP"sshd_enable="YES"
moused_enable="YES"
powerd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"I have also tried to change ifconfig_msk0="DHCP" to ifconfig_msk0="SYNCDHCP" but nothing changed.If nothing helps, I will buy a new network card.


_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

Denis D

unread,
Jul 7, 2013, 4:10:42 PM7/7/13
to
Hello Community,I hope someone could help me with this problem. The last days I have tried to find a solution, but haven't found one.The watchdog timeout happens, when I'm going to download something or copy a file on my FTP server. When I start the transfer of the file, I wait a moment and then my down-/upload freezes at something around 500 KB. After waiting a little while or press a key like "return", it comes to the interrupt storm.
interrupt storm detected on "irq51:"; throttling interrupt source.
Here is some information about my system:
ifconfig msk0msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,VLAN_HWTSO,LINKSTATE>
ether bc:ae:c5:5a:ef:ec
inet 192.168.2.30 netmask 0xffffff00 broadcast 192.168.2.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>)
status: active
pciconf -lv
mskc0@pci0:3:0:0: class=0x020000 card=0x84391043 chip=0x438111ab rev=0x11 hdr=0x00
vendor = 'Marvell Technology Group Ltd.'
device = 'Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB]'
class = network
subclass = ethernetvmstat -iinterrupt total rate
irq1: atkbd0 916 2
irq16: hdac1 97 0
irq17: ehci0 ehci1+ 8729 21
irq18: ohci0 ohci1* 67 0
irq19: ahci1 2883 7
irq25: hdac0 4 0
irq51: mskc0 90 0
irq256: hpet0:t0 30332 75
Total 43118 107
My loader.conf:
hw.msk.msi_disable=1
hw.pci.enable_msi=0
hw.pci.enable_msix=0
My rc.conf
hostname="FreeBSD.local.domain"
keymap="german.iso.acc.kbd"
ifconfig_msk0="DHCP"sshd_enable="YES"
moused_enable="YES"
powerd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
I have also tried to change ifconfig_msk0="DHCP" to ifconfig_msk0="SYNCDHCP" but nothing changed.If nothing helps, I will buy a new network card.
P.S: Can someone delete my other 2 posts? The format of them was horrible and the another one has no subject :(

Yonghyeon PYUN

unread,
Jul 10, 2013, 2:57:01 AM7/10/13
to
If you use dual-boot, please try "cold-boot" it. Other OS may have
put the PHY into weird state. Cold-boot shall make firmware restore
its PHY configuration.

Denis D

unread,
Jul 13, 2013, 7:39:06 AM7/13/13
to
> If you use dual-boot, please try "cold-boot" it. Other OS may have


> put the PHY into weird state. Cold-boot shall make firmware restore


> its PHY configuration.


>





Hello pyunyh,




when i really understand the word coldbootkorrekt,it means, that i have to shutdown my pc.
And start it (during he was off) and boot into FreeBSD.




My PC was off for 9 hours because of work, but still the same "watchdog timeout" error.




Maybe some other solutions?

Yonghyeon PYUN

unread,
Jul 14, 2013, 6:34:44 AM7/14/13
to
On Sat, Jul 13, 2013 at 01:39:06PM +0200, Denis D wrote:
> > If you use dual-boot, please try "cold-boot" it. Other OS may have
>
>
> > put the PHY into weird state. Cold-boot shall make firmware restore
>
>
> > its PHY configuration.
>
>
> >
>
>
>
>
>
> Hello pyunyh,
>
>
>
>
> when i really understand the word coldbootkorrekt,it means, that i have to shutdown my pc.
> And start it (during he was off) and boot into FreeBSD.
>
>
>
>
> My PC was off for 9 hours because of work, but still the same "watchdog timeout" error.

Did you completely remove power-cord and wait 1 ~ 2 min. before
boot?

There are many Yukon II variants and each controller seems to
require special handling to work-around silicon bugs. And your
controller has a Audio Video Bridging (AVB) feature which may
or may not need a special handling in TX/RX path. At least it may
need to initialize or disable QoS specific feature of controller,
I guess. Unfortunately errata or detailed programming information
is not available to open source developers.

Interrupt storm seems to indicate one of important event was not
properly handled in driver. Not sure what it is.

>
>
>
>
> Maybe some other solutions?

Sorry, have no further idea at this moment.
I hoped cold-boot shall put controller into compatible mode but it
seems it does not. I'll let you know if I happen to find a clue.
0 new messages