From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: "lshw" seems to get stuck at the "DMI" stage with 4.x Date: Mon, 15 Aug 2011 11:29:50 -0400 Message-ID: <20110815152950.GA22941@dumpdata.com> References: <20110815020939.GV19219@bitfolk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110815020939.GV19219@bitfolk.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: Andy Smith Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Mon, Aug 15, 2011 at 02:09:39AM +0000, Andy Smith wrote: > Hello, > > I just noticed that the "lshw" command gets stuck at the "DMI" stage > for me on all (three of) my Xen 4.x installs. Meanwhile the Xen > dmesg is filling with: > > (XEN) mm.c:860:d0 Error getting mfn 1592 (pfn 601f) from L1 entry 8000000001592625 for l1e_owner=0, pg_owner=32753 > (XEN) mm.c:860:d0 Error getting mfn 1592 (pfn 601f) from L1 entry 8000000001592625 for l1e_owner=0, pg_owner=32753 > > until I ctrl-c the lshw. Hm, so I ran this on 3.0 (Ubuntu 11.04) with Xen 4.1.1 and it ran fine for me. Can you try that kernel instead (just use the stock 3.0 kernel from ftp.kernel.org) and see if you get the same problem? > > Searching for this I found this thread: > > http://lists.xensource.com/archives/html/xen-devel/2010-10/msg00257.html > > although that is discussing a boot failure (crash) which I am not > experiencing. Alan does mention having to patch lshw to have it > complete the DMI probe. > > lshw works fine on my Xen 3.x installs. > > Does this mean the bug is in lshw, or in Xen? I would think Dom0, but we can narrow that down if you run with 3.0 (which works for me) and see how that fares. > > Cheers, > Andy > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel