Date: Sat, 14 Jan 2006 07:48:36 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Miroslaw Mieszczak <mirek@mieszczak.com.pl>, linux-kernel@vger.kernel.org,
       Zwane Mwaikambo <zwane@arm.linux.org.uk>,
       "Seth, Rohit" <rohit.seth@intel.com>
Subject: Re: [2.6] Problem with PDC20265 on system with I865 chipset and PIV HT
Message-ID: <20060114064836.GB9699@elte.hu>
References: <43C6DA9D.4060300@mieszczak.com.pl> <20060113001618.66821fcb.akpm@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060113001618.66821fcb.akpm@osdl.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 715
Lines: 24


* Andrew Morton <akpm@osdl.org> wrote:

> That's oopsing when trying to write to the APIC:
> 
> 	apic_write_around(APIC_EOI, 0);
> 
> <cc's x86 people>
> 
> Is there any sane way in which APIC accesses can fault, or does this 
> indicate bad hardware?

no - the local APIC in that context is like ordinary memory. If there's  
fault, it must be the pagetables.

perhaps the "data corruption and system crash" mentioned in the report 
corrupted kernel pagetables?

	Ingo
-
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/