From owner-freebsd-hackers Thu Mar 4 12:42:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D7F014F21 for ; Thu, 4 Mar 1999 12:42:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31909; Thu, 4 Mar 1999 12:42:39 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 12:42:39 -0800 (PST) From: Matthew Dillon Message-Id: <199903042042.MAA31909@apollo.backplane.com> To: Ulf Zimmermann Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> <199903042027.MAA31748@apollo.backplane.com> <19990304123311.C3659@TelcoSucks.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> A backtrace from the core dump would be useful. It's hard to tell :> what the cause of the crash is - it could be the BT848, it could the :> SBPRO. It could be something else. You might have to mess around :> disabling various bits to figure out the cause. : :Crashes have been occuring at all different times. X11 running, no X11 running. :X11 with with fxtv or without. I can give you the ssh root login to access :the /var/crash. : :Regards, Ulf. :Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Well, I don't quite have enough time to get knee deep into a crash dump. I can suggest a few things. You could try moving to -current. The VM group is in the midst of comitting a bunch of bug fixes into -current ( current == -4.x ) but, more importantly, there are bug fixes already in -current which have not yet been backported to -3.x. If your crashing problem does not occur under 4.x, there's a good chance that it will be fixed in -3.x in the next week or so as the fixes are backported. If the crash still occurs under -4.x, we know there's still a problem somewhere. Also, a large number of changes have been made to BT driver even since the 3.1 release. It might be beneficial to upgrade to the latest -stable ( i.e. -3.x ) first, and if that does not clear up the problem to try -current ( i.e. -4.x ). There are no guarentees with any of these, unfortunately. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message