Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422681AbVLOJ75 (ORCPT ); Thu, 15 Dec 2005 04:59:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422676AbVLOJ75 (ORCPT ); Thu, 15 Dec 2005 04:59:57 -0500 Received: from ns.suse.de ([195.135.220.2]:64909 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1422681AbVLOJ7z (ORCPT ); Thu, 15 Dec 2005 04:59:55 -0500 Date: Thu, 15 Dec 2005 10:59:49 +0100 From: Andi Kleen To: Hugh Dickins Cc: Andi Kleen , Dave , linux-kernel@vger.kernel.org Subject: Re: x86_64 segfault error codes Message-ID: <20051215095949.GZ23384@wotan.suse.de> References: <8746466a0512141017j141d61dft3dd2b1ab95dc2351@mail.gmail.com> <8746466a0512141124u68c3f5c9o3411c8af64667d8d@mail.gmail.com> <20051214195848.GQ23384@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1096 Lines: 26 On Thu, Dec 15, 2005 at 09:55:40AM +0000, Hugh Dickins wrote: > On Wed, 14 Dec 2005, Andi Kleen wrote: > > > > Don't know what kernel you're looking at, but 2.6.15rc5 has > > > > * bit 0 == 0 means no page found, 1 means protection fault > > * bit 1 == 0 means read, 1 means write > > * bit 2 == 0 means kernel, 1 means user-mode > > * bit 3 == 1 means use of reserved bit detected > > * bit 4 == 1 means fault was an instruction fetch > > I can't see it there in 2.6.15-rc5 or 2.6.15-rc5-git; but it is there > in 2.6.15-rc5-mm3: which seems to contains a lot of x86_64 patches, > perhaps some of which you're expecting already to be in 2.6.15? Yah it's only in the 2.6.16 queue. Sorry for the confusion. Anyways nobody should rely on these comments. If you want the details look at the architecture manuals. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/