From owner-freebsd-current@freebsd.org Tue Aug 2 18:12:45 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B8F2BAC149 for ; Tue, 2 Aug 2016 18:12:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1262D1BF6 for ; Tue, 2 Aug 2016 18:12:44 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-226-8.lns20.per1.internode.on.net [121.45.226.8]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u72ICdSh000894 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 2 Aug 2016 11:12:42 -0700 (PDT) (envelope-from julian@freebsd.org) To: freebsd-current From: Julian Elischer Subject: Xen networking problems in -current with xn driver? Message-ID: <0b90d4f0-fc02-7a07-6ce1-135a61cbc352@freebsd.org> Date: Wed, 3 Aug 2016 02:12:33 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 02 Aug 2016 18:12:45 -0000 I upgraded my VPS machine to today's current, and on reboot I couldn't get into it by network. A quick switch to the VNC console showed that it was up but that it couldn't get out. The xn interfaces said they were UP but attempts to get out were met with "network is down". if I did 'tcpdump -n -i xn0' (and xn1) hten all was fine again. tcpdump saw packets, and in fact ipfw saw some packets coming in even before that but it was not possible to send. Has anyone seen similar? some relevant parts of the dmesg output.: T(vga): text 80x25 XEN: Hypervisor version 3.4 detected. CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2400.05-MHz 686-class CPU) Origin="GenuineIntel" Id=0x206c2 Family=0x6 Model=0x2c Stepping=2 Features=0x1781fbff Features2=0x80982201 AMD Features=0x20100000 AMD Features2=0x1 Hypervisor: Origin = "XenVMMXenVMM" real memory = 536870912 (512 MB) avail memory = 503783424 (480 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: WARNING: L1 data cache covers less APIC IDs than a core 0 < 1 WARNING: L2 data cache covers less APIC IDs than a core 0 < 1 WARNING: L3 data cache covers less APIC IDs than a core 0 < 1 ipfw2 (+ipv6) initialized, divert loadable, nat enabled, default to deny, logging disabled xs_dev0: on xenstore0 xenbusb_front0: on xenstore0 xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:01:99:54 xn1: at device/vif/1 on xenbusb_front0 xn1: Ethernet address: 00:16:3e:01:9a:54 xenbusb_back0: on xenstore0 xenballoon0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xn1: backend features: feature-sg feature-gso-tcp4 xbd0: 20480MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd0: features: write_barrier xbd0: synchronize cache commands enabled.