From owner-freebsd-stable@freebsd.org Sun Sep 3 06:20:52 2017 Return-Path: Delivered-To: freebsd-stable@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 0D8B7E1D9AD for ; Sun, 3 Sep 2017 06:20:52 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from roadkill.tharned.org (gcrivers-1-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD63A840BD for ; Sun, 3 Sep 2017 06:20:51 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:adab:5aab:1c33:3706]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id v836Kiqe063279 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 3 Sep 2017 01:20:50 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2017; t=1504419650; bh=zxihmS84Tpag6HEpgYX3MMnNBweppHfGlgHHfjXjbm0=; l=321; h=From:To:Subject:Date:In-Reply-To:References; b=QQ2q3W5w6AjuMBln8jH6jHxGsdGbdGpD+RFNGvUDmkEUB4x1sX/lFzO7drJqcmW/g E0mh5JmUMw00uwIrzmZ1htHjUrGsMCi5WMtA3rYKP54DRpgRqRI3yRcvtzXiPoRXCW /8otfUjQUxasemh/HnadqCHfxUkhbhSkKk55yy138b94YJeKIIs1E1Cl5ALQHGHcHT rTdcfOaXNM5jx+Keu27PirKsrsuPxqRtWBJ8TBhY7P6NImsjaK+NG8Tvv/8P9BvS5n GFQAhDGtBKtfixBXN4ozCBj5GOq00OxB41nNzoP0Y2siAr1/FOn5Wh2ShznZ3u35CG BPlYAZwxLcE3Q== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:adab:5aab:1c33:3706] claimed to be flake.tharned.org From: Greg Rivers To: freebsd-stable@freebsd.org Subject: Re: SLAAC not working Date: Sun, 03 Sep 2017 01:20:42 -0500 Message-ID: <3078071.oYt2PD7K2Q@flake.tharned.org> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <1646645.UkMcyRZBVl@flake.tharned.org> References: <1646645.UkMcyRZBVl@flake.tharned.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Sun, 03 Sep 2017 01:20:50 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 06:20:52 -0000 Aside from ruling out the MTU option in the RAs as the cause, I've made little progress on finding the problem. Can anyone explain the use of net.inet6.icmp6.nd6_debug=1 for NDP debugging? I get no log output at all. -- Greg Rivers https://lists.freebsd.org/pipermail/freebsd-stable/2017-August/087576.html From owner-freebsd-stable@freebsd.org Sun Sep 3 08:58:10 2017 Return-Path: Delivered-To: freebsd-stable@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 B6537E00A50 for ; Sun, 3 Sep 2017 08:58:10 +0000 (UTC) (envelope-from tarjei99@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C4FA3CD2 for ; Sun, 3 Sep 2017 08:58:10 +0000 (UTC) (envelope-from tarjei99@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id n18so27283503oig.2 for ; Sun, 03 Sep 2017 01:58:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=UJCcH8WrlfRN27sP5IA9KdyRGmeiIjmywKKiQkudQw8=; b=naGIKKZrWU8PA11aWYDxDE8yb0oU/bQA/2LwVWyVgk7Q55sCB+Fpnk9JLKIgvPy0no 5BqLkpxB4le6ow9VV5vql0Wu0WdounJxgCnZzqCJmIEvbHntllbGettsghkiVOjtkm+0 qBm0mnWeMfxc4wrKZvpVeiNz+n9WQmCyEN181a5vFIVybKkfho5r1P7/gSWq/VgujGT2 512OsQnd0DpCUloha6ZKKuquJ5up+QzZvdHpsSttFyt423WWSNnV2jVUjZ3x7xdTIYDO KFjpOyG3sg2RARyowWlevnFgl8t+K4jnq38UetNMeXp4jpBi6xFiTJtNlXbGpD1plFAI GTuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UJCcH8WrlfRN27sP5IA9KdyRGmeiIjmywKKiQkudQw8=; b=MICSNTXAXx+LcqlZ0VNe9smoO8+qleBZgB4OI16LsSTKEBxRRxnbvs67cFcjxeFnTR jvVVx5BBLWfpIf9+UTiSmocm8LrIAsAZM1gS6PN4W0JM9Rb9BJi/PSinc0pXvoDaYcIk LVPtlG0UNqNLf9L+Dft/lOBFRQ65/RdQ4iIARBIvPx2+UrotobN/D3exoDN1hXmD/2Mo MgwrS2dxgzRjCBCSUof2vtpaNfgVruVpPq+vFsxFHUmdrGhlENE9fanlzc2NE2ucTfxi R6KaSpCaC0MDAG7rDO5WjBY5oldQvwufqGHbfozk6/yGzpipyLeVWjye6cUr8TZmU3Gn yOnA== X-Gm-Message-State: AHPjjUjewePe3aXWkgbwEPQdmeRMnVatcbdh61VeOR5MGac11EcGgJE6 VHcLNlRhcfuRllzPIkAr42VtMSv4O21Z X-Google-Smtp-Source: ADKCNb7ZdWfySj593p/ZUlMw3hQoFYqYxnsmjlJLgyddhe5QIHmnwJxlHyGYBw38f/7skonBsItuulQp4/fPO0m0DtM= X-Received: by 10.202.72.17 with SMTP id v17mr5895995oia.141.1504429089381; Sun, 03 Sep 2017 01:58:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.35.244 with HTTP; Sun, 3 Sep 2017 01:58:09 -0700 (PDT) From: Tarjei Jensen Date: Sun, 3 Sep 2017 10:58:09 +0200 Message-ID: Subject: Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 08:58:10 -0000 It is perhaps a bit late to chip in on the fixincludes issue. The "easy" fix for the fix includes issue is to edit the mkfixinc.sh file as suggested in the page which I linked to below. I suppose the packages kits could be loaded, the fix applied and the kit repackaged. A different fixe would perhaps be to complain to those who maintain autoconf an request that they implement something that will fix the issue. Either through an environment variable or a configuration file. The latter, preferably something that is simple to use. Not something that requires programming. Iy interest in this is that I'm trying to build gcc6-aux on a Raspberry PI 3 using FreeBSD v 12. And the fixinclude bites. OSdev.org on fixincludes Greetings, From owner-freebsd-stable@freebsd.org Sun Sep 3 12:54:38 2017 Return-Path: Delivered-To: freebsd-stable@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 E69AEE0A28A for ; Sun, 3 Sep 2017 12:54:38 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 640586ADCA for ; Sun, 3 Sep 2017 12:54:37 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v83CsCR6002573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Sep 2017 22:24:13 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Mark Saad'" , Cc: , References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> In-Reply-To: <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> Subject: RE: HP Smart array P440 support Date: Sun, 3 Sep 2017 22:23:30 +0930 Message-ID: <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gHTaXA5AxT7FosCgV+fHaDOXcRQ Content-Language: en-au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 12:54:39 -0000 I have tried to install FreeBSD 10.3 in a HP DL20 Gen 9 server with P440 smart array. My installation media is in a USB drive. In BIOS I set the Boot mode to Legacy boot mode.=20 Created my P440 array and a logical drive with RAID 1. Disabled B140i controller. The installation process went on and I saw the following messages : =20 >ciss0: port 0x2000-0x20ff mem=20 > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff irq 16 at device 0.0 on=20 > pci3 > ciss0: PERFORMANT Transport > ... > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: Serial Number PDNLH0BRH8S3RF > da0: 135.168MB/s transfers > da0: Command Queueing enabled > da0: 139979MB (286677120 512 byte sectors) Similar to yours but not exactly the same. But I have ciss0 on P440 and = da0 on ciss0. I think my P440 is properly probed and instantiated. After = this stage my installation process hangs with the following error: Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. Then my usb keyboard is frozen and I can not enter anything to let the installation process continue.=20 I can not figure what the problem is. Could you please give me some solution? Could it be an installation media download issue?. = Installation media creation problem ? ( I used=20 dd if=3DFreeBSD-10.3-RELEASE-i386-mini-memstick.img of=3D/dev/da1 = bs=3D1M conv=3Dsync command to create the boot usb) Regards, Chandrasena -----Original Message----- From: Mark Saad [mailto:nonesuch@longcount.org]=20 Sent: Sunday, 3 September 2017 3:56 AM To: sthaug@nethelp.no Cc: vpc@ulka.com.au; rainer@ultra-secure.de; FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support All Also don't forget to is install cciss_vol_status to monitor the array . --- Mark Saad | nonesuch@longcount.org On Sep 2, 2017, at 11:41 AM, sthaug@nethelp.no wrote: >>> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in=20 >>> it. I have a HP smart array P440 in my server. I can not find out=20 >>> anywhere if ciss driver support include HP Gen 9 storage=20 >>> controllers. Could you please update the ciss driver in 10.3? >>=20 >> Try 10.3 >>=20 >> I know the release-notes say nothing about it, but I believe it is supported. >>=20 >> If not that, 11.0 surely does (even though the release-notes=20 >> don=1B$,1ry=1B(Bt mention it, either) >=20 > I can confirm that 10.3 supports the P440 controller. From a DL360=20 > Gen9 server running 10.3 here: >=20 > ciss0: port 0x2000-0x20ff mem=20 > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff irq 16 at device 0.0 on=20 > pci3 > ciss0: PERFORMANT Transport > ... > da0 at ciss0 bus 0 scbus0 target 0 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: Serial Number PDNLH0BRH8S3RF > da0: 135.168MB/s transfers > da0: Command Queueing enabled > da0: 139979MB (286677120 512 byte sectors) >=20 > Steinar Haug, Nethelp consulting, sthaug@nethelp.no=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list=20 > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Sun Sep 3 12:57:08 2017 Return-Path: Delivered-To: freebsd-stable@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 74138E0A46D for ; Sun, 3 Sep 2017 12:57:08 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id D60286AF20 for ; Sun, 3 Sep 2017 12:57:07 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sun, 03 Sep 2017 14:57:06 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id AFC02EAA-82A9-4AC7-B6E8-B12DBE06220C.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Sun, 03 Sep 2017 14:57:03 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HP Smart array P440 support From: Rainer Duffner In-Reply-To: <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> Date: Sun, 3 Sep 2017 14:57:00 +0200 Cc: Mark Saad , sthaug@nethelp.no, FreeBSD-stable@FreeBSD.org Content-Transfer-Encoding: 7bit Message-Id: References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> To: Priyadarshana Chandrasena X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=1 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3849, bad: 1, connections: 4274, history: 3848, asn_score: 382, asn_connections: 393, asn_good: 382, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 12:57:08 -0000 > Am 03.09.2017 um 14:53 schrieb Priyadarshana Chandrasena : > > I have tried to install FreeBSD 10.3 in a HP DL20 Gen 9 server with P440 > smart array. My installation media is in a USB drive. > > In BIOS I set the Boot mode to Legacy boot mode. Why? It should work in UEFI. That said, we only have DL360 and DL380 here. Never saw a DL20 besides on slides from HP ;-) From owner-freebsd-stable@freebsd.org Sun Sep 3 13:05:21 2017 Return-Path: Delivered-To: freebsd-stable@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 5DF9CE0A9B8 for ; Sun, 3 Sep 2017 13:05:21 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8FC36B33A for ; Sun, 3 Sep 2017 13:05:20 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v83D52XV002603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Sep 2017 22:35:02 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Rainer Duffner'" Cc: "'Mark Saad'" , , References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> In-Reply-To: Subject: RE: HP Smart array P440 support Date: Sun, 3 Sep 2017 22:34:19 +0930 Message-ID: <000201d324b5$2a72bf40$7f583dc0$@ulka.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gHTaXA5AxT7FosCgV+fHQI64gavAvR2vKugpOl4gA== Content-Language: en-au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 13:05:21 -0000 In UEFI mode the boot process does not read the installation media usb. Never booted from the usb in UEFI mode! -----Original Message----- From: Rainer Duffner [mailto:rainer@ultra-secure.de] Sent: Sunday, 3 September 2017 10:27 PM To: Priyadarshana Chandrasena Cc: Mark Saad; sthaug@nethelp.no; FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support > Am 03.09.2017 um 14:53 schrieb Priyadarshana Chandrasena : > > I have tried to install FreeBSD 10.3 in a HP DL20 Gen 9 server with > P440 smart array. My installation media is in a USB drive. > > In BIOS I set the Boot mode to Legacy boot mode. Why? It should work in UEFI. That said, we only have DL360 and DL380 here. Never saw a DL20 besides on slides from HP ;-) From owner-freebsd-stable@freebsd.org Sun Sep 3 14:33:43 2017 Return-Path: Delivered-To: freebsd-stable@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 39DB3E0E1B1 for ; Sun, 3 Sep 2017 14:33:43 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 8CF7E6D64E for ; Sun, 3 Sep 2017 14:33:41 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Sun, 03 Sep 2017 16:33:34 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 7564DED7-925B-4127-9527-182632A187A3.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Sun, 03 Sep 2017 16:33:31 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HP Smart array P440 support From: Rainer Duffner In-Reply-To: <000201d324b5$2a72bf40$7f583dc0$@ulka.com.au> Date: Sun, 3 Sep 2017 16:33:29 +0200 Cc: Mark Saad , FreeBSD-stable@FreeBSD.org, sthaug@nethelp.no Content-Transfer-Encoding: 7bit Message-Id: References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> <000201d324b5$2a72bf40$7f583dc0$@ulka.com.au> To: Priyadarshana Chandrasena X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=2 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3850, bad: 1, connections: 4275, history: 3849, asn_score: 383, asn_connections: 394, asn_good: 383, asn_bad: 0, pass:asn, asn_all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 14:33:43 -0000 > Am 03.09.2017 um 15:04 schrieb Priyadarshana Chandrasena : > > In UEFI mode the boot process does not read the installation media usb. > Never booted from the usb in UEFI mode! Hm. Interesting. Can you try 11.1 then? I think I had that problem around the 9.x days, with G7 hardware. Or I think it was with booting from the emulated CD via iLO. From owner-freebsd-stable@freebsd.org Sun Sep 3 15:15:00 2017 Return-Path: Delivered-To: freebsd-stable@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 DC5CBE1018D for ; Sun, 3 Sep 2017 15:15:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6F4E6EB4B for ; Sun, 3 Sep 2017 15:15:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id f99so13586902ioi.3 for ; Sun, 03 Sep 2017 08:15:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ovk7IQyPgfYu9lDwqD3bMs1F5FiRNT5u82D//ynMlRU=; b=czM10JYhRJObs6nWuClY7/ep3iwtijDWsgRUWL+MTF/8QSf/mhqXj6weeg7UoQ6q6N aFE2sCixaD49SXCKD+BNBb/Mogy0QhkVXka8RgxhL4rOZ4PKFPmHFkCZXyLGbUohJEHe +FYKHpAX9wErmLqQxHLgaRQKDMOyeXDiAVafUmJgZJPUsjoSl2Hu2Lm5quprGKByVn4E UN1qo6C/cmhZYEXdK4Or2YHtWTap2SUVcGOplAyHGteP3IcAnEbg3laciPvbqVQLbwac YfwNE78xhO1j5gS/YpQk4nYwLV/iaLt1WR0/N1/sB4ksjAc4r3HQAqjWIgVg3zZXR+k2 tsqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ovk7IQyPgfYu9lDwqD3bMs1F5FiRNT5u82D//ynMlRU=; b=sFX6SKbJ7RhCkGY+G4vcdTaunUskQsL9RYswH/ulSOYmnPWbdVHr8ekMp2jQEM7nJi 1f/e/11CXg04ZH8M+PLfWITV5tOHXRZXQss0TlXxdNB6M4sjCpBowv3X/7TQqE+CmSSb xUBhaw7aakFClLXpfKJd6f1t4VF4iU1WfdL7Fty3hYUoEaKOjL2U58b9JKvX0BekqChe 4cuddXlLo5rK9rN0RrsyCi+Px77wkgHk36rRDG1VPVPV3nO+AyyHM6WTux53zbJgS6ns hijAMKG46xvoX3rhnZBL+6ieqR2KnXeaslGHDr0N2AsWFVWyXEBjFY3KcFpWTzpN4+qx CC/g== X-Gm-Message-State: AHPjjUheedqNDHIMgYd4QL9ghHGQraNRO8U2yuG6Ze0chFDE5tpPLrnW X2w9Mqh9RAzSnkDlp+cyL1pvS7Ujgp1m X-Google-Smtp-Source: ADKCNb5glD8RRlPP+1I/l4GVJhWRiT5u4W+3HIyGxYuIr3AK1rajswGdhlbHTHRB9HzNQ4IzCv25sdDY8O1rd83ul1E= X-Received: by 10.107.186.69 with SMTP id k66mr2204768iof.189.1504451699662; Sun, 03 Sep 2017 08:14:59 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Sun, 3 Sep 2017 08:14:59 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:7467:6cd9:459e:8562] In-Reply-To: References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <3D731E17-CB4B-495E-8D9E-6614BD3D919E@ultra-secure.de> <20170902.174119.74668153.sthaug@nethelp.no> <02C1D059-24AD-4114-BBF6-ECB443DC49E1@longcount.org> <000101d324b3$a9c4a8a0$fd4df9e0$@ulka.com.au> <000201d324b5$2a72bf40$7f583dc0$@ulka.com.au> From: Warner Losh Date: Sun, 3 Sep 2017 09:14:59 -0600 X-Google-Sender-Auth: 5VBZHaOy6RTZJpZoEbKv-ffXK8I Message-ID: Subject: Re: HP Smart array P440 support To: Rainer Duffner Cc: Priyadarshana Chandrasena , Mark Saad , FreeBSD-STABLE Mailing List , sthaug@nethelp.no Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 15:15:01 -0000 On Sun, Sep 3, 2017 at 8:33 AM, Rainer Duffner wrote: > > > Am 03.09.2017 um 15:04 schrieb Priyadarshana Chandrasena < > vpc@ulka.com.au>: > > > > In UEFI mode the boot process does not read the installation media usb. > > Never booted from the usb in UEFI mode! > > > Hm. Interesting. > Can you try 11.1 then? > > I think I had that problem around the 9.x days, with G7 hardware. > Or I think it was with booting from the emulated CD via iLO. More recent boot1.efi's have better behavior. I'd be curious to know what doesn't work. Warner From owner-freebsd-stable@freebsd.org Sun Sep 3 19:19:18 2017 Return-Path: Delivered-To: freebsd-stable@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 2C232E1A60F for ; Sun, 3 Sep 2017 19:19:18 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo.suszko.eu (archeo.unixguru.pl [IPv6:2001:41d0:2:8316::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DBFDA7550B for ; Sun, 3 Sep 2017 19:19:17 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo (localhost [127.0.0.1]) by archeo.suszko.eu (Postfix) with ESMTP id 19828DA4; Sun, 3 Sep 2017 21:19:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at archeo.local Received: from archeo.suszko.eu ([127.0.0.1]) by archeo (archeo.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NF34ek3_qs0n; Sun, 3 Sep 2017 21:19:13 +0200 (CEST) Received: from leo (89-67-26-133.dynamic.chello.pl [89.67.26.133]) by archeo.suszko.eu (Postfix) with ESMTPSA id 855D2D9C; Sun, 3 Sep 2017 21:19:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=suszko.eu; s=dkim; t=1504466353; bh=QArakgpLgK4IiG0gqR83N58iN05aDLFImt4ek453My8=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=CFrFVvIcHFgHqTrJAqxqlQiD1RSDq6nQK7tsf2Lpk4N7QZq/2tcMcXDAr/8OHg75g lFq31xRiFF1pwmdrvoLTyr/H7meLPNX49t3i+IJWml4pdbhxQwRCItv/mHMlQztbMZ 89l2oGGPHHNwA3xHjTUULFH+DSde+xAbCihhvvn0= Date: Sun, 3 Sep 2017 21:19:08 +0200 From: Maciej Suszko To: "Priyadarshana Chandrasena" Cc: Subject: Re: HP Smart array P440 support Message-ID: <20170903211908.510b5724@leo> In-Reply-To: <001501d323f2$3e517560$baf46020$@ulka.com.au> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/tlRR0G3QhNC8BZxoza2AD_8"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Sep 2017 19:19:18 -0000 --Sig_/tlRR0G3QhNC8BZxoza2AD_8 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Priyadarshana Chandrasena" wrote: > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in > it. I have a HP smart array P440 in my server. I can not find out > anywhere if ciss driver support include HP Gen 9 storage > controllers. Could you please update the ciss driver in 10.3? Hi, Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). In a few days I plan to boot it in HBA mode, we'll see if it's working. A few messages: #v+ root@storage-04:~ # uname -a FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 2= 2 06:12:04 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src= /sys/GENERIC amd64 root@storage-04:~ # grep ciss /var/run/dmesg.boot ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cfffff,0= x92d00000-0x92d003ff at device 0.0 numa-domain 0 on pci2 ciss0: PERFORMANT Transport da2 at ciss0 bus 0 scbus2 target 0 lun 0 root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-3 SCSI device pass2: Serial Number PDNMF0ARH401MI =20 pass2: 135.168MB/s transfers, Command Queueing Enabled #v- --=20 regards, Maciej Suszko. --Sig_/tlRR0G3QhNC8BZxoza2AD_8 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRBv6xO7mzN+RcEaiUKKRSTSXuIagUCWaxVrQAKCRAKKRSTSXuI ag0yAJ9LEkXUhHKDzXZ0wZVg0gcfJe2wYwCfclb8G6RV0I5gTH3Ed1+oq2CVLiU= =5fZ4 -----END PGP SIGNATURE----- --Sig_/tlRR0G3QhNC8BZxoza2AD_8-- From owner-freebsd-stable@freebsd.org Mon Sep 4 01:11:25 2017 Return-Path: Delivered-To: freebsd-stable@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 1230AE05965 for ; Mon, 4 Sep 2017 01:11:25 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8515C8323D for ; Mon, 4 Sep 2017 01:11:23 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v841ArCM004499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Sep 2017 10:40:54 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Maciej Suszko'" Cc: References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> In-Reply-To: <20170903211908.510b5724@leo> Subject: RE: HP Smart array P440 support Date: Mon, 4 Sep 2017 10:40:11 +0930 Message-ID: <001c01d3251a$92d20090$b87601b0$@ulka.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gG9PdpuoPyTBnA= Content-Language: en-au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 01:11:25 -0000 I tried to install 11.1 but I still have the same error. UEFI boot mode does not see my usb bootable media as of type UEFI. So still the Legacy BIOS is the only option. Do I need to create the usb UEFI when I create the usb boot disk?. -----Original Message----- From: Maciej Suszko [mailto:maciej@suszko.eu] Sent: Monday, 4 September 2017 4:49 AM To: Priyadarshana Chandrasena Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support "Priyadarshana Chandrasena" wrote: > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. > I have a HP smart array P440 in my server. I can not find out anywhere > if ciss driver support include HP Gen 9 storage controllers. Could > you please update the ciss driver in 10.3? Hi, Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). In a few days I plan to boot it in HBA mode, we'll see if it's working. A few messages: #v+ root@storage-04:~ # uname -a FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:12:04 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 root@storage-04:~ # grep ciss /var/run/dmesg.boot ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 on pci2 ciss0: PERFORMANT Transport da2 at ciss0 bus 0 scbus2 target 0 lun 0 root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-3 SCSI device pass2: Serial Number PDNMF0ARH401MI pass2: 135.168MB/s transfers, Command Queueing Enabled #v- -- regards, Maciej Suszko. From owner-freebsd-stable@freebsd.org Mon Sep 4 01:13:35 2017 Return-Path: Delivered-To: freebsd-stable@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 22FA0E05E1A for ; Mon, 4 Sep 2017 01:13:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E51DD835EB for ; Mon, 4 Sep 2017 01:13:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id f99so15264446ioi.3 for ; Sun, 03 Sep 2017 18:13:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rm/YTM4KekRq9mJkaoCql7n2hzmHO5fgbCmS/W/0AUU=; b=KjdaFEwHyiX2gi249V4Z7pRh5sndJr7AOGIOYGWELtoHBUuzn+ajLjwkeizC/0KwOM 4mRh35pbZxuQqmjpCMG23+gYguNbBFhzHJHFTq4bwXaLRCu5MfPW1iwc5uKllNonNO1B j3Q5NLedTjmcCTHjQfHfe68gbEkNNP2Ijb7E9f4s5CnxiXyaAMScH6TEZla0sOFuYryX iLxJzuk7JGFrNlh9fCNZj4Jn1Oah52bC8C6grkfE0Y25VK3jjxGSMfQHlKDRJfFGYnaS Om47qsfS74RY17BkU+bdUrxc9bgyWjlxaU7WIBdwPtHBdAyZxXvee4AQ9mGJfyPrg7P2 s1uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rm/YTM4KekRq9mJkaoCql7n2hzmHO5fgbCmS/W/0AUU=; b=OYm1Gy/Z9sEoYJ/J1mKcnxN678Rd/yXek3a10cNSeFkG6eANR0fGQkyw9MHvgXAsJC jlAl7yNniAn5FHS6oJk0OxMxP0Gvno/GhJj1QzWAiAefEDdbK/84G80DX4O2RQSAD6Lt rHAwe966X5SlNZ2PwmX0qLGgrqucd0La4PfpWprmh3kc4J+/tu/bHoMzhdg+qFnEak2X 896MPndxFVtQjoC6hrAq01D4V3wowAwz3tSoiEZ3VMmzRcH1Gb1VjvVLGZ1GFOS1Avd7 DwgWGB33jNTp77ax9+EI+KMUW3diEyyFyDQ+AUbmeOmQd7/Nyct3bHrWmtoaZSmFEEmR T/TQ== X-Gm-Message-State: AHPjjUjT1OTbwDFPyOgE3xb+sw/FS0QwVH4WnDl0m6AB4Cn4Eo8UG8xS gFSeXugGEZ6/Vk1M7bIlGNfHOXNepgUy X-Google-Smtp-Source: ADKCNb54OoqGxynBf9Dml2l0R2bzym1eS4ve+Tb47yaILtFStvOLMv8987KNlim/II0kj+X96wxSfRFK2du2+sQ6hdI= X-Received: by 10.107.186.69 with SMTP id k66mr3107883iof.189.1504487614025; Sun, 03 Sep 2017 18:13:34 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Sun, 3 Sep 2017 18:13:33 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:7467:6cd9:459e:8562] In-Reply-To: <001c01d3251a$92d20090$b87601b0$@ulka.com.au> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> From: Warner Losh Date: Sun, 3 Sep 2017 19:13:33 -0600 X-Google-Sender-Auth: WKoy-tcWOyPJShL5ImxzaWKH0cs Message-ID: Subject: Re: HP Smart array P440 support To: Priyadarshana Chandrasena Cc: Maciej Suszko , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 01:13:35 -0000 Our UEFI stuff is designed so that the defaults will just work... I find it odd that your computer doesn't work with the defaults. IT's BIOS doesn't even consider the USB drive a bootable device? Warner On Sun, Sep 3, 2017 at 7:10 PM, Priyadarshana Chandrasena wrote: > I tried to install 11.1 but I still have the same error. UEFI boot mode > does > not see my usb bootable media as of type UEFI. So still the Legacy BIOS is > the only option. Do I need to create the usb UEFI when I create the usb > boot > disk?. > > -----Original Message----- > From: Maciej Suszko [mailto:maciej@suszko.eu] > Sent: Monday, 4 September 2017 4:49 AM > To: Priyadarshana Chandrasena > Cc: FreeBSD-stable@FreeBSD.org > Subject: Re: HP Smart array P440 support > > "Priyadarshana Chandrasena" wrote: > > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. > > I have a HP smart array P440 in my server. I can not find out anywhere > > if ciss driver support include HP Gen 9 storage controllers. Could > > you please update the ciss driver in 10.3? > > Hi, > > Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). > In a few days I plan to boot it in HBA mode, we'll see if it's working. > > A few messages: > #v+ > root@storage-04:~ # uname -a > FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb > 22 > 06:12:04 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > root@storage-04:~ # grep ciss /var/run/dmesg.boot > ciss0: port 0x2000-0x20ff mem > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 on > pci2 > ciss0: PERFORMANT Transport > da2 at ciss0 bus 0 scbus2 target 0 lun 0 > > root@storage-04:~ # camcontrol inquiry da2 > pass2: Fixed Direct Access SPC-3 SCSI device > pass2: Serial Number PDNMF0ARH401MI > pass2: 135.168MB/s transfers, Command Queueing Enabled > #v- > -- > regards, Maciej Suszko. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Mon Sep 4 01:17:43 2017 Return-Path: Delivered-To: freebsd-stable@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 169A1E061B8 for ; Mon, 4 Sep 2017 01:17:43 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55245837C5 for ; Mon, 4 Sep 2017 01:17:41 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v841HKmD004545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Sep 2017 10:47:20 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Warner Losh'" Cc: "'Maciej Suszko'" , "'FreeBSD-STABLE Mailing List'" References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> In-Reply-To: Subject: RE: HP Smart array P440 support Date: Mon, 4 Sep 2017 10:46:37 +0930 Message-ID: <002601d3251b$77eb9970$67c2cc50$@ulka.com.au> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gG9PdpuAcI+A+ACTCLhGaDcIlcg Content-Language: en-au Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 01:17:43 -0000 It is saying that missing bootable media and what is found is not UEFI.=20 =20 From: wlosh@bsdimp.com [mailto:wlosh@bsdimp.com] On Behalf Of Warner = Losh Sent: Monday, 4 September 2017 10:44 AM To: Priyadarshana Chandrasena Cc: Maciej Suszko; FreeBSD-STABLE Mailing List Subject: Re: HP Smart array P440 support =20 Our UEFI stuff is designed so that the defaults will just work... I find = it odd that your computer doesn't work with the defaults. IT's BIOS = doesn't even consider the USB drive a bootable device? =20 Warner =20 =20 On Sun, Sep 3, 2017 at 7:10 PM, Priyadarshana Chandrasena = wrote: I tried to install 11.1 but I still have the same error. UEFI boot mode = does not see my usb bootable media as of type UEFI. So still the Legacy BIOS = is the only option. Do I need to create the usb UEFI when I create the usb = boot disk?. -----Original Message----- From: Maciej Suszko [mailto:maciej@suszko.eu] Sent: Monday, 4 September 2017 4:49 AM To: Priyadarshana Chandrasena Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support "Priyadarshana Chandrasena" wrote: > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. > I have a HP smart array P440 in my server. I can not find out anywhere > if ciss driver support include HP Gen 9 storage controllers. Could > you please update the ciss driver in 10.3? Hi, Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). In a few days I plan to boot it in HBA mode, we'll see if it's working. A few messages: #v+ root@storage-04:~ # uname -a FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed = Feb 22 06:12:04 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 root@storage-04:~ # grep ciss /var/run/dmesg.boot ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 = on pci2 ciss0: PERFORMANT Transport da2 at ciss0 bus 0 scbus2 target 0 lun 0 root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-3 SCSI device pass2: Serial Number PDNMF0ARH401MI pass2: 135.168MB/s transfers, Command Queueing Enabled #v- -- regards, Maciej Suszko. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" =20 From owner-freebsd-stable@freebsd.org Mon Sep 4 02:55:42 2017 Return-Path: Delivered-To: freebsd-stable@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 C710DE0C0F3 for ; Mon, 4 Sep 2017 02:55:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A1401D19 for ; Mon, 4 Sep 2017 02:55:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id k189so12120821itk.0 for ; Sun, 03 Sep 2017 19:55:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=8b6qppVvnQO/W0wja5FpS6NZc6dEwfHPzKb8azd7JoY=; b=1fDLy39HXUEEJ5bC46YtGeGiG68CBMZK2xvdWcyEbHETbeJqYOr7rmpCFf/oQxniRp M+lXB4sx3bS+ronUCI7zFiWGzKGXfxarMVG9ptrWL9p8w3k9PmxQKa+5OwtHYYHtyxAS 0qVSkDNzS9yFlNUPkJC3LsLwwwth4BIrstrTGNp8+e5TgN2YfTbif0nfQQiQJul+NbED t23dY65kzC+75/8WEIa84tvzSzUSJKgwxxfgrrSeE7v8RB+DAZtICq5+3ZkqTXKufOfi rgE/D6zvS0Y7NAkEwGr+c4tyIasBRcEjShv1MDK0aFtkAuPyV01N1MELCjGFuCTOpST+ v9gA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=8b6qppVvnQO/W0wja5FpS6NZc6dEwfHPzKb8azd7JoY=; b=MDhF7G40PoHAcr9SnKmgICJ7hyqVn6MOBhLMM0D+6wdNbpX6sdg+xbKD79d6ONrR6J 4WdCcb08LL7k8lVCZVjKtecwY205znyHyxAWxjIX0J10kAzK+llTbVEKk0vvvgUNf+4x DUQI9twOKHC3QAB8cYl5iFWOLYcPhJPYwNm/JBxTu3PnjnlZakWD4+QyPsCGTxMWC651 jgq/JqXrVSyIfmLvBc/UPYeHMQOGsbmFgdz0Kd4nWpAnzaXCdnbzcrDT2TWLjJGSL7Vu +eoPzuvOLN298P9NKSGjL/XBXqv3rmFA8uKUvAFhfKOat8BuQgsfXo6faWS4aoU5J83L 44/w== X-Gm-Message-State: AHPjjUjeS+HDnLBg0tZn6W/KcfYrnYXLLEY3+mFKa9OTRGbIlK+SWzo+ Hf3RFvXdz9HI3CCnA6fh2jzUx2nbVRBu X-Google-Smtp-Source: ADKCNb48YMRsxY90MTu96FPaukpjxp5XACRMtFF+bGJnP6Y49auUvpobDiwoFYq/Dltrwkvx78s81pEwwy8n/Sj3QMI= X-Received: by 10.36.36.210 with SMTP id f201mr5018504ita.24.1504493741792; Sun, 03 Sep 2017 19:55:41 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Sun, 3 Sep 2017 19:55:41 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:7467:6cd9:459e:8562] In-Reply-To: <002601d3251b$77eb9970$67c2cc50$@ulka.com.au> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> <002601d3251b$77eb9970$67c2cc50$@ulka.com.au> From: Warner Losh Date: Sun, 3 Sep 2017 20:55:41 -0600 X-Google-Sender-Auth: ZpF5V4ndyIS0HeemYlncfDGN3Q0 Message-ID: Subject: Re: HP Smart array P440 support To: Priyadarshana Chandrasena Cc: Maciej Suszko , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 02:55:42 -0000 I maintain that it's wrong. However, to make progress, what version of the BIOS is it? What motherboard? What UEFI compliance does it claim? Warner On Sun, Sep 3, 2017 at 7:16 PM, Priyadarshana Chandrasena wrote: > It is saying that missing bootable media and what is found is not UEFI. > > > > *From:* wlosh@bsdimp.com [mailto:wlosh@bsdimp.com] *On Behalf Of *Warner > Losh > *Sent:* Monday, 4 September 2017 10:44 AM > *To:* Priyadarshana Chandrasena > *Cc:* Maciej Suszko; FreeBSD-STABLE Mailing List > > *Subject:* Re: HP Smart array P440 support > > > > Our UEFI stuff is designed so that the defaults will just work... I find > it odd that your computer doesn't work with the defaults. IT's BIOS doesn't > even consider the USB drive a bootable device? > > > > Warner > > > > > > On Sun, Sep 3, 2017 at 7:10 PM, Priyadarshana Chandrasena > wrote: > > I tried to install 11.1 but I still have the same error. UEFI boot mode > does > not see my usb bootable media as of type UEFI. So still the Legacy BIOS is > the only option. Do I need to create the usb UEFI when I create the usb > boot > disk?. > > -----Original Message----- > From: Maciej Suszko [mailto:maciej@suszko.eu] > Sent: Monday, 4 September 2017 4:49 AM > To: Priyadarshana Chandrasena > Cc: FreeBSD-stable@FreeBSD.org > Subject: Re: HP Smart array P440 support > > "Priyadarshana Chandrasena" wrote: > > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. > > I have a HP smart array P440 in my server. I can not find out anywhere > > if ciss driver support include HP Gen 9 storage controllers. Could > > you please update the ciss driver in 10.3? > > Hi, > > Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). > In a few days I plan to boot it in HBA mode, we'll see if it's working. > > A few messages: > #v+ > root@storage-04:~ # uname -a > FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb > 22 > 06:12:04 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > root@storage-04:~ # grep ciss /var/run/dmesg.boot > ciss0: port 0x2000-0x20ff mem > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 on > pci2 > ciss0: PERFORMANT Transport > da2 at ciss0 bus 0 scbus2 target 0 lun 0 > > root@storage-04:~ # camcontrol inquiry da2 > pass2: Fixed Direct Access SPC-3 SCSI device > pass2: Serial Number PDNMF0ARH401MI > pass2: 135.168MB/s transfers, Command Queueing Enabled > #v- > -- > regards, Maciej Suszko. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > From owner-freebsd-stable@freebsd.org Mon Sep 4 06:29:59 2017 Return-Path: Delivered-To: freebsd-stable@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 69A60E1715D for ; Mon, 4 Sep 2017 06:29:59 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo.suszko.eu (archeo.unixguru.pl [IPv6:2001:41d0:2:8316::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F92067261 for ; Mon, 4 Sep 2017 06:29:58 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo (localhost [127.0.0.1]) by archeo.suszko.eu (Postfix) with ESMTP id 1D08A6FB; Mon, 4 Sep 2017 08:29:56 +0200 (CEST) X-Virus-Scanned: amavisd-new at archeo.local Received: from archeo.suszko.eu ([127.0.0.1]) by archeo (archeo.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0nP9vumArt4Y; Mon, 4 Sep 2017 08:29:55 +0200 (CEST) Received: from helium (unknown [195.8.99.234]) by archeo.suszko.eu (Postfix) with ESMTPSA id 91C7D6F3; Mon, 4 Sep 2017 08:29:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=suszko.eu; s=dkim; t=1504506595; bh=PLA/ch80k2sEyAlBA+EVboCTIXMjMUDwU9Sf41pEnUk=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=LFcBSFjJJdydLY/JeP9WBkYFzQhX0qiOIX4YfWvWVqg9F8ioYBKuDYHpyi7o0QmGJ vHwsFZKitPZvLW98Zf18xFo1JeIpTYfKWSDNB0tWB7mmiNOx98Qe5BxIr0Q7QxasIq gzWnWAjkWdiy5fc/BSYvh/5Gm5NQYA09F85RR080= Date: Mon, 4 Sep 2017 08:29:47 +0200 From: Maciej Suszko To: "Priyadarshana Chandrasena" Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support Message-ID: <20170904082947.499c7bf0@helium> In-Reply-To: <001c01d3251a$92d20090$b87601b0$@ulka.com.au> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/03a7lt//RJbBagVFu=w17sf"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 06:29:59 -0000 --Sig_/03a7lt//RJbBagVFu=w17sf Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 4 Sep 2017 10:40:11 +0930 "Priyadarshana Chandrasena" wrote: > I tried to install 11.1 but I still have the same error. UEFI boot mode d= oes > not see my usb bootable media as of type UEFI. So still the Legacy BIOS is > the only option. Do I need to create the usb UEFI when I create the usb b= oot > disk?.=20 I don't remember how the OS was installed, but I'm sure I haven't used USB, probably used PXE or virtual CD using iLO. --=20 regards, Maciej Suszko. --Sig_/03a7lt//RJbBagVFu=w17sf Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRBv6xO7mzN+RcEaiUKKRSTSXuIagUCWazy2wAKCRAKKRSTSXuI atR/AJ4rdgoTY4X5hnx0t7bz9DxRMM5KkwCcC1FuqzIgQE2rPYiCdDD9hMf60J0= =P1KR -----END PGP SIGNATURE----- --Sig_/03a7lt//RJbBagVFu=w17sf-- From owner-freebsd-stable@freebsd.org Mon Sep 4 10:26:34 2017 Return-Path: Delivered-To: freebsd-stable@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 6A80DE21020 for ; Mon, 4 Sep 2017 10:26:34 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4p.cmail.yandex.net (forward4p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E43C6E495 for ; Mon, 4 Sep 2017 10:26:34 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [77.88.29.86]) by forward4p.cmail.yandex.net (Yandex) with ESMTP id B18BC20F5D; Mon, 4 Sep 2017 13:26:14 +0300 (MSK) Received: from smtp3p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3p.mail.yandex.net (Yandex) with ESMTP id 97B4E13201BC; Mon, 4 Sep 2017 13:25:43 +0300 (MSK) Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id UJF3kx6T9i-Pf2GkocA; Mon, 04 Sep 2017 13:25:42 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504520742; bh=HRgf4enSE8/35EC1xU/V3TW2UJ/n+itFiyhKCHNKOXw=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=hHROxjOrfS5qwsFzmFjeS2DzDX48p1LfIggqT3b8fyFm/gRgBJkSgmg2LlRbe8P6t ee3NW236iNddJmUHExNLfZqnBUkNy3C12JipuDJ7ZHEOoG4RDaPI5eZs0PYkG7+gm+ hk7+wxZGG3vhbzDjbF/d+jrUvh+g+rAW7zcpJ15o= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: SLAAC not working To: Greg Rivers , freebsd-stable@freebsd.org References: <1646645.UkMcyRZBVl@flake.tharned.org> <3078071.oYt2PD7K2Q@flake.tharned.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Mon, 4 Sep 2017 13:22:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <3078071.oYt2PD7K2Q@flake.tharned.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="hODA2IEjHugC8vGuaBSbW1tXjNtIkq26P" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 10:26:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --hODA2IEjHugC8vGuaBSbW1tXjNtIkq26P Content-Type: multipart/mixed; boundary="a5kUn0pqxP5qSPjBdjKBkXjq9cs8G0lfs"; protected-headers="v1" From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org Message-ID: Subject: Re: SLAAC not working References: <1646645.UkMcyRZBVl@flake.tharned.org> <3078071.oYt2PD7K2Q@flake.tharned.org> In-Reply-To: <3078071.oYt2PD7K2Q@flake.tharned.org> --a5kUn0pqxP5qSPjBdjKBkXjq9cs8G0lfs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 03.09.2017 09:20, Greg Rivers wrote: > Aside from ruling out the MTU option in the RAs as the cause, I've > made little progress on finding the problem. >=20 > Can anyone explain the use of net.inet6.icmp6.nd6_debug=3D1 for NDP > debugging? I get no log output at all. I just tried: # sysctl net.inet6.icmp6.nd6_debug=3D1 net.inet6.icmp6.nd6_debug: 0 -> 1 # ifconfig lagg0 inet6 fe80::1/64 # dmesg | tail lagg0: got interface identifier from itself lagg0: ifid: e6:a7:a0:ff:fe:8e:16:bf lagg0: starting DAD for fe80:4::e6a7:a0ff:fe8e:16bf lagg0: DAD complete for fe80:4::e6a7:a0ff:fe8e:16bf - no duplicates found= lagg0: starting DAD for fe80:4::1 lagg0: DAD detected duplicate IPv6 address fe80:4::1: NS in/out/loopback=3D0/1/0, NA in=3D1 lagg0: DAD complete for fe80:4::1 - duplicate found lagg0: manual intervention required As you can see, it works. --=20 WBR, Andrey V. Elsukov --a5kUn0pqxP5qSPjBdjKBkXjq9cs8G0lfs-- --hODA2IEjHugC8vGuaBSbW1tXjNtIkq26P Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmtKVkACgkQAcXqBBDI oXolzAf/az+FFBmtNmTIBBPpOu2x/qa88nNiNCGXy7WkeovCxh+OguadwtDQaiCN ZRu0aKPZmAU3pa16R97keswf0KbQUNIt8gd9tZTEL38Qd9ORj7LC+TLfwBYR1HNa tWsVYvAntf482ioUMqOZbemIUmJDbgALNs7wnfsUdt2ClCqPVkaajfwqffJSWjxG Bzt/qyIfhe75T1FdizAWJN1+e3pFOQ2PseHCNaC01DFZVqGXk1TT417SMyPAoOKD 179xoXKBTBXjHYHM8gBJo3GIjeiok9L8SFJDrtURt+EKeDWTz+7AqFr3dPbHHh+Y zW3vUOBDtLhgUGz6sork5ew3jUK/iw== =yzUv -----END PGP SIGNATURE----- --hODA2IEjHugC8vGuaBSbW1tXjNtIkq26P-- From owner-freebsd-stable@freebsd.org Mon Sep 4 12:28:22 2017 Return-Path: Delivered-To: freebsd-stable@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 86B0BE0486C for ; Mon, 4 Sep 2017 12:28:22 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D83271CDC for ; Mon, 4 Sep 2017 12:28:20 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v84CRsdB006004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 4 Sep 2017 21:57:55 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Warner Losh'" Cc: "'Maciej Suszko'" , "'FreeBSD-STABLE Mailing List'" References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> <002601d3251b$77eb9970$67c2cc50$@ulka.com.au> In-Reply-To: Subject: RE: HP Smart array P440 support Date: Mon, 4 Sep 2017 21:57:11 +0930 Message-ID: <004e01d32579$26351580$729f4080$@ulka.com.au> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gG9PdpuAcI+A+ACTCLhGQGpUHV1AfyWJJmgv6vzAA== Content-Language: en-au Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 12:28:22 -0000 The BIOS version is U22 v2.22 and the motherboard specification can not = be found. But the machine is 823562-B21.=20 When the boot mode is in UEFI the machine does not recognize a bootable = disk to boot from and it specifically ask for a UEFI boot disk. When the = boot mode is in Legacy mode I can boot from usb and external cd but = hangs the booting giving error : Mounting from = ufs:/dev/ufs/FreeBSD_Install failed with error 19. In legacy mode I = installed Ubuntu 16.4 from a USB. Ubuntu 16.4 does not boot from the usb = in UEFI mode. =20 =20 From: wlosh@bsdimp.com [mailto:wlosh@bsdimp.com] On Behalf Of Warner = Losh Sent: Monday, 4 September 2017 12:26 PM To: Priyadarshana Chandrasena Cc: Maciej Suszko; FreeBSD-STABLE Mailing List Subject: Re: HP Smart array P440 support =20 I maintain that it's wrong. =20 However, to make progress, what version of the BIOS is it? What = motherboard? What UEFI compliance does it claim? =20 Warner =20 On Sun, Sep 3, 2017 at 7:16 PM, Priyadarshana Chandrasena = wrote: It is saying that missing bootable media and what is found is not UEFI.=20 =20 From: wlosh@bsdimp.com [mailto:wlosh@bsdimp.com] On Behalf Of Warner = Losh Sent: Monday, 4 September 2017 10:44 AM To: Priyadarshana Chandrasena Cc: Maciej Suszko; FreeBSD-STABLE Mailing List Subject: Re: HP Smart array P440 support =20 Our UEFI stuff is designed so that the defaults will just work... I find = it odd that your computer doesn't work with the defaults. IT's BIOS = doesn't even consider the USB drive a bootable device? =20 Warner =20 =20 On Sun, Sep 3, 2017 at 7:10 PM, Priyadarshana Chandrasena = wrote: I tried to install 11.1 but I still have the same error. UEFI boot mode = does not see my usb bootable media as of type UEFI. So still the Legacy BIOS = is the only option. Do I need to create the usb UEFI when I create the usb = boot disk?. -----Original Message----- From: Maciej Suszko [mailto:maciej@suszko.eu] Sent: Monday, 4 September 2017 4:49 AM To: Priyadarshana Chandrasena Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support "Priyadarshana Chandrasena" wrote: > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it. > I have a HP smart array P440 in my server. I can not find out anywhere > if ciss driver support include HP Gen 9 storage controllers. Could > you please update the ciss driver in 10.3? Hi, Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). In a few days I plan to boot it in HBA mode, we'll see if it's working. A few messages: #v+ root@storage-04:~ # uname -a FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed = Feb 22 06:12:04 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 root@storage-04:~ # grep ciss /var/run/dmesg.boot ciss0: port 0x2000-0x20ff mem 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 = on pci2 ciss0: PERFORMANT Transport da2 at ciss0 bus 0 scbus2 target 0 lun 0 root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-3 SCSI device pass2: Serial Number PDNMF0ARH401MI pass2: 135.168MB/s transfers, Command Queueing Enabled #v- -- regards, Maciej Suszko. _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" =20 =20 From owner-freebsd-stable@freebsd.org Mon Sep 4 14:25:21 2017 Return-Path: Delivered-To: freebsd-stable@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 280E8E0A0C2 for ; Mon, 4 Sep 2017 14:25:21 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB2457580D for ; Mon, 4 Sep 2017 14:25:20 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dosJS-0007UY-6u for freebsd-stable@freebsd.org; Mon, 04 Sep 2017 14:25:18 +0000 Subject: Re: zfs, iSCSI and volmode=dev To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: <203bd4d2-8c12-620a-8d0c-5c76d279174c@ingresso.co.uk> Date: Mon, 4 Sep 2017 15:25:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 14:25:21 -0000 > I have an iSCSI production system that exports a large number of zvols > as the iSCSI targets. System is running FreeBSD 11.0-RELEASE-p7 and > initially all of the zvols were confugured with default volmode. I've > read that it's recommended to use them in dev mode, so the system isn't > bothered with all of these geom structures, so I've switched all of the > zvols to dev mode, then I exported/imported the pools back. > Surprisingly, the performance has fallen down like 10 times (200-300 > Mbits/sec against 3-4 Gbits/sec previously). After observing for 5 > minutes the ESXes trying to boot up, and doing this extremely slowly, I > switched the volmode back to default, then again exported/imported the > pools. The performance went back to normal. I too ghave a number of zvols exportes as iscsi, and I was using dev mode util I read this. AM going to experiment with switching back to default mode to see what happens. I also use dev mode for my virtualbox drives. Am going to try and test that too and see what I get. Interesting result though... -pete. From owner-freebsd-stable@freebsd.org Mon Sep 4 17:49:24 2017 Return-Path: Delivered-To: freebsd-stable@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 5F304E14324 for ; Mon, 4 Sep 2017 17:49:24 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B0BD7F9BA for ; Mon, 4 Sep 2017 17:49:24 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qt0-x22f.google.com with SMTP id q8so75819qtb.5 for ; Mon, 04 Sep 2017 10:49:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LhIHXkvukW++zQPb15+QEUjAhFbyTB6xWkK9qMFZJ44=; b=blOs/Z210ZHaPMYr09xgP+li8Sdtnkjo12llBrQf7a/ynoSjLbmOzlr8tMcpB6Wtu3 Zcu1ydBKgunuI2eulUoOrBw9LYLVwQ42sd0/03/GFinCbniR3a2aYtIbEkDEBtw3Toa8 0YIbqBSgBLjBE3TWzFnTPNS5SK0xQVwISwcTqULuIdtQiWxY1gVszrywvbcO0ArRNXMm PONvPE9/OydWvCwiapb7rreG6/2AhN1eDC22zDRVZ2b4I3MCnJwoJ5OUGvV4YpzpOTCQ koZdc/Prbt2slJX1XMl96lgpbc2xOXCUfA9K6FT2jiKBpAVmWMK2pCL3AngXOMKPNqIr nghA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LhIHXkvukW++zQPb15+QEUjAhFbyTB6xWkK9qMFZJ44=; b=t0RbwA3i7fpr1VzSuH19CZM7bPwj7JtY5a6FS7DLzyZZuIUoNnQnqEXkN6/UfJOwGG MGNRpqqgVs2/X0uBBINvJSiFNKlozs7xmOzZX9PzwEiMXhfjHPu0lQLrDJYDCLQhHEsa T535jO2X0QFKk6Tj8FhCyv9J2K+u599eRyYGfE3D4Cou+DDzUWpSdN49SOEsyysVNU0c qlNuuFotb56dd/WSt2BogXkCjG991Rrs5orr5i9FXCGdMWXsKbmVi7QAKM+g3Vw8fHi6 1GDq0Gdm2X1Ktx2Nl81vXD+EdNVDNCrqcJ4321CRUPFh1rtHWaHrpBSw6ns58Wqwln/0 O0sQ== X-Gm-Message-State: AHPjjUjiIfJ4OmTemDBUUy37FAHBjvxO3BNcLzQ10GqfVCerVt4zRIA3 DNRqxHhMe8UhJxnSxUgMeA== X-Google-Smtp-Source: ADKCNb6VEU/tSEPMDBXCuFHNIEam4m6lTmREAWK2EqCItyM7rBUkCfOnU0qt7Dc4dlY7NXmMRKu31w== X-Received: by 10.200.26.131 with SMTP id x3mr1741288qtj.119.1504547363079; Mon, 04 Sep 2017 10:49:23 -0700 (PDT) Received: from [25.229.132.232] (ool-d18c205a.dyn.optonline.net. [209.140.32.90]) by smtp.gmail.com with ESMTPSA id r48sm5334074qte.57.2017.09.04.10.49.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 04 Sep 2017 10:49:21 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: HP Smart array P440 support From: Mark Saad X-Mailer: iPhone Mail (14G60) In-Reply-To: <001c01d3251a$92d20090$b87601b0$@ulka.com.au> Date: Mon, 4 Sep 2017 13:49:20 -0400 Cc: Maciej Suszko , FreeBSD-stable@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <2FE93DAE-5EB3-460D-9E2E-296A8E7B47DC@longcount.org> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <001c01d3251a$92d20090$b87601b0$@ulka.com.au> To: Priyadarshana Chandrasena X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 17:49:24 -0000 Hello Have you tried to update the servers firmware using the hp spp or update t= ool . In the past with 9.3 and 10.0 I had boot issues until I updated the se= rvers firmware. I only have a ml10 with a p410 so I can't test much ; my jo= b also moved to dell about 2 years ago .=20 --- Mark Saad | nonesuch@longcount.org Sep 3, 2017, at 9:10 PM, Priyadarshana Chandrasena wrote= : >=20 > I tried to install 11.1 but I still have the same error. UEFI boot mode do= es > not see my usb bootable media as of type UEFI. So still the Legacy BIOS is= > the only option. Do I need to create the usb UEFI when I create the usb bo= ot > disk?.=20 >=20 > -----Original Message----- > From: Maciej Suszko [mailto:maciej@suszko.eu]=20 > Sent: Monday, 4 September 2017 4:49 AM > To: Priyadarshana Chandrasena > Cc: FreeBSD-stable@FreeBSD.org > Subject: Re: HP Smart array P440 support >=20 > "Priyadarshana Chandrasena" wrote: >> I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in it.=20= >> I have a HP smart array P440 in my server. I can not find out anywhere=20= >> if ciss driver support include HP Gen 9 storage controllers. Could=20 >> you please update the ciss driver in 10.3? >=20 > Hi, >=20 > Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). > In a few days I plan to boot it in HBA mode, we'll see if it's working. >=20 > A few messages: > #v+ > root@storage-04:~ # uname -a > FreeBSD storage-04.gr 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 2= 2 > 06:12:04 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > root@storage-04:~ # grep ciss /var/run/dmesg.boot > ciss0: port 0x2000-0x20ff mem > 0x92c00000-0x92cfffff,0x92d00000-0x92d003ff at device 0.0 numa-domain 0 on= > pci2 > ciss0: PERFORMANT Transport > da2 at ciss0 bus 0 scbus2 target 0 lun 0 >=20 > root@storage-04:~ # camcontrol inquiry da2 > pass2: Fixed Direct Access SPC-3 SCSI device > pass2: Serial Number PDNMF0ARH401MI > pass2: 135.168MB/s transfers, Command Queueing Enabled > #v- > -- > regards, Maciej Suszko. >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Mon Sep 4 21:20:13 2017 Return-Path: Delivered-To: freebsd-stable@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 25979E1F04D for ; Mon, 4 Sep 2017 21:20:13 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from roadkill.tharned.org (gcrivers-1-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E91162FE0 for ; Mon, 4 Sep 2017 21:20:12 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:c8de:be:be6f:9cb4]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id v84LK51x084523 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Sep 2017 16:20:11 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2017; t=1504560011; bh=UO+EeLltu+9KiZQzltBqALtHU7nYfiveXrM6XxbVn4k=; l=3791; h=From:To:Subject:Date:In-Reply-To:References; b=v8ESRNipbrbWxkQ+oKTAOWsLaqH1p3mYLz2R1K+dDtPsjKuFyFHx0rWsDYeo+SWhE pJbt80AUrKPD9B8VnEzuwFG4RCTScfYvUMPmKArF1ZEv3ZoJdj5WKhOb4JPhjLXOfF XPCeaLkoncply0HGw9cPK9QvVoQ8tdu6V4RLMjOOsey9ix/grQG3750VJown9fjMcV eN+pSXEm1uYdV7xsfXcHEbl9YSKLp4xhIK/FPRnlfke3eQMCPNU2bLaFh9KEsrA43k n7YooSPoMUOiJlEGl4Kg4e+72fjNlNs0Ycip/CKyBCMJosYdBxltJG8hkzUkSXTL7C huulwdp0T5Kcg== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:c8de:be:be6f:9cb4] claimed to be flake.tharned.org From: Greg Rivers To: "Andrey V. Elsukov" , freebsd-stable@freebsd.org Subject: Re: SLAAC not working Date: Mon, 04 Sep 2017 16:20:05 -0500 Message-ID: <16545541.lkKC6IFVDn@flake.tharned.org> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: References: <1646645.UkMcyRZBVl@flake.tharned.org> <3078071.oYt2PD7K2Q@flake.tharned.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Mon, 04 Sep 2017 16:20:11 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Sep 2017 21:20:13 -0000 On Monday, September 04, 2017 13:22:16 Andrey V. Elsukov wrote: > On 03.09.2017 09:20, Greg Rivers wrote: > > Aside from ruling out the MTU option in the RAs as the cause, I've > > made little progress on finding the problem. > > > > Can anyone explain the use of net.inet6.icmp6.nd6_debug=1 for NDP > > debugging? I get no log output at all. > > I just tried: > # sysctl net.inet6.icmp6.nd6_debug=1 > net.inet6.icmp6.nd6_debug: 0 -> 1 > # ifconfig lagg0 inet6 fe80::1/64 > # dmesg | tail > lagg0: got interface identifier from itself > lagg0: ifid: e6:a7:a0:ff:fe:8e:16:bf > lagg0: starting DAD for fe80:4::e6a7:a0ff:fe8e:16bf > lagg0: DAD complete for fe80:4::e6a7:a0ff:fe8e:16bf - no duplicates found > lagg0: starting DAD for fe80:4::1 > lagg0: DAD detected duplicate IPv6 address fe80:4::1: NS in/out/loopback=0/1/0, NA in=1 > lagg0: DAD complete for fe80:4::1 - duplicate found > lagg0: manual intervention required > > As you can see, it works. > Thanks. Trying your same experiment, I do get output for duplicate detection, though it doesn't include the interface identifier or a check for the auto generated link-local address (maybe you're running -CURRENT?): # ifconfig lagg0 inet6 fe80::8/64 # ifconfig lagg0 inet6 fe80::8/64 delete # dmesg | tail -2 lagg0: starting DAD for fe80:c::8 lagg0: DAD complete for fe80:c::8 - no duplicates found What puzzles me is that there are two Cisco routers on this network that each send RAs every ~10 minutes, yet nothing is ever logged on the host, and the RAs, which should trigger address auto-configuration, are completely ignored. tcpdump on the host sees the RAs arriving on the lagg0 interface, yet nothing ever happens. How can one troubleshoot an issue like this when the receipt and/or disposition of RAs are not logged? Also strange is the fact that pinging the source IP in the RAs (i.e. the router's link-local IP) fails without ever placing a packet on the wire: # tcpdump -e -tttt -i lagg0 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on lagg0, link-type EN10MB (Ethernet), capture size 262144 bytes 2017-09-04 13:48:10.663913 64:a0:e7:45:63:43 (oui Unknown) > 33:33:00:00:00:01 (oui Unknown), ethertype IPv6 (0x86dd), length 118: fe80:XXXX:XXXX:4013:23::2 > ff02::1: ICMP6, router advertisement, length 64 $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 ping6: UDP connect: Network is unreachable How can it be that the host can receive a RA from a router's link-local address, but otherwise thinks it's unreachable? No entries that contain either the router's source IP or MAC address ever appear in the NDP table: $ ndp -a Neighbor Linklayer Address Netif Expire S Flags fe80::ae16:2dff:fe1e:b880%lagg0 ac:16:2d:1e:b8:80 lagg0 permanent R SLAAC works fine on my home network, which naturally has a FreeBSD router running rtadvd(8). The only appreciable difference between the RAs sent by FreeBSD and the RAs sent by Cisco are the "Traffic Class" and "Differentiated Services Codepoint" in the IPv6 headers: Cisco -Internet Protocol Version 6, Src: fe80:XXXX:XXXX:4013:23::2, Dst: ff02::1 FreeBSD +Internet Protocol Version 6, Src: fe80::91:f7ff:fe8b:e900, Dst: ff02::1 @@ -27,2 +27,2 @@ - .... 1110 0000 .... .... .... .... .... = Traffic Class: 0xe0 (DSCP: CS7, ECN: Not-ECT) - .... 1110 00.. .... .... .... .... .... = Differentiated Services Codepoint: Class Selector 7 (56) + .... 0000 0000 .... .... .... .... .... = Traffic Class: 0x00 (DSCP: CS0, ECN: Not-ECT) + .... 0000 00.. .... .... .... .... .... = Differentiated Services Codepoint: Default (0) Could this be causing a problem? -- Greg Rivers From owner-freebsd-stable@freebsd.org Tue Sep 5 10:55:09 2017 Return-Path: Delivered-To: freebsd-stable@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 3A4A4E027A0 for ; Tue, 5 Sep 2017 10:55:09 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward103j.mail.yandex.net (forward103j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D175171CDB for ; Tue, 5 Sep 2017 10:55:08 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback13g.mail.yandex.net (mxback13g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:92]) by forward103j.mail.yandex.net (Yandex) with ESMTP id CBA3034C1697; Tue, 5 Sep 2017 13:55:02 +0300 (MSK) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [2a02:6b8:0:1a2d::25]) by mxback13g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 79Lh38TiHi-t2vefnQW; Tue, 05 Sep 2017 13:55:02 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504608902; bh=ViccMTSKbuG/ZS8VRlwo84Q763ti8JoTyoOANONQKKw=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=CFjU7hPSetP13NMrK1v7Bs4d9QCVt91Xvw+IcvrYHF7kpkf5NLgcq0NsszVjF9pfG FMTzh5j9Ifyct66pRL6hUA+O/BB8YHTjSpjyaRt6qv+d0hvHalOnX/lt6NmZgR8B2z R1QSQX07EUtKJNLI/xHeFWpyB0jeeQP5Z8HKRTCY= Received: by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id UciAmKzhBJ-t1eqLh9D; Tue, 05 Sep 2017 13:55:02 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504608902; bh=ViccMTSKbuG/ZS8VRlwo84Q763ti8JoTyoOANONQKKw=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=CFjU7hPSetP13NMrK1v7Bs4d9QCVt91Xvw+IcvrYHF7kpkf5NLgcq0NsszVjF9pfG FMTzh5j9Ifyct66pRL6hUA+O/BB8YHTjSpjyaRt6qv+d0hvHalOnX/lt6NmZgR8B2z R1QSQX07EUtKJNLI/xHeFWpyB0jeeQP5Z8HKRTCY= Authentication-Results: smtp1o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: SLAAC not working To: Greg Rivers , freebsd-stable@freebsd.org References: <1646645.UkMcyRZBVl@flake.tharned.org> <3078071.oYt2PD7K2Q@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> Date: Tue, 5 Sep 2017 13:51:32 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <16545541.lkKC6IFVDn@flake.tharned.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WnBkXtkm3BXLpF4gAqPHekiFLTfW4f9is" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 10:55:09 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WnBkXtkm3BXLpF4gAqPHekiFLTfW4f9is Content-Type: multipart/mixed; boundary="C109CfQVE3TMPM0Qhj6uGhAq2G50nVmAx"; protected-headers="v1" From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org Message-ID: <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> Subject: Re: SLAAC not working References: <1646645.UkMcyRZBVl@flake.tharned.org> <3078071.oYt2PD7K2Q@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> In-Reply-To: <16545541.lkKC6IFVDn@flake.tharned.org> --C109CfQVE3TMPM0Qhj6uGhAq2G50nVmAx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.09.2017 00:20, Greg Rivers wrote: > Thanks. Trying your same experiment, I do get output for duplicate dete= ction, though it doesn't include the interface identifier or a check for = the auto generated link-local address (maybe you're running -CURRENT?): Yes, it is CURRENT, but auto generated address is there because lagg0 did not have enabled IPv6 at beginning of test. > # ifconfig lagg0 inet6 fe80::8/64 > # ifconfig lagg0 inet6 fe80::8/64 delete > # dmesg | tail -2 > lagg0: starting DAD for fe80:c::8 > lagg0: DAD complete for fe80:c::8 - no duplicates found >=20 > What puzzles me is that there are two Cisco routers on this network tha= t each send RAs every ~10 minutes, yet nothing is ever logged on the host= , and the RAs, which should trigger address auto-configuration, are compl= etely ignored. You can try to use dtrace to detect that RA is received by IPv6 stack. # kldload dtraceall # dtrace -n 'fbt::nd6_ra_input:entry {m =3D (struct mbuf *)arg0; ip6 =3D= (struct ip6_hdr *)m->m_data; printf("RA from %s received on %s", inet_ntoa6(&ip6->ip6_src), stringof(m->m_pkthdr.rcvif->if_xname));}' It should produce the output like this: dtrace: description 'fbt::nd6_ra_input:entry ' matched 1 probe CPU ID FUNCTION:NAME 2 37912 nd6_ra_input:entry RA from fe80:1::92e2:baff:fe6a:c7c received on ix0 2 37912 nd6_ra_input:entry RA from fe80:1::92e2:baff:fe6a:c7c received on ix0 > $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 > ping6: UDP connect: Network is unreachable Hmm. Can you show the second word of address in this example? Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? --=20 WBR, Andrey V. Elsukov --C109CfQVE3TMPM0Qhj6uGhAq2G50nVmAx-- --WnBkXtkm3BXLpF4gAqPHekiFLTfW4f9is Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmugbQACgkQAcXqBBDI oXpeGQgAo3bx7JDUJiCUrXjLocLqOIeo5OiFkMxUpDTY6iAt0Xw41I/K14/LVURO r+fG3MBnib4NY8SbkkzaOLC8mFF8bVzOWEO52cLFkxFmE+9931oltLjzABFpC+CJ 6D4AuqA6Ziy1oqDP4520N3MIA8PXH2FNUAK326loTwlqcMmAGbCzJYP8Zr2hi2na ow33Y9Cta7bkXSE6IlMfLC5Cyp1S6yGd5Dr/arTKUcvKR8caNuvWnyj54lYRM4kg ZB0gxcTAnssPGZ9JeKJvUjIXEd/il+pyk4isz02MelqQ5rkUbGqqpv2sDYD+YRRn zOr5elhOs5SjDPkupCJezVWuvu9Hrg== =AIKX -----END PGP SIGNATURE----- --WnBkXtkm3BXLpF4gAqPHekiFLTfW4f9is-- From owner-freebsd-stable@freebsd.org Tue Sep 5 15:25:19 2017 Return-Path: Delivered-To: freebsd-stable@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 BE167E0E78D for ; Tue, 5 Sep 2017 15:25:19 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from roadkill.tharned.org (gcrivers-1-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 759EA82E11 for ; Tue, 5 Sep 2017 15:25:19 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:fcb7:e619:e59d:bac1]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id v85FPCOn093655 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Sep 2017 10:25:17 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2017; t=1504625117; bh=K8D/5QwFj+OcKlee7R7rHyUZ2SYXwPqBpDwQgR5ImKI=; l=5972; h=From:To:Subject:Date:In-Reply-To:References; b=FeQpdJ3+k6qbV6PzkV3HzApnO6v8wWGLdwlJ2dQ8k7VHfuJX7LM5C5PKNISOb2S+V X8AFeniZMrVcNXfGfAi+TT4zIzE1c/v+1hiUESuXjBrW0k7iQit123zOyvS6e/7SB9 KwzATsbDb9hzkQFwl5ToSBNgMfnfTpA8KAcH/budOb0ew9c3FwJp+q+IVSsV5+9twF R0YVdGNaBvbdlRCnrUg9QJ1UkXJ9XjWiiDvMumKNFsoioolXx2h85VofMHo9BgdnBO HC52HOqJ0WANKz0bOucx8JW2AHB2UX5CFaKKgTCdpMz1dTAHSBV+IqP0stbM63if7B w93LjQ9o5cY7g== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:fcb7:e619:e59d:bac1] claimed to be flake.tharned.org From: Greg Rivers To: "Andrey V. Elsukov" , freebsd-stable@freebsd.org Subject: Re: SLAAC not working Date: Tue, 05 Sep 2017 10:25:12 -0500 Message-ID: <1762879.zBQMMkUt4K@flake.tharned.org> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Tue, 05 Sep 2017 10:25:17 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 15:25:19 -0000 On Tuesday, September 05, 2017 13:51:32 Andrey V. Elsukov wrote: > You can try to use dtrace to detect that RA is received by IPv6 stack. > # kldload dtraceall > # dtrace -n 'fbt::nd6_ra_input:entry {m = (struct mbuf *)arg0; ip6 = > (struct ip6_hdr *)m->m_data; printf("RA from %s received on %s", > inet_ntoa6(&ip6->ip6_src), stringof(m->m_pkthdr.rcvif->if_xname));}' > > It should produce the output like this: > dtrace: description 'fbt::nd6_ra_input:entry ' matched 1 probe > CPU ID FUNCTION:NAME > 2 37912 nd6_ra_input:entry RA from > fe80:1::92e2:baff:fe6a:c7c received on ix0 > 2 37912 nd6_ra_input:entry RA from > fe80:1::92e2:baff:fe6a:c7c received on ix0 > Thank you Andrey! I started both dtrace and tcpdump, and then ran rtsol; here's the result: # rtsol -dD lagg0 checking if lagg0 is ready... lagg0 is ready set timer for lagg0 to 0s New timer is 0s timer expiration on lagg0, state = 1 send RS on lagg0, whose state is 2 set timer for lagg0 to 4s New timer is 4s timer expiration on lagg0, state = 2 send RS on lagg0, whose state is 2 set timer for lagg0 to 4s New timer is 4s timer expiration on lagg0, state = 2 send RS on lagg0, whose state is 2 set timer for lagg0 to 1s New timer is 1s timer expiration on lagg0, state = 2 No answer after sending 3 RSs stop timer for lagg0 there is no timer # tcpdump -tttt -i lagg0 ip6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on lagg0, link-type EN10MB (Ethernet), capture size 262144 bytes 2017-09-05 09:30:24.195501 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:24.195573 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:28.199198 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:28.199395 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:28.199724 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, router advertisement, length 64 2017-09-05 09:30:28.199729 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, router advertisement, length 64 2017-09-05 09:30:29.196133 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:29.196369 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:30.196234 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:30.196649 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:31.196341 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:31.196915 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:32.199683 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:32.199746 IP6 fe80::ae16:2dff:fe1e:b880 > ff02::2: ICMP6, router solicitation, length 16 2017-09-05 09:30:32.200289 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, router advertisement, length 64 2017-09-05 09:30:32.200597 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, router advertisement, length 64 2017-09-05 09:30:37.200331 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:37.212444 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:38.200407 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:38.212714 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:39.200517 IP6 fe80:XXXX:XXXX:4013:23::2 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 2017-09-05 09:30:39.213490 IP6 fe80:XXXX:XXXX:4013:23::3 > fe80::ae16:2dff:fe1e:b880: ICMP6, neighbor solicitation, who has fe80::ae16:2dff:fe1e:b880, length 32 ^C 22 packets captured 38215 packets received by filter 0 packets dropped by kernel # dtrace -n 'fbt::nd6_ra_input:entry {m = (struct mbuf *)arg0; ip6 = (struct ip6_hdr *)m->m_data; printf("RA from %s received on %s", inet_ntoa6(&ip6->ip6_src), stringof(m->m_pkthdr.rcvif->if_xname));}' dtrace: description 'fbt::nd6_ra_input:entry ' matched 1 probe ^C dtrace saw nothing, yet tcpdump recorded what one would expect. Apparently the inbound RAs and NSs are not making it through to the IPv6 stack. At this point I suspect a bug in the Emulex oce(4) driver, or a bad interaction between oce(4) and lagg(4). I have not seen this issue on hosts with lagg and other NICs. As soon as I can, I'm going to eliminate lagg and repeat the experiment while running on just one oce interface. I'll report back with results. > > $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 > > ping6: UDP connect: Network is unreachable > > Hmm. Can you show the second word of address in this example? > Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? > Correct, neither of the XXXX parts are zero; the :: part is at the end of the address: ...::2%lagg0. Sorry for the obfuscation, but policy at $WORK about company information on public lists is very strict. -- Greg Rivers From owner-freebsd-stable@freebsd.org Tue Sep 5 17:13:05 2017 Return-Path: Delivered-To: freebsd-stable@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 D39E4E13510 for ; Tue, 5 Sep 2017 17:13:05 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76AD375131 for ; Tue, 5 Sep 2017 17:13:05 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback8o.mail.yandex.net (mxback8o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::22]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 565395D8157E; Tue, 5 Sep 2017 20:12:51 +0300 (MSK) Received: from smtp3o.mail.yandex.net (smtp3o.mail.yandex.net [2a02:6b8:0:1a2d::27]) by mxback8o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 8JW3msPGXq-CoPKO4md; Tue, 05 Sep 2017 20:12:51 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504631571; bh=Y4npVe08gyJa28qIfceDCBkrTI5xjJV++a/DAC+acDA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Noo9G7V2dh457UROW7k4iBr7cl9hmqM6+YAIy71+q4OamdcR/ZIof/1VRBioGefTf BJKJNJZk+ZnWrdFBtM3mPqorkY4RHf4c+mLvno499sfw3y7adfafofmnjaQ5iTarlm DWun+JdPyA/4z/eL3BfqL1Umc4KhNH+e9gZSBHhQ= Received: by smtp3o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id xgb3kuiElG-CnEKDL0Z; Tue, 05 Sep 2017 20:12:49 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504631570; bh=Y4npVe08gyJa28qIfceDCBkrTI5xjJV++a/DAC+acDA=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=hP0HIVnnpO45Gyd5xQHw+ZpEnWRysXJNCi6/wLrnt6deT3+E1ki62MPO1wNVkyEg1 0OxCmppJZS1+HlCjwPTWUM/+nf8Z/u+n0xBt7u7+Sggqh4Sv5lHhxPwAoF1EQkpdYM n2kb6F1jTM3abkgPMNNBy9LSUFvXDMez4XTV6D7I= Authentication-Results: smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: SLAAC not working To: Greg Rivers , freebsd-stable@freebsd.org References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Date: Tue, 5 Sep 2017 20:09:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1762879.zBQMMkUt4K@flake.tharned.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 17:13:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx Content-Type: multipart/mixed; boundary="Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI"; protected-headers="v1" From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org Message-ID: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Subject: Re: SLAAC not working References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> In-Reply-To: <1762879.zBQMMkUt4K@flake.tharned.org> --Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.09.2017 18:25, Greg Rivers wrote: > dtrace saw nothing, yet tcpdump recorded what one would expect. Apparen= tly the inbound RAs and NSs are not making it through to the IPv6 stack. = At this point I suspect a bug in the Emulex oce(4) driver, or a bad inter= action between oce(4) and lagg(4). I have not seen this issue on hosts wi= th lagg and other NICs. As soon as I can, I'm going to eliminate lagg and= repeat the experiment while running on just one oce interface. I'll repo= rt back with results. >=20 >>> $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 >>> ping6: UDP connect: Network is unreachable >> >> Hmm. Can you show the second word of address in this example? >> Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? >> > Correct, neither of the XXXX parts are zero; the :: part is at the end = of the address: ...::2%lagg0. Sorry for the obfuscation, but policy at $W= ORK about company information on public lists is very strict. I think the problem is not with oce(4) driver. Unfortunately, your router uses IPv6 LLA that is not compatible with KAME based IPv6 stack that is used by all BSDs. The FreeBSD kernel internally uses special form of IPv6 addresses, that have IPv6 scope zone id embedded into second word of address. This problem was recently discussed here: https://mailarchive.ietf.org/arch/msg/ipv6/fuzpfBXJHeBfsEddMBtgIpGjKvk Some time ago I have patched the kernel to avoid use of this hack, but this was done for 9.3 kernel and currently I have no time to port patches to recent CURRENT. --=20 WBR, Andrey V. Elsukov --Fxum1ij6eOBdO3hS9orO6CMLWnp16tmiI-- --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmu2j8ACgkQAcXqBBDI oXqVxgf8CCzVpEVFMOQ4zpMh7sCP2AUc70ojW884+/Oq2tbB5NTOMtY19QtUc28K TX3spruzZKWa31xERAx0t2ZbTEfR3uNyCtH7uDqim8fPMV2rzcuhlQ9YdpyWFIWB 6+vnHwlQMoYv5wBK/lmlEfhb9RNxoEhO+YO9pfE8RDQR2sMH4mFYDYU/oveNdX04 UD55AQx9W/CS6Fn3b8AnoO2egr6KcubKd87yUaYvbI4EEuImBkTpRGLLHFLHfiCe 022UPoHoJVVhhuc1WyNjDUPd64Y4XqDynkbdgxur7Yf0pe6KJXox7f4Xw9bgXKYZ VGjF695hp0+QIMMGBBwhDYIdwNPrJQ== =xqv2 -----END PGP SIGNATURE----- --PJuSB0LrirJBUbOju2kT5mvMD1QOm5gOx-- From owner-freebsd-stable@freebsd.org Tue Sep 5 17:48:33 2017 Return-Path: Delivered-To: freebsd-stable@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 2C9F4E15418 for ; Tue, 5 Sep 2017 17:48:33 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward104o.mail.yandex.net (forward104o.mail.yandex.net [37.140.190.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 565C181030 for ; Tue, 5 Sep 2017 17:48:31 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback7j.mail.yandex.net (mxback7j.mail.yandex.net [IPv6:2a02:6b8:0:1619::110]) by forward104o.mail.yandex.net (Yandex) with ESMTP id 704752C810A4; Tue, 5 Sep 2017 20:48:21 +0300 (MSK) Received: from smtp1p.mail.yandex.net (smtp1p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:6]) by mxback7j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id t0oYrEyJeO-mLxOl0OY; Tue, 05 Sep 2017 20:48:21 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504633701; bh=DD3lATdA/Vex327nm+KbzE7aSM2USn7DS/+BrWhGcDY=; h=Subject:From:To:References:Message-ID:Date:In-Reply-To; b=HEmVdobNJerPBR/DUEF1ew4P+6XfCy4lw1+/N6ft2sza26Qwri9fqFjqSyF+7ORZN Z8i7xchefgH3eCLXA15vql38Eu7xIdlU0OKqOB8/ChjkiqfXhADK+xqJx8DJp8zNy0 kjy7p5bvhagrjF8kE/rdqsxBTJQfZ8OMP3jOs47Q= Received: by smtp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id cPljpFd9Q3-mKICI3S0; Tue, 05 Sep 2017 20:48:20 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1504633700; bh=DD3lATdA/Vex327nm+KbzE7aSM2USn7DS/+BrWhGcDY=; h=Subject:From:To:References:Message-ID:Date:In-Reply-To; b=FHyeQfqkPo7QwSTkqnaan3p5tZOpOYBa9Ihq+O7ojK/q36tvI1NmnrOhVgBi+AkmV TEE0/5gdZv8Q84+2T9MMdRB1TjWR7EVFRNOwVBMbjNAByHfdnPkQ+KOSOc/L/YP4qf p15ry3+uw9D4gNlThaqwjYyKHfZIbUUzc1w/dOOM= Authentication-Results: smtp1p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: SLAAC not working From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <49c7a517-3f20-3629-9aaa-eb96bd506753@yandex.ru> Date: Tue, 5 Sep 2017 20:44:49 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xNK2FMnUJhLMClImQrVrvtQiBdqIW8DB0" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 17:48:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xNK2FMnUJhLMClImQrVrvtQiBdqIW8DB0 Content-Type: multipart/mixed; boundary="KtHmautsIvmcIxpgo3eNMXmbghA0mmbLb"; protected-headers="v1" From: "Andrey V. Elsukov" To: Greg Rivers , freebsd-stable@freebsd.org Message-ID: <49c7a517-3f20-3629-9aaa-eb96bd506753@yandex.ru> Subject: Re: SLAAC not working References: <1646645.UkMcyRZBVl@flake.tharned.org> <16545541.lkKC6IFVDn@flake.tharned.org> <37bf1f27-0cdd-b5a9-7345-d16eb228c4cb@yandex.ru> <1762879.zBQMMkUt4K@flake.tharned.org> <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> In-Reply-To: <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> --KtHmautsIvmcIxpgo3eNMXmbghA0mmbLb Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05.09.2017 20:09, Andrey V. Elsukov wrote: >>>> $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 >>>> ping6: UDP connect: Network is unreachable >>> >>> Hmm. Can you show the second word of address in this example? >>> Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? >>> >> Correct, neither of the XXXX parts are zero; the :: part is at the end= of the address: ...::2%lagg0. Sorry for the obfuscation, but policy at $= WORK about company information on public lists is very strict. >=20 > I think the problem is not with oce(4) driver. > Unfortunately, your router uses IPv6 LLA that is not compatible with > KAME based IPv6 stack that is used by all BSDs. To be sure, you can check the output of # netstat -sp ip6 | grep 'scope rules' This counter will be incremented for each RA from this server. --=20 WBR, Andrey V. Elsukov --KtHmautsIvmcIxpgo3eNMXmbghA0mmbLb-- --xNK2FMnUJhLMClImQrVrvtQiBdqIW8DB0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlmu4pEACgkQAcXqBBDI oXpoUgf/U0EAYkF9HlVhaBc/2GVJt/jN1NGh09GRvlsV60oEkUk6WMDEDuADcHui qNm8Ku164q7misvWbLqAFKuYEKIvkaJrYltgGW37MRII/gbd1gXag7lJUQj17nGl +bAILcsUVSJ8xKkFF0I6oW46rJpehu1/vBFGpd5h3ByLy+zZtz/dfqLRR0hd2OoF 834odH0XoGwOxPX77ukDkNcDXQqvaNtxY0a/mD1uoy6ZdJyrUtaO9HivoLFyUZA1 ljdiBAo0Vg2gG9QO6xqNfzFypmrZiG3zDvCG0kSaSb+P+PlTsIFcuslrGHain1JW y3F6m5dF+Q4GEXwHRkE7HVtnhsDb3A== =uIe7 -----END PGP SIGNATURE----- --xNK2FMnUJhLMClImQrVrvtQiBdqIW8DB0-- From owner-freebsd-stable@freebsd.org Tue Sep 5 18:17:37 2017 Return-Path: Delivered-To: freebsd-stable@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 8CA79E1699A for ; Tue, 5 Sep 2017 18:17:37 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from roadkill.tharned.org (gcrivers-1-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:107f::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0223D2C4E for ; Tue, 5 Sep 2017 18:17:36 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from flake.tharned.org ([IPv6:2001:470:1f11:107f:fcb7:e619:e59d:bac1]) (authenticated bits=0) by roadkill.tharned.org (8.15.2/8.15.2) with ESMTPSA id v85IHTcC095418 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Sep 2017 13:17:35 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tharned.org; s=2017; t=1504635455; bh=1MHVTyBFoD2GXLSzdP/cDqpx7DudLNjXg9RFcqMuV8U=; l=2066; h=From:To:Subject:Date:In-Reply-To:References; b=xp6ycFpxyRKog79C2xa3fUhaPI4ag7z42Hzif6bA7kuFtOWRjeMV69iZKnHc01h+c IIdC9hBlfssMoNR+CvUpn3+0Z0RTodC7H1apLqUrgIQXZcZv0U5Mx5N0qXnqw5PMQ4 OLMNC9+1PbfatcvXQXM7LxhZn2wkxZmL06jFF9f2S4DFITxlESDXZLSegNInkwKMCN XB4VOgxt4MLgH/tC374IxT+u/jwEqontf+rrgAvTVvlwgW/Q8dBAVQjLLHz+VSTM59 g9xv06IgN/8xn5vaehos8GINePlTw48bdZJyrDdC5tlY+fyW0maSYTdOFPZh7tKZdr EReGiT+yCrbng== X-Authentication-Warning: roadkill.tharned.org: Host [IPv6:2001:470:1f11:107f:fcb7:e619:e59d:bac1] claimed to be flake.tharned.org From: Greg Rivers To: "Andrey V. Elsukov" , freebsd-stable@freebsd.org Subject: Re: SLAAC not working [solved] Date: Tue, 05 Sep 2017 13:17:29 -0500 Message-ID: <4592443.rsZxAkcZRt@flake.tharned.org> User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <49c7a517-3f20-3629-9aaa-eb96bd506753@yandex.ru> References: <1646645.UkMcyRZBVl@flake.tharned.org> <17a5889c-3a62-9028-c2d2-96c2b55695e3@yandex.ru> <49c7a517-3f20-3629-9aaa-eb96bd506753@yandex.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (roadkill.tharned.org [IPv6:2001:470:1f10:107f:0:0:0:2]); Tue, 05 Sep 2017 13:17:35 -0500 (CDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Sep 2017 18:17:37 -0000 On Tuesday, September 05, 2017 20:44:49 Andrey V. Elsukov wrote: > On 05.09.2017 20:09, Andrey V. Elsukov wrote: > >>>> $ ping6 fe80:XXXX:XXXX:4013:23::2%lagg0 > >>>> ping6: UDP connect: Network is unreachable > >>> > >>> Hmm. Can you show the second word of address in this example? > >>> Is it not zero? I.e. fe80:XXXX: is correct or you missed '::' part? > >>> > >> Correct, neither of the XXXX parts are zero; the :: part is at the end of the address: ...::2%lagg0. Sorry for the obfuscation, but policy at $WORK about company information on public lists is very strict. > > > > I think the problem is not with oce(4) driver. > > Unfortunately, your router uses IPv6 LLA that is not compatible with > > KAME based IPv6 stack that is used by all BSDs. > > To be sure, you can check the output of > # netstat -sp ip6 | grep 'scope rules' > This counter will be incremented for each RA from this server. > Indeed: # netstat -sp ip6 | grep 'scope rules' 63 packets that violated scope rules # rtsol -dD oce0 checking if oce0 is ready... oce0 is ready set timer for oce0 to 1s New timer is 1s timer expiration on oce0, state = 1 send RS on oce0, whose state is 2 set timer for oce0 to 4s New timer is 4s timer expiration on oce0, state = 2 send RS on oce0, whose state is 2 set timer for oce0 to 4s New timer is 4s timer expiration on oce0, state = 2 send RS on oce0, whose state is 2 set timer for oce0 to 1s New timer is 1s timer expiration on oce0, state = 2 No answer after sending 3 RSs stop timer for oce0 there is no timer # netstat -sp ip6 | grep 'scope rules' 73 packets that violated scope rules Looks like we've nailed it. The network engineering guys say that setting the LLA on the routers as they do is a Cisco convention. The value chosen reflects the /64 prefix being published in the RAs. I guess that makes it easy at a glance to see which prefix is in use on a given network. I'll see if I can get them to change it and report back. Thanks for your help! -- Greg Rivers From owner-freebsd-stable@freebsd.org Wed Sep 6 09:33:25 2017 Return-Path: Delivered-To: freebsd-stable@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 D87D1E1D2B1 for ; Wed, 6 Sep 2017 09:33:25 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [45.32.79.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A583C688AA for ; Wed, 6 Sep 2017 09:33:25 +0000 (UTC) (envelope-from paul.koch@akips.com) Date: Wed, 6 Sep 2017 19:33:09 +1000 From: Paul Koch To: freebsd-stable@freebsd.org Subject: 11.1 running on HyperV hn interface hangs Message-ID: <20170906193309.796c79ed@akips.com> Organization: AKIPS MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 09:33:26 -0000 No sure if -stable is the right mailing list for this one. We recently moved our software from 11.0-p9 to 11.1-p1, but looks like there is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) where the virtual hn0 interface hangs with the following kernel messages: hn0: on vmbus0 hn0: Ethernet address: 00:15:5d:31:21:0f hn0: link state changed to UP ... hn0: RXBUF ack retry hn0: RXBUF ack failed last message repeated 571 times It requires a restart of the HyperV VM. This is a customer production server (remote customer ~4000km away) running fairly critical monitoring software, so we needed to roll it back to 11.0-p9. We only have two customers running our software in HyperV, vs lots in VMware and a handful on physical hardware. 11.0-p9 has been very stable. Has anyone seen this problem before with 11.1 ? 11.1 is listed here https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-freebsd-virtual-machines-on-hyper-v Paul. -- Paul Koch | Founder | CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@freebsd.org Wed Sep 6 11:02:50 2017 Return-Path: Delivered-To: freebsd-stable@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 481C7E21191 for ; Wed, 6 Sep 2017 11:02:50 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D58AF80ED1 for ; Wed, 6 Sep 2017 11:02:49 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dpY6W-000GDE-1T for freebsd-stable@freebsd.org; Wed, 06 Sep 2017 11:02:44 +0000 Subject: Re: 11.1 running on HyperV hn interface hangs To: freebsd-stable@freebsd.org References: <20170906193309.796c79ed@akips.com> From: Pete French Message-ID: <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> Date: Wed, 6 Sep 2017 12:02:43 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170906193309.796c79ed@akips.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 11:02:50 -0000 > We recently moved our software from 11.0-p9 to 11.1-p1, but looks like there > is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) where > the virtual hn0 interface hangs with the following kernel messages: > > hn0: on vmbus0 > hn0: Ethernet address: 00:15:5d:31:21:0f > hn0: link state changed to UP > ... > hn0: RXBUF ack retry > hn0: RXBUF ack failed > last message repeated 571 times > > It requires a restart of the HyperV VM. > > This is a customer production server (remote customer ~4000km away) running > fairly critical monitoring software, so we needed to roll it back to 11.0-p9. > We only have two customers running our software in HyperV, vs lots in VMware > and a handful on physical hardware. > > 11.0-p9 has been very stable. Has anyone seen this problem before with 11.1 ? I don't run anything on local hyper-v anymore, but I do run a ot of stuff in Azure, and we havent seen anything like this. I track STABLE for things though, updating after reading the commits and testing locally for a week or so, so the version I am running currently is r320175, which was part of 11.1-BETA2. I am going to upgrade to a more recent STABLE sometime this weke or next though, will do that on a test amchine and let you now how it goes. I seem to recall that there were some large changes to the hn code in August to add virtual function support. When does 11.1-p1 date from ? -pete. From owner-freebsd-stable@freebsd.org Wed Sep 6 11:08:44 2017 Return-Path: Delivered-To: freebsd-stable@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 BE44DE2157F for ; Wed, 6 Sep 2017 11:08:44 +0000 (UTC) (envelope-from paul.koch137@gmail.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3604D823BE for ; Wed, 6 Sep 2017 11:08:44 +0000 (UTC) (envelope-from paul.koch137@gmail.com) Received: by mail-io0-x22c.google.com with SMTP id q64so23098252iod.5 for ; Wed, 06 Sep 2017 04:08:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=7HqNh0aAvClNalcaQQN3DdRV+FF+TDLxA5Nyz2vZz6g=; b=Sl5ta0L2UUEtYVJsBEH4fMFKEocq9jbe8/3iVkVgIFHGNBFNhscpNpTv19XP1SdO0j DmbD5Y3I+MqCZ3sf7gODCMCXWUbJca1zvHgeBttotlZqnxy0snU0duWXzxF9IMuNJ/hZ 4EzoJKEa6KUh67jnoq4eIwx+iKkZFiv+UHzYghOpX4/WGKZMCy0nLc7VPLDtF3vMvViu aGrLJhj3TlZfocAW7KFHAgPvVN3NTNL2tMIZU/J1ANFPM0ZmaHnDBmIQFrqEMzvcsrZm hgq9gzJE/RpG7xELRRBQZK0W9Xxk+dQWm9Qus/Eq0ljKTmuVprCHjKakN4vVQkiE/jxX 07oQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=7HqNh0aAvClNalcaQQN3DdRV+FF+TDLxA5Nyz2vZz6g=; b=Rt6AnzREGOZxfnXh38B9pT1zmB9OVo0/8aX5rqpUtmnrz8gYKjDttxubh0arLGyBn2 MQ7kOGcnN08Cr9bHBxMHRbFCS6nzh/o8q1WeGZYQp26zoXhpBouAH5NW8Gy/0RMsTdRf vzWNmKev6uLSgks5vn05qzfwROCSlljAw8x9xiBGJPfjtZeUA+xio9qrRIOusuMl0me3 7PwsxIZvDIc3UExNj2SqFqCDUBUVfSREDO6Izurfibu17dXE/VHnZZBYMMjDxLNm8JbT vqNSN88f7tcrACdPRIJm5UvfppbtqP1lR/ik19xTVxaxAgoCYFKIIM5ZSLsPps7saie1 YhRw== X-Gm-Message-State: AHPjjUiDzneCKo6Xvf7IeYvcdaJqPzqCSGG4lM+xhRWQmqH/XoDV3hFw MXcvXVMuAuLFfDJc X-Google-Smtp-Source: AOwi7QAf1cd8Y/BoXg/Uxozlk33V1jjj1IWi+mPFEc0xu69KLrmsrxENnEKUQzbRdTX/KXK27Bt9Kg== X-Received: by 10.107.170.36 with SMTP id t36mr2277117ioe.327.1504696123420; Wed, 06 Sep 2017 04:08:43 -0700 (PDT) Received: from splash.akips.com (CPE-120-146-191-2.static.qld.bigpond.net.au. [120.146.191.2]) by smtp.gmail.com with ESMTPSA id q18sm1406285ioe.55.2017.09.06.04.08.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Sep 2017 04:08:42 -0700 (PDT) Date: Wed, 6 Sep 2017 21:08:29 +1000 From: Paul Koch To: Pete French Cc: freebsd-stable@freebsd.org Subject: Re: 11.1 running on HyperV hn interface hangs Message-ID: <20170906210830.469cbd38@splash.akips.com> In-Reply-To: <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 11:08:44 -0000 On Wed, 6 Sep 2017 12:02:43 +0100 Pete French wrote: > > We recently moved our software from 11.0-p9 to 11.1-p1, but looks like > > there is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 > > R2) where the virtual hn0 interface hangs with the following kernel > > messages: > > > > hn0: on vmbus0 > > hn0: Ethernet address: 00:15:5d:31:21:0f > > hn0: link state changed to UP > > ... > > hn0: RXBUF ack retry > > hn0: RXBUF ack failed > > last message repeated 571 times > > > > It requires a restart of the HyperV VM. > > > > This is a customer production server (remote customer ~4000km away) > > running fairly critical monitoring software, so we needed to roll it back > > to 11.0-p9. We only have two customers running our software in HyperV, vs > > lots in VMware and a handful on physical hardware. > > > > 11.0-p9 has been very stable. Has anyone seen this problem before with > > 11.1 ? > > > I don't run anything on local hyper-v anymore, but I do run a ot of > stuff in Azure, and we havent seen anything like this. I track STABLE > for things though, updating after reading the commits and testing > locally for a week or so, so the version I am running currently is > r320175, which was part of 11.1-BETA2. I am going to upgrade to a more > recent STABLE sometime this weke or next though, will do that on a test > amchine and let you now how it goes. > > I seem to recall that there were some large changes to the hn code in > August to add virtual function support. When does 11.1-p1 date from ? Looks like 2017-08-10 Paul. From owner-freebsd-stable@freebsd.org Wed Sep 6 15:23:52 2017 Return-Path: Delivered-To: freebsd-stable@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 A0C73E07C38 for ; Wed, 6 Sep 2017 15:23:52 +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 2885075772; Wed, 6 Sep 2017 15:23:51 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (125-209-132-171.dyn.iinet.net.au [125.209.132.171]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id v86FNbWB088118 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 6 Sep 2017 08:23:42 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: 11.1 running on HyperV hn interface hangs To: freebsd-stable@freebsd.org, paul.koch137@gmail.com References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> Cc: Sepherosa Ziehau , Hongjiang Zhang From: Julian Elischer Message-ID: <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> Date: Wed, 6 Sep 2017 23:23:32 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 15:23:53 -0000 On 6/9/17 7:02 pm, Pete French wrote: >> We recently moved our software from 11.0-p9 to 11.1-p1, but looks >> like there >> is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 >> R2) where >> the virtual hn0 interface hangs with the following kernel messages: >> >>   hn0: on vmbus0 >>   hn0: Ethernet address: 00:15:5d:31:21:0f >>   hn0: link state changed to UP >>   ... >>   hn0: RXBUF ack retry >>   hn0: RXBUF ack failed >>   last message repeated 571 times >> >> It requires a restart of the HyperV VM. >> >> This is a customer production server (remote customer ~4000km away) >> running >> fairly critical monitoring software, so we needed to roll it back >> to 11.0-p9. >> We only have two customers running our software in HyperV, vs lots >> in VMware >> and a handful on physical hardware. >> >> 11.0-p9 has been very stable.  Has anyone seen this problem before >> with 11.1 ? > > > I don't run anything on local hyper-v anymore, but I do run a ot of > stuff in Azure, and we havent seen anything like this. I track > STABLE for things though, updating after reading the commits and > testing locally for a week or so, so the version I am running > currently is r320175, which was part of 11.1-BETA2. I am going to > upgrade to a more recent STABLE sometime this weke or next though, > will do that on a test amchine and let you now how it goes. > > I seem to recall that there were some large changes to the hn code > in August to add virtual function support. When does 11.1-p1 date > from ? make sure you contact the FreeBSD/Microsoft guys.  Very responsive.. don't know if they watch -stable.. I'll cc a couple.. > > -pete. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Wed Sep 6 16:00:42 2017 Return-Path: Delivered-To: freebsd-stable@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 2D514E0994F for ; Wed, 6 Sep 2017 16:00:42 +0000 (UTC) (envelope-from cheryl.weston@anycontactsolution.com) Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0113.outbound.protection.outlook.com [104.47.100.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 340CA815DE for ; Wed, 6 Sep 2017 16:00:40 +0000 (UTC) (envelope-from cheryl.weston@anycontactsolution.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT2930127.onmicrosoft.com; s=selector1-anycontactsolution-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2l1lF9TvMTpO6u5JtztIY5C/+6Kk0FoDI9uDMz6br88=; b=YPqMp3k21K6RCpCxheYfjS7NOi/lF4jhM+Edur6jomK2ToJlHLGjP8hdSikidujaaez7K+jgQ0CB3f+ff2E+3beJfXtIDmYivMdkVJxOPghVkkcmESzrn6YWde0YTtY6J0mARLsXqkxuzANxe/1SF6aeAmL10q7/F3/+HE84Ok0= Received: from PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM (10.174.147.8) by PN1PR01MB0768.INDPRD01.PROD.OUTLOOK.COM (10.174.146.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.13.10; Wed, 6 Sep 2017 16:00:37 +0000 Received: from PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM ([10.174.147.8]) by PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM ([10.174.147.8]) with mapi id 15.20.0013.018; Wed, 6 Sep 2017 16:00:37 +0000 From: Cheryl Weston To: "freebsd-stable@freebsd.org" Subject: AWS and Cloud Service Providers Contact List Thread-Topic: AWS and Cloud Service Providers Contact List Thread-Index: AdMnKExJrBioaI8TSxSM5rb9Ryms1w== Date: Wed, 6 Sep 2017 15:56:28 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=cheryl.weston@anycontactsolution.com; x-originating-ip: [103.92.101.25] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; PN1PR01MB0768; 6:rHjZhjGzpW+dAfds5mvQ1hsAnv91+CzGi62revXeDverlHbvw5WK/fKmr6QU1/ISZ5Yz/oF4QlcGMjcDE3oHpvafM6XH1x0nt+hVNHiIR8BdNfapETefca+BSo+CRewT7cW5h0Q0g7LYhonMsWnScXp+AASzxUyBiriF1p+nOkjWXLlLIFJyeo7bR4dfhoAuTIXlDoNyXyGdPFXZRNMRk5gAIc+gDGrJnAELnGbDT+QVDwewvBqX2UofMdY1fytQyiiMDVXkezD6eadaM+py2QER/PpcuwW1/OYu0h8ICWCag8kZW9X+zOy/c10kS9HM5MDeCxchKB4RqDfKHTjYpQ==; 5:C9Uj4qNjkvU/X3h4f/jWlorFI4ys3lvTvhHibPiriUHt2+yf/uhSlDZf1jVl8v/j6O+tgN4q1IPgY9W2OMfAmW/SzQVrj3apMe5gdJ5cZOkuuN+t5msNlW1J4CCiDQ9skzKFQ4wVUTokCiSeyRa8QQ==; 24:0jT4E99znd6/ftD1Y7yHbt1j7Sgc9T0FlTBMPJGuc8rjTE/vRbZM/jYQ1jGUVnew7OOLE+/znqIo2gpShZEHDb/NkhHsgVC/Jb1rxajWBJU=; 7:9EHlRdC55rHw/TBM0pp+ESjANLmcFqGkl9V4e7VxMbEDq9rseBNpiHfkrkQRUwL6sdcuIIYy0EybkAPtYK/J6UxnBtYx3E5elRKpf0D5G9V4KwldNizyfzfVulH9Rx1AcG7SOpEp+K8buxh+Cxc8xaYKmHuRIZm/W9cVJw+puIKXOHK2PkA1oYBts5354m297GBVNC1gDnEwXHO0qIkV1aGIhZCAnHIDuc8Jz09X8sQ= x-ms-office365-filtering-correlation-id: 6cc8c79e-c745-4826-6323-08d4f5406a24 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:PN1PR01MB0768; x-ms-traffictypediagnostic: PN1PR01MB0768: x-exchange-antispam-report-test: UriScan:(21748063052155); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6041248)(201703131423075)(201703061421075)(20161123560025)(20161123564025)(20161123562025)(20161123558100)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:PN1PR01MB0768; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PN1PR01MB0768; x-forefront-prvs: 0422860ED4 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(151974002)(199003)(189002)(7736002)(66066001)(54896002)(6306002)(110136004)(25786009)(74316002)(33656002)(53936002)(223583001)(14454004)(81156014)(7696004)(3846002)(5640700003)(102836003)(81166006)(55016002)(508600001)(8936002)(45080400002)(189998001)(8676002)(6116002)(5660300001)(9326002)(9686003)(50986999)(6436002)(54356999)(97736004)(3280700002)(2351001)(68736007)(6506006)(2501003)(3660700001)(101416001)(2900100001)(106356001)(77096006)(86362001)(2906002)(6916009)(105586002)(6666003)(64060200001)(26710200004); DIR:OUT; SFP:1102; SCL:1; SRVR:PN1PR01MB0768; H:PN1PR01MB0879.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: anycontactsolution.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: anycontactsolution.com X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2017 15:56:28.7621 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 1f7cdfaf-0ac2-432e-8c8f-91e5c3f7b2fb X-MS-Exchange-Transport-CrossTenantHeadersStamped: PN1PR01MB0768 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 16:00:42 -0000 Hi, Are you looking to acquire the updated and verified Amazon web services - C= loud Service Users Email List in excel sheet for unlimited usage? You may also be interested in the database of: Citrix Cloud, Google Cloud, = IBM Cloud, Salesforce Cloud, Microsoft Cloud, Rackspace Cloud, VMware Cloud= , NetApp Cloud, HPE Cloud and more Please review and let me know your interest if you are looking for above me= ntioned users list or other technology users list for your campaigns. Kindly let us know you're interested to provide you with detailed informati= on. Thanks, Cheryl Weston to remove from this mailing: reply with subject line as "Unsubscribe" From owner-freebsd-stable@freebsd.org Wed Sep 6 21:46:56 2017 Return-Path: Delivered-To: freebsd-stable@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 290CAE18FD7 for ; Wed, 6 Sep 2017 21:46:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-90.reflexion.net [208.70.210.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82DB667DBC for ; Wed, 6 Sep 2017 21:46:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29103 invoked from network); 6 Sep 2017 21:46:48 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 6 Sep 2017 21:46:48 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Wed, 06 Sep 2017 17:46:48 -0400 (EDT) Received: (qmail 27528 invoked from network); 6 Sep 2017 21:46:48 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 6 Sep 2017 21:46:48 -0000 Received: from [192.168.1.109] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 81915EC8FF9; Wed, 6 Sep 2017 14:46:47 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: 11.1 running on HyperV hn interface hangs Message-Id: Date: Wed, 6 Sep 2017 14:46:46 -0700 To: paul.koch@akips.com, FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 21:46:56 -0000 Paul Koch paul.koch at akips.com wrote on Wed Sep 6 09:33:26 UTC 2017 : > We recently moved our software from 11.0-p9 to 11.1-p1, but looks like = there > is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) = where > the virtual hn0 interface hangs with the following kernel messages: >=20 > hn0: on vmbus0 > hn0: Ethernet address: 00:15:5d:31:21:0f > hn0: link state changed to UP > ... > hn0: RXBUF ack retry > hn0: RXBUF ack failed > last message repeated 571 times >=20 > . . . >=20 > Has anyone seen this problem before with 11.1 ? While it is/was a personal use/experiment I have used all the following under Windows 10 Pro's Hyper-V with networking via hn0 Ethernet as seen from the guest FreeBSD: releng/11.1 (no longer around to remind me of the most recent -r?????? but various updates ) stable/11 (various updates, -r320807 currently) head (various updates, -r323147 currently) I had no problems with my use. (By no means a traffic match to your context but definitely used.) In all cases the Virtual Switch Manager was tied to the (builtin) "External network" that is listed as: Intel(R) I211 Gigabit Network Connection in the Virtual Switch Properties pop-up for External network. The machine is not a server. So not totally broken as far as I can tell. Something more specific to your context would seem to also be involved. Hyper-V has worked nicely for assigning 14 of the machine's 16 hardware threads to FreeBSD and doing buildworld buildkernel and poudriere based port builds. (Windows 10 Pro not being otherwise busy.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-stable@freebsd.org Thu Sep 7 02:22:43 2017 Return-Path: Delivered-To: freebsd-stable@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 C19E1E0000D for ; Thu, 7 Sep 2017 02:22:43 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDF913EF7; Thu, 7 Sep 2017 02:22:42 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id z143so23984807qkb.3; Wed, 06 Sep 2017 19:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=SwaOEFFdQ51OTqezjWjZwTHU/rGgoPFDtui4omi3j2M=; b=mX0IALZEpNSlzFj6iG1rI+HMm2OPXcF6OShQnPZX/rT59ySMVDsO3UbzpsziIHATfr MJGo970/ucH7PGH2kGnfgcjOZoxZR3kDryfEHUZE69780zKczKveCJbz8S06rTpyXlHr cTomLTTu/gIXi6tp2ItPfoykjTiPjvtVMzJ0tmLfQfKmCqWK+DJmdrg0CNT32TxIX3fF SdBQs1w2C+o62Emt78jkKF4cK/s+aaavdzVuzW/Cvh9slgLZCHtXFIfJiuYnkN8gbr4l uVbOc6s5qo/uXtb6kRxpOhzX6zay4MGBc8HCl/chtVUWFWCzUXd79yPvml+syQpeKN01 d6Kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=SwaOEFFdQ51OTqezjWjZwTHU/rGgoPFDtui4omi3j2M=; b=dcO7mygc/QCxGl3G+i6vUmVQJU07VJXh+s5vXZ8+QgSukl57q0/3pjpD/w7N9WvhH1 pczuEIgaFlwxsswzyv+ph4Q2+D4wkdiury+Nv0LvWp80PSImyRij8TTAJ4rvvTbogmZD qjUDyxDR3eZ6BwnG0AR+bLPIjsTkH6tVOYDIEuPvI61xgqNFqH8yUlq/8gTTTJlJ5Z26 Sp5jcdxpbSOWhhBiGBshcUNlIQiIBcD69GaFEC4bowD/Ga1V9XJ0FokZDXcRu1qu2Egr BRxBFh0PFfGLLnGSZMpUJrmrJwsNlAyW0oJXdq+6/np7aAn5HnicZ4UfudfthEUZ+DjO Cilg== X-Gm-Message-State: AHPjjUhuVLnJOorG77I6cif9Ez6YmdGT6ZXNFqCj16QxcgZUFfX0aSHy hZL/Dpns852i5GgV1EPe4MBYNNSBHnev X-Google-Smtp-Source: ADKCNb4g6ZnvBlYVfpEJy5VYXqaXH/oB5f/5TtrbXp74epojzAVC8/1cPPlXc/E8aebqCt6qQCip3E8wObSjtbwe56A= X-Received: by 10.55.167.144 with SMTP id q138mr1607704qke.74.1504750961434; Wed, 06 Sep 2017 19:22:41 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.106.102 with HTTP; Wed, 6 Sep 2017 19:22:40 -0700 (PDT) In-Reply-To: <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> From: Sepherosa Ziehau Date: Thu, 7 Sep 2017 10:22:40 +0800 X-Google-Sender-Auth: PPEpCA14CrmF5KmwmqnA-YJppIc Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Julian Elischer Cc: freebsd-stable@freebsd.org, paul.koch137@gmail.com, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 02:22:43 -0000 Is it possible to tell me your workload? e.g. TX heavy or RX heavy. Enabled TSO or not. Details like how the send syscalls are issue will be interesting. And your Windows version, include the patch level, etc. Please try the following patch: https://people.freebsd.org/~sephe/hn_dec_txdesc.diff Thanks, sephe On Wed, Sep 6, 2017 at 11:23 PM, Julian Elischer wrote: > On 6/9/17 7:02 pm, Pete French wrote: >>> >>> We recently moved our software from 11.0-p9 to 11.1-p1, but looks like >>> there >>> is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) >>> where >>> the virtual hn0 interface hangs with the following kernel messages: >>> >>> hn0: on vmbus0 >>> hn0: Ethernet address: 00:15:5d:31:21:0f >>> hn0: link state changed to UP >>> ... >>> hn0: RXBUF ack retry >>> hn0: RXBUF ack failed >>> last message repeated 571 times >>> >>> It requires a restart of the HyperV VM. >>> >>> This is a customer production server (remote customer ~4000km away) >>> running >>> fairly critical monitoring software, so we needed to roll it back to >>> 11.0-p9. >>> We only have two customers running our software in HyperV, vs lots in >>> VMware >>> and a handful on physical hardware. >>> >>> 11.0-p9 has been very stable. Has anyone seen this problem before with >>> 11.1 ? >> >> >> >> I don't run anything on local hyper-v anymore, but I do run a ot of stuff >> in Azure, and we havent seen anything like this. I track STABLE for things >> though, updating after reading the commits and testing locally for a week or >> so, so the version I am running currently is r320175, which was part of >> 11.1-BETA2. I am going to upgrade to a more recent STABLE sometime this weke >> or next though, will do that on a test amchine and let you now how it goes. >> >> I seem to recall that there were some large changes to the hn code in >> August to add virtual function support. When does 11.1-p1 date from ? > > make sure you contact the FreeBSD/Microsoft guys. Very responsive.. don't > know if they watch -stable.. > I'll cc a couple.. > >> >> -pete. >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > -- Tomorrow Will Never Die From owner-freebsd-stable@freebsd.org Thu Sep 7 05:07:27 2017 Return-Path: Delivered-To: freebsd-stable@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 B0243E06E14 for ; Thu, 7 Sep 2017 05:07:27 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [45.32.79.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3AE564E42; Thu, 7 Sep 2017 05:07:26 +0000 (UTC) (envelope-from paul.koch@akips.com) Date: Thu, 7 Sep 2017 15:07:11 +1000 From: Paul Koch To: Sepherosa Ziehau Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Subject: Re: 11.1 running on HyperV hn interface hangs Message-ID: <20170907150711.025e4e41@akips.com> In-Reply-To: References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> Organization: AKIPS MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 05:07:27 -0000 On Thu, 7 Sep 2017 10:22:40 +0800 Sepherosa Ziehau wrote: > Is it possible to tell me your workload? e.g. TX heavy or RX heavy. > Enabled TSO or not. Details like how the send syscalls are issue will > be interesting. And your Windows version, include the patch level, > etc. > > Please try the following patch: > https://people.freebsd.org/~sephe/hn_dec_txdesc.diff > > Thanks, > sephe Hi Sephe, Here's a bit of an explanation of the environment... AKIPS Network Monitor workload: - 22000 devices (routers/switches/APs/etc) - 123000 interfaces (60 snmp polling) - 131 netflow exporters - ~1500 pings per second - ~1000 snmp requests/responses per second (~1.9 million MIB object/min) - ~250 netflow packets/sec (~4500 flows/sec incoming) - ~130 syslog messages/sec (incoming) - ~200 snmp traps/sec (incoming) The ping/snmp poller is a single monolithic process (no threads). Separate processes for each of the syslog/trap/netflow collection. SNMP requests are sent using the sendto() system call over a non-blocking UDP socket for both IPv4 and v6. We set the UDP socket receive buffer size to 4 Mbytes. Nothing really complex with it. Pings are interlaced with snmp requests so we limit the bursty nature of small back-to-back packets (eliminates issues with switch interfaces dropping bursts of packets). Ping requests are sent using a raw icmp socket. We don't read the responses from the icmp socket, instead we put the interface into promiscuous mode and use the BPF info to measure the tx/rx RTT values. Syslog daemon just listens on a UDP socket with a 4 Mbyte receive buffer. Same with the snmp trap daemon. Here's some links to performance graphs of the VM: https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last2h.pdf https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last24h.pdf https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last7d.pdf The OS was upgraded to 11.1p1 at 5pm on the 5th Sep. The hn0 interface hung at 7:36pm. The interface hung three times before we reverted to 11.0p9. It takes a few hours after rebooting the VM before the interface hangs. Microsoft Host is running Windows 2012 R2. Waiting for patch level info from the customer. I'll have to get the customer to spin up a new VM before trying your patch. Here's some info (after a reboot of the VM) Guest VM dmesg: FreeBSD 11.1-RELEASE-p1 #0 r322350: Thu Aug 10 22:16:21 UTC 2017 root@shed31.akips.com:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) VT(vga): text 80x25 Hyper-V Version: 6.3.9600 [SP18] Features=0xe7f PM Features=0x0 [C2] Features3=0x7b2 Timecounter "Hyper-V" frequency 10000000 Hz quality 2000 CPU: Intel(R) Xeon(R) CPU E5-2695 v3 @ 2.30GHz (2300.00-MHz K8-class CPU) Origin="GenuineIntel" Id=0x306f2 Family=0x6 Model=0x3f Stepping=2 Features=0x1f83fbff Features2=0x80002001 AMD Features=0x20100800 AMD Features2=0x1 Hypervisor: Origin = "Microsoft Hv" real memory = 34359738368 (32768 MB) avail memory = 33325903872 (31782 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: unblocking device. ioapic0: Changing APIC ID to 0 ioapic0 irqs 0-23 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80f5b220, 0) error 19 nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 vmbus0: on pcib0 pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 7.3 (no driver attached) vgapci0: mem 0xf8000000-0xfbffffff irq 11 at device 8.0 on pci0 vgapci0: Boot video device atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 vmbus_res0: irq 5,7 on acpi0 orm0: at iomem 0xc0000-0xcbfff on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec usb_needs_explore_all: no devclass nvme cam probe device init vmbus0: version 3.0 hvet0: on vmbus0 Event timer "Hyper-V" frequency 10000000 Hz quality 1000 storvsc0: on vmbus0 hvkbd0: on vmbus0 hvheartbeat0: on vmbus0 hvkvp0: on vmbus0 hvshutdown0: on vmbus0 hvvss0: on vmbus0 storvsc1: on vmbus0 hn0: on vmbus0 da0 at blkvsc0 bus 0 scbus2 target 1 lun 0 da0: Fixed Direct Access SPC-3 SCSI device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 307200MB (629145600 512 byte sectors) cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SPC-3 SCSI device cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present hn0: Ethernet address: 00:15:5d:31:21:0f hn0: link state changed to UP Trying to mount root from ufs:/dev/gpt/akips-root1 [rw]... Setting hostuuid: 2b0f0733-401e-7646-9724-a89072a2f005. Setting hostid: 0xd87511b7. Starting file system checks: /dev/gpt/akips-root1: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/gpt/akips-root1: clean, 961795 free (227 frags, 120196 blocks, 0.0% fragmentation) /dev/gpt/akips-root0: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/gpt/akips-root0: clean, 977258 free (146 frags, 122139 blocks, 0.0% fragmentation) Mounting local filesystems:. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/perl5/5.24/mach/CORE 32-bit compatibility ldconfig path: /usr/lib32 Setting hostname: xxxxxx Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED Feeding entropy: . Limiting icmp unreach response from 358 to 200 packets/sec Limiting icmp unreach response from 464 to 200 packets/sec Starting Network: lo0 hn0. lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo hn0: flags=8843 metric 0 mtu 1500 options=51b ether 00:15:5d:31:21:0f hwaddr 00:15:5d:31:21:0f inet 172.31.5.13 netmask 0xffffff00 broadcast 172.31.5.255 nd6 options=29 media: Ethernet autoselect (10Gbase-T ) status: active Starting devd. add host 127.0.0.1: gateway lo0 fib 0: route already in table add net default: gateway 172.31.5.254 add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Creating and/or trimming log files. Starting syslogd. Setting date via ntp. Limiting icmp unreach response from 398 to 200 packets/sec Limiting icmp unreach response from 350 to 200 packets/sec Limiting icmp unreach response from 333 to 200 packets/sec Limiting icmp unreach response from 501 to 200 packets/sec Limiting icmp unreach response from 336 to 200 packets/sec Limiting icmp unreach response from 351 to 200 packets/sec No core dumps found. Clearing /tmp (X related). Updating motd:. Mounting late filesystems:. Starting ntpd. Limiting icmp unreach response from 424 to 200 packets/sec postfix/postfix-script: starting the Postfix mail system vfs.zfs.zfetch.max_distance: 8388608 -> 67108864 vfs.usermount: 0 -> 1 net.inet.tcp.sendbuf_inc: 8192 -> 16384 net.inet.tcp.recvbuf_inc: 16384 -> 524288 net.inet.tcp.keepidle: 7200000 -> 60000 net.inet.tcp.keepintvl: 75000 -> 30000 net.inet.tcp.keepinit: 75000 -> 30000 net.inet.udp.blackhole: 0 -> 1 net.inet.tcp.blackhole: 0 -> 1 net.inet.sctp.blackhole: 0 -> 1 net.link.ether.inet.log_arp_movements: 1 -> 0 kern.init_shutdown_timeout: 120 -> 300 root: Clearing temporary files root: Clearing core files root: Clearing state machines root: Prefetching database files root: Starting time daemon 2017-09-06 09:03:46 nm-timed common.c:6032 DEBUG: Create fmap tmap 1032 bytes root: Starting joat daemon root: Starting watchdog 2017-09-06 09:03:46 nm-joatd common.c:5802 INFO: Start Sep 6 09:03:46 bull nm-joatd: Start Configuring vt: blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting cron. -------------------------------------------------------------------- ifconfig: lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo hn0: flags=8843 metric 0 mtu 1500 options=51b ether 00:15:5d:31:21:0f hwaddr 00:15:5d:31:21:0f inet 172.31.5.13 netmask 0xffffff00 broadcast 172.31.5.255 nd6 options=29 media: Ethernet autoselect (10Gbase-T ) status: active ------------------------------------------------------------------------ Some sysctl info for the hn device hw.hn.tx_agg_pkts: -1 hw.hn.tx_agg_size: -1 hw.hn.lro_mbufq_depth: 512 hw.hn.tx_swq_depth: 0 hw.hn.tx_ring_cnt: 0 hw.hn.chan_cnt: 0 hw.hn.use_if_start: 0 hw.hn.use_txdesc_bufring: 1 hw.hn.tx_taskq_mode: 0 hw.hn.tx_taskq_cnt: 1 hw.hn.lro_entry_count: 128 hw.hn.direct_tx_size: 128 hw.hn.tx_chimney_size: 0 hw.hn.tso_maxlen: 65535 hw.hn.trust_hostip: 1 hw.hn.trust_hostudp: 1 hw.hn.trust_hosttcp: 1 dev.hn.0.vf: dev.hn.0.polling: 0 dev.hn.0.agg_pkts: -1 dev.hn.0.agg_size: -1 dev.hn.0.rndis_agg_align: 8 dev.hn.0.rndis_agg_pkts: 8 dev.hn.0.rndis_agg_size: 4026531839 dev.hn.0.rss_ind_size: 128 dev.hn.0.rss_hash: 1701 dev.hn.0.rxfilter: d dev.hn.0.hwassist: 17 dev.hn.0.caps: 3ff dev.hn.0.ndis_version: 6.30 dev.hn.0.nvs_version: 327680 dev.hn.0.channel.13.sub.3.br.tx.state: rindex:122136 windex:122136 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.3.br.rx.state: rindex:157368 windex:157368 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.3.mnf: 1 dev.hn.0.channel.13.sub.3.cpu: 3 dev.hn.0.channel.13.sub.3.chanid: 16 dev.hn.0.channel.13.sub.2.br.tx.state: rindex:116032 windex:116032 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.2.br.rx.state: rindex:150096 windex:150096 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.2.mnf: 1 dev.hn.0.channel.13.sub.2.cpu: 2 dev.hn.0.channel.13.sub.2.chanid: 15 dev.hn.0.channel.13.sub.1.br.tx.state: rindex:236264 windex:236264 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.1.br.rx.state: rindex:304448 windex:304448 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.1.mnf: 1 dev.hn.0.channel.13.sub.1.cpu: 1 dev.hn.0.channel.13.sub.1.chanid: 14 dev.hn.0.channel.13.br.tx.state: rindex:147520 windex:147520 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.br.rx.state: rindex:167776 windex:167776 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.mnf: 1 dev.hn.0.channel.13.cpu: 0 dev.hn.0.rx_ring_inuse: 4 dev.hn.0.rx_ring_cnt: 4 dev.hn.0.rx_ack_failed: 0 dev.hn.0.small_pkts: 538 dev.hn.0.csum_trusted: 0 dev.hn.0.csum_udp: 8734 dev.hn.0.csum_tcp: 18 dev.hn.0.csum_ip: 9758 dev.hn.0.trust_hostip: 1 dev.hn.0.trust_hostudp: 1 dev.hn.0.trust_hosttcp: 1 dev.hn.0.lro_ackcnt_lim: 2 dev.hn.0.lro_length_lim: 18000 dev.hn.0.lro_tried: 18 dev.hn.0.lro_flushed: 18 dev.hn.0.lro_queued: 18 dev.hn.0.rx.3.pktbuf_len: 16384 dev.hn.0.rx.3.rss_pkts: 2223 dev.hn.0.rx.3.packets: 2223 dev.hn.0.rx.2.pktbuf_len: 16384 dev.hn.0.rx.2.rss_pkts: 2186 dev.hn.0.rx.2.packets: 2186 dev.hn.0.rx.1.pktbuf_len: 16384 dev.hn.0.rx.1.rss_pkts: 4323 dev.hn.0.rx.1.packets: 4323 dev.hn.0.rx.0.pktbuf_len: 16384 dev.hn.0.rx.0.rss_pkts: 1026 dev.hn.0.rx.0.packets: 1275 dev.hn.0.agg_align: 8 dev.hn.0.agg_pktmax: 8 dev.hn.0.agg_szmax: 6144 dev.hn.0.tx_ring_inuse: 4 dev.hn.0.tx_ring_cnt: 4 dev.hn.0.sched_tx: 1 dev.hn.0.direct_tx_size: 128 dev.hn.0.tx_chimney_size: 6144 dev.hn.0.tx_chimney_max: 6144 dev.hn.0.txdesc_cnt: 512 dev.hn.0.tx_chimney_tried: 1345 dev.hn.0.tx_chimney: 1345 dev.hn.0.tx_collapsed: 0 dev.hn.0.agg_flush_failed: 0 dev.hn.0.txdma_failed: 0 dev.hn.0.send_failed: 0 dev.hn.0.no_txdescs: 0 dev.hn.0.tx.3.sends: 0 dev.hn.0.tx.3.packets: 0 dev.hn.0.tx.3.oactive: 0 dev.hn.0.tx.2.sends: 0 dev.hn.0.tx.2.packets: 0 dev.hn.0.tx.2.oactive: 0 dev.hn.0.tx.1.sends: 19 dev.hn.0.tx.1.packets: 19 dev.hn.0.tx.1.oactive: 0 dev.hn.0.tx.0.sends: 1326 dev.hn.0.tx.0.packets: 1425 dev.hn.0.tx.0.oactive: 0 dev.hn.0.%parent: vmbus0 dev.hn.0.%pnpinfo: classid=f8615163-df3e-46c5-913f-f2d2f965ed0e deviceid=503f1ad8-7dad-4d5f-9f16-6c4383e28d12 dev.hn.0.%location: dev.hn.0.%driver: hn dev.hn.0.%desc: Hyper-V Network Interface dev.hn.%parent: ------------------------------------------------------------ From owner-freebsd-stable@freebsd.org Thu Sep 7 03:42:07 2017 Return-Path: Delivered-To: freebsd-stable@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 AFB02E02BF8 for ; Thu, 7 Sep 2017 03:42:07 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E94D9746FF; Thu, 7 Sep 2017 03:42:06 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x22f.google.com with SMTP id r141so24225780qke.2; Wed, 06 Sep 2017 20:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=oNc/TQqXi1PlNWhyijC/a26y4GNo6+VEoaVKgXaZhgQ=; b=m+Mf/utu7ngSeMaSXxPkPmwI6WJW3GtIjsqlENOcS5jhlqq4vueVsODO8AfAFteNBs 5lytA/kl/M4rjbQrKtBH8wpAYK/P7PQ7vDIQqfqLSGSNZXjd7woKPHXpPDy6o61oya/z ffzF2Wety5SwoNVWOfx7smiwkDaCdJNPpSLe3NfLDEqyQWeIxacJjGAgiQJP6Wi0uxwN /i9JYM2Y57LFXxY+8Q8mwmsinLZM87t9KZ1TFolsG/xyN39Yvlte13s4y+YHuNjdShY/ Y7wyy1OcrRHaosnRpCT6TqD4fhmC88xnFLuucbKaXs/LAyPam1Msj09gJUOw1gzHpIoC s09g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=oNc/TQqXi1PlNWhyijC/a26y4GNo6+VEoaVKgXaZhgQ=; b=jOQ9eHgP8ZCw2VVmoDoAZVY1/wUFKhNPtrN1DhVkOBEN/l5eG7W8WGeGekNg4xIYoh b40avPOoJ0XU8XCbatFGfQJB7VpvoBj4fd8pc4csxNsUEv8hU4fG10lvfj7Bl1yQsBmZ dp0+nirIdUEF1LUpqTjgj4nT0Xxgp0HxvrpASDnzzveitZhvAp41X3ixhGApB5+fjncx kOvereaCEz1YEPn8o8ZtPZhjJZWRz9+iCw0D61AvSmZaYEbFXmkkbUQ3QDiE+OSaShhs 99vYxLCEFK36htr7AYnHowM3uZhARDpgl3ltLlAhp/C8aDGVikIlk9GLxN2ktz70mcWp BumQ== X-Gm-Message-State: AHPjjUhwxVmmrAUx+f31R2nPsdrKXk4FvpXAc0QgQPE852AGXr8i6K7X iwBCnlCFeOmiH+a5C8iXloPxBDXaLzXw X-Google-Smtp-Source: AOwi7QDOckJ8f5xK/xffwnKK98TsHCKHGIyeoBgWr9wHWxATKtjRjQ47p8YB8wn0/gni2gdxFgNKr8dHKakg/dywrS8= X-Received: by 10.55.102.13 with SMTP id a13mr1820801qkc.320.1504755725539; Wed, 06 Sep 2017 20:42:05 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.106.102 with HTTP; Wed, 6 Sep 2017 20:42:04 -0700 (PDT) In-Reply-To: References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> From: Sepherosa Ziehau Date: Thu, 7 Sep 2017 11:42:04 +0800 X-Google-Sender-Auth: 1bDlBC0fby4u44eo-9_bhxrq4C4 Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Julian Elischer Cc: freebsd-stable@freebsd.org, paul.koch137@gmail.com, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 03:42:07 -0000 Ignore ths hn_dec_txdesc.diff, please try this done; should be more effective: https://people.freebsd.org/~sephe/hn_inc_txbr.diff On Thu, Sep 7, 2017 at 10:22 AM, Sepherosa Ziehau wrote: > Is it possible to tell me your workload? e.g. TX heavy or RX heavy. > Enabled TSO or not. Details like how the send syscalls are issue will > be interesting. And your Windows version, include the patch level, > etc. > > Please try the following patch: > https://people.freebsd.org/~sephe/hn_dec_txdesc.diff > > Thanks, > sephe > > > On Wed, Sep 6, 2017 at 11:23 PM, Julian Elischer wrote: >> On 6/9/17 7:02 pm, Pete French wrote: >>>> >>>> We recently moved our software from 11.0-p9 to 11.1-p1, but looks like >>>> there >>>> is a regression in 11.1-p1 running on HyperV (Windows/HyperV 2012 R2) >>>> where >>>> the virtual hn0 interface hangs with the following kernel messages: >>>> >>>> hn0: on vmbus0 >>>> hn0: Ethernet address: 00:15:5d:31:21:0f >>>> hn0: link state changed to UP >>>> ... >>>> hn0: RXBUF ack retry >>>> hn0: RXBUF ack failed >>>> last message repeated 571 times >>>> >>>> It requires a restart of the HyperV VM. >>>> >>>> This is a customer production server (remote customer ~4000km away) >>>> running >>>> fairly critical monitoring software, so we needed to roll it back to >>>> 11.0-p9. >>>> We only have two customers running our software in HyperV, vs lots in >>>> VMware >>>> and a handful on physical hardware. >>>> >>>> 11.0-p9 has been very stable. Has anyone seen this problem before with >>>> 11.1 ? >>> >>> >>> >>> I don't run anything on local hyper-v anymore, but I do run a ot of stuff >>> in Azure, and we havent seen anything like this. I track STABLE for things >>> though, updating after reading the commits and testing locally for a week or >>> so, so the version I am running currently is r320175, which was part of >>> 11.1-BETA2. I am going to upgrade to a more recent STABLE sometime this weke >>> or next though, will do that on a test amchine and let you now how it goes. >>> >>> I seem to recall that there were some large changes to the hn code in >>> August to add virtual function support. When does 11.1-p1 date from ? >> >> make sure you contact the FreeBSD/Microsoft guys. Very responsive.. don't >> know if they watch -stable.. >> I'll cc a couple.. >> >>> >>> -pete. >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>> >> > > > > -- > Tomorrow Will Never Die -- Tomorrow Will Never Die From owner-freebsd-stable@freebsd.org Thu Sep 7 05:51:14 2017 Return-Path: Delivered-To: freebsd-stable@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 0E7EFE091D0 for ; Thu, 7 Sep 2017 05:51:14 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 589C36E557; Thu, 7 Sep 2017 05:51:13 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qt0-x243.google.com with SMTP id 7so5109606qtz.3; Wed, 06 Sep 2017 22:51:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=q1fe0YzRRH/1mu3S9Er/K21+JGRiBkkzRZGuBgoOFFs=; b=NZ3MiWTi4CXg3DvxSWvvbzWT4XB+hFLQ/JMcEO6He9ri840R0eT0OFxNiEDa42V4te f1bE4YcJkCjFkvSW3hHyja1iUykUZU3EKdANQyA/jYRwSwcwV7zLav4DgkRbAtecX5/D yJXWqqQzVeBNkOYcFVHLrNlnolUsMMI9SV0+NZ55mADcgnd8c+EPeHvV1EmmDEogqCDN SrFaoY4EYjpn16Hq9tsZxrF72UjvVlpQSUf3GTRivg4yAiC7ii/18zh4AjSrpo1yFdsp yQvfbLhx8shktRDAY83phfEqK/ynxsnHIkwE6NU+d5gwt9q4T9dVNTHl2RDmtk0tHUdM N8wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=q1fe0YzRRH/1mu3S9Er/K21+JGRiBkkzRZGuBgoOFFs=; b=AU/1pet7FLSA2+iS7M2hpsixhmpNgUJPRwQkBFOd0lJ2SYO13kkeZXqTL0sKtWWsmD FXGQzPbIPzCno0XR/TCSUQfBExbPvarHyhmW2cUzLtSGvbMsJtW0m/F7816VwO4AhoCO acE20EW76vWJ3OCjf5R3HyCJuwThP0SZiYvwg8xrmL4/6sHPNn4Pka2k+UxOPLd7CKKP 95rMPYWD0Ek8Zuvsc5VhIrzPa8BtrXSxrJrX7PS0HpFLgRRGOYfQ3h5V4RFxfe+Tf9jk xeqnxzyhvnoRvaxa5Ka1S/TBffSz+LPTlac/FWjVpK8SBaEiu64NuNzI33k2Xe1r9CWy CQPw== X-Gm-Message-State: AHPjjUjPfOOZZco8hiPPhhSjcfOxLPOAAM9KgWqjyG4R0+a0oVh7dc7B sCHwoHogM0k65amGHBP5qF7sl2V006g4 X-Google-Smtp-Source: ADKCNb5fgNCncRHAHOLN5GU1TtkxXrbamdK1VVPlCyv1mSkEv3RJZjr6/II4i5nNp9wg8eGnnYNA8SWxhnndhg3UXuw= X-Received: by 10.237.39.157 with SMTP id a29mr2221940qtd.121.1504763472122; Wed, 06 Sep 2017 22:51:12 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.106.102 with HTTP; Wed, 6 Sep 2017 22:51:11 -0700 (PDT) In-Reply-To: <20170907150711.025e4e41@akips.com> References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> <20170907150711.025e4e41@akips.com> From: Sepherosa Ziehau Date: Thu, 7 Sep 2017 13:51:11 +0800 X-Google-Sender-Auth: jvsvoa7nPHzROXsHWbsrwtSQeS8 Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Paul Koch Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 05:51:14 -0000 Weird, your traffic pattern does not even belong to anything heavy. Sending is mainly UDP, which will never be able to saturate the TX buffer ring causing the RXBUF ACK sending failure. This is weird. Anyhow, make sure to test this patch: 8762017-Sep-07 02:19 hn_inc_txbr.diff On Thu, Sep 7, 2017 at 1:07 PM, Paul Koch wrote: > On Thu, 7 Sep 2017 10:22:40 +0800 > Sepherosa Ziehau wrote: > >> Is it possible to tell me your workload? e.g. TX heavy or RX heavy. >> Enabled TSO or not. Details like how the send syscalls are issue will >> be interesting. And your Windows version, include the patch level, >> etc. >> >> Please try the following patch: >> https://people.freebsd.org/~sephe/hn_dec_txdesc.diff >> >> Thanks, >> sephe > > Hi Sephe, > > Here's a bit of an explanation of the environment... > > AKIPS Network Monitor workload: > - 22000 devices (routers/switches/APs/etc) > - 123000 interfaces (60 snmp polling) > - 131 netflow exporters > - ~1500 pings per second > - ~1000 snmp requests/responses per second (~1.9 million MIB object/min) > - ~250 netflow packets/sec (~4500 flows/sec incoming) > - ~130 syslog messages/sec (incoming) > - ~200 snmp traps/sec (incoming) > > The ping/snmp poller is a single monolithic process (no threads). > Separate processes for each of the syslog/trap/netflow collection. > > SNMP requests are sent using the sendto() system call over a non-blocking UDP > socket for both IPv4 and v6. We set the UDP socket receive buffer size to > 4 Mbytes. Nothing really complex with it. > > Pings are interlaced with snmp requests so we limit the bursty nature of > small back-to-back packets (eliminates issues with switch interfaces dropping > bursts of packets). Ping requests are sent using a raw icmp socket. We > don't read the responses from the icmp socket, instead we put the interface > into promiscuous mode and use the BPF info to measure the tx/rx RTT values. > > Syslog daemon just listens on a UDP socket with a 4 Mbyte receive buffer. > Same with the snmp trap daemon. > > > Here's some links to performance graphs of the VM: > https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last2h.pdf > https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last24h.pdf > https://www.akips.com/downloads/hyperv-fbsd11.1p1/system-graphs-last7d.pdf > > The OS was upgraded to 11.1p1 at 5pm on the 5th Sep. The hn0 interface hung > at 7:36pm. The interface hung three times before we reverted to 11.0p9. It > takes a few hours after rebooting the VM before the interface hangs. > > > Microsoft Host is running Windows 2012 R2. Waiting for patch level info from > the customer. > > I'll have to get the customer to spin up a new VM before trying your patch. > > > Here's some info (after a reboot of the VM) > > Guest VM dmesg: > > FreeBSD 11.1-RELEASE-p1 #0 r322350: Thu Aug 10 22:16:21 UTC 2017 > root@shed31.akips.com:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM > 4.0.0) > VT(vga): text 80x25 > Hyper-V Version: 6.3.9600 [SP18] > Features=0xe7f > PM Features=0x0 [C2] > Features3=0x7b2 > Timecounter "Hyper-V" frequency 10000000 Hz quality 2000 > CPU: Intel(R) Xeon(R) CPU E5-2695 v3 @ 2.30GHz (2300.00-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x306f2 Family=0x6 Model=0x3f Stepping=2 > Features=0x1f83fbff > Features2=0x80002001 > AMD Features=0x20100800 > AMD Features2=0x1 > Hypervisor: Origin = "Microsoft Hv" > real memory = 34359738368 (32768 MB) > avail memory = 33325903872 (31782 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > random: unblocking device. > ioapic0: Changing APIC ID to 0 > ioapic0 irqs 0-23 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > Timecounter "Hyper-V-TSC" frequency 10000000 Hz quality 3000 > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff80f5b220, 0) error 19 > nexus0 > vtvga0: on motherboard > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > vmbus0: on pcib0 > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 > ata0: at channel 0 on atapci0 > ata1: at channel 1 on atapci0 > pci0: at device 7.3 (no driver attached) > vgapci0: mem 0xf8000000-0xfbffffff irq 11 at device > 8.0 on pci0 > vgapci0: Boot video device > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > acpi0 > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > vmbus_res0: irq 5,7 on acpi0 > orm0: at iomem 0xc0000-0xcbfff on isa0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ppc0: cannot reserve I/O port range > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounters tick every 1.000 msec > usb_needs_explore_all: no devclass > nvme cam probe device init > vmbus0: version 3.0 > hvet0: on vmbus0 > Event timer "Hyper-V" frequency 10000000 Hz quality 1000 > storvsc0: on vmbus0 > hvkbd0: on vmbus0 > hvheartbeat0: on vmbus0 > hvkvp0: on vmbus0 > hvshutdown0: on vmbus0 > hvvss0: on vmbus0 > storvsc1: on vmbus0 > hn0: on vmbus0 > da0 at blkvsc0 bus 0 scbus2 target 1 lun 0 > da0: Fixed Direct Access SPC-3 SCSI device > da0: 300.000MB/s transfers > da0: Command Queueing enabled > da0: 307200MB (629145600 512 byte sectors) > cd0 at ata1 bus 0 scbus1 target 0 lun 0 > cd0: Removable CD-ROM SPC-3 SCSI device > cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) > cd0: Attempt to query device size failed: NOT READY, Medium not present > hn0: Ethernet address: 00:15:5d:31:21:0f > hn0: link state changed to UP > Trying to mount root from ufs:/dev/gpt/akips-root1 [rw]... > Setting hostuuid: 2b0f0733-401e-7646-9724-a89072a2f005. > Setting hostid: 0xd87511b7. > Starting file system checks: > /dev/gpt/akips-root1: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/gpt/akips-root1: clean, 961795 free (227 frags, 120196 blocks, 0.0% > fragmentation) > /dev/gpt/akips-root0: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/gpt/akips-root0: clean, 977258 free (146 frags, 122139 blocks, 0.0% > fragmentation) > Mounting local filesystems:. > ELF ldconfig > path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/perl5/5.24/mach/CORE > 32-bit compatibility ldconfig path: /usr/lib32 > Setting hostname: xxxxxx > Setting up harvesting: > [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED > Feeding entropy: . > Limiting icmp unreach response from 358 to 200 packets/sec > Limiting icmp unreach response from 464 to 200 packets/sec > Starting Network: lo0 hn0. > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > groups: lo > hn0: flags=8843 metric 0 mtu 1500 > options=51b > ether 00:15:5d:31:21:0f > hwaddr 00:15:5d:31:21:0f > inet 172.31.5.13 netmask 0xffffff00 broadcast 172.31.5.255 > nd6 options=29 > media: Ethernet autoselect (10Gbase-T ) > status: active > Starting devd. > add host 127.0.0.1: gateway lo0 fib 0: route already in table > add net default: gateway 172.31.5.254 > add host ::1: gateway lo0 fib 0: route already in table > add net fe80::: gateway ::1 > add net ff02::: gateway ::1 > add net ::ffff:0.0.0.0: gateway ::1 > add net ::0.0.0.0: gateway ::1 > Creating and/or trimming log files. > Starting syslogd. > Setting date via ntp. > Limiting icmp unreach response from 398 to 200 packets/sec > Limiting icmp unreach response from 350 to 200 packets/sec > Limiting icmp unreach response from 333 to 200 packets/sec > Limiting icmp unreach response from 501 to 200 packets/sec > Limiting icmp unreach response from 336 to 200 packets/sec > Limiting icmp unreach response from 351 to 200 packets/sec > No core dumps found. > Clearing /tmp (X related). > Updating motd:. > Mounting late filesystems:. > Starting ntpd. > Limiting icmp unreach response from 424 to 200 packets/sec > postfix/postfix-script: starting the Postfix mail system > vfs.zfs.zfetch.max_distance: 8388608 -> 67108864 > vfs.usermount: 0 -> 1 > net.inet.tcp.sendbuf_inc: 8192 -> 16384 > net.inet.tcp.recvbuf_inc: 16384 -> 524288 > net.inet.tcp.keepidle: 7200000 -> 60000 > net.inet.tcp.keepintvl: 75000 -> 30000 > net.inet.tcp.keepinit: 75000 -> 30000 > net.inet.udp.blackhole: 0 -> 1 > net.inet.tcp.blackhole: 0 -> 1 > net.inet.sctp.blackhole: 0 -> 1 > net.link.ether.inet.log_arp_movements: 1 -> 0 > kern.init_shutdown_timeout: 120 -> 300 > root: Clearing temporary files > root: Clearing core files > root: Clearing state machines > root: Prefetching database files > root: Starting time daemon > 2017-09-06 09:03:46 nm-timed common.c:6032 DEBUG: Create fmap tmap 1032 bytes > root: Starting joat daemon > root: Starting watchdog > 2017-09-06 09:03:46 nm-joatd common.c:5802 INFO: Start > Sep 6 09:03:46 bull nm-joatd: Start > Configuring vt: blanktime. > Performing sanity check on sshd configuration. > Starting sshd. > Starting cron. > -------------------------------------------------------------------- > > > ifconfig: > > lo0: flags=8049 metric 0 mtu 16384 > options=600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > groups: lo > hn0: flags=8843 metric 0 mtu 1500 > options=51b > ether 00:15:5d:31:21:0f > hwaddr 00:15:5d:31:21:0f > inet 172.31.5.13 netmask 0xffffff00 broadcast 172.31.5.255 > nd6 options=29 > media: Ethernet autoselect (10Gbase-T ) > status: active > ------------------------------------------------------------------------ > > > Some sysctl info for the hn device > > hw.hn.tx_agg_pkts: -1 > hw.hn.tx_agg_size: -1 > hw.hn.lro_mbufq_depth: 512 > hw.hn.tx_swq_depth: 0 > hw.hn.tx_ring_cnt: 0 > hw.hn.chan_cnt: 0 > hw.hn.use_if_start: 0 > hw.hn.use_txdesc_bufring: 1 > hw.hn.tx_taskq_mode: 0 > hw.hn.tx_taskq_cnt: 1 > hw.hn.lro_entry_count: 128 > hw.hn.direct_tx_size: 128 > hw.hn.tx_chimney_size: 0 > hw.hn.tso_maxlen: 65535 > hw.hn.trust_hostip: 1 > hw.hn.trust_hostudp: 1 > hw.hn.trust_hosttcp: 1 > dev.hn.0.vf: > dev.hn.0.polling: 0 > dev.hn.0.agg_pkts: -1 > dev.hn.0.agg_size: -1 > dev.hn.0.rndis_agg_align: 8 > dev.hn.0.rndis_agg_pkts: 8 > dev.hn.0.rndis_agg_size: 4026531839 > dev.hn.0.rss_ind_size: 128 > dev.hn.0.rss_hash: 1701 > dev.hn.0.rxfilter: d > dev.hn.0.hwassist: 17 > dev.hn.0.caps: > 3ff > dev.hn.0.ndis_version: 6.30 dev.hn.0.nvs_version: 327680 > dev.hn.0.channel.13.sub.3.br.tx.state: rindex:122136 windex:122136 imask:0 > ravail:0 wavail:520192 dev.hn.0.channel.13.sub.3.br.rx.state: rindex:157368 > windex:157368 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.3.mnf: 1 > dev.hn.0.channel.13.sub.3.cpu: 3 > dev.hn.0.channel.13.sub.3.chanid: 16 > dev.hn.0.channel.13.sub.2.br.tx.state: rindex:116032 windex:116032 imask:0 > ravail:0 wavail:520192 dev.hn.0.channel.13.sub.2.br.rx.state: rindex:150096 > windex:150096 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.2.mnf: 1 > dev.hn.0.channel.13.sub.2.cpu: 2 > dev.hn.0.channel.13.sub.2.chanid: 15 > dev.hn.0.channel.13.sub.1.br.tx.state: rindex:236264 windex:236264 imask:0 > ravail:0 wavail:520192 dev.hn.0.channel.13.sub.1.br.rx.state: rindex:304448 > windex:304448 imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.sub.1.mnf: 1 > dev.hn.0.channel.13.sub.1.cpu: 1 > dev.hn.0.channel.13.sub.1.chanid: 14 > dev.hn.0.channel.13.br.tx.state: rindex:147520 windex:147520 imask:0 ravail:0 > wavail:520192 dev.hn.0.channel.13.br.rx.state: rindex:167776 windex:167776 > imask:0 ravail:0 wavail:520192 dev.hn.0.channel.13.mnf: 1 > dev.hn.0.channel.13.cpu: 0 > dev.hn.0.rx_ring_inuse: 4 > dev.hn.0.rx_ring_cnt: 4 > dev.hn.0.rx_ack_failed: 0 > dev.hn.0.small_pkts: 538 > dev.hn.0.csum_trusted: 0 > dev.hn.0.csum_udp: 8734 > dev.hn.0.csum_tcp: 18 > dev.hn.0.csum_ip: 9758 > dev.hn.0.trust_hostip: 1 > dev.hn.0.trust_hostudp: 1 > dev.hn.0.trust_hosttcp: 1 > dev.hn.0.lro_ackcnt_lim: 2 > dev.hn.0.lro_length_lim: 18000 > dev.hn.0.lro_tried: 18 > dev.hn.0.lro_flushed: 18 > dev.hn.0.lro_queued: 18 > dev.hn.0.rx.3.pktbuf_len: 16384 > dev.hn.0.rx.3.rss_pkts: 2223 > dev.hn.0.rx.3.packets: 2223 > dev.hn.0.rx.2.pktbuf_len: 16384 > dev.hn.0.rx.2.rss_pkts: 2186 > dev.hn.0.rx.2.packets: 2186 > dev.hn.0.rx.1.pktbuf_len: 16384 > dev.hn.0.rx.1.rss_pkts: 4323 > dev.hn.0.rx.1.packets: 4323 > dev.hn.0.rx.0.pktbuf_len: 16384 > dev.hn.0.rx.0.rss_pkts: 1026 > dev.hn.0.rx.0.packets: 1275 > dev.hn.0.agg_align: 8 > dev.hn.0.agg_pktmax: 8 > dev.hn.0.agg_szmax: 6144 > dev.hn.0.tx_ring_inuse: 4 > dev.hn.0.tx_ring_cnt: 4 > dev.hn.0.sched_tx: 1 > dev.hn.0.direct_tx_size: 128 > dev.hn.0.tx_chimney_size: 6144 > dev.hn.0.tx_chimney_max: 6144 > dev.hn.0.txdesc_cnt: 512 > dev.hn.0.tx_chimney_tried: 1345 > dev.hn.0.tx_chimney: 1345 > dev.hn.0.tx_collapsed: 0 > dev.hn.0.agg_flush_failed: 0 > dev.hn.0.txdma_failed: 0 > dev.hn.0.send_failed: 0 > dev.hn.0.no_txdescs: 0 > dev.hn.0.tx.3.sends: 0 > dev.hn.0.tx.3.packets: 0 > dev.hn.0.tx.3.oactive: 0 > dev.hn.0.tx.2.sends: 0 > dev.hn.0.tx.2.packets: 0 > dev.hn.0.tx.2.oactive: 0 > dev.hn.0.tx.1.sends: 19 > dev.hn.0.tx.1.packets: 19 > dev.hn.0.tx.1.oactive: 0 > dev.hn.0.tx.0.sends: 1326 > dev.hn.0.tx.0.packets: 1425 > dev.hn.0.tx.0.oactive: 0 > dev.hn.0.%parent: vmbus0 > dev.hn.0.%pnpinfo: classid=f8615163-df3e-46c5-913f-f2d2f965ed0e > deviceid=503f1ad8-7dad-4d5f-9f16-6c4383e28d12 dev.hn.0.%location: > dev.hn.0.%driver: hn > dev.hn.0.%desc: Hyper-V Network Interface > dev.hn.%parent: > ------------------------------------------------------------ > -- Tomorrow Will Never Die From owner-freebsd-stable@freebsd.org Thu Sep 7 12:04:02 2017 Return-Path: Delivered-To: freebsd-stable@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 7C7FAE1B201 for ; Thu, 7 Sep 2017 12:04:02 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo.suszko.eu (archeo.unixguru.pl [IPv6:2001:41d0:2:8316::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 925D781E76 for ; Thu, 7 Sep 2017 12:04:01 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo (localhost [127.0.0.1]) by archeo.suszko.eu (Postfix) with ESMTP id D88006B1; Thu, 7 Sep 2017 14:03:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at archeo.local Received: from archeo.suszko.eu ([127.0.0.1]) by archeo (archeo.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id omIo_WUK_Y8e; Thu, 7 Sep 2017 14:03:58 +0200 (CEST) Received: from helium (unknown [195.8.99.234]) by archeo.suszko.eu (Postfix) with ESMTPSA id 5A6C26AA; Thu, 7 Sep 2017 14:03:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=suszko.eu; s=dkim; t=1504785838; bh=oNCO1Lcn6aonS7C3sEmmNmpcoCy6WAFu8O2SZvUqm1o=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=KWLaI4U15K42thjplTJe8U8SX/EcVBqya6wdyHLiIlapmjmTxO8KJ19xLD9b9s7CI CJ4j+5gU0ydeUMHhn3e7+Tix7yVgJOlOmn42A1NTpZetc8zpOc6jARnRFad+2m/M0M pSevupKJPCtLoxj7/j9dxxKUIcPNd51WaD6OFx4g= Date: Thu, 7 Sep 2017 14:03:51 +0200 From: Maciej Suszko To: "Priyadarshana Chandrasena" Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support Message-ID: <20170907140351.34724dd2@helium> In-Reply-To: <20170903211908.510b5724@leo> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/T21Fgpkm5WBHUrZM6Cew2a/"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 12:04:02 -0000 --Sig_/T21Fgpkm5WBHUrZM6Cew2a/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 3 Sep 2017 21:19:08 +0200 Maciej Suszko wrote: > "Priyadarshana Chandrasena" wrote: > > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in > > it. I have a HP smart array P440 in my server. I can not find out > > anywhere if ciss driver support include HP Gen 9 storage > > controllers. Could you please update the ciss driver in 10.3? =20 >=20 > Hi, >=20 > Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). > In a few days I plan to boot it in HBA mode, we'll see if it's working. Just tested, HBA mode... Machine BIOS U22 v1.80, one-time booted in Legacy mode with mfsBSD iso in Virtual CD drive (through iLO), recreated system zpool to mirror of 2 drives, booted in UEFI mode - it does work. #v+ root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-4 SCSI device pass2: Serial Number S4226CNT0000M70507YN pass2: 135.168MB/s transfers, Command Queueing Enabled root@storage-04:~ # camcontrol inquiry da3 pass3: Fixed Direct Access SPC-4 SCSI device pass3: Serial Number S4226CHH0000M70540VJ pass3: 135.168MB/s transfers, Command Queueing Enabled root@storage-04:~ # zpool status rpool pool: rpool state: ONLINE scan: scrub repaired 0 in 0h2m with 0 errors on Thu Sep 7 11:56:31 2017 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da2p3 ONLINE 0 0 0 da3p3 ONLINE 0 0 0 errors: No known data errors #v- [ c u t ] --=20 regards, Maciej Suszko. --Sig_/T21Fgpkm5WBHUrZM6Cew2a/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRBv6xO7mzN+RcEaiUKKRSTSXuIagUCWbE1pwAKCRAKKRSTSXuI amSrAJ0d0jKjBdf80nJRjSQ70J9Wba0hkACdGi4mGtmYttFvbJpN6MAJiQbcC/M= =V5ZM -----END PGP SIGNATURE----- --Sig_/T21Fgpkm5WBHUrZM6Cew2a/-- From owner-freebsd-stable@freebsd.org Thu Sep 7 15:04:20 2017 Return-Path: Delivered-To: freebsd-stable@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 E3F47E21B56 for ; Thu, 7 Sep 2017 15:04:20 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [45.32.79.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A84D96383B; Thu, 7 Sep 2017 15:04:20 +0000 (UTC) (envelope-from paul.koch@akips.com) Date: Fri, 8 Sep 2017 01:04:00 +1000 From: Paul Koch To: Sepherosa Ziehau Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Subject: Re: 11.1 running on HyperV hn interface hangs Message-ID: <20170908010400.0fb81bc4@akips.com> In-Reply-To: References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> <20170907150711.025e4e41@akips.com> Organization: AKIPS MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 15:04:21 -0000 On Thu, 7 Sep 2017 13:51:11 +0800 Sepherosa Ziehau wrote: > Weird, your traffic pattern does not even belong to anything heavy. > Sending is mainly UDP, which will never be able to saturate the TX > buffer ring causing the RXBUF ACK sending failure. This is weird. It's a bit tricky. The poller is very fast. We ping every device every 15 seconds, and collect every MIB object every 60 seconds. The poller "rate limits" itself by dividing each minute into 100ms time slots and only sends a specific amount of pings/snmp packets in each time slot. The problem is, it blasts the request packets out really fast at the start of each time slot, and then sits in a receive loop until the next time slot comes around. The requests are not paced over the 100ms, therefore it will blast out a lot of packets in a few milliseconds. We use to use a 1 second rate limiting time slot, and didn't interlace ping/snmp requests, but we found certain interface types on Cisco 6509 switches couldn't keep up with back-to-back pings and would lose them. > Anyhow, make sure to test this patch: > 8762017-Sep-07 02:19 hn_inc_txbr.diff Yep. Might take a bit of time to test though because we'll need to get the customer to spin up a test VM on the same platform, and they are fairly remote (Perth, Australia). We don't run any Microsoft servers/HyperV setups in our lab. Paul. -- Paul Koch | Founder | CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@freebsd.org Thu Sep 7 15:28:32 2017 Return-Path: Delivered-To: freebsd-stable@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 68370E22AF5; Thu, 7 Sep 2017 15:28:32 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE13669241; Thu, 7 Sep 2017 15:28:31 +0000 (UTC) (envelope-from julien.charbon@gmail.com) Received: by mail-wm0-f46.google.com with SMTP id r10so1111663wmf.1; Thu, 07 Sep 2017 08:28:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fCwFZtBtV8puzrgJsf/Ff+CwOjYExRIeBcA/j4Nn1Y8=; b=ekyZi0uR1c24BXQ9j4cgMwmUCQI+5iGAeFuQwGRiv53rkO9Z3cmUTYi3l+v+58fKzi aMC1mlOsvWNodMg1M0D0tTcjejcPwmsV07ym6rNlGauiJqrd5alsly7Y97oBVy86r0ud pOyFAk/ukPlTeyMrISreCqDFaU0NzrR0HYHG6FwTVL9WFGl+t7/wTKkzEZp52Dhn508u 0OJ8ModSEhVhKqqZjWBZZdsXC9OUW7ql8bzxqaGWYpgQPy991IGT+gSSeN3zyrcy8K4x 8mzZjawiHu3FZ9546/R+R4dGOYUbVtGQyF42TovNwI/ZYRptbbBCkEOcnpFwe1347H7Q 09ww== X-Gm-Message-State: AHPjjUi3u+HWZJi39Z9Lf5iEodJh/TlHcsIYgP17hWUvwBb9dECBPv0Y qOeD32Xwq95O4tcZJrA= X-Google-Smtp-Source: AOwi7QCNlpAFFoDEZjffIL1wOLyNMEeBxzYyGGDbEnRFTFKc/+QIkrMIlrOaCgoUFSeZqXRGD4zfdg== X-Received: by 10.28.131.197 with SMTP id f188mr795787wmd.71.1504797746215; Thu, 07 Sep 2017 08:22:26 -0700 (PDT) Received: from [10.100.64.46] ([217.30.88.7]) by smtp.gmail.com with ESMTPSA id 29sm4615163wrz.77.2017.09.07.08.22.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Sep 2017 08:22:25 -0700 (PDT) Subject: Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???) To: Ben RUBSON Cc: Hans Petter Selasky , FreeBSD Net , hiren , Slawa Olhovchenkov , FreeBSD Stable References: <4C91C6E5-0725-42E7-9813-1F3ACF3DDD6E@gmail.com> <5840c25e-7472-3276-6df9-1ed4183078ad@selasky.org> <2ADA8C57-2C2D-4F97-9F0B-82D53EDDC649@gmail.com> <061cdf72-6285-8239-5380-58d9d19a1ef7@selasky.org> <92BEE83D-498F-47D5-A53C-39DCDC00A0FD@gmail.com> <5d8960d8-e1ff-8719-320f-d3ae84054714@selasky.org> <6B4A35F7-5694-4945-9575-19ADB678F9FA@gmail.com> <297a784a-3d80-b1a6-652e-a78621fe5a8b@selasky.org> <3ECCFBF1-18D9-4E33-8F39-0C366C3BB8B4@gmail.com> <0a5787c5-8a53-ab09-971a-dc1cd5f3aca0@freebsd.org> <645f2ee3-3eaa-660e-2a64-37d53e88322f@freebsd.org> <13DE4E6D-CE83-4B5D-BF88-0EFE65111311@gmail.com> <7B084207-062A-4529-B0DC-5BFEB6517780@gmail.com> <82e661b4-1bac-ff5b-f776-8dba44cac15e@freebsd.org> <82EFBD5E-8FC2-4156-A030-AF70D97A37BA@gmail.com> From: Julien Charbon Message-ID: <25938f82-a32e-e014-8a98-4f9452dca9b5@freebsd.org> Date: Thu, 7 Sep 2017 11:22:19 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <82EFBD5E-8FC2-4156-A030-AF70D97A37BA@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 15:28:32 -0000 Hi Ben, On 8/31/17 12:04 PM, Ben RUBSON wrote: >> On 28 Aug 2017, at 11:27, Julien Charbon wrote: >> >> On 8/28/17 10:25 AM, Ben RUBSON wrote: >>>> On 16 Aug 2017, at 11:02, Ben RUBSON wrote: >>>> >>>>> On 15 Aug 2017, at 23:33, Julien Charbon wrote: >>>>> >>>>> On 8/11/17 11:32 AM, Ben RUBSON wrote: >>>>>>> On 08 Aug 2017, at 13:33, Julien Charbon wrote: >>>>>>> >>>>>>> On 8/8/17 10:31 AM, Hans Petter Selasky wrote: >>>>>>>> >>>>>>>> Suggested fix attached. >>>>>>> >>>>>>> I agree we your conclusion. Just for the record, more precisely this >>>>>>> regression seems to have been introduced with: >>>>>>> (...) >>>>>>> Thus good catch, and your patch looks good. I am going to just verify >>>>>>> the other in_pcbrele_wlocked() calls in TCP stack. >>>>>> >>>>>> Julien, do you plan to make this fix reach 11.0-p12 ? >>>>> >>>>> I am checking if your issue is another flavor of the issue fixed by: >>>>> >>>>> https://svnweb.freebsd.org/base?view=revision&revision=307551 >>>>> https://reviews.freebsd.org/D8211 >>>>> >>>>> This fix in not in 11.0 but in 11.1. Currently I did not found how an >>>>> inp in INP_TIMEWAIT state can have been INP_FREED without having its tw >>>>> set to NULL already except the issue fixed by r307551. >>>>> >>>>> Thus could you try to apply this patch: >>>>> >>>>> https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087c5f7d0a0.patch >>>>> >>>>> and see if you can still reproduce this issue? >>>> >>>> Thank you for your answer Julien. >>>> Unfortunately, I'm not sure at all how to reproduce the issue. >>>> I have other servers which are 100% identical to this one, same workload, >>>> same some-months uptime, but they did not trigger the bug yet. >>>> >>>> If other network stack experts (I'm not) agree with your analysis, >>>> we could then certainly go further with D8211 / r307551. >>>> >>>> One thing that perhaps might help : >>>> # netstat -an | grep TIME_WAIT$ | wc -l >>>> 468 >>>> >>>> Note that due to this running bug, sendmail has lots of difficulties to send outgoing mails. >>>> As soon as I run the above netstat command, I receive a lot of stacked mails (more than 20 this time). >>>> As if netstat was able to somehow help... >>>> >>>> Number of TIME_WAIT connections however does not decrease, but increases. >>>> >>>>> And in the spirit of r307551 fix and based on Hans patch I will also >>>>> propose to add a kernel log describing the issue instead of starting an >>>>> infinite loop when INVARIANT is not set. >>>> >>>> Which should then never be triggered :) >>>> Good idea I think ! >>> >>> What about : >>> D8211/r307551 >>> + Hans' patch >>> + Julien's idea of a kernel log (sort of "We should not be here but we are") >> >> I did this change and I am testing it > > Good news ! > >> on your side did you try this patch applied on 11.0? >> >> https://github.com/freebsd/freebsd/commit/acb5bfda99b753d9ead3529d04f20087c5f7d0a0.patch > > Yes, patch applied and running correctly, > however hard to say whether or not it solves this issue, > as there is no easy way to reproduce it. No problem, it is just a matter of not seeing the issue anymore during a long enough period. I created a review that includes Hans's patch and uses the same log(LOG_ERR) logic than r307551: https://reviews.freebsd.org/D12267 On my side, TCP smoke tests are ok. And I am going to launch our TCP QA on it while receiving review comments. > Mail sent to FreeBSD Security Team ! > > Many thanks, let's stay tuned ! Thanks to you and Hans for reporting that issue. And in summary: - Applying r307551 on top of 11.0 should prevent this case to happen - D12267 will prevent the tcp_tw_2msl_scan() infinite loop while reporting the error, in case a regression defeating r307551 is introduced Thanks. -- Julien From owner-freebsd-stable@freebsd.org Thu Sep 7 21:14:29 2017 Return-Path: Delivered-To: freebsd-stable@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 44347E10260 for ; Thu, 7 Sep 2017 21:14:29 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from ua.ulka.com.au (ua.ulka.com.au [203.217.10.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65F17731AB for ; Thu, 7 Sep 2017 21:14:27 +0000 (UTC) (envelope-from vpc@ulka.com.au) Received: from PLUTO (pluto.ulka.com.au [10.0.0.27]) by ua.ulka.com.au (8.14.7/8.14.7) with SMTP id v87LE2Zt017339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 8 Sep 2017 06:44:03 +0930 (CST) (envelope-from vpc@ulka.com.au) From: "Priyadarshana Chandrasena" To: "'Maciej Suszko'" Cc: References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <20170907140351.34724dd2@helium> In-Reply-To: <20170907140351.34724dd2@helium> Subject: RE: HP Smart array P440 support Date: Fri, 8 Sep 2017 06:43:14 +0930 Message-ID: <000601d3281e$22b2cef0$68186cd0$@ulka.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKf262D1pzaEW0PjHJqNu5p+S/e0gG9PdpuApX7Slmg7epRsA== Content-Language: en-au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 21:14:29 -0000 I have not installed FreeBSD using iLo and virtual CD method. I will read about this method and try it out. Thanks. -----Original Message----- From: Maciej Suszko [mailto:maciej@suszko.eu] Sent: Thursday, 7 September 2017 9:34 PM To: Priyadarshana Chandrasena Cc: FreeBSD-stable@FreeBSD.org Subject: Re: HP Smart array P440 support On Sun, 3 Sep 2017 21:19:08 +0200 Maciej Suszko wrote: > "Priyadarshana Chandrasena" wrote: > > I have HP DL20 Gen 9 server. But I can not install FreeBSD 10.2 in > > it. I have a HP smart array P440 in my server. I can not find out > > anywhere if ciss driver support include HP Gen 9 storage > > controllers. Could you please update the ciss driver in 10.3? > > Hi, > > Got two DL20 with P440, UEFI booted 11.0 to logical disk (raid array). > In a few days I plan to boot it in HBA mode, we'll see if it's working. Just tested, HBA mode... Machine BIOS U22 v1.80, one-time booted in Legacy mode with mfsBSD iso in Virtual CD drive (through iLO), recreated system zpool to mirror of 2 drives, booted in UEFI mode - it does work. #v+ root@storage-04:~ # camcontrol inquiry da2 pass2: Fixed Direct Access SPC-4 SCSI device pass2: Serial Number S4226CNT0000M70507YN pass2: 135.168MB/s transfers, Command Queueing Enabled root@storage-04:~ # camcontrol inquiry da3 pass3: Fixed Direct Access SPC-4 SCSI device pass3: Serial Number S4226CHH0000M70540VJ pass3: 135.168MB/s transfers, Command Queueing Enabled root@storage-04:~ # zpool status rpool pool: rpool state: ONLINE scan: scrub repaired 0 in 0h2m with 0 errors on Thu Sep 7 11:56:31 2017 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da2p3 ONLINE 0 0 0 da3p3 ONLINE 0 0 0 errors: No known data errors #v- [ c u t ] -- regards, Maciej Suszko. From owner-freebsd-stable@freebsd.org Thu Sep 7 21:28:50 2017 Return-Path: Delivered-To: freebsd-stable@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 C175EE10FE1 for ; Thu, 7 Sep 2017 21:28:50 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id CA6D576539 for ; Thu, 7 Sep 2017 21:28:49 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Thu, 07 Sep 2017 23:28:41 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id CD2D1532-B677-437B-BDEE-5CF59E2038CE.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Thu, 07 Sep 2017 23:28:39 +0200 From: Rainer Duffner Message-Id: <9E955DD6-6F54-4244-AC38-8AD2943099B9@ultra-secure.de> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: HP Smart array P440 support Date: Thu, 7 Sep 2017 23:28:38 +0200 References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <20170907140351.34724dd2@helium> <000601d3281e$22b2cef0$68186cd0$@ulka.com.au> To: freebsd-stable In-Reply-To: <000601d3281e$22b2cef0$68186cd0$@ulka.com.au> X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=15 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3897, bad: 1, connections: 4322, history: 3896, asn_score: 430, asn_connections: 441, asn_good: 430, asn_bad: 0, pass:asn, asn_all_good, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 21:28:51 -0000 > Am 07.09.2017 um 23:13 schrieb Priyadarshana Chandrasena = : >=20 > I have not installed FreeBSD using iLo and virtual CD method. I will = read > about this method and try it out.=20 You will need an iLO license for that. Also, enjoy Gen10 servers, where even more features are going to be = =E2=80=9Epay-for-play=E2=80=9C. From owner-freebsd-stable@freebsd.org Fri Sep 8 07:08:59 2017 Return-Path: Delivered-To: freebsd-stable@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 C5B64E0806E for ; Fri, 8 Sep 2017 07:08:59 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo.suszko.eu (archeo.unixguru.pl [IPv6:2001:41d0:2:8316::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 73610722DB for ; Fri, 8 Sep 2017 07:08:59 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo (localhost [127.0.0.1]) by archeo.suszko.eu (Postfix) with ESMTP id 8506DE59; Fri, 8 Sep 2017 09:08:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at archeo.local Received: from archeo.suszko.eu ([127.0.0.1]) by archeo (archeo.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jLfjCi9kitcw; Fri, 8 Sep 2017 09:08:49 +0200 (CEST) Received: from helium (unknown [195.8.99.234]) by archeo.suszko.eu (Postfix) with ESMTPSA id 06D71E52; Fri, 8 Sep 2017 09:08:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=suszko.eu; s=dkim; t=1504854529; bh=NxHbcwSQZWpALbTwkgylsbH3mJwcIbuJ5MCgeJ2FWjE=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=WI6OqeViuyakt7RVOnsCi/lEPx2XRTSzACweYZ5a0cvKGA9r/qAmYUkwD2eNq3IRO KaELqqk6KX9uiN9jOrWpYgyBO5HKPGd4lbeqzUiZ79OQ9ze9RM58b8Y/vuL+T8LIUy iGmTPwjQ7fTvgh0Jgi+6jFucuoEIKVmG5BWffP8E= Date: Fri, 8 Sep 2017 09:08:41 +0200 From: Maciej Suszko To: Rainer Duffner Cc: freebsd-stable Subject: Re: HP Smart array P440 support Message-ID: <20170908090841.3cfc6c2e@helium> In-Reply-To: <9E955DD6-6F54-4244-AC38-8AD2943099B9@ultra-secure.de> References: <001501d323f2$3e517560$baf46020$@ulka.com.au> <20170903211908.510b5724@leo> <20170907140351.34724dd2@helium> <000601d3281e$22b2cef0$68186cd0$@ulka.com.au> <9E955DD6-6F54-4244-AC38-8AD2943099B9@ultra-secure.de> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/XYBws7P7vApw22bbCG656lJ"; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 07:08:59 -0000 --Sig_/XYBws7P7vApw22bbCG656lJ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, 7 Sep 2017 23:28:38 +0200 Rainer Duffner wrote: > > Am 07.09.2017 um 23:13 schrieb Priyadarshana Chandrasena : > >=20 > > I have not installed FreeBSD using iLo and virtual CD method. I will re= ad > > about this method and try it out. =20 >=20 >=20 >=20 > You will need an iLO license for that. I have no CD/DVD drive installed, but you can use external one for sure. > Also, enjoy Gen10 servers, where even more features are going to be =E2= =80=9Epay-for-play=E2=80=9C. That sukcs. --=20 regards, Maciej Suszko. --Sig_/XYBws7P7vApw22bbCG656lJ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQRBv6xO7mzN+RcEaiUKKRSTSXuIagUCWbJB+gAKCRAKKRSTSXuI ak7BAJ44I5fRXWFVvw7Pki4xiOypql2D/wCeJyEIltVICUhs8TUJ6Xn0u8QQ6Xk= =sRSo -----END PGP SIGNATURE----- --Sig_/XYBws7P7vApw22bbCG656lJ-- From owner-freebsd-stable@freebsd.org Fri Sep 8 11:13:21 2017 Return-Path: Delivered-To: freebsd-stable@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 8D7D1E11B4E for ; Fri, 8 Sep 2017 11:13:21 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1.freebsd.org (Postfix) with ESMTP id 07B2164681 for ; Fri, 8 Sep 2017 11:13:19 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 9FCBC1954835 for ; Fri, 8 Sep 2017 04:13:13 -0700 (MST) Date: Fri, 8 Sep 2017 04:13:13 -0700 (MST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1504869193651-0.post@n6.nabble.com> Subject: Since about week 11-STABLE is building debug files regardless of src.conf settings MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Sep 2017 11:13:21 -0000 Hello, I have WITHOUT_DEBUG_FILES=true WITHOUT_ASSERT_DEBUG=true WITHOUT_KERNEL_SYMBOLS=true in src.conf. Nonetheless, in the last two updates I had files removed from /usr/lib/debug/ upon make-delete-old. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html From owner-freebsd-stable@freebsd.org Sat Sep 9 19:55:59 2017 Return-Path: Delivered-To: freebsd-stable@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 3DFEDE06188 for ; Sat, 9 Sep 2017 19:55:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B6A57669D for ; Sat, 9 Sep 2017 19:55:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v89Jtwii005045 for ; Sat, 9 Sep 2017 19:55:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 183817] [patch] [mac] [panic] kernel compiled with options INVARIANTS and MAC_PORTACL panices if loader loads mac_portacl.ko too Date: Sat, 09 Sep 2017 19:55:58 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: crash, easy, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Sep 2017 19:55:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183817 --- Comment #3 from Eugene Grosbein --- *** Bug 186362 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Sat Sep 9 21:54:44 2017 Return-Path: Delivered-To: freebsd-stable@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 10972E0CB4C for ; Sat, 9 Sep 2017 21:54:44 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AEDBD7F1F6; Sat, 9 Sep 2017 21:54:43 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.15.2/8.15.2/ALCHEMY.FRANKEN.DE) with ESMTPS id v89LsYa4049682 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 9 Sep 2017 23:54:34 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.15.2/8.15.2/Submit) id v89LsYU8049681; Sat, 9 Sep 2017 23:54:34 +0200 (CEST) (envelope-from marius) Date: Sat, 9 Sep 2017 23:54:34 +0200 From: Marius Strobl To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 10.4-BETA4 Now Available Message-ID: <20170909215434.GD20729@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Sep 2017 21:54:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The fourth BETA build of the 10.4-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC o armv6 BEAGLEBONE o armv6 CUBOX-HUMMINGBOARD o armv6 GUMSTIX o armv6 PANDABOARD o armv6 RPI-B o armv6 WANDBOARD Note regarding arm/armv6 images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/10.4/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "stable/10" branch. A list of changes since 10.3-RELEASE are available in the stable/10 release notes: https://www.freebsd.org/relnotes/10-STABLE/relnotes/article.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.4-RELEASE cycle progresses. === Noteworthy Changes Since 10.4-BETA3 === o An erroneous implementation of a silicon bug workaround caused the em(4) driver to always silently disable support for VLAN_HWTSO and TSO4 on the first time an interface was configured. That implementation bug has been corrected but em(4) also changed to no longer automatically enable the VLAN_HWTSO and TSO4 capabilities by default. The latter is due to the fact that the particular hardware defect cannot be reliably worked around in all circumstances. Moreover, desipite several workarounds for TSO- related deficiencies of devices supported em(4) being in place, testing has shown that at least with Intel 82579 employing TSO may hang the chip. Generally, with this changes in place it is now possible again to use TSO with em(4) by manually enabling vlanhwtso and/or tso4 via ifconfig(4). However, care must be taken that doing so is only considered to be safe in environments where the link speed is not to be expected to change from GbE and that at least some models still may experience device timeouts then. o The igb(4) driver now handles received packets whose EtherType protocols are unsupported or for which support has not been compiled in gracefully instead of triggering a panic. o A crash of date(1) that could be triggered by passing invalid time has been corrected. o The file(1) utility received a fix for CVE-2017-1000249. o A bug in ipfilter(4) preventing NATed MTU discovery to work has been addressed. o Mellanox ConnectX-4 series adapters are now supported by the newly added mlx5ib(4) driver. o OpenSSH received an update to version 7.3p1. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/10.4-BETA4/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 160 MB and 128 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: Created AMI in ap-south-1 region: ami-384a0d57 Created AMI in eu-west-2 region: ami-65564501 Created AMI in eu-west-1 region: ami-3ae42243 Created AMI in ap-northeast-2 region: ami-7bd40f15 Created AMI in ap-northeast-1 region: ami-a805c3ce Created AMI in sa-east-1 region: ami-617c0e0d Created AMI in ca-central-1 region: ami-0bf0496f Created AMI in ap-southeast-1 region: ami-acb8d1cf Created AMI in ap-southeast-2 region: ami-312cc853 Created AMI in eu-central-1 region: ami-273e8a48 Created AMI in us-east-1 region: ami-9ccad6e7 Created AMI in us-east-2 region: ami-d45674b1 Created AMI in us-west-1 region: ami-0b1a2d6b Created AMI in us-west-2 region: ami-9b9167e3 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-10.4-BETA4 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.4-BETA4 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 10.4-BETA4 amd64 GENERIC: SHA512 (FreeBSD-10.4-BETA4-amd64-bootonly.iso) = 1586a427af5f33dba44dc812aadb0c79236748d94f3bb323718d49e688a9a4584fbfda698c62b71226d263699f31ad097efaac2c0e36db977f61224e526a60ba SHA512 (FreeBSD-10.4-BETA4-amd64-bootonly.iso.xz) = d4698fff8033ae66df6def9b851484539851a77a0e1fc9ccdb715a69acee9b4ecba132432e6b2a4751cbe0dfd23ce46d8dfaf7310583b8f1cfce8119f574fdf8 SHA512 (FreeBSD-10.4-BETA4-amd64-disc1.iso) = f2662893c823cb587edda99830fbeffc8a6bc0bf1fc0d8a4c94174cfd196f42684bd8b32f520449a149dfc7ee4f912c1ec74f850358f194ddf28f1058e31c93b SHA512 (FreeBSD-10.4-BETA4-amd64-disc1.iso.xz) = 4687151cd19958c268738d970601464aadfd16fc1b304bf680ea8bf81ffa9635c299d6d17238bc6b21d11ebf3613358f83a5d914dbd5505b70c133519d49fd5b SHA512 (FreeBSD-10.4-BETA4-amd64-dvd1.iso) = c59759d60346a441c16689cebc915cc526bc60f72e824ac76d0b6d1514252485ad444b1e4e09ef14e3d7990acb8cfd2a020b2986466cf18db836a2604e78e42b SHA512 (FreeBSD-10.4-BETA4-amd64-dvd1.iso.xz) = a67a45db808229044faff317dccd3e1004fc0003994d37445c2fbe6357b1511511a8ebba2fe4f75d2e2b0ba7c9f955cce18ea28a5db834c3d6eb51b52c6aebb4 SHA512 (FreeBSD-10.4-BETA4-amd64-memstick.img) = 53768d7ed7d6286828b922d4c2a5d423e94ad5f8a01740c3b9ab0ba274b8cf9a65904e629e69d4b69af9b818cc330c092915060e35da2c2d35a221a38849781f SHA512 (FreeBSD-10.4-BETA4-amd64-memstick.img.xz) = d2fff154df240fe1af30c4eaaa6364a4c197159f42294b3e1b8dcc645c91ba5f458ed5709d94ba332e3d0a8b960170f648ca25beac1c2e25451f88c3011514b8 SHA512 (FreeBSD-10.4-BETA4-amd64-mini-memstick.img) = cb59355346aab0ba7ee115d3fee59e1baa488042aebc09fad4cc0e7fb43699f36a2d06efc38ee59a5391bc5da25edd9657201fa1052b0602a164dd71caee5c93 SHA512 (FreeBSD-10.4-BETA4-amd64-mini-memstick.img.xz) = 18f155d0f0e2c10e4b959c9f5bf7145e5ed28657cf857f1677afb7c6954467d4e494db09e31fa065d4a662a8c2a0851e7d5964a7088c7e6a580530df9a85f9b8 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-bootonly.iso) = 6d348f683a2062edc0ad119316f209cc59c3eaee85fa29a909696680188eae59c10eca36334c7ab0063140ed20dad1294ba80764793df419a53e17da754e97d3 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-bootonly.iso.xz) = 46bad05c18424160371cb65c10a838c0ac9ed092bbbf84b3b7e98f39a8495c63ca58a22539754bfb9700005b06195b21d2417eeddca111c74dfb963653b72017 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-disc1.iso) = 3da9113fc77d83a98a9c4ca444d3b5518db713898b45083b488781679a38416ee613fe0865962a5515913a1ce07151ca37e8aa234a66a5746a88a6f3939f7fe2 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-disc1.iso.xz) = 9d2647b26219d98207bc18467599f2a4489eddf929ec640a68a579109aed448e94a1e9d58bb1ba70d0662e8ea2d79ec1631317ac4e4a98a5f24c768332a1b198 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-dvd1.iso) = e3808e82fd7207fb6542e9fede7f424ae617baded006b357e1ef14b790fc79bfe8096920cf05553b0941634eadee0271d036c06d12aa490d9024e5b3b3e7ecba SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-dvd1.iso.xz) = 91ff0e01fc882b288edce65f70ff2a7460cc39723c0ea9fcf21920674d70454c6d4bdfa9d165d8c5eee389bc8ada2830bbbd3e1514489591721bca0579af6cd9 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-memstick.img) = e1f5587db35f8349a674f8855caa02ab143f5d92addefa4089178ec8edd931bb7711787d0cf51f7027f73ec9cb20355d2b5fc6f31c9bcaaa0329b457de0a1be7 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-memstick.img.xz) = acea341aad095b7663aa5f2349f19def16ef300d722c09a134659d1f7738c468a17cee37bd29003a82bb58e76175e21a9c86872488fbf72c5f1d08307c7c049e SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-mini-memstick.img) = e9067bc2cd17d7ab827ed41beda85ed5540f2d1debf1d5f18b9f6348153ada65e0d4a4ef381c6b2b12e520f1c43a42990d4627ecdae61e989cc15c9043f5a125 SHA512 (FreeBSD-10.4-BETA4-amd64-uefi-mini-memstick.img.xz) = f652952aa3cc419f3369bea3bd32d3f7e1d40958cdda991d3d4051c742aa061f18b54e8d8e583b8158f7b67a02a0cb62db83465bd5fb4c96de2aa06338f12a1c SHA256 (FreeBSD-10.4-BETA4-amd64-bootonly.iso) = 6ae810d442b17dec66f9fcb4135bf81bf84054283d1bc8b1f76e842488a54c14 SHA256 (FreeBSD-10.4-BETA4-amd64-bootonly.iso.xz) = d43212a23b6ab619dd7d4c9c238bd9cfd2a249eeba40d0842300c0205c1ac94e SHA256 (FreeBSD-10.4-BETA4-amd64-disc1.iso) = 9104bff980a0b940df3d0b87d54050411135f929b5fc03cbe36a0d90cfb8573e SHA256 (FreeBSD-10.4-BETA4-amd64-disc1.iso.xz) = b49cb50775e022e12d2f175c63e0b8e4d765c38d545e2abfb8ed21f537897e5a SHA256 (FreeBSD-10.4-BETA4-amd64-dvd1.iso) = a9e2b7c35573f8b8acdebb1f4af9f5bdef44922b15c45495cf049dbedfc83221 SHA256 (FreeBSD-10.4-BETA4-amd64-dvd1.iso.xz) = d9f5b2f60d3bb75560df87ed39897a7588c82d48abb4d168030f25651fea8a17 SHA256 (FreeBSD-10.4-BETA4-amd64-memstick.img) = 7db98b00ffe84dd302c3e6d44c039ad5fcf11b90ee30adff8e042567775cec40 SHA256 (FreeBSD-10.4-BETA4-amd64-memstick.img.xz) = 61a055a861ab1819f19a5fe9346e83beb3f71b50755119ca9967946093c53dc4 SHA256 (FreeBSD-10.4-BETA4-amd64-mini-memstick.img) = 164df21be1b5fdc477d3fa677d9171f37222da56d412fa9ed619012f34fe2946 SHA256 (FreeBSD-10.4-BETA4-amd64-mini-memstick.img.xz) = 8550e7da519d05ac150c08cd9c9a16b9ede3bad2a463e0f4394e04089430bf69 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-bootonly.iso) = 6acdf5168d72abdca7ea29919ae701ccdab5b131b2e656ef0a3f96425dacada0 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-bootonly.iso.xz) = 3daac887911b6f85e2494a0339c1a14b359b623783bc782b650716a5e87884ef SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-disc1.iso) = 4df5aa3bdd7795a1cf8f500472d4f70ae97092b40967970201faf4d815f984c6 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-disc1.iso.xz) = ede5f1f96baac251b5aaa57d05d592bb09a410a6185892236d42d015779722a5 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-dvd1.iso) = 667d40803f16c239cad649e045d78404b29772b48a72d57247fc7418fd928e70 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-dvd1.iso.xz) = 2ae315d2b2451880e713b0c3ce08b53bde87c8a95e3c4e6b306c2204e32f5695 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-memstick.img) = 991f547b53d6045743e5d25ca73356cd74ed3ed6c711423bade8f5b9d25d1ddf SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-memstick.img.xz) = 161bad35b40ea343eed8bed3b8a36482653ee85d52a4e39976522e0df86c4161 SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-mini-memstick.img) = b1be4c1db56ddd7d27499b02e8a9e3de6d9cac8030363dd252dcd9cf5a6230ea SHA256 (FreeBSD-10.4-BETA4-amd64-uefi-mini-memstick.img.xz) = 1630d667cad14778c4aaef954636326ba83e97d5b3d5eb00b9f84f57164c7e26 o 10.4-BETA4 i386 GENERIC: SHA512 (FreeBSD-10.4-BETA4-i386-bootonly.iso) = 900bef334ac18536002d57f46be3b5b408925d2f2735740e6869a277f3e2f2e8946aef0409947fede2740b68adfd85f49e6e3fe45be5ac7040b4a2ac47c8340b SHA512 (FreeBSD-10.4-BETA4-i386-bootonly.iso.xz) = cc0e78ea7d6e535c340ce10b2abb0d6eb9ed2c86596419f7f1d7862252a320986dfb45337407a0743e807264b0cfaa7ce8df8033f4abce4de0a02df132a2c00c SHA512 (FreeBSD-10.4-BETA4-i386-disc1.iso) = 5f2714bacc772718d703cc4fe36f7074f7c32cfa4ce610f97882dc9b09d1a331a30654046bc92e5ef5c11f50516277c146b1a7f08e65d32722bb63293462ea63 SHA512 (FreeBSD-10.4-BETA4-i386-disc1.iso.xz) = 099f01556e2d8f0db004f4b7c79bb1c779e5aebe3caa0178f9b8761b99cce5c5d585d23fd0b2074da761b34a6a78d572f5fd24969af15b6aa2a1cff426892ecb SHA512 (FreeBSD-10.4-BETA4-i386-dvd1.iso) = 8f826eb2b970f110ea0c8b216a2114782f8a50cdd368addeabd3c1ec35fe4a7eae574db0c697ec7d73e4e0b5261c507007912b0fd45d29ed17b69d1fb1bc528b SHA512 (FreeBSD-10.4-BETA4-i386-dvd1.iso.xz) = a3f92c8a8f911d85c192fb06ce7f9404e3d7a52979b0b3faca2e62c58cfd897c604236752a4298c5ce73221962eef92e76b05bc11a807ea1dd0b53726163a95c SHA512 (FreeBSD-10.4-BETA4-i386-memstick.img) = 2a8bd190d331f0aa5dd25d41ac848a2135d1968138e87b1466fe5cc2c928f2cb73a64d3b87a8300a2724ed039783ff0cfd84fbe50cc47dd714edc358fe44371e SHA512 (FreeBSD-10.4-BETA4-i386-memstick.img.xz) = 73394570bbd5552218aa5daab35c3c7f0b9040dc9c9d808b54bcba00614444e2ab995408894b0852f087304846a8cf7fbb1adee2f1e2ef75fc0b0c8b33e4e594 SHA512 (FreeBSD-10.4-BETA4-i386-mini-memstick.img) = 91d4e4a7da354126ec8fdee1d27699b4e8de0a0ee09b8bf5115b28d06c0cae35abad55b532a518c94b0e53e987c226c1c732a2c1e4cb44ec2f2cddcdfe4b9336 SHA512 (FreeBSD-10.4-BETA4-i386-mini-memstick.img.xz) = 5b330fa236cac1f2d7f205e2d061777c3ca0cbc2143bc30da8929754506dc2058bbde95a3fe068b50913cd707f0ed0b7449ab1ca8e3f221c2cbec7ad50899bd5 SHA256 (FreeBSD-10.4-BETA4-i386-bootonly.iso) = e817d5dbbaf1aa3235bc84f83e971fa335e0d07bc7719b7902fa7b7c43f734aa SHA256 (FreeBSD-10.4-BETA4-i386-bootonly.iso.xz) = 2280a947b1d8f29bf8e10471f988829cc96017facd9bdbfced7de70b78936109 SHA256 (FreeBSD-10.4-BETA4-i386-disc1.iso) = 0b52183de783281af69a9cf51f0107e5a09d20f96c487ea83675ba4d98549f89 SHA256 (FreeBSD-10.4-BETA4-i386-disc1.iso.xz) = 5e82a5a032ee8b8372cb9a444a215310496714b14dc2c019cad925b620051cf2 SHA256 (FreeBSD-10.4-BETA4-i386-dvd1.iso) = 758f7c50b32c5a5a2af265f6b27f6bead7a27620832364e0763c1072140da537 SHA256 (FreeBSD-10.4-BETA4-i386-dvd1.iso.xz) = 63ee4f4edbf75748eb92ab159cd720ee24fd44bb1a16d9680bd6ce0cdf6095be SHA256 (FreeBSD-10.4-BETA4-i386-memstick.img) = 5936e1add4a03fc0dc8f6dd3aebd3515a3f5e8053b658201c57786d8edac5dea SHA256 (FreeBSD-10.4-BETA4-i386-memstick.img.xz) = 41be71c8bb207f512b9f0342288d182a74cbdefdf9d6ca72e2a11c970ec21562 SHA256 (FreeBSD-10.4-BETA4-i386-mini-memstick.img) = fb133d7354ead9906fcaa58a48d2e1478d96d8149edf397aea44bf7570f9401f SHA256 (FreeBSD-10.4-BETA4-i386-mini-memstick.img.xz) = 5f6343dbe00e1e7c44ca2856174973ca7529876569f4017002ddeaf06feec26d o 10.4-BETA4 ia64 GENERIC: SHA512 (FreeBSD-10.4-BETA4-ia64-bootonly.iso) = 2f9f61df518ce8c2e66a804d3aeda4bdc4783121180b49c59ca6c7613ed607b3b0d8d8e9e63d6f0400bd7e425efc6098911da3d96fb518fd592d0d30e24270ff SHA512 (FreeBSD-10.4-BETA4-ia64-bootonly.iso.xz) = 63f39a92366313fba25ff680ec1ec0e0e111ade87780a8d3d936d6970466219b5a0d4302419dd7c852f373b3f6e4fdb5634d2919edce6cec6a1d70bd83799018 SHA512 (FreeBSD-10.4-BETA4-ia64-disc1.iso) = 7f8decb4f992a98bcb7a4bec53e8777bce203bbdf9badd7c437fdd9054b4412af1027ffe65ef860d5ffbafbc9e73338d7bbee9202eccc9158c56d5c289c3cbaf SHA512 (FreeBSD-10.4-BETA4-ia64-disc1.iso.xz) = d41b17c06176f7eadb77c9feacc06f3604dd90c985ff631ec9be4cd96f3c5a6b14939d3d6fd9d36686e672dd39ee0667e12256cf96bf1b5280293c565be2fea3 SHA512 (FreeBSD-10.4-BETA4-ia64-dvd1.iso) = 054d49110a5d1ccee7ac9064c4e3f792a24becc5e2b5b60e6ef1ba13acf92876d4bbf385982a5448ca9106959fa53147aff55745962040f1eb26e01a6e2fabd6 SHA512 (FreeBSD-10.4-BETA4-ia64-dvd1.iso.xz) = 5033813e12d46bdc87369cfcdde2fcd305b2937f178eec970b46a592991aa0406487a03d11ea4c991a3e53f1a7671e04d37fa25958e84945cc53cafa5036c118 SHA512 (FreeBSD-10.4-BETA4-ia64-memstick.img) = 81e2fd40946a30485e1167483ce9c53120beeb315a6fd8ceef78d52c4c9a2e220f3649959ca592d105e30b1b19160c98af4f467bc2239c9e49e399af63731297 SHA512 (FreeBSD-10.4-BETA4-ia64-memstick.img.xz) = 59bf0265bdb8bfab4e1c3ee80b5c53687e9b580c2e45366ff26e4597496708627c36351b90f3aeb7047177be38d2c2b2ee7a9c359d10ccbfc7f7602dbb7a076b SHA512 (FreeBSD-10.4-BETA4-ia64-mini-memstick.img) = eaf99401320c92c7ef492501a31496ab2c39a05eb312acd74d93b5f86c4e0cdff06d6879505e56c48bc994b41be1b011e41d30fcb0ea7ed0ac0cc39ea4834a07 SHA512 (FreeBSD-10.4-BETA4-ia64-mini-memstick.img.xz) = 7fa941bb26ffcb9dbb0b85a2d13cdab3d96daa9f37b9931245e19f287367b4fa9708dc896cd213da23f5b1d54e08da19073ae542327e5def4882911e0418b875 SHA256 (FreeBSD-10.4-BETA4-ia64-bootonly.iso) = a2b63b7c8bbde5785508dd6bf4e97d86d477a2e9bcdeb0d21b45a999601d9faf SHA256 (FreeBSD-10.4-BETA4-ia64-bootonly.iso.xz) = 6b980c1edda11e56b08d67387deb153c9c9bab2a6ffd62efde0a07305cc8c54b SHA256 (FreeBSD-10.4-BETA4-ia64-disc1.iso) = 71ff674f98e9f443ac618a048821a72e7316323ab81db303006c161aa6a16045 SHA256 (FreeBSD-10.4-BETA4-ia64-disc1.iso.xz) = 21dd28dabcef57b28241c4c76101803c4722e8ec60e9088587b8cfe53cd7c1bf SHA256 (FreeBSD-10.4-BETA4-ia64-dvd1.iso) = 5c8fd516e3470ebb1678c15fa449c027423dbf2ca9e85870dae9518284aaf42e SHA256 (FreeBSD-10.4-BETA4-ia64-dvd1.iso.xz) = aff1e1ecfa8ef44c02b5bb66105aa31aa2ffd3d5c8612716a97f643610c92595 SHA256 (FreeBSD-10.4-BETA4-ia64-memstick.img) = d4f86bbae42864017c0a6a27ef76037c088e43596b848a358e96bd0d7cf4d556 SHA256 (FreeBSD-10.4-BETA4-ia64-memstick.img.xz) = 816f2679cad36390f55f4ca3bcd46445c07884a96f87dfbe2ab1d108e19ddbe2 SHA256 (FreeBSD-10.4-BETA4-ia64-mini-memstick.img) = 6ff4166732e4cafabfe8ad6321ec3553105af01dccd70e3cc9ff8f6a63135636 SHA256 (FreeBSD-10.4-BETA4-ia64-mini-memstick.img.xz) = 27c80482267dcf16e19861eeb896fe6b9acd6c99f7b92facb66092ec742939fb o 10.4-BETA4 powerpc GENERIC: SHA512 (FreeBSD-10.4-BETA4-powerpc-bootonly.iso) = 8c4fa3333db71f8643f3a982e4e925d4ae4697252942eb5de956d3592c4ebd40a8f55b8bb245799e584bb927527aefabacb37b90a171feba04d8ba2a43a4bf8e SHA512 (FreeBSD-10.4-BETA4-powerpc-bootonly.iso.xz) = 7536875841107a8eff8b5aa85e61b7c807acb7e4a8f83c8375b3120a98e684ce846de4791d5ad4b1fc01523153bff2f82ee4b134fd470288ed16dbfb57ea2b99 SHA512 (FreeBSD-10.4-BETA4-powerpc-disc1.iso) = ac825f3ecb668228cf504c40b77f4c84390563e34497ef62a7f6a6ed14d2065bb009a0d7d94ca5781e133d83a14bfcc0deb135310d12106d32b08276112e579d SHA512 (FreeBSD-10.4-BETA4-powerpc-disc1.iso.xz) = bccca943c7e63507d4435d0773677ce6fe706468708ec56f120d1e9eb616419c2d8441c8628f56809569c1a92ca78621db8ecdec1c606c1c66473249f6d3bdc3 SHA512 (FreeBSD-10.4-BETA4-powerpc-dvd1.iso) = 5c4c537f5f97cea23368080a6990b64c781f8cdfd19d48c4078549bb0db8a6eccac1185433b9f53131e2e74645ca43784092f0aedd3576e86bbc0f28f8281705 SHA512 (FreeBSD-10.4-BETA4-powerpc-dvd1.iso.xz) = 745db9ae1fd5be733a1ff86a6922128ce6f34a328fc93fb5a7b3fdf7786696aa509b17aeeffca47e3a5eb281837a06e8fd26b928d7b6943f3ea451570890c52a SHA512 (FreeBSD-10.4-BETA4-powerpc-memstick.img) = 47ba3ec5e31aa4f6bc09479fab748d5ddfedadff7c852c51732f39d28f91e18ddba86d104a14008736616b47f6e48b08fa767e4c104ab0393e081b6bae481ffa SHA512 (FreeBSD-10.4-BETA4-powerpc-memstick.img.xz) = 25eeea998aee536b7f4d044f59642765418efa6bc7cb0260b1bc352f27f764f423d39ee691d5e241d202342f837beb98c5df1c578c29ecd70d7a557021f8d3a2 SHA512 (FreeBSD-10.4-BETA4-powerpc-mini-memstick.img) = 3a8f505f650a9f3aa8c6cf8694f6928041c6788337fd7c98a9708147b22799f3852b4563ccb0453ec786d7e9759931dde693fc81019c18eb14299ec8c1b848dd SHA512 (FreeBSD-10.4-BETA4-powerpc-mini-memstick.img.xz) = 4c5bd2e9044527a85f4fbd94e1d679ff89d03cef034b3da1b2b39cd40d53b8ba27773e515f4284d90fe05ca1516fe1a17ed901d4d61ccaaeda3f0263dfbbf745 SHA256 (FreeBSD-10.4-BETA4-powerpc-bootonly.iso) = 7291e0d09c634205c61bdd886a178b29dfe25929e5970ee920991deaa7c4abae SHA256 (FreeBSD-10.4-BETA4-powerpc-bootonly.iso.xz) = b67bc30294851bed6dd34037fe0b28ff3809de3ad80474aa0af18286e140b7af SHA256 (FreeBSD-10.4-BETA4-powerpc-disc1.iso) = 5cb8011c32606d394524b3ea97e16f7edae05fa6086470c081f9948b46d37500 SHA256 (FreeBSD-10.4-BETA4-powerpc-disc1.iso.xz) = 2ede17783b92d2872ac2ec55f371bda8eeb7ffea28bfdd7af127d06772d06581 SHA256 (FreeBSD-10.4-BETA4-powerpc-dvd1.iso) = 35ee41d1c3eabe50fde14bf4ecc1dfa4489672abaa5cf18cb5eb442b2e1ae10c SHA256 (FreeBSD-10.4-BETA4-powerpc-dvd1.iso.xz) = 96e2110de18a4121ebd564985415803f90e13d7633c661846f7c0439c85df519 SHA256 (FreeBSD-10.4-BETA4-powerpc-memstick.img) = 12a3b2c126093663fb986ed9c1b0dcdd12b3bccf09d5833b0fadc0c2a7d22e03 SHA256 (FreeBSD-10.4-BETA4-powerpc-memstick.img.xz) = edc9fa2b99c691e2a422977e42cbb17cf6121e2f7e52a382982e43b5bc767d61 SHA256 (FreeBSD-10.4-BETA4-powerpc-mini-memstick.img) = 3c674821be5d262338042d497fdf9e076e3617087a3f97aa938c38e04c7ddfda SHA256 (FreeBSD-10.4-BETA4-powerpc-mini-memstick.img.xz) = 4173a7a57710e2c8f3e4030c481183023d78aa9ea138a538359e46af51b0a13b o 10.4-BETA4 powerpc64 GENERIC64: SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-bootonly.iso) = f68695955418a53638509b7a0abc3f3a8a98bd5e39a1574a867876b7789faf3472086db2a95e2f4b7dbb8697463a9125e6ac865aa05bf63ad9003699c12891df SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-bootonly.iso.xz) = 0fbd4bf87907b132b4a5fc5ea8c6d4c76c3a7a37b7164c57efac22c51ea0171a20cc2e0ca2b3cf2c5e334dc76880dbef0a7a788bfe555ca5b6becf05b0586754 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-disc1.iso) = 447e747c82496897844d2edc1e772f0dd05fe2f0af1c28f75515096266dfbded7ecdffc6a9bd9753ccf453dc4a41d6d83d5dacac814dd1b05dc4b1bd9eadf363 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-disc1.iso.xz) = 0685bbb159d9bc9b300011068b88adee7219e49bdfb322284a0235ff93d584c677adeb1396a60bf440856f3ecfec223617337b06b710941128422c20b1be2db4 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-dvd1.iso) = f2f1bb8f12aee2f4c74fb537e60a1eda5ce78fd88a24262537fd66b19317a1032ebaf8277bba692d77e3fdadda0b22b2fe9c4498671a67578dc9734a918dff1e SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-dvd1.iso.xz) = 1fbdbad765ebd54038377f57848b5553d72fc15c2aed3b08344c1cc4b7e6e6e90ea89a0a32b83464b7b9d55558229b7bd9b3618ee4233d22d10139b409be5cd6 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-memstick.img) = 477c6146c1b46e60e4ca01e65b83b0ab106cd7c663254639f1e92543196740a5444b1aa67abc05239258dace3a4ec266215f39f1f6d521867e6053830489c8b4 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-memstick.img.xz) = daeced3f07ca8e47b9292602f6907ff7d8aab7a8525c945d5d48ec57e5a652a33d0c6312eb13be0f5d6baf4644d23192716b03e34723c888188e9025feebf8a7 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-mini-memstick.img) = 7b7e5545d567552db4ae6e5d929364ed62e0e74cfd4a93e253ae32e03cb855f57da14c1f90565e83b7c4066f17397d47e1355bf574b3b33982479d6d7dc5f505 SHA512 (FreeBSD-10.4-BETA4-powerpc-powerpc64-mini-memstick.img.xz) = 621fe5895c3a62b7a6eb5d7e7b9d6d4af513419c4d47dfe939e1eaad7c922776dad279ed421f09a2ebf1aec6a2dc29264a2f4da5cc0df6c5c9f6f5cdf511ab18 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-bootonly.iso) = 271adb1e531b9b7c58124a9f58a84e252f7acb64d2fa17893103e902bf24da0a SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-bootonly.iso.xz) = 49e9f4f5831fcb7bba8238c46ed7a68316e3887cd2bb637a9367f2bf9176d6ef SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-disc1.iso) = 642d80a6c0245be5b31d8cd81ae5b6a68ae6c4c8e40e08cad2bc407a7703cd67 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-disc1.iso.xz) = 7094b13740222673fd5c2670bd07bdcea7d58c1a49a8b8dc1df3552bee9d8656 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-dvd1.iso) = 5fe5e37a4db9865a1c0e157ef12c6f93d3f9a84d20a7793632fe05e61fee0b07 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-dvd1.iso.xz) = e4d2e11a2859fd983bdbb59ac28ecf6e124b3c7aec2d2b610b1d61138facbfde SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-memstick.img) = f9c447b65a8b17bbc6da203471d8abf60b7adcecd475baf457ceea2c88219ee1 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-memstick.img.xz) = 263b59bb9e1756bcf7edd90f210fa625f8458255d58d04a77e80fda3d1acf298 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-mini-memstick.img) = 8312f9102f4b9f030950e7d21a9bbe19d98cdbe6fae1509584d0aec6ba666618 SHA256 (FreeBSD-10.4-BETA4-powerpc-powerpc64-mini-memstick.img.xz) = 6017afd0c7c1e69d3cbb47af6f4270b626b7b7a5baefa00394d810e469c1329f o 10.4-BETA4 sparc64 GENERIC: SHA512 (FreeBSD-10.4-BETA4-sparc64-bootonly.iso) = ef0253e2feb13cce61870b38d6c39545ccc432fe68e9c0fa4c60953e6ba7a910bd1afabe6710b638d1c7a3d6767ea6058489adfa454193fba2f8efa2154da816 SHA512 (FreeBSD-10.4-BETA4-sparc64-bootonly.iso.xz) = 24a75862e2e0ffbe0d066f0a03b3f3980820e15eb55999c294c0de51e815ea6faa06a7963fc1e9186cf4bc8ba439048c3ee3c1d7bc9805ae163310b326cde527 SHA512 (FreeBSD-10.4-BETA4-sparc64-disc1.iso) = 46ab5a473e85f4798c06dcad40f81022d15ac03b33ec1f3a7994b56e75c07b3da601c2f9b2bbf9eb07e8492b678b9e44d8a76e9b7d873c751b9c0bef735a8beb SHA512 (FreeBSD-10.4-BETA4-sparc64-disc1.iso.xz) = 16a57044876a3bd7d7415ab12aca3d8e9a0e0047e521dec5a58dcb822fd9d9751c993310f1ca7027a41db24da5502868619a71f9d6d7f7d032b90e2140edf858 SHA512 (FreeBSD-10.4-BETA4-sparc64-dvd1.iso) = f0af0c21a00b660c4d62cb3c15427cb8d1d4599f07a69cab2d8073b1817ff645d5e3b26f204d81d7a295be62781c7163e9e7df558a09869993bbeedc70efcf64 SHA512 (FreeBSD-10.4-BETA4-sparc64-dvd1.iso.xz) = ef3a013b48755000249c053ac3b8b3c0b79a584f37e1faca5fd49e147205ba86882c72c16371267db051055f6115c407322a572ccbffa01d780dee1b1a1602f8 SHA256 (FreeBSD-10.4-BETA4-sparc64-bootonly.iso) = d1cfc64306a26d5821a52da5fdae5e514f3e24572227e78d30f0a547990f7cdf SHA256 (FreeBSD-10.4-BETA4-sparc64-bootonly.iso.xz) = da1fda43ed9347d6b163f4b1a3e0dc48f6843d97a8ec859270a475010e33792b SHA256 (FreeBSD-10.4-BETA4-sparc64-disc1.iso) = 2e4e897dff2690c7751d7ec033f91aa3f4982fc3b6c01aba48d28a4ccc3156dc SHA256 (FreeBSD-10.4-BETA4-sparc64-disc1.iso.xz) = 5cdd6e329a3f9bdc4ee99a99277905f2f537016e2327e8004f68cfe841bb0914 SHA256 (FreeBSD-10.4-BETA4-sparc64-dvd1.iso) = 1121da03cb2e9f1f36a305614cd7bd19a796c6efb069af1f68685d8ed0a1dff3 SHA256 (FreeBSD-10.4-BETA4-sparc64-dvd1.iso.xz) = 591879bde667894db7f39bb2552f5f3eee13bf2eab6a3a0aa1df7b56b20f8d1f o 10.4-BETA4 armv6 BEAGLEBONE: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-BEAGLEBONE.img.xz) = d183e4bbee43329806942aa0e6b3b67202e0966e33e5aa19f5861746a9958a0dad029f8f95a2b28b98c356e8d0c3f4abd8f010e68e79ab9c78fc332402033de1 SHA256 (FreeBSD-10.4-BETA4-arm-armv6-BEAGLEBONE.img.xz) = a06485bbd583d5b02dcfa5178160f3727868b4c9e8d261958a99e6da61806223 o 10.4-BETA4 armv6 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = 6a5c11dfa03f6c079b0929ecbfbe9f64159652d024a82c6230460e7c01a4cccb7fd03c7f7ecb4722d51e4da954359a4e0c0baddcaf9f6918d93bc322af710b52 SHA256 (FreeBSD-10.4-BETA4-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = d0330e1a5cc672be16a6413dd941dcb9bc305bb47ef43c6be6bef56275acb3ae o 10.4-BETA4 armv6 GUMSTIX: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-GUMSTIX.img.xz) = 042e8e5887cc48c74ca1abf30410197082605024c810bb1d0e5a9c3eafde1edaa8bc7b1c420cb5ac1d6a281aa94e57d55e258f792ca7be7b65c285ed809c2061 SHA256 (FreeBSD-10.4-BETA4-arm-armv6-GUMSTIX.img.xz) = 402ee0da0e02d776f51b88ae847fcf17f6e49f4820dd8f52c4b40d4bc8d7e9a0 o 10.4-BETA4 armv6 RPI-B: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-RPI-B.img.xz) = 18f0ffee79d98e86a8ae07b53702d8ca76c9527370e867119668545a0c83bdd2acbe3009ab00766a158e9c45ccb4c7b677aee2c4e100f03a7278bdcc1bed2a0b SHA256 (FreeBSD-10.4-BETA4-arm-armv6-RPI-B.img.xz) = a2e6208732933328ad47f75bab0727915f116af959ce5fdd79fd27cc5d154fb8 o 10.4-BETA4 armv6 PANDABOARD: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-PANDABOARD.img.xz) = fa6f8d069912749e09f539134cfe1ee2989a96dd31feeb6d78228837fb0eb3a9836caec1cfe54b1683f131daa6065b72962b7adaa30187c4ee86cba2607f663a SHA256 (FreeBSD-10.4-BETA4-arm-armv6-PANDABOARD.img.xz) = abaf6a1d8da7e90d863b48b627da70e1fdf5788d59cb67933d1c3ec6d06e01bd o 10.4-BETA4 armv6 WANDBOARD: SHA512 (FreeBSD-10.4-BETA4-arm-armv6-WANDBOARD.img.xz) = 555c144ea342a724dba5efc1ecbd5ac754195fd93f334486164c048bbf533184d2aa207697b834f2bb39a3b0c95c412d04ff51c3435e02065d73d056498e49e8 SHA256 (FreeBSD-10.4-BETA4-arm-armv6-WANDBOARD.img.xz) = 5b77eba4f6014e6f2da811f3564ee8801fe52d57e9b36f7b6f58e5215636b87a == VM IMAGE CHECKSUMS == o 10.4-BETA4 amd64: SHA512 (FreeBSD-10.4-BETA4-amd64.qcow2.xz) = e655a87d6d2878d257fab678ccfc5f2a4d8e15e55592b511cf0f37cb923c6417af337ca90bc97cfc6f7c5e068352a79b94020997a0b7882f4d759ca79170f0b5 SHA512 (FreeBSD-10.4-BETA4-amd64.raw.xz) = 2992974d3a82e583096ee4a91ab4237e9780d215b40999ed65d6ef1d4231e1fda447c9d51b5706dbe79d9b5bf5d57630d8ea1bbb3bab22975ae9e64c1ec0f854 SHA512 (FreeBSD-10.4-BETA4-amd64.vhd.xz) = 350fa14ad74036bec0f1934fecc556d5e74255ae964317d2e4049b2a5ea1cee5193fbce239cc83f030e0dc22fdabcd8267405e76a49a5ffd96a256e5b202fa99 SHA512 (FreeBSD-10.4-BETA4-amd64.vmdk.xz) = e178c74dcacfa0959fd0a4df5de57fab615143a30bf319179f679991e0c4a16eae62d494f7cd9e3966a60c32ff1d455204820789a0b5c3d7f388b4314eb15330 SHA256 (FreeBSD-10.4-BETA4-amd64.qcow2.xz) = 04be4beb3ba3dd8f3f3945095c107b7f6e5539413fe57737b49e47f52d3e5e78 SHA256 (FreeBSD-10.4-BETA4-amd64.raw.xz) = 26c1de5e2a73574b18a6740e1e1a54474606f9b2d9d850bd3b048168f371d8cf SHA256 (FreeBSD-10.4-BETA4-amd64.vhd.xz) = 6c6dcce0d677c691e5f857018781148f9eedc12da0549671f9c9204af0ea4fa4 SHA256 (FreeBSD-10.4-BETA4-amd64.vmdk.xz) = 7a6dcf3c5dc677cb1ae6fd619fae3127b2b3315fb6cde30f6b51365f9e6a95dd o 10.4-BETA4 i386: SHA512 (FreeBSD-10.4-BETA4-i386.qcow2.xz) = 49d3769ee46630b71346671682074cc8d2c0ac0e0659931b0c91744ffe1056a35c07e06b0c915896596bc0efb782acff970cb3ef1bd191c90a82177537162d2a SHA512 (FreeBSD-10.4-BETA4-i386.raw.xz) = e3c05124383715c956b13a972e59e3f354448d3020bc8bfd35ffc95f9daa379ddbe6919b6d37620df52a88355d9c77627805cfc051f20b2b9839f6a0ebefb3e6 SHA512 (FreeBSD-10.4-BETA4-i386.vhd.xz) = 69339a81b9a6c3b7e5c2fe41834e64b7911758e4920aaba8e9569fa211f0a1c1d48accda45068aead45239b4578694359e62cc1c43584a805dad1e063f50057b SHA512 (FreeBSD-10.4-BETA4-i386.vmdk.xz) = 721d909bb3b146e1f5c03e1842c2bb88c9d77762fb1c25ff7c99882902e5056d785879196118a2482a4ccec63371397036886237c874f2a2d84bf6155ed8fa5b SHA256 (FreeBSD-10.4-BETA4-i386.qcow2.xz) = 85e01024271615f6c80258cc55effe4733fea59b54ae6204bc251466f9061ebb SHA256 (FreeBSD-10.4-BETA4-i386.raw.xz) = bdbc68e8e51e77a146d2f4902ab287474bbf2e85b27972cb739478b9e0005754 SHA256 (FreeBSD-10.4-BETA4-i386.vhd.xz) = ca1dd98229954321147ece044a25b7d86debe19501d91db46d38d4583069ed88 SHA256 (FreeBSD-10.4-BETA4-i386.vmdk.xz) = 1e7158274a79b6ed74efcc4b663b860606ee3cd869535b2e994f89ef68942d4e Regards Marius -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZtGMWXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1M0Q5QjQzNTVGOTU5ODBGQzVENzZCMDIy MEI3MERFMTNGMUQxRTRGAAoJECC3DeE/HR5PXxoP/3KLPIFdplj43YJd1/J/ijuC X3TEPhgq0HViKZ1PbIfeYhlLrpWqRXKjlEIOdWW1DIeCuBUmFF9YnF8/FZLTD8Py mxqmVZUBBVjv+Xe2NUzFEX5NXRQczYnqtosYpmOP0MQkKceaPB4uzt+r9sOjANSp +nShvcgq+glEGHErc0CJEmetEe+I3OVLylsq24zB5d97tyBHfS7qa+jLp+JRgQx8 ghuNAHNMCAp/9ekQs3GsLzSIsgLOv8PTHmH2K2gELvOZCs9LAevxwzKp4bJSJ1EU IDf9Kp3XjYr5ZZtOhjlDaDvxUXdXqnWLk/SK9oyRocYouCM6GSlftyHCxRStUOwd CPAnXBwFcmZruMnVQ01NXNxIBNa5cEGfIhX5WBpyP9sc3yWC3vR3vxV/Y/RO0YCj 7murX29FG9SQCKN2giIKrJS/5GJY59QrrMVT5KKNztEGeg2+EIfbgJnMqpfMz0yB RULCC20opBghN/RDZhpLPpyGUA4TI0h2b+c9/oJSMKbKSqFk0VGzmvGRATEI7Qtp fYUv7gT8A1CeBNwWmYqp+83qI2GVkuB74SONV1Xa29M3orDehet8LlysurRD0Oeu yNzhgqP+TOWjM4s3WLEGigeBy00uBovenvL+HiaNp5XaqKJbE5ZDuZi9WTy0PS3v h5/MGcaNCkBNH0xiJbYb =cM9b -----END PGP SIGNATURE-----