From owner-freebsd-current Fri Sep 15 16:08:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13602 for current-outgoing; Fri, 15 Sep 1995 16:08:47 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13594 for ; Fri, 15 Sep 1995 16:08:45 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id QAA06428; Fri, 15 Sep 1995 16:06:26 -0700 Message-Id: <199509152306.QAA06428@precipice.shockwave.com> To: davidg@Root.COM cc: "Jonathan M. Bresler" , Andreas Klemm , current@freebsd.org Subject: Re: Which SUP files are available and where ? In-reply-to: Your message of "Fri, 15 Sep 1995 15:08:58 PDT." <199509152209.PAA02115@corbin.Root.COM> Date: Fri, 15 Sep 1995 16:06:25 -0700 From: Paul Traina Sender: owner-current@freebsd.org Precedence: bulk Thanks for the update, ok, then one of my machines is going to switch over to -stable. Paul From: David Greenman Subject: Re: Which SUP files are available and where ? >I thought a couple of people were reporting sig 11 problems on -stable. >Is it true that there are NO sig 11 problems that we're aware of? There are no known reliability problems with -stable. All of the people that I'm aware of that reported (any sort of) problems have since figured out what was causing them and have fixed them. There was one bug which Rod found that was causing a "CMAP busy" panic, but this isn't a new problem and has been with us since last year. It is caused by an attempt to read from /dev/kmem in an area that has no currently mapped page. This results in a page fault and subsequantly messed up 'CMAP' page table entry. The problem will normally only be seen when you have an out of date /var/db/kvm_kernel.foo.db file. It only happens at boot time and it's actuall >>y quite rare. -DG