From: Andy Smith <andy@strugglers.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: "lshw" seems to get stuck at the "DMI" stage with 4.x
Date: Mon, 15 Aug 2011 02:09:39 +0000 [thread overview]
Message-ID: <20110815020939.GV19219@bitfolk.com> (raw)
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
next reply other threads:[~2011-08-15 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 2:09 Andy Smith [this message]
2011-08-15 7:32 ` "lshw" seems to get stuck at the "DMI" stage with 4.x Jan Beulich
2011-08-15 9:47 ` Ian Campbell
2011-08-15 15:29 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110815020939.GV19219@bitfolk.com \
--to=andy@strugglers.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.