From owner-freebsd-alpha Fri Oct 16 00:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24955 for freebsd-alpha-outgoing; Fri, 16 Oct 1998 00:33:27 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from diablo.OntheNet.com.au (diablo.OntheNet.com.au [203.10.89.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24949 for ; Fri, 16 Oct 1998 00:33:22 -0700 (PDT) (envelope-from tonyg@OntheNet.com.au) Received: from OntheNet.com.au (swanee.nt.com.au [203.14.201.3]) by diablo.OntheNet.com.au (8.9.1/8.9.1) with ESMTP id RAA14452 for ; Fri, 16 Oct 1998 17:33:01 +1000 (EST) Message-ID: <3626F657.8B1DA535@OntheNet.com.au> Date: Fri, 16 Oct 1998 17:31:35 +1000 From: Tony Griffiths Reply-To: tonyg@OntheNet.com.au Organization: On the Net (ISP on the Gold Coast, Australia) X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.ORG Subject: Re: kernel panic() on unaligned memory access... References: <199810160644.OAA16113@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Wemm wrote: > > Mike Smith wrote: > [..] > > > In my opinion, it's not only bad, but _irresponsible_ to let the > > > system bumble on in the face of such a bug. High uptime is nice, but > > > if it comes at the cost of ignoring serious system errors or > > > corrupting data, it's worthless. > > > > I don't think anyone would disagree with you here. However an unaligned > > access doesn't fit into this case, as you can handle it cleanly (while > > tagging the problem as an error) without crying wolf. Which is why I said in a previous response that a panic() should be conditionally taken based on a sysctl variable. For debugging purposes in -alpha/beta/v1.0 releases, a little more toleration of "non-fatal" errors should be acceptable! The sysctl flag still gives a developer the option of dumping if they really want one to track down why the unaligned access is occurring while at the same time giving everyone else a few less headaches trying to track down someone elses stuffup... At some release after the first when most code paths have been thoroughly exercised, the default can be changed from doing a fixup+printf to panicing. Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message