From owner-freebsd-current@freebsd.org Sun Feb 5 19:47:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83404CD2806 for ; Sun, 5 Feb 2017 19:47:25 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 3B3EFB9E for ; Sun, 5 Feb 2017 19:47:25 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id 11so37546672qkl.3 for ; Sun, 05 Feb 2017 11:47:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SnJGK+3GEAqGxJSXIUnkYrw9XkjzdKURL0FRppr32Sc=; b=dG8P1YKYPFpKqOIbXYTd4GqwmT0/ryMLW57g0knmy+mzSFM2O0WO7T9CIkdVyIPS51 12QfEYW5LGcL4f7TuHK8sjTLiNgCCVC9C4xI5RoA026eGKrT5/1l3ehIVo+6TtK9XlKs Zracs4Rb0KeOO590unYoDS51ytbtBGfxuy/k4CR8dXFLgxZ3dEW8bZCCPgPdF7vVLBE+ Id2EueEYfVqeEDVbZ423+NONIE+Q4zqnlpoibwwfGcQCI0WIR//Ec64O2bD13D0oKct9 ECecV61uDcatafFJm9+biChW2plqdHbeb1kuIPlKteoZ0DQ3DxfBdLkyStp+LVgOQbMz HFCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SnJGK+3GEAqGxJSXIUnkYrw9XkjzdKURL0FRppr32Sc=; b=mkoWNkiTfNw2iNWVMgl9X5nUIVCdRKcSIA/BeCr9Igmclmz6jphX4KCeGjYHSmgNt8 fsCtjbPVaeRC0ntnRH0d4aUiUF5zi/8V7q8DtHVTLv2BpXDM6H32K0g+ZCImVlXtHe8C AY/AZTvW/R416MIY1sjdZb7fnjizQIT1ZmVIfoRBMV3jgtMG0gnkQ5F4O8kCC5xP3jD/ EzucJiPL3NYQFObUpRsLH4200QE0qDmCcy4I0NrTJlhyo4UgJZSFi2+GGg+JzH7DA7uE dRnyiR3UCKbwnHxY/yE3kK8s36acIiWCfg9c5LO5Y8LQAOhN1UZKIQ2F2GYi6O9f1lq6 XzYQ== X-Gm-Message-State: AMke39ms5igrPqDyXNyA/8d50D7rC7Al0WpoZK/FvOhf75hA9BoP8S0XJzOEd/I0gplsJ3o1PRa6Xmeu15Xn5A== X-Received: by 10.55.99.132 with SMTP id x126mr7458879qkb.62.1486324044355; Sun, 05 Feb 2017 11:47:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.104.8 with HTTP; Sun, 5 Feb 2017 11:46:53 -0800 (PST) In-Reply-To: References: <20170113120534.GC2349@kib.kiev.ua> <20170115202008.GL2349@kib.kiev.ua> <20170116120021.GQ2349@kib.kiev.ua> <5f814a7a-5e46-057e-62ad-dde0a61bc1c8@selasky.org> From: Jia-Shiun Li Date: Mon, 6 Feb 2017 03:46:53 +0800 Message-ID: Subject: Re: TSC as timecounter makes system lag To: Hans Petter Selasky Cc: Konstantin Belousov , freebsd-current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2017 19:47:25 -0000 FYI since it was not really solved as of r313090, I created bug 216833 to keep track of it. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216833 -Jia-Shiun. From owner-freebsd-current@freebsd.org Mon Feb 6 09:08:15 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31309CD2C6D; Mon, 6 Feb 2017 09:08:15 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 5EA4D1908; Mon, 6 Feb 2017 09:08:14 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [RFC/RFT] projects/ipsec To: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> From: "Andrey V. Elsukov" Message-ID: <400b1efb-f770-b41b-805a-a755236da85b@FreeBSD.org> Date: Mon, 6 Feb 2017 12:07:00 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 09:08:15 -0000 On 11.12.2016 02:07, Andrey V. Elsukov wrote: > I am pleased to announce that projects/ipsec, that I started several > months ago is ready for testing and review. > The main goals were: > * rework locking to make IPsec code more friendly for concurrent > processing; > * make lookup in SADB/SPDB faster; > * revise PFKEY implementation, remove stale code, make it closer > to RFC; > * implement IPsec VTI (virtual tunneling interface); > * make IPsec code loadable as kernel module. JFYI, the project was merged into head/ in r313330. -- WBR, Andrey V. Elsukov From owner-freebsd-current@freebsd.org Mon Feb 6 13:28:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFBFECD179F for ; Mon, 6 Feb 2017 13:28:05 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E3001AE7; Mon, 6 Feb 2017 13:28:05 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.34.116] (helo=smtp8.mnd.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cajKn-0004Us-IO; Mon, 06 Feb 2017 14:27:57 +0100 Received: from 5ed15678.cm-7-2b.dynamic.ziggo.nl ([94.209.86.120] helo=wan0.bsd4all.org) by smtp8.mnd.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1cajKn-0000jG-GU; Mon, 06 Feb 2017 14:27:57 +0100 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id 5E2074AB; Mon, 6 Feb 2017 14:27:57 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgIOWQUNLhLB; Mon, 6 Feb 2017 14:27:56 +0100 (CET) Received: from [192.168.1.64] (mm [192.168.1.64]) by wan0.bsd4all.org (Postfix) with ESMTPSA id DE87B4A2; Mon, 6 Feb 2017 14:27:56 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: [RFC/RFT] projects/ipsec From: peter.blok@bsd4all.org In-Reply-To: <400b1efb-f770-b41b-805a-a755236da85b@FreeBSD.org> Date: Mon, 6 Feb 2017 14:27:56 +0100 Cc: freebsd-current@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> <400b1efb-f770-b41b-805a-a755236da85b@FreeBSD.org> To: "Andrey V. Elsukov" X-Mailer: Apple Mail (2.3259) X-SourceIP: 94.209.86.120 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=Uv8TD64B c=1 sm=1 tr=0 a=IkzOOneQUJP1+bAPekPvBg==:17 a=kj9zAlcOel0A:10 a=n2v9WMKugxEA:10 a=6I5d2MoRAAAA:8 a=4FOKkXSynkp8-R7XuEsA:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 13:28:05 -0000 Andrey, Is this going to MFC'ed to stable-11 in the future? I have tested with = current and found no issues, but I would like to add it to a = semi-production environment running stable-11 Peter > On 6 Feb 2017, at 10:07, Andrey V. Elsukov wrote: >=20 > On 11.12.2016 02:07, Andrey V. Elsukov wrote: >> I am pleased to announce that projects/ipsec, that I started several >> months ago is ready for testing and review. >> The main goals were: >> * rework locking to make IPsec code more friendly for concurrent >> processing; >> * make lookup in SADB/SPDB faster; >> * revise PFKEY implementation, remove stale code, make it closer >> to RFC; >> * implement IPsec VTI (virtual tunneling interface); >> * make IPsec code loadable as kernel module. >=20 > JFYI, the project was merged into head/ in r313330. >=20 > --=20 > WBR, Andrey V. Elsukov > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Feb 6 13:41:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33167CD1D42 for ; Mon, 6 Feb 2017 13:41:26 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 6939265C; Mon, 6 Feb 2017 13:41:25 +0000 (UTC) (envelope-from ae@FreeBSD.org) Subject: Re: [RFC/RFT] projects/ipsec To: peter.blok@bsd4all.org References: <2bd32791-944f-2417-41e9-e0fe1c705502@FreeBSD.org> <400b1efb-f770-b41b-805a-a755236da85b@FreeBSD.org> Cc: freebsd-current@FreeBSD.org From: "Andrey V. Elsukov" Message-ID: Date: Mon, 6 Feb 2017 16:40:10 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 13:41:26 -0000 On 06.02.2017 16:27, peter.blok@bsd4all.org wrote: > Andrey, > > Is this going to MFC'ed to stable-11 in the future? I have tested > with current and found no issues, but I would like to add it to a > semi-production environment running stable-11 > Hi, I thought to make MFC after a month or two, but I didn't seen any information when 11.1-RELEASE is planned. So, I don't know when feature freeze begins. Also there are some changes that can be considered as POLA violation, especially the single name space for SPI can affect some users. -- WBR, Andrey V. Elsukov From owner-freebsd-current@freebsd.org Mon Feb 6 16:01:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49DD8CD3A2B for ; Mon, 6 Feb 2017 16:01:33 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 37091314 for ; Mon, 6 Feb 2017 16:01:33 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3036ECD3A29; Mon, 6 Feb 2017 16:01:33 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F941CD3A27; Mon, 6 Feb 2017 16:01:33 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8D09312; Mon, 6 Feb 2017 16:01:32 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1caljN-0002gG-2Y; Mon, 06 Feb 2017 17:01:29 +0100 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1caljN-0007Rw-0Z; Mon, 06 Feb 2017 17:01:29 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Mon, 06 Feb 2017 16:01:28 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "ports" CC: "current" Subject: Re: Seamonkey update Date: Mon, 06 Feb 2017 08:01:28 -0800 (PST) X-Mailer: RMM6 In-Reply-To: <22679.52207.6914.639479@jerusalem.litteratus.org> Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Feb 2017 16:01:33 -0000 On Sun, 5 Feb 2017 20:05:51 -0500, roberthuff@rcn.com wrote: >=20 > Jeffrey Bouquet writes: >=20 > > pkg today updated seamonkey, now it segfaults,=20 > > every which way I try to run it. >=20 > I am running SeaMonkey 2.46_5 (compiled today) under: >=20=09 > FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 >=20 > . > So far, indistinguishable from _4. >=20 >=20 >=20 > Respectfully, >=20 >=20 > Robert Huff More progress but not so encouraging. Rebuilt the machine on which seamonkey segfaulted, to v12-CURRENT=20 .............. seamonkey still segfaults after _4 _5 [ a showstopper for the v11 OR v12 desktop on that disk ]=20 /usr/bin/cc segfaults, prohibiting port building after installworld [ a showstopper for v12 on that disk ] pkg -vv reports v11 FreeBSD.conf=20 containing FreeBSD:12:x86:32, containing /${ABI}/, containing FreeBSD:12:i386 each error out in some manner or another, making package not usable. [a showstopper for pkg usage on that disk ] Firefox prohibits 2 entry anywhere, so I cannot log into the forums as jb_fvwm2 on the newer machine to inquire there, not use most any search query containing the numeric digit(s) 2 and at least two others. [ a showstopper for firefox usage on that disk ] ................. None of these 4 problems were present on Feb 4 vs by the morning of today F= eb 6... From owner-freebsd-current@freebsd.org Tue Feb 7 01:35:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BB6ECD3669 for ; Tue, 7 Feb 2017 01:35:25 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 75D17EE6 for ; Tue, 7 Feb 2017 01:35:25 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 753C6CD3665; Tue, 7 Feb 2017 01:35:25 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74BE8CD3664; Tue, 7 Feb 2017 01:35:25 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A9F8EE4; Tue, 7 Feb 2017 01:35:24 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1cauge-0001lc-8Q; Tue, 07 Feb 2017 02:35:16 +0100 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1cauge-0002jt-79; Tue, 07 Feb 2017 02:35:16 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Tue, 07 Feb 2017 01:35:16 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "pkg" CC: "ports" , "current" Subject: 12-CURRENT won't configure to download packagesite.txz yet Date: Mon, 06 Feb 2017 17:35:16 -0800 (PST) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 01:35:25 -0000 All the files /etc/FreeBSD.conf /usr/local/etc/pkg/repos/FreeBSD.conf /usr/local/etc/pkg.conf I edit time after time for {$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386 Anytime I try to attune to freebsd:12:x86:32 or FreeBSD:12:i386 ... it downloads the packagesite again, as it does in the ABI example, but a te= rse error of wrong architecture, etc, and a fail to do anything to upgrade to = Pkg-12. Can the proper file be rename upstream to what its architecture in simpler = terms: like packagesite-i386-12.txz and a message printed upon de-TXZ the file so = that the proper nomenclature is given to put into each of those three files above so that the generic packagesite.txz will not error out upon download? Or, put the instructions in /usr/src/UPDATING ?? since it is part of base?= =20 Or some other way to de-showstopper this v11 April 2016 CURRENT to v12 Feb = 2017 CURRENT upgrade which still has failed to enable seamonkey-2.46_5 to run non-segfau= lt [ ie cannot run ] vs seamonkey-2.46_4 which four days ago ran without EVER segfaulting?? And= cannot build from ports for obscure .h clang-header file related reasons?=20= From owner-freebsd-current@freebsd.org Tue Feb 7 05:59:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B82E2CD27EC for ; Tue, 7 Feb 2017 05:59:13 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A74841163 for ; Tue, 7 Feb 2017 05:59:13 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id A3FA2CD27E8; Tue, 7 Feb 2017 05:59:13 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1A36CD27E7; Tue, 7 Feb 2017 05:59:13 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B62F1162; Tue, 7 Feb 2017 05:59:13 +0000 (UTC) (envelope-from allanjude@FreeBSD.org) Received: from [10.59.59.57] (unknown [91.183.237.24]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 3694013105; Tue, 7 Feb 2017 05:59:05 +0000 (UTC) Date: Tue, 07 Feb 2017 06:59:02 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: 12-CURRENT won't configure to download packagesite.txz yet To: jbtakk@iherebuywisely.com,pkg CC: ports ,current From: Allan Jude Message-ID: <4CC6808A-6F3C-4559-8663-4A493EEA2F64@FreeBSD.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 05:59:13 -0000 On February 7, 2017 2:35:16 AM GMT+01:00, Jeffrey Bouquet wrote: >All the files > >/etc/FreeBSD=2Econf >/usr/local/etc/pkg/repos/FreeBSD=2Econf >/usr/local/etc/pkg=2Econf > >I edit time after time for >{$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386 >Anytime I try to attune to >freebsd:12:x86:32 or >FreeBSD:12:i386 =2E=2E=2E >it downloads the packagesite again, as it does in the ABI example, but >a terse >error of wrong architecture, etc, and a fail to do anything to upgrade >to Pkg-12=2E > >Can the proper file be rename upstream to what its architecture in >simpler terms: >like packagesite-i386-12=2Etxz and a message printed upon de-TXZ the file >so that >the proper nomenclature is given to put into each of those three files >above >so that the generic packagesite=2Etxz will not error out upon download? >Or, put the instructions in /usr/src/UPDATING ?? since it is part of >base?=20 > > >Or some other way to de-showstopper this v11 April 2016 CURRENT to v12 >Feb 2017 CURRENT >upgrade which still has failed to enable seamonkey-2=2E46_5 to run >non-segfault [ ie cannot run ] >vs seamonkey-2=2E46_4 which four days ago ran without EVER segfaulting??= =20 >And cannot build >from ports for obscure =2Eh clang-header file related reasons?=20 >_______________________________________________ >freebsd-current@freebsd=2Eorg mailing list >https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to >"freebsd-current-unsubscribe@freebsd=2Eorg" Please provide the output of: uname -a uname -K uname -U --=20 Allan Jude From owner-freebsd-current@freebsd.org Tue Feb 7 11:09:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42FAFCD484C for ; Tue, 7 Feb 2017 11:09:22 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 230C41063 for ; Tue, 7 Feb 2017 11:09:22 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2247ECD484B; Tue, 7 Feb 2017 11:09:22 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21ED5CD484A for ; Tue, 7 Feb 2017 11:09:22 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm3-vm2.bullet.mail.ne1.yahoo.com (nm3-vm2.bullet.mail.ne1.yahoo.com [98.138.91.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9EBE1062 for ; Tue, 7 Feb 2017 11:09:21 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1486465754; bh=hni3zsL0x77fBTaHeqFMIanGJip8eVsgpb9P+J52eqU=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=e7b2H7OgvutKqATlvZQ7p7fiSz0xG6V353xo3GyhplmF1yiCtnfjofGQMdgVe8LyPuJ1+TtR//suLWmeykUh4Uj9L17vgJkE3nKdVPCkz02IYV1dZ7bSEDwdGuN24jCRt1xF8khf9GXHcJWjWem9QPTqJpUg1PY95CrdyX4j5s35fTiJgTiHYE/5WWw/ZWEJwpslCPNlC4LCTjOVW7SWA0zzzSAmvIPVKV8TnUT/YpFuU3Ls1zEfigt8rDL+1pVsBffxDa0puuAw8oHp99ixJgF80M0STehopBDbJroXmjlX14FU6o9DdrMmoQcLvkLKuFoKe6SMyyqJ9yzsKX6+Dw== Received: from [98.138.100.102] by nm3.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2017 11:09:14 -0000 Received: from [98.138.226.124] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2017 11:09:14 -0000 Received: from [127.0.0.1] by smtp203.mail.ne1.yahoo.com with NNFMP; 07 Feb 2017 11:09:14 -0000 X-Yahoo-Newman-Id: 870178.4840.bm@smtp203.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 2Lo0OAcVM1m3TmYdq9vJhPhMft2CJR.rH9pPrpCOkXQ0UhE SborSl.2PS4RK5NijMcD_IIDh6TQ2HTUD7WwZF4MzvKhBw6p_7PYmBAzcJST Q67XM7qUjlcWQFRWdmytDCdEpXPPvPoiIvTyp6sBUlGu_DQFALRrtSLGm_dK gMCNuyyiDEPUMNSIRO89AU69wmWpBFyLKCj0TTfUJudQBLHbcIXdHnEWuNE2 0kIYj7x_.1VEJ1wteSGuJvGlQDbDndU_NT0CwyDIM95xMcjRbsvVCgh_UCcd Qz9m.7YuT68f.kNT6HbGsQ2fidIOsHcQIsGdEl__LAlFzcoBaqmfy1VWd2J1 Fpm0ahKUcJBBkODrW.4coK4p46WiEKooTpRdlrtfoT_YnZ97Egr9DMZYyth0 sLI6Jxkys.BG8gfuDWJ_ADXb_qTx8yAAH16QAQpPPrHvQ2Wx7a0jNwIbTZoE GzRVDcYA3JjO4BNuOUCNl.88AxTuAjKsE4mq3TY2wnR4N4eA8.oGNE_AWktM _umQN7owrHOPUZPqFUGjzKW_a7HV.7P6L.eCfZiKC68pn_JpKpzI9vBMtYB. ozShlAT5XSxWBm0ThU0dPyw-- X-Yahoo-SMTP: 6IZaPQyswBAeyzp3urHRlQfBxGxx4Js3YAIn Subject: Re: 12-CURRENT won't configure to download packagesite.txz yet To: Allan Jude , jbtakk@iherebuywisely.com, pkg References: <4CC6808A-6F3C-4559-8663-4A493EEA2F64@FreeBSD.org> Cc: ports , current From: Jeffrey Bouquet Message-ID: Date: Tue, 7 Feb 2017 03:09:12 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <4CC6808A-6F3C-4559-8663-4A493EEA2F64@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 07 Feb 2017 12:07:08 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 11:09:22 -0000 On 02/ 6/17 09:59 PM, Allan Jude wrote: > On February 7, 2017 2:35:16 AM GMT+01:00, Jeffrey Bouquet wrote: >> All the files >> >> /etc/FreeBSD.conf >> /usr/local/etc/pkg/repos/FreeBSD.conf >> /usr/local/etc/pkg.conf >> >> I edit time after time for >> {$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386 >> Anytime I try to attune to >> freebsd:12:x86:32 or >> FreeBSD:12:i386 ... >> it downloads the packagesite again, as it does in the ABI example, but >> a terse >> error of wrong architecture, etc, and a fail to do anything to upgrade >> to Pkg-12. >> >> Can the proper file be rename upstream to what its architecture in >> simpler terms: >> like packagesite-i386-12.txz and a message printed upon de-TXZ the file >> so that >> the proper nomenclature is given to put into each of those three files >> above >> so that the generic packagesite.txz will not error out upon download? >> Or, put the instructions in /usr/src/UPDATING ?? since it is part of >> base? >> >> >> Or some other way to de-showstopper this v11 April 2016 CURRENT to v12 >> Feb 2017 CURRENT >> upgrade which still has failed to enable seamonkey-2.46_5 to run >> non-segfault [ ie cannot run ] >> vs seamonkey-2.46_4 which four days ago ran without EVER segfaulting?? >> And cannot build > >from ports for obscure .h clang-header file related reasons? >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > Please provide the output of: > uname -a machine on which firefox, thunderbird, seamonkey, cc, pkg work: ....................... 11.0-CURRENT #2 R298350 Wed Apr 20 2016 I386 1100105 1100105 DEC22KRNL10 ( not GENERIC ) ................... machine on which firefox has broken numeric input [ I cannot log into the FreeBSD forum as my nickname has a "2" within it... nor use browser search in firefox that searches for terms with a "2" within the text field... jumps to another tab..., cc MAY be fixed, pkg still works only at v11, seamonkey segfaults, thunderbird segfaults, otter-browser has bus error, seamonkey won't build due to maybe clang header files: .................. 12.0-CURRENT #3 R313305 Mon Feb 6 2017 i386 1200020 ( guess from strings on the kernel) ... (forgot to run uname when booted into the system) 1200020 ( guess from strings on the kernel) " DEC22KRNL10 (not GENERIC) and per pkg -vv, still v11... > uname -K > uname -U > Again, maybe a ${ABI} set of three files (FreeBSD.conf (2) , pkg.conf ) that I could use as a template may fix the package issue and if that is fixed, could fix the seamonkey/thunderbird/firefox issues... Precise documentation is lacking in the limited time I have to test solutions in forum and mailing list posts. ..... From owner-freebsd-current@freebsd.org Tue Feb 7 16:08:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 104C8CD508F for ; Tue, 7 Feb 2017 16:08:51 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout06.bt.lon5.cpcloud.co.uk (rgout0606.bt.lon5.cpcloud.co.uk [65.20.0.133]) by mx1.freebsd.org (Postfix) with ESMTP id 913371810 for ; Tue, 7 Feb 2017 16:08:49 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 31.54.234.60 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2017.2.7.151815:17:7.944, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NO_NAME, __SUBJ_ALPHA_START, __SUBJ_ALPHA_END, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CTYPE_MULTIPART_ALT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __MIME_TEXT_P2, __MIME_TEXT_H2, __CASH, __CP_MEDIA_BODY, __MULTIPLE_URI_TEXT, __HTML_MSWORD, __URI_IN_BODY, __STYLE_RATWARE_NEG, __STYLE_TAG, __HAS_HTML, __HTML_TAG_DIV, BODY_SIZE_4000_4999, BODYTEXTP_SIZE_3000_LESS, BODYTEXTH_SIZE_3000_MORE, BODYTEXTH_SIZE_10000_LESS, __MIME_TEXT_H1, __MIME_TEXT_P1, __MIME_HTML, __TAG_EXISTS_HTML, HTML_50_70, __FRAUD_MONEY_CURRENCY, BODY_SIZE_5000_LESS, __FRAUD_WEBMAIL, __OUTLOOK_MUA, NO_URI_FOUND, NO_CTA_URI_FOUND, __URI_NO_PATH, __MIME_TEXT_H, __MIME_TEXT_P, FORGED_MUA_OUTLOOK, BODY_SIZE_7000_LESS, NO_URI_HTTPS Received: from ThomasPC (31.54.234.60) by rgout06.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as Thomas.Sparrevohn) id 58482F250577AE23 for FreeBSD-current@FreeBSD.org; Tue, 7 Feb 2017 16:08:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1486483730; bh=3NLDKc8tuDoes4uMB4xkl4GtoxVDnoq7PgT0Dxp8Nnc=; h=From:To:Subject:Date:Message-ID:MIME-Version:X-Mailer; b=BQmwMxL2mzPn9XXqvDEhoyzSsQA9TETyLECZbYaa1/ZhbEfw2Vw/S31BlKu4C2ACk1NeBIQH7yIl1kT+LSKmqFUQoL8/2w2lKpXCJk+BCPt792r34Jnu8OqbuO2b4wfE9ateeZDWNkSvvEWJoz+cfFH9o/eyT7pmUYEUITlosFU= From: "Thomas Sparrevohn" To: Subject: gptzfsboot trouble Date: Tue, 7 Feb 2017 16:08:44 -0000 Message-ID: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 15.0 Thread-Index: AdKBXHSA7QmKdWrCRgycSvnxqVnpJw== Content-Language: en-gb Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 16:08:51 -0000 Hi all Last week I decided to upgrade my FreeBSD installation - it's been a while (September 16 was last time). Unfortunately CURRENT does not boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to attempt to read blocks that exceeds the physical disk. Initially I through it was a hard disk error - but after a "oh" experience I realised that the "gptzfsboot: error 4 lba 921592" is actually beyond the physical boundaries of the disk (300GB disk). In order to rule out different options - I installed a vanilla 11-RELEASE on the 300G with a simple stripe - it also gives the error but does boot - the LBA of the error is slightly different on 11 CURRENT and comes up with LBA 921600 I have scanned all the disks for physical faults and there seems to be none and I have tried doing a single disk installation on each disk - they give the same error - Does anybody have any idea? Included Photos as sometimes it get through to the actual boot menu but then crash in another place I have some images - but they are 2 bit for the mailing list ;-) From owner-freebsd-current@freebsd.org Tue Feb 7 16:33:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2BA7CD55C0 for ; Tue, 7 Feb 2017 16:33:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CC788A4 for ; Tue, 7 Feb 2017 16:33:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL000900J04VS00@st13p35im-asmtp002.me.com> for FreeBSD-current@FreeBSD.org; Tue, 07 Feb 2017 16:33:24 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486485203; bh=9eA6gQzsRK5rwxaXNCkrTAN1sZ6d0bRcOEYSzqNChys=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=q8pD1HMY5RH4jLP+FUf1ObPfWDjufAyioBNx1dGCohhMUvNAKmvQZCFnItwgBQ+G+ TC9qcivWf0XCD60YCV8FYteikkLXp/K4rFzgMVkDYr9PL0NcSwQR8F0PiIa+g12JHp 6iMCXylrErbPqNkIlxPFiFEwv86Z7nSta1WPJoBzDzOW52TLEhW+U0XyVWmQSw9NqO Mcva9j1MSAKwam2d0C/LvoyH7pkbQOcTgMUwoOjZA/gSrU1+iVANYAmuhGT3COevQz n4zDagF8hmvcTsC9gcQ+kIdAsfZoFWXbzLIhUnn3WZo6l0TaIbPFI1rk2x+7pUn481 qRjQ3TdugpH2w== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL0003C4JBLS520@st13p35im-asmtp002.me.com> for FreeBSD-current@FreeBSD.org; Tue, 07 Feb 2017 16:33:23 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-07_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=4 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702070158 From: Toomas Soome Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: gptzfsboot trouble Date: Tue, 07 Feb 2017 18:33:21 +0200 References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> To: FreeBSD-current@FreeBSD.org In-reply-to: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> Message-id: <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 16:33:38 -0000 > On 7. veebr 2017, at 18:08, Thomas Sparrevohn = wrote: >=20 > Hi all >=20 >=20 >=20 > Last week I decided to upgrade my FreeBSD installation - it's been a = while > (September 16 was last time). Unfortunately CURRENT does not boot and = cash > in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to = attempt > to read blocks that exceeds the physical disk. Initially I through it = was a > hard disk error - but after a "oh" experience I realised that the > "gptzfsboot: error 4 lba 921592" is actually beyond the physical = boundaries > of the disk (300GB disk). In order to rule out different options - I > installed a vanilla 11-RELEASE on the 300G with a simple stripe - it = also > gives the error but does boot - the LBA of the error is slightly = different > on 11 CURRENT and comes up with LBA 921600 >=20 >=20 >=20 > I have scanned all the disks for physical faults and there seems to be = none > and I have tried doing a single disk installation on each disk - they = give > the same error - Does anybody have any idea? Included Photos as = sometimes it > get through to the actual boot menu but then crash in another place >=20 The gptzfsboot does read the backup label from the disk and the GPT = backup label is stored at the end of the disk. The location of the = backup label is in the primary GPT table, alternate sector field. I = wonder if that location is somehow set to bad value=E2=80=A6 rgds, toomas= From owner-freebsd-current@freebsd.org Tue Feb 7 16:41:29 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78628CD593C for ; Tue, 7 Feb 2017 16:41:29 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wj0-x231.google.com (mail-wj0-x231.google.com [IPv6:2a00:1450:400c:c01::231]) (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 15806EC0 for ; Tue, 7 Feb 2017 16:41:28 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wj0-x231.google.com with SMTP id b20so5446820wjs.2 for ; Tue, 07 Feb 2017 08:41:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=BqwY2EuenV6Ty0HH1s54kmvfiG/94hgY1aSwfbDdAsw=; b=EQwA1/McPv2+RLfoTN6tVvwoxEWaLpxm48CBeWKAF8lTt6WlKFqmaqy3XDSGF4N1aA IrfTR1WAIy07SLN4F3L8X9gT7Y8VoAIscBaAJamtOoVKQh1twk/wi96dtJKi3MUolEo1 nPsdQ93eVL+gRcI2L6w8bxxy7xM8jml1C+drntAaQM4JjU2QV/zWOB3G4CgUK2FCL/7K WKNO+pIjTEZqudxAL7M70SqCog8dYz3adjGSmL2tdyVHk7TrHm2DT4cpcmq7/rZH6ajh 46maagmBidFmbzeSo+ww1ID/9FwXiXgkZEXADNNqgn0FmzjcNvEHE0vKZ/RNAWwHNtJh ZqKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=BqwY2EuenV6Ty0HH1s54kmvfiG/94hgY1aSwfbDdAsw=; b=t8LqwTl+bQMoASM7GX4ayL5Q8ZsVTfaw0sooJC3v8GTupiJJRVcJ57kfcH5nUbxQiQ hVGPZuY/TQXD/hO2+c+zSu7LisD9C1qUibg8DRm6E7xE0cZ0jCl92ouV/2eyycGNH0Hc XQD8xAex8XvhGwcM59opolb+m2NJF4PoQaSQz4+YTd9JrVTe3rAwMdKvPb710G5+Xei4 Ijwqpl/5dg8geg9+3Mbu2Co8vpJVVLyBLkiqk6uC2ycMl6box3Jr7bUn1ucPYuByOWOW OFj5xNVdl2gb6G84ZceVLch8z6+coBaPXtbTelRCwGuZMpmnN7r7BhoAKAb2C5zWB6XW Bghw== X-Gm-Message-State: AIkVDXKkepTzxrvRXmH8yEh+xKLIxPNHbYjjWTKPb2r4+Jrhm6mkPv+LUaLIaI65iB/l0Hkc X-Received: by 10.223.133.131 with SMTP id 3mr14962539wrt.161.1486485687025; Tue, 07 Feb 2017 08:41:27 -0800 (PST) Received: from [10.10.1.58] ([185.97.61.26]) by smtp.gmail.com with ESMTPSA id 61sm8225334wrs.29.2017.02.07.08.41.26 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 08:41:26 -0800 (PST) Subject: Re: gptzfsboot trouble To: freebsd-current@freebsd.org References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> From: Steven Hartland Message-ID: <78739e6c-a645-25a6-a65b-968941fc4864@multiplay.co.uk> Date: Tue, 7 Feb 2017 16:41:25 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 16:41:29 -0000 On 07/02/2017 16:33, Toomas Soome wrote: > >> On 7. veebr 2017, at 18:08, Thomas Sparrevohn wrote: >> >> Hi all >> >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a while >> (September 16 was last time). Unfortunately CURRENT does not boot and cash >> in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to attempt >> to read blocks that exceeds the physical disk. Initially I through it was a >> hard disk error - but after a "oh" experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical boundaries >> of the disk (300GB disk). In order to rule out different options - I >> installed a vanilla 11-RELEASE on the 300G with a simple stripe - it also >> gives the error but does boot - the LBA of the error is slightly different >> on 11 CURRENT and comes up with LBA 921600 >> >> >> >> I have scanned all the disks for physical faults and there seems to be none >> and I have tried doing a single disk installation on each disk - they give >> the same error - Does anybody have any idea? Included Photos as sometimes it >> get through to the actual boot menu but then crash in another place >> > > The gptzfsboot does read the backup label from the disk and the GPT backup label is stored at the end of the disk. The location of the backup label is in the primary GPT table, alternate sector field. I wonder if that location is somehow set to bad value… > > Booting from a live CD and inspecting the label with gpart show should be able to confirm that. Regards Steve From owner-freebsd-current@freebsd.org Tue Feb 7 17:22:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE7CDCD56B5 for ; Tue, 7 Feb 2017 17:22:59 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout06.bt.lon5.cpcloud.co.uk (rgout0606.bt.lon5.cpcloud.co.uk [65.20.0.133]) by mx1.freebsd.org (Postfix) with ESMTP id 5B7331203 for ; Tue, 7 Feb 2017 17:22:58 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 86.150.65.0 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2017.2.7.164215:17:8.129, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __REFERENCES, __IN_REP_TO, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __HTTPS_URI, __URI_WITH_PATH, __CANPHARM_UNSUB_LINK, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __CASH, __CP_MEDIA_BODY, __CP_URI_IN_BODY, __SUBJ_ALPHA_NEGATE, SUPERLONG_LINE, __URI_IN_BODY, __FORWARDED_MSG, __NO_HTML_TAG_RAW, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, HTML_00_01, HTML_00_10, __FRAUD_MONEY_CURRENCY, BODY_SIZE_5000_LESS, __FRAUD_WEBMAIL, __OUTLOOK_MUA, __SINGLE_URI_TEXT, SINGLE_URI_IN_BODY, __PHISH_SPEAR_STRUCTURE_1, IN_REP_TO, __MIME_TEXT_P, FORGED_MUA_OUTLOOK, REFERENCES, BODY_SIZE_7000_LESS, MSG_THREAD, __TO_REAL_NAMES, LEGITIMATE_SIGNS Received: from ThomasPC (86.150.65.0) by rgout06.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as Thomas.Sparrevohn) id 58482F2505797304; Tue, 7 Feb 2017 17:21:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1486488179; bh=R9YxqfTOapGCNrAAph5nPPNdl53cn/lJl78slzJTAEs=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:X-Mailer; b=b3qKly031yE4zFhrelORhfXF7aGnZfqyFpOqHyRSShPA/R4fPdzGPU7hLFx+HrFUHvqVz74EUUR0vJ0TlGS/7hhl8SfDcr37H7nO6bJnl54cs31sahZh+kn/Y2MOUGKK7c2jnS7XCSelXlcHtDoP8tgearkmxmUSN+8pI5tQ9ro= From: "Thomas Sparrevohn" To: "'Steven Hartland'" , References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> <78739e6c-a645-25a6-a65b-968941fc4864@multiplay.co.uk> In-Reply-To: <78739e6c-a645-25a6-a65b-968941fc4864@multiplay.co.uk> Subject: RE: gptzfsboot trouble Date: Tue, 7 Feb 2017 17:21:29 -0000 Message-ID: <001e01d28166$9eac3960$dc04ac20$@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQJGBpsumuYIjmx3iyDp4DKqQEXNdQIgMYu1AgBSxhagVbtJ8A== Content-Language: en-gb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2017 17:22:59 -0000 I will check but I don't think so - The system has worked for years = without any trouble and I did a full wipe e.g. "dd if=3D/dev/zero = of=3D/dev/ada1" but let me check again - for ease - I think I am going = to do a vanilla single drive pool=20 -----Original Message----- From: owner-freebsd-current@freebsd.org = [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Steven Hartland Sent: 07 February 2017 16:41 To: freebsd-current@freebsd.org Subject: Re: gptzfsboot trouble On 07/02/2017 16:33, Toomas Soome wrote: > >> On 7. veebr 2017, at 18:08, Thomas Sparrevohn = wrote: >> >> Hi all >> >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a=20 >> while (September 16 was last time). Unfortunately CURRENT does not=20 >> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot=20 >> loader seems to attempt to read blocks that exceeds the physical=20 >> disk. Initially I through it was a hard disk error - but after a "oh" = >> experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical=20 >> boundaries of the disk (300GB disk). In order to rule out different=20 >> options - I installed a vanilla 11-RELEASE on the 300G with a simple=20 >> stripe - it also gives the error but does boot - the LBA of the error = >> is slightly different on 11 CURRENT and comes up with LBA 921600 >> >> >> >> I have scanned all the disks for physical faults and there seems to=20 >> be none and I have tried doing a single disk installation on each=20 >> disk - they give the same error - Does anybody have any idea?=20 >> Included Photos as sometimes it get through to the actual boot menu=20 >> but then crash in another place >> > > The gptzfsboot does read the backup label from the disk and the GPT=20 > backup label is stored at the end of the disk. The location of the=20 > backup label is in the primary GPT table, alternate sector field. I=20 > wonder if that location is somehow set to bad value=E2=80=A6 > > Booting from a live CD and inspecting the label with gpart show should = be able to confirm that. Regards Steve _______________________________________________ freebsd-current@freebsd.org mailing list = https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 11:50:19 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08DE2CD6E90 for ; Wed, 8 Feb 2017 11:50:19 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout0801.bt.lon5.cpcloud.co.uk (rgout0801.bt.lon5.cpcloud.co.uk [65.20.0.148]) by mx1.freebsd.org (Postfix) with ESMTP id 8D69214C5 for ; Wed, 8 Feb 2017 11:50:18 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 86.150.65.0 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2017.2.8.105717:17:8.129, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __REFERENCES, __IN_REP_TO, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __HTTPS_URI, __URI_WITH_PATH, __CANPHARM_UNSUB_LINK, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __CASH, __CP_MEDIA_BODY, __CP_URI_IN_BODY, __SUBJ_ALPHA_NEGATE, SUPERLONG_LINE, __MULTIPLE_URI_TEXT, __URI_IN_BODY, __FORWARDED_MSG, __NO_HTML_TAG_RAW, BODY_SIZE_3000_3999, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, __SXL_SIG_TIMEOUT[ee1b197f6eef2e65a1226c27fb4cad78.sig.aus1.sophosxl.com], __SXL_URI_TIMEOUT[lists.freebsd.org.uri.aus1.sophosxl.com], HTML_00_01, HTML_00_10, __FRAUD_MONEY_CURRENCY, BODY_SIZE_5000_LESS, __FRAUD_WEBMAIL, __OUTLOOK_MUA, __PHISH_SPEAR_STRUCTURE_1, IN_REP_TO, __MIME_TEXT_P, FORGED_MUA_OUTLOOK, REFERENCES, BODY_SIZE_7000_LESS, MSG_THREAD, __TO_REAL_NAMES, LEGITIMATE_SIGNS Received: from ThomasPC (86.150.65.0) by rgout08.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as Thomas.Sparrevohn) id 584830E3059B1A7E; Wed, 8 Feb 2017 11:48:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1486554618; bh=IiIqAR9goGdffG6YuWBpAMF3GKa7vPF5G4AsJthZZn0=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:X-Mailer; b=k/XgWZCo1V68HLz3+4wLbWIV38Hyraw52hIhb8Kp34hrdlO3iDn8KhFK7pfjRBoiRDvU7npCorhJPavtic1Zcigg3jeIZxnKhTFpZUr72S6+5MmOTnhjhxSQtTy1w5HRshK2KJzNr3flHiBV+AxZ3+Lxn4kjjB6jK/bgsBo0atI= From: "Thomas Sparrevohn" To: "'Steven Hartland'" , References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> <78739e6c-a645-25a6-a65b-968941fc4864@multiplay.co.uk> <001e01d28166$9eac3960$dc04ac20$@btinternet.com> In-Reply-To: <001e01d28166$9eac3960$dc04ac20$@btinternet.com> Subject: RE: gptzfsboot trouble Date: Wed, 8 Feb 2017 11:48:50 -0000 Message-ID: <002801d28201$50cf3260$f26d9720$@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQJGBpsumuYIjmx3iyDp4DKqQEXNdQIgMYu1AgBSxhYCUsnhCKBEWE9A Content-Language: en-gb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 11:50:19 -0000 Getting more and more weird - Installed a vanilla 11-RELEASE using UFS = rather ZFS and it issues no errors. Tried to roll back an older snapshot = but getting issues as the pool is build using 11-CURRENT. Looking at the = part - the LBA complained about is an empty sector (did a dd = if=3D/dev/zero of=3D/dev/ada1) and then read the blocks but they are = empty.=20 Both the UFS and ZFS was installed using GPT - and UFS does not = complain. The disks are old and so is the host and should most likely be = replaced anyhow but I am not sure if it will help.=20 -----Original Message----- From: owner-freebsd-current@freebsd.org = [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Thomas = Sparrevohn Sent: 07 February 2017 17:21 To: 'Steven Hartland' ; = freebsd-current@freebsd.org Subject: RE: gptzfsboot trouble I will check but I don't think so - The system has worked for years = without any trouble and I did a full wipe e.g. "dd if=3D/dev/zero = of=3D/dev/ada1" but let me check again - for ease - I think I am going = to do a vanilla single drive pool=20 -----Original Message----- From: owner-freebsd-current@freebsd.org = [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Steven Hartland Sent: 07 February 2017 16:41 To: freebsd-current@freebsd.org Subject: Re: gptzfsboot trouble On 07/02/2017 16:33, Toomas Soome wrote: > >> On 7. veebr 2017, at 18:08, Thomas Sparrevohn = wrote: >> >> Hi all >> >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a=20 >> while (September 16 was last time). Unfortunately CURRENT does not=20 >> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot=20 >> loader seems to attempt to read blocks that exceeds the physical=20 >> disk. Initially I through it was a hard disk error - but after a "oh" >> experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical=20 >> boundaries of the disk (300GB disk). In order to rule out different=20 >> options - I installed a vanilla 11-RELEASE on the 300G with a simple=20 >> stripe - it also gives the error but does boot - the LBA of the error = >> is slightly different on 11 CURRENT and comes up with LBA 921600 >> >> >> >> I have scanned all the disks for physical faults and there seems to=20 >> be none and I have tried doing a single disk installation on each=20 >> disk - they give the same error - Does anybody have any idea? >> Included Photos as sometimes it get through to the actual boot menu=20 >> but then crash in another place >> > > The gptzfsboot does read the backup label from the disk and the GPT=20 > backup label is stored at the end of the disk. The location of the=20 > backup label is in the primary GPT table, alternate sector field. I=20 > wonder if that location is somehow set to bad value=E2=80=A6 > > Booting from a live CD and inspecting the label with gpart show should = be able to confirm that. Regards Steve _______________________________________________ freebsd-current@freebsd.org mailing list = https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list = https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 12:26:46 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9FC3CD66F0 for ; Wed, 8 Feb 2017 12:26:46 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3946F30 for ; Wed, 8 Feb 2017 12:26:42 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cbRKZ-00006q-Ha; Wed, 08 Feb 2017 13:26:39 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: FreeBSD-current@freebsd.org, "Thomas Sparrevohn" Subject: Re: gptzfsboot trouble References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> Date: Wed, 08 Feb 2017 13:26:38 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: c09395f469c52153b963e4ff2d10f427 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 12:26:47 -0000 On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn wrote: > Hi all > > > Last week I decided to upgrade my FreeBSD installation - it's been a > while > (September 16 was last time). Unfortunately CURRENT does not boot and > cash > in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to > attempt > to read blocks that exceeds the physical disk. Initially I through it > was a > hard disk error - but after a "oh" experience I realised that the > "gptzfsboot: error 4 lba 921592" is actually beyond the physical > boundaries > of the disk (300GB disk). In order to rule out different options - I > installed a vanilla 11-RELEASE on the 300G with a simple stripe - it also > gives the error but does boot - the LBA of the error is slightly > different > on 11 CURRENT and comes up with LBA 921600 > > > I have scanned all the disks for physical faults and there seems to be > none > and I have tried doing a single disk installation on each disk - they > give > the same error - Does anybody have any idea? Included Photos as > sometimes it > get through to the actual boot menu but then crash in another place > > > I have some images - but they are 2 bit for the mailing list ;-) Can it be related to this issue? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 Would be nice if you tell more about the system. CPU? dmesg? The 11-RELEASE did that boot from the same disk? In the mentioned issue there is the case that gptzfsboot does recognize a secondary disk (can be configured as mirror), but not the first. As you say UFS works, the bug might be in the gptzfsboot code, because that is not used for UFS. Regards, Ronald. From owner-freebsd-current@freebsd.org Wed Feb 8 12:35:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E765DCD6919 for ; Wed, 8 Feb 2017 12:35:53 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C148B13CF for ; Wed, 8 Feb 2017 12:35:53 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL200K002R26K00@st13p35im-asmtp001.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 12:35:46 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486557346; bh=mTo0Hoqo9Yho0HlG9yiw+t1KA7fBWvvBN+ow4xeELUY=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=GJ6Bzoat2zoRqI4wdh8qnDDTDuTY1be+O64wBkWDGJp5PUddP7aLWR0/Qg/tjTDXY HH6tPtZUrdy/2x/AJVQIFPQWOeGj7VPMjYbnBV/cCzk5PNPhLFxqjLD8fFpi42ygF1 la6r70rRV9NqFMwhHjcfhXCmYP9i2WyjUpHdbKcAxwQIJMmIDO4v8wC3H4dUvuE2Q9 uhKAoMNuhUqI10fa+csy0173ZQvVEr9UOcmdL2MghQtQpSBHNqC0PaUX8LHGLzAFS8 yGI0D+/uWBT0naZVYedfS/fvR9Z7AfMEngUkIwVi+3Zj1RxJV9Jg+zRzF83Yc3+Vzm QNBhKwNFlv1AA== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL200GKF2ZJNY00@st13p35im-asmtp001.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 12:35:46 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-08_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=5 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702080123 From: Toomas Soome Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: gptzfsboot trouble Date: Wed, 08 Feb 2017 14:35:43 +0200 References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> To: FreeBSD-current@freebsd.org In-reply-to: Message-id: X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 12:35:54 -0000 > On 8. veebr 2017, at 14:26, Ronald Klop wrote: >=20 > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn = wrote: >=20 >> Hi all >>=20 >>=20 >> Last week I decided to upgrade my FreeBSD installation - it's been a = while >> (September 16 was last time). Unfortunately CURRENT does not boot and = cash >> in a weird way. Both 11-RELEASE and 12 CURRENT boot loader seems to = attempt >> to read blocks that exceeds the physical disk. Initially I through it = was a >> hard disk error - but after a "oh" experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical = boundaries >> of the disk (300GB disk). In order to rule out different options - I >> installed a vanilla 11-RELEASE on the 300G with a simple stripe - it = also >> gives the error but does boot - the LBA of the error is slightly = different >> on 11 CURRENT and comes up with LBA 921600 >>=20 >>=20 >> I have scanned all the disks for physical faults and there seems to = be none >> and I have tried doing a single disk installation on each disk - they = give >> the same error - Does anybody have any idea? Included Photos as = sometimes it >> get through to the actual boot menu but then crash in another place >>=20 >>=20 >> I have some images - but they are 2 bit for the mailing list ;-) >=20 >=20 > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 >=20 > Would be nice if you tell more about the system. CPU? dmesg? > The 11-RELEASE did that boot from the same disk? In the mentioned = issue there is the case that gptzfsboot does recognize a secondary disk = (can be configured as mirror), but not the first. >=20 > As you say UFS works, the bug might be in the gptzfsboot code, because = that is not used for UFS. >=20 There is another possible test scenario - to create pool on BSD labeled = disk, so we can see if it is just about the zfs code itself or rather = related to GPT. Or vice versa, try ufs on GPT labeled disk. rgds, toomas From owner-freebsd-current@freebsd.org Wed Feb 8 12:51:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE828CD6C98 for ; Wed, 8 Feb 2017 12:51:33 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFD321A07 for ; Wed, 8 Feb 2017 12:51:32 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cbRib-0005H8-47; Wed, 08 Feb 2017 13:51:30 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Thomas Sparrevohn" , "FreeBSD Current" Subject: Re: gptzfsboot trouble References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002201d28208$85492bc0$8fdb8340$@btinternet.com> Date: Wed, 08 Feb 2017 13:51:28 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <002201d28208$85492bc0$8fdb8340$@btinternet.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 18b3e585b0ef946fc0f6ee9ab4fcc4ff X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 12:51:34 -0000 On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn wrote: > > The bug in the bugzilla could be related - what is weird is I have been > running this setup for years without issues - which I guess just shows > how good ye'ol FreeBSD still is ;-) Tried to run through the svn log but > could not immediately see anything that seemed to be related I was triggered on that bugzilla issue because of the wrong lba number. > Would the photos of the screen help? Everything helps. NB: please keep the mailinglist in the address list. There are more knowledgeable people there. Ronald. > -----Original Message----- > From: Ronald Klop [mailto:ronald-lists@klop.ws] > Sent: 08 February 2017 12:27 > To: FreeBSD-current@freebsd.org; Thomas Sparrevohn > > Subject: Re: gptzfsboot trouble > > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn > wrote: > >> Hi all >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a >> while (September 16 was last time). Unfortunately CURRENT does not >> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot >> loader seems to attempt to read blocks that exceeds the physical disk. >> Initially I through it was a hard disk error - but after a "oh" >> experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical >> boundaries of the disk (300GB disk). In order to rule out different >> options - I installed a vanilla 11-RELEASE on the 300G with a simple >> stripe - it also gives the error but does boot - the LBA of the error >> is slightly different on 11 CURRENT and comes up with LBA 921600 >> >> >> I have scanned all the disks for physical faults and there seems to be >> none and I have tried doing a single disk installation on each disk - >> they give the same error - Does anybody have any idea? Included Photos >> as sometimes it get through to the actual boot menu but then crash in >> another place >> >> >> I have some images - but they are 2 bit for the mailing list ;-) > > > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > Would be nice if you tell more about the system. CPU? dmesg? > The 11-RELEASE did that boot from the same disk? In the mentioned issue > there is the case that gptzfsboot does recognize a secondary disk (can > be configured as mirror), but not the first. > > As you say UFS works, the bug might be in the gptzfsboot code, because > that is not used for UFS. > > Regards, > Ronald. From owner-freebsd-current@freebsd.org Wed Feb 8 12:53:48 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 004EDCD6D52 for ; Wed, 8 Feb 2017 12:53:48 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BED431D7C for ; Wed, 8 Feb 2017 12:53:47 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cbRkn-0005hH-Dk; Wed, 08 Feb 2017 13:53:45 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Thomas Sparrevohn" , "FreeBSD Current" Subject: Re: gptzfsboot trouble References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002001d28207$d0d493a0$727dbae0$@btinternet.com> Date: Wed, 08 Feb 2017 13:53:44 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <002001d28207$d0d493a0$727dbae0$@btinternet.com> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 67ca9281b58cf5c8a5b2b1d981559170 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 12:53:48 -0000 On Wed, 08 Feb 2017 13:35:22 +0100, Thomas Sparrevohn wrote: > > What would help? Takes a little while as I have to rebuild to 11-RELEASE > each time? 12-CURRENT cashed either before the boot menu or immediately > after which could be unrelated - I have photos but they are quite big > e.g. > 4 MB You can't mail them as attachment, but you might put them on Dropbox or something else and link to them. > I suggest - > > 1) Single disk ZFS pool on the 320GB disks should allow for faster > dd wipes if needed > 2) Run 11-RELEASE initially in case the 12-CURRENT issues are > unrelated > > I send > Dmesg output > Gpart show > Gpart list > Zpool status > Camcontrol devlist > Anything else? That is a really good start for people to look further on. Did you update your boot blocks while updating? Regards, Ronald. > > > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Ronald Klop > Sent: 08 February 2017 12:27 > To: FreeBSD-current@freebsd.org; Thomas Sparrevohn > > Subject: Re: gptzfsboot trouble > > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn > wrote: > >> Hi all >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a >> while (September 16 was last time). Unfortunately CURRENT does not >> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot >> loader seems to attempt to read blocks that exceeds the physical disk. >> Initially I through it was a hard disk error - but after a "oh" >> experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical >> boundaries of the disk (300GB disk). In order to rule out different >> options - I installed a vanilla 11-RELEASE on the 300G with a simple >> stripe - it also gives the error but does boot - the LBA of the error >> is slightly different on 11 CURRENT and comes up with LBA 921600 >> >> >> I have scanned all the disks for physical faults and there seems to be >> none and I have tried doing a single disk installation on each disk - >> they give the same error - Does anybody have any idea? Included Photos >> as sometimes it get through to the actual boot menu but then crash in >> another place >> >> >> I have some images - but they are 2 bit for the mailing list ;-) > > > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > Would be nice if you tell more about the system. CPU? dmesg? > The 11-RELEASE did that boot from the same disk? In the mentioned issue > there is the case that gptzfsboot does recognize a secondary disk (can be > configured as mirror), but not the first. > > As you say UFS works, the bug might be in the gptzfsboot code, because > that > is not used for UFS. > > Regards, > Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 13:17:41 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2BCA1CD657B for ; Wed, 8 Feb 2017 13:17:41 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03B6C11E3 for ; Wed, 8 Feb 2017 13:17:41 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL2005004UR8700@st13p35im-asmtp002.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 13:17:40 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486559860; bh=ceJYMEUUqRMUfaHESOav6WWA9sOfriCoGhZ7JdEWTtg=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=A7DHd/qO7f3Rp53OMleBNyAcj/zUX+Pav05krNEMFbgpjpuDnO3VdRJ7z85TXNBdx Eqp7fft3Spr82rrmOZyWDesk+mAtFTef7gtWRZFPJx6Auk5Y6ePoh3lNqG/nGx1FeZ qHjAXy6eutQhBXiOZXMDrr2ShktwE32gVBjiY0TsUhuqZ/Ni7lzwVm9g0/AAxKxu7x iBoJZ15c93+/QD4pfAf2JIUbx618LU+Tt7lgD36YMdDS3ue7xB1bDsHdLyx0JOHRZE B9P5qK2nfPPZiNYVXJ16vzxH75g+Sqd48X6L+Nw8o5mHyrGzyEyuGX9Hq2YuTlM8lJ iiCkW41LFOiyw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL200M9S4XEEE20@st13p35im-asmtp002.me.com> for FreeBSD-current@freebsd.org; Wed, 08 Feb 2017 13:17:39 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-08_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=12 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702080131 From: Toomas Soome Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: gptzfsboot trouble Date: Wed, 08 Feb 2017 15:17:37 +0200 References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002201d28208$85492bc0$8fdb8340$@btinternet.com> To: FreeBSD Current In-reply-to: Message-id: <2F2FC064-7508-4BA2-96EE-820A4E1E9F64@me.com> X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 13:17:41 -0000 > On 8. veebr 2017, at 14:51, Ronald Klop wrote: >=20 > On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn = wrote: >=20 >>=20 >> The bug in the bugzilla could be related - what is weird is I have = been running this setup for years without issues - which I guess just = shows how good ye'ol FreeBSD still is ;-) Tried to run through the svn = log but could not immediately see anything that seemed to be related >=20 > I was triggered on that bugzilla issue because of the wrong lba = number. I would start from carte blanche. 1. extract/write down the GPT header content; especially = important/interesting ones are alternate LBA for backup label location = (and therefore the disk end), the sector size used by GPT. 2. verify we do get the same sector size used with BIOS INT13 and if we = can actually read the last sectors. This one is with catch - it implies = some coding with gptzfsboot just to try to extract the information, = fortunately the BIOS interface is simple enough to use and it should not = be too hard:) Based on the results, we can try to figure out what really is happening = there and why things break down. One possible hypothesis is: as you wrote, your disk is 3TB; now it *may* = be the actual BIOS INT13 interface to address higher sectors is just = buggy, and it just can be so that the zfsloader binary is stored towards = the disk end in case of zfs and therefore revealing the issue. Another way to verify this hypothesis is to create separate (smaller) = zroot partition at the beginning of the disk. Having older system sort = of points towards the possibility. Another thing - have you checked for BIOS updates?=20 rgds, toomas >=20 >> Would the photos of the screen help? >=20 > Everything helps. > NB: please keep the mailinglist in the address list. There are more = knowledgeable people there. >=20 > Ronald. >=20 >=20 >> -----Original Message----- >> From: Ronald Klop [mailto:ronald-lists@klop.ws] >> Sent: 08 February 2017 12:27 >> To: FreeBSD-current@freebsd.org; Thomas Sparrevohn = >> Subject: Re: gptzfsboot trouble >>=20 >> On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn = wrote: >>=20 >>> Hi all >>>=20 >>>=20 >>> Last week I decided to upgrade my FreeBSD installation - it's been a >>> while (September 16 was last time). Unfortunately CURRENT does not >>> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot >>> loader seems to attempt to read blocks that exceeds the physical = disk. >>> Initially I through it was a hard disk error - but after a "oh" >>> experience I realised that the >>> "gptzfsboot: error 4 lba 921592" is actually beyond the physical >>> boundaries of the disk (300GB disk). In order to rule out different >>> options - I installed a vanilla 11-RELEASE on the 300G with a simple >>> stripe - it also gives the error but does boot - the LBA of the = error >>> is slightly different on 11 CURRENT and comes up with LBA 921600 >>>=20 >>>=20 >>> I have scanned all the disks for physical faults and there seems to = be >>> none and I have tried doing a single disk installation on each disk = - >>> they give the same error - Does anybody have any idea? Included = Photos >>> as sometimes it get through to the actual boot menu but then crash = in >>> another place >>>=20 >>>=20 >>> I have some images - but they are 2 bit for the mailing list ;-) >>=20 >>=20 >> Can it be related to this issue? >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 >>=20 >> Would be nice if you tell more about the system. CPU? dmesg? >> The 11-RELEASE did that boot from the same disk? In the mentioned = issue there is the case that gptzfsboot does recognize a secondary disk = (can be configured as mirror), but not the first. >>=20 >> As you say UFS works, the bug might be in the gptzfsboot code, = because that is not used for UFS. >>=20 >> Regards, >> Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 14:20:57 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3285ACD6876 for ; Wed, 8 Feb 2017 14:20:57 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout07.bt.lon5.cpcloud.co.uk (rgout07.bt.lon5.cpcloud.co.uk [65.20.0.157]) by mx1.freebsd.org (Postfix) with ESMTP id BFD881A40 for ; Wed, 8 Feb 2017 14:20:55 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 86.150.65.0 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2017.2.8.132119:17:7.944, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __REFERENCES, __IN_REP_TO, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __CTYPE_MULTIPART_MIXED, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __MIME_TEXT_P2, __HAS_ATTACHMENT1, TXT_ATTACHED, __ANY_URI, __HTTPS_URI, __URI_WITH_PATH, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __CASH, __CP_MEDIA_BODY, __CP_URI_IN_BODY, __FRAUD_CONTACT_ADDY, __C230066_P5, __SUBJ_ALPHA_NEGATE, __URI_IN_BODY, __FORWARDED_MSG, BODY_SIZE_10000_PLUS, __ATTACHMENT_SIZE_0_10K, __HAS_ATTACHMENT2, MULTIPLE_APP_ATT, __MIME_TEXT_P1, __URI_NS, HTML_00_01, HTML_00_10, __FRAUD_MONEY_CURRENCY, __FRAUD_WEBMAIL, __OUTLOOK_MUA, __HAS_ATTACHMENT, IN_REP_TO, __MIME_TEXT_P, FORGED_MUA_OUTLOOK, REFERENCES, MSG_THREAD, __TO_REAL_NAMES, LEGITIMATE_SIGNS Received: from ThomasPC (86.150.65.0) by rgout07.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as Thomas.Sparrevohn) id 58482FD7059231E0; Wed, 8 Feb 2017 14:19:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1486563656; bh=XjcWcb8fVy6GguBFnkPOUnD0KCRb+qUe92IbSLGXir8=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:X-Mailer; b=HwlTuej8v0YNFLJ1IrW+sQWzIyOj97sf7AyT3PBdzErIEZ8ShyWBliUbAFJgHa4eSSX0XynNJg/QDr0OFJYxxKDVLOou85gmF46gyT5WeemFgDfS5hNwW8XPWODxhXxjpAFIp59eMnYjeUtdZWZFUbqciPAEgVjG2qesbKDcR1M= From: "Thomas Sparrevohn" To: "'Ronald Klop'" , "'FreeBSD Current'" References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002201d28208$85492bc0$8fdb8340$@btinternet.com> In-Reply-To: Subject: RE: gptzfsboot trouble Date: Wed, 8 Feb 2017 14:19:31 -0000 Message-ID: <000501d28216$5f6e9620$1e4bc260$@btinternet.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0006_01D28216.5F6F0B50" X-Mailer: Microsoft Outlook 15.0 Thread-index: AQJGBpsumuYIjmx3iyDp4DKqQEXNdQLi+afJAngLc7cC1cJRU6A2mRdA Content-language: en-gb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 14:20:57 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ok Basic data included -----Original Message----- From: Ronald Klop [mailto:ronald-lists@klop.ws]=20 Sent: 08 February 2017 12:51 To: Thomas Sparrevohn ; FreeBSD = Current Subject: Re: gptzfsboot trouble On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn = wrote: > > The bug in the bugzilla could be related - what is weird is I have = been =20 > running this setup for years without issues - which I guess just shows = =20 > how good ye'ol FreeBSD still is ;-) Tried to run through the svn log = but =20 > could not immediately see anything that seemed to be related I was triggered on that bugzilla issue because of the wrong lba number. > Would the photos of the screen help? Everything helps. NB: please keep the mailinglist in the address list. There are more =20 knowledgeable people there. Ronald. > -----Original Message----- > From: Ronald Klop [mailto:ronald-lists@klop.ws] > Sent: 08 February 2017 12:27 > To: FreeBSD-current@freebsd.org; Thomas Sparrevohn =20 > > Subject: Re: gptzfsboot trouble > > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn =20 > wrote: > >> Hi all >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a >> while (September 16 was last time). Unfortunately CURRENT does not >> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot >> loader seems to attempt to read blocks that exceeds the physical = disk. >> Initially I through it was a hard disk error - but after a "oh" >> experience I realised that the >> "gptzfsboot: error 4 lba 921592" is actually beyond the physical >> boundaries of the disk (300GB disk). In order to rule out different >> options - I installed a vanilla 11-RELEASE on the 300G with a simple >> stripe - it also gives the error but does boot - the LBA of the error >> is slightly different on 11 CURRENT and comes up with LBA 921600 >> >> >> I have scanned all the disks for physical faults and there seems to = be >> none and I have tried doing a single disk installation on each disk - >> they give the same error - Does anybody have any idea? Included = Photos >> as sometimes it get through to the actual boot menu but then crash in >> another place >> >> >> I have some images - but they are 2 bit for the mailing list ;-) > > > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 > > Would be nice if you tell more about the system. CPU? dmesg? > The 11-RELEASE did that boot from the same disk? In the mentioned = issue =20 > there is the case that gptzfsboot does recognize a secondary disk (can = =20 > be configured as mirror), but not the first. > > As you say UFS works, the bug might be in the gptzfsboot code, because = =20 > that is not used for UFS. > > Regards, > Ronald. ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: application/octet-stream; name="camcontrol_devlist" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="camcontrol_devlist" at scbus0 target 0 lun 0 (cd0,pass0)=0A= at scbus5 target 0 lun 0 = (pass1,ada0)=0A= at scbus6 target 0 lun 0 (pass2,ada1)=0A= at scbus7 target 0 lun 0 (pass3,ada2)=0A= at scbus8 target 0 lun 0 (pass4,ada3)=0A= at scbus9 target 0 lun 0 (pass5,ada4)=0A= at scbus10 target 0 lun 0 = (pass6,ada5)=0A= at scbus11 target 0 lun 0 (pass7,ses0)=0A= at scbus12 target 0 lun 0 (da0,pass8)=0A= at scbus13 target 0 lun 0 (da2,pass10)=0A= at scbus13 target 0 lun 1 = (ses1,pass11)=0A= at scbus14 target 0 lun 0 (da1,pass9)=0A= ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: application/octet-stream; name="camcontrol_identify" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="camcontrol_identify" pass2: ATA8-ACS SATA 2.x device=0A= pass2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= =0A= protocol ATA/ATAPI-8 SATA 2.x=0A= device model Hitachi HDP725032GLA360=0A= firmware revision GM3OA52A=0A= serial number GEB030RG03EZZH=0A= WWN 5000cca32bc191aa=0A= cylinders 16383=0A= heads 16=0A= sectors/track 63=0A= sector size logical 512, physical 512, offset 0=0A= LBA supported 268435455 sectors=0A= LBA48 supported 625142448 sectors=0A= PIO supported PIO4=0A= DMA supported WDMA2 UDMA6 =0A= media RPM 7200=0A= =0A= Feature Support Enabled Value Vendor=0A= read ahead yes yes=0A= write cache yes yes=0A= flush cache yes yes=0A= overlap no=0A= Tagged Command Queuing (TCQ) no no=0A= Native Command Queuing (NCQ) yes 32 tags=0A= NCQ Queue Management no=0A= NCQ Streaming no=0A= Receive & Send FPDMA Queued no=0A= SMART yes yes=0A= microcode download yes yes=0A= security yes no=0A= power management yes yes=0A= advanced power management yes no 0/0x00=0A= automatic acoustic management yes yes 254/0xFE 128/0x80=0A= media status notification no no=0A= power-up in Standby yes no=0A= write-read-verify no no=0A= unload no no=0A= general purpose logging yes yes=0A= free-fall no no=0A= Data Set Management (DSM/TRIM) no=0A= Host Protected Area (HPA) yes no 625142448/625142448=0A= HPA - Security no=0A= ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.txt" Waiting (max 60 seconds) for system process `vnlru' to stop... done=0A= Waiting (max 60 seconds) for system process `bufdaemon' to stop... done=0A= Waiting (max 60 seconds) for system process `syncer' to stop... =0A= Syncing disks, vnodes remaining... 0 0 0 0 0 0 0 0 0 0 0 done=0A= All buffers synced.=0A= Copyright (c) 1992-2016 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD is a registered trademark of The FreeBSD Foundation.=0A= FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016=0A= root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64=0A= FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on = LLVM 3.8.0)=0A= VT(vga): resolution 640x480=0A= CPU: Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz (3208.03-MHz = K8-class CPU)=0A= Origin=3D"GenuineIntel" Id=3D0x106a5 Family=3D0x6 Model=3D0x1a = Stepping=3D5=0A= = Features=3D0xbfebfbff=0A= = Features2=3D0x98e3bd=0A= AMD Features=3D0x28100800=0A= AMD Features2=3D0x1=0A= VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID=0A= TSC: P-state invariant, performance statistics=0A= real memory =3D 12884901888 (12288 MB)=0A= avail memory =3D 12401463296 (11826 MB)=0A= Event timer "LAPIC" quality 400=0A= ACPI APIC Table: =0A= FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs=0A= FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads=0A= random: unblocking device.=0A= ioapic0 irqs 0-23 on motherboard=0A= random: entropy device external interface=0A= kbd1 at kbdmux0=0A= netmap: loaded module=0A= module_register_init: MOD_LOAD (vesa, 0xffffffff8101c950, 0) error 19=0A= vtvga0: on motherboard=0A= cryptosoft0: on motherboard=0A= acpi0: on motherboard=0A= acpi0: Power Button (fixed)=0A= cpu0: on acpi0=0A= cpu1: on acpi0=0A= cpu2: on acpi0=0A= cpu3: on acpi0=0A= cpu4: on acpi0=0A= cpu5: on acpi0=0A= cpu6: on acpi0=0A= cpu7: on acpi0=0A= attimer0: port 0x40-0x43 irq 0 on acpi0=0A= Timecounter "i8254" frequency 1193182 Hz quality 0=0A= Event timer "i8254" frequency 1193182 Hz quality 100=0A= atrtc0: port 0x70-0x71 irq 8 on acpi0=0A= Event timer "RTC" frequency 32768 Hz quality 0=0A= hpet0: iomem 0xfed00000-0xfed003ff on acpi0=0A= Timecounter "HPET" frequency 14318180 Hz quality 950=0A= Event timer "HPET" frequency 14318180 Hz quality 350=0A= Event timer "HPET1" frequency 14318180 Hz quality 340=0A= Event timer "HPET2" frequency 14318180 Hz quality 340=0A= Event timer "HPET3" frequency 14318180 Hz quality 340=0A= Timecounter "ACPI-fast" frequency 3579545 Hz quality 900=0A= acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0=0A= pcib0: port 0xcf8-0xcff on acpi0=0A= pci0: on pcib0=0A= pcib1: at device 1.0 on pci0=0A= pci1: on pcib1=0A= pcib2: at device 3.0 on pci0=0A= pci2: on pcib2=0A= vgapci0: port 0xe000-0xe0ff mem = 0xd0000000-0xdfffffff,0xcf800000-0xcfffffff,0xfbc00000-0xfbc3ffff irq 16 = at device 0.0 on pci2=0A= vgapci0: Boot video device=0A= hdac0: mem 0xfbe00000-0xfbe03fff irq 17 at = device 0.1 on pci2=0A= pcib3: at device 7.0 on pci0=0A= pci3: on pcib3=0A= pcib4: at device 9.0 on pci0=0A= pci4: on pcib4=0A= pci0: at device 20.0 (no driver = attached)=0A= pci0: at device 20.1 (no driver = attached)=0A= pci0: at device 20.2 (no driver = attached)=0A= pci0: at device 20.3 (no driver = attached)=0A= uhci0: port 0xa400-0xa41f = irq 16 at device 26.0 on pci0=0A= uhci0: LegSup =3D 0x2f00=0A= usbus0 on uhci0=0A= uhci1: port 0xa480-0xa49f = irq 21 at device 26.1 on pci0=0A= uhci1: LegSup =3D 0x2f00=0A= usbus1 on uhci1=0A= uhci2: port 0xa800-0xa81f = irq 19 at device 26.2 on pci0=0A= uhci2: LegSup =3D 0x2f00=0A= usbus2 on uhci2=0A= ehci0: mem = 0xf9e00000-0xf9e003ff irq 18 at device 26.7 on pci0=0A= usbus3: EHCI version 1.0=0A= usbus3 on ehci0=0A= hdac1: mem 0xfa000000-0xfa003fff irq 22 = at device 27.0 on pci0=0A= pcib5: irq 17 at device 28.0 on pci0=0A= pcib5: [GIANT-LOCKED]=0A= pcib6: irq 16 at device 28.1 on pci0=0A= pcib6: [GIANT-LOCKED]=0A= pci5: on pcib6=0A= bge0: mem 0xfb800000-0xfb80ffff irq 17 at device 0.0 on pci5=0A= bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E=0A= miibus0: on bge0=0A= brgphy0: PHY 1 on miibus0=0A= brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow=0A= bge0: Using defaults for TSO: 65518/35/2048=0A= bge0: Ethernet address: a4:ba:db:02:6f:a2=0A= pcib7: irq 18 at device 28.2 on pci0=0A= pcib7: [GIANT-LOCKED]=0A= pci6: on pcib7=0A= bge1: mem 0xfb600000-0xfb60ffff irq 18 at device 0.0 on pci6=0A= bge1: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E=0A= miibus1: on bge1=0A= brgphy1: PHY 1 on miibus1=0A= brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow=0A= bge1: Using defaults for TSO: 65518/35/2048=0A= bge1: Ethernet address: a4:ba:db:02:6f:a1=0A= pcib8: irq 19 at device 28.3 on pci0=0A= pcib8: [GIANT-LOCKED]=0A= pci7: on pcib8=0A= atapci0: port = 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f = mem 0xfb200000-0xfb201fff irq 19 at device 0.0 on pci7=0A= ahci0: at channel -1 on atapci0=0A= ahci0: AHCI v1.00 with 2 3Gbps ports, Port Multiplier supported=0A= ahci0: quirks=3D0x1=0A= ahcich0: at channel 0 on ahci0=0A= ahcich1: at channel 1 on ahci0=0A= ata2: at channel 0 on atapci0=0A= pcib9: irq 16 at device 28.5 on pci0=0A= pcib9: [GIANT-LOCKED]=0A= pci8: on pcib9=0A= siis0: port 0xcc00-0xcc7f mem = 0xfb000000-0xfb00007f,0xfae00000-0xfae03fff irq 17 at device 0.0 on pci8=0A= siisch0: at channel 0 on siis0=0A= siisch1: at channel 1 on siis0=0A= uhci3: port 0xa880-0xa89f = irq 23 at device 29.0 on pci0=0A= uhci3: LegSup =3D 0x2f00=0A= usbus4 on uhci3=0A= uhci4: port 0xac00-0xac1f = irq 19 at device 29.1 on pci0=0A= uhci4: LegSup =3D 0x2f00=0A= usbus5 on uhci4=0A= uhci5: port 0xb000-0xb01f = irq 18 at device 29.2 on pci0=0A= uhci5: LegSup =3D 0x2f00=0A= usbus6 on uhci5=0A= ehci1: mem = 0xfa200000-0xfa2003ff irq 23 at device 29.7 on pci0=0A= usbus7: EHCI version 1.0=0A= usbus7 on ehci1=0A= pcib10: at device 30.0 on pci0=0A= pci9: on pcib10=0A= pci9: at device 2.0 (no driver attached)=0A= isab0: at device 31.0 on pci0=0A= isa0: on isab0=0A= ahci1: port = 0xb880-0xb887,0xb800-0xb803,0xb480-0xb487,0xb400-0xb403,0xb080-0xb09f = mem 0xfa400000-0xfa4007ff irq 19 at device 31.2 on pci0=0A= ahci1: AHCI v1.20 with 6 3Gbps ports, Port Multiplier not supported=0A= ahcich2: at channel 0 on ahci1=0A= ahcich3: at channel 1 on ahci1=0A= ahcich4: at channel 2 on ahci1=0A= ahcich5: at channel 3 on ahci1=0A= ahcich6: at channel 4 on ahci1=0A= ahcich7: at channel 5 on ahci1=0A= ahciem0: on ahci1=0A= acpi_button0: on acpi0=0A= qpi0: on motherboard=0A= pcib11: pcibus 255 on qpi0=0A= pci10: on pcib11=0A= orm0: at iomem 0xc0000-0xcffff on isa0=0A= atkbdc0: at port 0x60,0x64 on isa0=0A= atkbd0: irq 1 on atkbdc0=0A= kbd0 at atkbd0=0A= atkbd0: [GIANT-LOCKED]=0A= ppc0: cannot reserve I/O port range=0A= uart0: <16550 or compatible> at port 0x3f8 irq 4 flags 0x10 on isa0=0A= est0: on cpu0=0A= est1: on cpu1=0A= est2: on cpu2=0A= est3: on cpu3=0A= est4: on cpu4=0A= est5: on cpu5=0A= est6: on cpu6=0A= est7: on cpu7=0A= usbus0: 12Mbps Full Speed USB v1.0=0A= ZFS filesystem version: 5=0A= ZFS storage pool version: features support (5000)=0A= Timecounters tick every 1.000 msec=0A= nvme cam probe device init=0A= hdacc0: at cad 0 on hdac0=0A= hdaa0: at nid 1 on hdacc0=0A= pcm0: at nid 3 on hdaa0=0A= pcm1: at nid 5 on hdaa0=0A= pcm2: at nid 7 on hdaa0=0A= pcm3: at nid 9 on hdaa0=0A= pcm4: at nid 11 on hdaa0=0A= pcm5: at nid 13 on hdaa0=0A= hdacc1: at cad 0 on hdac1=0A= hdaa1: at nid 1 on hdacc1=0A= pcm6: at nid 20,22,21,23,27 and = 24,25,26 on hdaa1=0A= pcm7: at nid 30 on hdaa1=0A= pcm8: at nid 17 on hdaa1=0A= usbus1: 12Mbps Full Speed USB v1.0=0A= usbus2: 12Mbps Full Speed USB v1.0=0A= ugen0.1: at usbus0=0A= uhub0: on usbus0=0A= ugen1.1: at usbus1=0A= uhub1: on usbus1=0A= ugen2.1: at usbus2=0A= uhub2: on usbus2=0A= usbus3: 480Mbps High Speed USB v2.0=0A= usbus4: 12Mbps Full Speed USB v1.0=0A= usbus5: 12Mbps Full Speed USB v1.0=0A= ugen3.1: at usbus3=0A= uhub3: on usbus3=0A= ugen4.1: at usbus4=0A= uhub4: on usbus4=0A= ugen5.1: at usbus5=0A= uhub5: on usbus5=0A= usbus6: 12Mbps Full Speed USB v1.0=0A= usbus7: 480Mbps High Speed USB v2.0=0A= ugen6.1: at usbus6=0A= uhub6: on usbus6=0A= ugen7.1: at usbus7=0A= uhub7: on usbus7=0A= uhub0: 2 ports with 2 removable, self powered=0A= uhub1: 2 ports with 2 removable, self powered=0A= uhub2: 2 ports with 2 removable, self powered=0A= uhub4: 2 ports with 2 removable, self powered=0A= uhub5: 2 ports with 2 removable, self powered=0A= uhub6: 2 ports with 2 removable, self powered=0A= ses0 at ahciem0 bus 0 scbus11 target 0 lun 0=0A= ses0: SEMB S-E-S 2.00 device=0A= ses0: SEMB SES Device=0A= ada0 at ahcich2 bus 0 scbus5 target 0 lun 0=0A= ada0: ACS-2 ATA SATA 3.x device=0A= ada0: Serial Number S1DFNEAD904333V=0A= ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes)=0A= ada0: Command Queueing enabled=0A= ada0: 238475MB (488397168 512 byte sectors)=0A= ada0: quirks=3D0x3<4K,NCQ_TRIM_BROKEN>=0A= ada1 at ahcich3 bus 0 scbus6 target 0 lun 0=0A= ada1: ATA8-ACS SATA 2.x device=0A= ada1: Serial Number GEB030RG03EZZH=0A= ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= ada1: Command Queueing enabled=0A= ada1: 305245MB (625142448 512 byte sectors)=0A= ada2 at ahcich4 bus 0 scbus7 target 0 lun 0=0A= ada2: ATA-7 SATA 2.x device=0A= ada2: Serial Number S1JNJ90Z104658=0A= ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= ada2: Command Queueing enabled=0A= ada2: 610480MB (1250263728 512 byte sectors)=0A= ada3 at ahcich5 bus 0 scbus8 target 0 lun 0=0A= ada3: ATA8-ACS SATA 2.x device=0A= ada3: Serial Number GEB330RC0ASTSF=0A= ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= ada3: Command Queueing enabled=0A= ada3: 305245MB (625142448 512 byte sectors)=0A= ada4 at ahcich6 bus 0 scbus9 target 0 lun 0=0A= ada4: ATA-7 SATA 2.x device=0A= ada4: Serial Number S1JNJ90Z104652=0A= ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= ada4: Command Queueing enabled=0A= ada4: 610480MB (1250263728 512 byte sectors)=0A= ada5 at ahcich7 bus 0 scbus10 target 0 lun 0=0A= ada5: ATA8-ACS SATA 2.x device=0A= ada5: Serial Number GECR34RF20X7LE=0A= ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)=0A= ada5: Command Queueing enabled=0A= ada5: 305245MB (625142448 512 byte sectors)=0A= SMP: AP CPU #1 Launched!=0A= SMP: AP CPU #3 Launched!=0A= SMP: AP CPU #4 Launched!=0A= SMP: AP CPU #2 Launched!=0A= SMP: AP CPU #5 Launched!=0A= SMP: AP CPU #6 Launched!=0A= SMP: AP CPU #7 Launched!=0A= cd0 at ahcich0 bus 0 scbus0 target 0 lun 0=0A= cd0: Removable CD-ROM SCSI device=0A= cd0: Serial Number R4606GFZ14166700=0A= cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO = 8192bytes)=0A= cd0: Attempt to query device size failed: NOT READY, Medium not present = - tray closed=0A= Timecounter "TSC-low" frequency 1604016454 Hz quality 1000=0A= Trying to mount root from zfs:zroot/ROOT/default []...=0A= Root mount waiting for: usbus7 usbus3=0A= Root mount waiting for: usbus7 usbus3=0A= uhub3: 6 ports with 6 removable, self powered=0A= uhub7: 6 ports with 6 removable, self powered=0A= Root mount waiting for: usbus7 usbus3=0A= ugen3.2: at usbus3=0A= uhub8: = on usbus3=0A= Root mount waiting for: usbus7 usbus3=0A= uhub8: 4 ports with 4 removable, self powered=0A= ugen5.2: at usbus5=0A= ukbd0: on = usbus5=0A= ugen0.2: at usbus0=0A= kbd2 at ukbd0=0A= ugen7.2: at usbus7=0A= umass0: on usbus7=0A= umass0: SCSI over Bulk-Only; quirks =3D 0x8100=0A= umass0:12:0: Attached to scbus12=0A= da0 at umass-sim0 bus 0 scbus12 target 0 lun 0=0A= da0: Removable Direct Access SPC-4 SCSI device=0A= da0: Serial Number AC220B7F2408000000000000000665=0A= da0: 40.000MB/s transfers=0A= da0: 29620MB (60661760 512 byte sectors)=0A= da0: quirks=3D0x12=0A= ugen3.3: at usbus3=0A= uhub9: on usbus3=0A= uhub9: 3 ports with 0 removable, self powered=0A= Root mount waiting for: usbus3=0A= ugen3.4: at usbus3=0A= ukbd1: = on usbus3=0A= kbd3 at ukbd1=0A= ugen3.5: at usbus3=0A= Root mount waiting for: usbus3=0A= ugen3.6: at usbus3=0A= uhub10: = on usbus3=0A= uhub10: MTT enabled=0A= Root mount waiting for: usbus3=0A= uhub10: 3 ports with 2 removable, self powered=0A= Root mount waiting for: usbus3=0A= Root mount waiting for: usbus3=0A= Root mount waiting for: usbus3=0A= Root mount waiting for: usbus3=0A= ugen3.7: at usbus3=0A= umass1: on usbus3=0A= umass1: SCSI over Bulk-Only; quirks =3D 0xc001=0A= umass1:13:1: Attached to scbus13=0A= ugen3.8: at usbus3=0A= Root mount waiting for: usbus3=0A= Root mount waiting for: usbus3=0A= ugen3.9: at usbus3=0A= umass2: on = usbus3=0A= umass2: SCSI over Bulk-Only; quirks =3D 0x8100=0A= umass2:14:2: Attached to scbus14=0A= (probe1:umass-sim2:2:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 = 10 00 00 =0A= (probe1:umass-sim2:2:0:0): CAM status: SCSI Status Error=0A= (probe1:umass-sim2:2:0:0): SCSI status: Check Condition=0A= (probe1:umass-sim2:2:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid = command operation code)=0A= (probe1:umass-sim2:2:0:0): Error 22, Unretryable error=0A= da1 at umass-sim2 bus 2 scbus14 target 0 lun 0=0A= da1: Fixed Direct Access SPC-3 SCSI device=0A= da1: Serial Number 00000000e4ed3c7b20df=0A= da1: 40.000MB/s transfers=0A= da1: 953869MB (1953525168 512 byte sectors)=0A= da1: quirks=3D0x2=0A= da2 at umass-sim1 bus 1 scbus13 target 0 lun 0=0A= da2: Fixed Direct Access SPC-4 SCSI device=0A= da2: Serial Number 575831314142343255325654=0A= da2: 40.000MB/s transfers=0A= da2: 953837MB (1953458176 512 byte sectors)=0A= da2: quirks=3D0x2=0A= ses1 at umass-sim1 bus 1 scbus13 target 0 lun 1=0A= ses1: Fixed Enclosure Services SPC-4 SCSI device=0A= ses1: Serial Number 575831314142343255325654=0A= ses1: 40.000MB/s transfers=0A= ses1: SCSI-3 ENC Device=0A= bge0: link state changed to DOWN=0A= bge0: link state changed to UP=0A= uhid0: on = usbus0=0A= uhid1: = on usbus3=0A= uhid2: on = usbus5=0A= ums0: on = usbus5=0A= ums1: = on usbus3=0A= ums1: 3 buttons and [XY] coordinates ID=3D2=0A= ums0: 16 buttons and [XYZT] coordinates ID=3D2=0A= ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: application/octet-stream; name="gpart.list.ada1" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="gpart.list.ada1" Geom name: ada1=0A= modified: false=0A= state: OK=0A= fwheads: 16=0A= fwsectors: 63=0A= last: 625142407=0A= first: 40=0A= entries: 152=0A= scheme: GPT=0A= Providers:=0A= 1. Name: ada1p1=0A= Mediasize: 524288 (512K)=0A= Sectorsize: 512=0A= Stripesize: 0=0A= Stripeoffset: 20480=0A= Mode: r0w0e0=0A= rawuuid: 6b80da2c-ee00-11e6-ba10-a4badb026fa2=0A= rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f=0A= label: gptboot0=0A= length: 524288=0A= offset: 20480=0A= type: freebsd-boot=0A= index: 1=0A= end: 1063=0A= start: 40=0A= 2. Name: ada1p2=0A= Mediasize: 2147483648 (2.0G)=0A= Sectorsize: 512=0A= Stripesize: 0=0A= Stripeoffset: 1048576=0A= Mode: r1w1e0=0A= rawuuid: 6ba4e4bf-ee00-11e6-ba10-a4badb026fa2=0A= rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b=0A= label: swap0=0A= length: 2147483648=0A= offset: 1048576=0A= type: freebsd-swap=0A= index: 2=0A= end: 4196351=0A= start: 2048=0A= 3. Name: ada1p3=0A= Mediasize: 317924048896 (296G)=0A= Sectorsize: 512=0A= Stripesize: 0=0A= Stripeoffset: 2148532224=0A= Mode: r1w1e1=0A= rawuuid: 6bc4642f-ee00-11e6-ba10-a4badb026fa2=0A= rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b=0A= label: zfs0=0A= length: 317924048896=0A= offset: 2148532224=0A= type: freebsd-zfs=0A= index: 3=0A= end: 625141759=0A= start: 4196352=0A= Consumers:=0A= 1. Name: ada1=0A= Mediasize: 320072933376 (298G)=0A= Sectorsize: 512=0A= Mode: r2w2e3=0A= =0A= ------=_NextPart_000_0006_01D28216.5F6F0B50 Content-Type: application/octet-stream; name="gpart.show.ada1" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="gpart.show.ada1" =3D> 40 625142368 ada1 GPT (298G)=0A= 40 1024 1 freebsd-boot (512K)=0A= 1064 984 - free - (492K)=0A= 2048 4194304 2 freebsd-swap (2.0G)=0A= 4196352 620945408 3 freebsd-zfs (296G)=0A= 625141760 648 - free - (324K)=0A= =0A= ------=_NextPart_000_0006_01D28216.5F6F0B50-- From owner-freebsd-current@freebsd.org Wed Feb 8 14:52:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC351CD6216 for ; Wed, 8 Feb 2017 14:52:53 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from rgout02.bt.lon5.cpcloud.co.uk (rgout0201.bt.lon5.cpcloud.co.uk [65.20.0.200]) by mx1.freebsd.org (Postfix) with ESMTP id 5825BDCF for ; Wed, 8 Feb 2017 14:52:52 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) X-OWM-Source-IP: 86.150.65.0 (GB) X-OWM-Env-Sender: Thomas.Sparrevohn@btinternet.com X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2017.2.8.142115:17:7.944, ip=, rules=__HAS_FROM, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __REFERENCES, __IN_REP_TO, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __HAS_MSGID, __SANE_MSGID, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_MAILER, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __HTTPS_URI, __URI_WITH_PATH, __CANPHARM_UNSUB_LINK, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __CASH, __CP_MEDIA_BODY, __CP_URI_IN_BODY, __SUBJ_ALPHA_NEGATE, __MULTIPLE_URI_TEXT, __URI_IN_BODY, __FORWARDED_MSG, __NO_HTML_TAG_RAW, BODY_SIZE_5000_5999, __MIME_TEXT_P1, __MIME_TEXT_ONLY, __URI_NS, HTML_00_01, HTML_00_10, __FRAUD_MONEY_CURRENCY, __FRAUD_WEBMAIL, __OUTLOOK_MUA, __PHISH_SPEAR_STRUCTURE_1, IN_REP_TO, __MIME_TEXT_P, FORGED_MUA_OUTLOOK, REFERENCES, BODY_SIZE_7000_LESS, MSG_THREAD, __TO_REAL_NAMES, LEGITIMATE_SIGNS Received: from ThomasPC (86.150.65.0) by rgout02.bt.lon5.cpcloud.co.uk (9.0.019.13-1) (authenticated as Thomas.Sparrevohn) id 58482B9705B28822; Wed, 8 Feb 2017 14:49:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1486565573; bh=iRhofV6UwhuCm71w9XOsHNfZ08jpJ8LlwA0NT+bUPcI=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:X-Mailer; b=P85f6ZZMy9BwqJGvxvoyq+1tGHbvjxwztnxB7z6EybYgNJ7a9dMRuGl849pHi1mUoixOUxh0VR6GzkiXCD1MQOwws73yMjPw7j+ShZOrfutbvTbD9u4X0eOyh6nQpb4QDXB0W4btPjUdE/R8oOOKsxDOT1gGDRwgGNJgtaoqvkY= From: "Thomas Sparrevohn" To: "'Toomas Soome'" , "'FreeBSD Current'" References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <002201d28208$85492bc0$8fdb8340$@btinternet.com> <2F2FC064-7508-4BA2-96EE-820A4E1E9F64@me.com> In-Reply-To: <2F2FC064-7508-4BA2-96EE-820A4E1E9F64@me.com> Subject: RE: gptzfsboot trouble Date: Wed, 8 Feb 2017 14:49:20 -0000 Message-ID: <001f01d2821a$88d77d70$9a867850$@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-index: AQJGBpsumuYIjmx3iyDp4DKqQEXNdQLi+afJAngLc7cC1cJRUwK0M4sdoCD+3MA= Content-language: en-gb X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 14:52:53 -0000 The disk is small 320GB but I have tried on a vanilla 600GB drive - same issue - as a matter of fact I have tried on all 5 SATA drives - but I suspect that BIOS could be an issue but I have not seen any updates for years (old machine) I have tried with single drive pools on both 600GB drive and 320GB drive - same issue - I wonder if it could be a memory error - I think I have an original resource CD somewhere would make sense to try a diagnostics from that -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Toomas Soome Sent: 08 February 2017 13:18 To: FreeBSD Current Subject: Re: gptzfsboot trouble > On 8. veebr 2017, at 14:51, Ronald Klop wrote: > > On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn wrote: > >> >> The bug in the bugzilla could be related - what is weird is I have >> been running this setup for years without issues - which I guess just >> shows how good ye'ol FreeBSD still is ;-) Tried to run through the >> svn log but could not immediately see anything that seemed to be >> related > > I was triggered on that bugzilla issue because of the wrong lba number. I would start from carte blanche. 1. extract/write down the GPT header content; especially important/interesting ones are alternate LBA for backup label location (and therefore the disk end), the sector size used by GPT. 2. verify we do get the same sector size used with BIOS INT13 and if we can actually read the last sectors. This one is with catch - it implies some coding with gptzfsboot just to try to extract the information, fortunately the BIOS interface is simple enough to use and it should not be too hard:) Based on the results, we can try to figure out what really is happening there and why things break down. One possible hypothesis is: as you wrote, your disk is 3TB; now it *may* be the actual BIOS INT13 interface to address higher sectors is just buggy, and it just can be so that the zfsloader binary is stored towards the disk end in case of zfs and therefore revealing the issue. Another way to verify this hypothesis is to create separate (smaller) zroot partition at the beginning of the disk. Having older system sort of points towards the possibility. Another thing - have you checked for BIOS updates? rgds, toomas > >> Would the photos of the screen help? > > Everything helps. > NB: please keep the mailinglist in the address list. There are more knowledgeable people there. > > Ronald. > > >> -----Original Message----- >> From: Ronald Klop [mailto:ronald-lists@klop.ws] >> Sent: 08 February 2017 12:27 >> To: FreeBSD-current@freebsd.org; Thomas Sparrevohn >> >> Subject: Re: gptzfsboot trouble >> >> On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn wrote: >> >>> Hi all >>> >>> >>> Last week I decided to upgrade my FreeBSD installation - it's been a >>> while (September 16 was last time). Unfortunately CURRENT does not >>> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot >>> loader seems to attempt to read blocks that exceeds the physical disk. >>> Initially I through it was a hard disk error - but after a "oh" >>> experience I realised that the >>> "gptzfsboot: error 4 lba 921592" is actually beyond the physical >>> boundaries of the disk (300GB disk). In order to rule out different >>> options - I installed a vanilla 11-RELEASE on the 300G with a simple >>> stripe - it also gives the error but does boot - the LBA of the >>> error is slightly different on 11 CURRENT and comes up with LBA >>> 921600 >>> >>> >>> I have scanned all the disks for physical faults and there seems to >>> be none and I have tried doing a single disk installation on each >>> disk - they give the same error - Does anybody have any idea? >>> Included Photos as sometimes it get through to the actual boot menu >>> but then crash in another place >>> >>> >>> I have some images - but they are 2 bit for the mailing list ;-) >> >> >> Can it be related to this issue? >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 >> >> Would be nice if you tell more about the system. CPU? dmesg? >> The 11-RELEASE did that boot from the same disk? In the mentioned issue there is the case that gptzfsboot does recognize a secondary disk (can be configured as mirror), but not the first. >> >> As you say UFS works, the bug might be in the gptzfsboot code, because that is not used for UFS. >> >> Regards, >> Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 15:57:45 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EE10CD57CE for ; Wed, 8 Feb 2017 15:57:45 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CF0C1164A for ; Wed, 8 Feb 2017 15:57:44 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v18Fntl6031831 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 8 Feb 2017 17:49:59 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v18FicJ6037191 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 8 Feb 2017 17:44:38 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v18FiY1k037190 for freebsd-current@freebsd.org; Wed, 8 Feb 2017 17:44:34 +0200 (EET) (envelope-from oleg@opentransfer.com) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@opentransfer.com using -f From: "Oleg V. Nauman" To: freebsd-current@freebsd.org Subject: 'Protocol not supported' on linux socket call ( r313313 amd64 ) Date: Wed, 08 Feb 2017 17:44:34 +0200 Message-ID: <2628207.fWzAjJv2TV@asus.theweb.org.ua> Organization: Ecommerce LLC User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.10; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 15:57:45 -0000 After upgrading of current on amd64 box to r313313 I noticed that skype has stopped working. Below is the end of 'truss' output for skype: 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not supported' 36723: write(6,"@",1) = 1 (0x1) 36723: close(6) = 0 (0x0) 36723: close(5) = 0 (0x0) 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) 36723: linux_exit_group(0x1) 36723: process exit, rval = 1 My second current box ( r313090 i386 ) runs skype successfully. From owner-freebsd-current@freebsd.org Wed Feb 8 16:39:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F86ACD65A0 for ; Wed, 8 Feb 2017 16:39:53 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 283B21483; Wed, 8 Feb 2017 16:39:53 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg0-x242.google.com with SMTP id 194so15614030pgd.0; Wed, 08 Feb 2017 08:39:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2q20Ugno+Dj7y2atsiX6yhaqEKnBLp+GWaGrMBb5o4g=; b=tSF5twlRwcNHL9ABmbf/td9CJ6wTi8XNTJfb0tOSQXq5ZKthKJN368yo1++rRB2ZSi Il3qCu30wqqFEllh03aYRsnhGuCIrQi4BWTD9mAwLriSAelAz0burUHE4J+8qrO9tRG9 dJrXit5/6CBxo/q/7SZ6Hi6hIgfGJGFGTWc+Qezmm7AngmZT+5yyAOyD6ZQSMdiVNYK+ 7lFSZ8wTUtGn8a5H8T4+NsWyNgB7u1lL8t8+MKzINLwe9NqLo0pAEad434VvEqO+qFTQ LgswZX1Kd+cl4ESaQoG36GC2SKaEfiCCPo0YzK/ucp3nTFccJtENTRam6o5nMEU9MgfQ Xl5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2q20Ugno+Dj7y2atsiX6yhaqEKnBLp+GWaGrMBb5o4g=; b=IcAXdIomeCOAkCxTtE6Q5S1x9uyfjCMbf9AvyfkQj5fd+XUdKpbnzm6VifO798luk5 9Cho6ooL33RykiuDSlwYbmbPCBd3jLLdhn7ce0i9wHPnSToDIC5epXFDuNiu6M5scOQa 6Ysd3pQusPzRqxdNgQihQdeebmVhOyWOvHDobvmPuYxSYYJWJ47i8BUjr/ndlVzrN0yp 3DlWIv+e01mafIfTE4cINjZFbckdG6hFhrZ+92LUKfchh3KhT9PTlX5r0L2PlZRbcn4b oo5dBu9650l4e6KQsxhSUcgf5kMpww3gqwwcaJ9S+j8oTo3VEeyVLE09QGKZgZOCcpl1 rnhA== X-Gm-Message-State: AIkVDXK8reS7aN6YLiq9AEhqi/4l9z+LS/zASvPMcWPhdQjG1QXiCP1wdqPKFXZ2tkAIJw== X-Received: by 10.84.213.9 with SMTP id f9mr35376382pli.138.1486571992556; Wed, 08 Feb 2017 08:39:52 -0800 (PST) Received: from [192.168.20.13] (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id u29sm21793015pfl.17.2017.02.08.08.39.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 08:39:51 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) From: Ngie Cooper X-Mailer: iPhone Mail (14D27) In-Reply-To: <2628207.fWzAjJv2TV@asus.theweb.org.ua> Date: Wed, 8 Feb 2017 08:39:50 -0800 Cc: freebsd-current@freebsd.org, trasz@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> To: "Oleg V. Nauman" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 16:39:53 -0000 > On Feb 8, 2017, at 07:44, Oleg V. Nauman wrote: >=20 > After upgrading of current on amd64 box to r313313 I noticed that skype ha= s=20 > stopped working. > Below is the end of 'truss' output for skype: >=20 > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not=20 > supported' > 36723: write(6,"@",1) =3D 1 (0x1) > 36723: close(6) =3D 0 (0x0) > 36723: close(5) =3D 0 (0x0) > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) =3D 0 (0x0) > 36723: linux_exit_group(0x1) > 36723: process exit, rval =3D 1 >=20 > My second current box ( r313090 i386 ) runs skype successfully. Hi, Please try reverting r312988. Thanks! -Ngie= From owner-freebsd-current@freebsd.org Wed Feb 8 19:04:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70375CD54D6 for ; Wed, 8 Feb 2017 19:04:14 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-wr0-f169.google.com (mail-wr0-f169.google.com [209.85.128.169]) (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 1131ED5A; Wed, 8 Feb 2017 19:04:13 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-wr0-f169.google.com with SMTP id 89so66244525wrr.2; Wed, 08 Feb 2017 11:04:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=cP2IAoBkKSv9BG/JmVfmSjZl5gd7pFsCMOJpOwEQUHU=; b=bMHAqr4FIUZQsV9E9GLTnlQ7nHB+9qb8GudQmjq0BHEYllIAaAR/KMoZTr0kCbjNN+ EbwB25VdShTXXXRPTD4d4UMEio8fLujahG1PYzYhDof0iRcc9KO2tK8mpAT4ICqF610c uVXrvtVf7r5V+N1CF9dSbv1tIIc+GALKg14h0zKEyUD/EtuX7a0ZfJysYVxoXUOdAIzr R7KLaWbow+FuzSgtSEFavMJcanpIS8l2a8qpjdy/K9zAYN7p84HIIsQZshWDnbPm71Ag kf1AcTq0LIqiiwVOmVaskDAeseb9TxASdu0KnyM/e6DPcRBW0OSLNETLJfeVKPMbrBco X4Tw== X-Gm-Message-State: AIkVDXKpkQ6p/vuN/8qshAXQADmQQxgjXNXaj2Xd3aIUZMNnNoxOhstMLuDgc+/z5hxi3g== X-Received: by 10.223.134.253 with SMTP id 58mr24166562wry.46.1486573604571; Wed, 08 Feb 2017 09:06:44 -0800 (PST) Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com. [74.125.82.49]) by smtp.gmail.com with ESMTPSA id g5sm14050118wrd.0.2017.02.08.09.06.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 09:06:44 -0800 (PST) Received: by mail-wm0-f49.google.com with SMTP id v77so198545187wmv.0; Wed, 08 Feb 2017 09:06:44 -0800 (PST) X-Received: by 10.28.221.11 with SMTP id u11mr17803630wmg.75.1486573604241; Wed, 08 Feb 2017 09:06:44 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.80.152.82 with HTTP; Wed, 8 Feb 2017 09:06:43 -0800 (PST) In-Reply-To: <2628207.fWzAjJv2TV@asus.theweb.org.ua> References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> From: Conrad Meyer Date: Wed, 8 Feb 2017 09:06:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) To: "Oleg V. Nauman" Cc: freebsd-current , dchagin@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 19:04:14 -0000 Hi Oleg, It seems likely it is related to r313284. Best, Conrad On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman wrote: > After upgrading of current on amd64 box to r313313 I noticed that skype has > stopped working. > Below is the end of 'truss' output for skype: > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not > supported' > 36723: write(6,"@",1) = 1 (0x1) > 36723: close(6) = 0 (0x0) > 36723: close(5) = 0 (0x0) > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) > 36723: linux_exit_group(0x1) > 36723: process exit, rval = 1 > > My second current box ( r313090 i386 ) runs skype successfully. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 19:53:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8090ACD692A for ; Wed, 8 Feb 2017 19:53:24 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B09841659; Wed, 8 Feb 2017 19:53:23 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v18JwVAq047164 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 8 Feb 2017 21:58:33 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v18JrHdR002049 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Feb 2017 21:53:17 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v18JrGHE002048; Wed, 8 Feb 2017 21:53:16 +0200 (EET) (envelope-from oleg@opentransfer.com) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@opentransfer.com using -f From: "Oleg V. Nauman" To: Ngie Cooper Cc: freebsd-current@freebsd.org, trasz@freebsd.org Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) Date: Wed, 08 Feb 2017 21:53:16 +0200 Message-ID: <1639154.lovTE8snb3@asus.theweb.org.ua> Organization: Ecommerce LLC User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 19:53:24 -0000 On Wednesday 08 February 2017 08:39:50 Ngie Cooper wrote: > > On Feb 8, 2017, at 07:44, Oleg V. Nauman wrote: > > > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > stopped working. > > Below is the end of 'truss' output for skype: > > > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not > > supported' > > 36723: write(6,"@",1) = 1 (0x1) > > 36723: close(6) = 0 (0x0) > > 36723: close(5) = 0 (0x0) > > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) > > 36723: linux_exit_group(0x1) > > 36723: process exit, rval = 1 > > > > My second current box ( r313090 i386 ) runs skype successfully. > > Hi, > Please try reverting r312988. skype still fails, unfortunately. 2024: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not supported' 2024: write(6,"@",1) = 1 (0x1) 2024: close(6) = 0 (0x0) 2024: close(5) = 0 (0x0) 2024: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) 2024: linux_exit_group(0x1) 2024: process exit, rval = 1 > Thanks! > -Ngie From owner-freebsd-current@freebsd.org Wed Feb 8 20:31:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C954CD6470 for ; Wed, 8 Feb 2017 20:31:33 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BFB7BE1; Wed, 8 Feb 2017 20:31:32 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v18Kaeqq047764 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 8 Feb 2017 22:36:44 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v18KVPMr034461 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Feb 2017 22:31:26 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v18KVPjd034460; Wed, 8 Feb 2017 22:31:25 +0200 (EET) (envelope-from oleg@opentransfer.com) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@opentransfer.com using -f From: "Oleg V. Nauman" To: cem@freebsd.org Cc: freebsd-current , dchagin@freebsd.org Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) Date: Wed, 08 Feb 2017 22:31:25 +0200 Message-ID: <3672530.AN0bPEA49V@asus.theweb.org.ua> Organization: Ecommerce LLC User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 20:31:33 -0000 On Wednesday 08 February 2017 09:06:43 Conrad Meyer wrote: > Hi Oleg, > > It seems likely it is related to r313284. Kernel compilation fails cc -O2 -pipe -DCOMPAT_FREEBSD32 -DCOMPAT_LINUX32 -march=nehalem -fno-strict- aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc - DHAVE_KERNEL_OPTION_HEADERS -include /usr/src/sys/amd64/compile/oleg3/opt_global.h -I. -I/usr/src/sys -fno-common - g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer - I/usr/src/sys/amd64/compile/oleg3 -MD -MF.depend.linux32_dummy.o - MTlinux32_dummy.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fwrapv -fstack-protector - gdwarf-2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes - Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer- sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics- show-option -Wno-unknown-pragmas -Wno-error-tautological-compare -Wno-error- empty-body -Wno-error-parentheses-equality -Wno-error-unused-function -Wno- error-pointer-sign -Wno-error-shift-negative-value -mno-aes -mno-avx - std=iso9899:1999 -c /usr/src/sys/modules/linux/../../amd64/linux32/linux32_dummy.c -o linux32_dummy.o /usr/src/sys/modules/linux/../../amd64/linux32/linux32_dummy.c:117:1: error: declaration of 'struct linux_rt_tsigqueueinfo_args' will not be visible outside of this function [-Werror,-Wvisibility] DUMMY(rt_tsigqueueinfo); ^ /usr/src/sys/compat/linux/linux_util.h:79:39: note: expanded from macro 'DUMMY' linux_ ## s(struct thread *td, struct linux_ ## s ## _args *args) \ ^ :162:1: note: expanded from here linux_rt_tsigqueueinfo_args ^ /usr/src/sys/modules/linux/../../amd64/linux32/linux32_dummy.c:117:1: error: no previous prototype for function 'linux_rt_tsigqueueinfo' [-Werror,-Wmissing- prototypes] /usr/src/sys/compat/linux/linux_util.h:78:13: note: expanded from macro 'DUMMY' int \ ^ :160:1: note: expanded from here linux_rt_tsigqueueinfo ^ 2 errors generated. *** Error code 1 It is sources revision 313313 with reverted 313284. > > Best, > Conrad > > On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman wrote: > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > > > stopped working. > > > > Below is the end of 'truss' output for skype: > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not > > supported' > > 36723: write(6,"@",1) = 1 (0x1) > > 36723: close(6) = 0 (0x0) > > 36723: close(5) = 0 (0x0) > > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) > > 36723: linux_exit_group(0x1) > > 36723: process exit, rval = 1 > > > > My second current box ( r313090 i386 ) runs skype successfully. > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 21:39:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADB5CCD689D for ; Wed, 8 Feb 2017 21:39:06 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from oleg.opentransfer.com (oleg.opentransfer.com [91.217.144.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "oleg-10.opentransfer.com", Issuer "oleg-10.opentransfer.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BCBD126E; Wed, 8 Feb 2017 21:39:05 +0000 (UTC) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua ([10.0.8.4]) by oleg.opentransfer.com (8.15.2/8.15.2) with ESMTPS id v18LiE57048584 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 8 Feb 2017 23:44:17 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: from asus.theweb.org.ua (localhost [127.0.0.1]) by asus.theweb.org.ua (8.15.2/8.15.2) with ESMTPS id v18Ld0Hu002087 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Feb 2017 23:39:00 +0200 (EET) (envelope-from oleg@opentransfer.com) Received: (from oleg@localhost) by asus.theweb.org.ua (8.15.2/8.15.2/Submit) id v18Ld0J6002086; Wed, 8 Feb 2017 23:39:00 +0200 (EET) (envelope-from oleg@opentransfer.com) X-Authentication-Warning: asus.theweb.org.ua: oleg set sender to oleg@opentransfer.com using -f From: "Oleg V. Nauman" To: cem@freebsd.org Cc: freebsd-current , dchagin@freebsd.org Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) Date: Wed, 08 Feb 2017 23:38:59 +0200 Message-ID: <1905409.YfjzorCZB4@asus.theweb.org.ua> Organization: Ecommerce LLC User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 21:39:06 -0000 On Wednesday 08 February 2017 09:06:43 Conrad Meyer wrote: > Hi Oleg, Hello Conrad, > > It seems likely it is related to r313284. I have reverted both r313285 and r313284, it makes linux socket happy. skype is working now. Thank you! > > Best, > Conrad > > On Wed, Feb 8, 2017 at 7:44 AM, Oleg V. Nauman wrote: > > After upgrading of current on amd64 box to r313313 I noticed that skype > > has > > > > stopped working. > > > > Below is the end of 'truss' output for skype: > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not > > supported' > > 36723: write(6,"@",1) = 1 (0x1) > > 36723: close(6) = 0 (0x0) > > 36723: close(5) = 0 (0x0) > > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) > > 36723: linux_exit_group(0x1) > > 36723: process exit, rval = 1 > > > > My second current box ( r313090 i386 ) runs skype successfully. > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 8 22:18:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C6ABCD45BB for ; Wed, 8 Feb 2017 22:18:38 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 4C21DA8A for ; Wed, 8 Feb 2017 22:18:37 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id C9A6F12307D for ; Wed, 8 Feb 2017 16:18:31 -0600 (CST) To: freebsd-current@freebsd.org From: Karl Denninger Subject: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Message-ID: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> Date: Wed, 8 Feb 2017 16:18:29 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms010903080803070002020401" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 22:18:38 -0000 This is a cryptographically signed message in MIME format. --------------ms010903080803070002020401 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable r313441 blows up on the Pi3 in /boot/loader.efi with: FreeBSD/arm64 EFI loader, Revision 1.1 (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net) Failed to start image provided by UFS (14) "Synchronous Abort" handler, esr 0x96000004 ELR: 3af62cec LR: 3af61d60 x0 : 0000000000000001 x1 : 0000000000000001 x2 : 000000003afeb000 x3 : 000000000000003f x4 : 0000000000000020 x5 : 0000000000000010 x6 : 0000000000000000 x7 : 0000000039b260a4 x8 : 000000003af61d48 x9 : 000000000000000d x10: 0000000000000030 x11: 0000000000000000 x12: 0000000000000000 x13: 0000000000000002 x14: 0000000000000000 x15: 0000000000000000 x16: 0000000000000000 x17: 0000000000000000 x18: 000000003ab30df8 x19: 0000000037a16008 x20: 0000000000000000 x21: 0000000000000000 x22: 0000000039b28000 x23: 0000000039b1d49c x24: 0000000039b28850 x25: 000000003ab3d740 x26: 000000003af839a0 x27: 0000000039b2e3e8 x28: 0000000000000000 x29: 000000003ab2ef60 Resetting CPU ... If you copy in a loader.efi from an earlier build (e.g. r313109) then the= system boots but complains about SMP problems, fails to start any of the= other CPUs (although it sees them) and panics before it reaches a login = prompt with what appears to be a problem reading the SD card (I also get = a couple of lor's in here too..... not sure if those are "real" or false = positives) Booting [/boot/kernel/kernel]... Using DTB provided by EFI at 0x8004000. KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2017 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved.= FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #0 r313389: Tue Feb 7 10:13:16 CST 2017 =20 freebsd@NewFS.denninger.net:/pics/Crochet-work/obj/arm64.aarch64/pics/Cro= ssBuild-12/src/sys/GENERIC arm64 FreeBSD clang version 3.9.1 (tags/RELEASE_391/final 289601) (based on LLVM 3.9.1) WARNING: WITNESS option enabled, expect reduced performance. VT: init without driver. can't re-use a leaf (geom_label)! module_register: cannot register g_label from kernel; already loaded from geom_label.ko Module g_label failed to register: 17 Starting CPU 1 (1) Starting CPU 2 (2) Starting CPU 3 (3) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs random: entropy device external interface kbd0 at kbdmux0 ofwbus0: simplebus0: on ofwbus0 ofw_clkbus0: on ofwbus0 clk_fixed0: on ofw_clkbus0 clk_fixed1: on ofw_clkbus0 clk_fixed2: on ofw_clkbus0 clk_fixed3: on ofw_clkbus0 clk_fixed4: on ofw_clkbus0 clk_fixed5: on ofw_clkbus0 clk_fixed6: on ofw_clkbus0 psci0: on ofwbus0 local_intc0: mem 0x40000000-0x400000ff on simplebus0 intc0: mem 0x7e00b200-0x7e00b3ff irq 16 on simplebus0 generic_timer0: irq 37,38,39,40 on simplebus0 Timecounter "ARM MPCore Timecounter" frequency 19200000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 19200000 Hz quality 1000 bcm_dma0: mem 0x7e007000-0x7e007eff irq 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 on simplebus0 mbox0: mem 0x7e00b880-0x7e00b8bf irq 17 on simplebus0 bcmwd0: mem 0x7e100000-0x7e100027 on simplebus0 gpio0: mem 0x7e200000-0x7e2000b3 irq 18,19 on simplebus0 gpiobus0: on gpio0 gpioc0: on gpio0 uart0: mem 0x7e201000-0x7e201fff irq 20 on simplebus0 uart0: console (115200,n,8,1) spi0: mem 0x7e204000-0x7e204fff irq 22 on simplebus0 spibus0: on spi0 spibus0: at cs 0 mode 0 spibus0: at cs 1 mode 0 sdhci_bcm0: mem 0x7e300000-0x7e3000ff irq 27 on simplebus0 mmc0: on sdhci_bcm0 iichb0: mem 0x7e804000-0x7e804fff irq 31 on simplebus0 iicbus0: on iichb0 bcm283x_dwcotg0: mem 0x7e980000-0x7e98ffff,0x7e006000-0x7e006fff irq 33,34 on simplebus0 usbus0 on bcm283x_dwcotg0 gpioled0: on simplebus0 gpioled0: failed to map pin fb0: on simplebus0 fbd0 on fb0 VT: initialize with new VT driver "fb". fb0: 656x416(656x416@0,0) 24bpp fb0: fbswap: 1, pitch 1968, base 0x3db33000, screen_size 818688 pmu0: irq 36 on simplebus0 cpulist0: on ofwbus0 cpu0: on cpulist0 bcm2835_cpufreq0: on cpu0 cpu1: on cpulist0 cpu2: on cpulist0 cpu3: on cpulist0 cryptosoft0: Timecounters tick every 1.000 msec The GEOM class LABEL is already loaded. usbus0: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 mmcsd0: 32GB at mmc0 41.6MHz/4bit/65535-block bcm2835_cpufreq0: ARM 600MHz, Core 250MHz, SDRAM 400MHz, Turbo OFF Release APs APs not started CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Instruction Set Attributes 0 =3D Instruction Set Attributes 1 =3D <0> Processor Features 0 =3D Processor Features 1 =3D <0> Memory Model Features 0 =3D <4k Granule,64k Granule,MixedEndian,S/N= S Mem,16bit ASID,1TB PA> Memory Model Features 1 =3D <> Debug Features 0 =3D <2 CTX Breakpoints,4 Watchpoints,6 Breakpoints,PMUv3,Debug v8> Debug Features 1 =3D <0> Auxiliary Features 0 =3D <0> Auxiliary Features 1 =3D <0> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 CPU 2: ARM Cortex-A53 r0p4 affinity: 2 CPU 3: ARM Cortex-A53 r0p4 affinity: 3 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]... uhub0: 1 port with 1 removable, self powered warning: no time-of-day clock registered, system time will not be set accurately Growing root partition to fill device ugen0.2: at usbus0 uhub1 on uhub0 uhub1: on usbus0 uhub1: MTT enabled GEOM_PART: mmcsd0s2 was automatically resized. Use `gpart commit mmcsd0s2` to save changes or `gpart undo mmcsd0s2` to revert them. mmcsd0s2 resized mmcsd0s2a resized super-block backups (for fsck_ffs -b #) at: 3802304, 4752832, 5703360, 6653888, 7604416, 8554944, 9505472, 10456000,= 11406528, 12357056, 13307584, 14258112, 15208640, 16159168, 17109696, 18060224, 19010752, 19961280, 20911808, 21862336, 22812864, 23763392, 24713920, 25664448, 26614976,uhub1: 5 ports with 4 removable, self power= ed 27565504, 28516032, 29466560, 30417088, 31367616, 32318144, 33268672, 34219200, 35169728, 36120256, 37070784, 38021312, 38971840, 39922368, 40872896, 41823424, 42773952, 43724480, 44675008, 45625536, 46576064, 47526592, 48477120, 49427648, 50378176, 51328704, 52279232, 53229760, 54180288, 55130816, 56081344, 57031872, 57982400, 58932928, 59883456, 60833984, 61784512 ugen0.3: at usbus0 smsc0 on uhub1 smsc0: on usbus0 smsc0: chip 0xec00, rev. 0002 miibus0: on smsc0 smscphy0: PHY 1 on miibus0 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: on smsc0 ue0: Ethernet address: b8:27:eb:4e:88:64 Setting hostuuid: 30303030-3030-3030-3331-346538383634. Setting hostid: 0x968824d5. No suitable dump device was found. Starting file system checks: /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 7272066 free (274 frags, 908974 blocks, 0.0% fragmentation) lock order reversal: 1st 0xffff000053248208 bufwait (bufwait) @ /pics/CrossBuild-12/src/sys/kern/vfs_bio.c:3500 2nd 0xfffffd0001559600 dirhash (dirhash) @ /pics/CrossBuild-12/src/sys/ufs/ufs/ufs_dirhash.c:281 stack backtrace: #0 0xffff00000034eb94 at witness_debugger+0x64 #1 0xffff0000002fb808 at _sx_xlock+0x6c #2 0xffff0000005576a4 at ufsdirhash_move+0x40 #3 0xffff00000055987c at ufs_direnter+0x2ac #4 0xffff000000561c98 at ufs_makeinode+0x464 #5 0xffff00000055e464 at ufs_create+0x3c #6 0xffff0000005eacac at VOP_CREATE_APV+0xc4 #7 0xffff0000003b9970 at vn_open_cred+0x284 #8 0xffff0000003b3524 at kern_openat+0x1d4 #9 0xffff0000005cf434 at do_el0_sync+0x4c8 #10 0xffff0000005b91d0 at handle_el0_sync+0x64 lock order reversal: 1st 0xfffffd00017c19a0 ufs (ufs) @ /pics/CrossBuild-12/src/sys/kern/vfs_subr.c:2600 2nd 0xffff000053248208 bufwait (bufwait) @ /pics/CrossBuild-12/src/sys/ufs/ffs/ffs_vnops.c:280 3rd 0xfffffd0001976068 ufs (ufs) @ /pics/CrossBuild-12/src/sys/kern/vfs_subr.c:2600 stack backtrace: #0 0xffff00000034eb94 at witness_debugger+0x64 #1 0xffff0000002ce980 at __lockmgr_args+0x57c #2 0xffff0000005527c8 at ffs_lock+0x88 #3 0xffff0000005ed764 at VOP_LOCK1_APV+0xc4 #4 0xffff0000003ba024 at _vn_lock+0x8c #5 0xffff0000003aba04 at vget+0x58 #6 0xffff00000039ea70 at vfs_hash_get+0xf0 #7 0xffff00000054ebac at ffs_vgetf+0x44 #8 0xffff000000545e1c at softdep_sync_buf+0x910 #9 0xffff000000553328 at ffs_syncvnode+0x274 #10 0xffff00000052e768 at ffs_truncate+0x624 #11 0xffff000000559d20 at ufs_direnter+0x750 #12 0xffff000000561c98 at ufs_makeinode+0x464 #13 0xffff00000055e464 at ufs_create+0x3c #14 0xffff0000005eacac at VOP_CREATE_APV+0xc4 #15 0xffff0000003b9970 at vn_open_cred+0x284 #16 0xffff0000003b3524 at kern_openat+0x1d4 #17 0xffff0000005cf434 at do_el0_sync+0x4c8 Mounting local filesystems:random: unblocking device. =2E ELF ldconfig path: /lib /usr/lib /usr/lib/compat Setting hostname: rpi3. Setting up harvesting: [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,AT= TACH,CACHED Feeding entropy: . smsc0: chip 0xec00, rev. 0002 ue0: link state changed to DOWN ue0: link state changed to UP Starting Network: lo0 ue0. lo0: flags=3D8049 metric 0 mtu 16384 options=3D600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=3D21 ue0: flags=3D8843 metric 0 mtu 15= 00 options=3D80009 ether b8:27:eb:4e:88:64 media: Ethernet autoselect (100baseTX ) status: active nd6 options=3D29 Starting devd. Starting dhclient. DHCPDISCOVER on ue0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.1.200 DHCPREQUEST on ue0 to 255.255.255.255 port 67 DHCPACK from 192.168.1.200 bound to 192.168.1.17 -- renewal in 21600 seconds. add host 127.0.0.1: gateway lo0 fib 0: route already in table add host ::1: gateway lo0 fib 0: route already in table add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Generating host.conf. Creating and/or trimming log files. Starting syslogd. Clearing /tmp (X related). Updating motd:. Mounting late filesystems:. Starting powerd. cpufreq0: rejecting change, SMP not started yet Configuring vt: blanktime. Generating RSA host key. cpufreq0: rejecting change, SMP not started yet cpufreq0: rejecting change, SMP not started yet cpufreq0: rejecting change, SMP not started yet cpufreq0: rejecting change, SMP not started yet cpufreq0: rejecting change, SMP not started yet cpufreq0: rejecting change, SMP not started yet 2048 SHA256:UFglYtdXWLG/Va5zmZ0OoGMhnvYiNyGDqEUkas7PZVs root@rpi3 (RSA) Generating ECDSA host key. cpufreq0: rejecting change, SMP not started yet 256 SHA256:XPQnIwHtB3Aau3jSQDitlqDZxF8hPLji5VpjOkJ3xqI root@rpi3 (ECDSA) Generating ED25519 host key. cpufreq0: rejecting change, SMP not started yet 256 SHA256:cVSnpBc4G0NX7+I3yUWiTa4YyYroJdbS0aKqdFky3a0 root@rpi3 (ED25519= ) Performing sanity check on sshd configuration. cpufreq0: rejecting change, SMP not started yet sdhci_bcm0-slot0: Controller timeout sdhci_bcm0-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D REGISTER DUM= P =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D sdhci_bcm0-slot0: Sys addr: 0x006d8000 | Version: 0x00009902 sdhci_bcm0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000015 sdhci_bcm0-slot0: Argument: 0x000af240 | Trn mode: 0x0000193a sdhci_bcm0-slot0: Present: 0x01ff0506 | Host ctl: 0x00000003 sdhci_bcm0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 sdhci_bcm0-slot0: Wake-up: 0x00000000 | Clock: 0x00000307 sdhci_bcm0-slot0: Timeout: 0x0000000e | Int stat: 0x00000010 sdhci_bcm0-slot0: Int enab: 0x01ff00bb | Sig enab: 0x01ff0089 sdhci_bcm0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 sdhci_bcm0-slot0: Caps: 0x00000000 | Max curr: 0x00000001 sdhci_bcm0-slot0: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D314343424, length=3D16384)]error =3D= 5 mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[READ(offset=3D1695514624, length=3D32768)]error =3D= 5 vm_fault: pager read error, pid 626 (sshd) mmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D314343424, length=3D16384)]error =3D= 5 Smmcsd0: Error indicated: 1 Timeout g_vfs_done():mmcsd0s2a[WRITE(offset=3D15509504, length=3D512)]error =3D 5= panic: brelse: inappropriate B_PAGING or B_CLUSTER bp 0xffff000053280d60 cpuid =3D 3 KDB: stack backtrace: db_trace_self() at db_trace_self_wrapper+0x28 pc =3D 0xffff0000005b76ac lr =3D 0xffff000000086048 sp =3D 0xffff000040328990 fp =3D 0xffff000040328ba0 db_trace_self_wrapper() at vpanic+0x170 pc =3D 0xffff000000086048 lr =3D 0xffff0000002f41b4 sp =3D 0xffff000040328bb0 fp =3D 0xffff000040328c30 vpanic() at kassert_panic+0x164 pc =3D 0xffff0000002f41b4 lr =3D 0xffff0000002f4040 sp =3D 0xffff000040328c40 fp =3D 0xffff000040328d00 kassert_panic() at brelse+0x7c4 pc =3D 0xffff0000002f4040 lr =3D 0xffff00000038e804 sp =3D 0xffff000040328d10 fp =3D 0xffff000040328d70 brelse() at bufwrite+0x338 pc =3D 0xffff00000038e804 lr =3D 0xffff00000038bb7c sp =3D 0xffff000040328d80 fp =3D 0xffff000040328dc0 bufwrite() at softdep_process_journal+0x714 pc =3D 0xffff00000038bb7c lr =3D 0xffff000000547e7c sp =3D 0xffff000040328dd0 fp =3D 0xffff000040328e70 softdep_process_journal() at flush_deplist+0xb4 pc =3D 0xffff000000547e7c lr =3D 0xffff00000054d34c sp =3D 0xffff000040328e80 fp =3D 0xffff000040328eb0 There's not a lot changed between 313109 and 313441 in the loader.efi and arm64 pieces of sys...... any ideas what boogered it? (Also have posted on this in -arm, but since it's Pi3 specific and that machine is -HEAD dependent is this the better place for it?) --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms010903080803070002020401 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAyMDgyMjE4MjlaME8GCSqGSIb3DQEJBDFCBECErYJ8 vFec/z4+Q7eL87igegMFQZ0x6wVcj7RkUE2yocH7WzOfnXyN5w9eJnMecZM6pxJblBSKpcxX 29XrntzWMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIAdpXpiFjnu/wm YIELFL0o89SHMmxSgVcCmkkOk0t+EC6YMUzlwfk50gu8UfU5Q15eq8ipQ4EcmmUKFWsXozdC CWMxmCaHTm/zxzEsb406A9yWocFqFhKOKltk6DQDLhVrEIdnuPcpXmINlhlZ3DLI85v6ChVl mfMF0HKdPwxRWkKfQbmPZlubGB/sl6N9x5JcRREo0LsG2HZs/Rdy8gAV9t+C4q4xxPexhIrJ L0wbwOi/g/doiMNSI7fQlOoPf8p0Wmu2pV3zFzfSRXkiwNK2bxNUDEyWZSbTowpjeTa5lpLX Ht1q4KB4n0nAochSIEgOcPZCrJbD4hmFJjvth+RvOgLHTr8V75MXghVPt/LfKWjBL069efPm KGRGfUaL5cg09k+5jyYU2Nq4C03PbFDvkbgEq0YN3DTlX7egqm9MSr+s2x1EoHUmW2AHqaWn trmpR0xLE2X7Lw0wJklaAiTwG2LJB2fUtLouUpw+opFtH6myP0lgbVPH6vsmnq9UNWcz9xvv UO1iYGJnc/2TbHhV4fEYW0qA1wRMi7wqu6vuMXtpXvUViGSOhpGOkiDkVOEKI2yngyT4wMdo D0+RaFDrWcxZUwU8e/5Y8Md+cHWEYmNUyiEBghIZoxOMlMJ3czm9R75Q9Gn2aIJn2T0bSniF DFtPJLh28QcI6WdDaW40ZzQAAAAAAAA= --------------ms010903080803070002020401-- From owner-freebsd-current@freebsd.org Thu Feb 9 14:36:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7930CD6114 for ; Thu, 9 Feb 2017 14:36:22 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 6854B146 for ; Thu, 9 Feb 2017 14:36:22 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 551D3182332 for ; Thu, 9 Feb 2017 08:36:21 -0600 (CST) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 To: freebsd-current@freebsd.org References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> From: Karl Denninger Message-ID: <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> Date: Thu, 9 Feb 2017 08:36:18 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms010906040404020903060900" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 14:36:22 -0000 This is a cryptographically signed message in MIME format. --------------ms010906040404020903060900 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2/8/2017 16:18, Karl Denninger wrote: > r313441 blows up on the Pi3 in /boot/loader.efi with: > > FreeBSD/arm64 EFI loader, Revision 1.1 > (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net) > Failed to start image provided by UFS (14) > "Synchronous Abort" handler, esr 0x96000004 > ELR: 3af62cec > LR: 3af61d60 > x0 : 0000000000000001 x1 : 0000000000000001 > x2 : 000000003afeb000 x3 : 000000000000003f > x4 : 0000000000000020 x5 : 0000000000000010 > x6 : 0000000000000000 x7 : 0000000039b260a4 > x8 : 000000003af61d48 x9 : 000000000000000d > x10: 0000000000000030 x11: 0000000000000000 > x12: 0000000000000000 x13: 0000000000000002 > x14: 0000000000000000 x15: 0000000000000000 > x16: 0000000000000000 x17: 0000000000000000 > x18: 000000003ab30df8 x19: 0000000037a16008 > x20: 0000000000000000 x21: 0000000000000000 > x22: 0000000039b28000 x23: 0000000039b1d49c > x24: 0000000039b28850 x25: 000000003ab3d740 > x26: 000000003af839a0 x27: 0000000039b2e3e8 > x28: 0000000000000000 x29: 000000003ab2ef60 > > Resetting CPU ... > > If you copy in a loader.efi from an earlier build (e.g. r313109) then t= he system boots but complains about SMP problems, fails to start any of t= he other CPUs (although it sees them) and panics before it reaches a logi= n prompt with what appears to be a problem reading the SD card (I also ge= t a couple of lor's in here too..... not sure if those are "real" or fals= e positives) > > B This has been isolated to r313333 in sys/boot/efi; reverting the EFI loader to a previous revision stops the crash. Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940 --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms010906040404020903060900 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAyMDkxNDM2MThaME8GCSqGSIb3DQEJBDFCBECt8kie SgAvVcVdtIFZVShBt+ZPATtvSp/DrTPAsnplk5zMJdu7mS2r8spx/vkFfEP7vPiMHn0S+/hz N4s+J3nXMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIAbXT8GNQx6uYW XEBstkBpJH9Sgq93P/8qMy3bUwQtDV3t2LBt+DBvP71tKe7mz/JmVEDqzaz63y9Io/vDu6ga ryW0c5x6urAdpbSJt09Kp5fZGdDZoktxJEuf2QfmLMaCUvq83tdQcQcrcPXK+FfFkmvDj0Bj bDq2A3J/qtM+fZmbZxVrF6bHcQRMAo9lKdRFCFN3wUSdM/+bS69Mu6g+AM9AfTCFMYxRFBbM DANCnyhlHuKZZd22eGmGR1URlktQEIHyNqjUCUTqM7YHmHdUapncVKMGOjifM+d+nmiS5iEq qe6IYYlvAplERgFAv9pocK9kf+a3vwm2bjXKHGJqZjzxTwSQpBPJMyoDgnhJucCmJZu0gYRV BFiqYOYNIBcszVJqCRWIIYImfQm7QtUrh9wY68G56nnxT38Z/pcpUjjVBGlExbGrJ8uZ8yBf wjFaqeDnxjButZVKjhp6jU+09c9F+UxJsdcYEJYPkRy1cuEXUcs8Hy3031xuNwRtSGKyCbqj 7rMUja6Qi4glejVIx3mtSyv4nAY0UTRrWlQiKWgxil9jSRlSWZeG+P5Yz8ExEmN8sMJvohBk MRwnAIPTdy6+729lsLNPv8+cPeaKbtXCItWVCokSlUWB9Ki5SNicoIeYqc8NzfCpvHpaWR+i FbqLD+AFbaXtyVcpqjMT2/8AAAAAAAA= --------------ms010906040404020903060900-- From owner-freebsd-current@freebsd.org Thu Feb 9 14:40:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F4168CD62E5 for ; Thu, 9 Feb 2017 14:40:31 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msa02a.plala.or.jp (msa02.plala.or.jp [IPv6:2400:7800:0:5010::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3833B9; Thu, 9 Feb 2017 14:40:31 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc02.plala.or.jp ([172.23.12.32]) by msa01b.plala.or.jp with ESMTP id <20170209143632.EFRO7801.msa01b.plala.or.jp@msc02.plala.or.jp>; Thu, 9 Feb 2017 23:36:32 +0900 Received: from localhost ([121.116.94.133]) by msc02.plala.or.jp with ESMTP id <20170209143632.FVOX26601.msc02.plala.or.jp@localhost>; Thu, 9 Feb 2017 23:36:32 +0900 Date: Thu, 09 Feb 2017 23:36:25 +0900 (JST) Message-Id: <20170209.233625.360228747927162044.ish@amail.plala.or.jp> To: oleg@opentransfer.com Cc: cem@freebsd.org, freebsd-current@freebsd.org, dchagin@freebsd.org Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) From: Masachika ISHIZUKA In-Reply-To: <1905409.YfjzorCZB4@asus.theweb.org.ua> References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> <1905409.YfjzorCZB4@asus.theweb.org.ua> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; msa01m; Thu, 9 Feb 2017 23:36:32 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 14:40:32 -0000 Hi. linux-flashplayer (with opera or firefox) is not working with r313440. After reverting r313285 and r313284, it is working again. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Thu Feb 9 14:59:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F997CD6994 for ; Thu, 9 Feb 2017 14:59:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB460124B for ; Thu, 9 Feb 2017 14:59:06 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL40060042O2C00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Thu, 09 Feb 2017 14:58:53 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486652333; bh=geiGPQU6Oair8QGz/zrxGA3zzxKuUvWMMKHbe9rOmOY=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=ZUivVBh3F6k8jpJFv8Wjy6l7J/gyif1lTbGa1XyO9CoOHZZMn7CfeJ3ZCITIiPfT6 dceE7gDv3QXTUgK2AHM78ntUConyR7iSSg1kLx/UGy8tyTk9vIE0jAlSStjy0yUvzB rfunaOYmky/JCUWh+/wqWvAqtsiaok2iPIpRfbiTNe3Tg9MA0mj/KSH+JW0aJ0Q4gJ /SzEIh5a2Xyip5YVxGnKyC/fix6NW3cwfMMCzGV8iPUZPrmLLdOvgLudog0GuJs04Y Jfrldfh5nifQVhTMe60w+ZGk2WzuCz0X5ryvB6RlGTbaUPrMl0W6p0NFmZwmI804WV vqP46BC/M11pw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL400OD94A2CU20@st13p35im-asmtp001.me.com>; Thu, 09 Feb 2017 14:58:53 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-09_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702090135 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Date: Thu, 09 Feb 2017 16:58:49 +0200 In-reply-to: <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> Cc: freebsd-current@freebsd.org To: Karl Denninger References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> X-Mailer: Apple Mail (2.3259) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 14:59:07 -0000 > On 9. veebr 2017, at 16:36, Karl Denninger wrote: >=20 >=20 > On 2/8/2017 16:18, Karl Denninger wrote: >> r313441 blows up on the Pi3 in /boot/loader.efi with: >>=20 >> FreeBSD/arm64 EFI loader, Revision 1.1 >> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net) >> Failed to start image provided by UFS (14) >> "Synchronous Abort" handler, esr 0x96000004 >> ELR: 3af62cec >> LR: 3af61d60 >> x0 : 0000000000000001 x1 : 0000000000000001 >> x2 : 000000003afeb000 x3 : 000000000000003f >> x4 : 0000000000000020 x5 : 0000000000000010 >> x6 : 0000000000000000 x7 : 0000000039b260a4 >> x8 : 000000003af61d48 x9 : 000000000000000d >> x10: 0000000000000030 x11: 0000000000000000 >> x12: 0000000000000000 x13: 0000000000000002 >> x14: 0000000000000000 x15: 0000000000000000 >> x16: 0000000000000000 x17: 0000000000000000 >> x18: 000000003ab30df8 x19: 0000000037a16008 >> x20: 0000000000000000 x21: 0000000000000000 >> x22: 0000000039b28000 x23: 0000000039b1d49c >> x24: 0000000039b28850 x25: 000000003ab3d740 >> x26: 000000003af839a0 x27: 0000000039b2e3e8 >> x28: 0000000000000000 x29: 000000003ab2ef60 >>=20 >> Resetting CPU ... >>=20 >> If you copy in a loader.efi from an earlier build (e.g. r313109) then = the system boots but complains about SMP problems, fails to start any of = the other CPUs (although it sees them) and panics before it reaches a = login prompt with what appears to be a problem reading the SD card (I = also get a couple of lor's in here too..... not sure if those are "real" = or false positives) >>=20 >> B >=20 > This has been isolated to r313333 in sys/boot/efi; reverting the EFI > loader to a previous revision stops the crash. >=20 > Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940 = >=20 Does it still crash with r313442? I think it does and this is why: =46rom your log above, the hint is "Failed to start image provided by = UFS (14)=E2=80=9D, so what we can guess here is that for some reason the = loader.efi main() failed to detect the boot device, and did return back = to boot1. Boot1 did print out this error message and did call panic(). So, the = question is, why it is failing to detect the root fs handle. I=E2=80=99ll = try to check if I can replicate the issue with x86 + ufs. BTW: sorry for trouble:) rgds, toomas From owner-freebsd-current@freebsd.org Thu Feb 9 15:05:57 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52BDECD6ED3 for ; Thu, 9 Feb 2017 15:05:57 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 1468D1AF9 for ; Thu, 9 Feb 2017 15:05:56 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 21E88180B53; Thu, 9 Feb 2017 09:05:56 -0600 (CST) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 To: freebsd-current@freebsd.org References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> Cc: tsoome@me.com From: Karl Denninger Message-ID: <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> Date: Thu, 9 Feb 2017 09:05:53 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms000600030805080004020705" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:05:57 -0000 This is a cryptographically signed message in MIME format. --------------ms000600030805080004020705 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2/9/2017 08:58, Toomas Soome wrote: >> On 9. veebr 2017, at 16:36, Karl Denninger wrote:= >> >> >> On 2/8/2017 16:18, Karl Denninger wrote: >>> r313441 blows up on the Pi3 in /boot/loader.efi with: >>> >>> FreeBSD/arm64 EFI loader, Revision 1.1 >>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net) >>> Failed to start image provided by UFS (14) >>> "Synchronous Abort" handler, esr 0x96000004 >>> ELR: 3af62cec >>> LR: 3af61d60 >>> x0 : 0000000000000001 x1 : 0000000000000001 >>> x2 : 000000003afeb000 x3 : 000000000000003f >>> x4 : 0000000000000020 x5 : 0000000000000010 >>> x6 : 0000000000000000 x7 : 0000000039b260a4 >>> x8 : 000000003af61d48 x9 : 000000000000000d >>> x10: 0000000000000030 x11: 0000000000000000 >>> x12: 0000000000000000 x13: 0000000000000002 >>> x14: 0000000000000000 x15: 0000000000000000 >>> x16: 0000000000000000 x17: 0000000000000000 >>> x18: 000000003ab30df8 x19: 0000000037a16008 >>> x20: 0000000000000000 x21: 0000000000000000 >>> x22: 0000000039b28000 x23: 0000000039b1d49c >>> x24: 0000000039b28850 x25: 000000003ab3d740 >>> x26: 000000003af839a0 x27: 0000000039b2e3e8 >>> x28: 0000000000000000 x29: 000000003ab2ef60 >>> >>> Resetting CPU ... >>> >>> If you copy in a loader.efi from an earlier build (e.g. r313109) then= the system boots but complains about SMP problems, fails to start any of= the other CPUs (although it sees them) and panics before it reaches a lo= gin prompt with what appears to be a problem reading the SD card (I also = get a couple of lor's in here too..... not sure if those are "real" or fa= lse positives) >>> >>> B >> This has been isolated to r313333 in sys/boot/efi; reverting the EFI >> loader to a previous revision stops the crash. >> >> Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940= >> > Does it still crash with r313442? I think it does and this is why: > > From your log above, the hint is "Failed to start image provided by UFS= (14)=E2=80=9D, so what we can guess here is that for some reason the loa= der.efi main() failed to detect the boot device, and did return back to b= oot1. > > Boot1 did print out this error message and did call panic(). So, the qu= estion is, why it is failing to detect the root fs handle. I=E2=80=99ll t= ry to check if I can replicate the issue with x86 + ufs. > > BTW: sorry for trouble:) > > rgds, > toomas > Yes. It's isolated to that particular revision, which appears to have reworked the enumeration of the available devices to boot from.=20 Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi that successfully loads and starts the kernel. --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms000600030805080004020705 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAyMDkxNTA1NTNaME8GCSqGSIb3DQEJBDFCBEB7nmdq Ope/vMW6YHNHSlOVF7lRVY6bPXcC/2/eSEQ2uCNFKBXPySPgP5VGLNvasndRNw79fDM6DXaV zY9MssehMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIAgdDLsc/mlR9Y 3dZHs0sC73PIzBru2E/TXzqAKSNboVD/8RETYobbU5xCIV1Z40iE65tkKrA5oxA5wwvR3wOo wpqIaOSinkbLSlN49TwYY8MOhXXG41LhX8nAVL5PpoA5AyGGirmre4OUqpu5uJeHT5qa/t4F UwsSYNuo0afv7TOFVSlnZXuVwH8otKgcSkzD14axdfKMQkctDpEbSSOqLr9uJdePgXReLSVB FTsff/MvruHk6lvIBivmJyGWEifmHClOmSwvcSSREAVMVzTRgRrRSGdk/Dh5Yu18wxrr9VHs u/KhU0tvmuKw/7qwuzJK8dLCzgU1aDEXqljlZ7dhC4pCKRoWfUoxTdw8iakLIEDWCMr0hBy3 M5ll8UKbz+40BpQ+ukqAawjpCfDUcGs2Twq5/d0v3TSMANKQ/nX7UoepnFh6GskDlcvZKWOn oXARzhbOJkF4+mzehqYXsc9Hvl8cx7xIOlAWW5ZbTrZibdZwWzF3YntC0AkmjEGV0KuNPhLR m9BR2aTNyJgVQM4LkIPRXF9nGrSQB2LN/aVpa2y5wdmFF1SzpwxQwJTmXtlcXpPN2CQCKelS SKLPEAx5MzUlViKWYIr/BzYMZVgWlBxCHq9V61w8vREqaYM/oyYLB3WmuI5Gzik8KMbQWLOI FfVfb7SHqBfUF/5HfAGlO08AAAAAAAA= --------------ms000600030805080004020705-- From owner-freebsd-current@freebsd.org Thu Feb 9 15:06:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4B9BCD6EEB for ; Thu, 9 Feb 2017 15:06:05 +0000 (UTC) (envelope-from dchagin@chd.heemeyer.club) Received: from heemeyer.club (heemeyer.club [108.61.204.158]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "heemeyer.club", Issuer "heemeyer.club" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB1781B7A for ; Thu, 9 Feb 2017 15:06:05 +0000 (UTC) (envelope-from dchagin@chd.heemeyer.club) Received: from chd.heemeyer.club (dchagin.static.corbina.ru [78.107.232.239]) by heemeyer.club (8.15.2/8.15.1) with ESMTPS id v19F5t6v060801 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 9 Feb 2017 15:05:57 GMT (envelope-from dchagin@chd.heemeyer.club) X-Authentication-Warning: heemeyer.club: Host dchagin.static.corbina.ru [78.107.232.239] claimed to be chd.heemeyer.club Received: from chd.heemeyer.club (localhost [127.0.0.1]) by chd.heemeyer.club (8.15.2/8.15.1) with ESMTPS id v19F5rwx028994 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 9 Feb 2017 18:05:53 +0300 (MSK) (envelope-from dchagin@chd.heemeyer.club) Received: (from dchagin@localhost) by chd.heemeyer.club (8.15.2/8.15.2/Submit) id v19F5rMs028993; Thu, 9 Feb 2017 18:05:53 +0300 (MSK) (envelope-from dchagin) Date: Thu, 9 Feb 2017 18:05:53 +0300 From: Chagin Dmitry To: "Oleg V. Nauman" Cc: freebsd-current@freebsd.org Subject: Re: 'Protocol not supported' on linux socket call ( r313313 amd64 ) Message-ID: <20170209150553.GA28973@chd.heemeyer.club> References: <2628207.fWzAjJv2TV@asus.theweb.org.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2628207.fWzAjJv2TV@asus.theweb.org.ua> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:06:06 -0000 On Wed, Feb 08, 2017 at 05:44:34PM +0200, Oleg V. Nauman wrote: > After upgrading of current on amd64 box to r313313 I noticed that skype has > stopped working. > Below is the end of 'truss' output for skype: > > 36723: linux_socketcall(1,{ LINUX_SOCKET, 0x0 }) ERR#-93 'Protocol not > supported' > 36723: write(6,"@",1) = 1 (0x1) > 36723: close(6) = 0 (0x0) > 36723: close(5) = 0 (0x0) > 36723: linux_rt_sigaction(0x11,0xffffbaf8,0xffffba6c,0x8) = 0 (0x0) > 36723: linux_exit_group(0x1) > 36723: process exit, rval = 1 > > My second current box ( r313090 i386 ) runs skype successfully. ok, I'll see, thank u for the report From owner-freebsd-current@freebsd.org Thu Feb 9 15:31:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9FA6CD7A78 for ; Thu, 9 Feb 2017 15:31:32 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E76AE96 for ; Thu, 9 Feb 2017 15:31:32 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL4008005SINY00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Thu, 09 Feb 2017 15:31:31 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486654291; bh=JNi1N45ad7uVpQhLg0DVtxfBt0zWIO/GGLkvJTxi/7E=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=daB8UWPIkisyDdQuLeaK/lBGmvHtLOq4UByvioiBzsWx25bQBhTxJmu98m6FLZm3d LiMgBvT1wlejSeSh2oW7lTxPfqT2C11E7qMSai4FXHAlGLMEvmU4+gMuWCwLoumG+G vYoixh+lpRiuSvT04m2nPv4iJVKWAIvRpaoBdtxQ7JReOCYvj1tIhwL6LMYww929IO uMf6NXVJdq8RLpKJsdxhxBGCsCsWo3GtIoD9q8LFcQo4YJvCcDNN5XOZ5z4ALnD2Jv So3x+xrLlcNpCbe7a8Bj6rHNDQoERB8QAXSpVoOyBxNtmjhqxDhZm1DSFuIHkKBD2t TdHO4wKP+0/8A== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL400CRH5SG5H40@st13p35im-asmtp001.me.com>; Thu, 09 Feb 2017 15:31:31 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-09_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702090139 From: Toomas Soome Message-id: <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Date: Thu, 09 Feb 2017 17:31:28 +0200 In-reply-to: <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> Cc: freebsd-current@freebsd.org To: Karl Denninger References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> X-Mailer: Apple Mail (2.3259) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:31:33 -0000 > On 9. veebr 2017, at 17:05, Karl Denninger wrote: >=20 >=20 > On 2/9/2017 08:58, Toomas Soome wrote: >>> On 9. veebr 2017, at 16:36, Karl Denninger = wrote: >>>=20 >>>=20 >>> On 2/8/2017 16:18, Karl Denninger wrote: >>>> r313441 blows up on the Pi3 in /boot/loader.efi with: >>>>=20 >>>> FreeBSD/arm64 EFI loader, Revision 1.1 >>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net = ) >>>> Failed to start image provided by UFS (14) >>>> "Synchronous Abort" handler, esr 0x96000004 >>>> ELR: 3af62cec >>>> LR: 3af61d60 >>>> x0 : 0000000000000001 x1 : 0000000000000001 >>>> x2 : 000000003afeb000 x3 : 000000000000003f >>>> x4 : 0000000000000020 x5 : 0000000000000010 >>>> x6 : 0000000000000000 x7 : 0000000039b260a4 >>>> x8 : 000000003af61d48 x9 : 000000000000000d >>>> x10: 0000000000000030 x11: 0000000000000000 >>>> x12: 0000000000000000 x13: 0000000000000002 >>>> x14: 0000000000000000 x15: 0000000000000000 >>>> x16: 0000000000000000 x17: 0000000000000000 >>>> x18: 000000003ab30df8 x19: 0000000037a16008 >>>> x20: 0000000000000000 x21: 0000000000000000 >>>> x22: 0000000039b28000 x23: 0000000039b1d49c >>>> x24: 0000000039b28850 x25: 000000003ab3d740 >>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 >>>> x28: 0000000000000000 x29: 000000003ab2ef60 >>>>=20 >>>> Resetting CPU ... >>>>=20 >>>> If you copy in a loader.efi from an earlier build (e.g. r313109) = then the system boots but complains about SMP problems, fails to start = any of the other CPUs (although it sees them) and panics before it = reaches a login prompt with what appears to be a problem reading the SD = card (I also get a couple of lor's in here too..... not sure if those = are "real" or false positives) >>>>=20 >>>> B >>> This has been isolated to r313333 in sys/boot/efi; reverting the EFI >>> loader to a previous revision stops the crash. >>>=20 >>> Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940= = = >>>=20 >> Does it still crash with r313442? I think it does and this is why: >>=20 >> =46rom your log above, the hint is "Failed to start image provided by = UFS (14)=E2=80=9D, so what we can guess here is that for some reason the = loader.efi main() failed to detect the boot device, and did return back = to boot1. >>=20 >> Boot1 did print out this error message and did call panic(). So, the = question is, why it is failing to detect the root fs handle. I=E2=80=99ll = try to check if I can replicate the issue with x86 + ufs. >>=20 >> BTW: sorry for trouble:) >>=20 >> rgds, >> toomas >>=20 > Yes. >=20 > It's isolated to that particular revision, which appears to have = reworked the enumeration of the available devices to boot from. = Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update = -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi = that successfully loads and starts the kernel. >=20 Well, the x86 version does not appear to have problems with finding the = ufs devices. So this has to be some sort of corner case related to arm:( = unfortunately I do not have much variants to test arm, except qemu=E2=80=A6= so some help would be needed there. Since the only crash is from boot1 = call to panic, I am pretty sure the disk detection and setup was ok, so = we should get disk list if we insert something like: for (i =3D 0; devsw[i] !=3D NULL; i++) { if (devsw[i]->dv_print !=3D NULL){ if (devsw[i]->dv_print(verbose)) break; } } after dv_init() loop. If thats true, then it should not take too much to find why we fail to = get the handle for root fs in case of arm=E2=80=A6=20 rgds, toomas From owner-freebsd-current@freebsd.org Thu Feb 9 15:40:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE109CD7DC8 for ; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DA61A128F for ; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id D626ACD7DC2; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D599CCD7DC1; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9AB45128E; Thu, 9 Feb 2017 15:40:11 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1cbqpL-0000XE-BI; Thu, 09 Feb 2017 16:40:07 +0100 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1cbqpL-0004hT-9P; Thu, 09 Feb 2017 16:40:07 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Thu, 09 Feb 2017 15:40:07 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "ports" , "timothy.bouquet" CC: "gecko" , "current" Subject: r313305 libevent2 problem and workaround NEED FIXING... Date: Thu, 09 Feb 2017 07:40:07 -0800 (PST) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:40:12 -0000 A huge six-day fix of seamonkey breakage on 11-CURRENT of april 2016, upgra= ded finally last night to pkg 12-CURRENT feb 2017 working and etc by base.txz=20 overwrite etc... ............................................... I've many many hours to restore the desktop to full how-it-was-before, but = as it is working, now, a wholesale 3xxx reinstall of ports by pkg (which had to occur OUT OF Xorg for stall issues... and lack of granularity in the use of "pkg upgrade" (ie thirty-by-thirty) or lack of code in "pkg install" (terse deinstalls necc. where reinstalls were needed) as of this date.... ................................................. Mostly fixed as I write from the fixed system, but the only reason I am usi= ng seamonkey now, and also fixed firefox, just then, is the series of commands... which = I expect to maybe re-break when v12 upgrades _4 seamonkey to _5 which broke (segfaults)= here from ports the port... but in the meantime .......................................... cp -iv /[backup mount}/usr/local/lib/libevent-2.0.so.5.10 /usr/local/lib/co= mpat/libevent-2.0.so.5 cp -iv /usr/local/lib/compat/libevent-2.0.so.5 /usr/ports/www/seamonkey/lib= event-2.0.so.5-NECC-FOR-SEAMONKEY .......................................... backup restored a newly overnight broken seamonkey AND firefox, the former = not as of a day or so from ports being able to run. ......................................... This is quite the showstopper here... almost forced a reinstall of 2004-201= 7 ( this desktop) to a 2016-STABLE v11 new disk.... which I may have to revert to if seamonke= y breaks again or the next iteration of libevent/seamonkey/firefox does not fix up with CLI s= uch as this time. .................................... Out of time for a PR or bug report offically, and hope to gain more pressing urgency to this problem than might be attained, that way... out of= time also. ................................... Thanks for reading, and thanks for putting up with interim list messages in= the last few days which still had a bit of almost PBKAC combined with lack of documentat= ion combined with newbie-ness here which had yet to resolve...=20 and thanks for the forum post(s) which helped resolve the seemingly-lost-ca= use issue of the v11-CURRENT upgrade to v12-CURRENT which appears to have worked today vs s= everal days ago, IF seamonkey continues to be fixable locally. .................................... J. Bouquet=20= From owner-freebsd-current@freebsd.org Thu Feb 9 18:02:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 888D4CD3931 for ; Thu, 9 Feb 2017 18:02:44 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53D9AD50 for ; Thu, 9 Feb 2017 18:02:44 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id l66so23352487ioi.1 for ; Thu, 09 Feb 2017 10:02:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=5ebC8YW1PhbSlrvvgTMvp/cveIhl/3qR9tBFrRfnyzM=; b=s7BD3qyR7wLIVT58QPb83pMzeAeyjxL4T0EPOCILK3agHLnH3v2wIvNyb2Z6PyznyD HleOm3YmXWuFhPwXXvolCWOUDR5QzEabHOEQRvBFtLRb4xEQT9uy0qJxY77t+3PAwaCp X80As42S4m94hpKv2ed6AINfap3Od23meGGX9azpWa280IEG4NuL708jfQ5VhmsN+pCb 5IQRhRRq7iAaGcPcHGkQlp8aNpyxHkC7+AyGRM4mCB2pvLkAzbLox9FQySQd2rlUhCId 3RDtvk4JZOd48kwfTVDRVYY0ScBvT4CbuzNIBTY2RxTm+MDL6/nya1AMecVVMI2JZV8I 5mLg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5ebC8YW1PhbSlrvvgTMvp/cveIhl/3qR9tBFrRfnyzM=; b=LThZphXfLy7O6L2cByY3klSXqpfyjIwUMd1kWn4zeYobUUzk6jJqtNYUac0/ZyoTAW Dc94NC2d9OLkCaAykKy8ZNNfVf61vjzIfKVU2KOO/xnyGmqFpUAwI5IVbglnEg+HZImf hPxQk/KDcHQbDGpjwcfheG+/ITMwbdnjK7JugCuwRWtT84CTfHmPKdsnN/LZ2zNBImo0 Ih3oZFuesdcUvxXur44h0cWDAZXHs0/IEPnz6wOBqH024fk2AQ55lw8yFYSsqOe+/fqi pnppfUCjL5nKVmZJbP2BBXPE2ZUBLpSNaEBxnebI3/t0cFUvQKO0GbGElYo5rlR5EFxc RoIg== X-Gm-Message-State: AMke39kvBevJ+hIkDYKb/Q4dNV8ed2nOJL5WXdSLkQE6lKmMo9673Vhal2NUwoUiQUP2HS7tBUtErL0Q4EY8AA== X-Received: by 10.107.15.70 with SMTP id x67mr4295461ioi.103.1486663363523; Thu, 09 Feb 2017 10:02:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.190.71 with HTTP; Thu, 9 Feb 2017 10:02:43 -0800 (PST) From: Ryan Stone Date: Thu, 9 Feb 2017 13:02:43 -0500 Message-ID: Subject: [PATCH] Check for preemption after lowering a thread's priority To: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 18:02:44 -0000 I've just put up a phabricator review for a fix to ULE and 4BSD for a priority inversion problem. The issue is that after a running thread's priority is lowered (usually due to releasing a mutex and having a priority load revoked), the scheduler does not check whether the thread should now be preempted by a thread waiting in the runq. See this old ML post for a detailed description of one instance that I saw: https://lists.freebsd.org/pipermail/freebsd-current/2013-January/039261.html The review can be found here: https://reviews.freebsd.org/D9518 From owner-freebsd-current@freebsd.org Thu Feb 9 21:56:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 016D0CD8238 for ; Thu, 9 Feb 2017 21:56:05 +0000 (UTC) (envelope-from karl@denninger.net) Received: from mail.denninger.net (denninger.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id B5180FF6 for ; Thu, 9 Feb 2017 21:56:04 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (Karl-Desktop.Denninger.net [192.168.1.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.denninger.net (Postfix) with ESMTPSA id 98A1F1A5AC4; Thu, 9 Feb 2017 15:56:03 -0600 (CST) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 To: Oleksandr Tymoshenko , Toomas Soome References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> Cc: freebsd-current@freebsd.org From: Karl Denninger Message-ID: Date: Thu, 9 Feb 2017 15:56:00 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170209213916.GA40599@bluezbox.com> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-512; boundary="------------ms000006090104000406080004" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 21:56:05 -0000 This is a cryptographically signed message in MIME format. --------------ms000006090104000406080004 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2/9/2017 15:39, Oleksandr Tymoshenko wrote: > Toomas Soome (tsoome@me.com) wrote: >>> On 9. veebr 2017, at 17:05, Karl Denninger wrote= : >>> >>> >>> On 2/9/2017 08:58, Toomas Soome wrote: >>>>> On 9. veebr 2017, at 16:36, Karl Denninger wrote: >>>>> >>>>> >>>>> On 2/8/2017 16:18, Karl Denninger wrote: >>>>>> r313441 blows up on the Pi3 in /boot/loader.efi with: >>>>>> >>>>>> FreeBSD/arm64 EFI loader, Revision 1.1 >>>>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net ) >>>>>> Failed to start image provided by UFS (14) >>>>>> "Synchronous Abort" handler, esr 0x96000004 >>>>>> ELR: 3af62cec >>>>>> LR: 3af61d60 >>>>>> x0 : 0000000000000001 x1 : 0000000000000001 >>>>>> x2 : 000000003afeb000 x3 : 000000000000003f >>>>>> x4 : 0000000000000020 x5 : 0000000000000010 >>>>>> x6 : 0000000000000000 x7 : 0000000039b260a4 >>>>>> x8 : 000000003af61d48 x9 : 000000000000000d >>>>>> x10: 0000000000000030 x11: 0000000000000000 >>>>>> x12: 0000000000000000 x13: 0000000000000002 >>>>>> x14: 0000000000000000 x15: 0000000000000000 >>>>>> x16: 0000000000000000 x17: 0000000000000000 >>>>>> x18: 000000003ab30df8 x19: 0000000037a16008 >>>>>> x20: 0000000000000000 x21: 0000000000000000 >>>>>> x22: 0000000039b28000 x23: 0000000039b1d49c >>>>>> x24: 0000000039b28850 x25: 000000003ab3d740 >>>>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 >>>>>> x28: 0000000000000000 x29: 000000003ab2ef60 >>>>>> >>>>>> Resetting CPU ... >>>>>> >>>>>> If you copy in a loader.efi from an earlier build (e.g. r313109) t= hen the system boots but complains about SMP problems, fails to start any= of the other CPUs (although it sees them) and panics before it reaches a= login prompt with what appears to be a problem reading the SD card (I al= so get a couple of lor's in here too..... not sure if those are "real" or= false positives) >>>>>> >>>>>> B >>>>> This has been isolated to r313333 in sys/boot/efi; reverting the EF= I >>>>> loader to a previous revision stops the crash. >>>>> >>>>> Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216= 940 >>>>> >>>> Does it still crash with r313442? I think it does and this is why: >>>> >>>> From your log above, the hint is "Failed to start image provided by = UFS (14)=E2=80=9D, so what we can guess here is that for some reason the = loader.efi main() failed to detect the boot device, and did return back t= o boot1. >>>> >>>> Boot1 did print out this error message and did call panic(). So, the= question is, why it is failing to detect the root fs handle. I=E2=80=99l= l try to check if I can replicate the issue with x86 + ufs. >>>> >>>> BTW: sorry for trouble:) >>>> >>>> rgds, >>>> toomas >>>> >>> Yes. >>> >>> It's isolated to that particular revision, which appears to have rewo= rked the enumeration of the available devices to boot from. Reverting on= ly sys/boot/efi to anything before 313333 (e.g. "svn update -r 313332 ." = in src/sys/boot/efi) and rebuilding results in a loader.efi that successf= ully loads and starts the kernel. >>> >> Well, the x86 version does not appear to have problems with finding th= e ufs devices. So this has to be some sort of corner case related to arm:= ( unfortunately I do not have much variants to test arm, except qemu=E2=80= =A6 so some help would be needed there. Since the only crash is from boot= 1 call to panic, I am pretty sure the disk detection and setup was ok, so= we should get disk list if we insert something like: >> >> for (i =3D 0; devsw[i] !=3D NULL; i++) { >> if (devsw[i]->dv_print !=3D NULL){ >> if (devsw[i]->dv_print(verbose)) >> break; >> } >> } >> >> after dv_init() loop. >> >> If thats true, then it should not take too much to find why we fail to= get the handle for root fs in case of arm=E2=80=A6=20 > > On RPi3 U-Boot EFI API provided by U-Boot and it's somewhat non-standar= d > comapring to x86 EFI or specialized EFI firmwares of ARM64. I did some > debugging and found that U-Boot reports driver with subtype MEDIA_FILEP= ATH_DP > so it's not recognized by disk handler. Quick hack below fixed boot > but it's not ideal and the device structure looks like this: > > disk devices: > disk0: 15564801 X 512 blocks (removable) > disk0s1: DOS/Windows 49MB > disk0s2: FreeBSD 1856MB > disk0s2a: FreeBSD UFS 1856MB > disk1: 102375 X 512 blocks (removable) > disk2: 3802112 X 512 blocks (removable) > disk2a: FreeBSD UFS 1856MB > net devices: > net0: > > > disk1 and disk2 are actuallypartitions from disk0. > I can work on proper fix but not sure what should be > considered proper in this case. So some guidelines are welcome > > Patch: > Index: boot/efi/libefi/efipart.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- boot/efi/libefi/efipart.c (revision 313477) > +++ boot/efi/libefi/efipart.c (working copy) > @@ -467,6 +467,15 @@ > efipart_hdinfo_add(handle, efipart_handles[i]);= > continue; > } > + > + /* > + * U-Boot case > + */ > + if (DevicePathType(node) =3D=3D MEDIA_DEVICE_PATH && > + DevicePathSubType(node) =3D=3D MEDIA_FILEPATH_DP) {= > + efipart_hdinfo_add(efipart_handles[i], efipart_= handles[i]); > + continue; > + } > } > } After a lot of back and forth with Toomas I'm sorta in the same place (slightly different code, but same effect)..... but while it enumerates the storage it still doesn't load the kernel. (pardon all the debugging printfs) >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Probing 3 block devices.....* done ZFS found no pools UFS found 1 partition Consoles: EFI console Enter efipart_updatehd nin [3] Nin 0 Type 4 subtype 4 Nin 0 name is NULL Cannot add as no logical partition is valid Nin 1 Type 4 subtype 4 Nin 1 name is NULL Added for 1 based on non-HD path Nin 2 Type 4 subtype 4 Nin 2 name is NULL Added for 2 based on non-HD path disk devices: disk0: 102375 X 512 blocks (removable) disk1: 62229504 X 512 blocks (removable) disk1a: FreeBSD UFS 29GB net devices: net0: Command line arguments: loader.efi Image base: 0x379b8008 EFI version: 2.05 EFI Firmware: Das U-boot (rev 0.00) FreeBSD/arm64 EFI loader, Revision 1.1 (Thu Feb 9 10:08:24 CST 2017 freebsd@NewFS.denninger.net) can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK lsdev -v disk devices: disk0: 102375 X 512 blocks (removable) disk1: 62229504 X 512 blocks (removable) disk1a: FreeBSD UFS 29GB net devices: net0: OK --=20 Karl Denninger karl@denninger.net /The Market Ticker/ /[S/MIME encrypted email preferred]/ --------------ms000006090104000406080004 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCC BlwwggZYMIIEQKADAgECAgE9MA0GCSqGSIb3DQEBCwUAMIGQMQswCQYDVQQGEwJVUzEQMA4G A1UECBMHRmxvcmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3Rl bXMgTExDMRwwGgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhND dWRhIFN5c3RlbXMgTExDIENBMB4XDTE2MTIxODE5NDUzNVoXDTIxMTIxNzE5NDUzNVowVzEL MAkGA1UEBhMCVVMxEDAOBgNVBAgTB0Zsb3JpZGExGTAXBgNVBAoTEEN1ZGEgU3lzdGVtcyBM TEMxGzAZBgNVBAMUEmthcmxAZGVubmluZ2VyLm5ldDCCAiIwDQYJKoZIhvcNAQEBBQADggIP ADCCAgoCggIBAM2N5maxs7NkoY9g5NMxFWll0TYiO7gXrGZTo3q25ZJgNdPMwrntLz/5ewE9 07TEbwJ3ah/Ep9BfZm7JF9vTtE1HkgKtXNKi0pawNGm1Yn26Dz5AbUr1byby6dFtDJr14E07 trzDCtRRvTkOVSBj6PQPal0fAnDtkIYQBVcuMkXkuMCtyfE95pjm8g4K9l7lAcKii3T1/3rE hCc1o2nBnb7EN1/XwBeCDGB+I2SN/ftZDbKQqGAF5q9dUn+iXU7Z/CVSfUWmhVh6cVZA4Ftv TglUqj410OuPx+cUQch3h1kFgsuhQR63HiJc3HbRJllHsV0rihvL1CjeARQkhnA6uY9NLFST p5I/PfzBzW2MSmtN/tGZvmfKKnmtbfUNgkzbIR1K3lsum+yEL71kB93Xtz/4f1demEx5c8TJ RBIniDHjDeLGK1aoBu8nfnvXAvgthFNTWBOEoR49AHEPjC3kZj0l8JQml1Y8bTQD5gtC5txl klO60WV0EufU7Hy9CmynMuFtjiA2v71pm097rXeCdrAKgisdYeEESB+SFrlY65rLiLv4n8o1 PX7DqRfqKkOYIakZ0ug/yHVKcq2EM3RiJxwzls5gT70CoOBlKbrC98O8TA6teON0Jq30M06t NTI2HhvNbJDLbBH+Awf4h1UKB+0ufENwjVvF5Jfz8Ww/FaSDAgMBAAGjgfQwgfEwNwYIKwYB BQUHAQEEKzApMCcGCCsGAQUFBzABhhtodHRwOi8vY3VkYXN5c3RlbXMubmV0Ojg4ODgwCQYD VR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQf Fh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUpfAI3y+751pp9A0w 6vJHx8RoR/MwHwYDVR0jBBgwFoAUJHGbnYV9/N3dvbDKkpQDofrTbTUwHQYDVR0RBBYwFIES a2FybEBkZW5uaW5nZXIubmV0MA0GCSqGSIb3DQEBCwUAA4ICAQBiB6MlugxYJdccD8boZ/u8 d8VxmLkJCtbfyYHRjYdyoABLW5hE3k3xSpYCM9L7vzWyV/UWwDYKi4ZzxHo4g+jG/GQZfKhx v38BQjL2G9xD0Hn2d+cygOq3UPjVYlbbfQoew6JbyCFXrrZ7/0jvRMLAN2+bRC7ynaFUixPH Whnj9JSH7ieYdzak8KN+G2coIC2t2iyfXVKehzi5gdNQ0vJ7+ypbGsRm4gE8Mdo9N/WgFPvZ HPFqR9Dwas7Z+aHwOabpk5r/336SyjOaZsn3MqKJQZL6GqDKusVOCWt+9uFAD8kadg7FetZe atIoD9I+zbp59oVoMnkMDMx7Hi85faU03csusqMGsjSsAzWSI1N8PJytZlchLiykokLKc3OL G87QKlErotlou7cfPX2BbEAH5wmkj9oiqZhxIL/wwAUA+PkiTbEmksKBNompSjUq/6UsR8EA s74gnu17lmijv8mrg2qMlwRirE7qG8pnE8egLtCDxcjd0Of9WMi2NJskn0/ovC7P+J60Napl m3ZIgPJst1piYSE0Zc1FIat4fFphMfK5v4iLblo1tFSlkdx1UNDGdg/U+LaXkNVXlMp8fyPm R80V6cIrCAlEWnBJNxG1UyfbbsvNMCCZBM4faGGsR/hhQOiydlruxhjL6P8J2WV8p11DdeGx KymWoil2s1J5WTGCBRMwggUPAgEBMIGWMIGQMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHRmxv cmlkYTESMBAGA1UEBxMJTmljZXZpbGxlMRkwFwYDVQQKExBDdWRhIFN5c3RlbXMgTExDMRww GgYDVQQDExNDdWRhIFN5c3RlbXMgTExDIENBMSIwIAYJKoZIhvcNAQkBFhNDdWRhIFN5c3Rl bXMgTExDIENBAgE9MA0GCWCGSAFlAwQCAwUAoIICTTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAyMDkyMTU2MDBaME8GCSqGSIb3DQEJBDFCBECU82Dm ttdouF0glatDoRxbvq8GlqoA6Mm/3ihR01DckW598aZSsN/BRcttqLcNOcnJdOW9Q1Ilib6F brQJi/azMGwGCSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggq hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZI hvcNAwICASgwgacGCSsGAQQBgjcQBDGBmTCBljCBkDELMAkGA1UEBhMCVVMxEDAOBgNVBAgT B0Zsb3JpZGExEjAQBgNVBAcTCU5pY2V2aWxsZTEZMBcGA1UEChMQQ3VkYSBTeXN0ZW1zIExM QzEcMBoGA1UEAxMTQ3VkYSBTeXN0ZW1zIExMQyBDQTEiMCAGCSqGSIb3DQEJARYTQ3VkYSBT eXN0ZW1zIExMQyBDQQIBPTCBqQYLKoZIhvcNAQkQAgsxgZmggZYwgZAxCzAJBgNVBAYTAlVT MRAwDgYDVQQIEwdGbG9yaWRhMRIwEAYDVQQHEwlOaWNldmlsbGUxGTAXBgNVBAoTEEN1ZGEg U3lzdGVtcyBMTEMxHDAaBgNVBAMTE0N1ZGEgU3lzdGVtcyBMTEMgQ0ExIjAgBgkqhkiG9w0B CQEWE0N1ZGEgU3lzdGVtcyBMTEMgQ0ECAT0wDQYJKoZIhvcNAQEBBQAEggIATxMilPKD9dME RW0l2tekMw6PkVlIOQk1lmEAHRe7XtZCejvtDbpE7llbEoT2NdRmjr4VnY/AHjQ48qV7CdN/ zq5kn8IDShS/9aC8WR6GzzA5VSfbdXOXd1ErPTixTPlSLF9cYM6mCLRHYxHZckrGwfNi4RTd 6Bb9Ec9eNV5Z2/lHfvW+l4G4INx+diXPOPHmZUygLxEfIIQLjcdQrVQ1p8nXTw21pxv5L7RH wdur9FEdR7t88eDtUc3oza3X9oyy/zbPtEBR8A/wANMroPiH5ZTPQ0xPb+rLrfsOz0urBMaF IqCVQYfVs+t8BboYmuMnyzPCYGEyjtm7iWS4W39ugePuvppd8MB08HvPoFke7gDxKHBIu1/p ZNpp2nlCsnBLbZSKoVdvRFabAOckbBVSqfvbsDAYfa3zgU9IqCMKLEV7dH2UTHm/bBqhLcM4 W3hpW4RiJ/+UTo0DNsU7zR/u+lNzxQoAmmYsT4+T74xVF6JhYN1ylEdDUh8ITsMJkbVhmTah p3OSwkczTZUC5iTlU28Yo0mGe2CTIpKwzkcwm8zLr6hPfxvym+T06lRR/6Bmqdk88dwhPpB3 wf5VPsz7Nmv3OYDoKANojSmaKpyP6r43UXD5zTs93UXH9zdfhZ8+cYeCzjCC0ZWhy2rY3wvx uUqJHXrD34TpbnNbKZP8ZVcAAAAAAAA= --------------ms000006090104000406080004-- From owner-freebsd-current@freebsd.org Thu Feb 9 22:02:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0628FCD84D7 for ; Thu, 9 Feb 2017 22:02:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D038B155B for ; Thu, 9 Feb 2017 22:02:57 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL400600NTHQV00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 09 Feb 2017 22:02:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486677763; bh=XrVZx2tXIsVWI3Wu4zPy+QLQjTJEir3NIM/KlwcWIGQ=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=UQTOSK/q0B/Qh0qwIYTa97FNPSMocAvqMogw5gdJ7UVIdTH7fEjEXdGPWSDtaH2wS uJCfiO18GBr510+4uSqAcjIJnPnMKE4vIEkOHdPAnCtdMd1INTNrUq01AXhijZYOs+ QFhxJzEuF/V2g9KPMSSMKQR81C9Es9xJUW/blBCWK2Oe5r7DgjaT3WVkpeMK0aDGwM 5TeZwLDCctvWfv5DAuD249LzyNCZjD/FpuYE0JZW9HUhbanUrTKSOMz4jvXTVBSDv7 f2s7Z+++fATE/ZVHhRf6TiBW+xbtOFl2QlFY+5J0d4SZGhkAylIaLdF01gF49k36i/ l8Xts0jBg6Djg== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL4005SRNWGYK10@st13p35im-asmtp002.me.com>; Thu, 09 Feb 2017 22:02:43 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-09_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702090198 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 From: Toomas Soome In-reply-to: <20170209213916.GA40599@bluezbox.com> Date: Fri, 10 Feb 2017 00:02:40 +0200 Cc: Karl Denninger , freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 22:02:58 -0000 > On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko = wrote: >=20 > Toomas Soome (tsoome@me.com) wrote: >>=20 >>> On 9. veebr 2017, at 17:05, Karl Denninger = wrote: >>>=20 >>>=20 >>> On 2/9/2017 08:58, Toomas Soome wrote: >>>>> On 9. veebr 2017, at 16:36, Karl Denninger = wrote: >>>>>=20 >>>>>=20 >>>>> On 2/8/2017 16:18, Karl Denninger wrote: >>>>>> r313441 blows up on the Pi3 in /boot/loader.efi with: >>>>>>=20 >>>>>> FreeBSD/arm64 EFI loader, Revision 1.1 >>>>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net = ) >>>>>> Failed to start image provided by UFS (14) >>>>>> "Synchronous Abort" handler, esr 0x96000004 >>>>>> ELR: 3af62cec >>>>>> LR: 3af61d60 >>>>>> x0 : 0000000000000001 x1 : 0000000000000001 >>>>>> x2 : 000000003afeb000 x3 : 000000000000003f >>>>>> x4 : 0000000000000020 x5 : 0000000000000010 >>>>>> x6 : 0000000000000000 x7 : 0000000039b260a4 >>>>>> x8 : 000000003af61d48 x9 : 000000000000000d >>>>>> x10: 0000000000000030 x11: 0000000000000000 >>>>>> x12: 0000000000000000 x13: 0000000000000002 >>>>>> x14: 0000000000000000 x15: 0000000000000000 >>>>>> x16: 0000000000000000 x17: 0000000000000000 >>>>>> x18: 000000003ab30df8 x19: 0000000037a16008 >>>>>> x20: 0000000000000000 x21: 0000000000000000 >>>>>> x22: 0000000039b28000 x23: 0000000039b1d49c >>>>>> x24: 0000000039b28850 x25: 000000003ab3d740 >>>>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 >>>>>> x28: 0000000000000000 x29: 000000003ab2ef60 >>>>>>=20 >>>>>> Resetting CPU ... >>>>>>=20 >>>>>> If you copy in a loader.efi from an earlier build (e.g. r313109) = then the system boots but complains about SMP problems, fails to start = any of the other CPUs (although it sees them) and panics before it = reaches a login prompt with what appears to be a problem reading the SD = card (I also get a couple of lor's in here too..... not sure if those = are "real" or false positives) >>>>>>=20 >>>>>> B >>>>> This has been isolated to r313333 in sys/boot/efi; reverting the = EFI >>>>> loader to a previous revision stops the crash. >>>>>=20 >>>>> Filed here: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940 = = = >>>>>=20 >>>> Does it still crash with r313442? I think it does and this is why: >>>>=20 >>>> =46rom your log above, the hint is "Failed to start image provided = by UFS (14)=E2=80=9D, so what we can guess here is that for some reason = the loader.efi main() failed to detect the boot device, and did return = back to boot1. >>>>=20 >>>> Boot1 did print out this error message and did call panic(). So, = the question is, why it is failing to detect the root fs handle. I=E2=80=99= ll try to check if I can replicate the issue with x86 + ufs. >>>>=20 >>>> BTW: sorry for trouble:) >>>>=20 >>>> rgds, >>>> toomas >>>>=20 >>> Yes. >>>=20 >>> It's isolated to that particular revision, which appears to have = reworked the enumeration of the available devices to boot from. = Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update = -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi = that successfully loads and starts the kernel. >>>=20 >>=20 >> Well, the x86 version does not appear to have problems with finding = the ufs devices. So this has to be some sort of corner case related to = arm:( unfortunately I do not have much variants to test arm, except = qemu=E2=80=A6 so some help would be needed there. Since the only crash = is from boot1 call to panic, I am pretty sure the disk detection and = setup was ok, so we should get disk list if we insert something like: >>=20 >> for (i =3D 0; devsw[i] !=3D NULL; i++) { >> if (devsw[i]->dv_print !=3D NULL){ >> if (devsw[i]->dv_print(verbose)) >> break; >> } >> } >>=20 >> after dv_init() loop. >>=20 >> If thats true, then it should not take too much to find why we fail = to get the handle for root fs in case of arm=E2=80=A6=20 >=20 >=20 > On RPi3 U-Boot EFI API provided by U-Boot and it's somewhat = non-standard > comapring to x86 EFI or specialized EFI firmwares of ARM64. I did some > debugging and found that U-Boot reports driver with subtype = MEDIA_FILEPATH_DP > so it's not recognized by disk handler. Quick hack below fixed boot > but it's not ideal and the device structure looks like this: >=20 > disk devices: > disk0: 15564801 X 512 blocks (removable) > disk0s1: DOS/Windows 49MB > disk0s2: FreeBSD 1856MB > disk0s2a: FreeBSD UFS 1856MB > disk1: 102375 X 512 blocks (removable) > disk2: 3802112 X 512 blocks (removable) > disk2a: FreeBSD UFS 1856MB > net devices: > net0: >=20 >=20 > disk1 and disk2 are actuallypartitions from disk0. > I can work on proper fix but not sure what should be > considered proper in this case. So some guidelines are welcome I think Karl got or is getting the same result as I am writing - we did = reach to the same point:) Yep, the idea behind the efipart_hdinfo_add() is that the first argument = is handle to the disk itself, so we can sort the partition handles into = the partition list in the disk. I think the logical step from there would be to dig out the path = structure and see if we can use something to identify the disk itself. So, the interesting part here also is that in your case it did dig out = the BSD label too. Ok, so the MEDIA_FILEPATH_DP has last node as CHAR16 file name, so we = need to pick the last node and cast to FILEPATH_DEVICE_PATH and then we = can see what that CHAR16 there has:) Also we may need to inspect all the nodes on the path, then we have = idea. Once we have method to identify the disk itself, then we should have the = solution. rgds, toomas >=20 > Patch: > Index: boot/efi/libefi/efipart.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- boot/efi/libefi/efipart.c (revision 313477) > +++ boot/efi/libefi/efipart.c (working copy) > @@ -467,6 +467,15 @@ > efipart_hdinfo_add(handle, efipart_handles[i]); > continue; > } > + > + /* > + * U-Boot case > + */ > + if (DevicePathType(node) =3D=3D MEDIA_DEVICE_PATH && > + DevicePathSubType(node) =3D=3D MEDIA_FILEPATH_DP) = { > + efipart_hdinfo_add(efipart_handles[i], = efipart_handles[i]); > + continue; > + } > } > } From owner-freebsd-current@freebsd.org Thu Feb 9 22:10:29 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F040CD86B8 for ; Thu, 9 Feb 2017 22:10:29 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 5ED3E18E5 for ; Thu, 9 Feb 2017 22:10:29 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cbwv0-000Adg-Hp; Thu, 09 Feb 2017 14:10:28 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v19MALMO040899; Thu, 9 Feb 2017 14:10:21 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 9 Feb 2017 14:10:21 -0800 From: Oleksandr Tymoshenko To: Toomas Soome Cc: Karl Denninger , freebsd-current@freebsd.org Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Message-ID: <20170209221021.GA40870@bluezbox.com> References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Toomas Soome (tsoome@me.com) wrote: > > > On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko wrote: > > > > Toomas Soome (tsoome@me.com) wrote: > >> > >>> On 9. veebr 2017, at 17:05, Karl Denninger wrote: > >>> > >>> > >>> On 2/9/2017 08:58, Toomas Soome wrote: > >>>>> On 9. veebr 2017, at 16:36, Karl Denninger wrote: > >>>>> > >>>>> > >>>>> On 2/8/2017 16:18, Karl Denninger wrote: > >>>>>> r313441 blows up on the Pi3 in /boot/loader.efi with: > >>>>>> > >>>>>> FreeBSD/arm64 EFI loader, Revision 1.1 > >>>>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net ) > >>>>>> Failed to start image provided by UFS (14) > >>>>>> "Synchronous Abort" handler, esr 0x96000004 > >>>>>> ELR: 3af62cec > >>>>>> LR: 3af61d60 > >>>>>> x0 : 0000000000000001 x1 : 0000000000000001 > >>>>>> x2 : 000000003afeb000 x3 : 000000000000003f > >>>>>> x4 : 0000000000000020 x5 : 0000000000000010 > >>>>>> x6 : 0000000000000000 x7 : 0000000039b260a4 > >>>>>> x8 : 000000003af61d48 x9 : 000000000000000d > >>>>>> x10: 0000000000000030 x11: 0000000000000000 > >>>>>> x12: 0000000000000000 x13: 0000000000000002 > >>>>>> x14: 0000000000000000 x15: 0000000000000000 > >>>>>> x16: 0000000000000000 x17: 0000000000000000 > >>>>>> x18: 000000003ab30df8 x19: 0000000037a16008 > >>>>>> x20: 0000000000000000 x21: 0000000000000000 > >>>>>> x22: 0000000039b28000 x23: 0000000039b1d49c > >>>>>> x24: 0000000039b28850 x25: 000000003ab3d740 > >>>>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 > >>>>>> x28: 0000000000000000 x29: 000000003ab2ef60 > >>>>>> > >>>>>> Resetting CPU ... > >>>>>> > >>>>>> If you copy in a loader.efi from an earlier build (e.g. r313109) then the system boots but complains about SMP problems, fails to start any of the other CPUs (although it sees them) and panics before it reaches a login prompt with what appears to be a problem reading the SD card (I also get a couple of lor's in here too..... not sure if those are [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: me.com] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 22:10:29 -0000 Toomas Soome (tsoome@me.com) wrote: > > > On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko wrote: > > > > Toomas Soome (tsoome@me.com) wrote: > >> > >>> On 9. veebr 2017, at 17:05, Karl Denninger wrote: > >>> > >>> > >>> On 2/9/2017 08:58, Toomas Soome wrote: > >>>>> On 9. veebr 2017, at 16:36, Karl Denninger wrote: > >>>>> > >>>>> > >>>>> On 2/8/2017 16:18, Karl Denninger wrote: > >>>>>> r313441 blows up on the Pi3 in /boot/loader.efi with: > >>>>>> > >>>>>> FreeBSD/arm64 EFI loader, Revision 1.1 > >>>>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net ) > >>>>>> Failed to start image provided by UFS (14) > >>>>>> "Synchronous Abort" handler, esr 0x96000004 > >>>>>> ELR: 3af62cec > >>>>>> LR: 3af61d60 > >>>>>> x0 : 0000000000000001 x1 : 0000000000000001 > >>>>>> x2 : 000000003afeb000 x3 : 000000000000003f > >>>>>> x4 : 0000000000000020 x5 : 0000000000000010 > >>>>>> x6 : 0000000000000000 x7 : 0000000039b260a4 > >>>>>> x8 : 000000003af61d48 x9 : 000000000000000d > >>>>>> x10: 0000000000000030 x11: 0000000000000000 > >>>>>> x12: 0000000000000000 x13: 0000000000000002 > >>>>>> x14: 0000000000000000 x15: 0000000000000000 > >>>>>> x16: 0000000000000000 x17: 0000000000000000 > >>>>>> x18: 000000003ab30df8 x19: 0000000037a16008 > >>>>>> x20: 0000000000000000 x21: 0000000000000000 > >>>>>> x22: 0000000039b28000 x23: 0000000039b1d49c > >>>>>> x24: 0000000039b28850 x25: 000000003ab3d740 > >>>>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 > >>>>>> x28: 0000000000000000 x29: 000000003ab2ef60 > >>>>>> > >>>>>> Resetting CPU ... > >>>>>> > >>>>>> If you copy in a loader.efi from an earlier build (e.g. r313109) then the system boots but complains about SMP problems, fails to start any of the other CPUs (although it sees them) and panics before it reaches a login prompt with what appears to be a problem reading the SD card (I also get a couple of lor's in here too..... not sure if those are "real" or false positives) > >>>>>> > >>>>>> B > >>>>> This has been isolated to r313333 in sys/boot/efi; reverting the EFI > >>>>> loader to a previous revision stops the crash. > >>>>> > >>>>> Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216940 > >>>>> > >>>> Does it still crash with r313442? I think it does and this is why: > >>>> > >>>> From your log above, the hint is "Failed to start image provided by UFS (14)”, so what we can guess here is that for some reason the loader.efi main() failed to detect the boot device, and did return back to boot1. > >>>> > >>>> Boot1 did print out this error message and did call panic(). So, the question is, why it is failing to detect the root fs handle. I’ll try to check if I can replicate the issue with x86 + ufs. > >>>> > >>>> BTW: sorry for trouble:) > >>>> > >>>> rgds, > >>>> toomas > >>>> > >>> Yes. > >>> > >>> It's isolated to that particular revision, which appears to have reworked the enumeration of the available devices to boot from. Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi that successfully loads and starts the kernel. > >>> > >> > >> Well, the x86 version does not appear to have problems with finding the ufs devices. So this has to be some sort of corner case related to arm:( unfortunately I do not have much variants to test arm, except qemu… so some help would be needed there. Since the only crash is from boot1 call to panic, I am pretty sure the disk detection and setup was ok, so we should get disk list if we insert something like: > >> > >> for (i = 0; devsw[i] != NULL; i++) { > >> if (devsw[i]->dv_print != NULL){ > >> if (devsw[i]->dv_print(verbose)) > >> break; > >> } > >> } > >> > >> after dv_init() loop. > >> > >> If thats true, then it should not take too much to find why we fail to get the handle for root fs in case of arm… > > > > > > On RPi3 U-Boot EFI API provided by U-Boot and it's somewhat non-standard > > comapring to x86 EFI or specialized EFI firmwares of ARM64. I did some > > debugging and found that U-Boot reports driver with subtype MEDIA_FILEPATH_DP > > so it's not recognized by disk handler. Quick hack below fixed boot > > but it's not ideal and the device structure looks like this: > > > > disk devices: > > disk0: 15564801 X 512 blocks (removable) > > disk0s1: DOS/Windows 49MB > > disk0s2: FreeBSD 1856MB > > disk0s2a: FreeBSD UFS 1856MB > > disk1: 102375 X 512 blocks (removable) > > disk2: 3802112 X 512 blocks (removable) > > disk2a: FreeBSD UFS 1856MB > > net devices: > > net0: > > > > > > disk1 and disk2 are actuallypartitions from disk0. > > I can work on proper fix but not sure what should be > > considered proper in this case. So some guidelines are welcome > > > I think Karl got or is getting the same result as I am writing - we did reach to the same point:) > > Yep, the idea behind the efipart_hdinfo_add() is that the first argument is handle to the disk itself, so we can sort the partition handles into the partition list in the disk. > > I think the logical step from there would be to dig out the path structure and see if we can use something to identify the disk itself. > > So, the interesting part here also is that in your case it did dig out the BSD label too. > > > Ok, so the MEDIA_FILEPATH_DP has last node as CHAR16 file name, so we need to pick the last node and cast to FILEPATH_DEVICE_PATH and then we can see what that CHAR16 there has:) > > Also we may need to inspect all the nodes on the path, then we have idea. > > Once we have method to identify the disk itself, then we should have the solution. >From reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks like names are in the form of typeN:M, where type is interface type, N is disk id and M is partition id. So 3 disks in my setup may be mmc0, mmc0:1, mmc0:2. -- gonzo From owner-freebsd-current@freebsd.org Thu Feb 9 22:16:56 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69955CD8A3F for ; Thu, 9 Feb 2017 22:16:56 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3EB771F32 for ; Thu, 9 Feb 2017 22:16:56 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL400G00OEB8300@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Thu, 09 Feb 2017 22:16:55 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486678615; bh=moNJL9pF8GfFNuqgsk1dLwtF6oC6CoriCZ5vOYr8R6Y=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=h8x41lkHlHTEaQQ75vqlrl2N3eSyf22Rm0tIjNwUkTEiuFVqX/3MDh+mAMToWudhQ I3BDXKkxnv+/fiQWiHAxZpq3RL9L4vu4MxEoGDBUpFLihs5ct213Bm3N/VnEHWyhUk L1GtiSjPsprQfFzX1AdRpfyuHDz5kubkezY2aAIo3UC7EyZKnJMeEZbUWvaKmqgHGu /WoSl3GyWVrCXguZSSAgoipGkJl0nJBijMncrhO56CC/TosrjrEvnd6fCb0nq2xIU8 nHZj3hhhnfWf9HtRiJ8Dd0MwnmxX98MQ56rCKKxx0+tC8MUOotegyixFnNEc56PtBH MW0Zp/l64/E+A== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL400GG7OK4TO30@st13p35im-asmtp002.me.com>; Thu, 09 Feb 2017 22:16:55 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-09_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702090200 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 From: Toomas Soome In-reply-to: <20170209221021.GA40870@bluezbox.com> Date: Fri, 10 Feb 2017 00:16:51 +0200 Cc: Karl Denninger , freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <64E64B7F-E1BE-4CC6-ACAB-E5D7FEE408C8@me.com> References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> <20170209221021.GA40870@bluezbox.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 22:16:56 -0000 > On 10. veebr 2017, at 0:10, Oleksandr Tymoshenko = wrote: >=20 > Toomas Soome (tsoome@me.com) wrote: >>=20 >>> On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko = wrote: >>>=20 >>> Toomas Soome (tsoome@me.com) wrote: >>>>=20 >>>>> On 9. veebr 2017, at 17:05, Karl Denninger = wrote: >>>>>=20 >>>>>=20 >>>>> On 2/9/2017 08:58, Toomas Soome wrote: >>>>>>> On 9. veebr 2017, at 16:36, Karl Denninger = wrote: >>>>>>>=20 >>>>>>>=20 >>>>>>> On 2/8/2017 16:18, Karl Denninger wrote: >>>>>>>> r313441 blows up on the Pi3 in /boot/loader.efi with: >>>>>>>>=20 >>>>>>>> FreeBSD/arm64 EFI loader, Revision 1.1 >>>>>>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net = ) >>>>>>>> Failed to start image provided by UFS (14) >>>>>>>> "Synchronous Abort" handler, esr 0x96000004 >>>>>>>> ELR: 3af62cec >>>>>>>> LR: 3af61d60 >>>>>>>> x0 : 0000000000000001 x1 : 0000000000000001 >>>>>>>> x2 : 000000003afeb000 x3 : 000000000000003f >>>>>>>> x4 : 0000000000000020 x5 : 0000000000000010 >>>>>>>> x6 : 0000000000000000 x7 : 0000000039b260a4 >>>>>>>> x8 : 000000003af61d48 x9 : 000000000000000d >>>>>>>> x10: 0000000000000030 x11: 0000000000000000 >>>>>>>> x12: 0000000000000000 x13: 0000000000000002 >>>>>>>> x14: 0000000000000000 x15: 0000000000000000 >>>>>>>> x16: 0000000000000000 x17: 0000000000000000 >>>>>>>> x18: 000000003ab30df8 x19: 0000000037a16008 >>>>>>>> x20: 0000000000000000 x21: 0000000000000000 >>>>>>>> x22: 0000000039b28000 x23: 0000000039b1d49c >>>>>>>> x24: 0000000039b28850 x25: 000000003ab3d740 >>>>>>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 >>>>>>>> x28: 0000000000000000 x29: 000000003ab2ef60 >>>>>>>>=20 >>>>>>>> Resetting CPU ... >>>>>>>>=20 >>>>>>>> If you copy in a loader.efi from an earlier build (e.g. = r313109) then the system boots but complains about SMP problems, fails = to start any of the other CPUs (although it sees them) and panics before = it reaches a login prompt with what appears to be a problem reading the = SD card (I also get a couple of lor's in here too..... not sure if those = are "real" or false positives) >>>>>>>>=20 >>>>>>>> B >>>>>>> This has been isolated to r313333 in sys/boot/efi; reverting the = EFI >>>>>>> loader to a previous revision stops the crash. >>>>>>>=20 >>>>>>> Filed here: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216940 = = = >>>>>>>=20 >>>>>> Does it still crash with r313442? I think it does and this is = why: >>>>>>=20 >>>>>> =46rom your log above, the hint is "Failed to start image = provided by UFS (14)=E2=80=9D, so what we can guess here is that for = some reason the loader.efi main() failed to detect the boot device, and = did return back to boot1. >>>>>>=20 >>>>>> Boot1 did print out this error message and did call panic(). So, = the question is, why it is failing to detect the root fs handle. I=E2=80=99= ll try to check if I can replicate the issue with x86 + ufs. >>>>>>=20 >>>>>> BTW: sorry for trouble:) >>>>>>=20 >>>>>> rgds, >>>>>> toomas >>>>>>=20 >>>>> Yes. >>>>>=20 >>>>> It's isolated to that particular revision, which appears to have = reworked the enumeration of the available devices to boot from. = Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update = -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi = that successfully loads and starts the kernel. >>>>>=20 >>>>=20 >>>> Well, the x86 version does not appear to have problems with finding = the ufs devices. So this has to be some sort of corner case related to = arm:( unfortunately I do not have much variants to test arm, except = qemu=E2=80=A6 so some help would be needed there. Since the only crash = is from boot1 call to panic, I am pretty sure the disk detection and = setup was ok, so we should get disk list if we insert something like: >>>>=20 >>>> for (i =3D 0; devsw[i] !=3D NULL; i++) { >>>> if (devsw[i]->dv_print !=3D NULL){ >>>> if (devsw[i]->dv_print(verbose)) >>>> break; >>>> } >>>> } >>>>=20 >>>> after dv_init() loop. >>>>=20 >>>> If thats true, then it should not take too much to find why we fail = to get the handle for root fs in case of arm=E2=80=A6=20 >>>=20 >>>=20 >>> On RPi3 U-Boot EFI API provided by U-Boot and it's somewhat = non-standard >>> comapring to x86 EFI or specialized EFI firmwares of ARM64. I did = some >>> debugging and found that U-Boot reports driver with subtype = MEDIA_FILEPATH_DP >>> so it's not recognized by disk handler. Quick hack below fixed boot >>> but it's not ideal and the device structure looks like this: >>>=20 >>> disk devices: >>> disk0: 15564801 X 512 blocks (removable) >>> disk0s1: DOS/Windows 49MB >>> disk0s2: FreeBSD 1856MB >>> disk0s2a: FreeBSD UFS 1856MB >>> disk1: 102375 X 512 blocks (removable) >>> disk2: 3802112 X 512 blocks (removable) >>> disk2a: FreeBSD UFS 1856MB >>> net devices: >>> net0: >>>=20 >>>=20 >>> disk1 and disk2 are actuallypartitions from disk0. >>> I can work on proper fix but not sure what should be >>> considered proper in this case. So some guidelines are welcome >>=20 >>=20 >> I think Karl got or is getting the same result as I am writing - we = did reach to the same point:) >>=20 >> Yep, the idea behind the efipart_hdinfo_add() is that the first = argument is handle to the disk itself, so we can sort the partition = handles into the partition list in the disk. >>=20 >> I think the logical step from there would be to dig out the path = structure and see if we can use something to identify the disk itself. >>=20 >> So, the interesting part here also is that in your case it did dig = out the BSD label too. >>=20 >>=20 >> Ok, so the MEDIA_FILEPATH_DP has last node as CHAR16 file name, so we = need to pick the last node and cast to FILEPATH_DEVICE_PATH and then we = can see what that CHAR16 there has:) >>=20 >> Also we may need to inspect all the nodes on the path, then we have = idea. >>=20 >> Once we have method to identify the disk itself, then we should have = the solution. >=20 > =46rom reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks = like > names are in the form of typeN:M, where type is interface type, > N is disk id and M is partition id. So 3 disks in my setup > may be mmc0, mmc0:1, mmc0:2.=20 >=20 > --=20 > gonzo Okay, so in case of arm or MEDIA_FILEPATH_DP we need to keep the initial = disk handle till there is an disk switch, and use it as first argument = for registering the disk. So the name in last node is probably the same = format and we can identify the disk this way. Worth to check in any = case:) rgds, toomas From owner-freebsd-current@freebsd.org Thu Feb 9 22:17:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 251D3CD8A71 for ; Thu, 9 Feb 2017 22:17:11 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 E8A421FF7 for ; Thu, 9 Feb 2017 22:17:10 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cbwQv-000AZP-9q; Thu, 09 Feb 2017 13:39:23 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v19LdGXA040634; Thu, 9 Feb 2017 13:39:16 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Thu, 9 Feb 2017 13:39:16 -0800 From: Oleksandr Tymoshenko To: Toomas Soome Cc: Karl Denninger , freebsd-current@freebsd.org Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Message-ID: <20170209213916.GA40599@bluezbox.com> References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Toomas Soome (tsoome@me.com) wrote: > > > On 9. veebr 2017, at 17:05, Karl Denninger wrote: > > > > > > On 2/9/2017 08:58, Toomas Soome wrote: > >>> On 9. veebr 2017, at 16:36, Karl Denninger wrote: > >>> > >>> > >>> On 2/8/2017 16:18, Karl Denninger wrote: > >>>> r313441 blows up on the Pi3 in /boot/loader.efi with: > >>>> > >>>> FreeBSD/arm64 EFI loader, Revision 1.1 > >>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net ) > >>>> Failed to start image provided by UFS (14) > >>>> "Synchronous Abort" handler, esr 0x96000004 > >>>> ELR: 3af62cec > >>>> LR: 3af61d60 > >>>> x0 : 0000000000000001 x1 : 0000000000000001 > >>>> x2 : 000000003afeb000 x3 : 000000000000003f > >>>> x4 : 0000000000000020 x5 : 0000000000000010 > >>>> x6 : 0000000000000000 x7 : 0000000039b260a4 > >>>> x8 : 000000003af61d48 x9 : 000000000000000d > >>>> x10: 0000000000000030 x11: 0000000000000000 > >>>> x12: 0000000000000000 x13: 0000000000000002 > >>>> x14: 0000000000000000 x15: 0000000000000000 > >>>> x16: 0000000000000000 x17: 0000000000000000 > >>>> x18: 000000003ab30df8 x19: 0000000037a16008 > >>>> x20: 0000000000000000 x21: 0000000000000000 > >>>> x22: 0000000039b28000 x23: 0000000039b1d49c > >>>> x24: 0000000039b28850 x25: 000000003ab3d740 > >>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 > >>>> x28: 0000000000000000 x29: 000000003ab2ef60 > >>>> > >>>> Resetting CPU ... > >>>> > >>>> If you copy in a loader.efi from an earlier build (e.g. r313109) then the system boots but complains about SMP problems, fails to start any of the other CPUs (although it sees them) and panics before it reaches a login prompt with what appears to be a problem reading the SD card (I also get a couple of lor's in here too..... not sure if those are "real" or false positives) > >>>> > >>>> B > >>> This has been isolated to r313333 in sys/boot/efi; reverting the EFI > >>> loader to a previous revision stops the crash. > >>> > >>> Filed here: [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: me.com] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 22:17:11 -0000 Toomas Soome (tsoome@me.com) wrote: > > > On 9. veebr 2017, at 17:05, Karl Denninger wrote: > > > > > > On 2/9/2017 08:58, Toomas Soome wrote: > >>> On 9. veebr 2017, at 16:36, Karl Denninger wrote: > >>> > >>> > >>> On 2/8/2017 16:18, Karl Denninger wrote: > >>>> r313441 blows up on the Pi3 in /boot/loader.efi with: > >>>> > >>>> FreeBSD/arm64 EFI loader, Revision 1.1 > >>>> (Tue Feb 7 15:15:52 CST 2017 freebsd@NewFS.denninger.net ) > >>>> Failed to start image provided by UFS (14) > >>>> "Synchronous Abort" handler, esr 0x96000004 > >>>> ELR: 3af62cec > >>>> LR: 3af61d60 > >>>> x0 : 0000000000000001 x1 : 0000000000000001 > >>>> x2 : 000000003afeb000 x3 : 000000000000003f > >>>> x4 : 0000000000000020 x5 : 0000000000000010 > >>>> x6 : 0000000000000000 x7 : 0000000039b260a4 > >>>> x8 : 000000003af61d48 x9 : 000000000000000d > >>>> x10: 0000000000000030 x11: 0000000000000000 > >>>> x12: 0000000000000000 x13: 0000000000000002 > >>>> x14: 0000000000000000 x15: 0000000000000000 > >>>> x16: 0000000000000000 x17: 0000000000000000 > >>>> x18: 000000003ab30df8 x19: 0000000037a16008 > >>>> x20: 0000000000000000 x21: 0000000000000000 > >>>> x22: 0000000039b28000 x23: 0000000039b1d49c > >>>> x24: 0000000039b28850 x25: 000000003ab3d740 > >>>> x26: 000000003af839a0 x27: 0000000039b2e3e8 > >>>> x28: 0000000000000000 x29: 000000003ab2ef60 > >>>> > >>>> Resetting CPU ... > >>>> > >>>> If you copy in a loader.efi from an earlier build (e.g. r313109) then the system boots but complains about SMP problems, fails to start any of the other CPUs (although it sees them) and panics before it reaches a login prompt with what appears to be a problem reading the SD card (I also get a couple of lor's in here too..... not sure if those are "real" or false positives) > >>>> > >>>> B > >>> This has been isolated to r313333 in sys/boot/efi; reverting the EFI > >>> loader to a previous revision stops the crash. > >>> > >>> Filed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216940 > >>> > >> Does it still crash with r313442? I think it does and this is why: > >> > >> From your log above, the hint is "Failed to start image provided by UFS (14)”, so what we can guess here is that for some reason the loader.efi main() failed to detect the boot device, and did return back to boot1. > >> > >> Boot1 did print out this error message and did call panic(). So, the question is, why it is failing to detect the root fs handle. I’ll try to check if I can replicate the issue with x86 + ufs. > >> > >> BTW: sorry for trouble:) > >> > >> rgds, > >> toomas > >> > > Yes. > > > > It's isolated to that particular revision, which appears to have reworked the enumeration of the available devices to boot from. Reverting only sys/boot/efi to anything before 313333 (e.g. "svn update -r 313332 ." in src/sys/boot/efi) and rebuilding results in a loader.efi that successfully loads and starts the kernel. > > > > Well, the x86 version does not appear to have problems with finding the ufs devices. So this has to be some sort of corner case related to arm:( unfortunately I do not have much variants to test arm, except qemu… so some help would be needed there. Since the only crash is from boot1 call to panic, I am pretty sure the disk detection and setup was ok, so we should get disk list if we insert something like: > > for (i = 0; devsw[i] != NULL; i++) { > if (devsw[i]->dv_print != NULL){ > if (devsw[i]->dv_print(verbose)) > break; > } > } > > after dv_init() loop. > > If thats true, then it should not take too much to find why we fail to get the handle for root fs in case of arm… On RPi3 U-Boot EFI API provided by U-Boot and it's somewhat non-standard comapring to x86 EFI or specialized EFI firmwares of ARM64. I did some debugging and found that U-Boot reports driver with subtype MEDIA_FILEPATH_DP so it's not recognized by disk handler. Quick hack below fixed boot but it's not ideal and the device structure looks like this: disk devices: disk0: 15564801 X 512 blocks (removable) disk0s1: DOS/Windows 49MB disk0s2: FreeBSD 1856MB disk0s2a: FreeBSD UFS 1856MB disk1: 102375 X 512 blocks (removable) disk2: 3802112 X 512 blocks (removable) disk2a: FreeBSD UFS 1856MB net devices: net0: disk1 and disk2 are actuallypartitions from disk0. I can work on proper fix but not sure what should be considered proper in this case. So some guidelines are welcome Patch: Index: boot/efi/libefi/efipart.c =================================================================== --- boot/efi/libefi/efipart.c (revision 313477) +++ boot/efi/libefi/efipart.c (working copy) @@ -467,6 +467,15 @@ efipart_hdinfo_add(handle, efipart_handles[i]); continue; } + + /* + * U-Boot case + */ + if (DevicePathType(node) == MEDIA_DEVICE_PATH && + DevicePathSubType(node) == MEDIA_FILEPATH_DP) { + efipart_hdinfo_add(efipart_handles[i], efipart_handles[i]); + continue; + } } } From owner-freebsd-current@freebsd.org Fri Feb 10 10:28:15 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B45ACD913B for ; Fri, 10 Feb 2017 10:28:15 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E50361486 for ; Fri, 10 Feb 2017 10:28:14 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OL500900MB2IB00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Fri, 10 Feb 2017 10:28:13 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1486722493; bh=eCAtAj3EEW2W0ElJHkeV+zjkqGDM/Dyqbwdl4TVcZY0=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=JxBvGV4GlFVkVpoMYYhPebZnXX3a6xeES3pHT84Qp8P9ui5ypEcri1nWwKUXxiidW PAe7hOEAMR4aDydXTlOlnVamowql6lEePluF0l85IrF4l6xhiPu4rmzlkgj0ooWn5H EjhXPtscSBVe1liqXdnSFmMMTKZ5f22CGIo61vGgTSoCGOPWpCxzp194zfrcurq9KO b0kfKa9N3r5hGMp0ljjcz4cs6dYKhf89MvhJIXewgROfHZadhWM51NK9vyldv9Q9de JTZbf8/b83RG6pAyavGCFerpQQ2h+SSw6K4vYCvChTmuCDTre3aF9UrcLFolfsMa/3 mDJEndkWUQ7mQ== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OL5009ZOMEZXD20@st13p35im-asmtp002.me.com>; Fri, 10 Feb 2017 10:28:13 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-10_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702100105 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 From: Toomas Soome In-reply-to: <64E64B7F-E1BE-4CC6-ACAB-E5D7FEE408C8@me.com> Date: Fri, 10 Feb 2017 12:28:10 +0200 Cc: Karl Denninger , freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <0E030158-CF2C-4A95-93EB-E06061689A6E@me.com> References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> <20170209221021.GA40870@bluezbox.com> <64E64B7F-E1BE-4CC6-ACAB-E5D7FEE408C8@me.com> To: Oleksandr Tymoshenko X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 10:28:15 -0000 >>=20 >> =46rom reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks = like >> names are in the form of typeN:M, where type is interface type, >> N is disk id and M is partition id. So 3 disks in my setup >> may be mmc0, mmc0:1, mmc0:2.=20 >>=20 >> --=20 >> gonzo >=20 > Okay, so in case of arm or MEDIA_FILEPATH_DP we need to keep the = initial disk handle till there is an disk switch, and use it as first = argument for registering the disk. So the name in last node is probably = the same format and we can identify the disk this way. Worth to check in = any case:) >=20 Based on current knowledge, I did put together the first sketch of the = fix: https://reviews.freebsd.org/D9520 However, it needs to be tested on arm, so I do ask help there:) rgds, toomas From owner-freebsd-current@freebsd.org Fri Feb 10 13:19:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A63EBCD6E90 for ; Fri, 10 Feb 2017 13:19:11 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76D56371 for ; Fri, 10 Feb 2017 13:19:11 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 017AD1C6450; Fri, 10 Feb 2017 21:09:54 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id BB9D21C644A for ; Fri, 10 Feb 2017 21:09:54 +0800 (CST) Date: Fri, 10 Feb 2017 21:09:52 +0800 From: Iblis Lin To: freebsd-current@freebsd.org Subject: r313494 make perl File::Temp broken Message-ID: <20170210130952.GA70284@abeing> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.071492, version=1.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 13:19:11 -0000 Hi, as not a perl programmer myself. I have no idea what is going on. I found this issue while compiling math/openblas. [iblis@ns]% uname -a FreeBSD ns 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313500: Fri Feb 10 16:39:21 CST 2017 root@ns:/usr/obj/usr/src/sys/GENERIC amd64 [iblis@ns]% cat test.pl use File::Temp qw(tempfile); $tmpf = new File::Temp( UNLINK => 1 ); [iblis@ns]% perl test.pl Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create temp file /tmp/dI5uhUsijR: Bad file descriptor at test.pl line 2. And part of truss's output: close(3) = 0 (0x0) stat("/tmp/",{ mode=drwxrwxrwt ,inode=24317568,size=1024,blksize=32768 }) = 0 (0x0) stat("/tmp/",{ mode=drwxrwxrwt ,inode=24317568,size=1024,blksize=32768 }) = 0 (0x0) openat(AT_FDCWD,"/tmp/Nn0Epra5ff",O_RDWR|O_EXLOCK|O_NOFOLLOW|O_CREAT|O_EXCL,0600) ERR#9 'Bad file descriptor' stat("/usr/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such file or directory' stat("/usr/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such file or directory' stat("/usr/local/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such file or directory' stat("/usr/local/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such file or directory' Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create temp file /tmp/Nn0Epra5ff: Bad file descriptor at test.pl line 2. write(2,"Error in tempfile() using templa"...,135) = 135 (0x87) -- Iblis Lin 林峻頤 From owner-freebsd-current@freebsd.org Fri Feb 10 13:30:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FF90CD81AC for ; Fri, 10 Feb 2017 13:30:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8ABD2C16 for ; Fri, 10 Feb 2017 13:30:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 86679CD81A8; Fri, 10 Feb 2017 13:30:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8609DCD81A6 for ; Fri, 10 Feb 2017 13:30:02 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 5CD89C15 for ; Fri, 10 Feb 2017 13:30:01 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v1ADTs7N077946 for ; Fri, 10 Feb 2017 13:29:54 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v1ADTsRw077945 for current@freebsd.org; Fri, 10 Feb 2017 05:29:54 -0800 (PST) (envelope-from david) Date: Fri, 10 Feb 2017 05:29:54 -0800 From: David Wolfskill To: current@freebsd.org Subject: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor Message-ID: <20170210132954.GE1523@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="BBpm95f3IOry5CQh" Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 13:30:02 -0000 --BBpm95f3IOry5CQh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This was head @r313544; previous successful build/smoke test was @r313467 (yesterday). Here's an excerpt from a typescript I made of some "poking around"; subsequent to that, I was able to set the IP address, netmask, and broadcast address on the NIC (wlano), then set the default route, and once that was done, I was able to use the network: wlan0: flags=3D8843 metric 0 mtu 15= 00 ether 00:24:d6:7a:03:ce inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255=20 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid lmdhw-net channel 1 (2412 MHz 11g ht/20) bssid 04:18:d6:22:22:= 1f regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan=20 (12.0-C)[4] pgrep dhclient (12.0-C)[5] dhclient wlan0 dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT dhclient: Leaving hostname set to=20 dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT dhclient: reason was PREINIT; no action taken dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor exiting. (12.0-C)[6] ls -lTio /var/db/dhclient.leases* 883105 ---------- 1 root wheel - 4017 Jan 4 09:18:10 2017 /var/db/dhcli= ent.leases.em0 883280 ---------- 1 root wheel - 856 Aug 11 04:52:54 2015 /var/db/dhcli= ent.leases.lagg0 883344 ---------- 1 root wheel - 3333 Jan 20 21:19:10 2015 /var/db/dhcli= ent.leases.vboxnet0 883108 ---------- 1 root wheel - 1993 Feb 10 04:30:13 2017 /var/db/dhcli= ent.leases.wlan0 883079 ---------- 1 root wheel - 2013 Jan 19 11:52:07 2017 /var/db/dhcli= ent.leases.wlan1 Moving /var/db/dhclient.leases.wlan0 aside did not change the behavior. Stable/11 shows the iwn(4) device as: g1-252(11.0-S)[4] pciconf -lv | grep -A 3 iwn iwn0@pci0:3:0:0: class=3D0x028000 card=3D0x13218086 chip=3D0x4232808= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'WiFi Link 5100' class =3D network g1-252(11.0-S)[5]=20 File system for /var is a fairly vanilla UFS2+SU. I suppose I could have tried ktrace (had I thought of it before switching back to the stable/11 slice). Peace, david --=20 David H. Wolfskill david@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying con-man??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --BBpm95f3IOry5CQh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYncBSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XEfkIAJkbuOXFjkfzsZsjNWrzcOOr Id9IE/NI7zshi2Icmu6/8rorAIj0AnNxHuuof7CAbi3ddgmx7MgCjvzUAe61Srd8 XuqJFEJjOyU0Wl00rSj2k1FZ1f2bImwrlqnwfaqXGoqFBTs9FNUHMhCpIgsZNXhi XSGwHr6ctGG9z7ot0Gclb5vS13mPc27NFZG6Gzd/dKWUCWb76xQsOFPM5ogKOreo fvypnO+olL5dDr8c77UeGtlpJ2BDQCnQVSsPvxPMh2WRlFmT4VZbjEsQkJIX8/zN RaCAOguhLLS6IgFR5XzJpD3wSCOKE2O6F22GpL9nhEKFyb+3/xtXW6jwTrhwiLg= =IWjn -----END PGP SIGNATURE----- --BBpm95f3IOry5CQh-- From owner-freebsd-current@freebsd.org Fri Feb 10 13:37:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70E21CD85F6 for ; Fri, 10 Feb 2017 13:37:20 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::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 2FB1110C2 for ; Fri, 10 Feb 2017 13:37:20 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3vKbbG1XnnzZ9; Fri, 10 Feb 2017 14:37:14 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1486733829; x=1489325830; bh=m94 qZVqDrX/brLlL0HnNaKnDSFIhUvdlD9JlEMLpjUA=; b=eDCypPAWNLIJBvAfWo9 3tcSlUExnZ7hdqCX6kWEbLqtKzVK8B8O/toS7/LLwkZ+Yl/iaJvzfJyfSQJAGzNO zRMZw8C3mJOUJjzZNbT6GeHeFLLau/E+4uRZ/7y5IzqgHjxzlBR2vZvOUzkHv9yo 2+Xn3Zl/gH/JTzK6yK6m+O5o= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id ACvQKXZjXmwp; Fri, 10 Feb 2017 14:37:09 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3vKbb60hS9zZ1; Fri, 10 Feb 2017 14:37:06 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3vKbb56xF6zHP; Fri, 10 Feb 2017 14:37:05 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by webmail.ijs.si with HTTP (HTTP/1.1 POST); Fri, 10 Feb 2017 14:37:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 10 Feb 2017 14:37:05 +0100 From: Mark Martinec To: freebsd-current@freebsd.org Cc: Iblis Lin Subject: Re: r313494 make perl File::Temp broken Organization: Jozef Stefan Institute In-Reply-To: <20170210130952.GA70284@abeing> References: <20170210130952.GA70284@abeing> Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 13:37:20 -0000 2017-02-10 14:09, Iblis Lin wrote: > as not a perl programmer myself. I have no idea what is going on. > I found this issue while compiling math/openblas. > > [iblis@ns]% uname -a > FreeBSD ns 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313500: Fri Feb 10 > 16:39:21 > CST 2017 root@ns:/usr/obj/usr/src/sys/GENERIC amd64 > > [iblis@ns]% cat test.pl > use File::Temp qw(tempfile); > $tmpf = new File::Temp( UNLINK => 1 ); > > [iblis@ns]% perl test.pl > Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create > temp file > /tmp/dI5uhUsijR: Bad file descriptor at test.pl line 2. [...] > stat("/tmp/",{ mode=drwxrwxrwt > ,inode=24317568,size=1024,blksize=32768}) = 0 (0x0) > stat("/tmp/",{ mode=drwxrwxrwt > ,inode=24317568,size=1024,blksize=32768}) = 0 (0x0) > openat(AT_FDCWD,"/tmp/Nn0Epra5ff",O_RDWR|O_EXLOCK|O_NOFOLLOW|O_CREAT|O_EXCL,0600) > ERR#9 'Bad file descriptor' Perhaps your /tmp is a logical link, and O_NOFOLLOW does not allow that. Mark From owner-freebsd-current@freebsd.org Fri Feb 10 13:50:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99DBACD89E9 for ; Fri, 10 Feb 2017 13:50:58 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6974B1803 for ; Fri, 10 Feb 2017 13:50:58 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 90C501C6473; Fri, 10 Feb 2017 21:50:56 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id 52D3A1C644A; Fri, 10 Feb 2017 21:50:56 +0800 (CST) Date: Fri, 10 Feb 2017 21:50:55 +0800 From: Iblis Lin To: Mark Martinec Cc: freebsd-current@freebsd.org Subject: Re: r313494 make perl File::Temp broken Message-ID: <20170210135054.GB70284@abeing> References: <20170210130952.GA70284@abeing> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.339787, version=1.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 13:50:58 -0000 On Fri, Feb 10, 2017 at 02:37:05PM +0100, Mark Martinec wrote: > 2017-02-10 14:09, Iblis Lin wrote: > > as not a perl programmer myself. I have no idea what is going on. > > I found this issue while compiling math/openblas. > > > > [iblis@ns]% uname -a > > FreeBSD ns 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313500: Fri Feb 10 > > 16:39:21 > > CST 2017 root@ns:/usr/obj/usr/src/sys/GENERIC amd64 > > > > [iblis@ns]% cat test.pl > > use File::Temp qw(tempfile); > > $tmpf = new File::Temp( UNLINK => 1 ); > > > > [iblis@ns]% perl test.pl > > Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create > > temp file > > /tmp/dI5uhUsijR: Bad file descriptor at test.pl line 2. > > [...] > > > stat("/tmp/",{ mode=drwxrwxrwt > > ,inode=24317568,size=1024,blksize=32768}) = 0 (0x0) > > stat("/tmp/",{ mode=drwxrwxrwt > > ,inode=24317568,size=1024,blksize=32768}) = 0 (0x0) > > openat(AT_FDCWD,"/tmp/Nn0Epra5ff",O_RDWR|O_EXLOCK|O_NOFOLLOW|O_CREAT|O_EXCL,0600) > > ERR#9 'Bad file descriptor' > > > Perhaps your /tmp is a logical link, and O_NOFOLLOW does not allow that. > > Mark hmm... no, it's no a logical link. I just reverted the file changed in r313494 (sys/kern/vfs_vnops.c), and perl is happy again. -- Iblis Lin 林峻頤 From owner-freebsd-current@freebsd.org Fri Feb 10 13:55:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61CAACD8C43 for ; Fri, 10 Feb 2017 13:55:42 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3180B1CCE for ; Fri, 10 Feb 2017 13:55:40 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 5D5011C6450; Fri, 10 Feb 2017 21:55:37 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id 2086E1C644A for ; Fri, 10 Feb 2017 21:55:30 +0800 (CST) Date: Fri, 10 Feb 2017 21:55:29 +0800 From: Iblis Lin To: freebsd-current@freebsd.org Subject: Re: r313495 make perl File::Temp broken Message-ID: <20170210135529.GC70284@abeing> References: <20170210130952.GA70284@abeing> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170210130952.GA70284@abeing> User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.216592, version=1.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 13:55:42 -0000 I just found i miss-typed the revision number in subject. It's r313495. (https://svnweb.freebsd.org/base/head/sys/kern/vfs_vnops.c?r1=313495&r2=313494&pathrev=313495) On Fri, Feb 10, 2017 at 09:09:52PM +0800, Iblis Lin wrote: > Hi, > > as not a perl programmer myself. I have no idea what is going on. > I found this issue while compiling math/openblas. > > [iblis@ns]% uname -a > FreeBSD ns 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313500: Fri Feb 10 16:39:21 > CST 2017 root@ns:/usr/obj/usr/src/sys/GENERIC amd64 > > [iblis@ns]% cat test.pl > use File::Temp qw(tempfile); > $tmpf = new File::Temp( UNLINK => 1 ); > > [iblis@ns]% perl test.pl > Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create temp file > /tmp/dI5uhUsijR: Bad file descriptor at test.pl line 2. > > > And part of truss's output: > > close(3) = 0 (0x0) > stat("/tmp/",{ mode=drwxrwxrwt ,inode=24317568,size=1024,blksize=32768 }) = 0 (0x0) > stat("/tmp/",{ mode=drwxrwxrwt ,inode=24317568,size=1024,blksize=32768 }) = 0 (0x0) > openat(AT_FDCWD,"/tmp/Nn0Epra5ff",O_RDWR|O_EXLOCK|O_NOFOLLOW|O_CREAT|O_EXCL,0600) ERR#9 'Bad file descriptor' > stat("/usr/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such file or directory' > stat("/usr/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such file or directory' > stat("/usr/local/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such file or directory' > stat("/usr/local/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such file or directory' > Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create temp file /tmp/Nn0Epra5ff: Bad file descriptor at test.pl line 2. > write(2,"Error in tempfile() using templa"...,135) = 135 (0x87) > > > -- > Iblis Lin > 林峻頤 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Iblis Lin 林峻頤 From owner-freebsd-current@freebsd.org Fri Feb 10 14:11:00 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01BA1CD815A for ; Fri, 10 Feb 2017 14:11:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DE45C7AA for ; Fri, 10 Feb 2017 14:10:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DAB07CD8159; Fri, 10 Feb 2017 14:10:59 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA578CD8158 for ; Fri, 10 Feb 2017 14:10:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 69C807A7 for ; Fri, 10 Feb 2017 14:10:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v1AEAfe5038258 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 10 Feb 2017 16:10:42 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v1AEAfe5038258 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v1AEAfhA038257; Fri, 10 Feb 2017 16:10:41 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 10 Feb 2017 16:10:41 +0200 From: Konstantin Belousov To: David Wolfskill Cc: Iblis Lin , current@freebsd.org Subject: Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor Message-ID: <20170210141041.GR2092@kib.kiev.ua> References: <20170210132954.GE1523@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170210132954.GE1523@albert.catwhisker.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 14:11:00 -0000 On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: > This was head @r313544; previous successful build/smoke test was > @r313467 (yesterday). > > Here's an excerpt from a typescript I made of some "poking around"; > subsequent to that, I was able to set the IP address, netmask, and > broadcast address on the NIC (wlano), then set the default route, and > once that was done, I was able to use the network: > > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:24:d6:7a:03:ce > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid lmdhw-net channel 1 (2412 MHz 11g ht/20) bssid 04:18:d6:22:22:1f > regdomain FCC country US authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 > protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi > -stbc -ldpc wme roaming MANUAL > groups: wlan > (12.0-C)[4] pgrep dhclient > (12.0-C)[5] dhclient wlan0 > dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT > dhclient: Leaving hostname set to > dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT > dhclient: reason was PREINIT; no action taken > dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 > can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor > exiting. > (12.0-C)[6] ls -lTio /var/db/dhclient.leases* > 883105 ---------- 1 root wheel - 4017 Jan 4 09:18:10 2017 /var/db/dhclient.leases.em0 > 883280 ---------- 1 root wheel - 856 Aug 11 04:52:54 2015 /var/db/dhclient.leases.lagg0 > 883344 ---------- 1 root wheel - 3333 Jan 20 21:19:10 2015 /var/db/dhclient.leases.vboxnet0 > 883108 ---------- 1 root wheel - 1993 Feb 10 04:30:13 2017 /var/db/dhclient.leases.wlan0 > 883079 ---------- 1 root wheel - 2013 Jan 19 11:52:07 2017 /var/db/dhclient.leases.wlan1 > > > Moving /var/db/dhclient.leases.wlan0 aside did not change the behavior. > > Stable/11 shows the iwn(4) device as: > g1-252(11.0-S)[4] pciconf -lv | grep -A 3 iwn > iwn0@pci0:3:0:0: class=0x028000 card=0x13218086 chip=0x42328086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'WiFi Link 5100' > class = network > g1-252(11.0-S)[5] > > File system for /var is a fairly vanilla UFS2+SU. I suppose I could have > tried ktrace (had I thought of it before switching back to the stable/11 > slice). > Please try this. diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c index 70cdcdc6f75..1f2cceaf7a6 100644 --- a/sys/kern/vfs_vnops.c +++ b/sys/kern/vfs_vnops.c @@ -351,8 +351,8 @@ vn_open_vnode(struct vnode *vp, int fmode, struct ucred *cred, while ((fmode & (O_EXLOCK | O_SHLOCK)) != 0) { KASSERT(fp != NULL, ("open with flock requires fp")); - if (fp->f_type != DTYPE_VNODE) { - error = EBADF; + if (fp->f_type != DTYPE_NONE && fp->f_type != DTYPE_VNODE) { + error = EOPNOTSUPP; break; } lock_flags = VOP_ISLOCKED(vp); diff --git a/sys/sys/file.h b/sys/sys/file.h index 353c92f365a..c51f26a41d2 100644 --- a/sys/sys/file.h +++ b/sys/sys/file.h @@ -53,6 +53,7 @@ struct vnode; #endif /* _KERNEL */ +#define DTYPE_NONE 0 /* not yet initialized */ #define DTYPE_VNODE 1 /* file */ #define DTYPE_SOCKET 2 /* communications endpoint */ #define DTYPE_PIPE 3 /* pipe */ From owner-freebsd-current@freebsd.org Fri Feb 10 14:46:17 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BB53CD8139 for ; Fri, 10 Feb 2017 14:46:17 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2414F1A2 for ; Fri, 10 Feb 2017 14:46:17 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 23664CD8137; Fri, 10 Feb 2017 14:46:17 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 230A5CD8136 for ; Fri, 10 Feb 2017 14:46:17 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 CC0FC1A1 for ; Fri, 10 Feb 2017 14:46:16 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id v1AEkEal078564; Fri, 10 Feb 2017 14:46:14 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v1AEkDJa078563; Fri, 10 Feb 2017 06:46:13 -0800 (PST) (envelope-from david) Date: Fri, 10 Feb 2017 06:46:13 -0800 From: David Wolfskill To: Konstantin Belousov Cc: Iblis Lin , current@freebsd.org Subject: Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor Message-ID: <20170210144613.GH1523@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Konstantin Belousov , Iblis Lin , current@freebsd.org References: <20170210132954.GE1523@albert.catwhisker.org> <20170210141041.GR2092@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bM6T5tSEJf/15wE6" Content-Disposition: inline In-Reply-To: <20170210141041.GR2092@kib.kiev.ua> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 14:46:17 -0000 --bM6T5tSEJf/15wE6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 10, 2017 at 04:10:41PM +0200, Konstantin Belousov wrote: > ... > Please try this. >=20 > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > index 70cdcdc6f75..1f2cceaf7a6 100644 > --- a/sys/kern/vfs_vnops.c > +++ b/sys/kern/vfs_vnops.c > @@ -351,8 +351,8 @@ vn_open_vnode(struct vnode *vp, int fmode, struct ucr= ed *cred, > =20 > while ((fmode & (O_EXLOCK | O_SHLOCK)) !=3D 0) { > KASSERT(fp !=3D NULL, ("open with flock requires fp")); > - if (fp->f_type !=3D DTYPE_VNODE) { > - error =3D EBADF; > + if (fp->f_type !=3D DTYPE_NONE && fp->f_type !=3D DTYPE_VNODE) { > + error =3D EOPNOTSUPP; > break; > } > lock_flags =3D VOP_ISLOCKED(vp); > diff --git a/sys/sys/file.h b/sys/sys/file.h > index 353c92f365a..c51f26a41d2 100644 > --- a/sys/sys/file.h > +++ b/sys/sys/file.h > @@ -53,6 +53,7 @@ struct vnode; > =20 > #endif /* _KERNEL */ > =20 > +#define DTYPE_NONE 0 /* not yet initialized */ > #define DTYPE_VNODE 1 /* file */ > #define DTYPE_SOCKET 2 /* communications endpoint */ > #define DTYPE_PIPE 3 /* pipe */ That seems to have done it -- thank you! :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying con-man??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key. --bM6T5tSEJf/15wE6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYndI1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XUgYH/iOqXjn3WrkxgTh6kOwbzig4 phBZdj4US2yNBn4N86pBOWH9XByN5EhllosnKOLg/EHmHMDJDWLzpEjua2kbBLDJ BJG1Sz4rAVaLWpcE54q/oL0c4ZBufXsDgUF+DbRRGQOF4rfzUHhu8isYtePqqhae u1/7YlAGG8+o9dWExeCLtoFK2ADclxF+HQvSegSfwXj2xuv8qF70PYr49mDtCjak 6k4ttJSkQIsVVczDfFoYHAZVqsH3nxoOQHve8Vgc5QlIy65KQGvMQbIL7BaXSxFr RF8qI0IoGq08C0TpuMK6rcITKEWtE7tg8hqz4hm2xFqL7KCMYpIwyGXA4gJVZQU= =8zAk -----END PGP SIGNATURE----- --bM6T5tSEJf/15wE6-- From owner-freebsd-current@freebsd.org Fri Feb 10 14:49:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BEB0CD8279 for ; Fri, 10 Feb 2017 14:49:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 37CE66BE for ; Fri, 10 Feb 2017 14:49:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id 343E2CD8274; Fri, 10 Feb 2017 14:49:33 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33E3ECD8271 for ; Fri, 10 Feb 2017 14:49:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 BB0E86BD for ; Fri, 10 Feb 2017 14:49:31 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.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 3420A1FE105; Fri, 10 Feb 2017 15:49:23 +0100 (CET) Subject: Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor To: Konstantin Belousov , David Wolfskill References: <20170210132954.GE1523@albert.catwhisker.org> <20170210141041.GR2092@kib.kiev.ua> Cc: Iblis Lin , current@freebsd.org From: Hans Petter Selasky Message-ID: <6382e902-82d6-f424-c835-3fcc1e797c73@selasky.org> Date: Fri, 10 Feb 2017 15:48:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170210141041.GR2092@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 14:49:33 -0000 On 02/10/17 15:10, Konstantin Belousov wrote: > On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: >> This was head @r313544; previous successful build/smoke test was >> @r313467 (yesterday). >> >> Here's an excerpt from a typescript I made of some "poking around"; >> subsequent to that, I was able to set the IP address, netmask, and >> broadcast address on the NIC (wlano), then set the default route, and >> once that was done, I was able to use the network: >> >> wlan0: flags=8843 metric 0 mtu 1500 >> ether 00:24:d6:7a:03:ce >> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 >> nd6 options=29 >> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng >> status: associated >> ssid lmdhw-net channel 1 (2412 MHz 11g ht/20) bssid 04:18:d6:22:22:1f >> regdomain FCC country US authmode WPA2/802.11i privacy ON >> deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 >> protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi >> -stbc -ldpc wme roaming MANUAL >> groups: wlan >> (12.0-C)[4] pgrep dhclient >> (12.0-C)[5] dhclient wlan0 >> dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT >> dhclient: Leaving hostname set to >> dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT >> dhclient: reason was PREINIT; no action taken >> dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 >> can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor >> exiting. >> (12.0-C)[6] ls -lTio /var/db/dhclient.leases* >> 883105 ---------- 1 root wheel - 4017 Jan 4 09:18:10 2017 /var/db/dhclient.leases.em0 >> 883280 ---------- 1 root wheel - 856 Aug 11 04:52:54 2015 /var/db/dhclient.leases.lagg0 >> 883344 ---------- 1 root wheel - 3333 Jan 20 21:19:10 2015 /var/db/dhclient.leases.vboxnet0 >> 883108 ---------- 1 root wheel - 1993 Feb 10 04:30:13 2017 /var/db/dhclient.leases.wlan0 >> 883079 ---------- 1 root wheel - 2013 Jan 19 11:52:07 2017 /var/db/dhclient.leases.wlan1 >> >> >> Moving /var/db/dhclient.leases.wlan0 aside did not change the behavior. >> >> Stable/11 shows the iwn(4) device as: >> g1-252(11.0-S)[4] pciconf -lv | grep -A 3 iwn >> iwn0@pci0:3:0:0: class=0x028000 card=0x13218086 chip=0x42328086 rev=0x00 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'WiFi Link 5100' >> class = network >> g1-252(11.0-S)[5] >> >> File system for /var is a fairly vanilla UFS2+SU. I suppose I could have >> tried ktrace (had I thought of it before switching back to the stable/11 >> slice). >> > Hi Konstantin, I hit the exact same issue with some rack servers and can confirm the patch below fixes this issue. --HPS > Please try this. > > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > index 70cdcdc6f75..1f2cceaf7a6 100644 > --- a/sys/kern/vfs_vnops.c > +++ b/sys/kern/vfs_vnops.c > @@ -351,8 +351,8 @@ vn_open_vnode(struct vnode *vp, int fmode, struct ucred *cred, > > while ((fmode & (O_EXLOCK | O_SHLOCK)) != 0) { > KASSERT(fp != NULL, ("open with flock requires fp")); > - if (fp->f_type != DTYPE_VNODE) { > - error = EBADF; > + if (fp->f_type != DTYPE_NONE && fp->f_type != DTYPE_VNODE) { > + error = EOPNOTSUPP; > break; > } > lock_flags = VOP_ISLOCKED(vp); > diff --git a/sys/sys/file.h b/sys/sys/file.h > index 353c92f365a..c51f26a41d2 100644 > --- a/sys/sys/file.h > +++ b/sys/sys/file.h > @@ -53,6 +53,7 @@ struct vnode; > > #endif /* _KERNEL */ > > +#define DTYPE_NONE 0 /* not yet initialized */ > #define DTYPE_VNODE 1 /* file */ > #define DTYPE_SOCKET 2 /* communications endpoint */ > #define DTYPE_PIPE 3 /* pipe */ > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Fri Feb 10 14:58:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC98CCD86A1 for ; Fri, 10 Feb 2017 14:58:31 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C7060E3C for ; Fri, 10 Feb 2017 14:58:31 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mailman.ysv.freebsd.org (Postfix) id C362ECD869E; Fri, 10 Feb 2017 14:58:31 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C30BECD869B for ; Fri, 10 Feb 2017 14:58:31 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: from mail.hs.ntnu.edu.tw (mail.hs.ntnu.edu.tw [140.131.149.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E2F3E39 for ; Fri, 10 Feb 2017 14:58:30 +0000 (UTC) (envelope-from iblis@hs.ntnu.edu.tw) Received: by mail.hs.ntnu.edu.tw (Postfix, from userid 800) id 01B9F1C647B; Fri, 10 Feb 2017 22:58:23 +0800 (CST) Received: from abeing (IP-215-9.cs.nctu.edu.tw [140.113.215.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: iblis@hs.ntnu.edu.tw) by mail.hs.ntnu.edu.tw (Postfix) with ESMTPSA id C61101C6450; Fri, 10 Feb 2017 22:58:23 +0800 (CST) Date: Fri, 10 Feb 2017 22:58:22 +0800 From: Iblis Lin To: Konstantin Belousov Cc: David Wolfskill , current@freebsd.org Subject: Re: dhclient fails: can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor Message-ID: <20170210145822.GA30133@abeing> References: <20170210132954.GE1523@albert.catwhisker.org> <20170210141041.GR2092@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20170210141041.GR2092@kib.kiev.ua> User-Agent: Mutt/1.7.1 (2016-10-04) X-Bogosity: Ham, tests=bogofilter, spamicity=0.500000, version=1.2.4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 14:58:32 -0000 On Fri, Feb 10, 2017 at 04:10:41PM +0200, Konstantin Belousov wrote: > On Fri, Feb 10, 2017 at 05:29:54AM -0800, David Wolfskill wrote: > > This was head @r313544; previous successful build/smoke test was > > @r313467 (yesterday). > > > > Here's an excerpt from a typescript I made of some "poking around"; > > subsequent to that, I was able to set the IP address, netmask, and > > broadcast address on the NIC (wlano), then set the default route, and > > once that was done, I was able to use the network: > > > > wlan0: flags=8843 metric 0 mtu 1500 > > ether 00:24:d6:7a:03:ce > > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > > nd6 options=29 > > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > > status: associated > > ssid lmdhw-net channel 1 (2412 MHz 11g ht/20) bssid 04:18:d6:22:22:1f > > regdomain FCC country US authmode WPA2/802.11i privacy ON > > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 > > protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi > > -stbc -ldpc wme roaming MANUAL > > groups: wlan > > (12.0-C)[4] pgrep dhclient > > (12.0-C)[5] dhclient wlan0 > > dhclient: /etc/dhclient-enter-hooks invoked with reason PREINIT > > dhclient: Leaving hostname set to > > dhclient: /etc/dhclient-exit-hooks invoked with reason PREINIT > > dhclient: reason was PREINIT; no action taken > > dhclient: Exiting /etc/dhclient-exit-hooks (PREINIT) with exit_status 0 > > can't open and lock /var/db/dhclient.leases.wlan0: Bad file descriptor > > exiting. > > (12.0-C)[6] ls -lTio /var/db/dhclient.leases* > > 883105 ---------- 1 root wheel - 4017 Jan 4 09:18:10 2017 /var/db/dhclient.leases.em0 > > 883280 ---------- 1 root wheel - 856 Aug 11 04:52:54 2015 /var/db/dhclient.leases.lagg0 > > 883344 ---------- 1 root wheel - 3333 Jan 20 21:19:10 2015 /var/db/dhclient.leases.vboxnet0 > > 883108 ---------- 1 root wheel - 1993 Feb 10 04:30:13 2017 /var/db/dhclient.leases.wlan0 > > 883079 ---------- 1 root wheel - 2013 Jan 19 11:52:07 2017 /var/db/dhclient.leases.wlan1 > > > > > > Moving /var/db/dhclient.leases.wlan0 aside did not change the behavior. > > > > Stable/11 shows the iwn(4) device as: > > g1-252(11.0-S)[4] pciconf -lv | grep -A 3 iwn > > iwn0@pci0:3:0:0: class=0x028000 card=0x13218086 chip=0x42328086 rev=0x00 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'WiFi Link 5100' > > class = network > > g1-252(11.0-S)[5] > > > > File system for /var is a fairly vanilla UFS2+SU. I suppose I could have > > tried ktrace (had I thought of it before switching back to the stable/11 > > slice). > > > > Please try this. > > diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c > index 70cdcdc6f75..1f2cceaf7a6 100644 > --- a/sys/kern/vfs_vnops.c > +++ b/sys/kern/vfs_vnops.c > @@ -351,8 +351,8 @@ vn_open_vnode(struct vnode *vp, int fmode, struct ucred *cred, > > while ((fmode & (O_EXLOCK | O_SHLOCK)) != 0) { > KASSERT(fp != NULL, ("open with flock requires fp")); > - if (fp->f_type != DTYPE_VNODE) { > - error = EBADF; > + if (fp->f_type != DTYPE_NONE && fp->f_type != DTYPE_VNODE) { > + error = EOPNOTSUPP; > break; > } > lock_flags = VOP_ISLOCKED(vp); > diff --git a/sys/sys/file.h b/sys/sys/file.h > index 353c92f365a..c51f26a41d2 100644 > --- a/sys/sys/file.h > +++ b/sys/sys/file.h > @@ -53,6 +53,7 @@ struct vnode; > > #endif /* _KERNEL */ > > +#define DTYPE_NONE 0 /* not yet initialized */ > #define DTYPE_VNODE 1 /* file */ > #define DTYPE_SOCKET 2 /* communications endpoint */ > #define DTYPE_PIPE 3 /* pipe */ > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" It works fine for me! :) -- Iblis Lin 林峻頤 From owner-freebsd-current@freebsd.org Fri Feb 10 18:39:03 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92B09CD96E3 for ; Fri, 10 Feb 2017 18:39:03 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (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 60407F1F; Fri, 10 Feb 2017 18:39:03 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pg0-x22b.google.com with SMTP id 14so12576242pgg.1; Fri, 10 Feb 2017 10:39:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=I2eUFP1P9OnOyDspIfmMmCfwEviRrq9lkrb2AEzzECw=; b=rVnRKrq0Y2uqUhZAness/fJv3jXG+7ARRc99g7HKfjNSfPZAy64xPKAVV9iOJpsHNw FLH1WaP6e58+Eo9+LKxkKaGwwabBhFoxqapr3jRo+Quptn5QRUfXaMSW9piRJwUO2Yrc b3ZviUO4VtAJpfSXsUGiPQ5Gc8gyGt5pFhoQrD/Z4uoFlafEePlt5hzc7w7629UyAr4Q ey995Vv/0eASDrrJ44I3J00Pvm+u+7aQKQb9k2xL5oEaGlCHALv+L5GjxKTR/zfmdv2T zS4sxTWj0YkXhFx2BLk9M6mVj3cTni9DXXrN/ECvB+kPCzbMBRqkUt2KJUxNO7kvhA9y 4f8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=I2eUFP1P9OnOyDspIfmMmCfwEviRrq9lkrb2AEzzECw=; b=G1LPOcj9wlqipX2siLHggtqeRj1Z6osAkKpRPGBaP++BJz/J00DSkphLv8HUgUEDCC HWo5kSkT3d/9PCSeqD5bEJjrJttm6mToJ4naV1jwIXn0N/IlFRzlFMuKQ/6LlImVjfBL TRFqUO/zHc3kttSP5q/aaRRN+iNqc9VqtrogFe/pBpy8KWbOE490O4C03I3kypFbA0uY Ke1l5jnLzW3F2PMuCZ7LHoOaHR4qe6c9HEAPkgKsMpJx8+Ib4qf0+U6FriccogxmJXNU 965IBYl1T/lOoLoxeJHoqOVa8M84z1tL9qNEu73oWgnhDnegwdFpoZGzwsJy+Yk6ucH6 1GuQ== X-Gm-Message-State: AMke39lp9NpmD1qdv6p5Ks326pkwbW38Lk+JZi8mu8mbv/azW2eNVLnB/0u99elKsotJIA== X-Received: by 10.84.232.67 with SMTP id f3mr13175125pln.55.1486751942898; Fri, 10 Feb 2017 10:39:02 -0800 (PST) Received: from pinklady.local (c-73-19-52-228.hsd1.wa.comcast.net. [73.19.52.228]) by smtp.gmail.com with ESMTPSA id l71sm7069986pga.13.2017.02.10.10.39.02 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 10 Feb 2017 10:39:02 -0800 (PST) Subject: Re: r313495 make perl File::Temp broken Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/signed; boundary="Apple-Mail=_75ED7A29-AA45-4911-BA99-637593044A95"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail From: "Ngie Cooper (yaneurabeya)" In-Reply-To: <20170210135529.GC70284@abeing> Date: Fri, 10 Feb 2017 10:39:01 -0800 Cc: Konstantin Belousov , FreeBSD CURRENT Message-Id: <599B2B62-1D6F-493B-A64B-DAD4B337E1B2@gmail.com> References: <20170210130952.GA70284@abeing> <20170210135529.GC70284@abeing> To: Iblis Lin X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 18:39:03 -0000 --Apple-Mail=_75ED7A29-AA45-4911-BA99-637593044A95 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Feb 10, 2017, at 05:55, Iblis Lin wrote: >=20 > I just found i miss-typed the revision number in subject. > It's r313495. >=20 > = (https://svnweb.freebsd.org/base/head/sys/kern/vfs_vnops.c?r1=3D313495&r2=3D= 313494&pathrev=3D313495) >=20 > On Fri, Feb 10, 2017 at 09:09:52PM +0800, Iblis Lin wrote: >> Hi, >>=20 >> as not a perl programmer myself. I have no idea what is going on. >> I found this issue while compiling math/openblas. >>=20 >> [iblis@ns]% uname -a >> FreeBSD ns 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313500: Fri Feb 10 = 16:39:21 >> CST 2017 root@ns:/usr/obj/usr/src/sys/GENERIC amd64 >>=20 >> [iblis@ns]% cat test.pl >> use File::Temp qw(tempfile); >> $tmpf =3D new File::Temp( UNLINK =3D> 1 ); >>=20 >> [iblis@ns]% perl test.pl >> Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create = temp file >> /tmp/dI5uhUsijR: Bad file descriptor at test.pl line 2. >>=20 >>=20 >> And part of truss's output: >>=20 >> close(3) =3D 0 (0x0) >> stat("/tmp/",{ mode=3Ddrwxrwxrwt = ,inode=3D24317568,size=3D1024,blksize=3D32768 }) =3D 0 (0x0) >> stat("/tmp/",{ mode=3Ddrwxrwxrwt = ,inode=3D24317568,size=3D1024,blksize=3D32768 }) =3D 0 (0x0) >> = openat(AT_FDCWD,"/tmp/Nn0Epra5ff",O_RDWR|O_EXLOCK|O_NOFOLLOW|O_CREAT|O_EXC= L,0600) ERR#9 'Bad file descriptor' >> stat("/usr/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such file = or directory' >> stat("/usr/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such file = or directory' >> stat("/usr/local/share/nls/C/libc.cat",0x7fffffffdcf8) ERR#2 'No such = file or directory' >> stat("/usr/local/share/nls/libc/C",0x7fffffffdcf8) ERR#2 'No such = file or directory' >> Error in tempfile() using template /tmp/XXXXXXXXXX: Could not create = temp file /tmp/Nn0Epra5ff: Bad file descriptor at test.pl line 2. >> write(2,"Error in tempfile() using templa"...,135) =3D 135 (0x87) Hi, kib@ has a patch out for another related issue that was reported = with dhclient =E2=80=94 please give his patch a shot: = https://lists.freebsd.org/pipermail/freebsd-current/2017-February/064780.h= tml . Cheers, -Ngie --Apple-Mail=_75ED7A29-AA45-4911-BA99-637593044A95 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJYngjFAAoJEPWDqSZpMIYVnvkP/ikqbpoKijqlGymNc5R/wg/A q01QX02I4UvPA3QZ8KkVAy7Bo04Ma9ArFcnoHS+6+NQiJO6rRNpDGeEgC6ydgc1d piqiy0MBpQeklc8HUCHZUyUnZrpRIWPMvsZ6AjhzzSaFVOwnUJjqh+Nmll6hEdzy 5oG4bOXxKkAmAtfUiRzgkvO84QDzfT4uuW0cKsU36ZuPwXIyf+1WlcpvWULhFQQ3 2ceqGwHFEnPPeogFdG/ak+nIR2gthV1MtLu8e5qolsSuTUG16SLWJ3CRsacOyHkf tO7ljt/F+RFRyyqs5TeMR+kjVtkr0UhSyrsbiv5x23tEMvjAU/ZQcUX4amSGpAlx BC4AWD3ki8kZ+q/bZJujXHd/1vpISMBTexamSJzYF3CwopUgGGbA/VzbhKRvZTze 8EuqueVn7O4CHFFTpJidG3MwM4+S9HatkN1TrZXjfTuOZNJgw6EsqlgvYMdgffRR NKSO0f/wXKKOiw37avLzHVvcT1yW3HTVr0LwiJWeskjgnRVNKtI3uXlmw0ZQBXta Ps4PrVCDaqoyupGP2M5I8ACZSxCeVVPqsF8+0XZBnqFR0cuwmfsmgolxseiFCwGs 8wDX8TRh8J2UusrJKRFz4w29dKsK2m+vi5+JLGwxLTIEr8C+0hJBqhF790T4vHlD rY35hYqo1kT+eVqQHJDV =cCgL -----END PGP SIGNATURE----- --Apple-Mail=_75ED7A29-AA45-4911-BA99-637593044A95-- From owner-freebsd-current@freebsd.org Fri Feb 10 19:36:52 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E541CCD9B41 for ; Fri, 10 Feb 2017 19:36:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 BFC93170D for ; Fri, 10 Feb 2017 19:36:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1ccGzz-000Dcb-TL; Fri, 10 Feb 2017 11:36:52 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id v1AJapxx052364; Fri, 10 Feb 2017 11:36:51 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Fri, 10 Feb 2017 11:36:50 -0800 From: Oleksandr Tymoshenko To: Toomas Soome Cc: Karl Denninger , freebsd-current@freebsd.org Subject: Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109 Message-ID: <20170210193650.GA52341@bluezbox.com> References: <517ab0d5-412a-35dd-7d0d-d8297af43b46@denninger.net> <4a6f872b-cee1-57e5-7a72-a1d445f9926f@denninger.net> <5128b9a9-1186-8c6c-6227-e5e8a087cf89@denninger.net> <0B4B40AA-E654-4A71-92B0-D8E6CD234B63@me.com> <20170209213916.GA40599@bluezbox.com> <20170209221021.GA40870@bluezbox.com> <64E64B7F-E1BE-4CC6-ACAB-E5D7FEE408C8@me.com> <0E030158-CF2C-4A95-93EB-E06061689A6E@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0E030158-CF2C-4A95-93EB-E06061689A6E@me.com> X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Toomas Soome (tsoome@me.com) wrote: > > >> > >> From reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks like > >> names are in the form of typeN:M, where type is interface type, > >> N is disk id and M is partition id. So 3 disks in my setup > >> may be mmc0, mmc0:1, mmc0:2. > >> > >> -- > >> gonzo > > > > Okay, so in case of arm or MEDIA_FILEPATH_DP we need to keep the initial disk handle till there is an disk switch, and use it as first argument for registering the disk. So the name in last node is probably the same format and we can identify the disk this way. Worth to check in any case:) > > > > > Based on current knowledge, I did put together the first sketch of the fix: > > https://reviews.freebsd.org/D9520 > > However, it needs to be tested on arm, so I do ask help there:) [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: me.com] -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2017 19:36:53 -0000 Toomas Soome (tsoome@me.com) wrote: > > >> > >> From reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks like > >> names are in the form of typeN:M, where type is interface type, > >> N is disk id and M is partition id. So 3 disks in my setup > >> may be mmc0, mmc0:1, mmc0:2. > >> > >> -- > >> gonzo > > > > Okay, so in case of arm or MEDIA_FILEPATH_DP we need to keep the initial disk handle till there is an disk switch, and use it as first argument for registering the disk. So the name in last node is probably the same format and we can identify the disk this way. Worth to check in any case:) > > > > > Based on current knowledge, I did put together the first sketch of the fix: > > https://reviews.freebsd.org/D9520 > > However, it needs to be tested on arm, so I do ask help there:) Thanks Toomas, rpi3 boots with this patch applied and device structure is correct: OK lsdev disk devices: disk0: 15564801 X 512 blocks (removable) disk0s1: DOS/Windows disk0s2: FreeBSD disk0s2a: FreeBSD UFS net devices: net0: -- gonzo From owner-freebsd-current@freebsd.org Sat Feb 11 02:59:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8A67CDA973 for ; Sat, 11 Feb 2017 02:59:26 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [50.7.9.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fbsd10.amd64", Issuer "fbsd10.amd64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 84DED133C for ; Sat, 11 Feb 2017 02:59:25 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from www.i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.15.2/8.15.2) with ESMTP id v1B4Xnum050073 for ; Sat, 11 Feb 2017 02:34:11 -0200 (BRST) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: freebsd-current@freebsd.org Subject: USB problem with keyboard Date: Sat, 11 Feb 2017 01:33:49 -0300 Message-Id: <20170211034900.M29912@i805.com.br> X-Mailer: OpenWebMail 3.00_beta4 20140806 79bb7cc X-OriginatingIP: 186.221.219.53 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on server.i805.com.br X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2017 02:59:26 -0000 Hi All, I changed my old multimedia keyboard (Genius) to a new one small and simple keyboard. I thought the problem was the dirty on the keyboard so i clened but it's still not working well ( it's not showing all keys pressed or sometimes repeat the last key pressed). This problem was started when I updated my box, but I had other old problem that I ignored for a while My usb mouse and my no-break APC random disconnect and reconnect sometimes per hours dmesg.yesterday:ugen0.2: at usbus0 dmesg.yesterday:ugen0.2: at usbus0 (disconnected) root@valfenda:/var/log # uname -a FreeBSD valfenda 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r313095: Fri Feb 3 17:48:08 BRST 2017 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA amd64 root@valfenda:/var/log # usbconfig list ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAV (0mA) ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAV (0mA) ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAE (0mA) ugen6.1: at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAV (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps pwr=ON (100mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pr=SAVE (100mA) ugen2.3: at usbus2, cfg=0 md=HOST spd=HIGH (40Mbps) pwr=ON (100mA) ugen2.4: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps)pwr=SAVE (100mA) ugen2.5: at ubus2, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA) ugen2.6: at usbus2, cfg=0 md=HOST spd=LOW (1.5Mbps) pw=ON (98mA) ugen2.7: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbs) pwr=ON (250mA) My mottttttttttttttttthboard is: ASUS M5A78L CPU: AMD FX(tm)-8300 Eight-Core Processor (3465.07-MHz K8-class CPU) Ps. I typed only once a letter t and it has been repeated sometimes --- /************************************************* **Nilton José Rizzo UFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **************************************************/ From owner-freebsd-current@freebsd.org Sat Feb 11 08:19:34 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 863FDCDBF27 for ; Sat, 11 Feb 2017 08:19:34 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5FD1AFEC for ; Sat, 11 Feb 2017 08:19:34 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-pg0-x229.google.com with SMTP id 194so17429932pgd.2 for ; Sat, 11 Feb 2017 00:19:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=tp+v0AQyLD/w3FV0oGBBGbj4xM2Hjpqw/LAWVfTPG9U=; b=sbdYmS/DN0yAr9yazY+1RIWntVPr2a1vzvFpslm5qZsGnSxIrHZ9J7iBgFz/qxGloZ nkLGvQygrhYW1IqjQxuf5gzrOIvU7YEHci/+6aATSiZSxdo+fMohM+QJkFSJfUarDWo9 HkYsW3JdQWUx03VNxGR93uFQv34tBqON9+Vnx0MDUavY0A1lZdhiJqorljDiRnlewMpQ +WvMXfwlYVONNevr7p1ue0dXLhnGk2dYIKvHEgwTjHTJEqBleIrXORcQUGiuvBpNX+w8 O3hMfc+KSVdXeoRSbX3bkiPQKOuA1rt796UBfPD/a9WX5TpPkd8DHatWM5EUHxFSa2ne TOoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=tp+v0AQyLD/w3FV0oGBBGbj4xM2Hjpqw/LAWVfTPG9U=; b=BIjuuJWtU4iQRBetmsL6YFE88ytpHLNcZjsmEEkvO617gc9zYa8F8siykPofcuTZZR 2FXLYx9hhOKbxIu7ai6e79TbHroEcJf89dLvF/81eclG6PJkCYWn6+NvUUtJkbdwJmwE 7xHFoRAsy1G+RWwjikr3Eozrb4+UyDFlKApWHueHbGQLOzupoY8AvpJe78ikuXZ5k6Ye ajRi6y3gXx6FZX29x1OYzvXOZN7Iad5s9xZ8nyrxADxDz4omp3GhSzeRuQdeempbTUOF 7QTKKDzuP/aA2AYr4qMEsVa1mP4yUfIjBEjSD3ArkdXgZ4VFkoQo1/msbRS35D3ZXSSa 3RFw== X-Gm-Message-State: AMke39m7R1BR3V3BfDlcaUmVODuftNOPuY9K8G9pVGrSBq5zyTZsbYVgCSGXylacKYhArA== X-Received: by 10.99.42.78 with SMTP id q75mr15459644pgq.144.1486801173953; Sat, 11 Feb 2017 00:19:33 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id p17sm3252084pfi.97.2017.02.11.00.19.30 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Sat, 11 Feb 2017 00:19:32 -0800 (PST) Date: Sat, 11 Feb 2017 09:19:24 +0100 From: Mateusz Guzik To: Ben Woods Cc: FreeBSD Current Subject: Re: Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837) Message-ID: <20170211081924.GA3868@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Ben Woods , FreeBSD Current References: <20160922130141.GA9643@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2017 08:19:34 -0000 On Thu, Oct 27, 2016 at 09:09:16PM +0800, Ben Woods wrote: > On 24 September 2016 at 18:13, Ben Woods wrote: > > > On 22 September 2016 at 21:01, Mateusz Guzik wrote: > > > >> On Thu, Sep 22, 2016 at 08:48:29PM +0800, Ben Woods wrote: > >> > #13 0xffffffff80b4d91c in turnstile_broadcast (ts=0x0, queue=1) at > >> > /usr/src/sys/kern/subr_turnstile.c:837 > >> > #14 0xffffffff80ae5e1f in __rw_wunlock_hard (c=0xfffff803f886d960, > >> > tid=, file=, line= >> > optimized out>) > >> > at /usr/src/sys/kern/kern_rwlock.c:1027 > >> > >> can you please: > >> f 14 > >> x/xg c > >> > >> > >> -- > >> Mateusz Guzik > >> > > > > Thanks for the help Mateusz. > > > > (kgdb) f 14 > > #14 0xffffffff80ae5e1f in __rw_wunlock_hard (c=0xfffff803f886d960, > > tid=, file=, line= > optimized out>) > > at /usr/src/sys/kern/kern_rwlock.c:1027 > > 1027 turnstile_broadcast(ts, queue); > > Current language: auto; currently minimal > > (kgdb) x/xg c > > 0xfffff803f886d960: 0xfffff8032893aa00 > > > > Regards, > > Ben > > > > Hi everyone, > > Just a heads up that after updating my FreeBSD 12-current machine to > r307773 I am still getting this kernel panic. > > Note that I have compiled the kernel with VIMAGE support if that makes any > difference. > > Mateusz: any further ideas on what it could be? > > Any help is appreciated :) > long time no see Is the problem still happening? There were quite a few locking changes recently and they could have interferred with the bug, so to speak. Can you move your kernel to r313260 (which predates locking changes) and make sure it is still there? The thread value shown in your first message corresponds to the lock value seen in __rw_wunlock_hard. But we should not get there if that's the case so there is something fishy going on. If the bug is still there at r313260, I'll provide you with a debug patch which will tell us what value was found and prevented a clean unlock. Then we will see if perhaps there are transient flags set or something corrupts the value somehow. -- Mateusz Guzik From owner-freebsd-current@freebsd.org Sat Feb 11 13:24:10 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8745BCDB064 for ; Sat, 11 Feb 2017 13:24:10 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 4A44E7BC for ; Sat, 11 Feb 2017 13:24:10 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.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 0BF2F1FE104; Sat, 11 Feb 2017 14:23:59 +0100 (CET) Subject: Re: USB problem with keyboard To: Nilton Jose Rizzo , freebsd-current@freebsd.org References: <20170211034900.M29912@i805.com.br> From: Hans Petter Selasky Message-ID: Date: Sat, 11 Feb 2017 14:23:26 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170211034900.M29912@i805.com.br> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2017 13:24:10 -0000 Hi, You might want to check the PCI ID's with Linux's EHCI/OHCI/UHCI and see if there are particular quirks missing for your ATI USB chipset. --HPS From owner-freebsd-current@freebsd.org Sat Feb 11 14:52:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C1CFCDB1DF for ; Sat, 11 Feb 2017 14:52:14 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [50.7.9.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fbsd10.amd64", Issuer "fbsd10.amd64" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B825211 for ; Sat, 11 Feb 2017 14:52:14 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from www.i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.15.2/8.15.2) with ESMTP id v1BGpnNR057191; Sat, 11 Feb 2017 14:52:10 -0200 (BRST) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: Hans Petter Selasky , freebsd-current@freebsd.org Subject: Re: USB problem with keyboard Date: Sat, 11 Feb 2017 13:51:49 -0300 Message-Id: <20170211165126.M20559@i805.com.br> In-Reply-To: References: <20170211034900.M29912@i805.com.br> X-Mailer: OpenWebMail 3.00_beta4 20140806 79bb7cc X-OriginatingIP: 186.221.219.53 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on server.i805.com.br X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2017 14:52:14 -0000 Em Sat, 11 Feb 2017 14:23:26 +0100, Hans Petter Selasky escreveu > Hi, > > You might want to check the PCI ID's with Linux's EHCI/OHCI/UHCI and > see if there are particular quirks missing for your ATI USB chipset. hummmm I have in this machine dual boot with Windowns 10, I'm instal to test my keyoard, and it's work fine. I'll try with Linux. I > > --HPS > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --- /************************************************* **Nilton José Rizzo UFRRJ **http://www.rizzo.eng.br http://www.ufrrj.br **http://lattes.cnpq.br/0079460703536198 **************************************************/