From owner-freebsd-ppc@freebsd.org Mon Oct 29 19:44:12 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 B0A4510E8703 for ; Mon, 29 Oct 2018 19:44:12 +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 584427FD24 for ; Mon, 29 Oct 2018 19:44:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 491CB1C5FF; Mon, 29 Oct 2018 19:44: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 2B8B31C5FE for ; Mon, 29 Oct 2018 19:44: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 F0EF37FD22 for ; Mon, 29 Oct 2018 19:44:11 +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 2B69FB9AE for ; Mon, 29 Oct 2018 19:44: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 w9TJiBPj090962 for ; Mon, 29 Oct 2018 19:44:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9TJiBTC090961 for powerpc@FreeBSD.org; Mon, 29 Oct 2018 19:44: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: Mon, 29 Oct 2018 19:44: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: Mon, 29 Oct 2018 19:44:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232387 --- Comment #12 from Mark Millard --- (In reply to Mark Millard from comment #10) It turns out that my amd64 kernel builds are like the devel/powerpc64-xtoolchain-gcc ones in that instead of SHN_ABS it has a normal st_shndx value: ( these are looking at /boot/kernel/kernel ) entry: 16765 st_name: __start_set_vnet st_value: 0xffffffff824dc200 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 50 This might suggest powerpc64's kernel having incomplete coverage for handling such things? For the amd64 context, that 50 is: entry: 50 sh_name: set_vnet sh_type: SHT_PROGBITS sh_flags: SHF_WRITE|SHF_ALLOC sh_addr: 0xffffffff824dc200 sh_offset: 36553216 sh_size: 220872 sh_link: 0 sh_info: 0 sh_addralign: 16 sh_entsize: 0 A constrasting devel/powerpc64-xtoolchain-gcc based kernel has entries (note the set_vnet sh_flags differences vs. amd64): ( these are also looking at /boot/kernel/kernel ) entry: 40 sh_name: set_vnet sh_type: SHT_PROGBITS sh_flags:=20 sh_addr: 0x1223800 sh_offset: 18036736 sh_size: 212656 sh_link: 0 sh_info: 0 sh_addralign: 8 sh_entsize: 0 and for __start_set_vnet : entry: 1490 st_name: __start_set_vnet st_value: 0x1223800 st_size: 0 st_info: STT_NOTYPE STB_GLOBAL st_shndx: 40 --=20 You are receiving this mail because: You are the assignee for the bug.=