From owner-freebsd-arch@freebsd.org Sat May 19 01:14:25 2018 Return-Path: Delivered-To: freebsd-arch@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 552F3EE3508 for ; Sat, 19 May 2018 01:14:25 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-23.consmr.mail.ne1.yahoo.com (sonic311-23.consmr.mail.ne1.yahoo.com [66.163.188.204]) (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 BB929730E1 for ; Sat, 19 May 2018 01:14:24 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: EwX6AUIVM1lUPOUXdR2CMcSo3rD78JVZu8CXtjGghZMOU5L4PB8VWRYEfIjtFiC SUK2qYU4m8MEAsoTOpna1L8CimXeb7p67RG_ZliOUy1ITLvI7edhRv_Vba7KeXhgf5R1JbnrUy2m pe4JoNAjyG.i6m.YV71dTVBtc0KZbx60Bjn2BrQdz2aG5ci5ZLVlC6s051N1fRW6cV57Zw3hwFU. LxqepViORRhYZ8rUZDd54XINyQkpMtYkIW_YZyZMlMgMmM33ZehvNO0gFvPU3pk5OiIcW9PLfl2v x5UDcN3EB1jzjZ2VhXWgHsTNIJhYVs56CdVXhUaqqpV00OLU_tHgyu5jszOFo_dY6HsH8digCbSD gyZejFG8OQ14QHKUhRSzCFnLbQ7pHQZUH3ablCZhwGzVxonBN2agmHfQEv3UkNVw.93JHt9NcE8Q 6wS6oyHu_HUbq.WJMRrk1xMLmgUDY1AK38skLyVKK_fK2FVzjFpFY679Idvs6mj7XBJdR3FvQ7bm RM1Ea5fOqOeB.g3vf4KDgwciq630KBnBXNprpgS1Ihjgw3PlBSYijUmI1sNbtVw1vN9Yzi0qdGpo 57H0S6u1zd_rKGQrGlasFbtH6rxGJwcpz1ppOZVi7RzLwtqJTqU1frZI0VgJlaBNFMXftx5sFE.. dk3KBnb2z Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ne1.yahoo.com with HTTP; Sat, 19 May 2018 01:14:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp409.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4b44c99488cf204d5d8b53f8e16ac17c; Sat, 19 May 2018 01:14:13 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC From: Mark Millard In-Reply-To: <20180518151120.GE5515@raichu> Date: Fri, 18 May 2018 18:14:12 -0700 Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <7F24144E-62CC-480F-A605-D06D2A4C7142@yahoo.com> References: <20180518061739.GC5515@raichu> <20180518151120.GE5515@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 01:14:25 -0000 On 2018-May-18, at 8:11 AM, Mark Johnston wrote: > On Fri, May 18, 2018 at 06:14:50AM -0700, Mark Millard wrote: >> On 2018-May-17, at 11:17 PM, Mark Johnston = wrote: >>=20 >>> On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: >>>> . . . >>>> Bugzilla 214598 (from late 2016) was about >>>> dump for TARGET_ARCH=3Dpowerpc64 builds getting >>>> failures like: >>>>=20 >>>> KDB: enter: manual escape to debugger >>>> [ thread pid 12 tid 10018 ] >>>> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 >>>> db> dump >>>> Dumping 9 MB (3 chunks) >>>> chunk 0: 10MB (2510 pages) ... ok >>>> chunk 1: 1MB (24 pages) ... ok >>>> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, = addr: c000000000022000 >>>>=20 >>>> (A 32-bit powerpc build on the same machine worked >>>> fine for dumping.) >>>>=20 >>>> I just tried it with head -r333594 and I got something >>>> similar. (Old and new mention routines with _bus_dma_map_ >>>> in the names near the trap in the call stack. I've not >>>> done a detailed comparison.) >>>=20 >>> What is the call stack? >>=20 >> I'll have to induce the failure, take a picture of >> the screen that results, and hand type in the >> material for the fairly modern backtrace (-r333594). >> I will not be able to do this until later today. >>=20 >> The bugzilla report has the old backtrace. I did not >> quote all the material from that report in the above. >> So there is something to compare against once I >> supply a modern one. >=20 > My apologies, I missed the fact that the backtrace was included in = that > PR. Since the problem still occurs and apparently manifests with a > similar backtrace, it wouldn't be useful to retest. I'm afraid I don't > have any suggestions on how to make progress here. Given that the new > options give only a small increase in the kernel size, I'm still > inclined to enable them on powerpc64 for consistency with other > architectures. Seems reasonable. May be there are other powerpc64 contexts that can test the updates. Useful or not, I've updated bugzilla 214598 with a backtrace from head -r333594 and have updated its one-line summary to reference -r333594 . Looks like I missed a 0 in: 0xe7ced0: at 0xc00000006ab17fc it should be: 0xe7ced0: at 0xc000000006ab17fc I've no clue why this address has no symbol. I showed more of the stack this time. At least now the old and new can be compared. That is better than forcing folks to rely on my earlier quick look. >> Also: in about a week I'll lose access to the PowerMacs >> for an unknown period of time (weeks? months?). >>=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)