From owner-freebsd-current Fri Sep 15 15:08:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA10503 for current-outgoing; Fri, 15 Sep 1995 15:08:24 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA10488 for ; Fri, 15 Sep 1995 15:08:13 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id PAA02087; Fri, 15 Sep 1995 15:06:58 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id PAA02115; Fri, 15 Sep 1995 15:09:15 -0700 Message-Id: <199509152209.PAA02115@corbin.Root.COM> To: Paul Traina 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 95 14:23:56 PDT." <199509152123.OAA05181@precipice.shockwave.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 15 Sep 1995 15:08:58 -0700 Sender: owner-current@freebsd.org Precedence: bulk >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 actually quite rare. -DG