From: Kip Macy <kmacy@fsmware.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: DEBUG output starving network requests
Date: Sun, 22 Feb 2004 14:02:55 -0800 (PST) [thread overview]
Message-ID: <20040222135845.K84871@demos.bsdclusters.com> (raw)
In-Reply-To: <E1Av1IY-0007Jf-00@wisbech.cl.cam.ac.uk>
I moved to a machine at work which is hooked up to a portmaster - so I
can get the debug output through a serial line. I'm testing out starting
up a domain with 12MB and I've been seeing the following for several
minutes:
file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128be: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128bf: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c0: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c1: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c2: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c3: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c4: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c5: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c6: ed=fc664be0,sd=fc1
(file=/u/kmacy/xen/xeno-unstable.bk/xen/include/xeno/mm.h, line=166) Error pfn 000128c7: ed=fc664be0,sd=fc1
Keir has told me that this is harmless. I don't know if there is any
way around it, but while this is going on I'm not able to talk to the
machine over the network.
-Kip
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-22 22:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 20:46 dumping a domain's core Kip Macy
2004-02-22 21:02 ` Ian Pratt
2004-02-22 21:17 ` Kip Macy
2004-02-22 21:38 ` Ian Pratt
2004-02-22 22:02 ` Kip Macy [this message]
2004-02-22 22:23 ` DEBUG output starving network requests Keir Fraser
2004-02-22 23:35 ` problems with recursively mapping page directory as a page table Kip Macy
2004-02-23 13:15 ` Christian Limpach
2004-02-23 21:02 ` refcount errors then crash on XenoLinux with the latest source Kip Macy
2004-02-23 21:36 ` Kip Macy
2004-02-23 23:35 ` Keir Fraser
2004-02-24 1:11 ` Kip Macy
2004-02-24 3:44 ` Kip Macy
2004-02-24 8:15 ` Ian Pratt
2004-02-24 8:35 ` Keir Fraser
2004-02-24 17:21 ` Kip Macy
2004-02-24 17:45 ` Ian Pratt
2004-02-24 8:40 ` Keir Fraser
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=20040222135845.K84871@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.