From owner-freebsd-current@FreeBSD.ORG Sat Sep 28 23:37:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 49BBF3E2 for ; Sat, 28 Sep 2013 23:37:26 +0000 (UTC) (envelope-from robotsondrugs@gmail.com) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1C47729B1 for ; Sat, 28 Sep 2013 23:37:26 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id e14so6924219iej.6 for ; Sat, 28 Sep 2013 16:37:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=aJzV7AOyjiALBgGNA5HYuak+jXf5Va2IoqOwa0/uISI=; b=c1xw7Zm0gETfzSWN3i7n26Fexfk0p9mhdhrVY58i1cZ+VweF2Owi/bwRo35Vq4mAEC JyEIiI8UB6TWYHznJOJGmekgNUezel271IQrb/JRyofv4M7zziihp1tUbv+c0XMD/jEl G3PSf6HuvbyjpGMsxesM1XhPx4ZozYH847puLxY9b+Oy8ckU2X8y85c8+v/LMTp9wrbw B80QW7vvY+dXwoZr2QZ4xpVYAbFSRfOm1NmxHUap20W58NcLiFZTauH6Ec9pRBWhNxej xUzpt7K+0F/nxPKKXcj29xECH/P0qzufIZcYrF6v8su6t0I8KxHKhRydCXDJz8+Ku69j J3sw== X-Received: by 10.50.25.129 with SMTP id c1mr8276625igg.23.1380411445441; Sat, 28 Sep 2013 16:37:25 -0700 (PDT) Received: from [10.0.0.66] (c-98-240-141-71.hsd1.mn.comcast.net. [98.240.141.71]) by mx.google.com with ESMTPSA id ri1sm7141281igc.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 28 Sep 2013 16:37:24 -0700 (PDT) Message-ID: <52476833.4050100@gmail.com> Date: Sat, 28 Sep 2013 18:37:23 -0500 From: Andrew Berg User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Issues with Hyper-V network driver on ALPHA2/3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Sep 2013 23:37:26 -0000 FreeBSD talkingzebra 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #0 r255918: Fri Sep 27 17:29:41 CDT 2013 toor@talkingzebra:/usr/obj/usr/src/sys/HYPERV amd64 Sometimes after a reboot, the interfaces get an IP (statically set), but there is no connectivity. Starting or restarting the netif service causes this to appear every time: --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80119b9ca, rsp = 0x7fffffffd488, rbp = 0x7fffffffd4d0 --- Waiting on "rndis sema" with the following non-sleepable locks held: exclusive sleep mutex NetVSCLock (network driver) r = 0 (0xfffff80001c4f2b0) locked @ /usr/src/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c:904 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00b989a410 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00b989a4c0 witness_warn() at witness_warn+0x4a8/frame 0xfffffe00b989a580 _cv_timedwait_sbt() at _cv_timedwait_sbt+0x94/frame 0xfffffe00b989a600 _sema_timedwait() at _sema_timedwait+0x74/frame 0xfffffe00b989a640 hv_rf_set_packet_filter() at hv_rf_set_packet_filter+0x184/frame 0xfffffe00b989a680 hv_rf_on_open() at hv_rf_on_open+0x46/frame 0xfffffe00b989a6a0 hn_ifinit() at hn_ifinit+0xbe/frame 0xfffffe00b989a6e0 ether_ioctl() at ether_ioctl+0x8a/frame 0xfffffe00b989a710 hn_ioctl() at hn_ioctl+0x28a/frame 0xfffffe00b989a770 in_control() at in_control+0xbe5/frame 0xfffffe00b989a820 ifioctl() at ifioctl+0xfc7/frame 0xfffffe00b989a8e0 kern_ioctl() at kern_ioctl+0x2ca/frame 0xfffffe00b989a950 sys_ioctl() at sys_ioctl+0x142/frame 0xfffffe00b989a9a0 amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe00b989aab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00b989aab0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80119b9ca, rsp = 0x7fffffffd488, rbp = 0x7fffffffd4d0 --- Every time, everything looks good according to ifconfig, but pings to IPs in the same network always time out. If I reboot again, it will generally come back with networking working just fine, and I have found no way to get the interfaces to work other than rebooting again. This is happening on ALPHA3 (r255918), but I have noticed it in a previous revision as well (I can't recall the revision, but it was after the hyperv device was removed from GENERIC). I have the entire dmesg saved (before reboot) from that session if that would help. Also, this is on client Hyper-V on Windows 8, if that matters.