From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 2 Nov 2012 09:04:42 -0400 To: 9fans@hamnavoe.com, 9fans@9fans.net Message-ID: <68a12d8f9eb13a850dde26a81a18c77d@brasstown.quanstro.net> In-Reply-To: <9c7307771640a386781142bab8d23a66@hamnavoe.com> References: <9c7307771640a386781142bab8d23a66@hamnavoe.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Kernel panic when compiling Go on native Plan 9 Topicbox-Message-UUID: cfbaca70-ead7-11e9-9d60-3106f5b1d025 On Fri Nov 2 08:00:29 EDT 2012, 9fans@hamnavoe.com wrote: > Are you running a recent (since 24 August) kernel on a multiprocessor? > > If so, try booting with *nomp=1 in plan9.ini and see if running on > just one cpu prevents the panic. > > I've just updated my kernel, and I'm getting a panic on opening > a particular email message in acme. Just debugging it now. what change do you see as problematic? i know it's typical for us to run with multi-gigabyte processes. so assuming that the op has got a couple of gigs of memory and there is no dastardly swap configured, it would be either (a) something in the sources kernel has introduced a panic (b) or something in go is tickling an existing panic. but the changes i see all look to be corner cases, or startup code which would fail on boot. i'm missing what change could have introduced this. i'd guess an old bug. - erik