From owner-freebsd-arm@freebsd.org Tue Feb 23 01:12:47 2016 Return-Path: Delivered-To: freebsd-arm@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 26E5BAB149E for ; Tue, 23 Feb 2016 01:12:47 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1A0BD6 for ; Tue, 23 Feb 2016 01:12:46 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: c15cfc88-d9ca-11e5-8de6-958346fd02ba X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 23 Feb 2016 01:14:15 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u1N1Cioh006684; Mon, 22 Feb 2016 18:12:44 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1456189964.1294.69.camel@freebsd.org> Subject: Re: Latest 11.0 snapshot won't boot on CUBOX either From: Ian Lepore To: =?ISO-8859-1?Q?Mika=EBl?= Urankar Cc: "freebsd-arm@freebsd.org" Date: Mon, 22 Feb 2016 18:12:44 -0700 In-Reply-To: References: <201602220109.SAA20866@mail.lariat.net> <1456113068.1294.46.camel@freebsd.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 01:12:47 -0000 On Mon, 2016-02-22 at 11:30 +0100, Mikaël Urankar wrote: > 2016-02-22 10:30 GMT+01:00 Mikaël Urankar : > > 2016-02-22 4:51 GMT+01:00 Ian Lepore : > > > On Sun, 2016-02-21 at 18:09 -0700, Brett Glass wrote: > > > > After the experience described in my last message, I tried the > > > > mid-February 11.0 snapshot (r295683). This one actually began > > > > to > > > > use the video display, but did not boot whether or not I > > > > attached a > > > > USB keyboard. A serial terminal showed the following: > > > > > > > > [...] > > > > --Brett Glass > > > > > > My wandboards have hung up the same way for about a week now, but > > > I > > > haven't had time to investigate why. > > > > > > -- Ian > > > > The update of the Linux dts breaks the imx6 (r295436) > > They have changed the interrupt-parent to gpc in the 'soc' structure: > /usr/src/sys/gnu/dts/arm/imx6qdl.dtsi > soc { > interrupt-parent = <&gpc>; > > My imx6q boots fine if I put back &intc > I don't know what is the correct fix though Thanks for diagnosing this, it saved me a bunch of time. The real fix some day will be to have a driver for the second interrupt controller and hand off control between that driver and the GIC driver as we switch in/out of deep sleep modes. First we would have to support deep sleep modes. :) For now, I've committed a workaround in r295904 that just rewrites the FDT in kernel memory during early kernel init, pointing the soc node interrupt parent back to the GIC controller, to make everything work the way it always has for us. -- Ian