From owner-freebsd-ppc@freebsd.org Fri Aug 5 09:33:32 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 37B8CBAF888 for ; Fri, 5 Aug 2016 09:33:32 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE740113C for ; Fri, 5 Aug 2016 09:33:31 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id q128so24110250wma.1 for ; Fri, 05 Aug 2016 02:33:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mkJ2N+CxyNorslP7cHY2dANymTub095gaP4whGDLz7Q=; b=USu9lPdV4uiY/8sCbVABJ5WieF/I7Hju1gKUI977n+ZTPXvYATEO/Mt5x3rCQ2ZBhJ Jmyanqo6Io3ldwHeD26aPguA2nYB2VRkUBuRbOVRnEQtBG7uLVshr5bvL31X56ExVSC9 lqFhVHFKPRu/Oe6rRHePapIp+/YhSIe+MeAyYbPL3SgePQwicEMH6ybkB2DSeZTkOe2V SN/T7GJaVCohZn+VTtrOXA1LRc2utCursrWuNJOKWLe+kdzwVbX3TK7hg+/NIEKdUu1/ ePFVvQvb1ueYrZYi4BsKsvjxsWE3fwXNM5HgALo1wF/vZludZbv8uamtb3HiOPJK6V9+ Yiwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mkJ2N+CxyNorslP7cHY2dANymTub095gaP4whGDLz7Q=; b=Js8bazgB4DGkL0tq8SmQnpL+o7xY6oFiV6jgW7l1V2qWJUrgeGgTIPdlB5DBhYcx62 5AVHJoY5GjsW8GjrOW+6VsUs5SGp0nECq6UYg+3JAaUlWqziEnw2rZFdfeV6vW1k7S1y 0Np8GQwUFvgpNiUSTsBzvoPPkcm5PX5oN61OkFRKg4jsgMks+xf6hT/hW680/GxQ5sJI MD1SDJqrcG5SzrPhmpKVQvHOojc4tzbn3CLKPDQ97cUGYdkYka9mVkoC7u/eOJQRxXL1 PLSQJbGSt/M50crnNMfrR3BSO2E/DQil2fjRdOvmyxh/C2SFAWZXOiLBSCANtT+Wvd2X l1ig== X-Gm-Message-State: AEkoouv98RAY0SG5+FMjfvUDhbXDgEw2a4f0K2j0kEFLZnmLGfO0A3fWVlBh/aEU4zBB8Q== X-Received: by 10.194.79.161 with SMTP id k1mr18132615wjx.119.1470389609870; Fri, 05 Aug 2016 02:33:29 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id p23sm7736702wme.8.2016.08.05.02.33.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Aug 2016 02:33:29 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig From: Jukka Ukkonen X-Mailer: iPad Mail (13G35) In-Reply-To: Date: Fri, 5 Aug 2016 12:33:23 +0300 Cc: FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> References: To: Justin Hibbits 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: Fri, 05 Aug 2016 09:33:32 -0000 > On 04 Aug 2016, at 17:31, Justin Hibbits wrote: > >> On Thu, Aug 4, 2016 at 1:59 AM, Jukka A. Ukkonen wrote: >> >> Hello all, >> >> Has anyone else noticed a similar problem with 11.0-BETA3? >> My G5 boots just fine with 11-BETA2. When I built the latest >> BETA3 source yesterday afternoon the system started panicing >> during the boot. The message shown flashes so quickly past >> the screen that I have no idea what it is trying to say. >> Though kern.panic_reboot_wait_time is set to 15 seconds, >> the system apparently does not obey this delay. It reboots >> immediately after showing the panic message. >> >> --jau > > Can you try setting at the loader 'debug.debugger_on_panic=1'? It > *shouldn't* reboot then so you can poke around, and give the panic > message. Unfortunately I haven't had time to update my G5, it's still > running head from back in October. > > - Justin I tried this and set also debug.bootverbose=1 to see some additional info. It did not help the debugging, though. The quick flashing of the error message and instant reboot still prevent reading the message. Anyhow I managed to notice that autoconfigure got past reporting atapci0 and atapci1. Right after these there has usually been notes about timecounter, etc. So, I got the idea that maybe it is the timecounter initialization that fails. This could also explain why there is no delay between the error message and reboot. Testing this hypothesis is now on my to do list, but it will take some time. --jau