From owner-freebsd-current Thu Oct 28 18:51:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 26FB3154E8 for ; Thu, 28 Oct 1999 18:51:20 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40359>; Fri, 29 Oct 1999 11:46:07 +1000 Content-return: prohibited Date: Fri, 29 Oct 1999 11:51:05 +1000 From: Peter Jeremy Subject: Re: odd NFS behaviour with DU 4.F client In-reply-to: <199910290103.SAA13818@apollo.backplane.com> To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct29.114607est.40359@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <14360.50663.727201.679421@grasshopper.cs.duke.edu> <199910282225.PAA12530@apollo.backplane.com> <14360.60247.329457.247327@grasshopper.cs.duke.edu> <199910290103.SAA13818@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Oct-29 11:03:20 +1000, Matthew Dillon wrote: > Unfortunately, we just don't see these sorts > of panics on Intel boxes all that much because IA32 allows misaligned > accesses. This means there are almost certainly alignment bugs in the > code. You can enable user-mode alignment traps on the IA32. Check out EFLAGS bit 18 and the AM bit in CR0 - unfortunately, it doesn't seem to work for ring 0, 1, 2 so you can't find alignment problems in the kernel. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message