On Fri Nov 2 08:00:29 EDT 2012, 9f...@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
