From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Smith Subject: "lshw" seems to get stuck at the "DMI" stage with 4.x Date: Mon, 15 Aug 2011 02:09:39 +0000 Message-ID: <20110815020939.GV19219@bitfolk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org 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. 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? Cheers, Andy