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: Megaraid SAS driver failing in Xen-3.3.0 but was working

To: "Kumar, Venkat" <Venkat.Kumar@xxxxxxx>
Subject: [Xen-devel] RE: Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Thu, 18 Sep 2008 14:32:22 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, espen.skoglund@xxxxxxxxxxxxx, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Delivery-date: Wed, 17 Sep 2008 23:33:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <532F993CC2E6654CADFE057ADC6C2FA31BA6462F4A@xxxxxxxxxxxxxxxxx>
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>
References: <0122C7C995D32147B66BF4F440D3016301BB7329@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <532F993CC2E6654CADFE057ADC6C2FA31BA6462F4A@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckYwjv7U27GYrVeR5i5APC3TzxQsgAdBWvQAASfLhAAAmmnQA==
Thread-topic: Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
per this log, we can see the context mapping is not created for 02:0e.0.
 
I checked the code, I suspect context mapping() for PCI device is incorrect (see case DEV_TYPE_PCI block code in domain_context_mapping()). Obviously the PCI device is not mapped. Espen changed this code in c/s 17972. Espen, can you give some explanation?
 
Venkat, pls try attached patch. and pls post your "lspci -v" output.
 
Randy (Weidong)


From: Kumar, Venkat [mailto:Venkat.Kumar@xxxxxxx]
Sent: 2008年9月18日 12:45
To: Han, Weidong
Cc: Cui, Dexuan; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3

 

Hi Randy,

 

I am attaching the complete output in a file.

 

But for your reference, a part of it I am pasting in the body.

==================================================================================

(XEN) PCI add device 02:0e.0

(XEN) [VT-D]iommu.c:775: iommu_page_fault: iommu->reg = ffff828bfff55000

(XEN) [VT-D]iommu.c:744: iommu_fault_status: Fault Overflow

(XEN) [VT-D]iommu.c:729: iommu_fault:DMA Write: 2:e.0 addr cddf2000 REASON 2 iommu->reg = ffff828bfff55000

(XEN) print_vtd_entries: iommu = ffff8300cde0db00 bdf = 2:e:0 gmfn = cddf2

(XEN)     root_entry = ffff83012bfe5000

(XEN)     root_entry[2] = 12779e001

(XEN)     context = ffff83012779e000

(XEN)     context[70] = 0_0

(XEN)     ctxt_entry[70] not present

(XEN) PCI add device 00:1b.0

(XEN) PCI remove device 02:0e.0

==================================================================================

 

02:0e.0 is the pci id of Megaraid SAS controller.

For some reason you can see that the device is removed.

I guess this output would give you some idea.

 

 

Thx,

Venkat


From: Han, Weidong [mailto:weidong.han@xxxxxxxxx]
Sent: Thursday, September 18, 2008 8:01 AM
To: Kumar, Venkat; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Cui, Dexuan
Subject: RE: Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3

 

Venkat,

 

Can you post the serial console output?

 

Randy (Weidong)

 


From: Kumar, Venkat [mailto:Venkat.Kumar@xxxxxxx]
Sent: 2008
917 20:38
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Han, Weidong; Cui, Dexuan
Subject: Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled.

It fails at the point of initializing firmware.

 

I wasn’t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working.

 

Looks like a degrade problem.

 

Any clues?

Thx,

Venkat

 

Attachment: nested.patch
Description: nested.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>