From owner-freebsd-ppc@freebsd.org Mon Oct 22 21:35:41 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCD32FD7D1A; Mon, 22 Oct 2018 21:35:40 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4174B7579C; Mon, 22 Oct 2018 21:35:40 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id BDA6710AFCD; Mon, 22 Oct 2018 17:35:38 -0400 (EDT) Subject: Re: Reasons to still not build buildworld buildkernel via system-clang --John Baldwin notes one I was unaware of To: Mark Millard , FreeBSD Toolchain , Sean Fertile References: <23400842-E5CB-4251-BFE5-78D524A64012@yahoo.com> Cc: Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML From: John Baldwin Message-ID: Date: Mon, 22 Oct 2018 14:35:37 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 22 Oct 2018 17:35:39 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2018 21:35:41 -0000 On 10/19/18 7:23 AM, Mark Millard wrote: > [I'm adding toolchain and John B. to the TO: list. John B. > may want to reply to Sean F. I'm also adding a > /lib/libgcc_s.so related item to the list of 3 known > issues.] > >> On 2018-Oct-19, at 6:21 AM, Sean Fertile wrote: >> >> Clang isn't getting the tls model wrong, it actually generates pic code by default as if -fpic were specified. I think the original intent behind switching >> to pic by default was due to incorrectly thinking gcc was pic by default (I'm not sure if this was meant as only gcc on BSD or gcc on powerpc64 in general), >> as well as working around some problems that clangs non-pic codegen has/had for the ELF V1 abi. There are some patches on phabricator for switching >> the default back to non-pic codegen, but they leave the pic default for BSD: https://reviews.llvm.org/D53384 and https://reviews.llvm.org/D53383 >> >> According to what you and John are saying the pic default is incorrect for BSD as well. If thats the case please either comment on the reviews to let Stefan know, >> or let me know here and we can update the patches accordingly. No, what I am saying is that in GCC, the decision for dynamic TLS model vs static TLS model is based on whether or not -fPIC is explicitly given on the command line. For MIPS at least (where I am familiar with this), both GCC and clang default to implicit PIC. However, GCC uses static TLS models (initial-exec, etc.) when -fPIC isn't given on the command line even if PIC is still implicitly enabled. It only uses the dynamic TLS models (intended for use in shared libraries) if -fPIC is explicitly passed on the command line. However, clang implements implicit PIC by passing the equivalent of -fPIC to the llvm backend, so on MIPS at least, the result is that llvm _always_ uses the dynamic TLS models including for static libraries and binaries where this is wrong. I have some patches from one of the LLVM MIPS folks that kind of hackishly fix this, but by adding a new flag only for MIPS. I wanted to adjust their patches to be more generic so that there's a new '-mshared-library' or some such passed from clang to llvm and have clang only set that to true if -fPIC is explicitly given on the command line to match GCC's behavior. So to be clear, this isn't saying that the implicit PIC setting is wrong. It is saying that the llvm backend incorrectly interprets the clang front-end's implicit PIC setting as being an explicit PIC setting for the purposes of choosing the TLS model to use. -- John Baldwin From owner-freebsd-ppc@freebsd.org Tue Oct 23 21:15:09 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05B00FFD1B0 for ; Tue, 23 Oct 2018 21:15:09 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-22.consmr.mail.ne1.yahoo.com (sonic304-22.consmr.mail.ne1.yahoo.com [66.163.191.148]) (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 9262170BBD for ; Tue, 23 Oct 2018 21:15:08 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: YCcHGaoVM1lXw9D9t78UlsECVl173YrkE0iHZihgZsKe9HPii4qsJimayYMupAB pPHnD6FLxiWgCRlECgLFk4vXNzd8.JGozzRXKoYlCIWIBixlPEb0ccAELX.cEGPMnoxVC_PZ8qiG d0xRKz4pt9fMfsVPkLfOQvjIvb_L0BZTTsMj3eCgRMk3E5Sfehwe1ZuCh1iY.tvUBZA7260V0ubB RXmuTI9Qoc.0BYMEZnEoQYS2bwVOQD4iiCRopVg40G.YG_CuqqVEsyCVAnjSzvs2rbks4wOPBh_G _w9g6btZmxDE0gXWUAv55mXsKHPBBGxudSsao.pa.D4SclWK7S2YiLjXHH.d2w3J8KhXORRWw4bX fr1RdGbDsruW32ZxUizI1K.tAGz4NzsQUcbVOPP8uGc43fqaXQaSeuiZT3iaj2c3wcxD80g5bXYP OvceoOnUMpLXg8ZqiBWyw3gW895WvihBNGpMMisDfQTdsGDZkR2K3POm21VMsN2szqRCviA1ZvfM HnfoS3B._Yz2WjxbtIhFcASKD4HJT3QFP.Qy.Qxzu4FPL_1TOooDtl2xioRODgjR9i_4JXhdgw8v NaKwoDfcNxcgslc1mJgIeUnaXzlxRnNI22WSAqryzuNKlb6KA2kDoMl13WveThs.zBX8HP3GMQh1 RSj4Jm08leN8TV4MRvh3r8VHisYGLltQvxlwJJFCbQRmgthNOoWRRlkPxYb4gNTOXifkpjFWzxwN GKIT.VzFxycd2k9E93V7vTgMcYF77.uwXtNcuBRpqA2KTU96lFszckhsmzCiJWzdPUlC_xemnHuT gIK6Oc93Lv7dHBw_Ek5bWB2nJQXQowwbCZ7cCQX8dlq_3i7rGOK4au50Wbym4t4RLQG1yb1BPUfm RFzazHnZ_ToLVHXmdby3ukXydP0reYAfKOoLnvgimVNvHeMn6DXgCZenz5FMe5OZ2Lfp0bdl1zkY Ywxc3ZProbTyVzDsSDMSDr6rSAADYv6K0hTwwCKaWJBdEE4nkChaSsRAvBOdoNHoN_PT1szysV30 DcFNmsjTZKWoJ2.VLgEQ.E7bRzUDZ4yOm.g3Q4JVFLg1ezQhsHOuXee13KHE1Djetu6yr3NjCD9S fJ41YEok- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ne1.yahoo.com with HTTP; Tue, 23 Oct 2018 21:15:00 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp413.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 0aa92ced50a486c022d21f2e083dfa26; Tue, 23 Oct 2018 21:14:57 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Reasons to still not build buildworld buildkernel via system-clang --John Baldwin notes one I was unaware of From: Mark Millard In-Reply-To: Date: Tue, 23 Oct 2018 14:14:56 -0700 Cc: FreeBSD Toolchain , Justin Hibbits , Nathan Whitehorn , FreeBSD PowerPC ML , John Baldwin Content-Transfer-Encoding: quoted-printable Message-Id: References: <23400842-E5CB-4251-BFE5-78D524A64012@yahoo.com> To: Sean Fertile X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2018 21:15:09 -0000 [Mostly just giving some powerpc64 detail, at least when base/binutils is used.] On 2018-Oct-22, at 2:35 PM, John Baldwin wrote: > On 10/19/18 7:23 AM, Mark Millard wrote: >> [I'm adding toolchain and John B. to the TO: list. John B. >> may want to reply to Sean F. I'm also adding a >> /lib/libgcc_s.so related item to the list of 3 known >> issues.] >>=20 >>> On 2018-Oct-19, at 6:21 AM, Sean Fertile = wrote: >>>=20 >>> Clang isn't getting the tls model wrong, it actually generates pic = code by default as if -fpic were specified. I think the original intent = behind switching=20 >>> to pic by default was due to incorrectly thinking gcc was pic by = default (I'm not sure if this was meant as only gcc on BSD or gcc on = powerpc64 in general),=20 >>> as well as working around some problems that clangs non-pic codegen = has/had for the ELF V1 abi. There are some patches on phabricator for = switching >>> the default back to non-pic codegen, but they leave the pic default = for BSD: https://reviews.llvm.org/D53384 and = https://reviews.llvm.org/D53383 >>>=20 >>> According to what you and John are saying the pic default is = incorrect for BSD as well. If thats the case please either comment on = the reviews to let Stefan know, >>> or let me know here and we can update the patches accordingly. >=20 > No, what I am saying is that in GCC, the decision for dynamic TLS = model > vs static TLS model is based on whether or not -fPIC is explicitly > given on the command line. For MIPS at least (where I am familiar = with > this), both GCC and clang default to implicit PIC. FYI: John discovered that mips64/powerpc64 is the context for PIC being the default for clang (I'm ignoring x86_64, Windows, MachO and MacOSX in my comments): bool Generic_GCC::isPICDefault() const { switch (getArch()) { case llvm::Triple::x86_64: return getTriple().isOSWindows(); case llvm::Triple::ppc64: case llvm::Triple::ppc64le: return !getTriple().isOSBinFormatMachO() && !getTriple().isMacOSX(); case llvm::Triple::mips64: case llvm::Triple::mips64el: return true; default: return false; } } > However, GCC uses > static TLS models (initial-exec, etc.) when -fPIC isn't given on the > command line even if PIC is still implicitly enabled. It only uses = the > dynamic TLS models (intended for use in shared libraries) if -fPIC is > explicitly passed on the command line. > However, clang implements implicit PIC by passing the equivalent of > -fPIC to the llvm backend, so on MIPS at least, the result is that = llvm > _always_ uses the dynamic TLS models including for static libraries = and > binaries where this is wrong. I have some patches from one of the = LLVM > MIPS folks that kind of hackishly fix this, but by adding a new flag > only for MIPS. I wanted to adjust their patches to be more generic so > that there's a new '-mshared-library' or some such passed from clang > to llvm and have clang only set that to true if -fPIC is explicitly > given on the command line to match GCC's behavior. >=20 > So to be clear, this isn't saying that the implicit PIC setting is > wrong. It is saying that the llvm backend incorrectly interprets > the clang front-end's implicit PIC setting as being an explicit PIC > setting for the purposes of choosing the TLS model to use. For powerpc64 things are somewhat different via some link-time optimizations when base/binutils is in use (lld not being ready for use for powerpc64 as I understand). (I've no clue what would happen with lld.) cc -g -O2 -c will produce .o files with the __tls_get_addr calls, for example (source shown later): # objdump -r tlsy.o | grep __tls_get_addr 0000000000000024 R_PPC64_REL24 __tls_get_addr 0000000000000038 R_PPC64_REL24 __tls_get_addr # objdump -r tls_main.o | grep __tls_get_addr 0000000000000020 R_PPC64_REL24 __tls_get_addr 0000000000000034 R_PPC64_REL24 __tls_get_addr 000000000000008c R_PPC64_REL24 __tls_get_addr 00000000000000a0 R_PPC64_REL24 __tls_get_addr This is as John indicated. But the likes of: # cc -g -O0 tls_main.o tlsy.o tls.o ends up with a.out having r13 use and no such subroutine calls to __tls_get_addr in x, y, or main. There are some nop instructions from where substitutions were made. It appears that mips64 does not have such a late-optimization in John's context: the __tls_get_addr use survives into a.out as I understand. The source for the example used above was: # more tls.c int __thread i =3D 3; int __thread j =3D 2; # more tlsy.c extern int __thread i; extern int __thread j; int y() { return i+j; } # more tls_main.c extern int __thread i; extern int __thread j; extern int y(); int x() { return i+j; } int main () { return x()-y(); } (So main got some inlining of x() in order for the tls_main.o to show 4 R_PPC64_REL24 uses for __tls_get_addr .) I have no clue if the late-optimization for powerpc64 covers all the cases where direct use of some static TLS model would be appropriate. I just know that, at least in some types of contexts, some calls to __tls_get_addr are eliminated at link time when base/binutils is in use. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Wed Oct 24 13:01:04 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 037E51079095 for ; Wed, 24 Oct 2018 13:01:04 +0000 (UTC) (envelope-from donotreplytothismail@gmx.com) Received: from SUNSTUDIO (li1865-135.members.linode.com [172.105.211.135]) (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 E886E85B5D for ; Wed, 24 Oct 2018 13:01:02 +0000 (UTC) (envelope-from donotreplytothismail@gmx.com) Message-ID: From: "Mark Chen" (Mark Chen) To: freebsd-ppc@freebsd.org Subject: RE: Satellite Broadband Internet Modem IP freebsd-ppc@freebsd.org Date: 24 Oct 2018 20:05:58 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 13:01:04 -0000 From owner-freebsd-ppc@freebsd.org Thu Oct 25 20:30:13 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F7461087A34 for ; Thu, 25 Oct 2018 20:30:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACF3571ADF for ; Thu, 25 Oct 2018 20:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 685D67172; Thu, 25 Oct 2018 20:30:12 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 4D8297170 for ; Thu, 25 Oct 2018 20:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 056A071AD7 for ; Thu, 25 Oct 2018 20:30:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 34ED119A62 for ; Thu, 25 Oct 2018 20:30:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9PKUBn4082150 for ; Thu, 25 Oct 2018 20:30:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9PKUB4i082149 for powerpc@FreeBSD.org; Thu, 25 Oct 2018 20:30:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 232387] head -r339076: system crash in vnet_epair_init during kern_jail_set in a kyua test on powerpc64 Date: Thu, 25 Oct 2018 20:30:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: vimage X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: powerpc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2018 20:30:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232387 --- Comment #9 from Mark Millard --- (In reply to Mark Millard from comment #6) Looks to me like r29 is the value of (uintptr_t)&VNET_NAME(n) . But r30 is supposed to be: (curthread->td_vnet)->vnet_data_base where: /* * All use of vnet-specific data will immediately subtract VNET_STA= RT * from the base memory pointer, so pre-calculate that now to avoid * it on each use. */ vnet->vnet_data_base =3D (uintptr_t)vnet->vnet_data_mem - VNET_STAR= T; and: /* * Location of the kernel's 'set_vnet' linker set. */ extern uintptr_t *__start_set_vnet; __GLOBL(__start_set_vnet); extern uintptr_t *__stop_set_vnet; __GLOBL(__stop_set_vnet); #define VNET_START (uintptr_t)&__start_set_vnet #define VNET_STOP (uintptr_t)&__stop_set_vnet This traces back to differing definitions for wokring vs. crashing. Working (gcc 4.2.1 toolchain) /boot/kernel/kernel : 00000000013dba00 g *ABS* 0000000000000000 __start_set_vnet /boot/kernel/if_epair.ko : 0000000000015448 g *ABS* 0000000000000000 __start_set_vnet devel/powerpc64-xtoolchain-gcc based kernel: /boot/kergoo/kernel : 0000000001223800 g set_vnet 0000000000000000 .protected __start_set_vnet /boot/kergoo/if_epair.ko : 0000000000014d30 g set_vnet 0000000000000000 .protected __start_set_vnet This apparently leads to VNET_START being some small value, possibly 0. That in turn means that ?->vnet_data_base ends up not being the intended offset but directly an address. This makes adding: (uintptr_t)&VNET_NAME(n) . and: (curthread->td_vnet)->vnet_data_base junk that makes the indexed store sdtx r3,r29,r30 fail for a bad target address. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Oct 26 00:31:13 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D7EF10CF690 for ; Fri, 26 Oct 2018 00:31:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7F557AB9A for ; Fri, 26 Oct 2018 00:31:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 8FB66AFDF; Fri, 26 Oct 2018 00:31:12 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 8BDC9AFDE for ; Fri, 26 Oct 2018 00:31:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59E117AB92 for ; Fri, 26 Oct 2018 00:31:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2DFC81BC1F for ; Fri, 26 Oct 2018 00:31:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9Q0V80Y071361 for ; Fri, 26 Oct 2018 00:31:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9Q0V8VB071360 for powerpc@FreeBSD.org; Fri, 26 Oct 2018 00:31:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 232387] head -r339076: system crash in vnet_epair_init during kern_jail_set in a kyua test on powerpc64 Date: Fri, 26 Oct 2018 00:31:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: vimage X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: powerpc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2018 00:31:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232387 --- Comment #10 from Mark Millard --- (In reply to Mark Millard from comment #9) In other terms, the gcc 4.2.1 WITH_BINUTILS_BOOTSTRAP=3D tool chain based build generates (elfdump output): entry: 72 st_name: __start_set_vnet st_value: 0x15448 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 65521 where 65521 is SHN_ABS, i.e., 0xfff1 . By contrast the devel/powerpc64-gcc + base/binutils (or devel/powerpc64-binutils ) toolchain context generates: entry: 73 st_name: __start_set_vnet st_value: 0x14d30 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 17 The 17 looks odd to me because: Sections: Idx Name Size VMA LMA File off A= lgn 0 .note.gnu.build-id 00000048 0000000000000158 0000000000000158 000001= 58=20 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA . . . 16 set_vnet 00000008 0000000000014d30 0000000000014d30 00004d30 2= **3 CONTENTS, ALLOC, LOAD, DATA 17 .bss 00000008 0000000000014d38 0000000000014d38 00004d38 2= **2 ALLOC . . . --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Oct 26 02:01:55 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E4D310D1D53 for ; Fri, 26 Oct 2018 02:01:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3662B7D70F for ; Fri, 26 Oct 2018 02:01:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id DF1D7C1CC; Fri, 26 Oct 2018 02:01:54 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id BA7B1C1CB for ; Fri, 26 Oct 2018 02:01:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D1637D70A for ; Fri, 26 Oct 2018 02:01:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B38591C876 for ; Fri, 26 Oct 2018 02:01:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9Q21rPA001650 for ; Fri, 26 Oct 2018 02:01:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9Q21rIs001643 for powerpc@FreeBSD.org; Fri, 26 Oct 2018 02:01:53 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 232387] head -r339076: system crash in vnet_epair_init during kern_jail_set in a kyua test on powerpc64 Date: Fri, 26 Oct 2018 02:01:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: vimage X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: powerpc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2018 02:01:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232387 --- Comment #11 from Mark Millard --- (In reply to Mark Millard from comment #10) Looks like objdump and elfdump do not match for how section headers are numbered: 17 matches show elfdump shows it: section header: entry: 0 sh_name:=20 sh_type: SHT_NULL sh_flags:=20 sh_addr: 0 sh_offset: 0 sh_size: 0 sh_link: 0 sh_info: 0 sh_addralign: 0 sh_entsize: 0 entry: 1 sh_name: .note.gnu.build-id sh_type: SHT_NOTE sh_flags:=20 sh_addr: 0x158 sh_offset: 344 sh_size: 72 sh_link: 0 sh_info: 0 sh_addralign: 4 sh_entsize: 0 . . . entry: 16 sh_name: set_sysuninit_set sh_type: SHT_PROGBITS sh_flags:=20 sh_addr: 0x14d10 sh_offset: 19728 sh_size: 32 sh_link: 0 sh_info: 0 sh_addralign: 8 sh_entsize: 0 entry: 17 sh_name: set_vnet sh_type: SHT_PROGBITS sh_flags:=20 sh_addr: 0x14d30 sh_offset: 19760 sh_size: 8 sh_link: 0 sh_info: 0 sh_addralign: 8 sh_entsize: 0 entry: 18 sh_name: .bss sh_type: SHT_NOBITS sh_flags:=20 sh_addr: 0x14d38 sh_offset: 19768 sh_size: 8 sh_link: 0 sh_info: 0 sh_addralign: 4 sh_entsize: 0 . . . --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Sat Oct 27 15:45:30 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B53A010C7935 for ; Sat, 27 Oct 2018 15:45:30 +0000 (UTC) (envelope-from dc@genunix.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 58AAB6F147 for ; Sat, 27 Oct 2018 15:45:30 +0000 (UTC) (envelope-from dc@genunix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1E9BE10C792B; Sat, 27 Oct 2018 15:45:30 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D88210C792A for ; Sat, 27 Oct 2018 15:45:30 +0000 (UTC) (envelope-from dc@genunix.com) Received: from atl4mhob03.registeredsite.com (atl4mhob03.registeredsite.com [209.17.115.41]) by mx1.freebsd.org (Postfix) with ESMTP id 90C596F145 for ; Sat, 27 Oct 2018 15:45:26 +0000 (UTC) (envelope-from dc@genunix.com) Received: from mailpod.hostingplatform.com (atl4qobmail02pod2.registeredsite.com [10.30.77.36]) by atl4mhob03.registeredsite.com (8.14.4/8.14.4) with ESMTP id w9RFjPlo009857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 27 Oct 2018 11:45:25 -0400 Received: (qmail 48213 invoked by uid 0); 27 Oct 2018 15:45:25 -0000 X-TCPREMOTEIP: 174.118.245.214 X-Authenticated-UID: dc@genunix.com Received: from unknown (HELO ?172.16.35.3?) (dc@genunix.com@174.118.245.214) by 0 with ESMTPA; 27 Oct 2018 15:45:25 -0000 To: ppc@FreeBSD.org From: Dennis Clarke Subject: Somewhat off topic .. is there a RISC-V project for FreeBSD ? Message-ID: Date: Sat, 27 Oct 2018 11:45:24 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2018 15:45:30 -0000 Somewhat off topic .. is there a RISC-V project for FreeBSD ? Also a maillist ? Dennis Clarke