From owner-freebsd-ppc@freebsd.org Sat May 20 05:24:52 2017 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 9E904D75DFB for ; Sat, 20 May 2017 05:24:52 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 5993C1EAD for ; Sat, 20 May 2017 05:24:52 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qk0-x230.google.com with SMTP id y201so75666352qka.0 for ; Fri, 19 May 2017 22:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=tQeTNwca8rGPM/9wA6vTLqDXLn7V4GJ5jUV6sb7sv98=; b=RhcJ70dKNpigTuRNy0XR6mTQrh6nAeI5vxjXSvCMj+luVunKcTvdHeBmnHiwYkIYOj CY+oyJJTtBuVZnH1O6IawAIDF2CaPKnm6/3kbygoE0zvmxa9927E7+3NBhs518ZCrE18 zqm6mXEI237G3+KvsAhcMuUAlBhttYvEy+EJRPXwwsaE07c2wL9kR7Mfr5N4Ka3RRP3z pH7m4AJQB3QlvLv+CzSMQZIxEhUfb+WSUQT7hiKZzbO/j1tA9vPrzenmlquuPX03DC9Y bL/Q2Isg9duNj01E1sldo7VeO28O+m9Dihqh574KH3B+S+gmhM5Q8n7KhNQ3RJQUufB2 CT0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=tQeTNwca8rGPM/9wA6vTLqDXLn7V4GJ5jUV6sb7sv98=; b=MTYHHOjqkGrC31ho6jg+FPZEz4oXvR0N7N1CSgTMejhEKqXGkoAi6eJ3Q8I9UzdwAb /0vNRBHBj5gXmMwgFp82DywvlRL4AUXXfIZP2YuflghinF4vnt9up6dAIc6bxwRil4B5 AxNSUnw6a5vBKIYp921WAOWP5X4AdudnZTUVI4UnenLMRg8CcmG9/bT343AO+o58yUn9 FX4tywCFEZcYS8EiLAGnwKoGpt21Wb5rTxUcYX/OX+b46BQNzzIZs7jy0aPtCSf5ykuy MhQl6KEjdMu5N33b8xZcW0j+1aMM2Ze7Xi14RXlYNmItpVCnTdRWyCLhuI+WTt0W4Cyz Y0LQ== X-Gm-Message-State: AODbwcDgaVAxcHSt25Ae7GkUuppyoqRLugYqS81XUyyp+zjnmErgMD08 4Bkp9CDB3BWUCkVbXM+OBqLMc79bOQ== X-Received: by 10.233.216.194 with SMTP id u185mr12876910qkf.105.1495257891510; Fri, 19 May 2017 22:24:51 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.168.203 with HTTP; Fri, 19 May 2017 22:24:50 -0700 (PDT) In-Reply-To: <0BC58DBC-AC9B-46F8-8F3A-1AEB90622BC4@dsl-only.net> References: <0BC58DBC-AC9B-46F8-8F3A-1AEB90622BC4@dsl-only.net> From: Justin Hibbits Date: Sat, 20 May 2017 00:24:50 -0500 X-Google-Sender-Auth: B1acCeLLeAc9VKbght21svV9fDc Message-ID: Subject: Re: FYI: powerpc EXC_LAST==0x2f00 vs. EXC_DEBUG ==0x2f10 and such? To: Mark Millard Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 May 2017 05:24:52 -0000 On Tuesday, May 16, 2017, Mark Millard wrote: > [Context: > > I'm having problems with production-style kernel builds > for TARGET_ARCH=powerpc (used an old PowerMac G5 so-called > "Quad Core") getting occasional panics that involve > oddities like: > > frame->exc == 0x903a64e > > in the fatal kernel trap information on the console > display. > > I'm not claiming the below is related but while looking > around to figure out how to investigate I ran into > what I report below. (The first 2 are from a block of > 4xx / 85xx EXC_'s). > ] > > > From /usr/src/sys/powerpc/include/trap.h : > > #define EXC_DEBUG 0x2f10 /* Debug trap */ > #define EXC_VECAST_E 0x2f20 /* Altivec Assist (Book-E) */ > > #define EXC_LAST 0x2f00 /* Last possible exception vector > */ > > #define EXC_AST 0x3000 /* Fake AST vector */ > > /* Trap was in user mode */ > #define EXC_USER 0x10000 > > And also: > > /usr/src/sys/powerpc/ofw/ofw_machdep.c:char > save_trap_init[0x2f00]; /* EXC_LAST */ > /usr/src/sys/powerpc/ofw/ofw_machdep.c:char > save_trap_of[0x2f00]; /* EXC_LAST */ > > /usr/src/sys/powerpc/include/profile.h:#define __PROFILE_VECTOR_TOP > (EXC_LAST + 0x100) > > These makes it look like EXC_LAST and some literal > 0x2f00's might be insufficient for some contexts. > Nope EXC_LAST is correct as-is. It's the last possible exception vector for AIM, as that uses physical pages at those addresses for the exception vectors. Anything above EXC_LAST is an artificial exception. Now, it does look odd, so I should move the EXC_DEBUG and EXC_VECAST_E down below the EXC_LAST for sorting purposes. - Justin