From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Larson <pl@us.ibm.com>
Subject: Re: kernel BUG at mm/rmap.c:555!
Date: Wed, 08 Feb 2006 14:54:08 -0600
Message-ID: <43EA5A70.3090902@us.ibm.com>
References: <20060205041922.BE8A7143D@huxley.watson.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20060205041922.BE8A7143D@huxley.watson.ibm.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Leendert van Doorn <leendert@watson.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Leendert van Doorn wrote:
> I noticed that when you kill xenstored in xen-unstable.hg 8758, it will
> take down all of domain 0. Killing xenstored is probably not the smartest
> thing to do, but it shouldn't take down dom0.
Killing it manually probably isn't typical, but it certainly get's 
killed and triggers this bug at shutdown/reboot.

As of yesterday, changeset 8777:581d4a0ac729, this bug is still there.  
It's in bugzilla as bug #520: 
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=520


Thanks,
Paul Larson