From: Keir Fraser Subject: Re: Latest xen-3.4-testing hangs on boot with iommu=1, on a Lenovo T500 Date: Thu, 16 Jul 2009 11:10:00 +0100 Message-ID: References: <8686c3cd0907160303o1ea25b54p5c6fbe1d0f9f3f26@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <8686c3cd0907160303o1ea25b54p5c6fbe1d0f9f3f26@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tom Rotenberg Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Well, I would 'make clean' in the xen/ subdirectory just to be sure at this point. But no, it doesn't really sound like a software issue. Have you trie= d iommu_inclusive_mapping Xen boot parameter? -- Keir On 16/07/2009 11:03, "Tom Rotenberg" wrote: > No... > and i remember that there was a problem of warm boots, so i did a cold > boot. It's really strange, i have no clew about what can cause it... > I did 'make install' on a clean repository. There is no chance it had > any "left-overs", right? >=20 > On Thu, Jul 16, 2009 at 1:00 PM, Keir Fraser w= rote: >> Did you upgrade the BIOS since your last successful test? There have bee= n >> problems which can persist across warm reboots. So did you power cycle >> between tests? >>=20 >> =A0-- Keir >>=20 >> On 16/07/2009 10:54, "Tom Rotenberg" wrote: >>=20 >>> Just bisected the tree, and i found out, that it's not because of Xen, >>> since even 19607 (which worked for me last time) didn't work. I tried >>> to play a little bit with some of the BIOS settings, but it didn't >>> help. >>> It looks like it's some kind of an hardware problem, which causes the >>> whole machine to freeze, when trying to work with the IOMMU. Any >>> suggestions on what to do next? to whom should i send this >>> information? >>>=20 >>> Tom >>>=20 >>> On Thu, Jul 16, 2009 at 11:26 AM, Tom Rotenberg >>> wrote: >>>> It didn't help. >>>> I will bisect the tree to find the problem. >>>>=20 >>>> On Wed, Jul 15, 2009 at 8:11 PM, Keir Fraser >>>> wrote: >>>>> I'd say changesets 19625 and 19632 are most likely suspects. You coul= d try >>>>> reverting those patches, or updating your tree to just before those >>>>> changesets, and see if that helps. >>>>>=20 >>>>> =A0-- Keir >>>>>=20 >>>>> On 15/07/2009 18:03, "Tom Rotenberg" wrote: >>>>>=20 >>>>>> The last version, i have tried and tested (and it worked), was: >>>>>>=20 >>>>>> changeset 19607: 1ac7832a2fcd >>>>>> author: Keir Fraser >>>>>> date: Mon May 18 13:54:48 2009 +0100 >>>>>> files: README >>>>>>=20 >>>>>>=20 >>>>>> On Wed, Jul 15, 2009 at 7:58 PM, Keir Fraser >>>>>> wrote: >>>>>>> On 15/07/2009 17:01, "Tom Rotenberg" wrot= e: >>>>>>>=20 >>>>>>>> I have cloned the latest xen 3,4 testing tree, changeset 19696: >>>>>>>> =A0 =A0 =A0 =A0 22ef8e900a6d (i386: fix handling of Xen entries in final L= 2 >>>>>>>> page >>>>>>>> table), and i have installed it on a Lenovo T500 machine, with VT-= d >>>>>>>> enabled. >>>>>>>=20 >>>>>>> When did it last work with the 3.4 tree? >>>>>>>=20 >>>>>>> =A0-- Keir >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>=20 >>=20 >>=20 >>=20