From owner-svn-src-head@freebsd.org Thu Jun 15 23:08:01 2017 Return-Path: Delivered-To: svn-src-head@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 3ECE2BF1109 for ; Thu, 15 Jun 2017 23:08:01 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-16.reflexion.net [208.70.210.16]) (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 E1A643F0E for ; Thu, 15 Jun 2017 23:08:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 18116 invoked from network); 15 Jun 2017 23:09:24 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 15 Jun 2017 23:09:24 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Thu, 15 Jun 2017 19:07:59 -0400 (EDT) Received: (qmail 31912 invoked from network); 15 Jun 2017 23:07:59 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 15 Jun 2017 23:07:59 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 941B8EC8B7B; Thu, 15 Jun 2017 16:07:58 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r319722 - in head: sys/cam/ctl sys/dev/iscsi sys/kern sys/netgraph sys/netgraph/bluetooth/socket sys/netinet sys/ofed/drivers/infiniband/core sys/ofed/drivers/infiniband/ulp/sdp sys/rpc... Message-Id: Date: Thu, 15 Jun 2017 16:07:58 -0700 To: andreast@FreeBSD.org, svn-src-head@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jun 2017 23:08:01 -0000 FYI: in the current memory layout my -r317820 variant has been up for 3 days 17+ hours. (Various extra checks for panicking on some observed failures earlier but no HACKISH_EXTRA_CODE.) I think the wrong code was looked up. . . The code you reported having the failure: > 5a5a18: 38 7c 00 10 addi r3,r28,16 > 5a5a1c: 4b f1 c4 61 bl 4c1e7c <__mtx_unlock_sleep> > 5a5a20: 7f 63 db 78 mr r3,r27 > ->5a5a24: 4b ff f5 9d bl 5a4fc0 > 5a5a28: 48 00 04 80 b 5a5ea8 > 5a5a2c: 7c 45 13 78 mr r5,r2 > 5a5a30: 39 20 00 04 li r9,4 The trap you reported in the picture (notes added): > exception = 0x700 (program) > srr0 = 0x6064a90 (the address were execution was attempted) > srr1 = 0x89032 > lr = 0x5a500c (early inside solisten_wakeup) > curthread = 0x6c So: 0x5a4fc0 (solisten_wakeup) 0x5a500c (lr being early inside solisten_wakeup?) What about the code around 0x5a5a24 could possibly jump to 0x6064a90 ? How about around 0x5a500c that is closer to where the processor was executing? I usually have to look at what the backtrace reports and see if a call was made (bl) there and look at what was called. Powerpc backtraces can miss a layer of subroutine that is active. === Mark Millard markmi at dsl-only.net