Date: Wed, 10 Sep 2014 14:08:19 -0700 From: Danilo Egea <daniloegea@yahoo.com.br> To: Hans Petter Selasky <hps@selasky.org>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: panic: run_interrupt_driven_config_hooks: waited to long on 10.1-PRERELEASE + RPI-B Message-ID: <1410383299.82284.YahooMailNeo@web162004.mail.bf1.yahoo.com> In-Reply-To: <5410BCEA.8060100@selasky.org> References: <1410382322.23950.YahooMailNeo@web162003.mail.bf1.yahoo.com> <1410382596.45838.YahooMailNeo@web162005.mail.bf1.yahoo.com> <5410BCEA.8060100@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/10/14 22:56, Danilo Egea wrote:=0A=0A=0A=0A> Hi all,=0A>=0A>=0A>=0A>= =0A>=0A>=0A> I updated my system on raspberry to 10.0-PRERELEASE (r271400) = and now the system is stopping at this point [1].=0A> This is a known probl= em?=0A>=0A> Sorry the bad quality picture...=0A>=0A> [1] - https://www.drop= box.com/sc/r89hs2wal7dpn44/AABCKqJzAB7FzlHugfUvQrUva=0A>=0A>=0A>=0A> Oops, = sorry. The correct is 10.1-PRERELEASE, of course.=0A=0A=0AHi,=0A=0AWhat doe= s "bt" say?=0A=0A--HPS=0A=0AThis is another problem, the usb keyboard is no= t working at this point.=0A From owner-freebsd-arm@FreeBSD.ORG Wed Sep 10 21:20:00 2014 Return-Path: <owner-freebsd-arm@FreeBSD.ORG> Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6655CC6 for <arm@freebsd.org>; Wed, 10 Sep 2014 21:20:00 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 90D5BDC6 for <arm@freebsd.org>; Wed, 10 Sep 2014 21:20:00 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9C890B964 for <arm@freebsd.org>; Wed, 10 Sep 2014 17:19:59 -0400 (EDT) From: John Baldwin <jhb@freebsd.org> To: arm@freebsd.org Subject: NEW_PCIB and arm take 3 (4?) Date: Wed, 10 Sep 2014 17:19:55 -0400 Message-ID: <74248385.OR9iBtFISv@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 10 Sep 2014 17:19:59 -0400 (EDT) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>; List-Post: <mailto:freebsd-arm@freebsd.org> List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 10 Sep 2014 21:20:00 -0000 The plan for NEW_PCIB was for it to be a temporary option that would eventually become the default on all platforms. I have long had patches to provide the one step of infrastructure (namely implementing "real" bus_activate_resource methods) for various arm chipsets, but I haven't been able to get anyone to review or test them. I'm about at the point of just committing them in a week barring any specific reports from testers or reviewers. You can read more about what NEW_PCIB is at: https://wiki.freebsd.org/NEW_PCIB These patches aim to implement step 2 from that wiki page. However, I have no way to test them (and to be honest, I haven't recently tested to see if they will compile. I will ensure make universe passes before pushing them in if it comes down to that.) http://people.freebsd.org/~jhb/patches/arm_activate2.patch As I noted previously, I don't know how to properly fix i80321_pci in large part because I do not understand what it is doing. Warner had previously suggested just dropping it and if the consensus is to do that, I'd be much obliged for someone to make it so. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1410383299.82284.YahooMailNeo>