Date: Sat, 05 May 2018 21:47:17 +0200 From: "Herbert J. Skuhra" <herbert@gojira.at> To: freebsd-arm@freebsd.org Subject: Re: Rpi2 at r333141, no usable event timer Message-ID: <87efipanqy.wl-herbert@gojira.at> In-Reply-To: <20180505164904.GA43536@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On Sat, 05 May 2018 18:49:04 +0200, bob prohaska wrote: > > An RPi2 at r333141 fails to boot with a series of "cannot allocate > resource...." messages, ending with > panic: No usable event timer found! > and a short backtrace. The console output is at > > > http://www.zefox.net/~fbsd/rpi2/crashes/20180505/console > > Is there a workaround, short of reinstallation? One oddity > is that old kernels, which formerly worked, now fail in the > same way. Since both buildworld and kernel-toolchain failed > to build with "out of swap" messages this kernel was made > using "make kernel". > > Swap is 2GB, formerly sufficient but seemingly no longer so. > > Thanks for reading, Author: gonzo Date: Wed May 2 20:04:25 2018 New Revision: 333177 URL: https://svnweb.freebsd.org/changeset/base/333177 Log: Unbreak RaspberryPi 2 boot after r332839 r332839 changed number of cells per interrupt for local_intc from 1 to 2 to pass type of IRQ. Driver expected only 1 cell so after r332839 all interrupt children of local_intc failed to allocate IRQ resource. Fix this regression by relaxing check for number of cells in interrupt property to be either 1 or 2. PR: 227904 Modified: head/sys/arm/broadcom/bcm2835/bcm2836.c -- Herberthelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87efipanqy.wl-herbert>