Date: Thu, 18 Apr 2013 07:39:23 -0600 From: Warner Losh <imp@bsdimp.com> To: Damjan Marion <damjan.marion@gmail.com> Cc: "freebsd-arm@FreeBSD.org" <freebsd-arm@freebsd.org> Subject: Re: __rw_wlock_hard panic on 1st malloc Message-ID: <1FDDB298-04ED-4633-89E3-29809FD743D0@bsdimp.com> In-Reply-To: <5BE690EF-486A-482F-A275-35B07D92113E@gmail.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> <20130418180818.1d036620@bender> <5BE690EF-486A-482F-A275-35B07D92113E@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 18, 2013, at 2:33 AM, Damjan Marion wrote: >=20 > On Apr 18, 2013, at 10:08 AM, Andrew Turner <andrew@fubar.geek.nz> = wrote: >=20 >> On Wed, 17 Apr 2013 22:36:29 -0600 >> Warner Losh <imp@bsdimp.com> wrote: >>=20 >>>=20 >>> On Apr 17, 2013, at 7:36 PM, Andrew Turner wrote: >>>=20 >>>> On Wed, 17 Apr 2013 09:37:26 -0600 >>>> Warner Losh <imp@bsdimp.com> wrote: >>>>=20 >>>>> 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. >>>>=20 >>>> 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. >>>=20 >>> If I take WITNESS out of the kernel, I have no issues either. Not >>> sure what WITNESS' problem is... >>=20 >> 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. >>=20 >> I have set unmapped_buf_allowed =3D 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. >=20 > Just tried clang + unmapped_buf_allowed=3D0: >=20 > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, = 1994 > The Regents of the University of California. All rights = reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-CURRENT #0 r+b594eb9-dirty: Thu Apr 18 09:29:34 CEST 2013 > dmarion@vm-freebsd-head:/tmp/WANDBOARD arm > FreeBSD clang version 3.3 (trunk 178860) 20130405 > WARNING: WITNESS option enabled, expect reduced performance. > panic: acquiring blockable sleep lock with spinlock or critical = section held (rw) pmap pv global @ /usr/src/sys/arm/arm/pmap-v6.c:1187 > KDB: enter: panic That's where it panics for me, but tr in ddb fails to give any = meaningful stack traceback. Turning off witness gets me to the = mountroot> prompt.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1FDDB298-04ED-4633-89E3-29809FD743D0>