From owner-freebsd-current@freebsd.org Sun Oct 2 00:58:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00024AC40CF for ; Sun, 2 Oct 2016 00:58:02 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 C4FC3E8F for ; Sun, 2 Oct 2016 00:58:02 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x235.google.com with SMTP id s13so52090254pfd.2 for ; Sat, 01 Oct 2016 17:58:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=o7Kr4BMc60rWbrYu6kh27fvjN8GMff9EuunwRdIP52s=; b=UDP5fN5UifKWrKCAJcRhL2C3EJxn4gt+uXacpDhtSoKUWiDfu1bfozRq0Tb/MgEMmt Q7rJo/yXOfKDqC49wi0QqBEsL3xj+DKK6IpZdH1COk4xV2aAVYZecVdiHltYq54oIHLo uI7CWJ13WosVUBtyK0wlN9X0ItDu5kZoirpnh/QZjN01KEDQgbRsx/A6hPPePSbf3YCE t2ITA9KIBGVMwFybnU+mmR49I5sScvjUqRkzP6AKugxOq514KDmGzZVLbmK674EsMrVB RGdhRIhFw9d0q6fyNti3ZMADKf2Ly83LCLn7PQh6MecwGzLy/uNz3QBUgBe7wgAk6HjW N3Iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=o7Kr4BMc60rWbrYu6kh27fvjN8GMff9EuunwRdIP52s=; b=AxFSp1vC0lD+rtvYkbt8fgttWwqGOTJ6/r6oySWE1zWwek0QvGK4gdl4VaK8WtQJT8 jdIGILPV6nN9rwF0hCFMfc48GNXY3BiZAA5zcGVTUPrv91XGzMB9RQnWkqTszl1PIXoG KOgmu4ZmyzZL6g2v20Ll7JdxNRxlZEaZYqmQtcYdBVXFDTccbjRKHoEwJqAZJJmsI6wR pZtL6nVBq5EZxLVdmufiAPVASo/WR0onIZnzuypcAYIAhJSbXuvDLUyFwOEP47QyzEe5 DY4L5lk+JUJAW4tezGZmtYGMWC+BSajP1YiGu+k6sHHQtFWsc+EfBUkbtm6kC5yvPA+2 zGTA== X-Gm-Message-State: AA6/9RndY6kbmJKowk3LBwNNTpGJYQSAbYY+d7KdFJ/4SIDBtS15gIWkvJ23gdQ0XHcMww== X-Received: by 10.98.201.215 with SMTP id l84mr24578985pfk.10.1475369882352; Sat, 01 Oct 2016 17:58:02 -0700 (PDT) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id fm6sm37343921pab.37.2016.10.01.17.58.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 01 Oct 2016 17:58:01 -0700 (PDT) Sender: Mark Johnston Date: Sat, 1 Oct 2016 17:58:00 -0700 From: Mark Johnston To: Franco Fichtner Cc: freebsd-current Subject: Re: rtsold debug message level Message-ID: <20161002005800.GB47402@raichu> References: <6B3DF4FD-CBA3-41F9-A09D-ED5D7929BC8B@opnsense.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6B3DF4FD-CBA3-41F9-A09D-ED5D7929BC8B@opnsense.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 00:58:03 -0000 On Sat, Oct 01, 2016 at 11:55:57AM +0200, Franco Fichtner wrote: > Hi, > > There is an informational message rtsold that should > be considered debug, details here: > > https://reviews.freebsd.org/D8108 > > Pardon my question: is this the right place, and/or > who should I contact? Committed as r306571, thanks. From owner-freebsd-current@freebsd.org Sat Oct 1 13:37:32 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A787C049A3 for ; Sat, 1 Oct 2016 13:37:32 +0000 (UTC) (envelope-from robert.burmeister@utoledo.edu) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0C4D51217 for ; Sat, 1 Oct 2016 13:37:31 +0000 (UTC) (envelope-from robert.burmeister@utoledo.edu) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id BC12D3290A38 for ; Sat, 1 Oct 2016 06:33:02 -0700 (PDT) Date: Sat, 1 Oct 2016 06:37:31 -0700 (MST) From: Robert_Burmeister To: freebsd-current@freebsd.org Message-ID: <1475329051012-6134033.post@n6.nabble.com> In-Reply-To: <57EDE9A9.1040304@UToledo.edu> References: <57EDE9A9.1040304@UToledo.edu> Subject: Re: FreeBSD 11.0 i386 buildworld failure MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 02 Oct 2016 03:04:02 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 13:37:32 -0000 Refreshed source 20160930 and make -j1 buildworld still fails: ===> lib/libdevctl (all) clang -O2 -fno-strict-aliasing -pipe -march=core2 -MD -MF.depend.devctl.o -MTdevctl.o -std=gnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments -c /usr/src/lib/libdevctl/devctl.c -o devctl.o /usr/src/lib/libdevctl/devctl.c:131:6: error: use of undeclared identifier 'DEVF_CLEAR_DRIVER_DETACH' DEVF_CLEAR_DRIVER_DETACH : 0)); ^ /usr/src/lib/libdevctl/devctl.c:130:32: error: use of undeclared identifier 'DEV_CLEAR_DRIVER' return (devctl_simple_request(DEV_CLEAR_DRIVER, device, force ? ^ 2 errors generated. *** Error code 1 Stop. make[5]: stopped in /usr/src/lib/libdevctl *** Error code 1 Stop. make[4]: stopped in /usr/src/lib *** Error code 1 Stop. make[3]: stopped in /usr/src *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. make: stopped in /usr/src BEASTIE# -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134033.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@freebsd.org Sun Oct 2 14:22:21 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A209AEF18C for ; Sun, 2 Oct 2016 14:22:21 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3A438184 for ; Sun, 2 Oct 2016 14:22:21 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 39727AEF18B; Sun, 2 Oct 2016 14:22:21 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3917CAEF18A for ; Sun, 2 Oct 2016 14:22:21 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 065E2183 for ; Sun, 2 Oct 2016 14:22:20 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 459AC273B3 for ; Sun, 2 Oct 2016 14:22:14 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u92EMCCq003922 for ; Sun, 2 Oct 2016 14:22:13 GMT (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org Subject: Mime issue on -current From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3920.1475418132.1@critter.freebsd.dk> Date: Sun, 02 Oct 2016 14:22:12 +0000 Message-ID: <3921.1475418132@critter.freebsd.dk> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 14:22:21 -0000 I just updated to current from source, and found that evince did claimed all .pdf files were "application/octet". The solution, after some digging around is to run /usr/local/bin/update-mime-database /usr/local/share/mime Which is something I pressume some port used to do, but for some reasons didn't do this time... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@freebsd.org Sun Oct 2 17:15:51 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECC9CAF15BE; Sun, 2 Oct 2016 17:15:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 C42F56D7; Sun, 2 Oct 2016 17:15:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id e66so101352936iod.1; Sun, 02 Oct 2016 10:15:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=CjQ8pUtRofyoGPvL+myDP+JcExP/txPUYlk7M/MU3P4=; b=pXfPwwLccxocC+8dilQkyXn22CqOabQv1GCWSGHVMS2ovu5yD5rARxMpXd/B9yQUwv RbipcABYOmiOZLben/636h8gFsApRiE76r3L2ltISuXkcXuMMR0owDii3ichh5bvsIJB cIuAg/YgmDyZq+NQuyGcMJ4BGo530nSu72Rn4zCBhJheyF7qK/TKc9Er1LoVjEKrgGhr ImcMvQPnrLluXET/ENEZZB5q+JRPQLYwXgGx3zLccsu4RU+by0UASmg+GZdS4ElHsT7C gyaWLFDmBPiFcCyD9ynAxS+O3Je+EW0i2zKjj490KGLxobhWis5wVx+zWGUNKLjdMyBG JNnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=CjQ8pUtRofyoGPvL+myDP+JcExP/txPUYlk7M/MU3P4=; b=nNLecA8GyQX4nH/ne+YzM64e7XcIEnBPqsnRwXwsVoHJREJULNPReQMdPGXVzDQ279 PJ51ORtis0ipm6HV+AtKs3Y96Pn+Gn9yxKBIaGP9M27Mkui0hZ7BKtbJ4ZoNgL8bRLBX WzlXkFLqK6La2S4kXAtLuqY9UlvKMDm7vwSF8Md4SMQeZGInkW+hQpXzZ0sh/2Mfk1TX kLEdNMtSuIJXH59jSVXvTObLtVrjNpKHKC33fd8J0fJdaHmfVevfy7jLP7YbK/WQinKu 8+S3TdB0+R6MHCaMfyVRSc6jKMGusDufRgidNUbsblO15/LkxALoLSkzAjL8WeKgldVt CUXQ== X-Gm-Message-State: AA6/9Rk5HFJOu00iNdMvTUCaGxG4r2GSXw+fyL5dxEovvZG9gcDY9f3TZ0XLc8T2r5p18zFHdpkTWLk5XImVdQ== X-Received: by 10.107.6.166 with SMTP id f38mr1005131ioi.129.1475428550578; Sun, 02 Oct 2016 10:15:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Sun, 2 Oct 2016 10:15:49 -0700 (PDT) In-Reply-To: <20161001150924.GA48641@ns.kevlo.org> References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> From: Adrian Chadd Date: Sun, 2 Oct 2016 10:15:49 -0700 Message-ID: Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing To: Kevin Lo Cc: Andriy Voskoboinyk , "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 17:15:52 -0000 hi, can you turn on debugging? Do you see RX frames? -a On 1 October 2016 at 08:09, Kevin Lo wrote: > Strange, rtwn(4) stops working. I tried to scan for the available networ= k, > but it just returns empty results. > > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote: >> >> Fri, 23 Sep 2016 10:18:30 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo : >> >> Few more questions: >> 1) does it work with h/w encryption support? (enabled by default) >> (if 'yes' - I will remove 'hardware crypto enabled' warning). >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then transm= it >> something - if it works then AMRR will print it's current status >> periodically) >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n) >> (see r92ce_adj_devcaps() in sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c). >> >> > It works for me, thanks :) >> > >> > Kevin >> > >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote: >> >> >> >> Fri, 23 Sep 2016 04:58:40 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0= =D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo >> >> : >> >> >> >> Thanks for the log file, >> >> >> >> Tx 'device timeouts' should be fixed in >> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa7= 67034a89f5 >> >> (currently I'm reviewing PCI-specific code to see if there are any >> >> additional >> >> issues - e.g., there are no Rx events in the log file). >> >> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote: >> >> >> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0= =B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo >> >> >> : >> >> >> >> >> >> Hi, >> >> >> >> >> >> So, the driver was fully tested. Thanks! >> >> >> Can you set dev.rtwn.0.debug=3D0x829f for RTL8188CE to see how big >> >> >> the problem is? >> >> > >> >> > Sure. Here you go >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt >> >> > >> >> > Thanks, >> >> > Kevin >> >> > >> >> >> > Hi Andriy, >> >> >> > >> >> >> > First of all, THANK YOU! You're doing amazing work! >> >> >> > Second, I've done some testing on the following devices, >> >> downloading >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from >> >> >> > ftp.freebsd.org: >> >> >> > >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS): >> >> >> > rtwn0: > >> addr >> >> >> > 3> on usbus0 >> >> >> > rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R >> >> >> > >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU): >> >> >> > rtwn0: = on >> >> >> > usbus0 >> >> >> > rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> >> >> > >> >> >> > - D-Link DWA-131 (RTL8192CU): >> >> >> > rtwn0: > >> addr >> >> >> > 3> on usbus0 >> >> >> > rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R >> >> >> > >> >> >> > - TP-Link Archer T4U (RTL8812AU): >> >> >> > rtwn0: = on >> >> >> > usbus0 >> >> >> > rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R >> >> >> > >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU): >> >> >> > rtwn0: <802.11n WLAN Adapter> on usbus0 >> >> >> > rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R >> >> >> > >> >> >> > - RTL8188CE mini pcie: >> >> >> > rtwn0: port 0xd000-0xd0ff mem >> >> >> > 0x90800000-0x90803fff irq 17 at device 0.0 on pci1 >> >> >> > rtwn0: r92ce_attach: warning: hardware crypto enabled >> >> >> > rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R >> >> >> > >> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work: >> >> >> > >> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used >> >> >> > rtwn0: device timeout >> >> >> > >> >> >> > Kevin >> >> >> > >> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wro= te: >> >> >> >> >> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD= =D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Andriy Voskoboinyk >> >> >> >> : >> >> >> >> >> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn >> >> (integrated >> >> >> >> into src tree, so it can be built with 'make buildkernel' / 'ma= ke >> >> >> >> buildworld'). >> >> >> >> >> >> >> >> This the last stage; once all reported issues will be resolved, >> >> I'm >> >> >> >> going to merge it into HEAD. >> >> >> >> >> >> >> >> > Hi everyone, >> >> >> >> > >> >> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers we= re >> >> >> merged >> >> >> >> > into a >> >> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); th= e >> >> >> code is >> >> >> >> > available on https://github.com/s3erios/rtwn repository. Amon= g >> >> >> >> bugfixes / >> >> >> >> > code deduplication, there some new features too: >> >> >> >> > >> >> >> >> > 1) multi-vap support (one any wireless interface + one STA >> >> >> interface + >> >> >> >> > any number of monitor mode interfaces). >> >> >> >> > 2) few new sysctls: >> >> >> >> > * dev.rtwn.#.crypto - controls how to use hardware crypto >> >> >> >> acceleration >> >> >> >> > * dev.rtwn.#.ratectl_selected >> >> >> >> > * dev.rtwn.#.ratectl - selects current 'rate control' >> >> algorithm >> >> >> >> > (currently only 'none' and 'net80211' are supported; RTL8192C= E >> >> >> needs >> >> >> >> > testing >> >> >> >> > with the last). >> >> >> >> > 3) (incomplete) power management support for RTL8188EU (requi= res >> >> >> >> > firmware). >> >> >> >> > 4) Short Guard Interval support. >> >> >> >> > >> >> >> >> > It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; >> >> >> however, >> >> >> >> > it was never tested with RTL8192CE or RTL8812AU. >> >> >> >> > >> >> >> >> > How-to-build: >> >> >> >> > 1) download / checkout the repository. >> >> >> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src' >> >> >> >> > 3) build and install rtwn module: >> >> >> >> > cd $repository/sys/modules/rtwn && make && make install >> >> >> >> > 4) build and install rtwn_usb/rtwn_pci: >> >> >> >> > cd ../rtwn_usb && make && make install >> >> >> >> > cd ../rtwn_pci && make && make install >> >> >> >> > 5) unload previous && load current drivers: >> >> >> >> > kldunload if_urtwn if_rtwn >> >> >> >> > kldload /boot/modules/if_rtwn.ko >> >> /boot/modules/if_rtwn_usb.ko >> >> >> >> > /boot/modules/if_rtwn_pci.ko >> >> >> >> > 6) Use. >> >> >> >> _______________________________________________ >> >> >> >> freebsd-wireless@freebsd.org mailing list >> >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> >> >> To unsubscribe, send any mail to >> >> >> >> "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> freebsd-current@freebsd.org mailing list >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >> To unsubscribe, send any mail to >> >> "freebsd-current-unsubscribe@freebsd.org" >> >> >> >> >> > _______________________________________________ >> > freebsd-wireless@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > To unsubscribe, send any mail to >> > "freebsd-wireless-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " From owner-freebsd-current@freebsd.org Sun Oct 2 19:25:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30D1CAF1CAC for ; Sun, 2 Oct 2016 19:25:13 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 E83A2C20 for ; Sun, 2 Oct 2016 19:25:12 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bqmNq-002NWi-DI>; Sun, 02 Oct 2016 21:25:10 +0200 Received: from x55b386b3.dyn.telefonica.de ([85.179.134.179] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bqmNq-002d79-39>; Sun, 02 Oct 2016 21:25:10 +0200 Date: Sun, 2 Oct 2016 21:25:04 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: ZFS - Abyssal slow on copying Message-ID: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/c95QN/d2z8owdNRCc0aIWp5"; protocol="application/pgp-signature" X-Originating-IP: 85.179.134.179 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 19:25:13 -0000 --Sig_/c95QN/d2z8owdNRCc0aIWp5 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:50 C= EST 2016 ), I have a NanoBSD setup which creates an image for a router device. The problem I face is related to ZFS. The system has a system's SSD (Samsun= g 850 Pro, 256GB) which has an UFS filesystem. Aditionally, I have also a backup and a= data HDD, both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both the = sources for the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing o= n the 3 TB data drive.=20 The box itself has 8 GB RAM. When it comes to create the memory disk, which= is ~ 1,3 GB in size, the NanoBSD script starts creating the memory disk and then instal= ling world into this memory disk. And this part is a kind of abyssal in terms of the s= peed. The drive sounds like hell, the heads are moving rapidly. The copy speed is= incredibly slow compared to another box I usually use in the lab with UFS filesystem o= nly (different type of HDD). The whole stuff the nanbsd is installed from and to is on a separate ZFS pa= rtition, but in the same pool as everything else. When I first setup the new partitions,= I switched on deduplication, but I quickly deactivated it, because it had a tremendous im= pact on the working speed and memory consumption on that box. But something seems not r= ight since then - as I initially described, the copy/initialisation speed/bandwith is = abyssal. Well, I also fear that I did something wrong when I firt initialised the HDD - th= ere is this 125bytes/4k block discussion and I do not know how to check whether I'm aff= ected to that or not (or even causing the problems) and how to check whether DEDUPLICATIO= N is definitely OFF (apart from the usual stuff list features via "zfs get all"). As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader fro= m source to memory disk and the HDD makes sounds like hell and close to loosing the r/w= heads. On other boxes this task is done in a blink of an eye ... Thanks for your patience, Regards, oh --Sig_/c95QN/d2z8owdNRCc0aIWp5 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX8V8QAAoJEOgBcD7A/5N87TkIAJFFJQ+zdXjtmSXuY5G99b6l 6vcjyehU0gBOdpqhHdpVuzmJ5lg3Bt7RLndYhxkde1nDK3z+QOAAaqPIwBE4B2I+ 0pkWn14ZRta7ptRV9pwUDxi9OvrG9W4HmnP2jQSRddeTQ0HxxYHD/Zp6gTA8Ys7m 2YH2iOwAIM1LN2j5Bf0N4oV5NW1g3d+Y980egNkoUkhwPtoSE4MJlcZX/9t9uPdo BTHb/asCdtnxzp2jx1UJWVtUnO9PoLDggZFWbM3tax1+LC0E82nddwamno2w9PeT eadzKoNFh0l5HCEB9gAbZ4o41BC5v++3Qr+10uGe1Ma7znmCFcb0pOHJS+VBCos= =r9Na -----END PGP SIGNATURE----- --Sig_/c95QN/d2z8owdNRCc0aIWp5-- From owner-freebsd-current@freebsd.org Sun Oct 2 19:30:49 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D427AF1EF8 for ; Sun, 2 Oct 2016 19:30:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 5F213EFD for ; Sun, 2 Oct 2016 19:30:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C67181503 for ; Sun, 2 Oct 2016 19:30:41 +0000 (UTC) Subject: Re: ZFS - Abyssal slow on copying To: freebsd-current@freebsd.org References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> From: Allan Jude Message-ID: Date: Sun, 2 Oct 2016 15:30:41 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 19:30:49 -0000 On 2016-10-02 15:25, O. Hartmann wrote: > > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:50 CEST 2016 ), I > have a NanoBSD setup which creates an image for a router device. > > The problem I face is related to ZFS. The system has a system's SSD (Samsung 850 Pro, > 256GB) which has an UFS filesystem. Aditionally, I have also a backup and a data HDD, > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both the sources for > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing on the 3 TB > data drive. > > The box itself has 8 GB RAM. When it comes to create the memory disk, which is ~ 1,3 GB > in size, the NanoBSD script starts creating the memory disk and then installing world > into this memory disk. And this part is a kind of abyssal in terms of the speed. > > The drive sounds like hell, the heads are moving rapidly. The copy speed is incredibly > slow compared to another box I usually use in the lab with UFS filesystem only (different > type of HDD). > > The whole stuff the nanbsd is installed from and to is on a separate ZFS partition, but > in the same pool as everything else. When I first setup the new partitions, I switched on > deduplication, but I quickly deactivated it, because it had a tremendous impact on the > working speed and memory consumption on that box. But something seems not right since > then - as I initially described, the copy/initialisation speed/bandwith is abyssal. Well, > I also fear that I did something wrong when I firt initialised the HDD - there is this > 125bytes/4k block discussion and I do not know how to check whether I'm affected to that > or not (or even causing the problems) and how to check whether DEDUPLICATION is > definitely OFF (apart from the usual stuff list features via "zfs get all"). > > As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader from source to > memory disk and the HDD makes sounds like hell and close to loosing the r/w heads. On > other boxes this task is done in a blink of an eye ... > > Thanks for your patience, > > Regards, > oh > Turning deduplication off, only stops new blocks from being deduplicated. Any data written while deduplication was on, are still deduplicated. You would need to zfs send | zfs recv, or backup/destroy/restore to get the data back to normal. If the drive is making that much noise, have you considered that the drive might be failing? -- Allan Jude From owner-freebsd-current@freebsd.org Sun Oct 2 19:51:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12859AF267F for ; Sun, 2 Oct 2016 19:51:13 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 C5804DF6; Sun, 2 Oct 2016 19:51:12 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bqmn0-002RDu-M5>; Sun, 02 Oct 2016 21:51:10 +0200 Received: from x55b386b3.dyn.telefonica.de ([85.179.134.179] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bqmn0-002ekh-BX>; Sun, 02 Oct 2016 21:51:10 +0200 Date: Sun, 2 Oct 2016 21:51:05 +0200 From: "O. Hartmann" To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: ZFS - Abyssal slow on copying Message-ID: <20161002215105.6eae4c9b.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/eltHrnPJxys8HcgwdHRgsVJ"; protocol="application/pgp-signature" X-Originating-IP: 85.179.134.179 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 19:51:13 -0000 --Sig_/eltHrnPJxys8HcgwdHRgsVJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 2 Oct 2016 15:30:41 -0400 Allan Jude schrieb: > On 2016-10-02 15:25, O. Hartmann wrote: > >=20 > > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:= 50 CEST 2016 > > ), I have a NanoBSD setup which creates an image for a router device. > >=20 > > The problem I face is related to ZFS. The system has a system's SSD (Sa= msung 850 Pro, > > 256GB) which has an UFS filesystem. Aditionally, I have also a backup a= nd a data HDD, > > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both = the sources for > > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residi= ng on the 3 TB > > data drive.=20 > >=20 > > The box itself has 8 GB RAM. When it comes to create the memory disk, w= hich is ~ 1,3 > > GB in size, the NanoBSD script starts creating the memory disk and then= installing > > world into this memory disk. And this part is a kind of abyssal in term= s of the speed. > >=20 > > The drive sounds like hell, the heads are moving rapidly. The copy spee= d is incredibly > > slow compared to another box I usually use in the lab with UFS filesyst= em only > > (different type of HDD). > >=20 > > The whole stuff the nanbsd is installed from and to is on a separate ZF= S partition, > > but in the same pool as everything else. When I first setup the new par= titions, I > > switched on deduplication, but I quickly deactivated it, because it had= a tremendous > > impact on the working speed and memory consumption on that box. But som= ething seems > > not right since then - as I initially described, the copy/initialisation > > speed/bandwith is abyssal. Well, I also fear that I did something wrong= when I firt > > initialised the HDD - there is this 125bytes/4k block discussion and I = do not know > > how to check whether I'm affected to that or not (or even causing the p= roblems) and > > how to check whether DEDUPLICATION is definitely OFF (apart from the us= ual stuff list > > features via "zfs get all"). > >=20 > > As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader= from source to > > memory disk and the HDD makes sounds like hell and close to loosing the= r/w heads. On > > other boxes this task is done in a blink of an eye ... > >=20 > > Thanks for your patience, > >=20 > > Regards, > > oh > > =20 >=20 Hello Jude. Thank you for your answer. > Turning deduplication off, only stops new blocks from being > deduplicated. Any data written while deduplication was on, are still > deduplicated. You would need to zfs send | zfs recv, or > backup/destroy/restore to get the data back to normal. All right, that confirms my fear - I had dedup on for a while when experime= nting ...=20 >=20 > If the drive is making that much noise, have you considered that the > drive might be failing? The drive seems all right, I think it's the reading/writing of many small b= locks at once when copying from that specific ZFS partition containing the nanbsd install= ation with dedup on once. The noise is "classical", but unusual in that specific task = when supposed not to do so many read/writes. But, anyway, it is an optimistic guess and s= omehow also wishful thinking ;-) I will take a drive failure also in consideration - I = hopefully have backups. Kind reagrds, Oliver >=20 --Sig_/eltHrnPJxys8HcgwdHRgsVJ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX8WUpAAoJEOgBcD7A/5N86woH/RLqkuzgfb/ZCYoABv8C6EoU 4ChJ5/YYKEVcGyYUP5DpdSYSjRSPNZW3jO43AXLJch/7G8+1Bj9s+a1O1ewjmVHk dE95avGZrfwe870XUbOUxeLtAv9XX9UCyi607ufB3M6JqQvMYYu2kI3r8WmuwnlM QWi8O31YF6vhjMgJjGSefkE+BjE6b5i/OuHNKBT6xxyV9SQ3TzbAe42a+WfmORAC sKv5uwz5Je/UV3SaX9wXF3kJSLiavtzBt7KMqJC1CbTtnUJKPBYLqOfYPmZ2KLvs TBiSfs4kgkN7j8MBadkTGYUpQ+BJFbocHmiZ2zdXuXhL7FeV1M+aLQjjTpuza2M= =fxKF -----END PGP SIGNATURE----- --Sig_/eltHrnPJxys8HcgwdHRgsVJ-- From owner-freebsd-current@freebsd.org Mon Oct 3 00:56:20 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 443A9AC695F; Mon, 3 Oct 2016 00:56:20 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A438E222; Mon, 3 Oct 2016 00:56:18 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id u930tOT0057462 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 3 Oct 2016 08:55:24 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id u930tOdI057461; Mon, 3 Oct 2016 08:55:24 +0800 (CST) (envelope-from kevlo) Date: Mon, 3 Oct 2016 08:55:23 +0800 From: Kevin Lo To: Adrian Chadd Cc: Andriy Voskoboinyk , "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing Message-ID: <20161003005523.GA57437@ns.kevlo.org> References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 00:56:20 -0000 On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote: > > hi, Hi Adrian, > can you turn on debugging? Do you see RX frames? No Rx frames. The log is pretty much the same one I sent on the list: https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html > -a Thanks, Kevin > On 1 October 2016 at 08:09, Kevin Lo wrote: > > Strange, rtwn(4) stops working. I tried to scan for the available network, > > but it just returns empty results. > > > > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote: > >> > >> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo : > >> > >> Few more questions: > >> 1) does it work with h/w encryption support? (enabled by default) > >> (if 'yes' - I will remove 'hardware crypto enabled' warning). > >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then transmit > >> something - if it works then AMRR will print it's current status > >> periodically) > >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n) > >> (see r92ce_adj_devcaps() in sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c). > >> > >> > It works for me, thanks :) > >> > > >> > Kevin > >> > > >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote: > >> >> > >> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo > >> >> : > >> >> > >> >> Thanks for the log file, > >> >> > >> >> Tx 'device timeouts' should be fixed in > >> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5 > >> >> (currently I'm reviewing PCI-specific code to see if there are any > >> >> additional > >> >> issues - e.g., there are no Rx events in the log file). > >> >> > >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote: > >> >> >> > >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo > >> >> >> : > >> >> >> > >> >> >> Hi, > >> >> >> > >> >> >> So, the driver was fully tested. Thanks! > >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big > >> >> >> the problem is? > >> >> > > >> >> > Sure. Here you go > >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt > >> >> > > >> >> > Thanks, > >> >> > Kevin > >> >> > > >> >> >> > Hi Andriy, > >> >> >> > > >> >> >> > First of all, THANK YOU! You're doing amazing work! > >> >> >> > Second, I've done some testing on the following devices, > >> >> downloading > >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from > >> >> >> > ftp.freebsd.org: > >> >> >> > > >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS): > >> >> >> > rtwn0: >> >> addr > >> >> >> > 3> on usbus0 > >> >> >> > rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R > >> >> >> > > >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU): > >> >> >> > rtwn0: on > >> >> >> > usbus0 > >> >> >> > rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R > >> >> >> > > >> >> >> > - D-Link DWA-131 (RTL8192CU): > >> >> >> > rtwn0: >> >> addr > >> >> >> > 3> on usbus0 > >> >> >> > rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R > >> >> >> > > >> >> >> > - TP-Link Archer T4U (RTL8812AU): > >> >> >> > rtwn0: on > >> >> >> > usbus0 > >> >> >> > rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R > >> >> >> > > >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU): > >> >> >> > rtwn0: <802.11n WLAN Adapter> on usbus0 > >> >> >> > rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R > >> >> >> > > >> >> >> > - RTL8188CE mini pcie: > >> >> >> > rtwn0: port 0xd000-0xd0ff mem > >> >> >> > 0x90800000-0x90803fff irq 17 at device 0.0 on pci1 > >> >> >> > rtwn0: r92ce_attach: warning: hardware crypto enabled > >> >> >> > rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R > >> >> >> > > >> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work: > >> >> >> > > >> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used > >> >> >> > rtwn0: device timeout > >> >> >> > > >> >> >> > Kevin > >> >> >> > > >> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote: > >> >> >> >> > >> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk > >> >> >> >> : > >> >> >> >> > >> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn > >> >> (integrated > >> >> >> >> into src tree, so it can be built with 'make buildkernel' / 'make > >> >> >> >> buildworld'). > >> >> >> >> > >> >> >> >> This the last stage; once all reported issues will be resolved, > >> >> I'm > >> >> >> >> going to merge it into HEAD. > >> >> >> >> > >> >> >> >> > Hi everyone, > >> >> >> >> > > >> >> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were > >> >> >> merged > >> >> >> >> > into a > >> >> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the > >> >> >> code is > >> >> >> >> > available on https://github.com/s3erios/rtwn repository. Among > >> >> >> >> bugfixes / > >> >> >> >> > code deduplication, there some new features too: > >> >> >> >> > > >> >> >> >> > 1) multi-vap support (one any wireless interface + one STA > >> >> >> interface + > >> >> >> >> > any number of monitor mode interfaces). > >> >> >> >> > 2) few new sysctls: > >> >> >> >> > * dev.rtwn.#.crypto - controls how to use hardware crypto > >> >> >> >> acceleration > >> >> >> >> > * dev.rtwn.#.ratectl_selected > >> >> >> >> > * dev.rtwn.#.ratectl - selects current 'rate control' > >> >> algorithm > >> >> >> >> > (currently only 'none' and 'net80211' are supported; RTL8192CE > >> >> >> needs > >> >> >> >> > testing > >> >> >> >> > with the last). > >> >> >> >> > 3) (incomplete) power management support for RTL8188EU (requires > >> >> >> >> > firmware). > >> >> >> >> > 4) Short Guard Interval support. > >> >> >> >> > > >> >> >> >> > It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; > >> >> >> however, > >> >> >> >> > it was never tested with RTL8192CE or RTL8812AU. > >> >> >> >> > > >> >> >> >> > How-to-build: > >> >> >> >> > 1) download / checkout the repository. > >> >> >> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src' > >> >> >> >> > 3) build and install rtwn module: > >> >> >> >> > cd $repository/sys/modules/rtwn && make && make install > >> >> >> >> > 4) build and install rtwn_usb/rtwn_pci: > >> >> >> >> > cd ../rtwn_usb && make && make install > >> >> >> >> > cd ../rtwn_pci && make && make install > >> >> >> >> > 5) unload previous && load current drivers: > >> >> >> >> > kldunload if_urtwn if_rtwn > >> >> >> >> > kldload /boot/modules/if_rtwn.ko > >> >> /boot/modules/if_rtwn_usb.ko > >> >> >> >> > /boot/modules/if_rtwn_pci.ko > >> >> >> >> > 6) Use. > >> >> >> >> _______________________________________________ > >> >> >> >> freebsd-wireless@freebsd.org mailing list > >> >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> >> >> >> To unsubscribe, send any mail to > >> >> >> >> "freebsd-wireless-unsubscribe@freebsd.org" > >> >> >> >> > >> >> >> > >> >> _______________________________________________ > >> >> freebsd-current@freebsd.org mailing list > >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> >> To unsubscribe, send any mail to > >> >> "freebsd-current-unsubscribe@freebsd.org" > >> >> > >> >> > >> > _______________________________________________ > >> > freebsd-wireless@freebsd.org mailing list > >> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >> > To unsubscribe, send any mail to > >> > "freebsd-wireless-unsubscribe@freebsd.org" > >> > >> > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Mon Oct 3 05:32:36 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 046D9AF379B; Mon, 3 Oct 2016 05:32:36 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4o.cmail.yandex.net (forward4o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::289]) (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 74E33B3B; Mon, 3 Oct 2016 05:32:35 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::26]) by forward4o.cmail.yandex.net (Yandex) with ESMTP id 84FBA20CDF; Mon, 3 Oct 2016 08:32:21 +0300 (MSK) Received: from smtp2o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2o.mail.yandex.net (Yandex) with ESMTP id 4EAE15080DC9; Mon, 3 Oct 2016 08:32:17 +0300 (MSK) Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id b9sjMryG1Q-WGNedRss; Mon, 03 Oct 2016 08:32:16 +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=1475472736; bh=GGsCPUt2RY7r6eOP7/yjLuvNczWU8JGHEHLGanxdaUs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=cYeSBcFBzdYeVTaeYn3+RZuBNBOu+JD21G778m99RPjFBfTQeC7hEkqLJhZ+lbplD zW0qgjcV2QNQ+/yu8b49hms84aVG2S+iHee1SSOG0jZRO2D4+EoPY5JycYWotwx4G4 maozFzenC+W9qDlYpwEAulqooifHj+Nibw2evlvU= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: Trying to read linux-lvm on 11.0-RC2 using geom, bhyve, fail. To: Zaphod Beeblebrox , freebsd-fs , freebsd-emulation@freebsd.org, freebsd-current References: From: "Andrey V. Elsukov" Message-ID: <601197a5-2717-79a7-bdce-95f82d1d819d@yandex.ru> Date: Mon, 3 Oct 2016 08:29:58 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="njF9DAuM29H4Kf2aTL5xv6utu1CebwaOH" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 05:32:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --njF9DAuM29H4Kf2aTL5xv6utu1CebwaOH Content-Type: multipart/mixed; boundary="hWSt7FLKMBtC6MeTlAbFbBAedGuc2UNtx"; protected-headers="v1" From: "Andrey V. Elsukov" To: Zaphod Beeblebrox , freebsd-fs , freebsd-emulation@freebsd.org, freebsd-current Message-ID: <601197a5-2717-79a7-bdce-95f82d1d819d@yandex.ru> Subject: Re: Trying to read linux-lvm on 11.0-RC2 using geom, bhyve, fail. References: In-Reply-To: --hWSt7FLKMBtC6MeTlAbFbBAedGuc2UNtx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 15.09.2016 08:10, Zaphod Beeblebrox wrote: > After this fail, I decided I didn't really _need_ to run linux here and= I > discovered 'geom_linux_lvm.ko' ... cool. But fail, too. Doesn't emit = any > messages. I even enabled the debug messages for it. >=20 > The linux disk is partitioned thusly: >=20 > =3D> 63 1953525105 ada1 MBR (932G) > 63 1985 - free - (993K) > 2048 1953523120 1 linux-data [active] (932G) Probably it isn't LVM or some modern version, which isn't supported by module. With enable kern.geom.linux_lvm.debug=3D1 module will complain only if it will find magic string "LABELONE" in the metadata. You can check what is stored in the metadata with the following command: # dd if=3D/dev/ada1s1 count=3D1 | hexdump -vC --=20 WBR, Andrey V. Elsukov --hWSt7FLKMBtC6MeTlAbFbBAedGuc2UNtx-- --njF9DAuM29H4Kf2aTL5xv6utu1CebwaOH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEvBAEBCAAZBQJX8ezWEhxidTdjaGVyQHlhbmRleC5ydQAKCRABxeoEEMihepiC B/9CERe+9OvyadqPBsh9MnXv7GHIOLuOt3FbrEQWxtT6Z6rr23lgRHMTgwsR8CRh PY8ImhjylPDC6LZbT2KVt6ka/u9S8phSOecjGXAiKsCmt79sljWz8u/MiHUD6Ar+ Y4HQ4aBc1JRf3X3PDcVSzEeG/2B2VfueOlcweBuga9FO5/P9j6H2XVkK8f+HT+5L 0IKU3Qrtcb2VY0Om4sIX8667PpgRwXonFVj8gEGkuZtyofISdaIprSubj2M7p9Ja 2e/lpEbaDmWoCuPY0ZZ2Atp6LJxaUueVJWezLMR/kKLh60Q14k+W+t6KNpVfMX5I 3MNifMMfasGwM4oSiYY7mImi =hnaG -----END PGP SIGNATURE----- --njF9DAuM29H4Kf2aTL5xv6utu1CebwaOH-- From owner-freebsd-current@freebsd.org Mon Oct 3 09:31:05 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18CD8AC625C for ; Mon, 3 Oct 2016 09:31:05 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 D04A77D8; Mon, 3 Oct 2016 09:31:04 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bqzaK-000Q2u-B3>; Mon, 03 Oct 2016 11:30:56 +0200 Received: from x4e34adaa.dyn.telefonica.de ([78.52.173.170] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bqzaK-003Tg5-0l>; Mon, 03 Oct 2016 11:30:56 +0200 Date: Mon, 3 Oct 2016 11:30:50 +0200 From: "O. Hartmann" To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: ZFS - Abyssal slow on copying Message-ID: <20161003113050.0f1b09bd.ohartman@zedat.fu-berlin.de> In-Reply-To: References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/6xEaX9simWG6gXG.eqLpTJs"; protocol="application/pgp-signature" X-Originating-IP: 78.52.173.170 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 09:31:05 -0000 --Sig_/6xEaX9simWG6gXG.eqLpTJs Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 2 Oct 2016 15:30:41 -0400 Allan Jude schrieb: > On 2016-10-02 15:25, O. Hartmann wrote: > >=20 > > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:= 50 CEST 2016 > > ), I have a NanoBSD setup which creates an image for a router device. > >=20 > > The problem I face is related to ZFS. The system has a system's SSD (Sa= msung 850 Pro, > > 256GB) which has an UFS filesystem. Aditionally, I have also a backup a= nd a data HDD, > > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both = the sources for > > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residi= ng on the 3 TB > > data drive.=20 > >=20 > > The box itself has 8 GB RAM. When it comes to create the memory disk, w= hich is ~ 1,3 > > GB in size, the NanoBSD script starts creating the memory disk and then= installing > > world into this memory disk. And this part is a kind of abyssal in term= s of the speed. > >=20 > > The drive sounds like hell, the heads are moving rapidly. The copy spee= d is incredibly > > slow compared to another box I usually use in the lab with UFS filesyst= em only > > (different type of HDD). > >=20 > > The whole stuff the nanbsd is installed from and to is on a separate ZF= S partition, > > but in the same pool as everything else. When I first setup the new par= titions, I > > switched on deduplication, but I quickly deactivated it, because it had= a tremendous > > impact on the working speed and memory consumption on that box. But som= ething seems > > not right since then - as I initially described, the copy/initialisation > > speed/bandwith is abyssal. Well, I also fear that I did something wrong= when I firt > > initialised the HDD - there is this 125bytes/4k block discussion and I = do not know > > how to check whether I'm affected to that or not (or even causing the p= roblems) and > > how to check whether DEDUPLICATION is definitely OFF (apart from the us= ual stuff list > > features via "zfs get all"). > >=20 > > As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader= from source to > > memory disk and the HDD makes sounds like hell and close to loosing the= r/w heads. On > > other boxes this task is done in a blink of an eye ... > >=20 > > Thanks for your patience, > >=20 > > Regards, > > oh > > =20 >=20 > Turning deduplication off, only stops new blocks from being > deduplicated. Any data written while deduplication was on, are still > deduplicated. You would need to zfs send | zfs recv, or > backup/destroy/restore to get the data back to normal. >=20 > If the drive is making that much noise, have you considered that the > drive might be failing? >=20 Hello. Might there be any hint I can investigate on that ZFS partition showing me = that the particular partition is still doing deduplication? If I wouldn't know that = I switch dedup on and later off, I would blame the OS instead. So, for further foren= sik analysis in the future, it would be nice to know how to look at it - if it is doable= via simple checking the features of the ZFS partition ... Thanks, oh=20 --Sig_/6xEaX9simWG6gXG.eqLpTJs Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX8iVKAAoJEOgBcD7A/5N8ApEIAIKj12AWXm+qQozZ9UTYi8Nq rgTADh6ICcVV4j2QmUBNv2Ry9oUDc0C0Y7HJ0t6Pr/2oESG7I62SxPbLyiqSl1ax EvB20YGDRMn7owRvk7y++rSmp8WwpKbl4aDGCez6Q6K408XZVJVu2jIiIG2db94l zSok0/ixPE7+u0+I9ilLYGZZrhaHD0B4b99NYVnxaBozfrtlggQ3hkwKVGPE6lor AhBgOMiehhFYPSsLnAkpy4ujcr3F7BMjpKsk7+7IcWm0tx2+ihK1D9u9WNCvePuf 9mQqETYn0b/c9dBZT0r99VMcPJ8q7CoUTVe6v/aAENAr8yAs5VO0ybZt7zP7tFU= =qqiZ -----END PGP SIGNATURE----- --Sig_/6xEaX9simWG6gXG.eqLpTJs-- From owner-freebsd-current@freebsd.org Mon Oct 3 09:35:18 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B6C8AC647C for ; Mon, 3 Oct 2016 09:35:18 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 D75A8C62; Mon, 3 Oct 2016 09:35:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from imac.bs.cs.huji.ac.il ([132.65.179.42]) by kabab.cs.huji.ac.il with esmtp id 1bqzeO-0003Wp-Vx; Mon, 03 Oct 2016 12:35:09 +0300 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS - Abyssal slow on copying From: Daniel Braniss In-Reply-To: <20161003113050.0f1b09bd.ohartman@zedat.fu-berlin.de> Date: Mon, 3 Oct 2016 12:35:08 +0300 Cc: Allan Jude , freebsd-current@freebsd.org Message-Id: <28DF6F19-A97F-4029-9D55-77E14B38B45D@cs.huji.ac.il> References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> <20161003113050.0f1b09bd.ohartman@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.3124) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 09:35:18 -0000 > On 3 Oct 2016, at 12:30 PM, O. Hartmann = wrote: >=20 > Am Sun, 2 Oct 2016 15:30:41 -0400 > Allan Jude > = schrieb: >=20 >> On 2016-10-02 15:25, O. Hartmann wrote: >>>=20 >>> Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 = 09:34:50 CEST 2016 >>> ), I have a NanoBSD setup which creates an image for a router = device. >>>=20 >>> The problem I face is related to ZFS. The system has a system's SSD = (Samsung 850 Pro, >>> 256GB) which has an UFS filesystem. Aditionally, I have also a = backup and a data HDD, >>> both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). = Both the sources for >>> the NanoBSD and the object tree as well as the NANO_WORLDDIR are = residing on the 3 TB >>> data drive.=20 >>>=20 >>> The box itself has 8 GB RAM. When it comes to create the memory = disk, which is ~ 1,3 >>> GB in size, the NanoBSD script starts creating the memory disk and = then installing >>> world into this memory disk. And this part is a kind of abyssal in = terms of the speed. >>>=20 >>> The drive sounds like hell, the heads are moving rapidly. The copy = speed is incredibly >>> slow compared to another box I usually use in the lab with UFS = filesystem only >>> (different type of HDD). >>>=20 >>> The whole stuff the nanbsd is installed from and to is on a separate = ZFS partition, >>> but in the same pool as everything else. When I first setup the new = partitions, I >>> switched on deduplication, but I quickly deactivated it, because it = had a tremendous >>> impact on the working speed and memory consumption on that box. But = something seems >>> not right since then - as I initially described, the = copy/initialisation >>> speed/bandwith is abyssal. Well, I also fear that I did something = wrong when I firt >>> initialised the HDD - there is this 125bytes/4k block discussion and = I do not know >>> how to check whether I'm affected to that or not (or even causing = the problems) and >>> how to check whether DEDUPLICATION is definitely OFF (apart from the = usual stuff list >>> features via "zfs get all"). >>>=20 >>> As an example: the nanbosd script takes ~ 1 minute to copy = /boot/loader from source to >>> memory disk and the HDD makes sounds like hell and close to loosing = the r/w heads. On >>> other boxes this task is done in a blink of an eye ... >>>=20 >>> Thanks for your patience, >>>=20 >>> Regards, >>> oh >>>=20 >>=20 >> Turning deduplication off, only stops new blocks from being >> deduplicated. Any data written while deduplication was on, are still >> deduplicated. You would need to zfs send | zfs recv, or >> backup/destroy/restore to get the data back to normal. >>=20 >> If the drive is making that much noise, have you considered that the >> drive might be failing? >>=20 >=20 > Hello. >=20 > Might there be any hint I can investigate on that ZFS partition = showing me that the > particular partition is still doing deduplication? If I wouldn't know = that I switch > dedup on and later off, I would blame the OS instead. So, for further = forensik analysis > in the future, it would be nice to know how to look at it - if it is = doable via simple > checking the features of the ZFS partition ... >=20 > Thanks, > oh=20 not really an answer, but zpool has a nice command: history, it = sometimes helps to find what and when nfs commands where given. =20 danny From owner-freebsd-current@freebsd.org Mon Oct 3 11:07:01 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39BFAAF3B3A; Mon, 3 Oct 2016 11:07:01 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4C74211E; Mon, 3 Oct 2016 11:06:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA27859; Mon, 03 Oct 2016 14:06:48 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1br156-0005bg-PR; Mon, 03 Oct 2016 14:06:48 +0300 To: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Subject: [request for testing] isl, cyapa on chromebooks Message-ID: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> Date: Mon, 3 Oct 2016 14:05:52 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 11:07:01 -0000 If you have a Chromebook where you are currently able to use isl and cyapa drivers, could you please test the following code change? https://people.freebsd.org/~avg/ig4-i2c.diff The change moves the drivers from the SMBus to the I2C bus and as such some configuration changes are required. Namely, you will now need iicbus driver either in the kernel configuration or as a module. For now the smbus driver is also required. You also need to add some entries to /boot/device.hints: hint.isl.0.at="iicbus0" hint.isl.0.addr=0x88 hint.isl.1.at="iicbus1" hint.isl.1.addr=0x88 hint.cyapa.0.at="iicbus0" hint.cyapa.0.addr=0xce hint.cyapa.1.at="iicbus1" hint.cyapa.1.addr=0xce The hints are required because auto-probing (either via the bus enumeration or self-identification) is disabled for now for safety reason. Also, as I understand, the Intel chipset used in the supported Chromebooks provides to i2c buses (possibly in addition in an smbus) and I am not sure on which of the i2c buses the devices reside. The changes are build tested only, because I do not have access to the hardware. So, kernel panics, etc are not unexpected. Please let me know if drivers attach at all and if there are any issues with them. A verbose dmesg would be of great help. That could be obtained by booting in a verbose mode if the drivers are auto-loaded or by setting debug.bootverbose=1 before loading the drivers if that's done manually. Please also note that ig4 driver is changed, so it too has to be rebuilt if you are going to build individual modules rather than do a kernel + modules build. I will appreciate your testing and feedback. Thank you! -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon Oct 3 11:22:52 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7EBCAC646A for ; Mon, 3 Oct 2016 11:22:52 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 B1BE4DB0 for ; Mon, 3 Oct 2016 11:22:52 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (123-48-23-227.dz.commufa.jp [123.48.23.227]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id u93AflZm023295; Mon, 3 Oct 2016 19:41:48 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 3 Oct 2016 19:41:47 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: ohartman@zedat.fu-berlin.de Subject: Re: ZFS - Abyssal slow on copying Message-Id: <20161003194147.9934fbbebc1c4cf9d3c5dc83@dec.sakura.ne.jp> In-Reply-To: <28DF6F19-A97F-4029-9D55-77E14B38B45D@cs.huji.ac.il> References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> <20161003113050.0f1b09bd.ohartman@zedat.fu-berlin.de> <28DF6F19-A97F-4029-9D55-77E14B38B45D@cs.huji.ac.il> Organization: Junchoon corps X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 11:22:53 -0000 On Mon, 3 Oct 2016 12:35:08 +0300 Daniel Braniss wrote: > > > On 3 Oct 2016, at 12:30 PM, O. Hartmann wrote: > > > > Am Sun, 2 Oct 2016 15:30:41 -0400 > > Allan Jude > schrieb: > > > >> On 2016-10-02 15:25, O. Hartmann wrote: > >>> > >>> Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:50 CEST 2016 > >>> ), I have a NanoBSD setup which creates an image for a router device. > >>> > >>> The problem I face is related to ZFS. The system has a system's SSD (Samsung 850 Pro, > >>> 256GB) which has an UFS filesystem. Aditionally, I have also a backup and a data HDD, > >>> both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both the sources for > >>> the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing on the 3 TB > >>> data drive. > >>> > >>> The box itself has 8 GB RAM. When it comes to create the memory disk, which is ~ 1,3 > >>> GB in size, the NanoBSD script starts creating the memory disk and then installing > >>> world into this memory disk. And this part is a kind of abyssal in terms of the speed. > >>> > >>> The drive sounds like hell, the heads are moving rapidly. The copy speed is incredibly > >>> slow compared to another box I usually use in the lab with UFS filesystem only > >>> (different type of HDD). > >>> > >>> The whole stuff the nanbsd is installed from and to is on a separate ZFS partition, > >>> but in the same pool as everything else. When I first setup the new partitions, I > >>> switched on deduplication, but I quickly deactivated it, because it had a tremendous > >>> impact on the working speed and memory consumption on that box. But something seems > >>> not right since then - as I initially described, the copy/initialisation > >>> speed/bandwith is abyssal. Well, I also fear that I did something wrong when I firt > >>> initialised the HDD - there is this 125bytes/4k block discussion and I do not know > >>> how to check whether I'm affected to that or not (or even causing the problems) and > >>> how to check whether DEDUPLICATION is definitely OFF (apart from the usual stuff list > >>> features via "zfs get all"). > >>> > >>> As an example: the nanbosd script takes ~ 1 minute to copy /boot/loader from source to > >>> memory disk and the HDD makes sounds like hell and close to loosing the r/w heads. On > >>> other boxes this task is done in a blink of an eye ... > >>> > >>> Thanks for your patience, > >>> > >>> Regards, > >>> oh > >>> > >> > >> Turning deduplication off, only stops new blocks from being > >> deduplicated. Any data written while deduplication was on, are still > >> deduplicated. You would need to zfs send | zfs recv, or > >> backup/destroy/restore to get the data back to normal. > >> > >> If the drive is making that much noise, have you considered that the > >> drive might be failing? > >> > > > > Hello. > > > > Might there be any hint I can investigate on that ZFS partition showing me that the > > particular partition is still doing deduplication? If I wouldn't know that I switch > > dedup on and later off, I would blame the OS instead. So, for further forensik analysis > > in the future, it would be nice to know how to look at it - if it is doable via simple > > checking the features of the ZFS partition ... > > > > Thanks, > > oh > > not really an answer, but zpool has a nice command: history, it sometimes helps to find what and when > nfs commands where given. > > danny Looks helpful to confirm 'when and how changed', but the output contains 'all' changes such as snapshots. Would be hard to determine what is the current configuration. To determine what is the current settings, `zfs get all zroot` for case that pool name is zroot. Pool name can include child dataset like zroot/local. To list all children, use `zfs get -r all zroot` instead. To focus on dedup `zfs get -p dedup zroot` can be better. If you want children datasets, '-r' shall be specified before '-p'. Unfortunately, this (sub)command cannot show change logs. HTH. -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Mon Oct 3 16:14:42 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47B53AF473F for ; Mon, 3 Oct 2016 16:14:42 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 86F77A85 for ; Mon, 3 Oct 2016 16:14:40 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 36129 invoked by uid 89); 3 Oct 2016 16:07:52 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@185.17.205.219) by mail.grem.de with ESMTPA; 3 Oct 2016 16:07:52 -0000 Date: Mon, 3 Oct 2016 18:07:50 +0200 From: Michael Gmelin To: Andriy Gapon Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161003180750.744dae0a@bsd64.grem.de> In-Reply-To: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 16:14:42 -0000 On Mon, 3 Oct 2016 14:05:52 +0300 Andriy Gapon wrote: > If you have a Chromebook where you are currently able to use isl and > cyapa drivers, could you please test the following code change? > https://people.freebsd.org/~avg/ig4-i2c.diff > > The change moves the drivers from the SMBus to the I2C bus and as > such some configuration changes are required. > Namely, you will now need iicbus driver either in the kernel > configuration or as a module. For now the smbus driver is also > required. You also need to add some entries to /boot/device.hints: > hint.isl.0.at="iicbus0" > hint.isl.0.addr=0x88 > hint.isl.1.at="iicbus1" > hint.isl.1.addr=0x88 > hint.cyapa.0.at="iicbus0" > hint.cyapa.0.addr=0xce > hint.cyapa.1.at="iicbus1" > hint.cyapa.1.addr=0xce > > The hints are required because auto-probing (either via the bus > enumeration or self-identification) is disabled for now for safety > reason. Also, as I understand, the Intel chipset used in the > supported Chromebooks provides to i2c buses (possibly in addition in > an smbus) and I am not sure on which of the i2c buses the devices > reside. > > The changes are build tested only, because I do not have access to > the hardware. So, kernel panics, etc are not unexpected. > > Please let me know if drivers attach at all and if there are any > issues with them. A verbose dmesg would be of great help. That could > be obtained by booting in a verbose mode if the drivers are > auto-loaded or by setting debug.bootverbose=1 before loading the > drivers if that's done manually. > > Please also note that ig4 driver is changed, so it too has to be > rebuilt if you are going to build individual modules rather than do a > kernel + modules build. > > I will appreciate your testing and feedback. > Thank you! Thanks for working on this. I have currently access to two c720 Chromebooks, one with a cyapa touchpad, the other with a (yet) unsupported replacement I'm planning to work on. I upgraded the latter the r306641, applied your patches (cleanly) and ran "make kernel" (GENERIC kernel), added the entries to device.hints and rebooted. Unfortunately ig4 won't load: # kldload ig4 link_elf_obj: symbol iicbus_transfer_desc undefined linker_load_file: Unsupported file type I also noticed that isl cannot be built from the module source directory: # cd /usr/src/sys/modules/i2c/isl # make ... /usr/src/sys/sys/vnode.h:571:10: fatal error: 'vnode_if.h' file not found #include "vnode_if.h" ^ 1 error generated *** Error code 1 This can be easily fixed by removing "#include " from isl.c (line 56). Best, Michael -- Michael Gmelin From owner-freebsd-current@freebsd.org Mon Oct 3 16:41:58 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A14EAF4D82; Mon, 3 Oct 2016 16:41:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0591FD31; Mon, 3 Oct 2016 16:41:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA28488; Mon, 03 Oct 2016 19:41:54 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1br6JO-0005te-DS; Mon, 03 Oct 2016 19:41:54 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Message-ID: Date: Mon, 3 Oct 2016 19:41:17 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161003180750.744dae0a@bsd64.grem.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 16:41:58 -0000 On 03/10/2016 19:07, Michael Gmelin wrote: > I upgraded the latter the r306641, applied your patches (cleanly) and > ran "make kernel" (GENERIC kernel), added the entries to device.hints > and rebooted. Unfortunately ig4 won't load: > > # kldload ig4 > link_elf_obj: symbol iicbus_transfer_desc undefined > linker_load_file: Unsupported file type Hmm, seems like forgot to declare the iicbus module dependency. Could you please kldload iicbus and see if that helps? Meanwhile I'll add the dependency. > I also noticed that isl cannot be built from the module source > directory: > > # cd /usr/src/sys/modules/i2c/isl > # make > ... > /usr/src/sys/sys/vnode.h:571:10: fatal error: 'vnode_if.h' file not > found > #include "vnode_if.h" > ^ > 1 error generated > *** Error code 1 > > This can be easily fixed by removing "#include " from > isl.c (line 56). Thank you for reporting this! Looks like I overlooked this because I didn't do make clean after removing vnode_if.h from the Makefile. Will fix this too. -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon Oct 3 17:12:44 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10A49AF391D for ; Mon, 3 Oct 2016 17:12:44 +0000 (UTC) (envelope-from evansus@gmail.com) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 C46BDC1 for ; Mon, 3 Oct 2016 17:12:43 +0000 (UTC) (envelope-from evansus@gmail.com) Received: by mail-yw0-x229.google.com with SMTP id i129so112252889ywb.0 for ; Mon, 03 Oct 2016 10:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:content-transfer-encoding:from:message-id:date:cc:to :mime-version; bh=gEOWNZwrt2lBMx826K9qoHUNYdObWzJDdyODQlM0zG0=; b=VpxGm2FMy4l/2Rdis7CVCrtKscHrtYnnqbgiARJZxJdqRXTcwO5yBuVdxKtsWznIG2 LrqmBU+z9rTVtNR/fJmr24FRcjrPNGvN9W8Wlq4x8j14e8n0dZW/CQuZkeTLd6hz0LD/ Qo4dqJnLoqUzWWOgH7sXkrlfoj5Ng3RUKFC64x04GnXZKkzDNFgAEu2MKjPA0o1S4JYD co9RFTe6hoyug87OgGz/qPHpxx8SdYre+OGYpFXCU/3WwoTUoN6Ukr+ZF0sRJq+HXzzF S9yE/F3mIO/rGxmwv8+VitXGJMamRqijjChAkIFJV5gny+01dfXWBS6HBwkqAjqYXTbY lWoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:content-transfer-encoding:from :message-id:date:cc:to:mime-version; bh=gEOWNZwrt2lBMx826K9qoHUNYdObWzJDdyODQlM0zG0=; b=GSfzI9PrlDFogcThKzG46fWFLw1mTMfAX6yKYiHM5vMu8ks5IXLJwKyPDi0hyS9BzG vsRwcats7xgwb2edqofqK4lPfhp2t2VFkSK6P5mFDJxnSOoCKoFkZg1QgWw0/S76yHW6 4JZPdWQgA3PPhWz4TzzSyLN4roynDk/yYBnaicCMS/4KOzUJqWu0w9Gb1HZITEgvNMw8 CzWP0n2UuaBc/b34Z6DBNRlwwShtSQaEQcHP0e1Q1zMyX54++pa6Z/ZMZNw3LtolxH9x 2tV8yfZNbF14T5DWcDG9EpVnsi1lCo68Tlin3t5StKSfaez+G2ItCoHdVd4NoqoJL+eR oOwA== X-Gm-Message-State: AA6/9Rn7YtBUG5fW31KMrv36XUt8eQqUMbDibT5MTP23kJtBSV8/GfR6pcxzGqnGd6A81A== X-Received: by 10.129.86.131 with SMTP id k125mr15979734ywb.21.1475514762897; Mon, 03 Oct 2016 10:12:42 -0700 (PDT) Received: from [10.0.0.44] ([208.102.167.120]) by smtp.gmail.com with ESMTPSA id i132sm10377281ywc.53.2016.10.03.10.12.41 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 03 Oct 2016 10:12:42 -0700 (PDT) Subject: Re: ZFS - Abyssal slow on copying Content-Transfer-Encoding: quoted-printable From: Evan Susarret Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13G34) Message-Id: <93D024AE-408C-4C1D-882D-9C526F2BB276@gmail.com> Date: Mon, 3 Oct 2016 13:12:41 -0400 Cc: freebsd-current@freebsd.org To: ohartman@zedat.fu-berlin.de Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 17:12:44 -0000 In case you are still trying to get this resolved: Since you have enabled deduplication in the past, unfortunately the deduplic= ation tables must be loaded into memory for any and all writes. ZFS must det= ermine if all writes match a previous block, to 1) increment the dedup count= for matches, or 2) decrement the dedup count for a no-longer needed block. This often means that the table must be loaded from disk repeatedly, especia= lly if the table is large enough that it is purged from memory often. It is e= ven possible to get your pool into a state where it cannot be imported due t= o the amount of memory required. =46rom the disk activity and slowness you described, it sounds like the dedu= p table (DDT) is being loaded, dumped, and loaded again repeatedly. I don't know of the top of my head if you can use the 'zdb' command to exami= ne the current DDT table, but there is a way to simulate the effect of enabl= ing dedup on a given dataset using zdb in order to estimate the size of the D= DT table that would result. The only resolution, as Allan stated, is to zfs send and zfs recv the datase= t into a new copy that does not have dedup enabled, or recreate it from scra= tch. Depending if you enabled dedup on single dataset, multiple datasets, or= the whole pool, it may be easiest to recreate the whole pool. This is a sid= e-effect of dedup that some have referred to as 'toxic', and some googling w= ill show that it is a common issue encountered when experimenting with dedup= (on all platforms). Some guides will recommend only enabling dedup if you know that your data wi= ll have many duplicated blocks, and also that the tables will easily fit int= o memory. There are also guides that can help to estimate the amount of ram r= equired to hold a DDT based on the blocksize and number of blocks in the dat= aset. This can be complicated by many factors, so it is usually best to avoi= d turning dedup on unless you are sure that it will help rather than hinder u= sage. Hope this helps! Evan= From owner-freebsd-current@freebsd.org Mon Oct 3 20:32:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79C4AAF40A6 for ; Mon, 3 Oct 2016 20:32:13 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id DB21C354 for ; Mon, 3 Oct 2016 20:32:12 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 38861 invoked by uid 89); 3 Oct 2016 20:25:30 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 3 Oct 2016 20:25:30 -0000 Date: Mon, 3 Oct 2016 22:25:28 +0200 From: Michael Gmelin To: Andriy Gapon Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161003222528.56d46787@bsd64.grem.de> In-Reply-To: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 20:32:13 -0000 On Mon, 3 Oct 2016 19:41:17 +0300 Andriy Gapon wrote: > On 03/10/2016 19:07, Michael Gmelin wrote: > > I upgraded the latter the r306641, applied your patches (cleanly) > > and ran "make kernel" (GENERIC kernel), added the entries to > > device.hints and rebooted. Unfortunately ig4 won't load: > > > > # kldload ig4 > > link_elf_obj: symbol iicbus_transfer_desc undefined > > linker_load_file: Unsupported file type > > Hmm, seems like forgot to declare the iicbus module dependency. > Could you please kldload iicbus and see if that helps? > Meanwhile I'll add the dependency. Unfortunately this doesn't help, you should be able to reproduce it yourself without access to the actual hardware though. I worked around this by adding the iicbus dependency to ig4_pci.c (and also to "files"). Now loading ig4 works and both lynx point controllers are detected. Loading isl doesn't create any output and doesn't seem to detect any devices. Also, devinfo shows both controllers (ig4iic0, ig4iic1), but no iicbus devices. # devinfo | grep iic ig4iic0 ig4iic1 -m -- Michael Gmelin From owner-freebsd-current@freebsd.org Mon Oct 3 22:05:09 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3F91AF353F; Mon, 3 Oct 2016 22:05:09 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C6009853; Mon, 3 Oct 2016 22:05:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id BAA29095; Tue, 04 Oct 2016 01:05:06 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brBMA-0006AI-7u; Tue, 04 Oct 2016 01:05:06 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Message-ID: Date: Tue, 4 Oct 2016 01:04:10 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161003222528.56d46787@bsd64.grem.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2016 22:05:09 -0000 On 03/10/2016 23:25, Michael Gmelin wrote: > On Mon, 3 Oct 2016 19:41:17 +0300 > Andriy Gapon wrote: > >> On 03/10/2016 19:07, Michael Gmelin wrote: >>> I upgraded the latter the r306641, applied your patches (cleanly) >>> and ran "make kernel" (GENERIC kernel), added the entries to >>> device.hints and rebooted. Unfortunately ig4 won't load: >>> >>> # kldload ig4 >>> link_elf_obj: symbol iicbus_transfer_desc undefined >>> linker_load_file: Unsupported file type >> >> Hmm, seems like forgot to declare the iicbus module dependency. >> Could you please kldload iicbus and see if that helps? >> Meanwhile I'll add the dependency. > > Unfortunately this doesn't help, you should be able to reproduce it > yourself without access to the actual hardware though. > > I worked around this by adding the iicbus dependency to ig4_pci.c (and > also to "files"). Okay, this should be in the latest patch anyway. > Now loading ig4 works and both lynx point controllers are detected. > Loading isl doesn't create any output and doesn't seem to detect any > devices. Also, devinfo shows both controllers (ig4iic0, ig4iic1), but > no iicbus devices. > > # devinfo | grep iic > ig4iic0 > ig4iic1 Is there anything interesting from from ig4 in the log / dmesg? Could you please check that your copy of the patch contains this chunk? @@ -549,7 +780,7 @@ ig4iic_attach(ig4iic_softc_t *sc) IG4_CTL_RESTARTEN | IG4_CTL_SPEED_STD); - sc->smb = device_add_child(sc->dev, "smbus", -1); + sc->smb = device_add_child(sc->dev, "iicbus", -1); if (sc->smb == NULL) { device_printf(sc->dev, "smbus driver not found\n"); error = ENXIO; -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Oct 4 09:17:57 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6139AF49E5; Tue, 4 Oct 2016 09:17:57 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A1C851062; Tue, 4 Oct 2016 09:17:56 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA00340; Tue, 04 Oct 2016 12:16:25 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brLpo-0006jM-Tm; Tue, 04 Oct 2016 12:16:24 +0300 Subject: Re: Regression with revision 303970 (was kern.proc.pathname failure while booting from zfs) To: Konstantin Belousov References: <1aebfb2b-5df6-abe0-686f-b170fdaef510@FreeBSD.org> <20160904145103.GD83214@kib.kiev.ua> Cc: Frederic Chardon , freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-fs@FreeBSD.org From: Andriy Gapon Message-ID: <7a30660a-1914-2f61-c162-7f9c2a7f6096@FreeBSD.org> Date: Tue, 4 Oct 2016 12:15:29 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 09:17:57 -0000 I've written a patch that implements zfs_vptocnp() using z_parent property. The new code should be 100% reliable for directories and "mostly" reliable for files (that is, when hardlinks across directories are not used). Could you please review / test it? https://reviews.freebsd.org/D8146 Thanks! -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Oct 4 09:53:21 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 099FBAF38BD for ; Tue, 4 Oct 2016 09:53:21 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 67602A88 for ; Tue, 4 Oct 2016 09:53:19 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 47876 invoked by uid 89); 4 Oct 2016 09:46:36 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@195.30.121.97) by mail.grem.de with ESMTPA; 4 Oct 2016 09:46:36 -0000 Date: Tue, 4 Oct 2016 11:46:35 +0200 From: Michael Gmelin To: Andriy Gapon Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161004114635.64857a29@bsd64.grem.de> In-Reply-To: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 09:53:21 -0000 On Tue, 4 Oct 2016 01:04:10 +0300 Andriy Gapon wrote: > On 03/10/2016 23:25, Michael Gmelin wrote: > > On Mon, 3 Oct 2016 19:41:17 +0300 > > Andriy Gapon wrote: > > > >> On 03/10/2016 19:07, Michael Gmelin wrote: > >>> I upgraded the latter the r306641, applied your patches (cleanly) > >>> and ran "make kernel" (GENERIC kernel), added the entries to > >>> device.hints and rebooted. Unfortunately ig4 won't load: > >>> > >>> # kldload ig4 > >>> link_elf_obj: symbol iicbus_transfer_desc undefined > >>> linker_load_file: Unsupported file type > >> > >> Hmm, seems like forgot to declare the iicbus module dependency. > >> Could you please kldload iicbus and see if that helps? > >> Meanwhile I'll add the dependency. > > > > Unfortunately this doesn't help, you should be able to reproduce it > > yourself without access to the actual hardware though. > > > > I worked around this by adding the iicbus dependency to ig4_pci.c > > (and also to "files"). > > Okay, this should be in the latest patch anyway. Based on what you wrote, I wasn't aware that there was a new patch. I downloaded the latest version from the same URL as your first one and built a new kernel. > > > Now loading ig4 works and both lynx point controllers are detected. > > Loading isl doesn't create any output and doesn't seem to detect any > > devices. Also, devinfo shows both controllers (ig4iic0, ig4iic1), > > but no iicbus devices. > > > > # devinfo | grep iic > > ig4iic0 > > ig4iic1 > > Is there anything interesting from from ig4 in the log / dmesg? > Could you please check that your copy of the patch contains this > chunk? @@ -549,7 +780,7 @@ ig4iic_attach(ig4iic_softc_t *sc) > IG4_CTL_RESTARTEN | > IG4_CTL_SPEED_STD); > > - sc->smb = device_add_child(sc->dev, "smbus", -1); > + sc->smb = device_add_child(sc->dev, "iicbus", -1); > if (sc->smb == NULL) { > device_printf(sc->dev, "smbus driver not found\n"); > error = ENXIO; > That code was in there, yes. iicbus(0|1) actually show up in devinfo -v, but nothing else works. You can find a log file and various outputs (dmesg, devinfo etc) here: https://people.freebsd.org/~grembo/c720-20161104.log -m -- Michael Gmelin From owner-freebsd-current@freebsd.org Tue Oct 4 10:08:32 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EBB6AF3E4A; Tue, 4 Oct 2016 10:08:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 96A6E684; Tue, 4 Oct 2016 10:08:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA00469; Tue, 04 Oct 2016 13:08:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brMeD-0006mB-Fb; Tue, 04 Oct 2016 13:08:29 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Message-ID: Date: Tue, 4 Oct 2016 13:07:28 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161004114635.64857a29@bsd64.grem.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 10:08:32 -0000 On 04/10/2016 12:46, Michael Gmelin wrote: > iicbus(0|1) actually show up in devinfo -v, but nothing else works. > > You can find a log file and various outputs (dmesg, devinfo etc) here: > > https://people.freebsd.org/~grembo/c720-20161104.log Thank you. Could you please double-check that device.hints contains the necessary hints? Could you also set debug.bootverbose=1 before kldload ig4 and kldload isl and show me any new log messages that appear after doing kldload? -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue Oct 4 10:58:35 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D814FAF4BD8 for ; Tue, 4 Oct 2016 10:58:35 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.28]) (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 9F5EFF53 for ; Tue, 4 Oct 2016 10:58:34 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.171.4] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1brNBA-0000v2-VR for freebsd-current@freebsd.org; Tue, 04 Oct 2016 12:42:33 +0200 Date: Tue, 4 Oct 2016 12:42:32 +0200 From: Fabian Keil To: freebsd-current@freebsd.org Subject: Re: ZFS - Abyssal slow on copying Message-ID: <20161004124232.6d655b61@fabiankeil.de> In-Reply-To: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> References: <20161002212504.2d782002.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/F8ZBStBvUfFgsuEJviflzLx"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 10:58:35 -0000 --Sig_/F8ZBStBvUfFgsuEJviflzLx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "O. Hartmann" wrote: > Running 12-CURRENT (FreeBSD 12.0-CURRENT #32 r306579: Sun Oct 2 09:34:50= CEST 2016 ), I > have a NanoBSD setup which creates an image for a router device. >=20 > The problem I face is related to ZFS. The system has a system's SSD (Sams= ung 850 Pro, > 256GB) which has an UFS filesystem. Aditionally, I have also a backup and= a data HDD, > both WD, one 3 TB WD RED Pro, on 4 TB WD RED (the backup device). Both th= e sources for > the NanoBSD and the object tree as well as the NANO_WORLDDIR are residing= on the 3 TB > data drive.=20 >=20 > The box itself has 8 GB RAM. When it comes to create the memory disk, whi= ch is ~ 1,3 GB > in size, the NanoBSD script starts creating the memory disk and then inst= alling world > into this memory disk. And this part is a kind of abyssal in terms of the= speed. Can you reproduce the issue if you replace the memory disk with a zvol or tmpfs? While I agree that depulication could be the cause of the problem, it probably wouldn't hurt to rule out a memory-disk related issue before recreating the pool. Fabian --Sig_/F8ZBStBvUfFgsuEJviflzLx Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlfzh5kACgkQBYqIVf93VJ36UQCeLN8gS1+IYN7XyocdiUCxrOtJ GVQAmweiXND8rPccqdMgZFiEf++Dev1H =lnl0 -----END PGP SIGNATURE----- --Sig_/F8ZBStBvUfFgsuEJviflzLx-- From owner-freebsd-current@freebsd.org Tue Oct 4 05:47:28 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32D25AF43BE for ; Tue, 4 Oct 2016 05:47:28 +0000 (UTC) (envelope-from robert.burmeister@utoledo.edu) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 19358F6A for ; Tue, 4 Oct 2016 05:47:27 +0000 (UTC) (envelope-from robert.burmeister@utoledo.edu) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id 028E532C5F8A for ; Mon, 3 Oct 2016 22:42:39 -0700 (PDT) Date: Mon, 3 Oct 2016 22:47:26 -0700 (MST) From: Robert_Burmeister To: freebsd-current@freebsd.org Message-ID: <1475560046440-6134583.post@n6.nabble.com> In-Reply-To: <57EDE9A9.1040304@UToledo.edu> References: <57EDE9A9.1040304@UToledo.edu> Subject: Re: FreeBSD 11.0 i386 buildworld failure MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 04 Oct 2016 11:22:04 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 05:47:28 -0000 Robert_Burmeister wrote > FreeBSD 11.0 i386 Stable > > I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September > 2016. > Upon refreshing and rebuilding world to catch the 28 September 2016 > Release update, > buildworld failed using the same build options that had worked for the 22 > Sept code. Refreshed source to FreeBSD 11 Stable revision 306664 as of Oct 3rd and tried buildworld with a FreeBSD 10.3 backup kernel with the same result. Has anyone been able to bootstrap FreeBSD 11.0 i386? -- View this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134583.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@freebsd.org Tue Oct 4 12:23:34 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F15DDAF4C2C for ; Tue, 4 Oct 2016 12:23:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C198CDA6; Tue, 4 Oct 2016 12:23:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id u94CNR6U011987 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Oct 2016 06:23:27 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u94CNQnq011984; Tue, 4 Oct 2016 06:23:26 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 4 Oct 2016 06:23:26 -0600 (MDT) From: Warren Block To: John Baldwin cc: freebsd-current@freebsd.org, Ngie Cooper , Ernie Luzar , "Hartmann, O." Subject: Re: Destroy GPT partition scheme absolutely, how? In-Reply-To: <1785064.lgVzRW13Wf@ralph.baldwin.cx> Message-ID: References: <20160926150109.0d0d793e@hermann> <57E92726.2020605@gmail.com> <5484D815-4B17-456B-BA60-CC6F4E97AFE3@gmail.com> <1785064.lgVzRW13Wf@ralph.baldwin.cx> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 04 Oct 2016 06:23:27 -0600 (MDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 12:23:35 -0000 On Mon, 26 Sep 2016, John Baldwin wrote: > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote: >> >>> On Sep 26, 2016, at 22:48, Ernie Luzar wrote: >> >> ... >> >>> This little script has been posted before. Maybe it will be what your looking for. Called gpart.nuke >>> >>> #! /bin/sh >>> echo "What disk do you want" >>> echo "to wipe? For example - da1 :" >>> read disk >>> echo "OK, in 10 seconds I will destroy all data on $disk!" >>> echo "Press CTRL+C to abort!" >>> sleep 10 >>> diskinfo ${disk} | while read disk sectorsize size sectors other >>> do >>> # Delete MBR and partition table. >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1 >>> # Delete GEOM metadata. >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr $sectors - 2` count=2 >>> done >> >> Why not just use "gpart destroy -F provider"? > > That doesn't always work. In particular, if a disk was partitioned with GPT > and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the > MBR will leave most of the GPT intact and the disk will come up with the old > GPT partitions, not as a raw disk. Right. So do a gpart destroy -F of whatever is on there, ignoring errors, then a gpart create -s gpt. Now there is definitely a secondary GPT, and a final gpart destroy -F removes it cleanly. From owner-freebsd-current@freebsd.org Tue Oct 4 17:43:01 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D002AF5ACC for ; Tue, 4 Oct 2016 17:43:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F1462C43 for ; Tue, 4 Oct 2016 17:43:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 1394210AF8F; Tue, 4 Oct 2016 13:43:00 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Robert_Burmeister Subject: Re: FreeBSD 11.0 i386 buildworld failure Date: Tue, 04 Oct 2016 10:36:15 -0700 Message-ID: <1615707.F6RsM24uq8@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <1475560046440-6134583.post@n6.nabble.com> References: <57EDE9A9.1040304@UToledo.edu> <1475560046440-6134583.post@n6.nabble.com> 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.4.3 (mail.baldwin.cx); Tue, 04 Oct 2016 13:43:00 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 17:43:01 -0000 On Monday, October 03, 2016 10:47:26 PM Robert_Burmeister wrote: > Robert_Burmeister wrote > > FreeBSD 11.0 i386 Stable > > > > I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September > > 2016. > > Upon refreshing and rebuilding world to catch the 28 September 2016 > > Release update, > > buildworld failed using the same build options that had worked for the 22 > > Sept code. > > Refreshed source to FreeBSD 11 Stable revision 306664 as of Oct 3rd > and tried buildworld with a FreeBSD 10.3 backup kernel > with the same result. > > Has anyone been able to bootstrap FreeBSD 11.0 i386? It seems like your build is using the host headers during the build instead of the staged headers (both errors were indicative of that). I would check your clock via ntpdate or the like in case that is confusing make into not installing the headers. Also, a build with an empty /usr/obj would be the next thing to try. -- John Baldwin From owner-freebsd-current@freebsd.org Tue Oct 4 17:43:02 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7DDCAF5ACF for ; Tue, 4 Oct 2016 17:43:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86C91C44 for ; Tue, 4 Oct 2016 17:43:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 631B710AF88; Tue, 4 Oct 2016 13:43:01 -0400 (EDT) From: John Baldwin To: Warren Block Cc: freebsd-current@freebsd.org, Ngie Cooper , Ernie Luzar , "Hartmann, O." Subject: Re: Destroy GPT partition scheme absolutely, how? Date: Tue, 04 Oct 2016 10:24:39 -0700 Message-ID: <16661613.eI4FiDRTSB@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <20160926150109.0d0d793e@hermann> <1785064.lgVzRW13Wf@ralph.baldwin.cx> 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.4.3 (mail.baldwin.cx); Tue, 04 Oct 2016 13:43:01 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 17:43:02 -0000 On Tuesday, October 04, 2016 06:23:26 AM Warren Block wrote: > On Mon, 26 Sep 2016, John Baldwin wrote: > > > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote: > >> > >>> On Sep 26, 2016, at 22:48, Ernie Luzar wrote: > >> > >> ... > >> > >>> This little script has been posted before. Maybe it will be what your looking for. Called gpart.nuke > >>> > >>> #! /bin/sh > >>> echo "What disk do you want" > >>> echo "to wipe? For example - da1 :" > >>> read disk > >>> echo "OK, in 10 seconds I will destroy all data on $disk!" > >>> echo "Press CTRL+C to abort!" > >>> sleep 10 > >>> diskinfo ${disk} | while read disk sectorsize size sectors other > >>> do > >>> # Delete MBR and partition table. > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1 > >>> # Delete GEOM metadata. > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr $sectors - 2` count=2 > >>> done > >> > >> Why not just use "gpart destroy -F provider"? > > > > That doesn't always work. In particular, if a disk was partitioned with GPT > > and then you use normal MBR on it afterwards, the 'gpart destroy -F' of the > > MBR will leave most of the GPT intact and the disk will come up with the old > > GPT partitions, not as a raw disk. > > Right. So do a gpart destroy -F of whatever is on there, ignoring > errors, then a gpart create -s gpt. Now there is definitely a secondary > GPT, and a final gpart destroy -F removes it cleanly. It is usually simpler to just dd zeroes over the first N and last N sectors. The only fool-proof way to ensure you don't have dangling tables in the middle of the disk is to zero the entire disk, but that takes too long. -- John Baldwin From owner-freebsd-current@freebsd.org Tue Oct 4 18:53:25 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 173A4AF5CDF for ; Tue, 4 Oct 2016 18:53:25 +0000 (UTC) (envelope-from sobomax@sippysoft.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 D22E0797 for ; Tue, 4 Oct 2016 18:53:24 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-io0-x22e.google.com with SMTP id r30so37700432ioi.1 for ; Tue, 04 Oct 2016 11:53:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zlMvuL3grOV/njxdiaW1nuss9YiUKTYj8/A8pn6MwO4=; b=Ir+Xu1KmwbTZbfS5XKwkV80nc3NZcpEFBSfS8LF7f8WJR0fbVI6NhwC4XyFvbMVPOV UTOoUjGF35uiOd3G1LSoyIMPH81KVAAeBvcunqPw141iAKjonIjte9FHv8YBZrYFmYVA BCCY45TCJQauHuHA799+IoVZnDVFZ+3FDpdOouKO3mHUA6AJB01cboLBlvZAjHwOJb/M N/HbgSs+j2buWGqg1x86mT472NBs6OeFbDfGVn3srXxw8KOB2ajhoJ/zA+jOP1m2wvv9 g61GgahgkYn12lMtNbzgKxMKw0pR/myPGfqd3dKnSnUq2GPf7/QHoL9QacgfZOnM+8B0 rIkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zlMvuL3grOV/njxdiaW1nuss9YiUKTYj8/A8pn6MwO4=; b=RwXxkW3z+MwhDZU8dDM5v9N+qscDFLRydmcOAbkn5cjJct9/DO68OIl2Uk2gKB7aae Dr3bKOWAwUUeTjfWxnRyFiCSIK0hzgCnJhsYoIzljZlsMw+RdUuUQErDA0Zgbq5ky5Rh mz1goP1lCMLULAFj+StAlRETpHoYDTbU0kmXqxHefLZIcgiX8qLD3WwR0pA9gAdFhqkb fUw/k6/gtV7A4iBN60/7Sixr3lm7dK3lbjDzNRTrcqnceNs39FHdhWHjsGcYwUhCQ1tm 41DjHCCA04xQ59+AYU7A+spRJJqQ6iVZ2W7vKZTavt/MbmcJbjQPDdzcpXAm9lFVwQ4G 85Ew== X-Gm-Message-State: AA6/9RkDrAkL+8LatHYiJEQg18axqjgJtmLHiUGJxsLfJy7wFXGQeS1QCiNmf+1jryshduyWZ17+/Uxwql4Zu7gl X-Received: by 10.107.32.75 with SMTP id g72mr6798488iog.136.1475607204129; Tue, 04 Oct 2016 11:53:24 -0700 (PDT) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.36.149.196 with HTTP; Tue, 4 Oct 2016 11:53:23 -0700 (PDT) In-Reply-To: <16661613.eI4FiDRTSB@ralph.baldwin.cx> References: <20160926150109.0d0d793e@hermann> <1785064.lgVzRW13Wf@ralph.baldwin.cx> <16661613.eI4FiDRTSB@ralph.baldwin.cx> From: Maxim Sobolev Date: Tue, 4 Oct 2016 11:53:23 -0700 X-Google-Sender-Auth: p0AURsMFc27KcqC6BrqomMc0uHU Message-ID: Subject: Re: Destroy GPT partition scheme absolutely, how? To: John Baldwin Cc: Warren Block , FreeBSD Current , Ngie Cooper , Ernie Luzar , "Hartmann, O." Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 18:53:25 -0000 For the whole disk destruction, hopefully one day we'd have BIO_DELETE coalesce code, so that you can batch of lot of operations into handful SATA commands. I've heard rumours imp@ was doing something along those lines. As well as SSD disks smart enough to process those requests in the background. Anyway, just saying. ) -Max On Tue, Oct 4, 2016 at 10:24 AM, John Baldwin wrote: > On Tuesday, October 04, 2016 06:23:26 AM Warren Block wrote: > > On Mon, 26 Sep 2016, John Baldwin wrote: > > > > > On Tuesday, September 27, 2016 12:36:22 AM Ngie Cooper wrote: > > >> > > >>> On Sep 26, 2016, at 22:48, Ernie Luzar wrote: > > >> > > >> ... > > >> > > >>> This little script has been posted before. Maybe it will be what > your looking for. Called gpart.nuke > > >>> > > >>> #! /bin/sh > > >>> echo "What disk do you want" > > >>> echo "to wipe? For example - da1 :" > > >>> read disk > > >>> echo "OK, in 10 seconds I will destroy all data on $disk!" > > >>> echo "Press CTRL+C to abort!" > > >>> sleep 10 > > >>> diskinfo ${disk} | while read disk sectorsize size sectors other > > >>> do > > >>> # Delete MBR and partition table. > > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1 > > >>> # Delete GEOM metadata. > > >>> dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr > $sectors - 2` count=2 > > >>> done > > >> > > >> Why not just use "gpart destroy -F provider"? > > > > > > That doesn't always work. In particular, if a disk was partitioned > with GPT > > > and then you use normal MBR on it afterwards, the 'gpart destroy -F' > of the > > > MBR will leave most of the GPT intact and the disk will come up with > the old > > > GPT partitions, not as a raw disk. > > > > Right. So do a gpart destroy -F of whatever is on there, ignoring > > errors, then a gpart create -s gpt. Now there is definitely a secondary > > GPT, and a final gpart destroy -F removes it cleanly. > > It is usually simpler to just dd zeroes over the first N and last N > sectors. > The only fool-proof way to ensure you don't have dangling tables in the > middle of the disk is to zero the entire disk, but that takes too long. > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Tue Oct 4 19:27:32 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FA1AAF57B5 for ; Tue, 4 Oct 2016 19:27:32 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::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 248D7E77 for ; Tue, 4 Oct 2016 19:27:31 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x22c.google.com with SMTP id p138so230874467wmb.1 for ; Tue, 04 Oct 2016 12:27:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=xD0MHZupERpeZVDOzVkA0vwa4DDanyUBXAjtPctcC08=; b=cDb9uzxQmfpH+Fj/5knTzlcTBq+lZsSnDetv/42WM84sQ4+/sgjXyn+w6AF9m928H0 oeYFV8vpw+ijaHaVJOPCbTf0iB+O2zTiGtF8Q8J6X3RObrL9cDjjnK8ZW3FQ0TaU5UR0 bv2p3OggFjnRinVj5GC3UOSF3jr1AIyWwLJaX9iTlqpCBWlhnePQnJMeIr47u1zB0hmj 6p7nEmNOhflz7uybVkYTboGf1pvgRXmCdpo/p4JbfBxxtSBUAaeetsqKD2Ji/r30RlJx MvWvgC3HHDhY942sXwlVfRnEhO+ahPojo5LmX2sO3LPWlWsQvxG5BtIMD5HTfCXX3Nnk 8K5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=xD0MHZupERpeZVDOzVkA0vwa4DDanyUBXAjtPctcC08=; b=MoHysIUQbexI34IDM5I0dgkQZ6GNJkDSmqri5n4J9dNVzCHYrMa7/J70EIQXvpfBNP GOAn5YL11NlloFrd2J7BQd1uJPNRSGFCfkRo5uV5sAp4vnIyAxNrlY/xExRXjLxAuCRV EyOIEQebk6MG1HDluUntgt3ti0qkLPb0owOposLQT0QDSo8uYa6/3KKYPJddaVU9qBtH ZpZTdskklfehPAeLs7nRK+UfjMNQv945/yTEJxvEP+n+M46qpb965mneboK27f0IprDC 9r5GknxxryMllZkxHhjHfuBzU16XSl4QKds4PLJq5bQ9ZdU0cnRKWpjkCpiwePTRKW4w 8JKQ== X-Gm-Message-State: AA6/9Rl3LU+FMi4Fk0+EVW1qzNi+nwrrxffVpP/o3xxF1QXar4NDtlCYoV99VsdSvBxsy47p X-Received: by 10.28.212.129 with SMTP id l123mr18102962wmg.22.1475609249932; Tue, 04 Oct 2016 12:27:29 -0700 (PDT) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id ce6sm5010055wjc.27.2016.10.04.12.27.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Oct 2016 12:27:29 -0700 (PDT) Subject: Re: Destroy GPT partition scheme absolutely, how? To: freebsd-current@freebsd.org References: <20160926150109.0d0d793e@hermann> <1785064.lgVzRW13Wf@ralph.baldwin.cx> <16661613.eI4FiDRTSB@ralph.baldwin.cx> From: Steven Hartland Message-ID: <3f32dbb8-2bab-6bb1-839b-33dd8ab0a1c9@multiplay.co.uk> Date: Tue, 4 Oct 2016 20:27:41 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 19:27:32 -0000 CAM already does this, doesn't really help with speed as much as you might think though. On 04/10/2016 19:53, Maxim Sobolev wrote: > For the whole disk destruction, hopefully one day we'd have BIO_DELETE > coalesce code, so that you can batch of lot of operations into handful SATA > commands. I've heard rumours imp@ was doing something along those lines. As > well as SSD disks smart enough to process those requests in the background. > Anyway, just saying. ) > From owner-freebsd-current@freebsd.org Tue Oct 4 22:55:16 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D084AF4B2E for ; Tue, 4 Oct 2016 22:55:16 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id D9C67B7A for ; Tue, 4 Oct 2016 22:55:15 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 57695 invoked by uid 89); 4 Oct 2016 22:48:33 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 4 Oct 2016 22:48:33 -0000 Date: Wed, 5 Oct 2016 00:48:31 +0200 From: Michael Gmelin To: Andriy Gapon Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161005004831.2a2fdc4b@bsd64.grem.de> In-Reply-To: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 22:55:16 -0000 On Tue, 4 Oct 2016 13:07:28 +0300 Andriy Gapon wrote: > On 04/10/2016 12:46, Michael Gmelin wrote: > > iicbus(0|1) actually show up in devinfo -v, but nothing else works. > > > > You can find a log file and various outputs (dmesg, devinfo etc) > > here: > > > > https://people.freebsd.org/~grembo/c720-20161104.log > > Thank you. > Could you please double-check that device.hints contains the > necessary hints? Could you also set debug.bootverbose=1 before > kldload ig4 and kldload isl and show me any new log messages that > appear after doing kldload? > Double-checked the hints, it's all ok. Please find a more verbose log file of loading the kernel modules here: https://people.freebsd.org/~grembo/c720-20161105.log -m -- Michael Gmelin From owner-freebsd-current@freebsd.org Wed Oct 5 04:57:31 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B380AF6560; Wed, 5 Oct 2016 04:57:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 F2D4D3CD; Wed, 5 Oct 2016 04:57:30 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-653ff7000000380d-7f-57f4883283eb Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id A0.22.14349.23884F75; Wed, 5 Oct 2016 00:57:22 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id u954vLvr023254; Wed, 5 Oct 2016 00:57:21 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u954vIIX020121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Oct 2016 00:57:20 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u954vHot001338; Wed, 5 Oct 2016 00:57:17 -0400 (EDT) Date: Wed, 5 Oct 2016 00:57:17 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Final call for 2016Q3 quarterly status reports Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCIsWRmVeSWpSXmKPExsUixCmqrGvU8SXcoHOyjsWua6fZLea8+cBk sX3zP0YHZo8Zn+azBDBGcdmkpOZklqUW6dslcGVcWf6buaCHp+LvDMEGxhauLkZODgkBE4kD zbfYuhi5OIQE2pgkzr5fwwrhbGCU2NC1gBHCOcgk8f5TEyNIi5BAvcSZNXvYQWwWAS2Jlp55 LCA2m4CaxPoV15ghxipKbD41CcwWEZCX2Nf0HqyeGcjesnoyG4gtLGAu8ffXVbA4r4CDxPLb B8HqRQV0JFbvn8ICEReUODnzCQtEr5bE8unbWCYw8s9CkpqFJLWAkWkVo2xKbpVubmJmTnFq sm5xcmJeXmqRrqlebmaJXmpK6SZGUOCxuyjtYJz4z+sQowAHoxIPb8fmz+FCrIllxZW5hxgl OZiURHmXhn4JF+JLyk+pzEgszogvKs1JLT7EKMHBrCTCq9UClONNSaysSi3Kh0lJc7AoifN2 zTgQLiSQnliSmp2aWpBaBJOV4eBQkuD93AbUKFiUmp5akZaZU4KQZuLgBBnOAzT8civI8OKC xNzizHSI/ClGRSlx3gSQZgGQREZpHlwvODHsZlJ9xSgO9Iowr307UBUPMKnAdb8CGswENDhw yweQwSWJCCmpBkYZrgMTljxN8Go7ZRPy+0XmCbn/P7n7g+u2qfUqMi441rRt84lY58hK64Qr geWvS0638XEx8Z7KzylMljURr9Qz9GS4ecNkt46QuJiqtHUWv6vr+X4xlzKFaTuT1wmel594 rUFs8k6NgkuTIgTamE/6LghcnbC7fNGig3O3f213Om6iX1N8UImlOCPRUIu5qDgRALm+GZDn AgAA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 04:57:31 -0000 Dear FreeBSD Community, The deadline for the submissions to the next FreeBSD Quarterly Status is October 9, 2016, for work done in July through September. This is the final call for submissions; please let us know if you are considering making a submission but are not sure that your submission will be ready by the deadline. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly at FreeBSD.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2016Q3 reports! Thanks, Ben (on behalf of monthly@) [1] https://www.FreeBSD.org/cgi/monthly.cgi [2] https://www.FreeBSD.org/news/status/report-sample.xml [3] https://www.FreeBSD.org/news/status/howto.html [4] https://www.FreeBSD.org/news/status/report-2016-01-2016-03.html [4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html From owner-freebsd-current@freebsd.org Wed Oct 5 05:50:30 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 795FFAF6ED6; Wed, 5 Oct 2016 05:50:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 63949D20; Wed, 5 Oct 2016 05:50:28 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA02872; Wed, 05 Oct 2016 08:50:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brf5w-0007o6-Uq; Wed, 05 Oct 2016 08:50:20 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Message-ID: <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> Date: Wed, 5 Oct 2016 08:48:59 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161005004831.2a2fdc4b@bsd64.grem.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 05:50:30 -0000 On 05/10/2016 01:48, Michael Gmelin wrote: > Double-checked the hints, it's all ok. > > Please find a more verbose log file of loading the kernel modules here: > > https://people.freebsd.org/~grembo/c720-20161105.log Unfortunately this doesn't provide any new insights. Could you please add some printf-s to iicbus_hinted_child() in sys/dev/iicbus/iicbus.c to see whether the isl devices are really added via the hints and what their properties are? Also, some printf-s to isl_probe() to see if it gets called and where it fails. And, just in case, to ig4iic_start() to see if gets called. Thank you! -- Andriy Gapon From owner-freebsd-current@freebsd.org Wed Oct 5 10:21:00 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40913AF6180 for ; Wed, 5 Oct 2016 10:21:00 +0000 (UTC) (envelope-from sb@sysinfo.pl) Received: from cloudserver114020.home.net.pl (cloudserver114020.home.net.pl [188.128.140.228]) by mx1.freebsd.org (Postfix) with SMTP id AD657856 for ; Wed, 5 Oct 2016 10:20:58 +0000 (UTC) (envelope-from sb@sysinfo.pl) Received: from 88-220-168-84.expressnet.pl (88.220.168.84) (HELO SBKPPT) by sysinfo.home.pl (188.128.140.228) with SMTP (IdeaSmtpServer v0.80.3) id 94e6683ad6562b94; Wed, 5 Oct 2016 12:20:51 +0200 From: =?iso-8859-2?Q?S=B3awomir_Babi=F1ski_|_SYSINFO?= To: Subject: Random panics Date: Wed, 5 Oct 2016 12:20:55 +0200 Message-ID: <091601d21ef2$28678ec0$7936ac40$@sysinfo.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdIe7QfPziFdV9tbS1SZnwR1N74c4A== Content-Language: pl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 10:21:00 -0000 Hi I have random panics. OS: FreeBSD 12.0-CURRENT #0 r305973M: Wed Sep 21 15:55:09 CEST 2016. Ipfilter compiled with LARGE_NAT to support our over 400 computers on lan. Ipnat unstable on high load? Last 3 captured: #1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: <110>ipfw: 3700 Deny TCP 200.100.229.149:12750 155.133.23.8:23 out via em1 <110>ipfw: 3700 Deny TCP 216.243.31.2:40159 155.133.22.217:443 out via em1 <110>ipfw: 3700 Deny TCP 192.168.0.101:48000 31.13.81.13:443 in via em1 Kernel page fault with the following non-sleepable locks held: shared rw ipf IP NAT rwlock (ipf IP NAT rwlock) r = 0 (0xffffffff818d6170) locked @ /usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:4925 shared rw ipf filter rwlock (ipf filter rwlock) r = 0 (0xffffffff818d6058) locked @ /usr/src/sys/contrib/ipfilter/netinet/fil.c:3024 shared rm PFil shared rmlock (PFil shared rmlock) r = 0 (0xffffffff81eab3f0) locked @ /usr/src/sys/net/pfil.c:78 stack backtrace: #0 0xffffffff80af7b90 at witness_debugger+0x70 #1 0xffffffff80af8e77 at witness_warn+0x3d7 #2 0xffffffff80f34507 at trap_pfault+0x57 #3 0xffffffff80f33bbb at trap+0x28b #4 0xffffffff80f14461 at calltrap+0x8 #5 0xffffffff803a7e87 at ipf_proxy_check+0x127 #6 0xffffffff8039b36b at ipf_nat_out+0x6db #7 0xffffffff8039a72f at ipf_nat_checkout+0x1ff #8 0xffffffff80381496 at ipf_check+0x726 #9 0xffffffff80ba08cb at pfil_run_hooks+0x8b #10 0xffffffff80c0326b at ip_tryforward+0x26b #11 0xffffffff80c058b7 at ip_input+0x377 #12 0xffffffff80b9f7b0 at netisr_dispatch_src+0x80 #13 0xffffffff80cecc07 at dummynet_send+0x167 #14 0xffffffff80cec530 at dummynet_task+0x310 #15 0xffffffff80aeb5bc at taskqueue_run_locked+0x13c #16 0xffffffff80aec138 at taskqueue_thread_loop+0x88 #17 0xffffffff80a5bd74 at fork_exit+0x84 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xe fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff803a09cd stack pointer = 0x28:0xfffffe023ab3e4e0 frame pointer = 0x28:0xfffffe023ab3e5c0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (dummynet) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe023ab3e060 vpanic() at vpanic+0x182/frame 0xfffffe023ab3e0e0 panic() at panic+0x43/frame 0xfffffe023ab3e140 trap_fatal() at trap_fatal+0x331/frame 0xfffffe023ab3e1a0 trap_pfault() at trap_pfault+0x1fd/frame 0xfffffe023ab3e200 trap() at trap+0x28b/frame 0xfffffe023ab3e410 calltrap() at calltrap+0x8/frame 0xfffffe023ab3e410 --- trap 0xc, rip = 0xffffffff803a09cd, rsp = 0xfffffe023ab3e4e0, rbp = 0xfffffe023ab3e5c0 --- ipf_p_ftp_process() at ipf_p_ftp_process+0x16d/frame 0xfffffe023ab3e5c0 ipf_proxy_check() at ipf_proxy_check+0x127/frame 0xfffffe023ab3e630 ipf_nat_out() at ipf_nat_out+0x6db/frame 0xfffffe023ab3e690 ipf_nat_checkout() at ipf_nat_checkout+0x1ff/frame 0xfffffe023ab3e740 ipf_check() at ipf_check+0x726/frame 0xfffffe023ab3e8b0 pfil_run_hooks() at pfil_run_hooks+0x8b/frame 0xfffffe023ab3e940 ip_tryforward() at ip_tryforward+0x26b/frame 0xfffffe023ab3e9c0 ip_input() at ip_input+0x377/frame 0xfffffe023ab3ea20 netisr_dispatch_src() at netisr_dispatch_src+0x80/frame 0xfffffe023ab3ea80 dummynet_send() at dummynet_send+0x167/frame 0xfffffe023ab3eac0 dummynet_task() at dummynet_task+0x310/frame 0xfffffe023ab3eb20 taskqueue_run_locked() at taskqueue_run_locked+0x13c/frame 0xfffffe023ab3eb80 taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe023ab3ebb0 fork_exit() at fork_exit+0x84/frame 0xfffffe023ab3ebf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe023ab3ebf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 3h12m45s Dumping 641 out of 8158 MB:..3%..13%..23%..33%..43%..53%..63%..73%..83%..93% Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/fdescfs.ko.debug...done. done. Loaded symbols for /boot/kernel/fdescfs.ko Reading symbols from /boot/kernel/iscsi.ko...Reading symbols from /usr/lib/debug//boot/kernel/iscsi.ko.debug...done. done. Loaded symbols for /boot/kernel/iscsi.ko #0 doadump (textdump=1) at pcpu.h:221 221 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) list *0xffffffff803a09cd 0xffffffff803a09cd is in ipf_p_ftp_process (ip_ftp_pxy.c:1336). 1331 aps = nat->nat_aps; 1332 1333 sel = aps->aps_sel[1 - rv]; 1334 sel2 = aps->aps_sel[rv]; 1335 if (rv == 1) { 1336 seqoff = aps->aps_seqoff[sel]; 1337 if (aps->aps_seqmin[sel] > seqoff + thseq) 1338 seqoff = aps->aps_seqoff[!sel]; 1339 ackoff = aps->aps_ackoff[sel2]; 1340 if (aps->aps_ackmin[sel2] > ackoff + thack) Current language: auto; currently minimal (kgdb) backtrace #0 doadump (textdump=1) at pcpu.h:221 #1 0xffffffff80a97b75 in kern_reboot (howto=) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80a9814b in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80a98193 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80f344a1 in trap_fatal (frame=0xfffffe023ab3e420, eva=14) at /usr/src/sys/amd64/amd64/trap.c:837 #5 0xffffffff80f346ad in trap_pfault (frame=0xfffffe023ab3e420, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:694 #6 0xffffffff80f33bbb in trap (frame=0xfffffe023ab3e420) at /usr/src/sys/amd64/amd64/trap.c:443 #7 0xffffffff80f14461 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff803a09cd in ipf_p_ftp_process (softf=, fin=0xfffffe023ab3e780, nat=0xfffff801c2ad7400, ftp=0xfffff800433e4c00, rv=) at ip_ftp_pxy.c:1331 #9 0xffffffff803a7e87 in ipf_proxy_check (fin=0xfffffe023ab3e780, nat=0xfffff801c2ad7400) at /usr/src/sys/contrib/ipfilter/netinet/ip_proxy.c:992 ---Type to continue, or q to quit---q Quit (kgdb) #2 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Kernel page fault with the following non-sleepable locks held: shared rw ipf IP NAT rwlock (ipf IP NAT rwlock) r = 0 (0xffffffff818d6170) locked @ /usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:4925 shared rw ipf filter rwlock (ipf filter rwlock) r = 0 (0xffffffff818d6058) locked @ /usr/src/sys/contrib/ipfilter/netinet/fil.c:3024 shared rm PFil shared rmlock (PFil shared rmlock) r = 0 (0xffffffff81eab3f0) locked @ /usr/src/sys/net/pfil.c:78 stack backtrace: #0 0xffffffff80af7b90 at witness_debugger+0x70 #1 0xffffffff80af8e77 at witness_warn+0x3d7 #2 0xffffffff80f34507 at trap_pfault+0x57 #3 0xffffffff80f33bbb at trap+0x28b #4 0xffffffff80f14461 at calltrap+0x8 #5 0xffffffff803a7e87 at ipf_proxy_check+0x127 #6 0xffffffff8039b36b at ipf_nat_out+0x6db #7 0xffffffff8039a72f at ipf_nat_checkout+0x1ff #8 0xffffffff80381496 at ipf_check+0x726 #9 0xffffffff80ba08cb at pfil_run_hooks+0x8b #10 0xffffffff80c0326b at ip_tryforward+0x26b #11 0xffffffff80c058b7 at ip_input+0x377 #12 0xffffffff80b9f7b0 at netisr_dispatch_src+0x80 #13 0xffffffff80cecc07 at dummynet_send+0x167 #14 0xffffffff80cec530 at dummynet_task+0x310 #15 0xffffffff80aeb5bc at taskqueue_run_locked+0x13c #16 0xffffffff80aec138 at taskqueue_thread_loop+0x88 #17 0xffffffff80a5bd74 at fork_exit+0x84 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0xe fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff803a09cd stack pointer = 0x28:0xfffffe023ab3e4e0 frame pointer = 0x28:0xfffffe023ab3e5c0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (dummynet) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe023ab3e060 vpanic() at vpanic+0x182/frame 0xfffffe023ab3e0e0 panic() at panic+0x43/frame 0xfffffe023ab3e140 trap_fatal() at trap_fatal+0x331/frame 0xfffffe023ab3e1a0 trap_pfault() at trap_pfault+0x1fd/frame 0xfffffe023ab3e200 trap() at trap+0x28b/frame 0xfffffe023ab3e410 calltrap() at calltrap+0x8/frame 0xfffffe023ab3e410 --- trap 0xc, rip = 0xffffffff803a09cd, rsp = 0xfffffe023ab3e4e0, rbp = 0xfffffe023ab3e5c0 --- ipf_p_ftp_process() at ipf_p_ftp_process+0x16d/frame 0xfffffe023ab3e5c0 ipf_proxy_check() at ipf_proxy_check+0x127/frame 0xfffffe023ab3e630 ipf_nat_out() at ipf_nat_out+0x6db/frame 0xfffffe023ab3e690 ipf_nat_checkout() at ipf_nat_checkout+0x1ff/frame 0xfffffe023ab3e740 ipf_check() at ipf_check+0x726/frame 0xfffffe023ab3e8b0 pfil_run_hooks() at pfil_run_hooks+0x8b/frame 0xfffffe023ab3e940 ip_tryforward() at ip_tryforward+0x26b/frame 0xfffffe023ab3e9c0 ip_input() at ip_input+0x377/frame 0xfffffe023ab3ea20 netisr_dispatch_src() at netisr_dispatch_src+0x80/frame 0xfffffe023ab3ea80 dummynet_send() at dummynet_send+0x167/frame 0xfffffe023ab3eac0 dummynet_task() at dummynet_task+0x310/frame 0xfffffe023ab3eb20 taskqueue_run_locked() at taskqueue_run_locked+0x13c/frame 0xfffffe023ab3eb80 taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe023ab3ebb0 fork_exit() at fork_exit+0x84/frame 0xfffffe023ab3ebf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe023ab3ebf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 3h48m19s Dumping 664 out of 8158 MB:..3%..13%..22%..32%..41%..51%..61%..73%..82%..92% Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/fdescfs.ko.debug...done. done. Loaded symbols for /boot/kernel/fdescfs.ko Reading symbols from /boot/kernel/iscsi.ko...Reading symbols from /usr/lib/debug//boot/kernel/iscsi.ko.debug...done. done. Loaded symbols for /boot/kernel/iscsi.ko #0 doadump (textdump=1) at pcpu.h:221 221 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) list *0xffffffff803a09cd 0xffffffff803a09cd is in ipf_p_ftp_process (ip_ftp_pxy.c:1336). 1331 aps = nat->nat_aps; 1332 1333 sel = aps->aps_sel[1 - rv]; 1334 sel2 = aps->aps_sel[rv]; 1335 if (rv == 1) { 1336 seqoff = aps->aps_seqoff[sel]; 1337 if (aps->aps_seqmin[sel] > seqoff + thseq) 1338 seqoff = aps->aps_seqoff[!sel]; 1339 ackoff = aps->aps_ackoff[sel2]; 1340 if (aps->aps_ackmin[sel2] > ackoff + thack) Current language: auto; currently minimal (kgdb) backtrace #0 doadump (textdump=1) at pcpu.h:221 #1 0xffffffff80a97b75 in kern_reboot (howto=) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80a9814b in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80a98193 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80f344a1 in trap_fatal (frame=0xfffffe023ab3e420, eva=14) at /usr/src/sys/amd64/amd64/trap.c:837 #5 0xffffffff80f346ad in trap_pfault (frame=0xfffffe023ab3e420, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:694 #6 0xffffffff80f33bbb in trap (frame=0xfffffe023ab3e420) at /usr/src/sys/amd64/amd64/trap.c:443 #7 0xffffffff80f14461 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff803a09cd in ipf_p_ftp_process (softf=, fin=0xfffffe023ab3e780, nat=0xfffff800c3920400, ftp=0xfffff8016863e000, rv=) at ip_ftp_pxy.c:1331 #9 0xffffffff803a7e87 in ipf_proxy_check (fin=0xfffffe023ab3e780, nat=0xfffff800c3920400) at /usr/src/sys/contrib/ipfilter/netinet/ip_proxy.c:992 #10 0xffffffff8039b36b in ipf_nat_out (fin=0xfffffe023ab3e780, nat=0xfffff800c3920400, natadd=, nflags=1) at /usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:5315 #11 0xffffffff8039a72f in ipf_nat_checkout (fin=, passp=) at /usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:5019 #12 0xffffffff80381496 in ipf_check (ctx=, ip=, hlen=, ifp=, out=1, mp=) at /usr/src/sys/contrib/ipfilter/netinet/fil.c:3104 #13 0xffffffff80ba08cb in pfil_run_hooks (ph=, mp=, ifp=, dir=, inp=) at /usr/src/sys/net/pfil.c:83 #14 0xffffffff80c0326b in ip_tryforward (m=0xffffffff818d5fe0) at /usr/src/sys/netinet/ip_fastfwd.c:330 #15 0xffffffff80c058b7 in ip_input (m=0x0) at /usr/src/sys/netinet/ip_input.c:558 #16 0xffffffff80b9f7b0 in netisr_dispatch_src (proto=1, source=0, m=0xfffff801843a0500) at /usr/src/sys/net/netisr.c:1120 #17 0xffffffff80cecc07 in dummynet_send (m=) at /usr/src/sys/netpfil/ipfw/ip_dn_io.c:791 #18 0xffffffff80cec530 in dummynet_task (context=, pending=) at /usr/src/sys/netpfil/ipfw/ip_dn_io.c:746 #19 0xffffffff80aeb5bc in taskqueue_run_locked (queue=) at /usr/src/sys/kern/subr_taskqueue.c:449 #20 0xffffffff80aec138 in taskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_taskqueue.c:708 #21 0xffffffff80a5bd74 in fork_exit (callout=0xffffffff80aec0b0 , arg=0xffffffff81e0c278, frame=0xfffffe023ab3ec00) at /usr/src/sys/kern/kern_fork.c:1038 ---Type to continue, or q to quit---q Quit (kgdb) #3 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: panic: Duplicate free of 0xfffff8014152f800 from zone 0xfffff8021ffcc000(1024) slab 0xfffff8012cff34d0(2) cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe022fcd9f90 vpanic() at vpanic+0x182/frame 0xfffffe022fcda010 panic() at panic+0x43/frame 0xfffffe022fcda070 uma_dbg_free() at uma_dbg_free+0xee/frame 0xfffffe022fcda0a0 uma_zfree_arg() at uma_zfree_arg+0x64/frame 0xfffffe022fcda0f0 free() at free+0xab/frame 0xfffffe022fcda130 ipf_p_ftp_pasvreply() at ipf_p_ftp_pasvreply+0x39f/frame 0xfffffe022fcda2e0 ipf_p_ftp_pasv() at ipf_p_ftp_pasv+0x568/frame 0xfffffe022fcda400 ipf_p_ftp_server() at ipf_p_ftp_server+0x227/frame 0xfffffe022fcda450 ipf_p_ftp_process() at ipf_p_ftp_process+0x98f/frame 0xfffffe022fcda540 ipf_proxy_check() at ipf_proxy_check+0x127/frame 0xfffffe022fcda5b0 ipf_nat_in() at ipf_nat_in+0x6b/frame 0xfffffe022fcda5f0 ipf_nat_checkin() at ipf_nat_checkin+0x1b7/frame 0xfffffe022fcda690 ipf_check() at ipf_check+0x2f5/frame 0xfffffe022fcda800 pfil_run_hooks() at pfil_run_hooks+0x8b/frame 0xfffffe022fcda890 ip_input() at ip_input+0x3bf/frame 0xfffffe022fcda8f0 netisr_dispatch_src() at netisr_dispatch_src+0x80/frame 0xfffffe022fcda950 ether_demux() at ether_demux+0x14a/frame 0xfffffe022fcda980 ether_nh_input() at ether_nh_input+0x347/frame 0xfffffe022fcda9c0 netisr_dispatch_src() at netisr_dispatch_src+0x80/frame 0xfffffe022fcdaa20 ether_input() at ether_input+0x62/frame 0xfffffe022fcdaa50 if_input() at if_input+0xa/frame 0xfffffe022fcdaa60 em_rxeof() at em_rxeof+0x28c/frame 0xfffffe022fcdaae0 em_handle_que() at em_handle_que+0x40/frame 0xfffffe022fcdab20 taskqueue_run_locked() at taskqueue_run_locked+0x13c/frame 0xfffffe022fcdab80 taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe022fcdabb0 fork_exit() at fork_exit+0x84/frame 0xfffffe022fcdabf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe022fcdabf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- Uptime: 1d2h56m47s Dumping 1365 out of 8158 MB:..2%..11%..22%..31%..42%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from /usr/lib/debug//boot/kernel/fdescfs.ko.debug...done. done. Loaded symbols for /boot/kernel/fdescfs.ko Reading symbols from /boot/kernel/iscsi.ko...Reading symbols from /usr/lib/debug//boot/kernel/iscsi.ko.debug...done. done. Loaded symbols for /boot/kernel/iscsi.ko #0 doadump (textdump=1) at pcpu.h:221 221 __asm("movq %%gs:%1,%0" : "=r" (td) (kgdb) up 1 #1 0xffffffff80a97b75 in kern_reboot (howto=) at /usr/src/sys/kern/kern_shutdown.c:366 366 doadump(TRUE); Current language: auto; currently minimal (kgdb) up 1 #2 0xffffffff80a9814b in vpanic (fmt=, ap=) at /usr/src/sys/kern/kern_shutdown.c:759 759 kern_reboot(bootopt); (kgdb) up 1 #3 0xffffffff80a98193 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:690 690 vpanic(fmt, ap); (kgdb) up 1 #4 0xffffffff80da0f7e in uma_dbg_free (zone=0xfffff8021ffcc000, slab=0xfffff8012cff34d0, item=0xfffff8014152f800) at /usr/src/sys/vm/uma_core.c:3612 3612 panic("Invalid free of %p from zone %p(%s) slab %p(%d)\n", (kgdb) list *0xffffffff80da0f7e 0xffffffff80da0f7e is in uma_dbg_free (/usr/src/sys/vm/uma_core.c:3606). 3601 return; 3602 if (slab == NULL) { 3603 slab = uma_dbg_getslab(zone, item); 3604 if (slab == NULL) 3605 panic("uma: Freed item %p did not belong to zone %s\n", 3606 item, zone->uz_name); 3607 } 3608 keg = slab->us_keg; 3609 freei = ((uintptr_t)item - (uintptr_t)slab->us_data) / keg->uk_rsize; 3610 (kgdb) --- Kernel config default plus: include GENERIC ident cobaltus-amd64 options KDB_UNATTENDED options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPFIREWALL_DEFAULT_TO_ACCEPT options DUMMYNET options IPFILTER options IPDIVERT options NO_SWAPPING --- SB From owner-freebsd-current@freebsd.org Wed Oct 5 11:19:29 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A100EAF5043 for ; Wed, 5 Oct 2016 11:19:29 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id F23EF35C for ; Wed, 5 Oct 2016 11:19:28 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 67067 invoked by uid 89); 5 Oct 2016 11:19:26 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.205.219) by mail.grem.de with ESMTPA; 5 Oct 2016 11:19:26 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [request for testing] isl, cyapa on chromebooks From: Michael Gmelin X-Mailer: iPhone Mail (13G36) In-Reply-To: <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> Date: Wed, 5 Oct 2016 13:19:25 +0200 Cc: Michael Gmelin , FreeBSD Current , freebsd-mobile@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> To: Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 11:19:29 -0000 > On 05 Oct 2016, at 07:48, Andriy Gapon wrote: >=20 >> On 05/10/2016 01:48, Michael Gmelin wrote: >> Double-checked the hints, it's all ok. >>=20 >> Please find a more verbose log file of loading the kernel modules here: >>=20 >> https://people.freebsd.org/~grembo/c720-20161105.log >=20 > Unfortunately this doesn't provide any new insights. >=20 > Could you please add some printf-s to iicbus_hinted_child() in > sys/dev/iicbus/iicbus.c to see whether the isl devices are really added vi= a the > hints and what their properties are? > Also, some printf-s to isl_probe() to see if it gets called and where it f= ails. > And, just in case, to ig4iic_start() to see if gets called. >=20 ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and= iicbus_attach are not. -m= From owner-freebsd-current@freebsd.org Wed Oct 5 11:45:01 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AC5DAF5895 for ; Wed, 5 Oct 2016 11:45:01 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 0FE59E3 for ; Wed, 5 Oct 2016 11:45:00 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1brkd2-000jYK-Bl>; Wed, 05 Oct 2016 13:44:52 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1brkd2-0030yx-4k>; Wed, 05 Oct 2016 13:44:52 +0200 Date: Wed, 5 Oct 2016 13:44:46 +0200 From: "O. Hartmann" To: freebsd-current Subject: jails in CURRENT: can not reach hosts on same network Message-ID: <20161005134446.7af8126c@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 11:45:01 -0000 Hello list. I struggle with setting up jails on most recent CURRENT. The machine containing the jails has two NICs (bce0 and bce1). the host itself is supposed to own NIC bce0 exclusively - means, the services running on that NIC - syslogd, named and others - are bound to that NIC and should not be shared with the bce1 or jails bound to bce1. I followed the instructions given in the most recent version of the handbook setting up a jail. So far, so good. The NIC bce1 (the second one) is "aliased" with IPs from the local network. forwarding is disabled (net.inet.ip.forwarding: 0). Setup of each jail is straigh forward, with "ip4.addr=" set to the specific IP and interface="bce1". Within a jail, I can not reach an IP on the same network, not even the gateway by pinging or doing name resolutions using the DNS server on the local net! The curious thing is, by setting "nameserver 8.8.8.8" in /etc/resolv.conf, I can ping "outer world systems" and performing name resolutions as well - this implies, that the IP pakets are delegated to the local gateway and then further to the DNS of Google's. But pinging the local gateway directly (192.168.0.1) seems to be prohibited as well as pinging or reching any other IP on the net, including the bce0 of the same host (via default gateway?) or any other aliased IP. Since I'm new to jails and the complicated handling with networks, I miss something here which is probably not well documented. I found some notes on the forum about setfib, FIB, but I lack in the correct manpage to read more about this concept, the meaning for a jail and its probable impact in my situation. Following the suggestion setting net.add_addr_allfibs=0 in /boot/loader.conf seems to be senseless - after a reboot this OID is always set back to 1 (net.add_addr_allfibs=1). maybe someone has an idea what's wrong in principle with my attempts. thanks in advance for your patience, Oliver From owner-freebsd-current@freebsd.org Wed Oct 5 11:55:39 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B19BAF5C88 for ; Wed, 5 Oct 2016 11:55:39 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 72D827E2 for ; Wed, 5 Oct 2016 11:55:37 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 67412 invoked by uid 89); 5 Oct 2016 11:48:55 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.205.219) by mail.grem.de with ESMTPA; 5 Oct 2016 11:48:55 -0000 Mime-Version: 1.0 (1.0) Subject: Re: [request for testing] isl, cyapa on chromebooks From: Michael Gmelin X-Mailer: iPhone Mail (13G36) In-Reply-To: Date: Wed, 5 Oct 2016 13:48:54 +0200 Cc: Andriy Gapon , freebsd-mobile@freebsd.org, FreeBSD Current Message-Id: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> To: Malcolm Matalka Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 11:55:39 -0000 > On 05 Oct 2016, at 13:32, Malcolm Matalka wrote: >=20 > Den 5 okt. 2016 13:19 skrev "Michael Gmelin" : > > > > > > > > > On 05 Oct 2016, at 07:48, Andriy Gapon wrote: > > > > > >> On 05/10/2016 01:48, Michael Gmelin wrote: > > >> Double-checked the hints, it's all ok. > > >> > > >> Please find a more verbose log file of loading the kernel modules her= e: > > >> > > >> https://people.freebsd.org/~grembo/c720-20161105.log > > > > > > Unfortunately this doesn't provide any new insights. > > > > > > Could you please add some printf-s to iicbus_hinted_child() in > > > sys/dev/iicbus/iicbus.c to see whether the isl devices are really adde= d via the > > > hints and what their properties are? > > > Also, some printf-s to isl_probe() to see if it gets called and where i= t fails. > > > And, just in case, to ig4iic_start() to see if gets called. > > > > > > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe= and iicbus_attach are not. > > > > -m > > _______________________________________________ > > freebsd-mobile@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-mobile > > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org= " >=20 > I'm running a laptop that uses an Elantech touch pad over i2c. I think I g= et Elantech is quite close to cyapa, would this patch be a good place to sta= rt for trying to get the touchpad to work? There is also an Elantech patch h= appening for the next release but that is not over i2c. I'm interested in m= aking the change I just have little idea of this layer of the machinery. >=20 I'm having such a machine here myself (one with cyapa, one with elan for tes= ting) and planning to work on it soon (once avg@ is done with this changes).= I also know another user in person waiting for this, so there is definitely= demand and enough hands for testing. -m From owner-freebsd-current@freebsd.org Wed Oct 5 11:32:51 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 321C5AF552D; Wed, 5 Oct 2016 11:32:51 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 C7E28C95; Wed, 5 Oct 2016 11:32:50 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id b184so24111324wma.3; Wed, 05 Oct 2016 04:32:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XZe5UWUJ001VpjKGxkAddX8F1wbLJfqKnQwLnWBvfB0=; b=IRIjmjlUvdcOEIzXWqpfPZUg6EqUJBsWiNn4Z8D3mz3jVYp3Dfm2fPuR/aGwuJFJxM ROBN+2T1PQ/NdRwyAS4lSeQ46P0fOR/HpYXrX4ukPgSe+TTUEpFdkv3iOTJSKPlEXvyp EiYKioLWfuAMUONcSKMgprdlmzaOdythSjyzLkbxqCIdLLHE4fVaDJdnNjfwk6gfkuxc EQI9kjX4VoXB5sDIO3obXgsqMp8nwofqdZag2gfgIIqGLJNP/jLd1iBNOfpLIvcwFXpv k0+P5j92+s/2PvgI0g6rfsDFfSvbPHb0bZAzyM03pSYPxJksl1JLJvI+cmmifbi7z+Tv FgpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XZe5UWUJ001VpjKGxkAddX8F1wbLJfqKnQwLnWBvfB0=; b=bJKE9UzAhwJFIv1qyAWF7uu/K6SAffON4ME9MVe6RVpSVN+/ja5YhaEw+kvRK2RMs5 BtaYzC71Aecq9BId6gb0vifDE5MjA7pfHGdJJCQlDnLk9JeymUquhwVNCxmEf4g55CaK fPJi0R+MY+riy3hMfnLpDxi6p99peEtemX4xLME15+Xi7yiUtdsaQUroNgIYBq0e4jP+ 5e+N+5mRY5v+gAoApatHCDKglgBhEyRYBtUFc1+ySMhPjL1hYnrxr3nMxWbdU1R46Q41 k7Tsmkau0kuxru/J2nbAuD1PO3SIlVHzTx1IiTKj62/43+KWWetp3BsndclnKpwiZdZQ xTBA== X-Gm-Message-State: AA6/9Rmew0jeAwg34J6+qrgcyygVR9hgMaJRga3rIb2PiReg1DUr209C1p/WS0pwpmkEIBsEBel2sBV/ZapHDQ== X-Received: by 10.28.41.6 with SMTP id p6mr19877484wmp.18.1475667168207; Wed, 05 Oct 2016 04:32:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.179.229 with HTTP; Wed, 5 Oct 2016 04:32:47 -0700 (PDT) Received: by 10.194.179.229 with HTTP; Wed, 5 Oct 2016 04:32:47 -0700 (PDT) In-Reply-To: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> From: Malcolm Matalka Date: Wed, 5 Oct 2016 13:32:47 +0200 Message-ID: Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin Cc: Andriy Gapon , freebsd-mobile@freebsd.org, FreeBSD Current X-Mailman-Approved-At: Wed, 05 Oct 2016 12:31:00 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 11:32:51 -0000 Den 5 okt. 2016 13:19 skrev "Michael Gmelin" : > > > > > On 05 Oct 2016, at 07:48, Andriy Gapon wrote: > > > >> On 05/10/2016 01:48, Michael Gmelin wrote: > >> Double-checked the hints, it's all ok. > >> > >> Please find a more verbose log file of loading the kernel modules here: > >> > >> https://people.freebsd.org/~grembo/c720-20161105.log > > > > Unfortunately this doesn't provide any new insights. > > > > Could you please add some printf-s to iicbus_hinted_child() in > > sys/dev/iicbus/iicbus.c to see whether the isl devices are really added via the > > hints and what their properties are? > > Also, some printf-s to isl_probe() to see if it gets called and where it fails. > > And, just in case, to ig4iic_start() to see if gets called. > > > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and iicbus_attach are not. > > -m > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" I'm running a laptop that uses an Elantech touch pad over i2c. I think I get Elantech is quite close to cyapa, would this patch be a good place to start for trying to get the touchpad to work? There is also an Elantech patch happening for the next release but that is not over i2c. I'm interested in making the change I just have little idea of this layer of the machinery. Thanks, /Malcolm From owner-freebsd-current@freebsd.org Wed Oct 5 12:32:44 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABD0FAF32C0; Wed, 5 Oct 2016 12:32:44 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 28F263C8; Wed, 5 Oct 2016 12:32:44 +0000 (UTC) (envelope-from mmatalka@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id x79so15359266lff.0; Wed, 05 Oct 2016 05:32:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pON/UvhR/c2BqSIPIJZye1Jps80CHpFuX9lDADHz/uc=; b=kZXAF14GHELmirtHSGTW2yTeAavgG2oByzVP5EFnmIimXVEiNNKBcnoQQeu1M+6ape tHJ2LngWmaOHw6wyOv06aLekxeGF199U82dGWu6DfC90Z94Q2z4t2ZXronvdQ2rfnaPg c5mysa8GJSM7HztEjjLTEhS5Av8wbc+SZlFVKJ3EzSdPxX6U1W19vEvKa3ZPkIh+ad+7 sd6YIF3H0iVKDD0A2fHmJDVOgxLgXf+uBug1uE+ehRoBgjsyFhjYAO6TANCAH2GU9Myx sF+roe1o7AcOemg0Dmj5ln9LAjOTKvReVg16avsJcb9MV/Vh+5PyQjKRUlya+5CwTp7t h05A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pON/UvhR/c2BqSIPIJZye1Jps80CHpFuX9lDADHz/uc=; b=ANOWwAlRKVzWPEiqK9Sc3VyXZukkC+yZgZodsiM82CCUIUPug/vn+UdaWcga28TIyo 5zN2PD+o+rJhu8ogB2DmIXYUrW7q80Emaq0rBGGloUs+Q+iY7JJeWDQPVnpS+ru2HjJB p4JEqEWwWCoyAtTgLqSEAmtsLRfO5Xjp/YMuqkzdzYK6xWS5XQtX01Iy9fwYeeFFKa1j Y+Gn8KoaVi9RqO6r/Y9P78ZySgVu5UQ6t04d7kIjX6ZEqOCo8jK2SGsjXo2ZqC2U58v9 GC5UlehUrMEihq8jbbrPdCt3An3BoidaQM5c9bbWajS0CWzeso2K2TMtd3Bhnuj3b9JE 1ttg== X-Gm-Message-State: AA6/9RmHnSbFinCuZdavoKB377h+dWNUohtwslwqCPDAMaFVEzjrPTXxjvfIpZwDwJsUc9JRU/DGBIRIRLkR2w== X-Received: by 10.194.122.137 with SMTP id ls9mr7326432wjb.29.1475670762136; Wed, 05 Oct 2016 05:32:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.179.229 with HTTP; Wed, 5 Oct 2016 05:32:40 -0700 (PDT) Received: by 10.194.179.229 with HTTP; Wed, 5 Oct 2016 05:32:40 -0700 (PDT) In-Reply-To: References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> From: Malcolm Matalka Date: Wed, 5 Oct 2016 14:32:40 +0200 Message-ID: Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin Cc: Andriy Gapon , freebsd-mobile@freebsd.org, FreeBSD Current X-Mailman-Approved-At: Wed, 05 Oct 2016 12:53:26 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 12:32:44 -0000 Nice! I'd love to follow along in development and learn whatever can. I've never worked at device driver level before. Do you have a suggested time I can start harassing you more about testing? Den 5 okt. 2016 13:48 skrev "Michael Gmelin" : > > > On 05 Oct 2016, at 13:32, Malcolm Matalka wrote: > > Den 5 okt. 2016 13:19 skrev "Michael Gmelin" : > > > > > > > > > On 05 Oct 2016, at 07:48, Andriy Gapon > wrote: > > > > > >> On 05/10/2016 01:48, Michael Gmelin wrote: > > >> Double-checked the hints, it's all ok. > > >> > > >> Please find a more verbose log file of loading the kernel modules > here: > > >> > > >> https://people.freebsd.org/~grembo/c720-20161105.log > > > > > > Unfortunately this doesn't provide any new insights. > > > > > > Could you please add some printf-s to iicbus_hinted_child() in > > > sys/dev/iicbus/iicbus.c to see whether the isl devices are really > added via the > > > hints and what their properties are? > > > Also, some printf-s to isl_probe() to see if it gets called and where > it fails. > > > And, just in case, to ig4iic_start() to see if gets called. > > > > > > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe > and iicbus_attach are not. > > > > -m > > _______________________________________________ > > freebsd-mobile@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-mobile > > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org > " > > I'm running a laptop that uses an Elantech touch pad over i2c. I think I > get Elantech is quite close to cyapa, would this patch be a good place to > start for trying to get the touchpad to work? There is also an Elantech > patch happening for the next release but that is not over i2c. I'm > interested in making the change I just have little idea of this layer of > the machinery. > > I'm having such a machine here myself (one with cyapa, one with elan for > testing) and planning to work on it soon (once avg@ is done with this > changes). I also know another user in person waiting for this, so there is > definitely demand and enough hands for testing. > > -m > > From owner-freebsd-current@freebsd.org Wed Oct 5 13:02:24 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C762AF3D31; Wed, 5 Oct 2016 13:02:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 47B7FBC8; Wed, 5 Oct 2016 13:02:22 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA03968; Wed, 05 Oct 2016 16:02:21 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brlq1-00089l-3d; Wed, 05 Oct 2016 16:02:21 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> Cc: FreeBSD Current , freebsd-mobile@FreeBSD.org From: Andriy Gapon Message-ID: <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> Date: Wed, 5 Oct 2016 16:01:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 13:02:24 -0000 On 05/10/2016 14:19, Michael Gmelin wrote: > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and > iicbus_attach are not. Thank you! Now I think I see where I made a silly mistake. Please try an updated version of the patch from here https://people.freebsd.org/~avg/ig4-i2c.v3.diff It contains a fix and some cosmetic changes on top of the previous patch. -- Andriy Gapon From owner-freebsd-current@freebsd.org Wed Oct 5 14:03:23 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72204AF61EF; Wed, 5 Oct 2016 14:03:23 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 49E9829A; Wed, 5 Oct 2016 14:03:22 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA04133; Wed, 05 Oct 2016 17:03:20 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1brmn2-0008DK-Ev; Wed, 05 Oct 2016 17:03:20 +0300 To: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-hackers@FreeBSD.org From: Andriy Gapon Subject: iicsmb Message-ID: Date: Wed, 5 Oct 2016 17:02:44 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 14:03:23 -0000 Does anyone use iicsmb driver for any practical purposes? Or more broadly, does anyone have a system with an I2C controller behind which SMBus-compatible slaves are known to exist? -- Andriy Gapon From owner-freebsd-current@freebsd.org Wed Oct 5 14:53:47 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36C68AF644B for ; Wed, 5 Oct 2016 14:53:47 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 CAA6A37C for ; Wed, 5 Oct 2016 14:53:46 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id b201so214268724wmb.0 for ; Wed, 05 Oct 2016 07:53:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UWDjlUlp+reJ0Av7N7bdkx/CpBTY9m0hgTzps45qFW4=; b=BnVJIv/Kvpk/qAZICleTGq7Kj05DXp2VqeMCnMcc73m211v/TAa8dGeyiDAqB73GLW rSKDye/05TKsezH52fPhXicDA9jR9BEdncFLYLtnLoXd51k9aoRlVwNSKJWu5Yp6SB4H UpLaUt9h4VCeTx7I2+4NbGoJ+akP732hq7aMmsGtWFDtQS23WgMzm5UhVykrFezvb8oU WH32PEmrtOgr2DT2VsXSUL334CDoi13kyxaBkDInL/WyqYHOgb/fl2wGEL2kKYORNnVl aMUCEcH/7LjlMj9yK/YE5JWRtHPceyH3HrZT9qYpcdcaavNObRmObdOs8+wY74TsaLkW SZHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=UWDjlUlp+reJ0Av7N7bdkx/CpBTY9m0hgTzps45qFW4=; b=IJzr1XrtVyvWCB2XV79krX1Yr5EWvvtmz39pyqxiSpom9iGfaVCq0qj2rzcuTzVcXN y2xjVwgy8Cd0ymG6atJaLNckAvdZTlFFHRQrkypufL6V979DhBdVzJnVyKjNGRN1dtiE DzUtXGeKDgQzi9M9S4seaHjNOEJAMQKEuFbMb4pcoLv587LtpAet5aWUDQ8ggieV66tL CRiXjpP1AQm8vAhbZlDkQJYH5zvSvyYC099A4cdCNFIO7fM59nMZgsDmBdl+QB6ZkK2N qdYadEn6vFL7/4RAD4UeEdIYUDKE+7ubKas7HFIAVIO++ri56Iz8IzBICBhV9DXFqIBh 88Pg== X-Gm-Message-State: AA6/9RkjeRAdghy1C6SL8TXjrDADjnSGkhtXhFPN3RbiWWU1h6nTGqS2+z2YbxOOdYVHgPAY5gOgGUvKswhnxg== X-Received: by 10.28.34.69 with SMTP id i66mr2774760wmi.96.1475679225029; Wed, 05 Oct 2016 07:53:45 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.194.15.137 with HTTP; Wed, 5 Oct 2016 07:53:44 -0700 (PDT) In-Reply-To: <20161005134446.7af8126c@freyja.zeit4.iv.bundesimmobilien.de> References: <20161005134446.7af8126c@freyja.zeit4.iv.bundesimmobilien.de> From: Alan Somers Date: Wed, 5 Oct 2016 08:53:44 -0600 X-Google-Sender-Auth: Feasoe-TblIGM6NvMv-xwil9cvw Message-ID: Subject: Re: jails in CURRENT: can not reach hosts on same network To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 14:53:47 -0000 On Wed, Oct 5, 2016 at 5:44 AM, O. Hartmann wrote: > Hello list. > > I struggle with setting up jails on most recent CURRENT. > > The machine containing the jails has two NICs (bce0 and bce1). the host itself > is supposed to own NIC bce0 exclusively - means, the services running on that > NIC - syslogd, named and others - are bound to that NIC and should not be > shared with the bce1 or jails bound to bce1. > > I followed the instructions given in the most recent version of the handbook > setting up a jail. So far, so good. The NIC bce1 (the second one) is "aliased" > with IPs from the local network. forwarding is disabled > (net.inet.ip.forwarding: 0). > > Setup of each jail is straigh forward, with "ip4.addr=" set to the specific IP > and interface="bce1". > > Within a jail, I can not reach an IP on the same network, not even the gateway > by pinging or doing name resolutions using the DNS server on the local net! The > curious thing is, by setting "nameserver 8.8.8.8" in /etc/resolv.conf, I can > ping "outer world systems" and performing name resolutions as well - this > implies, that the IP pakets are delegated to the local gateway and then further > to the DNS of Google's. But pinging the local gateway directly (192.168.0.1) > seems to be prohibited as well as pinging or reching any other IP on the net, > including the bce0 of the same host (via default gateway?) or any other aliased > IP. > > Since I'm new to jails and the complicated handling with networks, I miss > something here which is probably not well documented. I found some notes on the > forum about setfib, FIB, but I lack in the correct manpage to read more about > this concept, the meaning for a jail and its probable impact in my situation. > > Following the suggestion setting > > net.add_addr_allfibs=0 > > in /boot/loader.conf seems to be senseless - after a reboot this OID is always > set back to 1 (net.add_addr_allfibs=1). > > maybe someone has an idea what's wrong in principle with my attempts. > > thanks in advance for your patience, > > Oliver Firstly, ping doesn't work in a jail, because jailed processes aren't allowed to open raw sockets. To lift that restriction, you can do "sysctl security.jail.allow_raw_sockets". Depending on what your security environment is like, you may or may not want to leave that set permanently. You can also control it on a per-jail basis. If you're using iocage to manage your jails, just do "iocage set allow_raw_sockets=1 ". If that doesn't work, then post the output of "ifconfig". You shouldn't need to screw with fibs unless your jails need to use a different gateway than the host. -Alan From owner-freebsd-current@freebsd.org Wed Oct 5 16:47:26 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4380FAF6062 for ; Wed, 5 Oct 2016 16:47:26 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 09C191BF for ; Wed, 5 Oct 2016 16:47:26 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x232.google.com with SMTP id o19so184104926ito.1 for ; Wed, 05 Oct 2016 09:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=T/OzDiRF8rdN0xkINWARpNUhCQP4HUn9tyeHZcOu6rU=; b=G/4Mq8vsWjEwJ3Nv4oj/P+7REHr6rXDSHqhwhhAvUWMZXZo8mNGSSML8EYrllM5sUV 02Be8K1HrbhvRwA1445xki0oKs232JktOdLDy7rFnQqlVlWPHz9SIPcdjzugkNtwd8Oe rgsj9v5xREWll8BiCwE+7UC2JxqODzJgP7Pu32CZ54AP0+p8uqpgArTEjyk0sXThv2FC sONYK2ETV3NI1GveCjQraplYXfWYqYw8zGZtLjK/5lHCsgadWPY6sDzkVWcu3rlWXQIX j9Xo4AcoXkBemXIQ+jODkD1a+T5kV1W8rNCUvm6faU7CD1JYUBR+HTtVh6E6QbwU4rjB 9A/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=T/OzDiRF8rdN0xkINWARpNUhCQP4HUn9tyeHZcOu6rU=; b=AcIAf0Y75LI7w2fG+PgX2JWB3FxuiHU9BA3N5tM5zWLvj1HccnqkWOygSWtupkLHBd wohqLABWImTz0WFZZmXd6Jhgf0WYkVKnG4WNH/C9Go9N6nHprE/pn8tmihjcIVl06+jd mNqM7p9KVKNHB+jGb230a7RQM2JCeMDNU/eOZs3y6I4nvVBTvKFxihvEVzEq7EWu02G3 2D/PJ5Edhq4HBaJoMiZDrpNW0FeGvVzAddIQOaPVffDfWEzy5AoqmRlUrBkbqW5wjjAl 1O1Y/y0tzXgz3Y6Ghg3CaVKeqPoogXcbtnd+iVugP2cB+Db5CQGOwH+ud7sKqOAfML1D SDyA== X-Gm-Message-State: AA6/9Rl5OPv8PzVqz3M+uqa1G3WI17zOyAMuHSEwSQ1Z6IfGsutp//8LpUZCsPr9KFDRHQ== X-Received: by 10.36.163.197 with SMTP id p188mr11064951ite.107.1475686044984; Wed, 05 Oct 2016 09:47:24 -0700 (PDT) Received: from [10.0.10.3] (cpe-24-165-201-26.neo.res.rr.com. [24.165.201.26]) by smtp.googlemail.com with ESMTPSA id r123sm12958225ith.1.2016.10.05.09.47.22 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 05 Oct 2016 09:47:22 -0700 (PDT) Message-ID: <57F52EA4.4080004@gmail.com> Date: Wed, 05 Oct 2016 12:47:32 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "O. Hartmann" CC: freebsd-current Subject: Re: jails in CURRENT: can not reach hosts on same network References: <20161005134446.7af8126c@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20161005134446.7af8126c@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 16:47:26 -0000 O. Hartmann wrote: > Hello list. > > I struggle with setting up jails on most recent CURRENT. > > The machine containing the jails has two NICs (bce0 and bce1). the host itself > is supposed to own NIC bce0 exclusively - means, the services running on that > NIC - syslogd, named and others - are bound to that NIC and should not be > shared with the bce1 or jails bound to bce1. > > I followed the instructions given in the most recent version of the handbook > setting up a jail. So far, so good. The NIC bce1 (the second one) is "aliased" > with IPs from the local network. forwarding is disabled > (net.inet.ip.forwarding: 0). > > Setup of each jail is straigh forward, with "ip4.addr=" set to the specific IP > and interface="bce1". > > Within a jail, I can not reach an IP on the same network, not even the gateway > by pinging or doing name resolutions using the DNS server on the local net! The > curious thing is, by setting "nameserver 8.8.8.8" in /etc/resolv.conf, I can > ping "outer world systems" and performing name resolutions as well - this > implies, that the IP pakets are delegated to the local gateway and then further > to the DNS of Google's. But pinging the local gateway directly (192.168.0.1) > seems to be prohibited as well as pinging or reching any other IP on the net, > including the bce0 of the same host (via default gateway?) or any other aliased > IP. > > Since I'm new to jails and the complicated handling with networks, I miss > something here which is probably not well documented. I found some notes on the > forum about setfib, FIB, but I lack in the correct manpage to read more about > this concept, the meaning for a jail and its probable impact in my situation. > > Following the suggestion setting > > net.add_addr_allfibs=0 > > in /boot/loader.conf seems to be senseless - after a reboot this OID is always > set back to 1 (net.add_addr_allfibs=1). > > maybe someone has an idea what's wrong in principle with my attempts. > > thanks in advance for your patience, > > Oliver First of all trying to teach your self about LAN & jail usage using [CURRENT] is the wrong version of FreeBSD to be using because it's the bleeding edge where all the OS updates are tested. You should be using 10.3 or soon to be published 11.0. With CURRENT you can't tell if problems are caused by you not configuring something correctly or you fell into a OS bug. Now if you have a LAN & jail setup working on a RELEASE version and you really think your problem is caused by a bug in CURRENT then you need to come out and state that. But based on the tone of your post that is not the case. Secondly, the "current" list is the incorrect list to be posting this type of question. You should post this to the "questions" or the "jail" list. The ping command from within a jail is a considered a security risk and disabled by jail(8) design. It seems to me that you are mixing 2 separate problems, LAN configuration and jail configuration. You need to first get your LAN nodes talking to each other and with the host, before you add jail(8) into the mix. The standard LAN configuration runs a DHCP server on the host to assign private IP address to the LAN PC's when they power on. Since your host box functions as a [gateway box] with a LAN behind it you need to have gateway_enable="YES" in your hosts rc.conf file. You also need a firewall to NAT the private LAN IP addresses to the hosts public ISP issued IP address. I recommend ipfilter which is in the base system, it's open source and runs on most all other Unix flavored OS's making it very easy to use the same firewall rule set across other OS's. After you have your LAN nodes being able to ping the host and other nodes on the LAN, and also access the pubic internet, Then is the time to play with jails. I recommend you use the jail utility sysutil/qjail port. It simplifies jail management and is very user friendly. Be sure not to assign private IP addresses to jails that are controlled by DHCP or the LAN node will stop working when the jail starts using the same IP address. A detailed description of how you intend to us jails would go a long way to customizing any additional help you may require from posts to the "questions" list. From owner-freebsd-current@freebsd.org Wed Oct 5 16:47:56 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EB7DAF60D0 for ; Wed, 5 Oct 2016 16:47:56 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 13543308 for ; Wed, 5 Oct 2016 16:47:55 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1brpMH-002dnN-Mz>; Wed, 05 Oct 2016 18:47:53 +0200 Received: from x5ce128df.dyn.telefonica.de ([92.225.40.223] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1brpMH-003SiT-Ej>; Wed, 05 Oct 2016 18:47:53 +0200 Date: Wed, 5 Oct 2016 18:47:48 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: CURRENT: "service netif restart" looses default route Message-ID: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Ki_leajgE=gHBpoLLynVTnb"; protocol="application/pgp-signature" X-Originating-IP: 92.225.40.223 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 16:47:56 -0000 --Sig_/Ki_leajgE=gHBpoLLynVTnb Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Today, I checked on two servers of ours running both a recent CURRENT (i.e.= FreeBSD 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service netif= restart" the upcoming network and realised that the default route is lost then! I'm able to config the route via "service routing restart" - or manually as= I did otherwise. But I recall that I did a simple "service netif restart" in 11-C= URRENT recently and that worked. Has there been a change? What is now the official way to restart network? Kind regards, Oliver --Sig_/Ki_leajgE=gHBpoLLynVTnb Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX9S60AAoJEOgBcD7A/5N8JEQH/1MGY1Ij1zYexOWHs8j4qLuk zU5Vi3q/ZjxdXqvtAVNFfBwLB7Ehaq3QFh8Zbllkq2sBRQDuAI9w5z/NJdYTHYQv 4jxBQlOTmg83TqfJyfAn4ml8g2S6sPT0RX7xltOK0ZKEeZsvxehUC+lzhHaYR300 VQBdLgMFra2uEgNcwxhCr7KC7tHA+uHETiqD+8VnQUfx9DAVm1KxNiqOJkm3JG2R dscRHlK6Z+3SrMSwheCnNh452L8NJzLEtJXrtPj0dX25UcyTWUNaU4kxHH4hoa+j 1B8U5g0lmqex8aSOl7voQpINPps7iDhNCyDWDMdGofoYDKAnDnOv9AZ1MGSpMA8= =jcsL -----END PGP SIGNATURE----- --Sig_/Ki_leajgE=gHBpoLLynVTnb-- From owner-freebsd-current@freebsd.org Wed Oct 5 17:50:34 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F45FAF614C for ; Wed, 5 Oct 2016 17:50:34 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BA5F3D88 for ; Wed, 5 Oct 2016 17:50:33 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id u95HoOnj076609 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Oct 2016 19:50:24 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id u95HoOmk076606; Wed, 5 Oct 2016 19:50:24 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Wed, 5 Oct 2016 19:50:24 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: "O. Hartmann" cc: FreeBSD CURRENT Subject: Re: CURRENT: "service netif restart" looses default route In-Reply-To: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> Message-ID: References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 17:50:34 -0000 On Wed, 5 Oct 2016 18:47+0200, O. Hartmann wrote: > > Today, I checked on two servers of ours running both a recent CURRENT (i.e. FreeBSD > 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service netif restart" the > upcoming network and realised that the default route is lost then! > > I'm able to config the route via "service routing restart" - or manually as I did > otherwise. But I recall that I did a simple "service netif restart" in 11-CURRENT > recently and that worked. > > Has there been a change? What is now the official way to restart network? I see something similar on stable/11, r306639. During boot this system can't add its IPv6 default route. I need to add it manually afterwards. Note, this is on XenServer 7.0.0, so maybe the hypervisor play a certain role. Oct 4 13:23:24 [WITHHELD] kernel: add host 127.0.0.1: gateway lo0 fib 0: route already in table Oct 4 13:23:24 [WITHHELD] kernel: add net default: gateway 128.x.y.z Oct 4 13:23:24 [WITHHELD] kernel: Additional inet routing options: gateway=YES. Oct 4 13:23:24 [WITHHELD] kernel: add host ::1: gateway lo0 fib 0: route already in table Oct 4 13:23:24 [WITHHELD] kernel: add net fe80::: gateway ::1 Oct 4 13:23:24 [WITHHELD] kernel: add net ff02::: gateway ::1 Oct 4 13:23:24 [WITHHELD] kernel: add net ::ffff:0.0.0.0: gateway ::1 Oct 4 13:23:24 [WITHHELD] kernel: add net ::0.0.0.0: gateway ::1 Oct 4 13:23:24 [WITHHELD] kernel: route: writing to routing socket: Network is unreachable Oct 4 13:23:24 [WITHHELD] kernel: add net default: gateway 2001:x:y:z::1 fib 0: Network is unreachable Also, why do the startup scripts attempt to add additional routes for 127.0.0.1 and ::1? I see that behaviour on both head and stable/11. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestl, | Trond Endrestl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@freebsd.org Wed Oct 5 17:54:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D983FAF63B4 for ; Wed, 5 Oct 2016 17:54:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 BE1722AE for ; Wed, 5 Oct 2016 17:54:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 834A811C8E for ; Wed, 5 Oct 2016 17:54:01 +0000 (UTC) Subject: Re: CURRENT: "service netif restart" looses default route To: freebsd-current@freebsd.org References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> From: Allan Jude Message-ID: <30598abd-3a76-10cd-e7f9-aa9bb0bad87b@freebsd.org> Date: Wed, 5 Oct 2016 13:54:00 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 17:54:03 -0000 On 2016-10-05 12:47, O. Hartmann wrote: > > Today, I checked on two servers of ours running both a recent CURRENT (i.e. FreeBSD > 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service netif restart" the > upcoming network and realised that the default route is lost then! > > I'm able to config the route via "service routing restart" - or manually as I did > otherwise. But I recall that I did a simple "service netif restart" in 11-CURRENT > recently and that worked. > > Has there been a change? What is now the official way to restart network? > > Kind regards, > Oliver > As far as I am aware, this has always been this way, at least with FreeBSD 6.0 and later. When you delete the interfaces, the route goes away, then you recreate the interfaces but not the routes. -- Allan Jude From owner-freebsd-current@freebsd.org Thu Oct 6 04:47:44 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 813DBBD3325; Thu, 6 Oct 2016 04:47:44 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3CC73BAF; Thu, 6 Oct 2016 04:47:43 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.108.172] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1bs0ak-0003FK-Jg; Thu, 06 Oct 2016 06:47:34 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u964lXUe002455 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 6 Oct 2016 06:47:33 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u964lWQC002454; Thu, 6 Oct 2016 06:47:32 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Thu, 6 Oct 2016 06:47:32 +0200 From: Matthias Apitz To: Andriy Gapon Cc: Michael Gmelin , FreeBSD Current , freebsd-mobile@FreeBSD.org Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Andriy Gapon , Michael Gmelin , FreeBSD Current , freebsd-mobile@FreeBSD.org References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 88.217.108.172 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 04:47:44 -0000 El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon escribió: > On 05/10/2016 14:19, Michael Gmelin wrote: > > > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and > > iicbus_attach are not. > > Thank you! > Now I think I see where I made a silly mistake. > Please try an updated version of the patch from here > https://people.freebsd.org/~avg/ig4-i2c.v3.diff > It contains a fix and some cosmetic changes on top of the previous patch. Hi Andriy, I have an Acer C720 too, since around two years and it works fine, thanks to Michael, with the cyapa chip. I have my C720 in daily heavy usage, actually with r292778. Should I apply the above patch or do I need to update before to a more recent CURRENT? I have a second C720 where I could do such test/update more easy, but this is current not in my hands and has, after a repair at Acer, a Elan touch pad. But I could prepare an USB key with 12-CURRENT, just for test. Btw: What is the reason for this change of ig4/i2c/cyapa driver? Last thing: I propose to remove freebsd-mobile@ from the thread. matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 From owner-freebsd-current@freebsd.org Thu Oct 6 05:39:05 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACC8BBD3007 for ; Thu, 6 Oct 2016 05:39:05 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A4B5AB94; Thu, 6 Oct 2016 05:39:04 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA06467; Thu, 06 Oct 2016 08:39:02 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bs1OY-00099v-Gz; Thu, 06 Oct 2016 08:39:02 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Matthias Apitz , Michael Gmelin , FreeBSD Current References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> From: Andriy Gapon Message-ID: <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> Date: Thu, 6 Oct 2016 08:37:40 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 05:39:05 -0000 On 06/10/2016 07:47, Matthias Apitz wrote: > El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon escribió: > >> On 05/10/2016 14:19, Michael Gmelin wrote: >>> >>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and >>> iicbus_attach are not. >> >> Thank you! >> Now I think I see where I made a silly mistake. >> Please try an updated version of the patch from here >> https://people.freebsd.org/~avg/ig4-i2c.v3.diff >> It contains a fix and some cosmetic changes on top of the previous patch. > > Hi Andriy, > > I have an Acer C720 too, since around two years and it works fine, > thanks to Michael, with the cyapa chip. I have my C720 in daily heavy > usage, actually with r292778. Should I apply the above patch or do I > need to update before to a more recent CURRENT? I think that the patch should apply. But if it doesn't... > I have a second C720 > where I could do such test/update more easy, but this is current not in > my hands and has, after a repair at Acer, a Elan touch pad. > But I could prepare an USB key with 12-CURRENT, just for test. The more testing the better! > Btw: What is the reason for this change of ig4/i2c/cyapa driver? The reason is that the hardware that ig4 handles is really an I2C controller. Moreover, isl and cyapa need to issue I2C commands that can not be mapped to SMBus commands to talk to their hardware. I am not sure why Matt Dillon (who I believe is the original author of the code) chose to use smbus(4) instead of iicbus(4). And to make that work he had to "extend" smbus(4) with smbus_trans() method which does not really map to anything defined by the SMBus specification and which can not be implemented on any of real pure SMBus controllers (like intpm or ichsmb). The closest command that SMBus supports is 'Block write - block read process call', but it's not quite the same. > Last thing: I propose to remove freebsd-mobile@ from the thread. Okay. I just was not sure where I can find FreeBSD Chromebook owners. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Oct 6 07:09:06 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30A5DBD3A1A for ; Thu, 6 Oct 2016 07:09:06 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 83BE8662 for ; Thu, 6 Oct 2016 07:09:04 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 81411 invoked by uid 89); 6 Oct 2016 07:08:58 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.205.219) by mail.grem.de with ESMTPA; 6 Oct 2016 07:08:58 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [request for testing] isl, cyapa on chromebooks From: Michael Gmelin X-Mailer: iPhone Mail (13G36) In-Reply-To: <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> Date: Thu, 6 Oct 2016 09:08:57 +0200 Cc: Michael Gmelin , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <3B8B4A4A-8583-4063-999A-780DD5867E04@freebsd.org> References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> To: Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:09:06 -0000 > On 05 Oct 2016, at 15:01, Andriy Gapon wrote: >=20 >> On 05/10/2016 14:19, Michael Gmelin wrote: >>=20 >> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe a= nd >> iicbus_attach are not. >=20 > Thank you! > Now I think I see where I made a silly mistake. > Please try an updated version of the patch from here > https://people.freebsd.org/~avg/ig4-i2c.v3.diff > It contains a fix and some cosmetic changes on top of the previous patch. >=20 Isl attaches cleanly on iicbus1 now, but it doesn't appear to function (all i= nputs, like dev.isl.ir etc, are stuck at 0). -m From owner-freebsd-current@freebsd.org Thu Oct 6 07:26:31 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0842BD3DC3 for ; Thu, 6 Oct 2016 07:26:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id D5950F8C; Thu, 6 Oct 2016 07:26:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA06636; Thu, 06 Oct 2016 10:26:22 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bs34Q-0009F3-HU; Thu, 06 Oct 2016 10:26:22 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <3B8B4A4A-8583-4063-999A-780DD5867E04@freebsd.org> Cc: FreeBSD Current From: Andriy Gapon Message-ID: <8ed7a632-6839-52b8-6a7a-68c661f67819@FreeBSD.org> Date: Thu, 6 Oct 2016 10:25:46 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3B8B4A4A-8583-4063-999A-780DD5867E04@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:26:31 -0000 On 06/10/2016 10:08, Michael Gmelin wrote: > > >> On 05 Oct 2016, at 15:01, Andriy Gapon wrote: >> >>> On 05/10/2016 14:19, Michael Gmelin wrote: >>> >>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and >>> iicbus_attach are not. >> >> Thank you! >> Now I think I see where I made a silly mistake. >> Please try an updated version of the patch from here >> https://people.freebsd.org/~avg/ig4-i2c.v3.diff >> It contains a fix and some cosmetic changes on top of the previous patch. >> > > Isl attaches cleanly on iicbus1 now, but it doesn't appear to function (all inputs, like dev.isl.ir etc, are stuck at 0). At least some progress... Anything interesting in logs? Oh! and I've just spotted a typo in isl.c: the last call to isl_read_byte() in isl_read_sensor() should have REG_DATA2 (not REG_DATA1 again). Thank you for testing! -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Oct 6 07:33:46 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89719BD3FFB for ; Thu, 6 Oct 2016 07:33:46 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from elsa.gfuzz.de (static.173.164.46.78.clients.your-server.de [78.46.164.173]) (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 4EF8964C for ; Thu, 6 Oct 2016 07:33:45 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from localhost (localhost [127.0.0.1]) by elsa.gfuzz.de (Postfix) with ESMTP id BEAA8100128 for ; Thu, 6 Oct 2016 09:27:55 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at elsa.gfuzz.de Received: from elsa.gfuzz.de ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKWFbWUe1qsF for ; Thu, 6 Oct 2016 09:27:55 +0200 (CEST) Received: from mail.opdns.de (ipbcc2386a.dynamic.kabel-deutschland.de [188.194.56.106]) (Authenticated sender: oliver@gfuzz.de) by elsa.gfuzz.de (Postfix) with ESMTPSA id 20607100072 for ; Thu, 6 Oct 2016 09:27:55 +0200 (CEST) Date: Thu, 6 Oct 2016 09:27:53 +0200 From: Oliver Peter To: FreeBSD CURRENT Subject: Re: CURRENT: "service netif restart" looses default route Message-ID: <20161006072753.GA11735@mail.opdns.de> References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> X-Operating-System: Linux 4.4.16-1-pve x86_64 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:33:46 -0000 On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: > > Today, I checked on two servers of ours running both a recent CURRENT (i.e. FreeBSD > 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service netif restart" the > upcoming network and realised that the default route is lost then! > > I'm able to config the route via "service routing restart" - or manually as I did > otherwise. But I recall that I did a simple "service netif restart" in 11-CURRENT > recently and that worked. > > Has there been a change? What is now the official way to restart network? Since the past couple of years on every new FreeBSD I put this in motd for my linux colleagues and coworkers: Network: To apply changes you have made to the network: # /etc/rc.d/netif restart && /etc/rc.d/routing restart Perhaps we could introduce a wrapper to be used with: # service network restart oliver@local ~ % cat /etc/rc.d/network #!/bin/sh # PROVIDE: network # REQUIRE: netif routing # KEYWORD: nojailvnet . /etc/rc.subr . /etc/network.subr name="network" start_cmd="network_start" stop_cmd="network_stop" network_start() { /etc/rc.d/netif start /etc/rc.d/routing start } network_stop() { /etc/rc.d/netif stop /etc/rc.d/routing stop } load_rc_config $name run_rc_command $* -- Oliver PETER oliver@gfuzz.de 0x456D688F From owner-freebsd-current@freebsd.org Thu Oct 6 07:40:54 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A88B3AF5166 for ; Thu, 6 Oct 2016 07:40:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C72F89B3; Thu, 6 Oct 2016 07:40:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA06654; Thu, 06 Oct 2016 10:40:51 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bs3IR-0009FX-Pn; Thu, 06 Oct 2016 10:40:51 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <1e66fc64-cdff-e94b-4b0c-55cb05e2b5a1@FreeBSD.org> <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <3B8B4A4A-8583-4063-999A-780DD5867E04@freebsd.org> <8ed7a632-6839-52b8-6a7a-68c661f67819@FreeBSD.org> Cc: FreeBSD Current From: Andriy Gapon Message-ID: Date: Thu, 6 Oct 2016 10:39:56 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <8ed7a632-6839-52b8-6a7a-68c661f67819@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:40:54 -0000 On 06/10/2016 10:25, Andriy Gapon wrote: > On 06/10/2016 10:08, Michael Gmelin wrote: >> >> >>> On 05 Oct 2016, at 15:01, Andriy Gapon wrote: >>> >>>> On 05/10/2016 14:19, Michael Gmelin wrote: >>>> >>>> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and >>>> iicbus_attach are not. >>> >>> Thank you! >>> Now I think I see where I made a silly mistake. >>> Please try an updated version of the patch from here >>> https://people.freebsd.org/~avg/ig4-i2c.v3.diff >>> It contains a fix and some cosmetic changes on top of the previous patch. >>> >> >> Isl attaches cleanly on iicbus1 now, but it doesn't appear to function (all inputs, like dev.isl.ir etc, are stuck at 0). > > At least some progress... > Anything interesting in logs? > > Oh! and I've just spotted a typo in isl.c: the last call to isl_read_byte() in > isl_read_sensor() should have REG_DATA2 (not REG_DATA1 again). And another, more severe typo :-( In isl_read_byte we should pass both messages to the bus: return (iicbus_transfer(dev, msgs, 2)); That is, s/1/2/. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Oct 6 07:49:38 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3625AF54A1 for ; Thu, 6 Oct 2016 07:49:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E9E05DFD; Thu, 6 Oct 2016 07:49:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA06677; Thu, 06 Oct 2016 10:49:36 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bs3Qu-0009G1-1s; Thu, 06 Oct 2016 10:49:36 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Matthias Apitz , Michael Gmelin , FreeBSD Current References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> From: Andriy Gapon Message-ID: <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> Date: Thu, 6 Oct 2016 10:48:40 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:49:38 -0000 On 06/10/2016 08:37, Andriy Gapon wrote: > The more testing the better! Based on Michael's results I've uploaded a new version: https://people.freebsd.org/~avg/ig4-i2c.v4.diff -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Oct 6 08:10:59 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DBE1BD3212 for ; Thu, 6 Oct 2016 08:10:59 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id E022ECEF for ; Thu, 6 Oct 2016 08:10:58 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 82177 invoked by uid 89); 6 Oct 2016 08:10:57 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@185.17.205.219) by mail.grem.de with ESMTPA; 6 Oct 2016 08:10:57 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [request for testing] isl, cyapa on chromebooks From: Michael Gmelin X-Mailer: iPhone Mail (13G36) In-Reply-To: <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> Date: Thu, 6 Oct 2016 10:10:56 +0200 Cc: Matthias Apitz , Michael Gmelin , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> To: Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 08:10:59 -0000 > On 06 Oct 2016, at 09:48, Andriy Gapon wrote: >=20 >> On 06/10/2016 08:37, Andriy Gapon wrote: >> The more testing the better! >=20 > Based on Michael's results I've uploaded a new version: > https://people.freebsd.org/~avg/ig4-i2c.v4.diff >=20 >=20 Good news. Applying the last two fixes manually, isl is working now. I'll rebuild a kernel using the complete v4 patch on my second machine later= today to test the modified cyapa driver. -m From owner-freebsd-current@freebsd.org Thu Oct 6 08:13:06 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FFA4BD33FA for ; Thu, 6 Oct 2016 08:13:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2F9C61CE; Thu, 6 Oct 2016 08:13:04 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA06724; Thu, 06 Oct 2016 11:13:03 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bs3na-0009HO-Ut; Thu, 06 Oct 2016 11:13:02 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Michael Gmelin References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> Cc: Matthias Apitz , FreeBSD Current From: Andriy Gapon Message-ID: Date: Thu, 6 Oct 2016 11:12:27 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 08:13:06 -0000 On 06/10/2016 11:10, Michael Gmelin wrote: > > >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote: >> >>> On 06/10/2016 08:37, Andriy Gapon wrote: >>> The more testing the better! >> >> Based on Michael's results I've uploaded a new version: >> https://people.freebsd.org/~avg/ig4-i2c.v4.diff >> >> > > Good news. Applying the last two fixes manually, isl is working now. Great! > I'll rebuild a kernel using the complete v4 patch on my second machine later today to test the modified cyapa driver. Thank you again! -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu Oct 6 13:58:04 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62E22BE9CFC for ; Thu, 6 Oct 2016 13:58:04 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 47B80F51 for ; Thu, 6 Oct 2016 13:58:03 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 498661928AD for ; Thu, 6 Oct 2016 13:58:01 +0000 (UTC) To: freebsd-current From: Sean Bruno Subject: Large patch/diff refuses to apply Message-ID: Date: Thu, 6 Oct 2016 07:57:57 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="x9owcww2F95XSlhBkaUAt6G5ax7mOf8Sf" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 13:58:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --x9owcww2F95XSlhBkaUAt6G5ax7mOf8Sf Content-Type: multipart/mixed; boundary="L5H2pnhjK8RFn3fgHcReVrb650D2KWBbb" From: Sean Bruno To: freebsd-current Message-ID: Subject: Large patch/diff refuses to apply --L5H2pnhjK8RFn3fgHcReVrb650D2KWBbb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I'm doing a large amount of change to ixgbe(4) in support of IFLIB implementations and running into failures when trying to apply large diffs. This is causing phabricator reviews to be unuseable as well. I've setup two trees to test this. The first tree is used to generate the diff and the second (vanilla) is used to apply the diff. The entire patch fails to apply, so I'm assuming that the size of the diff is failing because of a sanity check or something. https://people.freebsd.org/~sbruno/test.diff % svn stat sys/dev/ixgbe/if_ix.c M sys/dev/ixgbe/if_ix.c % svn diff sys/dev/ixgbe/if_ix.c > ~/test.diff % cd ../vanilla/ % patch -p0 < ~/test.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: sys/dev/ixgbe/if_ix.c |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- sys/dev/ixgbe/if_ix.c (revision 306673) |+++ sys/dev/ixgbe/if_ix.c (working copy) -------------------------- Patching file sys/dev/ixgbe/if_ix.c using Plan A... Hunk #1 failed at 1. 1 out of 1 hunks failed--saving rejects to sys/dev/ixgbe/if_ix.c.rej done % ls -l sys/dev/ixgbe/if_ix.c* -rw-r--r-- 1 sbruno wheel 166692 Oct 6 06:41 sys/dev/ixgbe/if_ix.c -rw-r--r-- 1 sbruno wheel 166692 Oct 6 06:37 sys/dev/ixgbe/if_ix.c.or= ig -rw-r--r-- 1 sbruno wheel 172779 Oct 6 06:41 sys/dev/ixgbe/if_ix.c.re= j % svn stat sys/dev/ixgbe/ ? sys/dev/ixgbe/if_ix.c.orig --L5H2pnhjK8RFn3fgHcReVrb650D2KWBbb-- --x9owcww2F95XSlhBkaUAt6G5ax7mOf8Sf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX9lhmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kCVIH/3+ju586fjpfhy/ODPUWMSK+ rp4LZQr2CP+WhQcCDxLjHCD0R5bb+D+gD0ixHZ7Ux3sQUEjtYiwPFiCo61N9ZimR M/AD1ZfTT0Q/GTW03KjUfOe7K1jmz18g50T/wajIfmwqRXco8QVsJ5gOZUrLFSn0 dfgfBJLXGXoZL7Eixkso0FPnH45LTnmLKIJ3aJ5302Cc70znIQfDYlF1ILB/7vfG ff1hjj27YXla5bIoD9ZrN723XZWOE6tY84QEA54hzuEyHyA56YYvk8GBkJ8Y1sdF xE+4d0UytnxZMqdlSwetDjVdUbJ6HUK9Jj3YmoI4f346vqYu21Dx02hHbxkeiJM= =0zvq -----END PGP SIGNATURE----- --x9owcww2F95XSlhBkaUAt6G5ax7mOf8Sf-- From owner-freebsd-current@freebsd.org Thu Oct 6 13:53:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEEB3BE9BBF for ; Thu, 6 Oct 2016 13:53:03 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 B5524D77; Thu, 6 Oct 2016 13:53:03 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bs96U-003saM-PW>; Thu, 06 Oct 2016 15:52:54 +0200 Received: from [141.89.176.196] (helo=hermann) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bs96U-000qhp-Id>; Thu, 06 Oct 2016 15:52:54 +0200 Date: Thu, 6 Oct 2016 15:52:53 +0200 From: "Hartmann, O." To: Oliver Peter Cc: FreeBSD CURRENT , allanjude@freebsd.org Subject: Re: CURRENT: "service netif restart" looses default route Message-ID: <20161006155253.3e97f90b@hermann> In-Reply-To: <20161006072753.GA11735@mail.opdns.de> References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> <20161006072753.GA11735@mail.opdns.de> Organization: FU Berlin MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 141.89.176.196 X-Mailman-Approved-At: Thu, 06 Oct 2016 14:18:02 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 13:53:04 -0000 On Thu, 6 Oct 2016 09:27:53 +0200 Oliver Peter wrote: > On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: > > > > Today, I checked on two servers of ours running both a recent > > CURRENT (i.e. FreeBSD 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 > > CEST 2016) via "service netif restart" the upcoming network and > > realised that the default route is lost then! > > > > I'm able to config the route via "service routing restart" - or > > manually as I did otherwise. But I recall that I did a simple > > "service netif restart" in 11-CURRENT recently and that worked. > > > > Has there been a change? What is now the official way to restart > > network? > > Since the past couple of years on every new FreeBSD I put this in > motd for my linux colleagues and coworkers: > > Network: > To apply changes you have made to the network: > # /etc/rc.d/netif restart && /etc/rc.d/routing restart > > Perhaps we could introduce a wrapper to be used with: > # service network restart > > oliver@local ~ % cat /etc/rc.d/network > #!/bin/sh > > # PROVIDE: network > # REQUIRE: netif routing > # KEYWORD: nojailvnet > > . /etc/rc.subr > . /etc/network.subr > > name="network" > start_cmd="network_start" > stop_cmd="network_stop" > > network_start() > { > /etc/rc.d/netif start > /etc/rc.d/routing start > } > > network_stop() > { > /etc/rc.d/netif stop > /etc/rc.d/routing stop > } > > load_rc_config $name > run_rc_command $* > > I'm sorry that my sloppyness brought up this discussion. I recall that I tried to hunt down a bug and did lots of "service netif restart". But on a local network with all essential servers on the same net, I never faced a problem with routing. If life gets too easy, people start digging for the reason of a problem too deep when the framework does too much stuff automated ... The knowledge of the fact that I also have to restart routing via a script is sufficient for me - also the fact to know that netif restart doesn't restart routing. Regards, Oliver From owner-freebsd-current@freebsd.org Thu Oct 6 14:23:43 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E135AF67FE for ; Thu, 6 Oct 2016 14:23:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 2143FFB0; Thu, 6 Oct 2016 14:23:43 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1bs9aF-000PXN-H6; Thu, 06 Oct 2016 17:23:39 +0300 Date: Thu, 6 Oct 2016 17:23:39 +0300 From: Slawa Olhovchenkov To: Sean Bruno Cc: freebsd-current Subject: Re: Large patch/diff refuses to apply Message-ID: <20161006142339.GF6177@zxy.spb.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 14:23:43 -0000 On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: > I'm doing a large amount of change to ixgbe(4) in support of IFLIB > implementations and running into failures when trying to apply large > diffs. This is causing phabricator reviews to be unuseable as well. > > I've setup two trees to test this. The first tree is used to generate > the diff and the second (vanilla) is used to apply the diff. The entire > patch fails to apply, so I'm assuming that the size of the diff is > failing because of a sanity check or something. No. This is expanded/collapsed keywords issuse: === -******************************************************************************/ -/*$FreeBSD$*/ === svn diff over repo generate patch w/ collapsed keywords. At working copy all keywords expanded. From owner-freebsd-current@freebsd.org Thu Oct 6 14:41:53 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77C21AF6E95 for ; Thu, 6 Oct 2016 14:41:53 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 59170A42 for ; Thu, 6 Oct 2016 14:41:53 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 857CA1928AD; Thu, 6 Oct 2016 14:41:51 +0000 (UTC) Subject: Re: Large patch/diff refuses to apply To: Slawa Olhovchenkov References: <20161006142339.GF6177@zxy.spb.ru> Cc: freebsd-current From: Sean Bruno Message-ID: Date: Thu, 6 Oct 2016 08:41:48 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20161006142339.GF6177@zxy.spb.ru> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LsuigKH5cVWTL5jLdNNp8dE86Jm1v08Ql" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 14:41:53 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LsuigKH5cVWTL5jLdNNp8dE86Jm1v08Ql Content-Type: multipart/mixed; boundary="5UKSVEgr1AHloTedHX3CKxj5Bj6a3DBK2" From: Sean Bruno To: Slawa Olhovchenkov Cc: freebsd-current Message-ID: Subject: Re: Large patch/diff refuses to apply References: <20161006142339.GF6177@zxy.spb.ru> In-Reply-To: <20161006142339.GF6177@zxy.spb.ru> --5UKSVEgr1AHloTedHX3CKxj5Bj6a3DBK2 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 10/06/16 08:23, Slawa Olhovchenkov wrote: > On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: >=20 >> I'm doing a large amount of change to ixgbe(4) in support of IFLIB >> implementations and running into failures when trying to apply large >> diffs. This is causing phabricator reviews to be unuseable as well. >> >> I've setup two trees to test this. The first tree is used to generate= >> the diff and the second (vanilla) is used to apply the diff. The enti= re >> patch fails to apply, so I'm assuming that the size of the diff is >> failing because of a sanity check or something. >=20 > No. This is expanded/collapsed keywords issuse: >=20 > =3D=3D=3D > -**********************************************************************= ********/ > -/*$FreeBSD$*/ > =3D=3D=3D >=20 > svn diff over repo generate patch w/ collapsed keywords. > At working copy all keywords expanded. >=20 Ah, I see. Thank you. I am regenerating the failed files now. That seems to work (if I leave the keywords alone). sean --5UKSVEgr1AHloTedHX3CKxj5Bj6a3DBK2-- --LsuigKH5cVWTL5jLdNNp8dE86Jm1v08Ql Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX9mKsXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5koC4H/iDGk/efynrYVsY31Z3pWzuD vtbTYss60FrIRqL9capzEkKQwUjiWM7R5kk0EEusNCaMmPwKqXnvprfwHgkQD2DS FwUBe4imMQsraMMrkYO/0KvHZPUnsjKlGD8aRrWB5bdQC4uMbqHf7AtNGkKBppcF i2vRolKIAtIcaE5B79JYR1mAy+bVRtbAa74ZABDn/n8ueFsj7/UFSnqSLATUS7Ad v/1mKd7bQEQeoaN1PjrHx/S9BiELG4Z0WOKD/teTgJ9NeawlIVPyejyYqsmZJYgF zDwDwBaO1VzzNbmsyLWwpDeNy+U5dVP+M09MQCR1fwsXg7QR99Qjn9175BpI3Pk= =9JDP -----END PGP SIGNATURE----- --LsuigKH5cVWTL5jLdNNp8dE86Jm1v08Ql-- From owner-freebsd-current@freebsd.org Thu Oct 6 15:00:40 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DF16BE93FB for ; Thu, 6 Oct 2016 15:00:40 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 B898C8E9; Thu, 6 Oct 2016 15:00:39 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id f193so295578024wmg.0; Thu, 06 Oct 2016 08:00:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=V9KivNYGfgTh0VM1HC9d4/6I24DHHpcz9ZGVnDTglEA=; b=G+xZ4CJJFWsKuzPKP8MKe4zw4WMm5Ts8OSRQmiVe9BN9JstPsCzboFzj57SVChFsQ6 2nbcq80XNr7/8iZ2QZFkqn2ir1+lW8wICts3mjXsUvIa2EyHsgqHtGbB7sCrc7kuutQT bQw4mSfe1spRoT7V8NiAjQ/gn972QEQFqZlw+vezgket1np7xyCTzun6sY5KRKeUa7RK BRCt9LHIQpptNdKRCBOGqgVSTLlbCmXUTBg2GvS0rKacjTzoTUgvB3AjWr1IpnFTD7R+ EtAD74KAzKQW97rOM+ePCnQWGbflTQBcCPCbV+hd9aKo+18FQe19iHKodw8ojyEr7ElR DNcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=V9KivNYGfgTh0VM1HC9d4/6I24DHHpcz9ZGVnDTglEA=; b=euQY/eSZkf/l+HyU7SjnBiO1eAQt6pqvz0Glb5NPUe/XA0Np89z+xJ81zXIR8uHgai YjSInA+FOsBPZ77mHWxJKvlXwj86pBAmOO0CU6VywFch7/Jz8eoDc1DLhZzb2bxbUz9e iEQLH4ZjifU2oRH4dof/9DJx80qD8i1AVXYrmnAO3OQaG41iJcr+nP7iICy03rrxsi1T F6VJfAoUB9v/kc6c34092JhvdE/imjV/wTYit6hlLZlaRU4Ihk9jMGYRJtO6TQVz4Jrq 3fwuik7z9Bj9RdkA+mJsOYUvdooKalJjqsXR7cDICvYWnFhqHwfggxNwaRZAcEaeZ/4z Inyw== X-Gm-Message-State: AA6/9RmK3Pho8Y62zeszIiIVdYvBad8Aclp1rBjgPxKAS3q4fGa8OMYKLjuUFjYIIMEVFCHALYCVgMhyjHKiUA== X-Received: by 10.194.86.201 with SMTP id r9mr12660548wjz.5.1475766038152; Thu, 06 Oct 2016 08:00:38 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.194.15.137 with HTTP; Thu, 6 Oct 2016 08:00:37 -0700 (PDT) In-Reply-To: References: <20161006142339.GF6177@zxy.spb.ru> From: Alan Somers Date: Thu, 6 Oct 2016 09:00:37 -0600 X-Google-Sender-Auth: 3Ra9-UAqxO_8cyXGVc8hnAUi6gY Message-ID: Subject: Re: Large patch/diff refuses to apply To: Sean Bruno Cc: Slawa Olhovchenkov , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 15:00:40 -0000 On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno wrote: > > > On 10/06/16 08:23, Slawa Olhovchenkov wrote: >> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: >> >>> I'm doing a large amount of change to ixgbe(4) in support of IFLIB >>> implementations and running into failures when trying to apply large >>> diffs. This is causing phabricator reviews to be unuseable as well. >>> >>> I've setup two trees to test this. The first tree is used to generate >>> the diff and the second (vanilla) is used to apply the diff. The entire >>> patch fails to apply, so I'm assuming that the size of the diff is >>> failing because of a sanity check or something. >> >> No. This is expanded/collapsed keywords issuse: >> >> === >> -******************************************************************************/ >> -/*$FreeBSD$*/ >> === >> >> svn diff over repo generate patch w/ collapsed keywords. >> At working copy all keywords expanded. >> > > Ah, I see. Thank you. > > I am regenerating the failed files now. That seems to work (if I leave > the keywords alone). > > sean > Also, I think the "svn patch" command (as opposed to plain "patch") can deal with the RCS keywords. From owner-freebsd-current@freebsd.org Thu Oct 6 15:20:01 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1693DBE99B4 for ; Thu, 6 Oct 2016 15:20:01 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 DAB1A305; Thu, 6 Oct 2016 15:20:00 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 64AFA1928AD; Thu, 6 Oct 2016 15:19:54 +0000 (UTC) Subject: Re: Large patch/diff refuses to apply To: Alan Somers References: <20161006142339.GF6177@zxy.spb.ru> Cc: Slawa Olhovchenkov , freebsd-current From: Sean Bruno Message-ID: Date: Thu, 6 Oct 2016 09:19:51 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Cvhdp4BUxX7dHJWuXNC7wOxcakK6NFXTg" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 15:20:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Cvhdp4BUxX7dHJWuXNC7wOxcakK6NFXTg Content-Type: multipart/mixed; boundary="C0v248WlPaqFdC5ksXxpgmTl0iA03DOPl" From: Sean Bruno To: Alan Somers Cc: Slawa Olhovchenkov , freebsd-current Message-ID: Subject: Re: Large patch/diff refuses to apply References: <20161006142339.GF6177@zxy.spb.ru> In-Reply-To: --C0v248WlPaqFdC5ksXxpgmTl0iA03DOPl Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/06/16 09:00, Alan Somers wrote: > On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno wrote: >> >> >> On 10/06/16 08:23, Slawa Olhovchenkov wrote: >>> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: >>> >>>> I'm doing a large amount of change to ixgbe(4) in support of IFLIB >>>> implementations and running into failures when trying to apply large= >>>> diffs. This is causing phabricator reviews to be unuseable as well.= >>>> >>>> I've setup two trees to test this. The first tree is used to genera= te >>>> the diff and the second (vanilla) is used to apply the diff. The en= tire >>>> patch fails to apply, so I'm assuming that the size of the diff is >>>> failing because of a sanity check or something. >>> >>> No. This is expanded/collapsed keywords issuse: >>> >>> =3D=3D=3D >>> -********************************************************************= **********/ >>> -/*$FreeBSD$*/ >>> =3D=3D=3D >>> >>> svn diff over repo generate patch w/ collapsed keywords. >>> At working copy all keywords expanded. >>> >> >> Ah, I see. Thank you. >> >> I am regenerating the failed files now. That seems to work (if I leav= e >> the keywords alone). >> >> sean >> >=20 > Also, I think the "svn patch" command (as opposed to plain "patch") > can deal with the RCS keywords. >=20 The use of "svn cp" also seems to generate a lot of failures as well. I do want to maintain history between certain files when I go to commit. e.g. svn cp fileA new_fileA, but this seems to confuse the crap out of diff/patch no matter what I do. This leads to suffering with phabricator as well. For now, I'm not going to do the "svn cp" part of my commit, but I will try and do this when I am ready to shove my work into current. sean --C0v248WlPaqFdC5ksXxpgmTl0iA03DOPl-- --Cvhdp4BUxX7dHJWuXNC7wOxcakK6NFXTg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX9muXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kr7AH/i+RdOYZUWQoFUqYTpIv8hIg w0fYSonB+VDO5GVVuyljKoV4t1OVSa+G2fnASFHLf9OzNeBK14I8kPYnxlda0jLO gUp+KeEnaUj2+9LcuvqloOcNdLa1OUVbjb0m7K3ubIvPEmLBPloEwHbSv08zsoPP 6PXrsxTVND46/CsOKDEkTz19jOsWyvUbbBBggPstKRkr9AeZckKRFhqAyt1sfd14 suO5ZfAOoML68rO9vlAj5UdhSzPwik6ehW3XJZfrv4tLkEWzS0eAU7yTOngL+Xmn mGNjjAKf5bRhphnLfy3jcLcmNuUMTN39lqAHpN6bn7lh+YzRE18QerS81zvpZ1E= =92o8 -----END PGP SIGNATURE----- --Cvhdp4BUxX7dHJWuXNC7wOxcakK6NFXTg-- From owner-freebsd-current@freebsd.org Thu Oct 6 15:23:12 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FA24BE9C6B for ; Thu, 6 Oct 2016 15:23:12 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 519C5AFA for ; Thu, 6 Oct 2016 15:23:12 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 5B4981928AD for ; Thu, 6 Oct 2016 15:23:11 +0000 (UTC) Subject: Re: Large patch/diff refuses to apply To: freebsd-current@freebsd.org References: <20161006142339.GF6177@zxy.spb.ru> From: Sean Bruno Message-ID: Date: Thu, 6 Oct 2016 09:23:10 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XpslqhaiTrVv4iKSDRvJx9lsjNj7qMkX5" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 15:23:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XpslqhaiTrVv4iKSDRvJx9lsjNj7qMkX5 Content-Type: multipart/mixed; boundary="7NAX0BuCvSPqDvwN6XbLCugbxVLeP0u76" From: Sean Bruno To: freebsd-current@freebsd.org Message-ID: Subject: Re: Large patch/diff refuses to apply References: <20161006142339.GF6177@zxy.spb.ru> In-Reply-To: --7NAX0BuCvSPqDvwN6XbLCugbxVLeP0u76 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 10/06/16 09:19, Sean Bruno wrote: >=20 >=20 > On 10/06/16 09:00, Alan Somers wrote: >> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno wrote:= >>> >>> >>> On 10/06/16 08:23, Slawa Olhovchenkov wrote: >>>> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: >>>> >>>>> I'm doing a large amount of change to ixgbe(4) in support of IFLIB >>>>> implementations and running into failures when trying to apply larg= e >>>>> diffs. This is causing phabricator reviews to be unuseable as well= =2E >>>>> >>>>> I've setup two trees to test this. The first tree is used to gener= ate >>>>> the diff and the second (vanilla) is used to apply the diff. The e= ntire >>>>> patch fails to apply, so I'm assuming that the size of the diff is >>>>> failing because of a sanity check or something. >>>> >>>> No. This is expanded/collapsed keywords issuse: >>>> >>>> =3D=3D=3D >>>> -*******************************************************************= ***********/ >>>> -/*$FreeBSD$*/ >>>> =3D=3D=3D >>>> >>>> svn diff over repo generate patch w/ collapsed keywords. >>>> At working copy all keywords expanded. >>>> >>> >>> Ah, I see. Thank you. >>> >>> I am regenerating the failed files now. That seems to work (if I lea= ve >>> the keywords alone). >>> >>> sean >>> >> >> Also, I think the "svn patch" command (as opposed to plain "patch") >> can deal with the RCS keywords. >> >=20 > The use of "svn cp" also seems to generate a lot of failures as well. >=20 > I do want to maintain history between certain files when I go to commit= =2E > e.g. svn cp fileA new_fileA, but this seems to confuse the crap out of= > diff/patch no matter what I do. This leads to suffering with > phabricator as well. >=20 > For now, I'm not going to do the "svn cp" part of my commit, but I will= > try and do this when I am ready to shove my work into current. >=20 > sean >=20 A good example of what I was trying to do: svn mkdir sys/modules/ix/ix_iflib svn cp sys/modules/ix/Makefile sys/modules/ix/ix/ix_iflib/Makefile That seems to really confuse things. sean --7NAX0BuCvSPqDvwN6XbLCugbxVLeP0u76-- --XpslqhaiTrVv4iKSDRvJx9lsjNj7qMkX5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX9mxeXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kMGkH/31eD8SE/b6oAv2wtJMTtzHp 2Ey8lcrRZyg7P21jw10yfdcVFwURzQqTuyMFJU8VAtb/1BvlIRVi0wG18jqNTbo4 XJhXUe6SbL5Pq+SgIPR/bDGtqXB6eDeYJTsaiLRdVErC5C1QKeVuyi48P6+GNfII TMLBNsZT/MUeBykXt0/AtIQ3gaE1X6fe794bVlkeWqReqgDTcqembAoq1ByhRybo 6DFKOoCqdR1qz+Q+o8hDWD3TOrJmoKJDIx+RGM6X0IzF0bwJaiswCtF8LQzyG3Js Ht9hir173cINmKFcvrqML9MxIV/0SpLKbLff8b/r3zUNLG5FQl/gbuXvk6EeADI= =iLQy -----END PGP SIGNATURE----- --XpslqhaiTrVv4iKSDRvJx9lsjNj7qMkX5-- From owner-freebsd-current@freebsd.org Thu Oct 6 16:40:30 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 126FBAF6663 for ; Thu, 6 Oct 2016 16:40:30 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::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 E8F9CF1A for ; Thu, 6 Oct 2016 16:40:29 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from la-dgt-31327.usa.tribune.com (nat-192-187-90-113.nat.tribpub.com [192.187.90.113]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 038848d7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 6 Oct 2016 09:40:29 -0700 (PDT) Subject: Re: CURRENT: "service netif restart" looses default route To: Oliver Peter , FreeBSD CURRENT References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> <20161006072753.GA11735@mail.opdns.de> From: Pete Wright Message-ID: Date: Thu, 6 Oct 2016 09:40:28 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161006072753.GA11735@mail.opdns.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 16:40:30 -0000 On 10/6/16 12:27 AM, Oliver Peter wrote: > On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: >> >> Today, I checked on two servers of ours running both a recent CURRENT (i.e. FreeBSD >> 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service netif restart" the >> upcoming network and realised that the default route is lost then! >> >> I'm able to config the route via "service routing restart" - or manually as I did >> otherwise. But I recall that I did a simple "service netif restart" in 11-CURRENT >> recently and that worked. >> >> Has there been a change? What is now the official way to restart network? > > Since the past couple of years on every new FreeBSD I put this in motd for my > linux colleagues and coworkers: > > Network: > To apply changes you have made to the network: > # /etc/rc.d/netif restart && /etc/rc.d/routing restart > > Perhaps we could introduce a wrapper to be used with: > # service network restart I think this is a great idea - especially as it would make it easier for dev's and other novice admin's to use freebsd as a development platform. cheers, -pete -- Pete Wright pete@nomadlogic.org nomadlogicLA From owner-freebsd-current@freebsd.org Thu Oct 6 16:59:11 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5059BAF6CBD for ; Thu, 6 Oct 2016 16:59:11 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06D68DB7; Thu, 6 Oct 2016 16:59:10 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [10.192.1.157] (unknown [178.20.50.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id BBF2A3C603; Thu, 6 Oct 2016 18:59:01 +0200 (CEST) Subject: Re: Large patch/diff refuses to apply Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_4E68803B-5D0F-4AD7-9985-47B66CB34A49"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.6.1 From: Dimitry Andric In-Reply-To: Date: Thu, 6 Oct 2016 18:58:54 +0200 Cc: freebsd-current@freebsd.org Message-Id: <5CAEF9E6-A5C2-40DC-ABCC-C146CA2E91A1@FreeBSD.org> References: <20161006142339.GF6177@zxy.spb.ru> To: Sean Bruno X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 16:59:11 -0000 --Apple-Mail=_4E68803B-5D0F-4AD7-9985-47B66CB34A49 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 06 Oct 2016, at 17:23, Sean Bruno wrote: > > On 10/06/16 09:19, Sean Bruno wrote: >> >> On 10/06/16 09:00, Alan Somers wrote: >>> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno wrote: >>>> >>>> On 10/06/16 08:23, Slawa Olhovchenkov wrote: >>>>> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: ... > A good example of what I was trying to do: > svn mkdir sys/modules/ix/ix_iflib > svn cp sys/modules/ix/Makefile sys/modules/ix/ix/ix_iflib/Makefile > > > That seems to really confuse things. Try using: svn diff --show-copies-as-adds -Dimitry --Apple-Mail=_4E68803B-5D0F-4AD7-9985-47B66CB34A49 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAlf2gtMACgkQsF6jCi4glqPxpACeNyMIOEAJYu+WJyr8GnrS4NVB EVYAoPxYFtfAedmxvBoZNpPqUky3NaiB =6NIa -----END PGP SIGNATURE----- --Apple-Mail=_4E68803B-5D0F-4AD7-9985-47B66CB34A49-- From owner-freebsd-current@freebsd.org Thu Oct 6 18:16:28 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 364D7BEC93B for ; Thu, 6 Oct 2016 18:16:28 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 917C3F1D for ; Thu, 6 Oct 2016 18:16:26 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: (qmail 89054 invoked by uid 89); 6 Oct 2016 18:16:24 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.70) by mail.grem.de with ESMTPA; 6 Oct 2016 18:16:24 -0000 Date: Thu, 6 Oct 2016 20:16:23 +0200 From: Michael Gmelin To: Andriy Gapon Cc: Matthias Apitz , FreeBSD Current Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161006201623.10bbc2c3@bsd64.grem.de> In-Reply-To: References: <20161003180750.744dae0a@bsd64.grem.de> <20161003222528.56d46787@bsd64.grem.de> <20161004114635.64857a29@bsd64.grem.de> <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.2) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 18:16:28 -0000 On Thu, 6 Oct 2016 11:12:27 +0300 Andriy Gapon wrote: > On 06/10/2016 11:10, Michael Gmelin wrote: > > > > > >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote: > >> > >>> On 06/10/2016 08:37, Andriy Gapon wrote: > >>> The more testing the better! > >> > >> Based on Michael's results I've uploaded a new version: > >> https://people.freebsd.org/~avg/ig4-i2c.v4.diff > >> > >> > > > > Good news. Applying the last two fixes manually, isl is working > > now. > > Great! > > > I'll rebuild a kernel using the complete v4 patch on my second > > machine later today to test the modified cyapa driver. > > Thank you again! > Just tested, cyapa is working ok as well, cool. Now, if we wanted to make touchpads like the Elantech (and probably other increasingly popular devices work), I assume we'll need HID over I2C support. OpenBSD got that recently (imt(4) and friends). Anybody interested in porting/re-implementing? -m -- Michael Gmelin From owner-freebsd-current@freebsd.org Thu Oct 6 20:18:47 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99A6EBEC600; Thu, 6 Oct 2016 20:18:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8C7EC895; Thu, 6 Oct 2016 20:18:47 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 41EEA182A; Thu, 6 Oct 2016 20:18:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Thu, 6 Oct 2016 20:18:45 +0000 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: 11.0-RELEASE Status Update Message-ID: <20161006201845.GB88088@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 20:18:47 -0000 --PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline As many of you are aware, 11.0-RELEASE needed to be rebuilt to address several issues that were discovered after the release was built. Extra caution is being taken in testing the rebuilt releases, so at present, the final release announcement is planned for Monday, October 10. Thank you for your patience in waiting for 11.0-RELEASE. Glen On behalf of: re@ --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX9rGlAAoJEAMUWKVHj+KTKIsQAJXPR1alq5G351iKazDY6lWq xyeleRfh5ru8YwxOjYUjKSsyz2lw2ETp7oLf5zK/BEPYgmWuwZd3sM9YjiIBX4+p 7YTOzUVkCr/wSr3BrnzWOuwCsoxISmMXJZoH9Sx5mFL9FHDa1FsYipcp5FNMTKGj kjHKIVx+O+bdPnV/XTnsPssH+0qH5MpOBhGhvX9JPCPWSBca6deg+PfnEUTvcNVf Ct9fnFlaNITG6Y5HcoI1d9xI17GHrnrf68Fo+Crm4kb/o7ptLL2w4Q+7voz5EtqA xsvaHetc31xD9fmGPprVESCE6Pw+kuGT/T2Dv6zadRQvSF9ZRd/1PQUExfQfU68a VBLjBva1bMtVqdRIZ/c3ppNRxScMbhk3gPJtKeE8HUl3tEw4SzvUgQpgfhROlXez arpw3CfWeT6jvi4VfCLAti+5RRwx7q8sHlRm2kAbrXZPwp5QTzCYHlV/mNbRe6SK Th8QDOnogWy29VJFo8UeAbHska0Oj2eYGlheEbrpZOGRba9PrMws4ay+p/7bDWf2 pfTlIpdEKIIc1C/ivtVSHVFqFUNiKKI9qYlTv+MatH9rcmbclgVidh6iZkMqSSYO O+9Mt8icy3CP4xNYxcBWH9EElvfxwahpYuVFVqj1VS5XnU9HwwLgFhd0LP56GbQm 6mU7MdLOu1t1FjsdZhCV =3bMb -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI-- From owner-freebsd-current@freebsd.org Thu Oct 6 21:37:35 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4AC7BEC06B for ; Thu, 6 Oct 2016 21:37:35 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 923DE1C58; Thu, 6 Oct 2016 21:37:35 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (97-123-129-224.albq.qwest.net [97.123.129.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 38A651928AD; Thu, 6 Oct 2016 21:37:34 +0000 (UTC) Subject: Re: Large patch/diff refuses to apply To: Dimitry Andric References: <20161006142339.GF6177@zxy.spb.ru> <5CAEF9E6-A5C2-40DC-ABCC-C146CA2E91A1@FreeBSD.org> Cc: freebsd-current@freebsd.org From: Sean Bruno Message-ID: Date: Thu, 6 Oct 2016 15:37:30 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <5CAEF9E6-A5C2-40DC-ABCC-C146CA2E91A1@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ch0l037S8pm9N0lB0oTjKDfPEQaqiQCcM" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 21:37:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Ch0l037S8pm9N0lB0oTjKDfPEQaqiQCcM Content-Type: multipart/mixed; boundary="k72U7Tq0J9CGGRNbWvOKJGiD41tLwgfAO" From: Sean Bruno To: Dimitry Andric Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: Large patch/diff refuses to apply References: <20161006142339.GF6177@zxy.spb.ru> <5CAEF9E6-A5C2-40DC-ABCC-C146CA2E91A1@FreeBSD.org> In-Reply-To: <5CAEF9E6-A5C2-40DC-ABCC-C146CA2E91A1@FreeBSD.org> --k72U7Tq0J9CGGRNbWvOKJGiD41tLwgfAO Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 10/06/16 10:58, Dimitry Andric wrote: > On 06 Oct 2016, at 17:23, Sean Bruno wrote: >> >> On 10/06/16 09:19, Sean Bruno wrote: >>> >>> On 10/06/16 09:00, Alan Somers wrote: >>>> On Thu, Oct 6, 2016 at 8:41 AM, Sean Bruno wrot= e: >>>>> >>>>> On 10/06/16 08:23, Slawa Olhovchenkov wrote: >>>>>> On Thu, Oct 06, 2016 at 07:57:57AM -0600, Sean Bruno wrote: > ... >> A good example of what I was trying to do: >> svn mkdir sys/modules/ix/ix_iflib >> svn cp sys/modules/ix/Makefile sys/modules/ix/ix/ix_iflib/Makefile >> >> >> That seems to really confuse things. >=20 > Try using: svn diff --show-copies-as-adds >=20 > -Dimitry >=20 Most of what I was trying to do was with arcanist. The review generation seemed to be fine, but applying the diff from arcanist seemed to blow up. sean --k72U7Tq0J9CGGRNbWvOKJGiD41tLwgfAO-- --Ch0l037S8pm9N0lB0oTjKDfPEQaqiQCcM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJX9sQaXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kdNAH+weCPqA+yV6mjA7GSFHvSxid EX4D27EIjvw8B5HcxZcWvirqObyY9MJDUsc4zQ5PTRedc6WH4+j31eGMbcQiNmAT YEln2qmI9tJfZN7Ow9u8z1U5bkZderCxxMOiT8n6pykqhZf8VYLllQTN7NXVznHL 5s2eBAJ8/BdVGaryFezrfvd8YSSBWvzhGvxS2X+kjoZehVMNKHBCVK+eFQtVylWf PtqkLkRjiYRUxJJwh+ZpZaBvsaPP0IANEIQpXGSUnhhHsYy46mM7zVefJkrcB6LF A1I12GKyDX3uGv5qw4HLBBOUFgyQwGAHkgBHpTCle7/iVrVTP6XkSQU8E/YeYUU= =gR0q -----END PGP SIGNATURE----- --Ch0l037S8pm9N0lB0oTjKDfPEQaqiQCcM-- From owner-freebsd-current@freebsd.org Thu Oct 6 21:57:54 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A9F4BEC837 for ; Thu, 6 Oct 2016 21:57:54 +0000 (UTC) (envelope-from yaneurabeya@gmail.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 40723B4F for ; Thu, 6 Oct 2016 21:57:54 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-io0-x233.google.com with SMTP id i202so29493993ioi.2 for ; Thu, 06 Oct 2016 14:57:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qBruzH30axVsaTkZrlNhI3G6hU/ICfqr+qJp0/+RtlI=; b=TpnEx+Bdbd7n00uTq4unGJYiYRb/4+ne2OiytGnqZHsfi7+d9pNuVIV/1Fgi1L6BpZ TC5s7sdn+TYloioFd4FZAjxKjkhO/5SLOa68La3GKOY4/GSDwdzVb+8F48OW++WKAjmV v/nUmsXyroeTGkPXImA5SY/HJIo/PG4DJSAm3VnEH5Q2jhCiNEbknJjQJPCo+0SsMQJO Yfrs3lcoRUAeGTf2NOhH1iuz3jn3QeiCb7969EB1lnafCWo592UAiEDW4zKg7q9vzOtx 9Lzyruu4aN3NrYw7HhLjFaDjH41OoEZUTCq6ZzXujn9zpkP/E0oP3Cm6IXwe791oAkMk Selg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qBruzH30axVsaTkZrlNhI3G6hU/ICfqr+qJp0/+RtlI=; b=hLPD8qz2C3YGdKCqNvZdsLyeAe6QITrKtvFM5NLvaShKjGvSSkWMaIelr47HNY8X4w NTyuzfoJbcb/cirXxI9qD5mcpXNAzjPg1QoKkHHAW1JQizItkLW3sxYL3NgthG/OxnEX LHfoGXK63VpucDkwvkDNlTwIPtO8B91i8GYbi3GM8NcbwAhuWTXw6G2mJZhhQl1bNbjp VRBpIAri+m2/gOJCF+WBYzI3zqmVo6zu91703sbAQKVBLxvMhWCxfEApmQs7SQd6rLf2 bag6hWxpG4glDJEx2+bEegt5kaIiQr96i9G7UojL+i41A7TRPEx7/TJS02EtH0kmTAh4 URxw== X-Gm-Message-State: AA6/9Rn/dGDnGNM1fTskGRPUk7P4ZulkOjO5UQiFIgy13Oa1og7MzgPf7EtYQD8UdCpBwg== X-Received: by 10.107.134.142 with SMTP id q14mr16930399ioi.220.1475791073715; Thu, 06 Oct 2016 14:57:53 -0700 (PDT) Received: from [22.66.200.5] ([172.56.12.135]) by smtp.gmail.com with ESMTPSA id m206sm14481209ita.13.2016.10.06.14.57.52 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 06 Oct 2016 14:57:53 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: CURRENT: "service netif restart" looses default route From: Ngie Cooper X-Mailer: iPhone Mail (13G36) In-Reply-To: Date: Thu, 6 Oct 2016 14:57:51 -0700 Cc: Oliver Peter , FreeBSD CURRENT Content-Transfer-Encoding: quoted-printable Message-Id: <786D056E-A8BE-42A7-A609-5152EB1D739F@gmail.com> References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> <20161006072753.GA11735@mail.opdns.de> To: Pete Wright X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 21:57:54 -0000 > On Oct 6, 2016, at 09:40, Pete Wright wrote: >=20 >> On 10/6/16 12:27 AM, Oliver Peter wrote: >>> On Wed, Oct 05, 2016 at 06:47:48PM +0200, O. Hartmann wrote: >>>=20 >>> Today, I checked on two servers of ours running both a recent CURRENT (i= .e. FreeBSD >>> 12.0-CURRENT #43 r306701: Wed Oct 5 06:40:40 CEST 2016) via "service ne= tif restart" the >>> upcoming network and realised that the default route is lost then! >>>=20 >>> I'm able to config the route via "service routing restart" - or manually= as I did >>> otherwise. But I recall that I did a simple "service netif restart" in 1= 1-CURRENT >>> recently and that worked. >>>=20 >>> Has there been a change? What is now the official way to restart network= ? >>=20 >> Since the past couple of years on every new FreeBSD I put this in motd fo= r my >> linux colleagues and coworkers: >>=20 >> Network: >> To apply changes you have made to the network: >> # /etc/rc.d/netif restart && /etc/rc.d/routing restart >>=20 >> Perhaps we could introduce a wrapper to be used with: >> # service network restart >=20 > >=20 > I think this is a great idea - especially as it would make it easier for d= ev's and other novice admin's to use freebsd as a development platform. Special casing would need to be done with DHCP, btw.. Also, what about IPv6 (rtsol/rtsold, etc)? Thanks! -Ngie= From owner-freebsd-current@freebsd.org Fri Oct 7 10:52:03 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 880EFC0260F for ; Fri, 7 Oct 2016 10:52:03 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 03A4BFE9 for ; Fri, 7 Oct 2016 10:52:02 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id u97Apqu1046584 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 7 Oct 2016 12:51:52 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id u97Apqaf046581 for ; Fri, 7 Oct 2016 12:51:52 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Fri, 7 Oct 2016 12:51:52 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD CURRENT Subject: Re: CURRENT: "service netif restart" looses default route In-Reply-To: Message-ID: References: <20161005184748.01aca03e.ohartman@zedat.fu-berlin.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 10:52:03 -0000 On Wed, 5 Oct 2016 19:50+0200, Trond Endrestl wrote: > Oct 4 13:23:24 [WITHHELD] kernel: add net default: gateway 2001:x:y:z::1 fib 0: Network is unreachable This problem was due to a typo, sorry for the noise. > Also, why do the startup scripts attempt to add additional routes for > 127.0.0.1 and ::1? I see that behaviour on both head and stable/11. It might be worth investigating this issue further, since this behaviour is absent on stable/10. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestl, | Trond Endrestl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@freebsd.org Fri Oct 7 15:57:28 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57F7AC048EA; Fri, 7 Oct 2016 15:57:28 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 237257FC; Fri, 7 Oct 2016 15:57:28 +0000 (UTC) (envelope-from jungleboogie0@gmail.com) Received: by mail-io0-x229.google.com with SMTP id i202so51299988ioi.2; Fri, 07 Oct 2016 08:57:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6E7uuXYxD7vF9wH12GuTr50jql1/BcC9GSWFV83CokA=; b=wdiNUuPBs0CurvS2RQ6Fk5rtpOVY4Lnkao8N0rjYgxFEeLAoCNozrBzH+ni2i7Jnl3 VA8S+XaIYNT8PsQ0XUOnWlAuMpsdusmRkGxvH1BDFe6Bdz9IPwfGeeM/sc+4NTV06UEn 4Oa4l6auyCl9EJzhz6sBprdr4KtYzCorls+djJI9rWiYEcVVv+n86S8+eOnlX4HeIqvR I9OFVUPA/eXzhO+xaFVKjhls1tdKAijKOOHBMSn8rayuT+FnJTlu0kwkVY4+KOse+KdN X6i/ycO84l+r/GLutC6llCnljwIJwmJlxaBYTDdcU5lWfvZOnoOBHzREUnjb0gLdT/Ex AGjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6E7uuXYxD7vF9wH12GuTr50jql1/BcC9GSWFV83CokA=; b=YqVAZsrJJsUXUqLtTriHUU2bvvj3ZNR4o/mivFPObXmF0va7WTyKpxkgKle70nvSIS xsyGCyQzUsFzGZYnm3205XFrOw3w/LKHOMRjrZK3xlSl6Htkq21F1UY/Gdx3vSQ6wjkH GKHpf8Wbt1oX7PpMNmYorx0bY2UA96Acp8KbGNZcGuyrPB7yBgAMDVettDH63EOKQQ1L 4WZ12JHY4DopQlH+H5r7R6iIUYuh2U6s/WGT+X6XVM6a7PvO5u5ZHJQa8aJOnsxyT7PI RTqSBY86UhzsrwsMaTOZ1Mr34r7Gz0Uu9tR7Q5xA6VX4uG2nlONhnqdRgih9iidDa4gK HY8Q== X-Gm-Message-State: AA6/9Rng182HPIN2Yuk2WR7cYw63Ei+H0zdZrm9tdN5paOxKvebRzVM40IMV3k+9d4hvmEBEAIEgSznj0Yw+Fg== X-Received: by 10.107.180.208 with SMTP id d199mr20870953iof.36.1475855847397; Fri, 07 Oct 2016 08:57:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.10.78 with HTTP; Fri, 7 Oct 2016 08:57:26 -0700 (PDT) In-Reply-To: <20161006201845.GB88088@FreeBSD.org> References: <20161006201845.GB88088@FreeBSD.org> From: jungle Boogie Date: Fri, 7 Oct 2016 08:57:26 -0700 Message-ID: Subject: Re: 11.0-RELEASE Status Update To: Glen Barber Cc: freebsd-current@freebsd.org, freebsd-stable , FreeBSD Release Engineering Team Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 15:57:28 -0000 On 6 October 2016 at 13:18, Glen Barber wrote: > the final release announcement is planned for Monday, October 10. suggestion: update the schedule https://www.freebsd.org/releases/11.0R/schedule.html -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info From owner-freebsd-current@freebsd.org Fri Oct 7 16:19:40 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FF66C04FE8; Fri, 7 Oct 2016 16:19:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0017B62C; Fri, 7 Oct 2016 16:19:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id C043C169B; Fri, 7 Oct 2016 16:19:38 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 7 Oct 2016 16:19:35 +0000 From: Glen Barber To: jungle Boogie Cc: freebsd-current@freebsd.org, freebsd-stable , FreeBSD Release Engineering Team Subject: Re: 11.0-RELEASE Status Update Message-ID: <20161007161935.GB57756@FreeBSD.org> References: <20161006201845.GB88088@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 16:19:40 -0000 --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote: > On 6 October 2016 at 13:18, Glen Barber wrote: > > the final release announcement is planned for Monday, October 10. >=20 > suggestion: > update the schedule > https://www.freebsd.org/releases/11.0R/schedule.html >=20 I thought I did, but it looks like a local network hiccup caused the commit to fail. Fixing. Thanks. Glen --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX98sSAAoJEAMUWKVHj+KT01UP/RrhS/LB9JTbonWI83AFCcII 33HnEXQ57IZs5AozOACDnAluUavrjXMiCM8ZPdB0y6wXLvAmBV39MR2EcfLKs2Pf QBbEpvs6lK3q/+6F10k5C7/YRtGfi/PANee8+c/+FciETJtA2CcAwezi/SaYiwA/ aXZ4hSCxGwpZuvVVsLmucS6vRwHlD7noXiF52ohVctIKcmZuphkNtcGZPrhsizQJ QF2k35VT3x31Ayx374GQ/CTQ/u64xc5ZNzZ7YmjbQ8QMK7PMdoS0Z+CQeeYFPzfw f6bW7MJsNdTRiAtGm1z0cMkwuJmx3yhbASCsT4u2c1/2Yj5PPTNY2vMLgyjzsqPb At0zTCo7pVnRlyc2Vgxw9Bv7HDel5+SCl07+aFhsbVj3fkyZu3oFYunW68aknXDT k49ZiNRLJGP0W53gsRZGHmbslEnclrVGA3JHDemaVzJsst7u/X3LTLx6Wj50AFNY htIUNCX9jxjNoNLgQJwRThLDS+ae5+Kas6KdGKEpqlHWnOQwsRLKB2jiWaJ+AJBt 99sw3fVXObhjZIZBvAOFhw+g3FGYQBNu5cgx+xewly8AD560PJpI0o4i5gqywBiF t3HB5RcIsks8ZAp/Mk1VdI5rBJsTeqnHrqFr9IbGJ7uUNKw/NFD1za9CpgHTfQXr Vf+eTI0SptXK09DiZteH =P5UX -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY-- From owner-freebsd-current@freebsd.org Fri Oct 7 23:25:31 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF6CFC0504B; Fri, 7 Oct 2016 23:25:31 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (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 5A8B5AE4; Fri, 7 Oct 2016 23:25:30 +0000 (UTC) (envelope-from andriyvos@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id l131so51393379lfl.2; Fri, 07 Oct 2016 16:25:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:cc:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=biH8GlaCyT91KhBxabgNewNh97eVcVHRp0jrZyr/6uo=; b=MVrn03oddWOaOyAOQYTl+VGl2Bc86UnBkzRA3wjbrXdyItdL/UHHQqeu8AIExmBVV0 0GV6dGA3rXGfcmfLn+hNxlOoSK0OGUbOjcGQEnG/wmKvBRsrNX1ojTAau7MGE+AewEtH Q8g+xCVsNz3NLQsrntIoCQojvWgjEbfAKA4nm1urs2hyIfASHYzNYT/h+EPrKsDYoigK L7RwkFzWxKZ26SqAJcOJXBn5Vlg5FXB0YK03EjiaxFQL8dacIGq4u5Ulsd8xFikoSqPa GjfB6s+XwxUdcKSOKxcX/cPF7q6tKbVN79EcoI4qltL5L7tsC/2TgWlKj/Jkh+OIX4nQ hakw== X-Gm-Message-State: AA6/9Rk4zHt8Q4c4W00dJuFZtW2xBY25hg3gRQUpSGWFeggL//ANHGKh9JeeMjFbXCRL2Q== X-Received: by 10.25.209.204 with SMTP id i195mr9593400lfg.20.1475882337918; Fri, 07 Oct 2016 16:18:57 -0700 (PDT) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id p42sm1005784lfg.48.2016.10.07.16.18.56 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 07 Oct 2016 16:18:57 -0700 (PDT) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Kevin Lo" Cc: "freebsd-wireless@freebsd.org" , "freebsd-current@freebsd.org" , "Adrian Chadd" Subject: Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing References: <20160922092442.GA72044@ns.kevlo.org> <20160923015840.GA77979@ns.kevlo.org> <20160923071830.GA79146@ns.kevlo.org> <20161001150924.GA48641@ns.kevlo.org> <20161003005523.GA57437@ns.kevlo.org> Date: Sat, 08 Oct 2016 02:18:54 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <20161003005523.GA57437@ns.kevlo.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Oct 2016 23:25:32 -0000 Mon, 03 Oct 2016 03:55:23 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo : Hi! Can you refresh the tree and retest it (dev.rtwn.0.debug=3D0x829f) ? P.S. If Rx is still broken (status is always 0) try to execute 'ifconfig wlan0 promisc' > On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote: >> >> hi, > > Hi Adrian, > >> can you turn on debugging? Do you see RX frames? > > No Rx frames. The log is pretty much the same one I sent on the list:= > https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/00= 7093.html > >> -a > > Thanks, > Kevin > >> On 1 October 2016 at 08:09, Kevin Lo wrote: >> > Strange, rtwn(4) stops working. I tried to scan for the available = = >> network, >> > but it just returns empty results. >> > >> > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote:= >> >> >> >> Fri, 23 Sep 2016 10:18:30 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0= =B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo = >> : >> >> >> >> Few more questions: >> >> 1) does it work with h/w encryption support? (enabled by default) >> >> (if 'yes' - I will remove 'hardware crypto enabled' warning). >> >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then = = >> transmit >> >> something - if it works then AMRR will print it's current status >> >> periodically) >> >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n)= >> >> (see r92ce_adj_devcaps() in = >> sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c). >> >> >> >> > It works for me, thanks :) >> >> > >> >> > Kevin >> >> > >> >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wro= te: >> >> >> >> >> >> Fri, 23 Sep 2016 04:58:40 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD= =D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo >> >> >> : >> >> >> >> >> >> Thanks for the log file, >> >> >> >> >> >> Tx 'device timeouts' should be fixed in >> >> >> = >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa7= 67034a89f5 >> >> >> (currently I'm reviewing PCI-specific code to see if there are = any >> >> >> additional >> >> >> issues - e.g., there are no Rx events in the log file). >> >> >> >> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk = = >> wrote: >> >> >> >> >> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 =D0=B1=D1=83=D0=BB=D0=BE =D0= =BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Kevin Lo >> >> >> >> : >> >> >> >> >> >> >> >> Hi, >> >> >> >> >> >> >> >> So, the driver was fully tested. Thanks! >> >> >> >> Can you set dev.rtwn.0.debug=3D0x829f for RTL8188CE to see h= ow = >> big >> >> >> >> the problem is? >> >> >> > >> >> >> > Sure. Here you go >> >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt >> >> >> > >> >> >> > Thanks, >> >> >> > Kevin >> >> >> > >> >> >> >> > Hi Andriy, >> >> >> >> > >> >> >> >> > First of all, THANK YOU! You're doing amazing work! >> >> >> >> > Second, I've done some testing on the following devices, >> >> >> downloading >> >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from= >> >> >> >> > ftp.freebsd.org: >> >> >> >> > >> >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS): >> >> >> >> > rtwn0: > 2.00/2.00, >> >> >> addr >> >> >> >> > 3> on usbus0 >> >> >> >> > rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R >> >> >> >> > >> >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU): >> >> >> >> > rtwn0: > addr 4> on >> >> >> >> > usbus0 >> >> >> >> > rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R >> >> >> >> > >> >> >> >> > - D-Link DWA-131 (RTL8192CU): >> >> >> >> > rtwn0: > 2.00/2.00, >> >> >> addr >> >> >> >> > 3> on usbus0 >> >> >> >> > rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R >> >> >> >> > >> >> >> >> > - TP-Link Archer T4U (RTL8812AU): >> >> >> >> > rtwn0: > addr 7> on >> >> >> >> > usbus0 >> >> >> >> > rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R >> >> >> >> > >> >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU): >> >> >> >> > rtwn0: <802.11n WLAN Adapter> on usbus0 >> >> >> >> > rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R >> >> >> >> > >> >> >> >> > - RTL8188CE mini pcie: >> >> >> >> > rtwn0: port 0xd000-0xd0ff mem >> >> >> >> > 0x90800000-0x90803fff irq 17 at device 0.0 on pci1 >> >> >> >> > rtwn0: r92ce_attach: warning: hardware crypto enabled >> >> >> >> > rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R >> >> >> >> > >> >> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't = = >> work: >> >> >> >> > >> >> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used >> >> >> >> > rtwn0: device timeout >> >> >> >> > >> >> >> >> > Kevin >> >> >> >> > >> >> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboin= yk = >> wrote: >> >> >> >> >> >> >> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 =D0=B1=D1=83=D0=BB=D0=BE = =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Andriy = >> Voskoboinyk >> >> >> >> >> : >> >> >> >> >> >> >> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn= >> >> >> (integrated >> >> >> >> >> into src tree, so it can be built with 'make buildkernel'= / = >> 'make >> >> >> >> >> buildworld'). >> >> >> >> >> >> >> >> >> >> This the last stage; once all reported issues will be = >> resolved, >> >> >> I'm >> >> >> >> >> going to merge it into HEAD. >> >> >> >> >> >> >> >> >> >> > Hi everyone, >> >> >> >> >> > >> >> >> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) = >> drivers were >> >> >> >> merged >> >> >> >> >> > into a >> >> >> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device = >> glue); the >> >> >> >> code is >> >> >> >> >> > available on https://github.com/s3erios/rtwn repository= . = >> Among >> >> >> >> >> bugfixes / >> >> >> >> >> > code deduplication, there some new features too: >> >> >> >> >> > >> >> >> >> >> > 1) multi-vap support (one any wireless interface + one = STA >> >> >> >> interface + >> >> >> >> >> > any number of monitor mode interfaces). >> >> >> >> >> > 2) few new sysctls: >> >> >> >> >> > * dev.rtwn.#.crypto - controls how to use hardware = >> crypto >> >> >> >> >> acceleration >> >> >> >> >> > * dev.rtwn.#.ratectl_selected >> >> >> >> >> > * dev.rtwn.#.ratectl - selects current 'rate control'= >> >> >> algorithm >> >> >> >> >> > (currently only 'none' and 'net80211' are supported; = >> RTL8192CE >> >> >> >> needs >> >> >> >> >> > testing >> >> >> >> >> > with the last). >> >> >> >> >> > 3) (incomplete) power management support for RTL8188EU = = >> (requires >> >> >> >> >> > firmware). >> >> >> >> >> > 4) Short Guard Interval support. >> >> >> >> >> > >> >> >> >> >> > It's known to work with RTL8188CUS, RTL8188EU and = >> RTL8821AU; >> >> >> >> however, >> >> >> >> >> > it was never tested with RTL8192CE or RTL8812AU. >> >> >> >> >> > >> >> >> >> >> > How-to-build: >> >> >> >> >> > 1) download / checkout the repository. >> >> >> >> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src' >> >> >> >> >> > 3) build and install rtwn module: >> >> >> >> >> > cd $repository/sys/modules/rtwn && make && make = >> install >> >> >> >> >> > 4) build and install rtwn_usb/rtwn_pci: >> >> >> >> >> > cd ../rtwn_usb && make && make install >> >> >> >> >> > cd ../rtwn_pci && make && make install >> >> >> >> >> > 5) unload previous && load current drivers: >> >> >> >> >> > kldunload if_urtwn if_rtwn >> >> >> >> >> > kldload /boot/modules/if_rtwn.ko >> >> >> /boot/modules/if_rtwn_usb.ko >> >> >> >> >> > /boot/modules/if_rtwn_pci.ko >> >> >> >> >> > 6) Use. >> >> >> >> >> _______________________________________________ >> >> >> >> >> freebsd-wireless@freebsd.org mailing list >> >> >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wirele= ss >> >> >> >> >> To unsubscribe, send any mail to >> >> >> >> >> "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> freebsd-current@freebsd.org mailing list >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> >> >> To unsubscribe, send any mail to >> >> >> "freebsd-current-unsubscribe@freebsd.org" >> >> >> >> >> >> >> >> > _______________________________________________ >> >> > freebsd-wireless@freebsd.org mailing list >> >> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >> > To unsubscribe, send any mail to >> >> > "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to = >> "freebsd-current-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sat Oct 8 10:59:42 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEDCFC05810 for ; Sat, 8 Oct 2016 10:59:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 B194AC40 for ; Sat, 8 Oct 2016 10:59:42 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bspLv-000r0N-8v>; Sat, 08 Oct 2016 12:59:39 +0200 Received: from x5ce12709.dyn.telefonica.de ([92.225.39.9] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bspLu-003yPd-Tm>; Sat, 08 Oct 2016 12:59:39 +0200 Date: Sat, 8 Oct 2016 12:59:33 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: CURRENT/11-STABLE: Realtek NICs crash FreeBSD Message-ID: <20161008125933.0a833469.ohartman@zedat.fu-berlin.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/mBPDcwgQw_FJjOMMqQrQ6J/"; protocol="application/pgp-signature" X-Originating-IP: 92.225.39.9 X-ZEDAT-Hint: A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 10:59:43 -0000 --Sig_/mBPDcwgQw_FJjOMMqQrQ6J/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I will start with a short problem description for the impatient, afterwards I'll describe the situation in more details. Running 11-CURRENT, 11-STABLE and now 12-CURRENT on hosts equipted with Realtek NIC chipsets bring the system down (crash) on a reproduciable manner. Plugging and unplugging the network cable is one method, having a more sophisticated switch with green power management does the same, but in an unpredictable way. Having the hosts attached directly to a "smart" switch, the crashes can be reproduced by plugging and unplugging the cord or having some traffic - then, it seems to me from an observers point of view, the switch does some arbitrary stuff like link up / link down or power saving or something I can't check and the systems are going down anyway. Having a dumb switch as intermediate device, like the Netgeas GS105, a 5 port GBit switch, the connection is stable as long the cabling is untouched. The problems occur also on my private Netgear GS110TPv2 8-port GBit "smart = maneged" switch, also in "unsmart" mode (means: Eco mode off, no sophiticated stuff = enabled, no powersaving/short cabling enabled, no snmp traps and so on, just factory se= ttings) Switching on some Eco mode facilities (powersavings,short cable etc.) bring= s the hosts in question down really rapidly even with cabling untouched. The NICs in question are: 1) Server/Host from dmesg: rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow from pciconf -lvceb re0@pci0:5:0:0: class=3D0x020000 card=3D0x81681849 chip=3D0x816810ec rev=3D= 0x06 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' class =3D network subclass =3D ethernet bar [10] =3D type I/O Port, range 32, base 0xd000, size 256, enabled bar [18] =3D type Prefetchable Memory, range 64, base 0xf2104000, size 4096, enabled bar [20] =3D type Prefetchable Memory, range 64, base 0xf2100000, size 16384, enabled cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] =3D MSI supports 1 message, 64 bit=20 cap 10[70] =3D PCI-Express 2 endpoint MSI 1 max data 128(128) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[b0] =3D MSI-X supports 4 messages, enabled Table in map 0x20[0x0], PBA in map 0x20[0x800] cap 03[d0] =3D VPD ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[140] =3D VC 1 max VC0 ecap 0003[160] =3D Serial 1 01000000684ce000 2) The second system, A Lenovo Laptop E540, has=20 re0: port 0x3000-0x30ff mem 0xf0d04000-0xf0d04fff,0xf0d00000-0xf0d03fff at device 0.0 on pci2 re0: Using 1 MSI-X message re0: ASPM disabled re0: Chip rev. 0x50800000 re0: MAC rev. 0x00100000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Using defaults for TSO: 65518/35/2048 re0: Ethernet address: 28:d2:44:79:87:32 re0: netmap queues/slots: TX 1/256, RX 1/256 and from pciconf: re0@pci0:3:0:0: class=3D0x020000 card=3D0x502817aa chip=3D0x816810ec rev=3D= 0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' class =3D network subclass =3D ethernet cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] =3D MSI supports 1 message, 64 bit=20 cap 10[70] =3D PCI-Express 2 endpoint MSI 1 max data 128(128) RO link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[b0] =3D MSI-X supports 4 messages, enabled Table in map 0x20[0x0], PBA in map 0x20[0x800] cap 03[d0] =3D VPD ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 0 corrected ecap 0002[140] =3D VC 1 max VC0 ecap 0003[160] =3D Serial 1 01000000684ce000 ecap 0018[170] =3D LTR 1 ecap 001e[178] =3D unknown 1 The longer story: As described above, The problem seems to be with realtek chips I have only.= The Host/server box is also equipted with an Intel NIC and the problem doesn't = occur. This specific host also has the same Realtek NIC as the crashing host (it's a cr= appy ASROCK board, sorry). At the campus lab, I realised that on the laptop plugging and unplugging th= e wired LAN brought down the system very quickly - that was with 11-CURRENT a couple of= months ago, that was intermediate with 11-STABLE the case and it is now with 12-CURRENT= the case (recent update, all boxes have FreeBSD 12.0-CURRENT #3 r306839: Sat Oct 8 = 11:16:48 CEST 2016). Since this laptop also has an Intel WiFi i7260 device which had seve= re problems in the past (iwm driver), I did not pay much attention to the wire net problem= - CURRENT always has some issues, so, I tried not to plug and unplug while the system= is running. Now at the lab/office, and at "home" the network infrastructure has changed= , CISCO or HP switches as the backbone infrastructure at the lab (I do not know the of= fice's infrastructure) and Netgear GS110TPv2 smart managed switch seems to cause m= ore trouble as anticipated. With both hosts attached to the GS110TPv2 and some Eco mode av= ailable, the systems go down predictable. Loggin in on the interface of the switch is al= so a deadly mission. Leaving the switch in factory settings untouched, pluggin/unpluggi= ng is also a deadly force to FreeBSD. Or simply waiting some time - while I do not know = what the switch is doing then - the systems crash.=20 At the moment, the systems with Realtek NICs (3) are unusable with this sma= rt switch and, as a result of my observation today after the GS110TPv2 got installed, prob= lems with other switches as well. I do not think its a problem with the switch, but s= ome switches seem to perform actions bringing down FreeBSD on a predictable manner (Eco mode/powersaving) or even unplugging the cabling. I start now changing NICs to separate Intel based ones to get rid of this R= ealtek crap. So the only debugging capable device left will be the laptop and I'd apprec= iate some tipps for giving you some more informations. Right now, I do not have crash= dumps or screenshots - the laptop shows some informations, but the vanish fast. I'll= configure as soon as possible a debugging kernel. Kind regards, oh --Sig_/mBPDcwgQw_FJjOMMqQrQ6J/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX+NGVAAoJEOgBcD7A/5N8YsMIAJN2yUC4FAfxQtuhIfnvn3VR jaXvCpMBcB6VSnoyUq2DAbz0WMOXOtZsn03ykk2yt8wqnjxajacKumLsuOXcOtrX oP8hnnDJahzzmkEugsrZRA1jNFl9Zk/aFuB6DU58n21oaM4Z7fNuaiXdX+j4G3NZ LhBQtOs9XM0XJAZSHBfL2mcdJPnGhTonzvYgsF+L728VQaEJrDcNLfFml2uFNwgz +/hHM+aHNBnacpN/jt/aB6IPWKIazFdpZdoYEjCOtmZV7AOvf0CW99C4sxiwIFgN S+Ds/ig53yeUVo7XrzcKbWu3DgUCN93zETW/2ShnXu1WBbAt3Cty3CuFPZ3xOZ8= =iHBl -----END PGP SIGNATURE----- --Sig_/mBPDcwgQw_FJjOMMqQrQ6J/-- From owner-freebsd-current@freebsd.org Sat Oct 8 18:07:56 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB68FC0682D for ; Sat, 8 Oct 2016 18:07:56 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6ABE4224; Sat, 8 Oct 2016 18:07:55 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.204.135.184] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1bsw2E-0001Gj-Mr; Sat, 08 Oct 2016 20:07:46 +0200 Received: from localhost.my.domain (c720-r292778-amd64 [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id u98I7iW2001976 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 8 Oct 2016 20:07:44 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id u98I7hVP001975; Sat, 8 Oct 2016 20:07:43 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sat, 8 Oct 2016 20:07:42 +0200 From: Matthias Apitz To: Andriy Gapon Cc: Michael Gmelin , FreeBSD Current Subject: Re: [request for testing] isl, cyapa on chromebooks Message-ID: <20161008180742.GA1912@c720-r292778-amd64> Reply-To: Matthias Apitz Mail-Followup-To: Matthias Apitz , Andriy Gapon , Michael Gmelin , FreeBSD Current References: <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT r292778 (amd64) User-Agent: Mutt/1.5.24 (2015-08-30) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.135.184 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 18:07:56 -0000 El día Thursday, October 06, 2016 a las 11:12:27AM +0300, Andriy Gapon escribió: > On 06/10/2016 11:10, Michael Gmelin wrote: > > > > > >> On 06 Oct 2016, at 09:48, Andriy Gapon wrote: > >> > >>> On 06/10/2016 08:37, Andriy Gapon wrote: > >>> The more testing the better! > >> > >> Based on Michael's results I've uploaded a new version: > >> https://people.freebsd.org/~avg/ig4-i2c.v4.diff > >> > >> > > > > Good news. Applying the last two fixes manually, isl is working now. > > Great! > > > I'll rebuild a kernel using the complete v4 patch on my second machine later today to test the modified cyapa driver. I have now produced a memstick with (unpatched) r306769 of October 6. It boots fine in my Acer C720 Chromebook and the moused is working fine with the cyapa(4) driver. I will apply tomorrow the above v4 patch or is there anything newer? And will test/report. matthias -- Matthias Apitz, ✉ guru@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 From owner-freebsd-current@freebsd.org Sat Oct 8 19:18:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 723B8C06D89 for ; Sat, 8 Oct 2016 19:18:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6D6C1638; Sat, 8 Oct 2016 19:18:11 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA14553; Sat, 08 Oct 2016 22:18:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1bsx8F-000D6r-Vo; Sat, 08 Oct 2016 22:18:04 +0300 Subject: Re: [request for testing] isl, cyapa on chromebooks To: Matthias Apitz , Michael Gmelin , FreeBSD Current References: <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> <20161008180742.GA1912@c720-r292778-amd64> From: Andriy Gapon Message-ID: <846bf31f-a757-2be0-a293-8c4ce3d42a2f@FreeBSD.org> Date: Sat, 8 Oct 2016 22:17:07 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161008180742.GA1912@c720-r292778-amd64> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 19:18:13 -0000 On 08/10/2016 21:07, Matthias Apitz wrote: > I have now produced a memstick with (unpatched) r306769 of October 6. It boots > fine in my Acer C720 Chromebook and the moused is working fine with the > cyapa(4) driver. I will apply tomorrow the above v4 patch or is there > anything newer? And will test/report. v4 is the latest. Thanks! -- Andriy Gapon From owner-freebsd-current@freebsd.org Sat Oct 8 21:54:29 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16CF3C0656B for ; Sat, 8 Oct 2016 21:54:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (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 CF7E1EA for ; Sat, 8 Oct 2016 21:54:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x242.google.com with SMTP id p26so4860225ioo.2 for ; Sat, 08 Oct 2016 14:54:28 -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=nUz0LaapasXOICY61pcexY+1BzW+UAOmh1KhMKPyYRE=; b=cov2A4Zt8KwTMKxhA521dK+zOcnT0MX+txiZI+tjrpLR9kwls0CfvmVwziPUuS1HN0 nEVemH2Y9SInWfwLxALOch/mZr6tifnu9srjsalkhiAkwZEiMDHYum5JiAa0tBHG5BlA y//q6P3XVZ68+Z/M0x99RayxhRHke5ERXGVcgXtxx5TEzAxCuD58JYcwMpRXpcnkHQOr IFxCpDjXNL4b/RDKhoGBZPHCtxuKsEZgC0/54sbSBA5ng+tYy/7HB66wvqN/FZvt94+P BsQjdAg1tzSyQtxW/m7yHWKqXdm7PwdH0kIqxKkkMxcXhKk34DQqLwzuLfkrmeRhT6Ny tGdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nUz0LaapasXOICY61pcexY+1BzW+UAOmh1KhMKPyYRE=; b=kxZKbMSnVObI4ZEkRtjBJIpUWLxYXrAgE64C5zVsyuB6JhHYfuzu7jW1oPTP3nTklN fWbkZi6eEBQeG4gIPd7oGPfXYDmum0tTtwbOLbFH7iVps4kQJlWR2iOIeTnsjrfnCUbD ckSA3lv5kc7WUpru8AnpJCIBLEsqnjUPVSAXRzi9UeAIQeaguxvvDHbBecfKPEc+m+56 Y1HGpBEcOEGZnDq6W2DnHC4Ws9tfh0XiqsSzwcifvfXTD+U6yGTJAniAZD1M1hsNO4I8 E3k43ckeOranXb0dr0L5KQf54EroqPw4RPj8eXchX9EPk8PrBA5UA23UQcr3TXd4BZap hkUw== X-Gm-Message-State: AA6/9RlP7VQO2eJlQvaxwLXsc8ZI2CXMqVuaLM0OGplGytyFdcrliiLgFF8pw7zQWfVZSF4n7uIYJSfZt+PMkA== X-Received: by 10.107.202.4 with SMTP id a4mr26525777iog.19.1475963667965; Sat, 08 Oct 2016 14:54:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.77.85 with HTTP; Sat, 8 Oct 2016 14:54:27 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <846bf31f-a757-2be0-a293-8c4ce3d42a2f@FreeBSD.org> References: <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> <20161008180742.GA1912@c720-r292778-amd64> <846bf31f-a757-2be0-a293-8c4ce3d42a2f@FreeBSD.org> From: Warner Losh Date: Sat, 8 Oct 2016 15:54:27 -0600 X-Google-Sender-Auth: SUnBbpK-_veIlHjIrua1Swz_J94 Message-ID: Subject: Re: [request for testing] isl, cyapa on chromebooks To: Andriy Gapon Cc: Matthias Apitz , Michael Gmelin , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 21:54:29 -0000 Speaking of Chromebooks, what's the best way to put FreeBSD onto one? Warner On Sat, Oct 8, 2016 at 1:17 PM, Andriy Gapon wrote: > On 08/10/2016 21:07, Matthias Apitz wrote: >> I have now produced a memstick with (unpatched) r306769 of October 6. It boots >> fine in my Acer C720 Chromebook and the moused is working fine with the >> cyapa(4) driver. I will apply tomorrow the above v4 patch or is there >> anything newer? And will test/report. > > v4 is the latest. Thanks! > > -- > Andriy Gapon > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Sat Oct 8 22:27:54 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38A97C06C83 for ; Sat, 8 Oct 2016 22:27:54 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E76A0D5A for ; Sat, 8 Oct 2016 22:27:53 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [88.217.109.187] (helo=[192.168.2.102]) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1bt05v-0008TL-DX for freebsd-current@freebsd.org; Sun, 09 Oct 2016 00:27:51 +0200 From: Matthias Apitz To: Subject: Re: [request for testing] isl, cyapa on chromebooks Date: Sun, 09 Oct 2016 00:27:50 +0200 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <181117b0-69ab-4a83-b428-295d5d1c998d@unixarea.de> In-Reply-To: References: <20161005004831.2a2fdc4b@bsd64.grem.de> <1bcfd282-63fd-f8ee-4dad-393b51f14bcd@FreeBSD.org> <302FDA6E-DEC7-49F0-8F2C-8C26C8A884AF@freebsd.org> <53bca4d2-975f-f4a0-d12a-5d73fba01a0c@FreeBSD.org> <20161006044732.GA2393@c720-r292778-amd64.oa.oclc.org> <734c7ac0-9018-051e-1df4-a3b719057e19@FreeBSD.org> <773efe54-8ebb-e0e7-7824-10cfaa96d850@FreeBSD.org> <1EE0A2F3-86B9-4806-875E-3845A209A743@freebsd.org> <20161008180742.GA1912@c720-r292778-amd64> <846bf31f-a757-2be0-a293-8c4ce3d42a2f@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 88.217.109.187 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2016 22:27:54 -0000 On Saturday, 8 October 2016 23:54:27 CEST, Warner Losh =20 wrote: > Speaking of Chromebooks, what's the best way to put FreeBSD onto one? >=20 Set it to developer mode or Legacy boot, boot and install 11-C or 12-C from=20= USB. matthias --=20 Sent from my Ubuntu phone http://www.unixarea.de/