From owner-freebsd-ppc@freebsd.org Tue Aug 23 08:53:30 2016 Return-Path: Delivered-To: freebsd-ppc@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 E177FBC1AEB for ; Tue, 23 Aug 2016 08:53:30 +0000 (UTC) (envelope-from rudihl@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 42C64184D for ; Tue, 23 Aug 2016 08:53:29 +0000 (UTC) (envelope-from rudihl@gmx.de) Received: from edge.fritz.box ([93.203.110.123]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M7Hao-1bFmxL17BO-00x0uV for ; Tue, 23 Aug 2016 10:53:21 +0200 Subject: Re: 11.0 RC1 kernel panic, how to get to the debugger? To: freebsd-ppc@freebsd.org References: <7dbd570a-0d69-4ec5-0ff0-58177b2880ed@gmx.de> From: Rudi X-Enigmail-Draft-Status: N1110 Message-ID: Date: Tue, 23 Aug 2016 10:53:20 +0200 User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <7dbd570a-0d69-4ec5-0ff0-58177b2880ed@gmx.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:PlitGYp+kqXf+JW4q3JTLT2906BCSoGYJ04nnseVRNu2wOojEeC TDeeNZO/hJYdcdiBHyBk03SGqe3JPMYwviH2OcHX70k5TVCqELrsY7HS1rBFCoAyN6OXHB6 w1031vRcaTi0WBH4RDIqc8ZPCcYVoFT4NyCAg1muaLa4FIRq5s1UmWwnnAIA7SduYFpnaJs 8gtTVuwkkXk81+gUdQQfQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:tLgmvdDivxk=:MG7N2lfRIIg0fZifYH7VST 3udH8oIaaE0G4xRlLFMUKFOy+lJXYbCkZlnRgZ3bReF/B7yrC8evvLT2589X43z1fqIrP1pIf 1K7OEWKuKQQ3SrAADlqQgKumvlfOuDs3Vp3KbPXcpZoRneZGyI/g19NcMLBZ1iBvSGnlKray0 hjOYwrCH0tOqQLPOCa2Mu0GamDJT5w5f3mbfgJiE4kMsn5rL/YmS6w5T7afVDuw8sdyVMZuca iSZcm1nBwEBXp74lzMR5gQm6MraYaLhtUaS22vF9YU1ZJI31160saE95zB/aU8YQR8ike0+ac xe/TnH53h+hVKpvN0TVl2xpOvXk7g7yn1t47lTID7JBP3dn7rVC6QtXr0sOKZoJPpxwTSlWfx tOf9cKAjyRjIAK+KNutdq16Rq11oglF7PZH96XopEPPix5M63xItMv9WtMmvWOBxMsZy4upZr mBgUcL5Sxnq3od6b4F6vnW1y2IGoN75OX/vxoUu81/qqqTQXURNdIz/TVkA6ulryK1xg/xY4F K7UJpjws06o2s7U1zPKeDLTbJpZWwjW4bijFev5yQMChvVQINS50rcYZS0GnqwsoCVV9sGC43 JStzfVjyFzo6Mu2QhDNnfMsKrw3HV/5fVlWD4zTi05PQQtEWoYajQlOPSBKPntv7Bm6KuXC2T DZtkY2HpGT63zwcqZewnY9o4H0B6bKGVoD1FAYaMW4HrAc62cSr8ZS2VR1LbcHbASvMNgRbMd P20dfQYG2rbDiXyj5EfMdnhbRZJnE0OO6ADSHGBnJMQB/y9TZ4ghOHR4VzDMTFY7Jo5CFb1VV F6mB3Z9 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 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 Aug 2016 08:53:31 -0000 Hi list, did some more research and found bug 196497 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196497 I wanted to verify if that bug is what I am seeing. The description is not clear on what to do exactly, but after consulting https://wiki.freebsd.org/Newcons I decided that getting to the kernel debugger and typing ddb: set vty=sc ddb: continue should do what is not spelled out directly. Is that assumption correct? However, I seam to be unable to get to the kernel debugger in the first place. How to repeat: ================ in open firmware 0 > boot cd:,\ppc\loader cd:0 //as per FreeBSD Handbook chapter 2.4 at the loader "hit return or wait 10 sec" I hit space, which gives the loader prompt: OK https://www.freebsd.org/cgi/man.cgi?query=loader&apropos=0&sektion=0&manpath=FreeBSD+11.0-RELEASE&arch=powerpc&format=html Unfortunatly makes not clear what to do exactly with the "boot_ddb" variable. set boot_ddb // set boot_ddb=YES // set boot_ddb=1 // set kernel_options=boot_ddb // and then boot All 4 fail the same way: the kernel loads, probes devices -at which point it is clear the variable did not take effect- and then ultimatly panic and reboot. Expected behaviour: =================== right after the copyright notice, befor any device is probed get: ddb: What am I missing? Enlightenment welcome. /Rudi