From owner-freebsd-current@FreeBSD.ORG Wed Jul 10 06:57:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 19AF218C for ; Wed, 10 Jul 2013 06:57:18 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) by mx1.freebsd.org (Postfix) with ESMTP id A4C4A180B for ; Wed, 10 Jul 2013 06:57:17 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id c41so4624442eek.12 for ; Tue, 09 Jul 2013 23:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=Ca1s26kkZTS1CyFaWnLKypVFT8Qeao4IUHONoLD5MdI=; b=M9YLA352Ot7rKs8TjRd1ryex7QGwur+4Wgg9FWjKod4tpcOMScX/OeEoUu1XLe6BrY ct43mIpjIPa1Z28YAK1A6iFLVSIEzUfRSm7yBqSNoFiD/5XYINiZ76p+TKt1rh7E82FQ wUklTZB/+UyqXILUCfkwS1P4v4Co/RKMDRD+iJrtR6tXnaoj5sMcvF4wKw7245ZeE8N8 xWFM62MEHojK4ZWTJLFOOIWrsqrOKr36Os1phqa1OsQHNP+L5ymVGD2Au0AS5Pv8hqlP INrkpwLEIBfQ43DHv5/jTQmoJQlNVISwdPZccdzNwxxOzn7XPnh1FoT2G9PDTrO8bJOW 3Dhw== X-Received: by 10.14.251.202 with SMTP id b50mr34482180ees.85.1373439436569; Tue, 09 Jul 2013 23:57:16 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id b7sm57371067eef.16.2013.07.09.23.57.12 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 09 Jul 2013 23:57:14 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 10 Jul 2013 15:57:01 +0900 From: Yonghyeon PYUN Date: Wed, 10 Jul 2013 15:57:01 +0900 To: Denis D Subject: Re: msk0 watchdog timeout and interrupt storm Message-ID: <20130710065701.GD2753@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 06:57:18 -0000 On Sun, Jul 07, 2013 at 10:10:42PM +0200, Denis D wrote: > 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 metric 0 mtu 1500 > options=c009b > ether bc:ae:c5:5a:ef:ec > inet 192.168.2.30 netmask 0xffffff00 broadcast 192.168.2.255 > nd6 options=29 > media: Ethernet autoselect (100baseTX ) > 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. 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. > P.S: Can someone delete my other 2 posts? The format of them was horrible and the another one has no subject :(