From owner-freebsd-current@freebsd.org Tue Oct 6 13:37:50 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7C09433643; Tue, 6 Oct 2020 13:37:50 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C5JSG03lKz4VbM; Tue, 6 Oct 2020 13:37:49 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qt1-x82c.google.com with SMTP id s47so4301715qth.4; Tue, 06 Oct 2020 06:37:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=BXTMiiP0ETsEtIkLqxngtJv9K8OCm2bx2i2BOsde/LE=; b=lwO19Lq2wY05Bat0+qbGvORLFD6jdCFWUp0xcnjMY3opc4fFqcf9RmzYx9tbm0qGJn 4mmGLrarMi5P34RkkKnjR8NujOcc3s3fZfGgwY7iS+64no06GuBZl/tsj92O79c2XKyu dQJ6bE9AgptcoRLwIUU73vCeEWgSO16p3OODV4dFQE3wVROMcf4y9DsqaXkphUZcmnJA s52QcuWfwf08ryQULo5fKiEs+KBkA96IQW+U7xv1ErEbAvnMrUmxTKmQwsQMC3yxLKQ+ KC81XHCODqfbVnPHPVWFJXHu5aGHOk+CdbZ/cdeKUeQIsKNyxSkrBHFD5BhLnVHg9Iag D58Q== X-Gm-Message-State: AOAM533osdiNfd3RTEuPxcFm2z8iVfbxB5mIKwRdCiSAKi4j/E9Wbyid cGEBwEo7j484XMlOXQXwoB+ge435xwf81w== X-Google-Smtp-Source: ABdhPJwGINjALUZUj089+qeHfs6DQkspgs3OOfwneyHqeIhq9rHeVKdCnz6U9pzQlmR8LrVLh6rbtg== X-Received: by 2002:ac8:3984:: with SMTP id v4mr5220627qte.240.1601991468946; Tue, 06 Oct 2020 06:37:48 -0700 (PDT) Received: from raichu (toroon0560w-lp130-01-174-88-77-103.dsl.bell.ca. [174.88.77.103]) by smtp.gmail.com with ESMTPSA id e39sm2374695qtk.32.2020.10.06.06.37.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 06 Oct 2020 06:37:47 -0700 (PDT) Sender: Mark Johnston Date: Tue, 6 Oct 2020 09:37:43 -0400 From: Mark Johnston To: bob prohaska Cc: freebsd-current@freebsd.org, freebsd-arm@freebsd.org Subject: Re: panic: non-current pmap 0xffffa00020eab8f0 on Rpi3 Message-ID: <20201006133743.GA96285@raichu> References: <20201006021029.GA13260@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201006021029.GA13260@www.zefox.net> X-Rspamd-Queue-Id: 4C5JSG03lKz4VbM X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.17 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.03)[-1.030]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; NEURAL_HAM_SHORT(-0.49)[-0.494]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::82c:from]; NEURAL_HAM_MEDIUM(-0.95)[-0.946]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; MAILMAN_DEST(0.00)[freebsd-current,freebsd-arm] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 13:37:51 -0000 On Mon, Oct 05, 2020 at 07:10:29PM -0700, bob prohaska wrote: > Still seeing non-current pmap panics on the Pi3, this time a B+ running > 13.0-CURRENT (GENERIC-MMCCAM) #0 71e02448ffb-c271826(master) > during a -j4 buildworld. The backtrace reports > > panic: non-current pmap 0xffffa00020eab8f0 Could you show the output of "show procvm" from the debugger?