From owner-freebsd-arm@freebsd.org Sun Mar 6 02:02:29 2016 Return-Path: Delivered-To: freebsd-arm@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 E36B3A13917 for ; Sun, 6 Mar 2016 02:02:29 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C43BF1D16 for ; Sun, 6 Mar 2016 02:02:29 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.chumby.lan (c-71-63-91-41.hsd1.va.comcast.net [71.63.91.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 73A13C1C for ; Sat, 5 Mar 2016 20:57:04 -0500 (EST) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Unstable NFS on recent CURRENT Message-Id: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> Date: Sat, 5 Mar 2016 20:57:03 -0500 To: freebsd-arm Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2016 02:02:30 -0000 On my BeagleBone Black running 11-CURRENT (r296162) lately I have been = having trouble with NFS. I have been doing a buildworld and buildkernel = with /usr/src and /usr/obj mounted via NFS. Recently, this process has = resulted in the buildworld failing at some point, with a variety of = errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" = of /usr/src doesn't manage to complete. It errors out thus: =3D=3D=3D=3D=3D [[...]] total 0 ls: ./.svn/pristine/fe: Permission denied ./.svn/pristine/ff: total 0 ls: ./.svn/pristine/ff: Permission denied ls: fts_read: Permission denied =3D=3D=3D=3D=3D On the console, I get the following: newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid = 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR = MIDDLEWARE) I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. = On the BeagleBone Black, I am mounting /usr/src and /usr/obj via = /etc/fstab as follows: chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 /build/src/head and /build/obj/bbb are both ZFS file systems. Has anyone else encountered this? It has only started happening = recently for me, it seems. Prior to this, I have been able to do a = buildworld and buildkernel successfully over NFS. Cheers, Paul.= From owner-freebsd-arm@freebsd.org Mon Mar 7 10:54:53 2016 Return-Path: Delivered-To: freebsd-arm@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 15E50AC1510 for ; Mon, 7 Mar 2016 10:54:53 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 8E6331828 for ; Mon, 7 Mar 2016 10:54:52 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lb0-x234.google.com with SMTP id xr8so28947842lbb.1 for ; Mon, 07 Mar 2016 02:54:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=AwNAlOL6+shJYInsBTyjlDikUz21lre7HUSvqTZMkWY=; b=Fjzflgxu43+Yu5js4dq+EgWzUKJL3cO9lA1MoMv9ikgZa9nF7ST2K9mcFhbwX8kEdo LqJ9FxqbAt4szEQ20+8om8oECuIR4JkmDR3X87jS0b8WLkwYZBliz1PdvtAII+tT05TL kSmcWV4MsN5qxSxRBzxtUVZyzgOrtqCwxZ6VFaDe1krvPRFrsjp/PWpkJj1JISwLCPhs rMgsaoI/c3Fxp84wyf4TkSqUo5I4H0z0gv1pc58+KdA4XpsmblUdKKhpPbVjc7DyMIqs YmlQ5iCJrU+2BjynYvageZL4kUpUcyG/9kCo21LaohAfyzGttDHM6d/suF6vbtGHanbw mUMg== 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:content-transfer-encoding; bh=AwNAlOL6+shJYInsBTyjlDikUz21lre7HUSvqTZMkWY=; b=AQPg1WpDOyIHmQPYXX3/IlU9218moIPH6tqTQPDBzyGb5jwAcGtNODkiTEK8Nty+AU H/vK2VX69cvy6TaJpSTdZy+thnnQp21Qo7vZUHE0T0yqrxJkTgXqQ1PkICD+ofoBK4z8 Bhs9jqV3zlfDP4DRF0CgyrYgGR/bTVYL1au/n7pYl1b/kyfxf+DSNDen8cWXcnc8Tbyq XidcWvhq8qQEnrOtm429nx9k6ZA8XsBRHyrqgxcDELRa2/QuuWKYE1U87JKol8VRN22A 0E96j5Qb2fLmxzgZMsSqUu4QVQHbR62DJ+rWqyeuC+KczD8XFR753LpT4HffjTaeoD8/ AVRA== X-Gm-Message-State: AD7BkJLVrTvgyk3TJnkyUHPXi8CJCANW4HOdlcHP2M0t7PXDwQcP6h36qLgsTH6kXMLp3A== X-Received: by 10.112.180.5 with SMTP id dk5mr4631207lbc.86.1457348090631; Mon, 07 Mar 2016 02:54:50 -0800 (PST) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id c126sm2739568lfb.2.2016.03.07.02.54.49 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Mar 2016 02:54:49 -0800 (PST) Subject: Re: Odd hang during boot on RPI2 for 2 days now To: freebsd-arm References: <56D99C2E.4020301@gmail.com> From: Jukka Ukkonen X-Enigmail-Draft-Status: N1110 Message-ID: <56DD5DF8.9090700@gmail.com> Date: Mon, 7 Mar 2016 12:54:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56D99C2E.4020301@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 10:54:53 -0000 Continuing where I previously left with this problem... When I set boot_verbose=1 in loader.conf I got a little more information before the poor RPI2 simply froze. Now the last shown line was... random: harvesting attach, 8 bytes (4 bits) from ukbd0 If I disconnect the USB keyboard and then reconnect it, the kernel prints the normal detach and attach messages, once again returns back to printing the "random: ..." line shown above, and freezes again. --jau On 03/04/16 16:31, Jukka Ukkonen wrote: > > Hello all, > > A couple of days ago I rebuilt 11-current for my RPI2. > For some odd and still unexplained reason it started > hanging after it had found the USB keyboard during the > auto-configure. I have tried "svn update" a few times > since the problem started, but apparently there has > been no patch to this. The latest svn version which I > have tried is 296383. > I attach the dmesg.boot from the last known good boot. > It shows the last known properly booting system was > 11.0-CURRENT r296310. > I have also marked the place where the boot now hangs > as follows ... > > ... > kbd1 at ukbd0 > *** > smsc0: chip 0xec00, rev. 0002 > ... > > Everything before the "***" mark seems to work just fine. > At the mark all progress stops and none of the messages > normally seen after this point are shown. > > Has something changed perhaps in a manner which could > cause this hang? > > --jau > From owner-freebsd-arm@freebsd.org Mon Mar 7 11:19:53 2016 Return-Path: Delivered-To: freebsd-arm@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 F03A6AC22F7 for ; Mon, 7 Mar 2016 11:19:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::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 BC6B1B69 for ; Mon, 7 Mar 2016 11:19:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 470501FE023; Mon, 7 Mar 2016 12:19:48 +0100 (CET) Subject: Re: Odd hang during boot on RPI2 for 2 days now To: Jukka Ukkonen , freebsd-arm References: <56D99C2E.4020301@gmail.com> <56DD5DF8.9090700@gmail.com> From: Hans Petter Selasky Message-ID: <56DD6476.80603@selasky.org> Date: Mon, 7 Mar 2016 12:22:30 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56DD5DF8.9090700@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 11:19:54 -0000 On 03/07/16 11:54, Jukka Ukkonen wrote: > > Continuing where I previously left with this problem... > When I set boot_verbose=1 in loader.conf I got a little > more information before the poor RPI2 simply froze. > Now the last shown line was... > > random: harvesting attach, 8 bytes (4 bits) from ukbd0 > > If I disconnect the USB keyboard and then reconnect it, > the kernel prints the normal detach and attach messages, > once again returns back to printing the "random: ..." > line shown above, and freezes again. > Then I think the init process is waiting for something. Would you manage to press CTRL+T in the console and see what is printed? --HPS From owner-freebsd-arm@freebsd.org Mon Mar 7 12:31:44 2016 Return-Path: Delivered-To: freebsd-arm@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 180109DB56E for ; Mon, 7 Mar 2016 12:31:44 +0000 (UTC) (envelope-from alan01346@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D91A71B0 for ; Mon, 7 Mar 2016 12:31:43 +0000 (UTC) (envelope-from alan01346@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id g203so129116794iof.2 for ; Mon, 07 Mar 2016 04:31:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=Hwu9eci/X3q7ccNDgfwGnREZAjbysWmuHUHTPbErF6Q=; b=P+yLVYukCBxNYimCOl49PI+WNeGeCLrrIru6zwDqYKJZDZgefvvNtV+VU+E3PJXKV2 Y84YBNf3pn9TubeiCOVtdoAPETGj+OvKO1RYYfdU6FGDNmvq4Ga7n/c0nrQLYGzp+c/y CNODGLKquePfV4KILyIiAzz8Rm28DydCtiXYJ0h72pBvG006nUYCw+IXIpS/5A7L+AHd Z93wUYMvVU3gVCJE3GJ9ezpf39WsqW+WA72zwu4n8fPmFTZDwTrEwlrNTedSGVDSTuhp fY/O6buknWsORIZ6NYExZgOoWuGVeQEXA4MnHb2aXlrKcF2CDgQS8tXH4gk11/DnPwzi GbTw== 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:date :message-id:subject:from:to; bh=Hwu9eci/X3q7ccNDgfwGnREZAjbysWmuHUHTPbErF6Q=; b=AQzD33v1yZn5W4uCJmaOuQJ8u8wqHRmYO0NoYGKXV5bXeHxl6F1pUwkAWC87IYl1TA cHX9F33RTZsQ0p0GlNfkGz8lbFL2q0dNUCG9J0VG6qIQwc/skuW67GGYs+8qAG0hFZWG 5LT6TaLXvItJz276ENzxTqGNvl+EPa6KkMiiiq8KDH2nWlRd8/2sG/3QxyQQzWBnefDJ EUv4oHNntUPCzHSiztDyU+dHoh71w32CWgjcLBwSSnjvruKyMZnqrpzo6eS+j83qyETe YZuR1VWfvZp42lWheVkbHd09wiIuan2IcBEZOIeUCJieVmSGHAaUItvtb3e9EOoQSTpK 46DQ== X-Gm-Message-State: AD7BkJJI+p93NHWL1AuEshcuYyQVZJLSK9AtNWz5Zfr5l6qrZQUGn9FytnMzbxRnqMbzdvg/5ZiyXUOJGUgZsA== MIME-Version: 1.0 X-Received: by 10.107.152.17 with SMTP id a17mr5580777ioe.195.1457353903073; Mon, 07 Mar 2016 04:31:43 -0800 (PST) Received: by 10.107.33.196 with HTTP; Mon, 7 Mar 2016 04:31:42 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Mar 2016 07:31:42 -0500 Message-ID: Subject: Re: freebsd-arm Digest, Vol 516, Issue 1 From: Alan Corey To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 12:31:44 -0000 Re: Odd hang during boot on RPI2 for 2 days now Sounds like it's trying to harvest entropy from keystrokes for randomness. Just guessing. This isn't a new installation that hasn't finished building ssl keys or something by any chance? I've seen mouse movements used for that. On 3/7/16, freebsd-arm-request@freebsd.org wrote: > Send freebsd-arm mailing list submissions to > freebsd-arm@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > or, via email, send a message with subject or body 'help' to > freebsd-arm-request@freebsd.org > > You can reach the person managing the list at > freebsd-arm-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-arm digest..." > > > Today's Topics: > > 1. Re: Odd hang during boot on RPI2 for 2 days now (Jukka Ukkonen) > 2. Re: Odd hang during boot on RPI2 for 2 days now > (Hans Petter Selasky) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 7 Mar 2016 12:54:48 +0200 > From: Jukka Ukkonen > To: freebsd-arm > Subject: Re: Odd hang during boot on RPI2 for 2 days now > Message-ID: <56DD5DF8.9090700@gmail.com> > Content-Type: text/plain; charset=utf-8 > > > Continuing where I previously left with this problem... > When I set boot_verbose=1 in loader.conf I got a little > more information before the poor RPI2 simply froze. > Now the last shown line was... > > random: harvesting attach, 8 bytes (4 bits) from ukbd0 > > If I disconnect the USB keyboard and then reconnect it, > the kernel prints the normal detach and attach messages, > once again returns back to printing the "random: ..." > line shown above, and freezes again. > > --jau > > > > On 03/04/16 16:31, Jukka Ukkonen wrote: >> >> Hello all, >> >> A couple of days ago I rebuilt 11-current for my RPI2. >> For some odd and still unexplained reason it started >> hanging after it had found the USB keyboard during the >> auto-configure. I have tried "svn update" a few times >> since the problem started, but apparently there has >> been no patch to this. The latest svn version which I >> have tried is 296383. >> I attach the dmesg.boot from the last known good boot. >> It shows the last known properly booting system was >> 11.0-CURRENT r296310. >> I have also marked the place where the boot now hangs >> as follows ... >> >> ... >> kbd1 at ukbd0 >> *** >> smsc0: chip 0xec00, rev. 0002 >> ... >> >> Everything before the "***" mark seems to work just fine. >> At the mark all progress stops and none of the messages >> normally seen after this point are shown. >> >> Has something changed perhaps in a manner which could >> cause this hang? >> >> --jau >> > > > > ------------------------------ > > Message: 2 > Date: Mon, 7 Mar 2016 12:22:30 +0100 > From: Hans Petter Selasky > To: Jukka Ukkonen , freebsd-arm > > Subject: Re: Odd hang during boot on RPI2 for 2 days now > Message-ID: <56DD6476.80603@selasky.org> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 03/07/16 11:54, Jukka Ukkonen wrote: >> >> Continuing where I previously left with this problem... >> When I set boot_verbose=1 in loader.conf I got a little >> more information before the poor RPI2 simply froze. >> Now the last shown line was... >> >> random: harvesting attach, 8 bytes (4 bits) from ukbd0 >> >> If I disconnect the USB keyboard and then reconnect it, >> the kernel prints the normal detach and attach messages, >> once again returns back to printing the "random: ..." >> line shown above, and freezes again. >> > > Then I think the init process is waiting for something. Would you manage > to press CTRL+T in the console and see what is printed? > > --HPS > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > ------------------------------ > > End of freebsd-arm Digest, Vol 516, Issue 1 > ******************************************* > -- Credit is the root of all evil. - AB1JX From owner-freebsd-arm@freebsd.org Mon Mar 7 14:31:53 2016 Return-Path: Delivered-To: freebsd-arm@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 E4DC5AC087E; Mon, 7 Mar 2016 14:31:53 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF52E77D; Mon, 7 Mar 2016 14:31:53 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1acwCB-0008IZ-Ki; Mon, 07 Mar 2016 15:31:45 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Subject: Re: Unstable NFS on recent CURRENT References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> Date: Mon, 07 Mar 2016 15:31:37 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=ALL_TRUSTED, BAYES_50, FUZZY_VPILL autolearn=disabled version=3.4.0 X-Scan-Signature: c09395f469c52153b963e4ff2d10f427 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 14:31:54 -0000 On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather wrote: > On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > having trouble with NFS. I have been doing a buildworld and buildkernel > with /usr/src and /usr/obj mounted via NFS. Recently, this process has > resulted in the buildworld failing at some point, with a variety of > errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > of /usr/src doesn't manage to complete. It errors out thus: > > ===== > [[...]] > total 0 > ls: ./.svn/pristine/fe: Permission denied > > ./.svn/pristine/ff: > total 0 > ls: ./.svn/pristine/ff: Permission denied > ls: fts_read: Permission denied > ===== > > On the console, I get the following: > > newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > MIDDLEWARE) > > > I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. > On the BeagleBone Black, I am mounting /usr/src and /usr/obj via > /etc/fstab as follows: > > chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 > chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 > > > /build/src/head and /build/obj/bbb are both ZFS file systems. > > Has anyone else encountered this? It has only started happening > recently for me, it seems. Prior to this, I have been able to do a > buildworld and buildkernel successfully over NFS. > > Cheers, > > Paul. I cc this to freebsd-fs for you. Ronald. From owner-freebsd-arm@freebsd.org Mon Mar 7 15:33:57 2016 Return-Path: Delivered-To: freebsd-arm@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 555ABAC238A for ; Mon, 7 Mar 2016 15:33:57 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::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 CF593B39 for ; Mon, 7 Mar 2016 15:33:56 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lb0-x229.google.com with SMTP id x1so134453166lbj.3 for ; Mon, 07 Mar 2016 07:33:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:cc:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=39jXR2u+YJyC8UyiClcYzxJF/WS73uaguy4u9rbcSAU=; b=nr+HMsdzcp6a/sM3aKv2B8HghkDtvB9t9XBRHO3w2cXYVS3wOsHdOTV2e5QstcikPS 3mbBv2cTlBFeSCHSZ7+rtrtJMLvuN7KQ4mEdMJN/DDUCHH688l0pXNKmlzJquaXNPxGm qy7iK+1WHFJ+y3iEWwR8S2y6rEetAZzjp1hHcRmeycTF2pg75UAFcu8++WEyta0w2JmC +n1FZYXGijAm59xvoIPpGoV4bWRRDUdwwiLuXpLgS7HDfIUiVssdTGOz/k97+oVNncZC pdnk1iwS6xUPl7aAx4ds6VJD/tbwTnz5naLqoT7MvjVzOj9gVO+M5vDFETJZwjv7qKTj V37A== 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:cc:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=39jXR2u+YJyC8UyiClcYzxJF/WS73uaguy4u9rbcSAU=; b=hoMw/RZUjjsaMAktRo/7hs+1OJsdyHRRgWrYK+EmEz7dEi9+zt+a/LnF/hpwes5ra5 ZxSo3Yxtrxaa6CtTNeS1TgiLgbf/dyhPtyKlCNOlETNEdseEwvzrsS8mCQCvip3/Xqt/ 0zJP7BqsJwpQwgR/sbKT3au7VPFflPy6KSCd2XveUeiGPBqBPFqGaAgq14AKD93AU8oK f7hIxCjyHb6SGWdX9COm8ZoCid68VDwlYhH3xos97jtn+fu8XiaHYxEtH8d7rajC2+xr mWItSH6bfnX1YYMylpRlcbb94accMahRllGWpGI4ezfJXWBNNfBB4a3WxzUpQFgwYmex iJeg== X-Gm-Message-State: AD7BkJL+cOLN/U083J1bFfDImq2tnHLSUSaxegXTZRwRiYD+bENV3Not7kX1kE9h6GrrKQ== X-Received: by 10.112.52.100 with SMTP id s4mr8109410lbo.108.1457364834861; Mon, 07 Mar 2016 07:33:54 -0800 (PST) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id su3sm2853649lbb.21.2016.03.07.07.33.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Mar 2016 07:33:53 -0800 (PST) Subject: Re: Odd hang during boot on RPI2 for 2 days now To: Hans Petter Selasky References: <56D99C2E.4020301@gmail.com> <56DD5DF8.9090700@gmail.com> <56DD6476.80603@selasky.org> From: Jukka Ukkonen X-Enigmail-Draft-Status: N1110 Cc: freebsd-arm Message-ID: <56DD9F60.7010509@gmail.com> Date: Mon, 7 Mar 2016 17:33:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56DD6476.80603@selasky.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 15:33:57 -0000 On 03/07/16 13:22, Hans Petter Selasky wrote: > On 03/07/16 11:54, Jukka Ukkonen wrote: >> >> Continuing where I previously left with this problem... >> When I set boot_verbose=1 in loader.conf I got a little >> more information before the poor RPI2 simply froze. >> Now the last shown line was... >> >> random: harvesting attach, 8 bytes (4 bits) from ukbd0 >> >> If I disconnect the USB keyboard and then reconnect it, >> the kernel prints the normal detach and attach messages, >> once again returns back to printing the "random: ..." >> line shown above, and freezes again. >> > > Then I think the init process is waiting for something. Would you manage > to press CTRL+T in the console and see what is printed? The ctrl-T trick might work with a keyboard connected via the serial line pins. With my USB keyboard and HDMI display combo it doesn't do anything at all. Surely the system must be waiting for something. Of that I am quite certain. It does not panic and it keeps reacting to the USB keyboard being disconnected and connected. Obviously it is still otherwise fine, at least sort of, but also firmly stuck waiting an event which either never happens or which goes undetected for some reason. --jau From owner-freebsd-arm@freebsd.org Mon Mar 7 15:48:12 2016 Return-Path: Delivered-To: freebsd-arm@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 D7EEFAC2B50 for ; Mon, 7 Mar 2016 15:48:12 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 B96A7973 for ; Mon, 7 Mar 2016 15:48:12 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 3e3e0e72-e47c-11e5-8de6-958346fd02ba X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Mon, 7 Mar 2016 15:49:57 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u27FmAlm001212; Mon, 7 Mar 2016 08:48:10 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1457365690.13785.179.camel@freebsd.org> Subject: Re: Odd hang during boot on RPI2 for 2 days now From: Ian Lepore To: Jukka Ukkonen , Hans Petter Selasky Cc: freebsd-arm Date: Mon, 07 Mar 2016 08:48:10 -0700 In-Reply-To: <56DD9F60.7010509@gmail.com> References: <56D99C2E.4020301@gmail.com> <56DD5DF8.9090700@gmail.com> <56DD6476.80603@selasky.org> <56DD9F60.7010509@gmail.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 15:48:12 -0000 On Mon, 2016-03-07 at 17:33 +0200, Jukka Ukkonen wrote: > On 03/07/16 13:22, Hans Petter Selasky wrote: > > On 03/07/16 11:54, Jukka Ukkonen wrote: > > > > > > Continuing where I previously left with this problem... > > > When I set boot_verbose=1 in loader.conf I got a little > > > more information before the poor RPI2 simply froze. > > > Now the last shown line was... > > > > > > random: harvesting attach, 8 bytes (4 bits) from ukbd0 > > > > > > If I disconnect the USB keyboard and then reconnect it, > > > the kernel prints the normal detach and attach messages, > > > once again returns back to printing the "random: ..." > > > line shown above, and freezes again. > > > > > > > Then I think the init process is waiting for something. Would you > > manage > > to press CTRL+T in the console and see what is printed? > > The ctrl-T trick might work with a keyboard connected via > the serial line pins. With my USB keyboard and HDMI display > combo it doesn't do anything at all. > Surely the system must be waiting for something. Of that I > am quite certain. It does not panic and it keeps reacting to > the USB keyboard being disconnected and connected. Obviously > it is still otherwise fine, at least sort of, but also firmly > stuck waiting an event which either never happens or which > goes undetected for some reason. Part of what's needed to diagnose this problem is dmesg output from a failed boot that is more than 1 or 2 lines snipped out of context. It sounds to me like this has nothing to do with the usb keyboard except for the random coincidence that it is the last usb device to be enumerated. It seems like the system is hung waiting for an interrupt, and there's no reason to think it's necessarily a usb interrupt that's missing. Also, it seems unlikely that ^T will produce any output, because it sounds like init hasn't even started yet, and the low-level console used during boot doesn't respond to ^T/SIGINFO. -- Ian From owner-freebsd-arm@freebsd.org Mon Mar 7 21:29:37 2016 Return-Path: Delivered-To: freebsd-arm@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 C1994AC3377 for ; Mon, 7 Mar 2016 21:29:37 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::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 7C06FFD2 for ; Mon, 7 Mar 2016 21:29:37 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-vk0-x232.google.com with SMTP id e6so132785200vkh.2 for ; Mon, 07 Mar 2016 13:29:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vzqjleksSE6feDxqRCZc9vNettHnzfKr52daLDtj5Y8=; b=WWcL3gRHYLJG8Wd628WZy7ThtjAsODCnvXB/VlZcfAUin3CMQpUliRGHSq+sLgwmze Ts1t2NHvmW1C6h0xIsQ/u3RVFXKy9o6mtyUqVTpKo5KPp2xLF/vQJ/qh2MsjZ4ZCWJrB 7CnjuQIAI+D/7ACz1gjqXEOwSF6YR6o12x1xQUt1fa/PwD+Jm7AqdfaR7cy3VWK4c0ze Ux+ZM9UdqVhjtgKHxtOcwK/P80ErQw66/d5UZuSF6VyfkCE+fYvM8RjvX8UKvLhLIJA5 rLrXxDnkvOCSqQlrnt5+O+F3aS7VcDhi2nCmJnAhZoQ4xC98ssk6bInsdN+TZ5X2EUFp 9alw== 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=vzqjleksSE6feDxqRCZc9vNettHnzfKr52daLDtj5Y8=; b=ZkRAbPNgY0LLZBQxpOF7o2khZLmihszsaeQSNgz5H0UKHKyNN8mD4oy901pNxXZFf3 6L/+xAQoU5Tc6WPiLYKsDi/hGtc+ZoZoRwz/j4i/Ergz2ysjLG7TmJEEbQnUZjvKxz+9 4+5Duz16EpKmPQaL16m6y5ypUVd5wirog4YJDyg/2vAZC5zT2CQnZPH3NCWReDMqyKG2 CR1L3Ql9U8GYIltdjbc1KbForkH+Ia1V/x2etCWHXsdtHEmW0WGy/wTAsZR5c9iCumiv Sog9r1G/bsfubdiEu9KzLYcKp8cMID8uMMKEHzQR/heloC/xo0MRcqYolmyjoNgMckJd GH/w== X-Gm-Message-State: AD7BkJJL9IP1sf3qniYy6SBLwAHNdBMsp+zrBr+MEYi2GA5fonMBzd6+3PCtxzOG5TuZb2ueSNQwmjGL6DLnWbiiHNVWfx88mcQjVyVRRUEIm9i00a2RwFqTbTSpNNF+ef9ByS41Rt17BwaOGizO+A== X-Received: by 10.31.14.195 with SMTP id 186mr22524945vko.2.1457386176308; Mon, 07 Mar 2016 13:29:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.36.197 with HTTP; Mon, 7 Mar 2016 13:29:21 -0800 (PST) In-Reply-To: <437ca32e613c8ecc6825e6da18ca64b1@bakulin.de> References: <20160229225811.GB74374@server.rulingia.com> <20160301002249.GA61549@mutt-hardenedbsd> <437ca32e613c8ecc6825e6da18ca64b1@bakulin.de> From: "Lundberg, Johannes" Date: Mon, 7 Mar 2016 13:29:21 -0800 Message-ID: Subject: Re: FreeBSD on the RaspberryPi 3 To: Ilya Bakulin Cc: Adrian Chadd , "freebsd-arm@freebsd.org" , imp@freebsd.org, owner-freebsd-arm@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 21:29:38 -0000 Hi Ilya Great work! I am eager to start using the eMMC on my Intel Atom board so whatever I can do to help. This board uses ACPI by default so I started working on a sdhci_acpi driver but it is also possible to switch to PCI in BIOS. However, with PCI mode and the original FreeBSD 11 code or your patch, it can't detect the MMC memory chip (which is soldered to the board). I wonder if that is related to the problem they have on Linux http://permalink.gmane.org/gmane.linux.kernel.mmc/35512 Simply, it says like this: "Intel BXT/APL use a card detect GPIO however the host controller will not enable bus power unless it's card detect also reflects the presence of a card. Unfortunately those 2 things race which can result in commands not starting, after which the controller does nothing and there is a 10 second wait for the driver's 10-second timer to timeout. That is fixed by having the driver look also at the present state register to determine if the card is present. Consequently, provide a 'get_cd' sdhci host operation for BXT/APL that does that." Will your patch take this into consideration? If you need a board for testing, let me know. On Wed, Mar 2, 2016 at 3:37 AM, Ilya Bakulin wrote: > On 2016-03-01 03:07, Adrian Chadd wrote: > >> Someone ordered me one, so I can take a crack at the broadcom sdio bits. >> >> It'll require the ARM SDIO driver to first work.. >> >> > Actually SDIO support I'm working on is not ARM-specific, it can work wit= h > any SDHC driver FreeBSD already has support for. > > With the release of RPi3 I'm kinda feel really motivated to finish SDIO > implementation ASAP. I've already ordered one board yesterday. > > Anyone who wants to track progress just keep an eye on > https://reviews.freebsd.org/D4761. > Short summary: my stack is already able to init SDIO cards and do data > transfers. I need to implement some missing bits, but it's in a good shap= e. > > I'm doing this work in my spare time, so cannot make any promises, though= . > > -- > Ilya > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > --=20 =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- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-arm@freebsd.org Tue Mar 8 02:55:58 2016 Return-Path: Delivered-To: freebsd-arm@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 368ADAC3018; Tue, 8 Mar 2016 02:55:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id D9A7984F; Tue, 8 Mar 2016 02:55:57 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:GkQ+Yh85dPzSQP9uRHKM819IXTAuvvDOBiVQ1KB91ukcTK2v8tzYMVDF4r011RmSDdqdu6gP1raempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXsq3G/pQQfBg/4fVIsYL+lRciC1Y/qi6ibwN76XUZhvHKFe7R8LRG7/036l/I9ps9cEJs30QbDuXBSeu5blitCLFOXmAvgtI/rpMYwu3cYh/V0zclGWKH2N4c8SqQQWC4hNWkx6IjvtALfViOM4nwEFHoNxElmGQ/AuSv7VZS5lyLxte5w3WHOJ8j/RrMwVDGK8qBkVRLskCdBPDdvozKfsdB5kK8O+EHpnBd42YOBOIw= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQAcPt5W/61jaINchAxtBrpCAQ2BaRcKhSRKAoFsFAEBAQEBAQEBYyeCLYIUAQEBAwEBAQEgKyALEAIBCBgCAg0ZAgInAQkmAgQIBwQBHASHewgOrxWPNwEBAQEBAQEBAgEBAQEBAQEVBHuFHIF3gkaEGwEBBRaDAoE6BYdWhk49iEmFY4JwgjKRY45TAh4BAUKCAxmBZh4uAQaIRjR+AQEB X-IronPort-AV: E=Sophos;i="5.22,554,1449550800"; d="scan'208";a="269547572" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 07 Mar 2016 21:55:56 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id DCD1115F56D; Mon, 7 Mar 2016 21:55:56 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id FlLsQhU7lwah; Mon, 7 Mar 2016 21:55:56 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 4246315F571; Mon, 7 Mar 2016 21:55:56 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id z5e-MhSE5FSM; Mon, 7 Mar 2016 21:55:56 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 239CB15F56D; Mon, 7 Mar 2016 21:55:56 -0500 (EST) Date: Mon, 7 Mar 2016 21:55:56 -0500 (EST) From: Rick Macklem To: Ronald Klop Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Message-ID: <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> In-Reply-To: References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> Subject: Re: Unstable NFS on recent CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191) Thread-Topic: Unstable NFS on recent CURRENT Thread-Index: XMoWvOdVc3ZSKiQh8ntIVyTwG3qPoQ== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 02:55:58 -0000 Paul Mather (forwarded by Ronald Klop) wrote: > On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather > wrote: > > > On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > > having trouble with NFS. I have been doing a buildworld and buildkernel > > with /usr/src and /usr/obj mounted via NFS. Recently, this process has > > resulted in the buildworld failing at some point, with a variety of > > errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > > of /usr/src doesn't manage to complete. It errors out thus: > > > > ===== > > [[...]] > > total 0 > > ls: ./.svn/pristine/fe: Permission denied > > > > ./.svn/pristine/ff: > > total 0 > > ls: ./.svn/pristine/ff: Permission denied > > ls: fts_read: Permission denied > > ===== > > > > On the console, I get the following: > > > > newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > > 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > > MIDDLEWARE) > > > > > > I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. > > On the BeagleBone Black, I am mounting /usr/src and /usr/obj via > > /etc/fstab as follows: > > > > chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 > > chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 > > > > > > /build/src/head and /build/obj/bbb are both ZFS file systems. > > Is it possible that a ZFS file system has gotten to the point where the i-node# exceeds 32bits? ZFS does support more than 32bits for i-node#s, but FreeBSD does not (it truncates to the low order 32bits). I know diddly about ZFS, so I don't know if you actually have to create more than 4billion files to get the i-node# to exceed 32bits or ??? There has been work done on making ino_t 64bits, but it hasn't made it into FreeBSD-current and I have no idea when it might. If you could try a build on newly created file systems (or UFS ones instead of ZFS), that would tell you if the above might be the problem. rick > > Has anyone else encountered this? It has only started happening > > recently for me, it seems. Prior to this, I have been able to do a > > buildworld and buildkernel successfully over NFS. > > > > Cheers, > > > > Paul. > > I cc this to freebsd-fs for you. > > Ronald. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Tue Mar 8 12:31:01 2016 Return-Path: Delivered-To: freebsd-arm@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 1EE95AC3B4A for ; Tue, 8 Mar 2016 12:31:01 +0000 (UTC) (envelope-from mgamsjager@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 E8A346E3 for ; Tue, 8 Mar 2016 12:31:00 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-io0-x229.google.com with SMTP id z76so23815485iof.3 for ; Tue, 08 Mar 2016 04:31:00 -0800 (PST) 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; bh=2Ka7NmVmQlxO8YneZJuTC7qLHsOfPOHdeLUcnxLTUQQ=; b=wWl7ON5tXS++HesX8lRX3loiFZ3kQpLlFv/lgXUMe7P25gm4QQQrSDiz9UxY9dY+yd 1r7TxvWji/TJAybii8CDolj+pndbXhuX4S1RjIi9+lWhTT5aHlYmA0yJb+kytoS7/SOt nnVDA9Q0ZHC2tGpTXoeAndPMK7kensc2LCBeDp2luS0NbbhObJ1W9+vw7EnzsFj8JlYm RCEw/xOJ24ixybPnoMHf3mX4ttaRqpiy3Hb0TfivUTk47jWTKxMWQFELxaxyruU2Bmm1 lbTDj6q3tSz7YZuXD+lcyEPow9tcT/6NBvneL70epjo7b3JQqmNgdOAqyxFCe/7QYzbG dNmQ== 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; bh=2Ka7NmVmQlxO8YneZJuTC7qLHsOfPOHdeLUcnxLTUQQ=; b=fkGZyamd8ZpFHSs77C+s+NlsxteT+XyJUFq0woQMEggzD2kcqSE50bkP07JM3y4ddA k6UlC01Yizx1qBAKmpdORYHosOIXqFJ8AcPCez1qDP2nhFc39ib4NTfXemnlBunmF6ps ge2W5dq6ooiPtC5lccASBPcZQQf9ceVlohrQi0IhZq7YW7ZkJ0szT+MRBhZjLwl2NhYp LhAYD1i7uz0R+3Dy2+1FkwaBt66pdrLELlInPfLwdYtyxqwz5VIkmevZ483K6Km2WVfL rapwTF45xWETHHgmbgUowNyMl0zdx+UHkRANFP2Wx5MaPR2+9Lq/7YN8HiObNjH188K+ fnCw== X-Gm-Message-State: AD7BkJJufgxaxZRzMCmLThMJQgG2lxTfmn198vB4r/WGJw0NJhA6uLAVSJqbiD0llZSaZu6R7204ceje70QW8g== X-Received: by 10.107.12.207 with SMTP id 76mr6978712iom.70.1457440260192; Tue, 08 Mar 2016 04:31:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.149.229 with HTTP; Tue, 8 Mar 2016 04:30:28 -0800 (PST) In-Reply-To: <56D995F2.10909@ceetonetechnology.com> References: <56D995F2.10909@ceetonetechnology.com> From: Matthias Gamsjager Date: Tue, 8 Mar 2016 13:30:28 +0100 Message-ID: Subject: Re: OpenBSD RPi3 dmesg and install prompt To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 12:31:01 -0000 On Fri, Mar 4, 2016 at 3:04 PM, George Rosamond < george@ceetonetechnology.com> wrote: > fyi: > > http://ix.io/oJV Totally offtopic but the last time (couple of days ago) I checked OpenBSD would never be ported to RPI because of the Broadcom bin blob that is/was needed. What changed? From owner-freebsd-arm@freebsd.org Tue Mar 8 14:01:36 2016 Return-Path: Delivered-To: freebsd-arm@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 B1436AC7EA9; Tue, 8 Mar 2016 14:01:36 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 87947224; Tue, 8 Mar 2016 14:01:36 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 45604E07; Tue, 8 Mar 2016 09:01:29 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Unstable NFS on recent CURRENT From: Paul Mather In-Reply-To: <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> Date: Tue, 8 Mar 2016 09:01:29 -0500 Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 14:01:36 -0000 On Mar 7, 2016, at 9:55 PM, Rick Macklem wrote: > Paul Mather (forwarded by Ronald Klop) wrote: >> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather = >> wrote: >>=20 >>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have = been >>> having trouble with NFS. I have been doing a buildworld and = buildkernel >>> with /usr/src and /usr/obj mounted via NFS. Recently, this process = has >>> resulted in the buildworld failing at some point, with a variety of >>> errors (Segmentation fault; Permission denied; etc.). Even a "ls = -alR" >>> of /usr/src doesn't manage to complete. It errors out thus: >>>=20 >>> =3D=3D=3D=3D=3D >>> [[...]] >>> total 0 >>> ls: ./.svn/pristine/fe: Permission denied >>>=20 >>> ./.svn/pristine/ff: >>> total 0 >>> ls: ./.svn/pristine/ff: Permission denied >>> ls: fts_read: Permission denied >>> =3D=3D=3D=3D=3D >>>=20 >>> On the console, I get the following: >>>=20 >>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid >>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER = OR >>> MIDDLEWARE) >>>=20 >>>=20 >>> I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS = server. >>> On the BeagleBone Black, I am mounting /usr/src and /usr/obj via >>> /etc/fstab as follows: >>>=20 >>> chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 >>> chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 >>>=20 >>>=20 >>> /build/src/head and /build/obj/bbb are both ZFS file systems. >>>=20 > Is it possible that a ZFS file system has gotten to the point where = the > i-node# exceeds 32bits? ZFS does support more than 32bits for = i-node#s, > but FreeBSD does not (it truncates to the low order 32bits). > I know diddly about ZFS, so I don't know if you actually have to = create > more than 4billion files to get the i-node# to exceed 32bits or ??? >=20 > There has been work done on making ino_t 64bits, but it hasn't made it > into FreeBSD-current and I have no idea when it might. >=20 > If you could try a build on newly created file systems (or UFS ones > instead of ZFS), that would tell you if the above might be the = problem. I don't think I have that big of a ZFS pool (it's 2 TB). :-) It doesn't seem that there are excessive numbers of inodes, and the = counts match up between the NFS client and server sides. In the information below, chumby is the NFS server and beaglebone the = client: pmather@beaglebone:~ % mount /dev/mmcsd0s2a on / (ufs, local, noatime, soft-updates) devfs on /dev (devfs, local) /dev/mmcsd0s1 on /boot/msdos (msdosfs, local, noatime) tmpfs on /tmp (tmpfs, local) tmpfs on /var/log (tmpfs, local) tmpfs on /var/tmp (tmpfs, local) chumby.chumby.lan:/build/src/head on /usr/src (nfs, nfsv4acls) chumby.chumby.lan:/build/obj/bbb on /usr/obj (nfs, nfsv4acls) pmather@beaglebone:~ % df -i /usr/src /usr/obj Filesystem 1K-blocks Used Avail Capacity = iused ifree %iused Mounted on chumby.chumby.lan:/build/src/head 2097152 1344484 752668 64% = 147835 1505336 9% /usr/src chumby.chumby.lan:/build/obj/bbb 530875884 1949364 528926520 0% = 70814 1057853040 0% /usr/obj paul@chumby:/home/paul> df -i /build/src/head /build/obj/bbb Filesystem 1K-blocks Used Avail Capacity iused = ifree %iused Mounted on zroot/SHARED/build/src/head 2097152 1344484 752668 64% 147835 = 1505336 9% /build/src/head zroot/SHARED/build/obj/bbb 530876268 1949364 528926904 0% 70814 = 1057853808 0% /build/obj/bbb On the NFS client system, these are the only NFS-related settings I have = in /etc/rc.conf: nfsuserd_enable=3D"YES" nfscbd_enable=3D"YES" Would you recommend I try it with nfscbd_enable=3D"NO"? I will try NFS from other clients to see whether it's just this = FreeBSD/arm system that's having problems. Cheers, Paul. >=20 > rick >=20 >>> Has anyone else encountered this? It has only started happening >>> recently for me, it seems. Prior to this, I have been able to do a >>> buildworld and buildkernel successfully over NFS. >>>=20 >>> Cheers, >>>=20 >>> Paul. >>=20 >> I cc this to freebsd-fs for you. >>=20 >> Ronald. >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Wed Mar 9 00:21:05 2016 Return-Path: Delivered-To: freebsd-arm@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 09646AC8CBB; Wed, 9 Mar 2016 00:21:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9EE0630E; Wed, 9 Mar 2016 00:21:04 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:PMRkmxKWSE7wICny8tmcpTZWNBhigK39O0sv0rFitYgVKfXxwZ3uMQTl6Ol3ixeRBMOAu60C27ed6fmocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWM5DIfUi/yKRBybrysXNWC0ILniqvootX6WEZhunmUWftKNhK4rAHc5IE9oLBJDeIP8CbPuWZCYO9MxGlldhq5lhf44dqsrtY4q3wD89pozcNLUL37cqIkVvQYSW1+ayFmrPDtrgTJGAuT+mMHACJRlhtTHxOD4gv3U53qvm39rOU63SCbOcj/S/cwWC++7qFlT1jmkioKPSU1tWjNj59Mi/djqQ+l7zl2347ZesnBLPNjeovSZ9QfRHYHUsJQXWpfHsWxY5ZZXMQbOuMNlYj2pBMrpBC9AQSpTLf1zzZDhXv72IUn1Os8HAXe3EorFoRd4zzvsNzpOfJKAqiOx67SwGCGNqsO1A== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQARa99W/61jaINcDoN+bQa6WAENgWkXCoUkSgKBfxQBAQEBAQEBAWMngi2CFAEBAQMBAQEBICsgCwULAgEIGAICDRkCAicBCSYCBAgHBAEcBId7CA6vT48oAQEBAQEBAQMBAQEBAQEBARQEe4UcgXuCR4QbAQEFFoMCgToFh1aGTj2ISYVjgnCCMpFkjlQCHgEBQoIDGYENWR4uAQaIRjR+AQEB X-IronPort-AV: E=Sophos;i="5.22,558,1449550800"; d="scan'208";a="269923465" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 08 Mar 2016 19:21:02 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 50CD315F56D; Tue, 8 Mar 2016 19:21:02 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id KJZ75w_GFmJ1; Tue, 8 Mar 2016 19:21:01 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 114FA15F571; Tue, 8 Mar 2016 19:21:01 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id sfvBTfNRv_Xb; Tue, 8 Mar 2016 19:21:00 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id E6BB715F56D; Tue, 8 Mar 2016 19:21:00 -0500 (EST) Date: Tue, 8 Mar 2016 19:21:00 -0500 (EST) From: Rick Macklem To: Paul Mather Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Message-ID: <913974596.10122887.1457482860865.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> Subject: Re: Unstable NFS on recent CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191) Thread-Topic: Unstable NFS on recent CURRENT Thread-Index: wFhsfjvkf8M3TtVVuwbPJgeedqxBkg== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 00:21:05 -0000 Paul Mather wrote: > On Mar 7, 2016, at 9:55 PM, Rick Macklem wrote: > > > Paul Mather (forwarded by Ronald Klop) wrote: > >> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather > >> wrote: > >> > >>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > >>> having trouble with NFS. I have been doing a buildworld and buildkernel > >>> with /usr/src and /usr/obj mounted via NFS. Recently, this process has > >>> resulted in the buildworld failing at some point, with a variety of > >>> errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > >>> of /usr/src doesn't manage to complete. It errors out thus: > >>> > >>> ===== > >>> [[...]] > >>> total 0 > >>> ls: ./.svn/pristine/fe: Permission denied > >>> > >>> ./.svn/pristine/ff: > >>> total 0 > >>> ls: ./.svn/pristine/ff: Permission denied > >>> ls: fts_read: Permission denied > >>> ===== > >>> > >>> On the console, I get the following: > >>> > >>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > >>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > >>> MIDDLEWARE) > >>> I have no idea how the fileid (i-node# in old terminology) could change. I haven't heard anyone else reporting this, so I can't explain it (except for the exceeds 32bits case, which you note below isn't likely). > >>> > >>> I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. > >>> On the BeagleBone Black, I am mounting /usr/src and /usr/obj via > >>> /etc/fstab as follows: > >>> > >>> chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 > >>> chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 > >>> > >>> > >>> /build/src/head and /build/obj/bbb are both ZFS file systems. > >>> > > Is it possible that a ZFS file system has gotten to the point where the > > i-node# exceeds 32bits? ZFS does support more than 32bits for i-node#s, > > but FreeBSD does not (it truncates to the low order 32bits). > > I know diddly about ZFS, so I don't know if you actually have to create > > more than 4billion files to get the i-node# to exceed 32bits or ??? > > > > There has been work done on making ino_t 64bits, but it hasn't made it > > into FreeBSD-current and I have no idea when it might. > > > > If you could try a build on newly created file systems (or UFS ones > > instead of ZFS), that would tell you if the above might be the problem. > > > I don't think I have that big of a ZFS pool (it's 2 TB). :-) > > It doesn't seem that there are excessive numbers of inodes, and the counts > match up between the NFS client and server sides. > > In the information below, chumby is the NFS server and beaglebone the client: > > pmather@beaglebone:~ % mount > /dev/mmcsd0s2a on / (ufs, local, noatime, soft-updates) > devfs on /dev (devfs, local) > /dev/mmcsd0s1 on /boot/msdos (msdosfs, local, noatime) > tmpfs on /tmp (tmpfs, local) > tmpfs on /var/log (tmpfs, local) > tmpfs on /var/tmp (tmpfs, local) > chumby.chumby.lan:/build/src/head on /usr/src (nfs, nfsv4acls) > chumby.chumby.lan:/build/obj/bbb on /usr/obj (nfs, nfsv4acls) > pmather@beaglebone:~ % df -i /usr/src /usr/obj > Filesystem 1K-blocks Used Avail Capacity iused > ifree %iused Mounted on > chumby.chumby.lan:/build/src/head 2097152 1344484 752668 64% 147835 > 1505336 9% /usr/src > chumby.chumby.lan:/build/obj/bbb 530875884 1949364 528926520 0% 70814 > 1057853040 0% /usr/obj > > > paul@chumby:/home/paul> df -i /build/src/head /build/obj/bbb > Filesystem 1K-blocks Used Avail Capacity iused > ifree %iused Mounted on > zroot/SHARED/build/src/head 2097152 1344484 752668 64% 147835 > 1505336 9% /build/src/head > zroot/SHARED/build/obj/bbb 530876268 1949364 528926904 0% 70814 > 1057853808 0% /build/obj/bbb > > > On the NFS client system, these are the only NFS-related settings I have in > /etc/rc.conf: > > nfsuserd_enable="YES" > nfscbd_enable="YES" > > > Would you recommend I try it with nfscbd_enable="NO"? > Unless you have enabled delegations, nfscbd isn't needed, so you can try this. However, I doubt it will make any difference. (Callbacks are only used for Delegations for NFSv4.0. As such, it doesn't matter if they are working unless delegations are enabled.) > I will try NFS from other clients to see whether it's just this FreeBSD/arm > system that's having problems. > There probably are few people using NFSv4 on arm (you may be the only one), so I wouldn't be surprised if there is some size/alignment bug in the client that arm finds. Trying non-arm clients may certainly be useful. You could also try an NFSv3 mount, since I would think others are using NFSv3 on arm. Good luck with it, rick > Cheers, > > Paul. > > > > > > rick > > > >>> Has anyone else encountered this? It has only started happening > >>> recently for me, it seems. Prior to this, I have been able to do a > >>> buildworld and buildkernel successfully over NFS. > >>> > >>> Cheers, > >>> > >>> Paul. > >> > >> I cc this to freebsd-fs for you. > >> > >> Ronald. > >> _______________________________________________ > >> freebsd-fs@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs > >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-arm@freebsd.org Wed Mar 9 00:49:33 2016 Return-Path: Delivered-To: freebsd-arm@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 4A30CAC77E0; Wed, 9 Mar 2016 00:49:33 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id C58306AF; Wed, 9 Mar 2016 00:49:32 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:C9qBfB2lXbfTlulqsmDT+DRfVm0co7zxezQtwd8ZsekVI/ad9pjvdHbS+e9qxAeQG96LtLQU1qGM7OjJYi8p39WoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6kO74TNaIBjjLw09fr2zQd6NyZTqnLrts7ToICx2xxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cYk7sb+sVBSaT3ebgjBfwdVWx+cjN92cvwqBOWTReT/mBOFSISkwFUGE7L9hz3VIz99Czgua140SieOMTwCrQ1Qiij6alsDxHyhSoNLDJ8+XvS2fB32ZpSvRbpghVjw4POKNWNPed6VqzHetYbWSxNWsdbETJdRI6wct1cIfAGOLNiroL+734Hphi6CAzkUPnqwzRLgnLz9bA93PksFRnGmgcpSYFd+E/Ipcn4Yf9BGdu+y7PFmHCaN6tb X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQAjct9W/61jaINcDoN+bQa6WAENgWkXCoUkSgKBfxQBAQEBAQEBAWMngi2CFQEBBAEBASAEJyALEAIBCBgCAg0ZAgInAQkmAgQIBwQBHASIAw6vW48lAQEBAQEBAQECAQEBAQEBAQEUBHuFHIF7gkeEGwEBBRaDAoE6BYdWhVp0PYhJhWOCcIIyhE2HaYUujlQCHgEBQoIDGYENWR4uAQaIRjR+AQEB X-IronPort-AV: E=Sophos;i="5.22,559,1449550800"; d="scan'208";a="269926196" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 08 Mar 2016 19:49:31 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 4710715F56D; Tue, 8 Mar 2016 19:49:31 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 0P5xFr62_XHf; Tue, 8 Mar 2016 19:49:30 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 9418815F571; Tue, 8 Mar 2016 19:49:30 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id b3VHMlovJOMe; Tue, 8 Mar 2016 19:49:30 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 7366715F56D; Tue, 8 Mar 2016 19:49:30 -0500 (EST) Date: Tue, 8 Mar 2016 19:49:30 -0500 (EST) From: Rick Macklem To: Paul Mather Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Message-ID: <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> Subject: Re: Unstable NFS on recent CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191) Thread-Topic: Unstable NFS on recent CURRENT Thread-Index: k8ThePUeTUqowV1bL9aF3N1wliHkwA== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 00:49:33 -0000 Paul Mather wrote: > On Mar 7, 2016, at 9:55 PM, Rick Macklem wrote: > > > Paul Mather (forwarded by Ronald Klop) wrote: > >> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather > >> wrote: > >> > >>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > >>> having trouble with NFS. I have been doing a buildworld and buildkernel > >>> with /usr/src and /usr/obj mounted via NFS. Recently, this process has > >>> resulted in the buildworld failing at some point, with a variety of > >>> errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > >>> of /usr/src doesn't manage to complete. It errors out thus: > >>> > >>> ===== > >>> [[...]] > >>> total 0 > >>> ls: ./.svn/pristine/fe: Permission denied > >>> > >>> ./.svn/pristine/ff: > >>> total 0 > >>> ls: ./.svn/pristine/ff: Permission denied > >>> ls: fts_read: Permission denied > >>> ===== > >>> > >>> On the console, I get the following: > >>> > >>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > >>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > >>> MIDDLEWARE) > >>> Oh, I had forgotten this. Here's the comment related to this error. (about line#445 in sys/fs/nfsclient/nfs_clport.c): 446 * BROKEN NFS SERVER OR MIDDLEWARE 447 * 448 * Certain NFS servers (certain old proprietary filers ca. 449 * 2006) or broken middleboxes (e.g. WAN accelerator products) 450 * will respond to GETATTR requests with results for a 451 * different fileid. 452 * 453 * The WAN accelerator we've observed not only serves stale 454 * cache results for a given file, it also occasionally serves 455 * results for wholly different files. This causes surprising 456 * problems; for example the cached size attribute of a file 457 * may truncate down and then back up, resulting in zero 458 * regions in file contents read by applications. We observed 459 * this reliably with Clang and .c files during parallel build. 460 * A pcap revealed packet fragmentation and GETATTR RPC 461 * responses with wholly wrong fileids. If you can connect the client->server with a simple switch (or just an RJ45 cable), it might be worth testing that way. (I don't recall the name of the middleware product, but I think it was shipped by one of the major switch vendors. I also don't know if the product supports NFSv4?) rick > >>> > >>> I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. > >>> On the BeagleBone Black, I am mounting /usr/src and /usr/obj via > >>> /etc/fstab as follows: > >>> > >>> chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 > >>> chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 > >>> > >>> > >>> /build/src/head and /build/obj/bbb are both ZFS file systems. > >>> > > Is it possible that a ZFS file system has gotten to the point where the > > i-node# exceeds 32bits? ZFS does support more than 32bits for i-node#s, > > but FreeBSD does not (it truncates to the low order 32bits). > > I know diddly about ZFS, so I don't know if you actually have to create > > more than 4billion files to get the i-node# to exceed 32bits or ??? > > > > There has been work done on making ino_t 64bits, but it hasn't made it > > into FreeBSD-current and I have no idea when it might. > > > > If you could try a build on newly created file systems (or UFS ones > > instead of ZFS), that would tell you if the above might be the problem. > > > I don't think I have that big of a ZFS pool (it's 2 TB). :-) > > It doesn't seem that there are excessive numbers of inodes, and the counts > match up between the NFS client and server sides. > > In the information below, chumby is the NFS server and beaglebone the client: > > pmather@beaglebone:~ % mount > /dev/mmcsd0s2a on / (ufs, local, noatime, soft-updates) > devfs on /dev (devfs, local) > /dev/mmcsd0s1 on /boot/msdos (msdosfs, local, noatime) > tmpfs on /tmp (tmpfs, local) > tmpfs on /var/log (tmpfs, local) > tmpfs on /var/tmp (tmpfs, local) > chumby.chumby.lan:/build/src/head on /usr/src (nfs, nfsv4acls) > chumby.chumby.lan:/build/obj/bbb on /usr/obj (nfs, nfsv4acls) > pmather@beaglebone:~ % df -i /usr/src /usr/obj > Filesystem 1K-blocks Used Avail Capacity iused > ifree %iused Mounted on > chumby.chumby.lan:/build/src/head 2097152 1344484 752668 64% 147835 > 1505336 9% /usr/src > chumby.chumby.lan:/build/obj/bbb 530875884 1949364 528926520 0% 70814 > 1057853040 0% /usr/obj > > > paul@chumby:/home/paul> df -i /build/src/head /build/obj/bbb > Filesystem 1K-blocks Used Avail Capacity iused > ifree %iused Mounted on > zroot/SHARED/build/src/head 2097152 1344484 752668 64% 147835 > 1505336 9% /build/src/head > zroot/SHARED/build/obj/bbb 530876268 1949364 528926904 0% 70814 > 1057853808 0% /build/obj/bbb > > > On the NFS client system, these are the only NFS-related settings I have in > /etc/rc.conf: > > nfsuserd_enable="YES" > nfscbd_enable="YES" > > > Would you recommend I try it with nfscbd_enable="NO"? > > I will try NFS from other clients to see whether it's just this FreeBSD/arm > system that's having problems. > > Cheers, > > Paul. > > > > > > rick > > > >>> Has anyone else encountered this? It has only started happening > >>> recently for me, it seems. Prior to this, I have been able to do a > >>> buildworld and buildkernel successfully over NFS. > >>> > >>> Cheers, > >>> > >>> Paul. > >> > >> I cc this to freebsd-fs for you. > >> > >> Ronald. > >> _______________________________________________ > >> freebsd-fs@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-fs > >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > From owner-freebsd-arm@freebsd.org Wed Mar 9 16:12:44 2016 Return-Path: Delivered-To: freebsd-arm@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 869BCAC9755; Wed, 9 Mar 2016 16:12:44 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5CDA1C50; Wed, 9 Mar 2016 16:12:44 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from pmather.lib.vt.edu (pmather.lib.vt.edu [128.173.126.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id E5109F21; Wed, 9 Mar 2016 11:12:36 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Unstable NFS on recent CURRENT From: Paul Mather In-Reply-To: <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> Date: Wed, 9 Mar 2016 11:12:36 -0500 Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <60E8006A-F0A8-4284-839E-882FAD7E6A55@gromit.dlib.vt.edu> References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 16:12:44 -0000 On Mar 8, 2016, at 7:49 PM, Rick Macklem wrote: > Paul Mather wrote: >> On Mar 7, 2016, at 9:55 PM, Rick Macklem = wrote: >>=20 >>> Paul Mather (forwarded by Ronald Klop) wrote: >>>> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather = >>>> wrote: >>>>=20 >>>>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have = been >>>>> having trouble with NFS. I have been doing a buildworld and = buildkernel >>>>> with /usr/src and /usr/obj mounted via NFS. Recently, this = process has >>>>> resulted in the buildworld failing at some point, with a variety = of >>>>> errors (Segmentation fault; Permission denied; etc.). Even a "ls = -alR" >>>>> of /usr/src doesn't manage to complete. It errors out thus: >>>>>=20 >>>>> =3D=3D=3D=3D=3D >>>>> [[...]] >>>>> total 0 >>>>> ls: ./.svn/pristine/fe: Permission denied >>>>>=20 >>>>> ./.svn/pristine/ff: >>>>> total 0 >>>>> ls: ./.svn/pristine/ff: Permission denied >>>>> ls: fts_read: Permission denied >>>>> =3D=3D=3D=3D=3D >>>>>=20 >>>>> On the console, I get the following: >>>>>=20 >>>>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid >>>>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER = OR >>>>> MIDDLEWARE) >>>>>=20 > Oh, I had forgotten this. Here's the comment related to this error. > (about line#445 in sys/fs/nfsclient/nfs_clport.c): > 446 * BROKEN NFS SERVER OR MIDDLEWARE > 447 * > 448 * Certain NFS servers (certain old proprietary = filers ca. > 449 * 2006) or broken middleboxes (e.g. WAN = accelerator products) > 450 * will respond to GETATTR requests with results = for a > 451 * different fileid. > 452 * > 453 * The WAN accelerator we've observed not only = serves stale > 454 * cache results for a given file, it also = occasionally serves > 455 * results for wholly different files. This = causes surprising > 456 * problems; for example the cached size = attribute of a file > 457 * may truncate down and then back up, resulting = in zero > 458 * regions in file contents read by = applications. We observed > 459 * this reliably with Clang and .c files during = parallel build. > 460 * A pcap revealed packet fragmentation and = GETATTR RPC > 461 * responses with wholly wrong fileids. >=20 > If you can connect the client->server with a simple switch (or just an = RJ45 cable), it > might be worth testing that way. (I don't recall the name of the = middleware product, but > I think it was shipped by one of the major switch vendors. I also = don't know if the product > supports NFSv4?) >=20 > rick Currently, the client is connected to the server via a dumb gigabit = switch, so it is already fairly direct. As for the above error, it appeared on the console only once. (Sorry if = I made it sound like it appears every time.) I just tried another buildworld attempt via NFS and it failed again. = This time, I get this on the BeagleBone Black console: nfs_getpages: error 13 vm_fault: pager read error, pid 5401 (install) The other thing I have noticed is that if I induce heavy load on the NFS = server---e.g., by starting a Poudriere bulk build---then that provokes = the client to crash much more readily. For example, I started a NFS = buildworld on the BeagleBone Black, and it seemed to be chugging along = nicely. The moment I kicked off a Poudriere build update of my packages = on the NFS server, it crashed the buildworld on the NFS client. I have had problems with swap on FreeBSD/arm before. Swapping to a file = does not appear to work for me. As a result, I switched to swapping to = a partition on the SD card. Maybe this is unreliable, too? Cheers, Paul. From owner-freebsd-arm@freebsd.org Wed Mar 9 18:34:12 2016 Return-Path: Delivered-To: freebsd-arm@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 BD212AC8773 for ; Wed, 9 Mar 2016 18:34:12 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 59688782; Wed, 9 Mar 2016 18:34:12 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lb0-x234.google.com with SMTP id k15so79339591lbg.0; Wed, 09 Mar 2016 10:34:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=cAqhsB1qR7WIKMp/8/J/i3Oi08ZXC0aNuPOvhcTfXvs=; b=i01t1JmXv65W84r1J3Rl22LQ8k7I5WUctxXddowVpqMURTF2CyP3ddKoWU1Nu+g3Lp Solj9azWGhCmbO7C15SqU6IcmlIcOrGblazH/4lh1Q4JNs2ItcOhppMlXv4UNH0vXUNa xwa5XuW1uCU0XWs7IYwjz/rESTif8oJZaz5Y37SuWW/td2UamxqbJPuh04EfJJqF4Gk5 IR5c2rj1NYGX+CilbFYtUaJW7Syqm7niAcgyOAUwujHG0BfxpgH8kP8chtU4OeOz7PRb CivrbED9GOO0Fruvj7RLUAbUDNrZsHoNf/uDGFZftalUjUfNW0pEIFF1NWVA64Cl61Y6 7bwQ== 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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=cAqhsB1qR7WIKMp/8/J/i3Oi08ZXC0aNuPOvhcTfXvs=; b=USz+10HfCiBOi67+lM30Q0/FLsWxqNfIbaBHEK1aRtKs9iSAFeY6JKoico/ixd6qDB 5QUkthSGdJFsz31nvCUWO89XJCIRwa67pYWamPpf1+N98jaYCaN3GzzHLbDS7kjWDjUM obOenssW8QJYMbeiDGCnn6QasyPIWcSlQpPumtwuyvdyz7y3SLozlUdCTbgbzAimPGx7 L1IGmC0B7ryfksgxhhzFkGVBbMrz6iwIKP0qghW4m4X890JSoNaO+0z45HOePwDMdPKD MOqnDrm7MtHzKkiQDoIUYq37fEiBp4rAwnPmtlu7c9346eLJ/fT49PtAmSJxRm8ehDEF OhGQ== X-Gm-Message-State: AD7BkJK+QgFLgTyoxGp8w9DmwIvFl1v0Cmo6r8xtlCLwTpI95s4tFSJqLSOCNohEzlE6Nw== X-Received: by 10.25.16.207 with SMTP id 76mr13232509lfq.133.1457548450312; Wed, 09 Mar 2016 10:34:10 -0800 (PST) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id e191sm1488883lfb.39.2016.03.09.10.34.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2016 10:34:09 -0800 (PST) Subject: Re: Odd hang during boot on RPI2 for 2 days now To: Ian Lepore , Hans Petter Selasky References: <56D99C2E.4020301@gmail.com> <56DD5DF8.9090700@gmail.com> <56DD6476.80603@selasky.org> <56DD9F60.7010509@gmail.com> <1457365690.13785.179.camel@freebsd.org> Cc: freebsd-arm From: Jukka Ukkonen X-Enigmail-Draft-Status: N1110 Message-ID: <56E06CA0.4030107@gmail.com> Date: Wed, 9 Mar 2016 20:34:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1457365690.13785.179.camel@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2016 18:34:12 -0000 On 03/07/16 17:48, Ian Lepore wrote: > On Mon, 2016-03-07 at 17:33 +0200, Jukka Ukkonen wrote: >> On 03/07/16 13:22, Hans Petter Selasky wrote: >>> On 03/07/16 11:54, Jukka Ukkonen wrote: >>>> >>>> Continuing where I previously left with this problem... >>>> When I set boot_verbose=1 in loader.conf I got a little >>>> more information before the poor RPI2 simply froze. >>>> Now the last shown line was... >>>> >>>> random: harvesting attach, 8 bytes (4 bits) from ukbd0 >>>> >>>> If I disconnect the USB keyboard and then reconnect it, >>>> the kernel prints the normal detach and attach messages, >>>> once again returns back to printing the "random: ..." >>>> line shown above, and freezes again. >>>> >>> >>> Then I think the init process is waiting for something. Would you >>> manage >>> to press CTRL+T in the console and see what is printed? >> >> The ctrl-T trick might work with a keyboard connected via >> the serial line pins. With my USB keyboard and HDMI display >> combo it doesn't do anything at all. >> Surely the system must be waiting for something. Of that I >> am quite certain. It does not panic and it keeps reacting to >> the USB keyboard being disconnected and connected. Obviously >> it is still otherwise fine, at least sort of, but also firmly >> stuck waiting an event which either never happens or which >> goes undetected for some reason. > > Part of what's needed to diagnose this problem is dmesg output from a > failed boot that is more than 1 or 2 lines snipped out of context. It > sounds to me like this has nothing to do with the usb keyboard except > for the random coincidence that it is the last usb device to be > enumerated. It seems like the system is hung waiting for an interrupt, > and there's no reason to think it's necessarily a usb interrupt that's > missing. Getting the dmesg output for the failed boot would require a serial console cable connecting the RPI2 to another computer and script running on the other computer to record the output. Lacking such a cable this is a no-go of course. A new fresh dmesg.boot file will be generated only after a normal successful boot. And after a successful boot I would no longer need the content of the file. > Also, it seems unlikely that ^T will produce any output, because it > sounds like init hasn't even started yet, and the low-level console > used during boot doesn't respond to ^T/SIGINFO. At least the system has already tried to start init. There is a line ... start_init: trying /sbin/init shown some 30 lines before the freeze. If anyone wishes to see a photo of what is shown on the display when the system freezes, let me know. I will send a copy separately. There are some 60-70 lines of text shown in the image. I don't wish to spam the whole mailing list with a large image file, though. --jau From owner-freebsd-arm@freebsd.org Thu Mar 10 02:00:28 2016 Return-Path: Delivered-To: freebsd-arm@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 A05B6ACA793; Thu, 10 Mar 2016 02:00:28 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3D816F75; Thu, 10 Mar 2016 02:00:27 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:xlj03BGc05JqgNxMttjsUJ1GYnF86YWxBRYc798ds5kLTJ75oMSwAkXT6L1XgUPTWs2DsrQf27WQ4/+rBTRIyK3CmU5BWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYsExnyfTB4Ov7yUtaLyZ/niKbipNaPO01hv3mUX/BbFF2OtwLft80b08NJC50a7V/3mEZOYPlc3mhyJFiezF7W78a0+4N/oWwL46pyv+YJa6jxfrw5QLpEF3xmdjltvIy4/SXEGDOG+39Ud2wKkhdSS1zd5Qz+dpjrtS77qqxx3CiQe9PqC704RGLxwb1sTUrSiSwEfxsw+2LTh8k42LheqRmioxF665PTb5yYMOJ+OKjUK4BJDVFdV9pcAnQSSri3aJECWq9YZb5V X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DOAQC71OBW/61jaINeDoRsBrhGghMBDYFthg8CggQUAQEBAQEBAQFjJ4ItghQBAQEDASMEUgULAgEIGAICDRkCAlcCBBOIHAiwCo8qAQEBAQEBBAEBAQEBAQEZfIUcgXuCR4QiFoMCgToFh1cChVl0PYhVj1eHa4UuhX6IXgIeAQFCggMZgQ1ZHi4BiBcjARl+AQEB X-IronPort-AV: E=Sophos;i="5.24,313,1454994000"; d="scan'208";a="271821200" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-annu.net.uoguelph.ca with ESMTP; 09 Mar 2016 20:59:57 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 90D6E15F574; Wed, 9 Mar 2016 20:59:57 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id LTeijNFXb1or; Wed, 9 Mar 2016 20:59:56 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id BE86615F577; Wed, 9 Mar 2016 20:59:56 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id f1mLcALzsdLK; Wed, 9 Mar 2016 20:59:56 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 9B80F15F574; Wed, 9 Mar 2016 20:59:56 -0500 (EST) Date: Wed, 9 Mar 2016 20:59:56 -0500 (EST) From: Rick Macklem To: Paul Mather Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Message-ID: <508973676.11871738.1457575196588.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <60E8006A-F0A8-4284-839E-882FAD7E6A55@gromit.dlib.vt.edu> References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> <60E8006A-F0A8-4284-839E-882FAD7E6A55@gromit.dlib.vt.edu> Subject: Re: Unstable NFS on recent CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191) Thread-Topic: Unstable NFS on recent CURRENT Thread-Index: RMlqSV8ZIP43xWv9Rxwnw2Yw7ASWew== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 02:00:28 -0000 Paul Mather wrote: > On Mar 8, 2016, at 7:49 PM, Rick Macklem wrote: > > > Paul Mather wrote: > >> On Mar 7, 2016, at 9:55 PM, Rick Macklem wrote: > >> > >>> Paul Mather (forwarded by Ronald Klop) wrote: > >>>> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather > >>>> > >>>> wrote: > >>>> > >>>>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > >>>>> having trouble with NFS. I have been doing a buildworld and > >>>>> buildkernel > >>>>> with /usr/src and /usr/obj mounted via NFS. Recently, this process has > >>>>> resulted in the buildworld failing at some point, with a variety of > >>>>> errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > >>>>> of /usr/src doesn't manage to complete. It errors out thus: > >>>>> > >>>>> ===== > >>>>> [[...]] > >>>>> total 0 > >>>>> ls: ./.svn/pristine/fe: Permission denied > >>>>> > >>>>> ./.svn/pristine/ff: > >>>>> total 0 > >>>>> ls: ./.svn/pristine/ff: Permission denied > >>>>> ls: fts_read: Permission denied > >>>>> ===== > >>>>> > >>>>> On the console, I get the following: > >>>>> > >>>>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > >>>>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > >>>>> MIDDLEWARE) > >>>>> > > Oh, I had forgotten this. Here's the comment related to this error. > > (about line#445 in sys/fs/nfsclient/nfs_clport.c): > > 446 * BROKEN NFS SERVER OR MIDDLEWARE > > 447 * > > 448 * Certain NFS servers (certain old proprietary filers > > ca. > > 449 * 2006) or broken middleboxes (e.g. WAN accelerator > > products) > > 450 * will respond to GETATTR requests with results for a > > 451 * different fileid. > > 452 * > > 453 * The WAN accelerator we've observed not only serves > > stale > > 454 * cache results for a given file, it also > > occasionally serves > > 455 * results for wholly different files. This causes > > surprising > > 456 * problems; for example the cached size attribute of > > a file > > 457 * may truncate down and then back up, resulting in > > zero > > 458 * regions in file contents read by applications. We > > observed > > 459 * this reliably with Clang and .c files during > > parallel build. > > 460 * A pcap revealed packet fragmentation and GETATTR > > RPC > > 461 * responses with wholly wrong fileids. > > > > If you can connect the client->server with a simple switch (or just an RJ45 > > cable), it > > might be worth testing that way. (I don't recall the name of the middleware > > product, but > > I think it was shipped by one of the major switch vendors. I also don't > > know if the product > > supports NFSv4?) > > > > rick > > > Currently, the client is connected to the server via a dumb gigabit switch, > so it is already fairly direct. > > As for the above error, it appeared on the console only once. (Sorry if I > made it sound like it appears every time.) > > I just tried another buildworld attempt via NFS and it failed again. This > time, I get this on the BeagleBone Black console: > > nfs_getpages: error 13 > vm_fault: pager read error, pid 5401 (install) > 13 is EACCES and could be caused by what I mention below. (Any mount of a file system on the server unless "-S" is specified as a flag for mountd.) > > The other thing I have noticed is that if I induce heavy load on the NFS > server---e.g., by starting a Poudriere bulk build---then that provokes the > client to crash much more readily. For example, I started a NFS buildworld > on the BeagleBone Black, and it seemed to be chugging along nicely. The > moment I kicked off a Poudriere build update of my packages on the NFS > server, it crashed the buildworld on the NFS client. > Try adding "-S" to mountd_flags on the server. Any time file systems are mounted (and Poudriere likes to do that, I am told), mount sends a SIGHUP to mountd to reload /etc/exports. When /etc/exports are being reloaded, there will be access errors for mounts (that are temporarily not exported) unless you specify "-S" (which makes mountd suspend the nfsd threads during the reload of /etc/exports). rick > I have had problems with swap on FreeBSD/arm before. Swapping to a file does > not appear to work for me. As a result, I switched to swapping to a > partition on the SD card. Maybe this is unreliable, too? > > Cheers, > > Paul. > > From owner-freebsd-arm@freebsd.org Thu Mar 10 14:29:29 2016 Return-Path: Delivered-To: freebsd-arm@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 3FF25ACBFDD; Thu, 10 Mar 2016 14:29:29 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EFB3D2ED; Thu, 10 Mar 2016 14:29:28 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from macbook.chumby.lan (c-71-63-91-41.hsd1.va.comcast.net [71.63.91.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 0D922185; Thu, 10 Mar 2016 09:29:26 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: Unstable NFS on recent CURRENT From: Paul Mather In-Reply-To: <508973676.11871738.1457575196588.JavaMail.zimbra@uoguelph.ca> Date: Thu, 10 Mar 2016 09:29:25 -0500 Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> <60E8006A-F0A8-4284-839E-882FAD7E6A55@gromit.dlib.vt.edu> <508973676.11871738.1457575196588.JavaMail.zimbra@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.3112) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 14:29:29 -0000 On Mar 9, 2016, at 8:59 PM, Rick Macklem wrote: > Paul Mather wrote: >> On Mar 8, 2016, at 7:49 PM, Rick Macklem = wrote: >>=20 >>> Paul Mather wrote: >>>> On Mar 7, 2016, at 9:55 PM, Rick Macklem = wrote: >>>>=20 >>>>> Paul Mather (forwarded by Ronald Klop) wrote: >>>>>> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather >>>>>> >>>>>> wrote: >>>>>>=20 >>>>>>> On my BeagleBone Black running 11-CURRENT (r296162) lately I = have been >>>>>>> having trouble with NFS. I have been doing a buildworld and >>>>>>> buildkernel >>>>>>> with /usr/src and /usr/obj mounted via NFS. Recently, this = process has >>>>>>> resulted in the buildworld failing at some point, with a variety = of >>>>>>> errors (Segmentation fault; Permission denied; etc.). Even a = "ls -alR" >>>>>>> of /usr/src doesn't manage to complete. It errors out thus: >>>>>>>=20 >>>>>>> =3D=3D=3D=3D=3D >>>>>>> [[...]] >>>>>>> total 0 >>>>>>> ls: ./.svn/pristine/fe: Permission denied >>>>>>>=20 >>>>>>> ./.svn/pristine/ff: >>>>>>> total 0 >>>>>>> ls: ./.svn/pristine/ff: Permission denied >>>>>>> ls: fts_read: Permission denied >>>>>>> =3D=3D=3D=3D=3D >>>>>>>=20 >>>>>>> On the console, I get the following: >>>>>>>=20 >>>>>>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid >>>>>>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS = SERVER OR >>>>>>> MIDDLEWARE) >>>>>>>=20 >>> Oh, I had forgotten this. Here's the comment related to this error. >>> (about line#445 in sys/fs/nfsclient/nfs_clport.c): >>> 446 * BROKEN NFS SERVER OR MIDDLEWARE >>> 447 * >>> 448 * Certain NFS servers (certain old = proprietary filers >>> ca. >>> 449 * 2006) or broken middleboxes (e.g. WAN = accelerator >>> products) >>> 450 * will respond to GETATTR requests with = results for a >>> 451 * different fileid. >>> 452 * >>> 453 * The WAN accelerator we've observed = not only serves >>> stale >>> 454 * cache results for a given file, it = also >>> occasionally serves >>> 455 * results for wholly different files. = This causes >>> surprising >>> 456 * problems; for example the cached size = attribute of >>> a file >>> 457 * may truncate down and then back up, = resulting in >>> zero >>> 458 * regions in file contents read by = applications. We >>> observed >>> 459 * this reliably with Clang and .c files = during >>> parallel build. >>> 460 * A pcap revealed packet fragmentation = and GETATTR >>> RPC >>> 461 * responses with wholly wrong fileids. >>>=20 >>> If you can connect the client->server with a simple switch (or just = an RJ45 >>> cable), it >>> might be worth testing that way. (I don't recall the name of the = middleware >>> product, but >>> I think it was shipped by one of the major switch vendors. I also = don't >>> know if the product >>> supports NFSv4?) >>>=20 >>> rick >>=20 >>=20 >> Currently, the client is connected to the server via a dumb gigabit = switch, >> so it is already fairly direct. >>=20 >> As for the above error, it appeared on the console only once. (Sorry = if I >> made it sound like it appears every time.) >>=20 >> I just tried another buildworld attempt via NFS and it failed again. = This >> time, I get this on the BeagleBone Black console: >>=20 >> nfs_getpages: error 13 >> vm_fault: pager read error, pid 5401 (install) >>=20 > 13 is EACCES and could be caused by what I mention below. (Any mount = of a file > system on the server unless "-S" is specified as a flag for mountd.) >=20 >>=20 >> The other thing I have noticed is that if I induce heavy load on the = NFS >> server---e.g., by starting a Poudriere bulk build---then that = provokes the >> client to crash much more readily. For example, I started a NFS = buildworld >> on the BeagleBone Black, and it seemed to be chugging along nicely. = The >> moment I kicked off a Poudriere build update of my packages on the = NFS >> server, it crashed the buildworld on the NFS client. >>=20 > Try adding "-S" to mountd_flags on the server. Any time file systems = are mounted > (and Poudriere likes to do that, I am told), mount sends a SIGHUP to = mountd to > reload /etc/exports. When /etc/exports are being reloaded, there will = be access > errors for mounts (that are temporarily not exported) unless you = specify "-S" > (which makes mountd suspend the nfsd threads during the reload of = /etc/exports). >=20 > rick Bingo! I think we may have a winner. I added that flag to mountd_flags = on the server and the "instability" appears to have gone away. It may be that all along the NFS problems on the client just coincided = with Poudriere runs on the server. I build custom packages for my local = machines using Poudriere so I use it quite a lot. Maybe the Poudriere = port should come with a warning at install to those using NFS that it = may provoke disruption and suggest the addition of "-S"? = (Alternatively, maybe "-S" could become a default for mountd_flags? Is = there a downside from using it that means making it a default option is = unsuitable?) Anyway, many, many thanks for all the help, Rick. I'll keep monitoring = my BeagleBone Black, but it looks for now that this has solved the NFS = "instability." Cheers, Paul. From owner-freebsd-arm@freebsd.org Thu Mar 10 19:14:04 2016 Return-Path: Delivered-To: freebsd-arm@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 B1FB4ACA3BD for ; Thu, 10 Mar 2016 19:14:04 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (pb-sasl0.int.icgroup.com [208.72.237.25]) (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 842DA383 for ; Thu, 10 Mar 2016 19:14:03 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id 3A96049883 for ; Thu, 10 Mar 2016 14:14:02 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date :message-id:from:to:subject:mime-version:content-type :content-transfer-encoding; s=sasl; bh=aWRdy+Enqtr1TPP/L+Oasynvo vE=; b=j0iux95j/JtyF6y4i50iJRg5KKPXcSJ9TrC7JIMyaYa3rMzt4liow/ofS eZD2WQyZmQZsavXQHW2RJ/YT2RqZ/sFPJRXWsyDryVFQ+S4sZxDis2mwa8W2y04t MzfQ87wqjOlvrfrA8QmvCaan/ns13MMDzcfJfM/FABewXsKRXk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:message-id :from:to:subject:mime-version:content-type :content-transfer-encoding; q=dns; s=sasl; b=vI5XoSSTvtjHW7wt7JV Hy8IqfPw+OpXBlm7QwI8BIHCI/vjlwejTCZUMyBjSPtXhMc/Ds9mnj3N8Y6qLon7 70Bk8abuzBM09cjd5wSMl9IhSRapyT/eYFy7TLFVpNt81cJGXi9eD6Lu4kPFj1yt o2wCbjb4nujzYh0NAGJ3TDZY= Received: from pb-sasl0.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id F103049882 for ; Thu, 10 Mar 2016 14:14:01 -0500 (EST) Received: from bmach.nederware.nl (unknown [27.252.226.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-sasl0.pobox.com (Postfix) with ESMTPSA id AFB624987F for ; Thu, 10 Mar 2016 14:14:00 -0500 (EST) Received: from bonobo.nederware.nl (bonobo.nederware.nl [192.168.33.4]) by bmach.nederware.nl (Postfix) with ESMTP id 998253FAA2 for ; Fri, 11 Mar 2016 08:13:58 +1300 (NZDT) Received: from bonobo.nederware.nl (localhost [127.0.0.1]) by bonobo.nederware.nl (Postfix) with ESMTP id 83A961981434 for ; Fri, 11 Mar 2016 08:13:58 +1300 (NZDT) Date: Fri, 11 Mar 2016 08:13:58 +1300 Message-ID: <87io0u16yx.wl-berend@pobox.com> From: Berend de Boer To: freebsd-arm@freebsd.org Subject: FreeBSD-11.0-CURRENT-arm-armv6-RPI-B-20160308-r296485 not booting on Raspberry Pi A+ User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Mar_11_08:13:58_2016-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 3EF5DF10-E6F4-11E5-BE46-3C811E2D4245-48001098!pb-sasl0.pobox.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 19:14:04 -0000 --pgp-sign-Multipart_Fri_Mar_11_08:13:58_2016-1 Content-Type: text/plain; format=flowed; charset=US-ASCII Hi All, Previous version booted fine, FreeBSD-11.0-CURRENT-arm-armv6-RPI-B-20160308-r296485 doesn't. Seems it tries to load the bootloader, and then reboots immediately, something like that, goes pretty quick. -- All the best, Berend de Boer --pgp-sign-Multipart_Fri_Mar_11_08:13:58_2016-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit Content-Description: OpenPGP Digital Signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJW4cd2AAoJEKOfeD48G3g5Xn4QAKpf/S1H4dnLX5nC0CGXLsQU p5eVbGZlERPweFdvVewI8t21p44WQNDi4cCQevR/0EACOL0Ea3Ox7tvvg95Ctk7S OBgfz3e82DpzRBmkrKIv5eramvg8zPIcMX6IXbpbYu12cSZQr0//A+gUrTxbjPP8 zhFsH9qOrSpx1b1UmnEz9mz/0ZgtWS2dz6bM6ONFTOKTAjlVMolwBo7cAG913ma9 j5+33YeCotovPgzzv6lu+hJp6+DgiBMlewfqPjWMXAivPHjUla6dtDZCpBPILu7o HJGlgIb4ypyKXAKGQJK8mXOOTjiGhbxrK0OYvtWAKN9d61VmWkV4RcIdfKjWpEF5 axPwj5cGvsKWbM3j16SJhEJtr/fsbsqeDkjw/+zKz6jwiZaKHESmXq5pO/FEnaoX 4WcnzMhBlF8YII9fwXAhZ+FYjEvs6WdB+nyNCMSGslaOiR/0EuYi1tEbqqurI523 I+bVkpSy1zqztz2Bg6FNQcSz4jVnDlnTkYUgqXeqU4yHVWUKFgPPARo54LmDv5BK dSdjuKMwYbZ4y4RsWUVz0ZqwnOrJeCh/03sKz4EQtOTraT3L4BkrvGt6VuWMPkvv PsC1jQqtr4NF3sP5LLiH5N257y7w0azuwGrAdtGXCTju5K8CuNM/b5oPAQ1/tmuy sqmhR0s0UbJSpMQV1JlV =VvHC -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Mar_11_08:13:58_2016-1-- From owner-freebsd-arm@freebsd.org Thu Mar 10 19:16:25 2016 Return-Path: Delivered-To: freebsd-arm@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 2A44CACA4A3 for ; Thu, 10 Mar 2016 19:16:25 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (pb-sasl0.int.icgroup.com [208.72.237.25]) (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 F1DC1650 for ; Thu, 10 Mar 2016 19:16:24 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id 4562B498D0 for ; Thu, 10 Mar 2016 14:16:23 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date :message-id:from:to:subject:mime-version:content-type :content-transfer-encoding; s=sasl; bh=NINMnD0I+PmjHCy70xXx7Yjhb xk=; b=UQuhKtN7HGlVtaxuSOFkaZ5xdN03QMspe4ZVM5rjgx1Ud4IFJbs6swdV6 H2J1OJPJTOdvhFitYwy2dAFq4UDvTU1NGOwtfNpa8H/fDgYdDzQ0gQUoDJBDquZT Rdie75e4YSdRmSb3MiW2WswjmtM0FOzFhdU3QnqOPIyyKVVKVw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:message-id :from:to:subject:mime-version:content-type :content-transfer-encoding; q=dns; s=sasl; b=ucEyMUIymVUFLTH5eLv dYzid+NjWpu8Hv6GnA/zwP3Z2W/AJR7uT85T9emab6NcpAxNV1eUzWDj00IIx9ln ExGIgxR1mWD8ST3a7AtXVPU5bYwiVII84EGcKAuK+07qMxKmOlk4331OQxlweXCM peEs2tcnJcb0N2gbGUbdeoVU= Received: from pb-sasl0.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id 3B683498CD for ; Thu, 10 Mar 2016 14:16:23 -0500 (EST) Received: from bmach.nederware.nl (unknown [27.252.226.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-sasl0.pobox.com (Postfix) with ESMTPSA id B2A29498CC for ; Thu, 10 Mar 2016 14:16:22 -0500 (EST) Received: from bonobo.nederware.nl (bonobo.nederware.nl [192.168.33.4]) by bmach.nederware.nl (Postfix) with ESMTP id 99ED43FAA7 for ; Fri, 11 Mar 2016 08:16:20 +1300 (NZDT) Received: from bonobo.nederware.nl (localhost [127.0.0.1]) by bonobo.nederware.nl (Postfix) with ESMTP id 813C41981434 for ; Fri, 11 Mar 2016 08:16:20 +1300 (NZDT) Date: Fri, 11 Mar 2016 08:16:20 +1300 Message-ID: <87fuvy16uz.wl-berend@pobox.com> From: Berend de Boer To: freebsd-arm@freebsd.org Subject: RT5390 support on Raspberry Pi A+ User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Mar_11_08:16:20_2016-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 939A2BB6-E6F4-11E5-9880-3C811E2D4245-48001098!pb-sasl0.pobox.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 19:16:25 -0000 --pgp-sign-Multipart_Fri_Mar_11_08:16:20_2016-1 Content-Type: text/plain; format=flowed; charset=US-ASCII Hi All, RT5390 was supposedly added in 2015, but FreeBSD 11-CURRENT doesn't seem to recognise this well. Anyone having luck with this? I have it on a very tiny USB stick. Unit is recognised by name, but no device is added. -- All the best, Berend de Boer --pgp-sign-Multipart_Fri_Mar_11_08:16:20_2016-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit Content-Description: OpenPGP Digital Signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJW4cgEAAoJEKOfeD48G3g5EQ4QAMkFSQaBo3XEetR4NymFzt9x 9lp9C0ui2qiudkmQBidFcgNv8mlmfn+4UaA2pAdzGZ1tcdGBeaxHZCfLyJfT/zww mmZNNq9H5O14DpcoS9gorUUHSjSqgRJjYdsq46u6/4OtDsuo9qxTBYdQM4OOGr2o vqcXTEBiHWoD0U5lY1/hCK2m0tMCgNK6vg6npvNBgsCe9mnQnOAPw7E/DmVE4mDI E1CCSYxZBvf1Fr2pJz6+1pRpZABc2LmhNwqJr3TT7pZfdkpSQVSZlEpBaKWv/xYu lJMsb4XKrrG8Jb50uCJf+6sHrzyr7ggHqS9lUfQIbVymwyjL1xIdQQjRM2DU7Vpr cn6AWi7ppsu0JaYOa7tknDDit3Hs8Z2lwuayn8VgY2EM9gCJfwQ7yILHXlyF3Rl0 iLQtDeHqnruYHCNIJzY4T0sg/41ozYuJOPfFIJ559XFOeo2CIialq6uRwU2zUEis hbU7PhRQeiRgFseQ7OO9KqnZ+qkRPcuJLVIq3ZGriDJ9UX0uxHMor/UBd91ku/et 7SOkgelLv0wOS31mWi6xWGLu+u0X0UALAuLJPu/lvYGtmE9z7qs20Sv0lBLaqRew vB9l0kKwtf5sLfmlB0Pvs5KDPYhJDLdeufOzT7G5jumCQG/tncmRD5BEAObsdQTm vK1Yv2uFsay/3kw8w32f =yLZQ -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Mar_11_08:16:20_2016-1-- From owner-freebsd-arm@freebsd.org Thu Mar 10 20:19:31 2016 Return-Path: Delivered-To: freebsd-arm@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 50C73ACB8FA for ; Thu, 10 Mar 2016 20:19:31 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (pb-sasl0.int.icgroup.com [208.72.237.25]) (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 119B9783 for ; Thu, 10 Mar 2016 20:19:30 +0000 (UTC) (envelope-from berend@pobox.com) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id 7C5F949E59 for ; Thu, 10 Mar 2016 15:19:28 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date :message-id:from:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=PIUdxeY+DMKH 9bmcjoMsPJeWESU=; b=B15RaVyf1VOf8OR5sGVaUYistfK95OvgS7lmLdrp4z1L Din9lZzceA+7KLqQY1xLaxQt0+NZXvzBHJOMdXL+2s/jePnDCs0HAX6IsVRcyP/S ywuCqF0JpzISVMBxpBTTnV8IL7SYRsAtXfojkn8L09Gi+mAyMSEIlbw0xRjt7Ec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:message-id :from:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=lTzxs0 94l+jKyTd5imCZK9WnY+prJi+O4Oh0ZPlhQqb7LJPoEmbrYqcscsG8F4aJRLEElr CbTco5wxEngmiNTYSrYAEmlCgszCcpw8d3U+aYrZXxz9Uud4G772CzSshIwgpdTE 0axcoOYNAYTpdFEddc8eGd4LNcIeFys79AYAM= Received: from pb-sasl0.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl0.pobox.com (Postfix) with ESMTP id 73AA149E58 for ; Thu, 10 Mar 2016 15:19:28 -0500 (EST) Received: from bmach.nederware.nl (unknown [27.252.226.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-sasl0.pobox.com (Postfix) with ESMTPSA id DF5A449E57 for ; Thu, 10 Mar 2016 15:19:27 -0500 (EST) Received: from bonobo.nederware.nl (bonobo.nederware.nl [192.168.33.4]) by bmach.nederware.nl (Postfix) with ESMTP id 4C76E40193 for ; Fri, 11 Mar 2016 09:19:25 +1300 (NZDT) Received: from bonobo.nederware.nl (localhost [127.0.0.1]) by bonobo.nederware.nl (Postfix) with ESMTP id 32CAB1981434 for ; Fri, 11 Mar 2016 09:19:25 +1300 (NZDT) Date: Fri, 11 Mar 2016 09:19:25 +1300 Message-ID: <87egbi13xu.wl-berend@pobox.com> From: Berend de Boer To: freebsd-arm@freebsd.org Subject: Re: RT5390 support on Raspberry Pi A+ In-Reply-To: <87fuvy16uz.wl-berend@pobox.com> References: <87fuvy16uz.wl-berend@pobox.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Mar_11_09:19:24_2016-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 63BF35FE-E6FD-11E5-B9DB-3C811E2D4245-48001098!pb-sasl0.pobox.com X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 20:19:31 -0000 --pgp-sign-Multipart_Fri_Mar_11_09:19:24_2016-1 Content-Type: text/plain; format=flowed; charset=US-ASCII >>>>> "Berend" == Berend de Boer writes: Berend> RT5390 was supposedly added in 2015, but FreeBSD Berend> 11-CURRENT doesn't seem to recognise this well. Anyone Berend> having luck with this? Tried FreeBSD 10.3, initially didn't work, but I got a bit furterh after loading if_run, always read the manual it seems. Next step will be to get the wifi actually working. -- All the best, Berend de Boer --pgp-sign-Multipart_Fri_Mar_11_09:19:24_2016-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit Content-Description: OpenPGP Digital Signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJW4dbMAAoJEKOfeD48G3g5BDQQAJ3TQw5eIrh7/8YfBR0zewGq eUBYsm4thGHiJkyVBnwyiwmIcxghNMJMTmLR4Kza8UPwpl0VmoKS2wiGUK3f5afO uVyna6/Tx8R4xI9Tra/Xd+2JMx6i39F+dFUztwU7TQCK1f4Y67poBeJv2eHfOmap neB9IPTZebiR5tk7sKaf8yw/Jl7bGUVoKp2VF/tUeZAmhU+TR/IgwXb686Ttpbm2 uhWfWlPANXdxiOMga3YSk7Djmq85wK/iGVzix4rCWn0gcNR+3JZUhVhHoc3h8N9F +lckG/pFQGYKhOL/x96mb0r08ZEFphvg2KTSE2Q+myE8ra0Wfx4GqYUdffbnZBpG Mgh1mw2WHWI4GInO0vXpn4eqJwW6V0IB4ea8s++LvS3J5EZi7wXObKQHtKeEtgRP vu6E43bR/a8adPHfdQLaUegwJ6HDtzyHD7vY6sOnLKcqlT1JuNb1scmIR77PwnRX pUnKgrtXzr6QRjUFJSVLLcvuxCawEIfsdgQPvT4Uu63UPWnkNqaL/JFnX08GUBfF xKStHUIEe+Shx7hKedmqKeBh4pS5bvq5DSqS0sveKADuxkNixM6APwgaPNclynf9 RS3e1XU/R1mbUhld7SzJ9zoR5DlrsqjbfSIgLVSy/poNsEeOIZYB/nbBCcfOt86F DXLqIwdBrRTU8YQxSgVw =eqmP -----END PGP SIGNATURE----- --pgp-sign-Multipart_Fri_Mar_11_09:19:24_2016-1-- From owner-freebsd-arm@freebsd.org Fri Mar 11 01:08:20 2016 Return-Path: Delivered-To: freebsd-arm@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 978FAACA62B; Fri, 11 Mar 2016 01:08:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1D5E2B0C; Fri, 11 Mar 2016 01:08:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:fqt3Eh14f65UqSW0smDT+DRfVm0co7zxezQtwd8ZsegeKvad9pjvdHbS+e9qxAeQG96LtLQU26GP7P+ocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWM5DIfUi/yKRBybrysXNWC0ILnh6vrpMKbSj4LrQT+SIs6FA+xowTVu5teqqpZAYF19CH0pGBVcf9d32JiKAHbtR/94sCt4MwrqHwI6LoJvvRNWqTifqk+UacQTHF/azh0t4XXskz7RBaLrl4VTmUbiFIcGwHY6Dn1RJD0sze8uu580m+EIYv7Qa1iChq46KI+ch7ji28iPjU69GzSwphqiatQoxasojRixIHJbYWNNLx1d/WOLpshWWNdU5MJBGR6CYSmYt5KVrJZMA== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DOAQCNGeJW/61jaINeDoRvBrgOghMBDYFthg8CgXgUAQEBAQEBAQFjJ4ItghQBAQEDASMEUgULAgEIGAICDRkCAlcCBBMbiAEIrkmPIQEBAQEBBQEBAQEBG3yFHIF7gkeEIhaDAoE6BYdYAoVadD2IWIhcB4Z8h2yFL4YCiGgCHgEBQoIDGYENWR4uAYkVIwEZfgEBAQ X-IronPort-AV: E=Sophos;i="5.24,318,1454994000"; d="scan'208";a="270314578" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 10 Mar 2016 20:08:12 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 6493415F55D; Thu, 10 Mar 2016 20:08:12 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id jwyDUfK0fRdY; Thu, 10 Mar 2016 20:08:11 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 587A615F56D; Thu, 10 Mar 2016 20:08:11 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4PskEHakYHaR; Thu, 10 Mar 2016 20:08:11 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 39A4615F55D; Thu, 10 Mar 2016 20:08:11 -0500 (EST) Date: Thu, 10 Mar 2016 20:08:10 -0500 (EST) From: Rick Macklem To: Paul Mather Cc: Ronald Klop , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Message-ID: <2136530467.13386220.1457658490896.JavaMail.zimbra@uoguelph.ca> In-Reply-To: References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> <1482595660.8940439.1457405756110.JavaMail.zimbra@uoguelph.ca> <08710728-3130-49BE-8BD7-AFE85A31C633@gromit.dlib.vt.edu> <1290552239.10146172.1457484570450.JavaMail.zimbra@uoguelph.ca> <60E8006A-F0A8-4284-839E-882FAD7E6A55@gromit.dlib.vt.edu> <508973676.11871738.1457575196588.JavaMail.zimbra@uoguelph.ca> Subject: Re: Unstable NFS on recent CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191) Thread-Topic: Unstable NFS on recent CURRENT Thread-Index: vkg/rK143TXd6S6nj595PPG46ZJutA== X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 01:08:20 -0000 Paul Mather wrote: > On Mar 9, 2016, at 8:59 PM, Rick Macklem wrote: > > > Paul Mather wrote: > >> On Mar 8, 2016, at 7:49 PM, Rick Macklem wrote: > >> > >>> Paul Mather wrote: > >>>> On Mar 7, 2016, at 9:55 PM, Rick Macklem wrote: > >>>> > >>>>> Paul Mather (forwarded by Ronald Klop) wrote: > >>>>>> On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather > >>>>>> > >>>>>> wrote: > >>>>>> > >>>>>>> On my BeagleBone Black running 11-CURRENT (r296162) lately I have > >>>>>>> been > >>>>>>> having trouble with NFS. I have been doing a buildworld and > >>>>>>> buildkernel > >>>>>>> with /usr/src and /usr/obj mounted via NFS. Recently, this process > >>>>>>> has > >>>>>>> resulted in the buildworld failing at some point, with a variety of > >>>>>>> errors (Segmentation fault; Permission denied; etc.). Even a "ls > >>>>>>> -alR" > >>>>>>> of /usr/src doesn't manage to complete. It errors out thus: > >>>>>>> > >>>>>>> ===== > >>>>>>> [[...]] > >>>>>>> total 0 > >>>>>>> ls: ./.svn/pristine/fe: Permission denied > >>>>>>> > >>>>>>> ./.svn/pristine/ff: > >>>>>>> total 0 > >>>>>>> ls: ./.svn/pristine/ff: Permission denied > >>>>>>> ls: fts_read: Permission denied > >>>>>>> ===== > >>>>>>> > >>>>>>> On the console, I get the following: > >>>>>>> > >>>>>>> newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > >>>>>>> 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > >>>>>>> MIDDLEWARE) > >>>>>>> > >>> Oh, I had forgotten this. Here's the comment related to this error. > >>> (about line#445 in sys/fs/nfsclient/nfs_clport.c): > >>> 446 * BROKEN NFS SERVER OR MIDDLEWARE > >>> 447 * > >>> 448 * Certain NFS servers (certain old proprietary > >>> filers > >>> ca. > >>> 449 * 2006) or broken middleboxes (e.g. WAN accelerator > >>> products) > >>> 450 * will respond to GETATTR requests with results for > >>> a > >>> 451 * different fileid. > >>> 452 * > >>> 453 * The WAN accelerator we've observed not only > >>> serves > >>> stale > >>> 454 * cache results for a given file, it also > >>> occasionally serves > >>> 455 * results for wholly different files. This causes > >>> surprising > >>> 456 * problems; for example the cached size attribute > >>> of > >>> a file > >>> 457 * may truncate down and then back up, resulting in > >>> zero > >>> 458 * regions in file contents read by applications. > >>> We > >>> observed > >>> 459 * this reliably with Clang and .c files during > >>> parallel build. > >>> 460 * A pcap revealed packet fragmentation and GETATTR > >>> RPC > >>> 461 * responses with wholly wrong fileids. > >>> > >>> If you can connect the client->server with a simple switch (or just an > >>> RJ45 > >>> cable), it > >>> might be worth testing that way. (I don't recall the name of the > >>> middleware > >>> product, but > >>> I think it was shipped by one of the major switch vendors. I also don't > >>> know if the product > >>> supports NFSv4?) > >>> > >>> rick > >> > >> > >> Currently, the client is connected to the server via a dumb gigabit > >> switch, > >> so it is already fairly direct. > >> > >> As for the above error, it appeared on the console only once. (Sorry if I > >> made it sound like it appears every time.) > >> > >> I just tried another buildworld attempt via NFS and it failed again. This > >> time, I get this on the BeagleBone Black console: > >> > >> nfs_getpages: error 13 > >> vm_fault: pager read error, pid 5401 (install) > >> > > 13 is EACCES and could be caused by what I mention below. (Any mount of a > > file > > system on the server unless "-S" is specified as a flag for mountd.) > > > >> > >> The other thing I have noticed is that if I induce heavy load on the NFS > >> server---e.g., by starting a Poudriere bulk build---then that provokes the > >> client to crash much more readily. For example, I started a NFS > >> buildworld > >> on the BeagleBone Black, and it seemed to be chugging along nicely. The > >> moment I kicked off a Poudriere build update of my packages on the NFS > >> server, it crashed the buildworld on the NFS client. > >> > > Try adding "-S" to mountd_flags on the server. Any time file systems are > > mounted > > (and Poudriere likes to do that, I am told), mount sends a SIGHUP to mountd > > to > > reload /etc/exports. When /etc/exports are being reloaded, there will be > > access > > errors for mounts (that are temporarily not exported) unless you specify > > "-S" > > (which makes mountd suspend the nfsd threads during the reload of > > /etc/exports). > > > > rick > > > Bingo! I think we may have a winner. I added that flag to mountd_flags on > the server and the "instability" appears to have gone away. > > It may be that all along the NFS problems on the client just coincided with > Poudriere runs on the server. I build custom packages for my local machines > using Poudriere so I use it quite a lot. Maybe the Poudriere port should > come with a warning at install to those using NFS that it may provoke > disruption and suggest the addition of "-S"? (Alternatively, maybe "-S" > could become a default for mountd_flags? Is there a downside from using it > that means making it a default option is unsuitable?) > Well, the first time I proposed "-S" the collective felt it wasn't the appropriate solution to the "export reload" problem. The second time, the "collective" agreed that it was ok as a non-default option. (Part of this story was an alternative to mountd called nfse which did update exports atomically, but it never made it into FreeBSD.) The only downside to making it a default is that it does change behaviour and some might consider that a POLA violation. Others would consider it just a bug fix. There was one report of long delays before exports got updated on a very busy server. (I have a one line patch that fixes this, but that won't be committed into FreeBSD-current until April.) Now that "-S" has been in FreeBSD for a couple of years, I am planning on asking the "collective" (I usually post these kind of things on freebsd-fs@) to make it the default in FreeBSD-current, because this problem seems to crop up fairly frequently. I will probably post w.r.t. this in April when I can again to svn commits. I only recently found out the Poudriere does mounts and causes this problem. I may also commit a man page update (which can be MFC'd) that mentions if you are using Poudriere you want this flag. Having the same thing mentioned in the Poudriere port install might be nice, too. Thanks for testing this, rick > Anyway, many, many thanks for all the help, Rick. I'll keep monitoring my > BeagleBone Black, but it looks for now that this has solved the NFS > "instability." > > Cheers, > > Paul. > > From owner-freebsd-arm@freebsd.org Fri Mar 11 04:30:44 2016 Return-Path: Delivered-To: freebsd-arm@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 7718DACA82D for ; Fri, 11 Mar 2016 04:30:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::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 4B577813 for ; Fri, 11 Mar 2016 04:30:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ig0-x22c.google.com with SMTP id ig19so1789033igb.1 for ; Thu, 10 Mar 2016 20:30:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:date:message-id:subject:from:to; bh=OjIvpUQfNodcV7JZYGjjITVJT9uI0Q57WGghBXNDQNU=; b=Wf36hKHamqkOKI7dKtC/UpaqWv12a8JKWAQqETdDbC8e+mf5auUXeNFKaI+GzAkBRw lE1D12iyeK1WOlJ6aH5whBvWqxs5KxJ+vWK274VtpT7CPAyiwODXavAnmaPrezOxkCbj Gez0ab6Ms5dOGh/I2BuQC5YwoPvockirHgeOT/M7G3BpCgJmUjT/uYWLX9Y2GzVbftT9 uVmYPpltkXAK+/WlwbU5mi47c6E1XYK7Gm1GtlI4IGapp3GYiIFo2RGwo2QWohfJR50Q DwIwi1DD0hzuaqOCsg8Onivn4ne99Pg1xDwx6/bzziC2HJLUNJkBpSDAIRw7gXapaJQ3 9FnA== 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:date:message-id:subject:from :to; bh=OjIvpUQfNodcV7JZYGjjITVJT9uI0Q57WGghBXNDQNU=; b=aqXA4va6XJq7CL5njM44JR3RretVdKPkcc+SjjnIDh2VpcNumwMZ41dKdIF5mRWZNj nHHA8XNEhj4fDfCz2pwNynkM+5Atj72dK74+gy7JxUF/a7bySYDNs2Xhgzy4hbr45SNX XUKY+ojz6CbeeslsB7KDSV7t0Rk8RNSFaQkU9+F5tdFRACBu5GTNMil5AwCxZqo9lKf0 F1ux/1/aJ2YI+J+lba+5mDUFyMd/k8XT2kfBzjCMJ4QHxUyP+FYSGzyGLmMVXj8mE3TL iUtOcLZzFICDdEYjvC1IbpecjHtSxbLc0xapsfT7js5nZwv/Jwf5sq9vcmUpza5vehZd dgxQ== X-Gm-Message-State: AD7BkJIf4WX6JmkG11X9OPCiLsOJXw1XVaazL1fITSaFP+XhDmMWWtbC/H/0IRo++Y+G+e4+/sp8tG6R1u1v1w== MIME-Version: 1.0 X-Received: by 10.50.30.134 with SMTP id s6mr504077igh.36.1457670643348; Thu, 10 Mar 2016 20:30:43 -0800 (PST) Sender: wlosh@bsdimp.com Received: by 10.36.65.230 with HTTP; Thu, 10 Mar 2016 20:30:43 -0800 (PST) X-Originating-IP: [50.253.99.174] Date: Thu, 10 Mar 2016 21:30:43 -0700 X-Google-Sender-Auth: 2BD-HJ0wwFZZyEfveSH47DIc3oE Message-ID: Subject: Hard float API to become default on ARMv6 April 2nd From: Warner Losh To: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 04:30:44 -0000 If all goes well, I plan on pulling the trigger to switch armv6 to hard float API from its current hard float with soft-float API it's using. If you are running armv4 or armv5 hardware, then you are unaffected. If you are running arm64 / aarch64, you are unaffected. You're unaffected if you are on any other architecture. A couple of Anticipated FAQs: Q: Where can I find this so I can test it? It's currently in review. https://reviews.freebsd.org/D5550 is what I plan to commit if all goes well April 2nd. Q: What about the upgrade path? The plan is that people that need to upgrade their system in place can do so, but they will have to build compat libraries. This is part of buildworld / installworld when WITH_LIBSOFT is set to y. Changes made to ld.so a long time ago will know if you are executing a hardfloat ABI or softfloat ABI binary (which uses hard float instructions). When you run a hard float binary after the change, it will grab the libraries from the default locations in the tree. When you run a soft float binary, it will grab the libraries from /libsoft /usr/libsoft. The same kernel can run both flavors of binaries. Q: So how do I generate the compat libraries? You can do this with a buildworld / installworld with WITH_LIBSOFT=y. However, you'll need https://reviews.freebsd.org/D5605 applied to the tree. This will also be committed April 2nd. Q: What about packages? pkg(8) will notice that you've upgraded ABIs and will refresh all packages from the repo. Q: But there's no packages at the moment, what gives? Yes, part of the reason to give 3 weeks notice is to allow time for these packages to be built, as well as give a chance for wider testing before the trigger is pulled. Q: What will happen to the armv6hf TARGET_ARCH? It will go away. Since the default armv6 target now uses that ABI, there's no need for a new one. Since this was never released, we don't have to worry about it. If we wanted the best performance, we'd have to have moved to a new name. But the new name would cause more problems than moving to the new ABI with the old ABI supported through proper shims. It made little sense to obsolete / deprecate armv6 and move to armv6hf in FreeBSD 11. We'd likely have needed two sets of packages, there'd be longer make universe times, etc for the whole life of FreeBSD 11. So we're only going to have one, and it will be the higher performing hard float ABI. It turns out there's almost no performance gain for most things (though floating point intensive applications benefit marginally). There's a much bigger gain from generating code for your particular ARM core. Much work has been done to make this work (it didn't before, due to a number of bugs that have been fixed). This change has been discussed and socialized since last summer. Most of the main arm developers are on board (though there is one notable exception) with this transition plan. This has been reported in quarterly reports, as well as disclosed on arm@ a few times over the past year. I had hoped to be sending this message with a July 1st, 2015 cut-over date, but time got away from me a bit. Q: But what if I need to build a system with soft float ABI under 11? You can still do that. CPUTYPE=soft has been created for this scenario, as well as to generate libraries for WITH_LIBSOFT. It's anticipated that this will live for the entire FreeBSD 11 branch, but go away in FreeBSD 12. Q: What about compat10 binaries for ARM? Those won't be provided in any flavor. While arm has reached Tier 1 status in FreeBSD 11, it was not Tier 1 status in FreeBSD 10, so there's no need to generate them as part of project. It's anticipated the demand for these will be quite light. Q: What if I want to run a hard float ABI system, but still use soft-float packages for a while? This isn't supported, and little testing has been done here. You may be able to move the shared libraries in the libsoft LD_LIBRARY_PATH and/or just keep the default paths in the libsoft loads. However, this is an untenable situation once you upgrade one of the binaries. In fact, they will all be upgraded by pkg(8) the first time it runs and notices /bin/sh has a different ABI. Q: Is there a wiki for this change? https://wiki.freebsd.org/FreeBSD/arm/hardabi contains a start (this message), but will be updated over time to reflect the current status. Warner From owner-freebsd-arm@freebsd.org Fri Mar 11 05:57:51 2016 Return-Path: Delivered-To: freebsd-arm@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 A0ED9ACC4B7 for ; Fri, 11 Mar 2016 05:57:51 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 84A9DBA5; Fri, 11 Mar 2016 05:57:51 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id DB5591101; Fri, 11 Mar 2016 05:57:51 +0000 (UTC) Date: Fri, 11 Mar 2016 05:57:51 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: np@FreeBSD.org, imp@FreeBSD.org, bdrewery@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <2119214909.3.1457675871822.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2578 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 05:57:51 -0000 FreeBSD_HEAD_arm64 - Build #2578 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2578/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2578/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2578/console Change summaries: 296647 by bdrewery: Use the new bmake .dinclude feature to make these safe. At least FAST_DEPEND won't even run 'make depend', so the code was potentially broken with FAST_DEPEND anyhow. The .dinclude directive will ignore missing files rather than make them be fatal. Sponsored by: EMC / Isilon Storage Division 296646 by bdrewery: FAST_DEPEND: Use .dinclude to enable full .depend logic in bmake. The inclusion of .MAKE.DEPENDFILE (.depend) has special logic in make to ignore stale/missing dependencies. bmake 20160220 added a '.dinclude' directive that uses the special logic for .depend when including the file. This fixes a build error when a file is moved or deleted that exists in a .depend.OBJ file. This happened in r292782 when sha512c.c "moved" and an incremental build of lib/libmd would fail with: make: don't know how to make /usr/src/lib/libcrypt/../libmd/sha512c.c. Stop Now this will just be seen as a stale dependency and cause a rebuild: make: /usr/obj/usr/src/lib/libmd/.depend.sha512c.o, 13: ignoring stale .depend for /usr/src/lib/libcrypt/../libmd/sha512c.c --- sha512c.o --- ... This rebuild will only be done once since the .depend.sha512c.o will be updated on the build with the -MF flags. This also removes -MP being passed for the .depend.OBJ generation (which would create fake targets for system headers) since the logic is no longer needed to protect from missing files. Sponsored by: EMC / Isilon Storage Division 296645 by bdrewery: Fix bmake upgrade NO_MAN warnings. MFC after: 1 week Sponsored by: EMC / Isilon Storage Division 296644 by bdrewery: Fix upgrade of bmake by not setting conflicting MAKE_VERSION. This may be used in later checks, such as in bsd.dep.mk, to enable features that rely on the built-in value. Sponsored by: EMC / Isilon Storage Division 296643 by bdrewery: Fix make -n upgrade_checks. MFC after: 1 week Sponsored by: EMC / Isilon Storage Division 296642 by imp: Factor out lib32 generation to its own file. This is prep for a similar Makefile.libsoft which will do the same for armv6 soft fp API libraries in prep for pulling the trigger on moving to armv6 hard float. Once there's two files, I'll work with bdrewery@ to merge the two files as they are mostly the same. The high rate of churn for Makefile* makes it quite difficult to make progress out of tree. Differential Review: https://reviews.freebsd.org/D5566 296641 by np: cxgbe(4): Add sysctls to display the TP microcode version and the expansion rom version (if there's one). trantor:~# sysctl dev.t4nex dev.t5nex | grep _version dev.t4nex.0.firmware_version: 1.15.28.0 dev.t4nex.0.tp_version: 0.1.9.4 dev.t5nex.0.firmware_version: 1.15.28.0 dev.t5nex.0.exprom_version: 1.0.0.68 dev.t5nex.0.tp_version: 0.1.4.9 296640 by np: cxgbe(4): Add a sysctl for the event capture mask of the TP block's logic analyzer. dev.t5nex..misc.tp_la_mask dev.t4nex..misc.tp_la_mask The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T05:55:06.519 +0000' U lib/clang/clang.build.mk U Makefile U share/mk/bsd.dep.mk U sys/conf/kern.post.mk U sys/dev/cxgbe/adapter.h U sys/dev/cxgbe/common/common.h U sys/dev/cxgbe/t4_main.c U usr.bin/bmake/Makefile U Makefile.inc1 AU Makefile.lib32 At revision 296647 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson6713370823925990356.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson5833273572120179487.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2578 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2578 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2578 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2578 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2578/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296647 SVN_REVISION_1=296647 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=4ddd6364-f93f-4402-8edb-8ad31b1648f3 BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson1494336075308372381.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 480: MK_MAN can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson5797224716980787936.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 07:56:02 2016 Return-Path: Delivered-To: freebsd-arm@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 B1A9AACB24C for ; Fri, 11 Mar 2016 07:56:02 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 96467BC6; Fri, 11 Mar 2016 07:56:02 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id E8C2D1159; Fri, 11 Mar 2016 07:56:02 +0000 (UTC) Date: Fri, 11 Mar 2016 07:56:02 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: ak@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <314996533.7.1457682962841.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <2119214909.3.1457675871822.JavaMail.jenkins@jenkins-9.freebsd.org> References: <2119214909.3.1457675871822.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2579 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 07:56:02 -0000 FreeBSD_HEAD_arm64 - Build #2579 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2579/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2579/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2579/console Change summaries: 296648 by ak: - Implement -T option to allow to specify a fs type for a vnode-backed memory disk - Rephrase -t option description (manpage) - Split long sentences (manpage) Differential Review: https://reviews.freebsd.org/D4394 Reviewed by: mav, wblock (manpage) Approved by: mav The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T07:55:01.410 +0000' U sbin/mdmfs/mdmfs.8 U sbin/mdmfs/mdmfs.c At revision 296648 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson5951524053121740341.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson3771902163758064557.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2579 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2579 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2579 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2579 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2579/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296648 SVN_REVISION_1=296648 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=2191f721-e759-4462-9a31-911fc058ec73 BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson8560789120438946315.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 480: MK_MAN can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson3950626898171889840.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 11:55:55 2016 Return-Path: Delivered-To: freebsd-arm@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 B0BC1ACB8A0 for ; Fri, 11 Mar 2016 11:55:55 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id A361AECC; Fri, 11 Mar 2016 11:55:55 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id B767B1216; Fri, 11 Mar 2016 11:55:55 +0000 (UTC) Date: Fri, 11 Mar 2016 11:55:55 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: des@FreeBSD.org, kib@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <618405419.11.1457697355691.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <314996533.7.1457682962841.JavaMail.jenkins@jenkins-9.freebsd.org> References: <314996533.7.1457682962841.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2580 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 11:55:55 -0000 FreeBSD_HEAD_arm64 - Build #2580 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2580/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2580/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2580/console Change summaries: 296652 by kib: Do not perform unneccessary shared recursion on the allproc_lock in pfs_visible(). The recursion does not cause deadlock because the sx implementation does not prefer exclusive waiters over the shared, but this is an implementation detail. Reported by: pho, Matthew Bryan Reviewed by: jhb Tested by: pho Approved by: des (pseudofs maintainer) Sponsored by: The FreeBSD Foundation MFC after: 2 weeks 296651 by des: Define __bounded__ to fix the gcc build. While there, raise WARNS. The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T11:54:52.685 +0000' U sys/fs/pseudofs/pseudofs_vnops.c U lib/libpam/modules/pam_ssh/Makefile U lib/libpam/modules/pam_ssh/pam_ssh.c At revision 296652 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson3741972110583661474.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson6097976351506367385.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2580 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2580 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2580 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2580 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2580/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296652 SVN_REVISION_1=296652 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=83484af6-a146-473f-81ae-4cc24ff859f8 BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson5159717738091352859.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 480: MK_MAN can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson5069987234697460583.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 13:55:48 2016 Return-Path: Delivered-To: freebsd-arm@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 9FC20ACC379 for ; Fri, 11 Mar 2016 13:55:48 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 8299C1FC; Fri, 11 Mar 2016 13:55:48 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 8E73C1270; Fri, 11 Mar 2016 13:55:48 +0000 (UTC) Date: Fri, 11 Mar 2016 13:55:48 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: mav@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <1297913544.17.1457704548524.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <618405419.11.1457697355691.JavaMail.jenkins@jenkins-9.freebsd.org> References: <618405419.11.1457697355691.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2581 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 13:55:48 -0000 FreeBSD_HEAD_arm64 - Build #2581 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2581/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2581/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2581/console Change summaries: 296654 by mav: Use `geom disk list` instead `camcontrol identify`. The new way works for almost any disk, while the old only for ATA. MFC after: 2 weeks 296653 by mav: Allow standard commands for "unknown" classes in RESCUE mode. For example, it allows quite useful `geom disk list` command. MFC after: 1 week The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T13:54:47.111 +0000' U usr.sbin/pc-sysinstall/backend-query/disk-list.sh U sbin/geom/core/geom.c At revision 296654 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson3937101719783415182.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson2001525774509538852.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2581 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2581 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2581 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2581 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2581/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296654 SVN_REVISION_1=296654 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=d1a4e6be-f043-4dc9-9670-85238302062c BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson4508611489276650190.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 480: MK_MAN can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson6025793428251998460.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 15:55:48 2016 Return-Path: Delivered-To: freebsd-arm@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 1B38AACCC58 for ; Fri, 11 Mar 2016 15:55:48 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 0FFF8B00; Fri, 11 Mar 2016 15:55:48 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 352E012C8; Fri, 11 Mar 2016 15:55:48 +0000 (UTC) Date: Fri, 11 Mar 2016 15:55:47 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: des@FreeBSD.org, maxim@FreeBSD.org, mav@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <1752852354.21.1457711748159.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1297913544.17.1457704548524.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1297913544.17.1457704548524.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2582 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 15:55:48 -0000 FreeBSD_HEAD_arm64 - Build #2582 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/console Change summaries: 296661 by maxim: o Xr icmp(4). 296660 by maxim: o Document net.inet.icmp.maskfake and net.inet.icmp.tstamprepl sysctls. 296659 by des: Apply upstream r3651: the IPv6 address of the L root has changed. 296657 by des: Not ready for level 6 yet due to -Wredundant-decls. 296656 by mav: Don't bother to invoke gmirror or zpool if the module is not loaded. 296655 by mav: Unify and improve metadata wiping. MFC after: 2 weeks The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T15:54:45.454 +0000' U sbin/ping/ping.8 U contrib/unbound/iterator/iter_hints.c U contrib/unbound U lib/libpam/modules/pam_ssh/Makefile U usr.sbin/pc-sysinstall/backend/functions-disk.sh At revision 296661 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson17289639383039056.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson7185979869138372977.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2582 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2582 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2582 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2582 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296661 SVN_REVISION_1=296661 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=e678f1f4-2856-4f80-8bc2-7e08e16f3bb2 BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson8641967493662081032.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 480: MK_MAN can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson2625254228492794663.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 17:12:47 2016 Return-Path: Delivered-To: freebsd-arm@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 7BFC5ACB060 for ; Fri, 11 Mar 2016 17:12:47 +0000 (UTC) (envelope-from maxim@freebsd.org) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.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 0D0B289B; Fri, 11 Mar 2016 17:12:46 +0000 (UTC) (envelope-from maxim@freebsd.org) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.15.2/8.15.2) with ESMTP id u2BHCiqK083030; Fri, 11 Mar 2016 20:12:44 +0300 (MSK) (envelope-from maxim@freebsd.org) Date: Fri, 11 Mar 2016 20:12:44 +0300 (MSK) From: Maxim Konovalov To: jenkins-admin@FreeBSD.org cc: des@FreeBSD.org, mav@FreeBSD.org, freebsd-arm@FreeBSD.org Subject: Re: FreeBSD_HEAD_arm64 - Build #2582 - Still Failing In-Reply-To: <1752852354.21.1457711748159.JavaMail.jenkins@jenkins-9.freebsd.org> Message-ID: References: <1297913544.17.1457704548524.JavaMail.jenkins@jenkins-9.freebsd.org> <1752852354.21.1457711748159.JavaMail.jenkins@jenkins-9.freebsd.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 17:12:47 -0000 Hello, On Fri, 11 Mar 2016, 15:55-0000, jenkins-admin@FreeBSD.org wrote: > FreeBSD_HEAD_arm64 - Build #2582 - Still Failing: > > Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/ > Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/changes > Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2582/console > Is it really working these days? My build just finished ok: $ MAKEOBJDIRPREFIX=/home/maxim/obj make -j 16 buildworld TARGET=arm64 <...> >>> World build completed on Fri Mar 11 20:05:02 MSK 2016 -- Maxim Konovalov From owner-freebsd-arm@freebsd.org Fri Mar 11 17:55:41 2016 Return-Path: Delivered-To: freebsd-arm@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 9D699ACC564 for ; Fri, 11 Mar 2016 17:55:41 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 8FD6F1AC8; Fri, 11 Mar 2016 17:55:41 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id C2BED1321; Fri, 11 Mar 2016 17:55:41 +0000 (UTC) Date: Fri, 11 Mar 2016 17:55:40 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: emaste@FreeBSD.org, bdrewery@FreeBSD.org, dim@FreeBSD.org, mav@FreeBSD.org, maxim@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <1620451985.25.1457718941703.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1752852354.21.1457711748159.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1752852354.21.1457711748159.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2583 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 17:55:41 -0000 FreeBSD_HEAD_arm64 - Build #2583 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2583/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2583/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2583/console Change summaries: 296673 by mav: Oops, remove debugging forgotten in r296655. MFC after: 2 weeks 296672 by dim: In nvmecontrol, fix gcc warnings about the local 'power' variables shadowing a global declaration. 296671 by bdrewery: Revert r296645 as it breaks stable/10->head builds. 296670 by bdrewery: Regenerate 296669 by bdrewery: Add a WITHOUT_FAST_DEPEND 296668 by bdrewery: Enable FAST_DEPEND by default. Discussed on: arch Sponsored by: EMC / Isilon Storage Division 296663 by emaste: libdwarf: fix SHT_REL relocation processing Relocation of type SHT_REL must use the current value as addend. PR: 204084 Obtained from: NetBSD libdwarf_elf_init.c v1.4 296662 by maxim: o Kill EoL whitespaces. No functional changes. The end of the build log: Started by an SCM change Building remotely on kyua4.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_HEAD_arm64 Updating svn://svnmir.freebsd.org/base/head at revision '2016-03-11T17:54:38.113 +0000' U usr.sbin/pc-sysinstall/backend/functions-disk.sh U sbin/nvmecontrol/power.c U sbin/ping/ping.c U Makefile U share/man/man5/src.conf.5 U share/mk/bsd.opts.mk AU tools/build/options/WITHOUT_FAST_DEPEND U UPDATING U contrib/elftoolchain/libdwarf/libdwarf_elf_init.c At revision 296673 No emails were triggered. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson7262023926863219782.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + true + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + true + sudo umount FreeBSD_HEAD_arm64/usr/src + true + sudo umount FreeBSD_HEAD_arm64/dev + true + sudo rm -fr FreeBSD_HEAD_arm64 + sudo chflags -R noschg FreeBSD_HEAD_arm64 + true + sudo rm -fr FreeBSD_HEAD_arm64 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson7449183585539669172.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo env: env: + /usr/bin/env BUILD_NUMBER=2583 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_HEAD_arm64 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/head BUILDER_JAIL_IP=2610:1c1:1:607c::104:1 jname=FreeBSD_HEAD_arm64 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=2583 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_HEAD_arm64 BUILD_TAG=jenkins-FreeBSD_HEAD_arm64-2583 NODE_LABELS=jailer kyua4.nyi.freebsd.org BUILD_DISPLAY_NAME=#2583 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2583/ SVN_URL_1=svn://svnmir.freebsd.org/base/head SVN_REVISION=296673 SVN_REVISION_1=296673 BUILDER_JAIL_IP6=2610:1c1:1:607c::104:1 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=e261895a-6231-4b8a-b869-9ba3d9479d1e BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_HEAD_arm64 NODE_NAME=kyua4.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_HEAD_arm64' setup jail FreeBSD_HEAD_arm64 + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/base.txz + fetch -m http://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/10.2-RELEASE/lib32.txz + mkdir FreeBSD_HEAD_arm64 + cd FreeBSD_HEAD_arm64 + sudo tar Jxf ../base.txz + sudo tar Jxf ../lib32.txz + cd - + sudo mount -t devfs devfs FreeBSD_HEAD_arm64/dev + sudo devfs -m FreeBSD_HEAD_arm64/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_HEAD_arm64/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_HEAD_arm64/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 alias + sudo jail -c persist 'name=FreeBSD_HEAD_arm64' 'path=FreeBSD_HEAD_arm64' 'host.hostname=FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::104:1' 'ip4=disable' allow.chflags + echo 'setup build environment' setup build environment + sudo pkg -j FreeBSD_HEAD_arm64 install -y aarch64-binutils pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended Updating FreeBSD repository catalogue... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching meta.txz: . done [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching packagesite.txz: .......... done Processing entries: .......... done FreeBSD repository update completed. 24686 packages processed. The following 1 package(s) will be affected (of 0 checked): New packages to be INSTALLED: aarch64-binutils: 2.25.1 The process will require 13 MiB more space. 1 MiB to be downloaded. [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] Fetching aarch64-binutils-2.25.1.txz: .......... done Checking integrity... done (0 conflicting) [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Installing aarch64-binutils-2.25.1... [FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org] [1/1] Extracting aarch64-binutils-2.25.1: .......... done + echo 'build environment:' build environment: + sudo jexec FreeBSD_HEAD_arm64 sh -c 'uname -a' FreeBSD FreeBSD_HEAD_arm64.jail.ci.FreeBSD.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296318: Wed Mar 2 16:40:46 UTC 2016 peter@build-11.freebsd.org:/usr/obj/usr/src/sys/CLUSTER11 amd64 + sudo pkg -j FreeBSD_HEAD_arm64 info -q pkg: Warning: Major OS version upgrade detected. Running "pkg-static install -f pkg" recommended aarch64-binutils-2.25.1 [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson8238654997313507744.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'start build in FreeBSD_HEAD_arm64' start build in FreeBSD_HEAD_arm64 + sudo jexec FreeBSD_HEAD_arm64 sh -c 'cd /usr/src && make -DNO_CLEAN -j 4 buildworld TARGET=arm64' --- upgrade_checks --- --- bmake --- -------------------------------------------------------------- >>> Building an up-to-date bmake(1) -------------------------------------------------------------- make[2]: "/usr/share/mk/bsd.own.mk" line 498: MK_TESTS can't be set by a user. *** [bmake] Error code 1 make[1]: stopped in /usr/src 1 error make[1]: stopped in /usr/src *** [upgrade_checks] Error code 2 make: stopped in /usr/src 1 error make: stopped in /usr/src Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_HEAD_arm64] $ /bin/sh -xe /tmp/hudson622890042019692718.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_HEAD_arm64' + echo 'clean up jail FreeBSD_HEAD_arm64' clean up jail FreeBSD_HEAD_arm64 + sudo jail -r FreeBSD_HEAD_arm64 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::104:1 -alias + sudo umount FreeBSD_HEAD_arm64/usr/src + sudo umount FreeBSD_HEAD_arm64/dev + sudo rm -fr FreeBSD_HEAD_arm64 + true + sudo chflags -R noschg FreeBSD_HEAD_arm64 + sudo rm -fr FreeBSD_HEAD_arm64 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-arm@freebsd.org Fri Mar 11 21:02:27 2016 Return-Path: Delivered-To: freebsd-arm@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 01210ACDB54 for ; Fri, 11 Mar 2016 21:02:27 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id E8C4A19F9; Fri, 11 Mar 2016 21:02:26 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 6118513B0; Fri, 11 Mar 2016 21:02:27 +0000 (UTC) Date: Fri, 11 Mar 2016 21:02:25 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: bdrewery@FreeBSD.org, dumbbell@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-arm@FreeBSD.org Message-ID: <810847370.29.1457730147293.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1620451985.25.1457718941703.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1620451985.25.1457718941703.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_HEAD_arm64 - Build #2584 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_HEAD_arm64 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 21:02:27 -0000 FreeBSD_HEAD_arm64 - Build #2584 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2584/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2584/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_arm64/2584/console Change summaries: 296676 by bdrewery: Avoid MK_TESTS error on stable/10 by just preventing SUBDIR recursion. 296675 by bdrewery: Avoid bmake upgrade NO_MAN warning by just setting MAN to empty. Suggested by: imp 296674 by dumbbell: drm: Fix dev->ioctl_count references leak This fixes the following error: kernel: error: [drm:pid1167:drm_release] *ERROR* Device busy: 2 Because of that, drm_lastclose() was not called, leading to a few memory leaks once the driver was unloaded. MFC after: 1 week From owner-freebsd-arm@freebsd.org Fri Mar 11 21:19:46 2016 Return-Path: Delivered-To: freebsd-arm@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 B3DFEACC0D6 for ; Fri, 11 Mar 2016 21:19:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4C808DB for ; Fri, 11 Mar 2016 21:19:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2BLJkrE030706 for ; Fri, 11 Mar 2016 21:19:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 207912] Banana Pi framebuffer doesn't work Date: Fri, 11 Mar 2016 21:19:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: allcoms@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2016 21:19:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207912 Bug ID: 207912 Summary: Banana Pi framebuffer doesn't work Product: Base System Version: 11.0-CURRENT Hardware: arm OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: allcoms@gmail.com I see the uboot output via the HDMI port on my Banana Pi fine when booting FreeBSD-11.0-CURRENT-arm-armv6-BANANAPI-20160308-r296485.img but as soon as= the kernel starts to boot all I see is a static, garbled image of sorts on my monitor although I know FreeBSD is otherwise booting fine via UART serial console. I have read of other BPi users having this same issue booting the FBSD 11 t= est images on the FBSD forum so its not just my config. --=20 You are receiving this mail because: You are the assignee for the bug.=