All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel@lists.xensource.com
Subject: changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console
Date: Sat, 24 Sep 2005 10:42:37 -0400	[thread overview]
Message-ID: <1127572957.3612.135.camel@pluto.linsolutions.com> (raw)

With changset 7048:c89485e939cc I have two FC4 domU,s that generates
these messages on startup.

(XEN) DOM11: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM11: (file=mm.c, line=461) Non-privileged attempt to map I/O
space 00000000

Happens every time I start an FC4 domU, not seeing this with Centos 4.1,
debian 3.1 or gentoo-2005 domu's.

Also seeing some strange behavior with the bridge setups as well.
Had one instance where network layer was toast, and llc was half
working. Also the bridge interfaces are not being cleaned up, if a domU
fails (sporadically seeing this) and I issue an xm destroy the bridge
interface for that domU is left behind.

My xen console also vanished, when I first connected I hit "h" and
output was humming along, then it just stopped. Still not sure if I am
using it properly. Is their some disable key stroke?


Also saw the OUCH timer gripe, but only a few entries.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=257


Question?
Is it better for me to reboot and startup clean after I see this types
of issues, or keep things running and test more.

Regards,
Ted

             reply	other threads:[~2005-09-24 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-24 14:42 Ted Kaczmarek [this message]
2005-09-24 16:25 ` changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console Keir Fraser
2005-09-24 17:12   ` Ted Kaczmarek

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=1127572957.3612.135.camel@pluto.linsolutions.com \
    --to=tedkaz@optonline.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.