WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: L1[0x1fb] = 0000000000000000 which faults on one type of

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, <gianni.tedesco@xxxxxxxxxx>, <andrew.thomas@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Wed, 16 Mar 2011 22:32:16 +0000
Cc: swente@xxxxxxxxxxxxx
Delivery-date: Wed, 16 Mar 2011 15:34:25 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=f08VEs3b15H1/j7dQ3jXrlZJEj6yOOwZdX7d5gyBBmw=; b=Ag7O11PcppINX2abY3zIxhMoeogOq9MEf0+hXAWY7CBIHzO0PzxRfk7ctmtmNE6aCo zGND1tRT2jX2LRybw5ar1KGne7XkeLvS17u1M7vhRwXTud5xeCfaHGGAtGXlEe5XQIGf Yy/X8jMpxdpNHWY7ARMMNPeyNa1cgENQnTu9k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=HCJS6eNlb2JMGF+67ircMw7CTuo3y/5tsPUfGBHZf6dHGPQyD7JNCNGS+ZucEdLipa 6qE9GiY2gehiuOwCiffLCvyE+RlSu/tV2ESfjo4kUUy8+bfN2Gbc5Cl6jTnV7Nk0gMXT uEuYgntl+7roYzq1ogqtASWkf2Y/kFbDeVlqs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110316221912.GA13035@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcvkKgCZVD0AK3YV8EmNXB5pzPcmoA==
Thread-topic: L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
User-agent: Microsoft-Entourage/12.28.0.101117
On 16/03/2011 22:19, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

> OK, so I've come up a fix that is a back-port of how 2.6.38 does it
> which is that it removes the check I mentioned above and in xen_set_fixmap
> we set the FIX_APIC_BASE to actually point to a dummy ioapic_mapping.
> It is 7cb068cf1ba90425e12f3a7b3caed9d018fa9b8c in for-2.6.32/bug-fixes
> 
> Gianni, you might want to check this out in case it fixes the problem you
> are experiencing.
> 
> But one thing I can't understand is why on one machine (IBM x3850)
> I get this crash, while another one with the same pagetable contents
> (L1 has nothing for 0x1fb) it works just fine? I added a panic and used
> the Xen hypervisor kdb to manually inspect the pagetable, and it has
> the same contents as the IBM x3850 -but it boots fine with this invalid value.
> Any ideas?

Could the native_apic_read() come from ACPI DSDT of that particular machine
type (x3850)?

 K.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel