From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Xu Subject: Re[3]: vcpu-pin cause dom0 kernel panic Date: Mon, 30 May 2011 09:12:16 +0800 Message-ID: <20110530091216.E863.3A8D29D5@cloudex.cn> References: <20110524140150.GE10926@dumpdata.com> <20110527173823.68CA.3A8D29D5@cloudex.cn> Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20110527173823.68CA.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: Konrad Rzeszutek Wilk , xen-devel@lists.xensource.com, yunhong.jiang@intel.com List-Id: xen-devel@lists.xenproject.org The panic reason of pin-1-core-dom0 is DMA-remapping error. 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 ... /* * 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 enabl= e 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: > 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] fault= 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 gmfn = =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-i= n-Linux-2-6-32-x-to-make-it-boot-and-work-with-Dell-LSI-RAID-adapts-td325= 4332.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/megarai= d_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 > ************************************************** > =D0=EC=B0=B2=A3=A8Andrew Xu=A3=A9 > =B2=BF=C3=C5 =A3=BA=D4=C6=BF=EC=CF=DF - =D4=CB=D3=AA=D6=A7=B3=C5=D6=D0= =D0=C4 - =D1=D0=B7=A2=D6=D0=D0=C4 > =CA=D6=BB=FA : 18910391796 > E-mail=A3=BAxu.an@cloudex.cn > =B5=D8=D6=B7 =A3=BA=B1=B1=BE=A9=CA=D0=B3=AF=D1=F4=C7=F8=BE=C6=CF=C9=C7= =C5=B6=AB=C2=B71=BA=C5M5=C2=A5 > ************************************************** >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel ************************************************** =D0=EC=B0=B2=A3=A8Andrew Xu=A3=A9 =B2=BF=C3=C5 =A3=BA=D4=C6=BF=EC=CF=DF - =D4=CB=D3=AA=D6=A7=B3=C5=D6=D0=D0= =C4 - =D1=D0=B7=A2=D6=D0=D0=C4 =CA=D6=BB=FA : 18910391796 E-mail=A3=BAxu.an@cloudex.cn =B5=D8=D6=B7 =A3=BA=B1=B1=BE=A9=CA=D0=B3=AF=D1=F4=C7=F8=BE=C6=CF=C9=C7=C5= =B6=AB=C2=B71=BA=C5M5=C2=A5 **************************************************