Date: Fri, 15 Mar 1996 15:28:19 -0500 (EST) From: "matthew c. mead" <mmead@Glock.COM> To: coredump@nervosa.com (invalid opcode) Cc: sos@FreeBSD.ORG, toor@dyson.iquest.net, current@FreeBSD.ORG Subject: Re: -current and accelx Message-ID: <199603152028.PAA03709@neon.Glock.COM> In-Reply-To: <Pine.BSF.3.91.960315122038.356A-100000@onyx.nervosa.com> from "invalid opcode" at Mar 15, 96 12:21:42 pm
index | next in thread | previous in thread | raw e-mail
invalid opcode writes: > On Fri, 15 Mar 1996 sos@FreeBSD.ORG wrote: > > In reply to John S. Dyson who wrote: > > > > > > Info, info, info :-). Jordan wants to cut a new snap soon, and I want > > > to fix the problems for him ASAP. Anything that you tell me about the hang > > Ok, so I did a simple test, and found out that its the change in > > vm_mmap.c (1.38->1.39) that makes life miserable for me and my accelx > > server... > > Hope that helps you John.... > > For others, just retrive the 1.38 version of vm_mmap.c and you're > > back in business... > > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > I second that. I got the 1.38 version, and I'm now writing this from > within X. No problems at all. All in all, -current is pretty stable for me. Hmm, it's been stable for me too (the reason that I installed it is that I got a JAZ drive today and I'm told that only the drivers in -current make it sleep and wake properly (I was running 2.1.0R)). How can I retrieve the 1.38 version? I have no freebsd.org account (unless someone wants to give me one... :-) -matt -- Matthew C. Mead mmead@Glock.COM http://www.Glock.COM/~mmead/help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603152028.PAA03709>