Date: Sun, 16 Jun 2013 17:12:13 -0700 From: Tim Kientzle <tim@kientzle.com> To: Sreekanth Rupavatharam <rskanth@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: arm/179561: Compilation issue for lighttpd on raspberry pi Message-ID: <A23406C8-531B-4722-9CFD-A678BC5F686A@kientzle.com> In-Reply-To: <201306162210.r5GMA05N031413@freefall.freebsd.org> References: <201306162210.r5GMA05N031413@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 16, 2013, at 3:10 PM, Sreekanth Rupavatharam wrote: >=20 > On 6/14/13 5:25 PM, hiren panchasara wrote: >> Does this look = similar?:http://www.freebsd.org/cgi/query-pr.cgi?pr=3D178495 >>=20 >> FWIW, Clang got updated to release 3.3 a couple days back on HEAD. = Not >> sure if this is fixed in that version. >>=20 >> cheers, >> Hiren > No, looks like the issue remains on today's revision of HEAD. On top = of=20 > that looks like the kernel for raspberry pi is broken. It now hangs at=20= > Kernel args: (null). The "Kernel args:" line is the last thing printed by ubldr before transferring control to the kernel. If this is the last thing you see, then any of the following could be at issue: * ubldr could be broken, either not loading the kernel or not = transferring control properly. * kernel could be crashing in the early setup * kernel could be crashing in initarm (before the console is = initialized) If you can boot an older kernel with newer ubldr, then that would rule out ubldr breakage. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A23406C8-531B-4722-9CFD-A678BC5F686A>