From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: eDP screen corruption using linux 3.8 & xen 4.2 Date: Tue, 5 Mar 2013 13:35:12 -0500 Message-ID: <20130305183512.GA27621@phenom.dumpdata.com> References: <20130305160113.GE15431@phenom.dumpdata.com> <51362E9202000078000C3455@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <51362E9202000078000C3455@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel , Ben Guthro , fengzhe.zhang@intel.com List-Id: xen-devel@lists.xenproject.org On Tue, Mar 05, 2013 at 04:42:42PM +0000, Jan Beulich wrote: > >>> On 05.03.13 at 17:33, Ben Guthro wrote: > > I turned up the debug, but didn't see this > > I am seeing other oops messages in the log now though...not sure if these > > are related. > > The first one likely is related (rax being 000000aa000000aa and > apparently used as memory address, and that value very much > looks like 2 pixels from a 32-bit pixel map). So I'd guess that > there's once again some physical/machine address mixup. Good spotting! Ben I think the i915 driver is innocent this time.