From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andy Smith <andy@strugglers.net>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: "lshw" seems to get stuck at the "DMI" stage with 4.x
Date: Mon, 15 Aug 2011 11:29:50 -0400 [thread overview]
Message-ID: <20110815152950.GA22941@dumpdata.com> (raw)
In-Reply-To: <20110815020939.GV19219@bitfolk.com>
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
prev parent reply other threads:[~2011-08-15 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 2:09 "lshw" seems to get stuck at the "DMI" stage with 4.x Andy Smith
2011-08-15 7:32 ` Jan Beulich
2011-08-15 9:47 ` Ian Campbell
2011-08-15 15:29 ` Konrad Rzeszutek Wilk [this message]
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=20110815152950.GA22941@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=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.