From owner-freebsd-arm@FreeBSD.ORG Sun Mar 22 15:19:59 2015 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5B97A26; Sun, 22 Mar 2015 15:19:59 +0000 (UTC) Received: from kanar.ci0.org (kanar.ci0.org [IPv6:2001:bc8:35e6::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87F24BF3; Sun, 22 Mar 2015 15:19:58 +0000 (UTC) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.14.8/8.14.8) with ESMTP id t2MFJYYL033123; Sun, 22 Mar 2015 16:19:34 +0100 (CET) (envelope-from mlfbsd@kanar.ci0.org) Received: (from mlfbsd@localhost) by kanar.ci0.org (8.14.8/8.14.8/Submit) id t2MFJYNj033122; Sun, 22 Mar 2015 16:19:34 +0100 (CET) (envelope-from mlfbsd) Date: Sun, 22 Mar 2015 16:19:34 +0100 From: Olivier Houchard To: Michael Tuexen Subject: Re: panic: pmap_demote_section: No l2_bucket for wired mapping Message-ID: <20150322151934.GA31108@ci0.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2015 15:20:00 -0000 On Sun, Mar 22, 2015 at 06:54:06AM -0500, Michael Tuexen wrote: > Dear all, > Hi Michael, > running head on a Raspberry Pi became unstable. When running > r280329 for a while (the machine is exposed to the Internet, so > ssh logins are continuously tried), the machine panics: > > panic: pmap_demote_section: No l2_bucket for wired mapping > > It might be related to > https://svnweb.freebsd.org/changeset/base/280324 > > Any idea what is going on? > Doest backing rev 280324 out fixes it ? I'm at a loss as to why my commit could provoke this, and can't seem to reproduce it on my pandaboard. Another possibility is that rev 280327, which makes it possible to map library's code using superpages, uncovered a bug somewhere. Regards, Olivier