Date: Thu, 18 Apr 2013 18:08:18 +1000 From: Andrew Turner <andrew@fubar.geek.nz> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arm@FreeBSD.org" <freebsd-arm@freebsd.org> Subject: Re: __rw_wlock_hard panic on 1st malloc Message-ID: <20130418180818.1d036620@bender> In-Reply-To: <0E720F47-E84A-4CC8-8A56-1031AB6DB65A@bsdimp.com> References: <DB4E4AA0-91D8-4253-8044-9C33B60E1A3A@gmail.com> <8DE83B01-4508-41C5-B2BD-95A72D0AD963@bsdimp.com> <BD1AE699-31B2-4F13-8222-BEB90EE0E57E@gmail.com> <B94DB19B-7940-4376-B38B-369FD0E45282@bsdimp.com> <92C60946-8FFB-46A1-9400-9E0F7B11FC23@gmail.com> <9A3C042F-3765-4791-AB51-63EA82488743@bsdimp.com> <20130418113609.5880e469@bender> <0E720F47-E84A-4CC8-8A56-1031AB6DB65A@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Apr 2013 22:36:29 -0600 Warner Losh <imp@bsdimp.com> wrote: > > On Apr 17, 2013, at 7:36 PM, Andrew Turner wrote: > > > On Wed, 17 Apr 2013 09:37:26 -0600 > > Warner Losh <imp@bsdimp.com> wrote: > > > >> I don't think it is, at least not with clang compiled code. Ian was > >> saying on IRC that he saw this and went back to gcc and life was > >> good. > > > > I suspect it is an issue with the newer version of clang imported > > recently. I have tested with an old version of clang and an updated > > kernel and had no issues booting. > > If I take WITNESS out of the kernel, I have no issues either. Not > sure what WITNESS' problem is... I've tried with an updated clang on a PandaBoard with WITNESS enabled. The only issue I'm hitting is vm_thread_new fails, but this is after FreeBSD enters userland which, from you other emails, appears to be further than you are getting. I have set unmapped_buf_allowed = 0 in sys/arm/arm/pmap-v6.c to work around the above stack issue. I don't know if this will fix the issue or not but you can try it to see. Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130418180818.1d036620>