From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: vcpu-pin cause dom0 kernel panic Date: Tue, 31 May 2011 10:12:49 -0400 Message-ID: <20110531141249.GH14641@dumpdata.com> References: <20110524140150.GE10926@dumpdata.com> <20110527173823.68CA.3A8D29D5@cloudex.cn> <20110530091216.E863.3A8D29D5@cloudex.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110530091216.E863.3A8D29D5@cloudex.cn> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Xu Cc: xen-devel@lists.xensource.com, yunhong.jiang@intel.com List-Id: xen-devel@lists.xenproject.org On Mon, May 30, 2011 at 09:12:16AM +0800, Andrew Xu wrote: > The panic reason of pin-1-core-dom0 is DMA-remapping error. >=20 > Dom0 (pv) does not require VT-d , although it can use. > So, adding "iommu=3Dno-pv,passthrough" to xen bootoption=20 > can avoid this problem, obviously, bug still exist ... Or the firmware on the LSI card is doing something icky.. Is the 3:0.0 your LSI/PERC card? This was not a problem with the 12.10.1.001 firmware right? >=20 > /* > * The 'iommu' parameter enables the IOMMU. Optional comma separated > * value may contain: > * > * off|no|false|disable Disable IOMMU (default) > * pv Enable IOMMU for PV domains > * no-pv Disable IOMMU for PV domains (default) > * force|required Don't boot unless IOMMU is enabled > * workaround_bios_bug Workaround some bios issue to still ena= ble > VT-d, don't guarantee security > * passthrough Enable VT-d DMA passthrough (no DMA > * translation for Dom0) > * no-snoop Disable VT-d Snoop Control > * no-qinval Disable VT-d Queued Invalidation > * no-intremap Disable VT-d Interrupt Remapping > */ > On Fri, 27 May 2011 17:38:23 +0800 > Andrew Xu wrote: >=20 > > I update update RAID firmware from 12.10.1.001 to 12.12.0.048. > > pin-2 dom0 can find disk, > > but, pin-1 dom0 still panic. > > ------------------------------------------------ > > (XEN) [VT-D]iommu.c:821: iommu_fault_status: Primary Pending Fault > > (XEN) [VT-D]iommu.c:796: DMAR:[DMA Read] Request device [03:00.0] fau= lt addr bf173000, iommu reg =3D ffff82c3fff57000 > > (XEN) DMAR:[fault reason 06h] PTE Read access is not set > > (XEN) print_vtd_entries: iommu =3D ffff83103fdf7ea0 bdf =3D 3:0.0 gmf= n =3D bf173 > > (XEN) root_entry =3D ffff83103fd38000 > > (XEN) root_entry[3] =3D 1011b5d001 > > (XEN) context =3D ffff831011b5d000 > > (XEN) context[0] =3D 2_1019da3005 > > (XEN) l4 =3D ffff831019da3000 > > (XEN) l4_index =3D 0 > > (XEN) l4[0] =3D 1019da2003 > > (XEN) l3 =3D ffff831019da2000 > > (XEN) l3_index =3D 2 > > (XEN) l3[2] =3D 101999f003 > > (XEN) l2 =3D ffff83101999f000 > > (XEN) l2_index =3D 1f8 > > (XEN) l2[1f8] =3D 10197a6003 > > (XEN) l1 =3D ffff8310197a6000 > > (XEN) l1_index =3D 173 > > (XEN) l1[173] =3D 0 > > (XEN) l1[173] not present > > ------------------------------------------------- > >=20 > > When I add "loglvl=3Dnone" to xen bootoptions, pin-1 dom0 run OK. > > It is so !!!strange!!! > >=20 > >=20 > > On Tue, 24 May 2011 10:01:50 -0400 > > Konrad Rzeszutek Wilk wrote: > >=20 > > > On Thu, May 19, 2011 at 09:08:24PM +0800, Andrew Xu wrote: > > > > I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on=20 > > >=20 > > > Did you open a Bugzilla with SLES? > > >=20 > > > > Dell R710 with PERC H700 RAID adapter. > > > > --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz > > > > --8 CPU cores. > > > > --Memory 64G > > > > --RAID5 4.5T > > > >=20 > > > > When I dedicated (pin) a CPU core only for dom0 use. > > > > (I specify "dom0_max_vcpus=3D1 dom0_vcpus_pin" options for Xen) > > > > I got dom0 kernel panic error(pin-1-5.30.bmp) > > > >=20 > > > > When I pin 2 core to dom0, the dom0 system can boot up, > > > > but it can't find any disk devices. > > > >=20 > > > > But when I pin 4 core to dom0, it run OK. > > > >=20 > > > > Does anyone can help me, please. > > > >=20 > > > > I have read this mail, and updated my megaraid_sas to version 05.= 30. > > > > http://xen.1045712.n5.nabble.com/HOWTO-Update-megaraid-sas-driver= -in-Linux-2-6-32-x-to-make-it-boot-and-work-with-Dell-LSI-RAID-adapts-td3= 254332.html > > > > Anyone can help me? > > > >=20 > > > > I download megaraid_sas_05.30 driver from LSI web: > > > > http://www.lsi.com/storage_home/products_home/internal_raid/megar= aid_sas/6gb_s_value_line/sas9260-8i/index.html > > >=20 > > >=20 > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xensource.com > > > > http://lists.xensource.com/xen-devel > > >=20 > > >=20 > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xensource.com > > > http://lists.xensource.com/xen-devel > >=20 > > ************************************************** > > =E5=BE=90=E5=AE=89=EF=BC=88Andrew Xu=EF=BC=89 > > =E9=83=A8=E9=97=A8 =EF=BC=9A=E4=BA=91=E5=BF=AB=E7=BA=BF - =E8=BF=90=E8= =90=A5=E6=94=AF=E6=92=91=E4=B8=AD=E5=BF=83 - =E7=A0=94=E5=8F=91=E4=B8=AD=E5= =BF=83 > > =E6=89=8B=E6=9C=BA : 18910391796 > > E-mail=EF=BC=9Axu.an@cloudex.cn > > =E5=9C=B0=E5=9D=80 =EF=BC=9A=E5=8C=97=E4=BA=AC=E5=B8=82=E6=9C=9D=E9=98= =B3=E5=8C=BA=E9=85=92=E4=BB=99=E6=A1=A5=E4=B8=9C=E8=B7=AF1=E5=8F=B7M5=E6=A5= =BC > > ************************************************** > >=20 > >=20 > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel >=20 > ************************************************** > =E5=BE=90=E5=AE=89=EF=BC=88Andrew Xu=EF=BC=89 > =E9=83=A8=E9=97=A8 =EF=BC=9A=E4=BA=91=E5=BF=AB=E7=BA=BF - =E8=BF=90=E8= =90=A5=E6=94=AF=E6=92=91=E4=B8=AD=E5=BF=83 - =E7=A0=94=E5=8F=91=E4=B8=AD=E5= =BF=83 > =E6=89=8B=E6=9C=BA : 18910391796 > E-mail=EF=BC=9Axu.an@cloudex.cn > =E5=9C=B0=E5=9D=80 =EF=BC=9A=E5=8C=97=E4=BA=AC=E5=B8=82=E6=9C=9D=E9=98= =B3=E5=8C=BA=E9=85=92=E4=BB=99=E6=A1=A5=E4=B8=9C=E8=B7=AF1=E5=8F=B7M5=E6=A5= =BC > **************************************************