[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] mcheck_mca_logout() panic insight


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Dan Peterson <dpiddy@xxxxxxxxx>
  • Date: Thu, 21 Jan 2010 00:12:26 -0400
  • Delivery-date: Wed, 20 Jan 2010 20:13:01 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oyJAhWIZohoxjGDX0SAv13smYee0+kbng1Nn2KoDF6s28XWjW0EjMEGPjGzw/YtdRg yWNROK0UJ5BJcUXG6WSTdU9mOJtiJLeD6CfSrjHg0I9sgOU07H3Jke9pNkcxDA2nIYNN kv148iAUNg0FmFdAIgB3i98isdsCdIoJNBuMk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

I seem to have run into this bug:

http://article.gmane.org/gmane.comp.emulators.xen.devel/71342

Have a machine that was running 3.4.1, booted it several times with no
trouble and it was running for 41+ days. Then it panic'd like in the
above message and hung. On subsequent reboots it panic'd the same way,
I'm pretty sure, before even doing the free RAM scrub. After upgrading
it to 3.4.2 it booted fine and seems to be ok.

I've searched for insight as to what triggers this bug but I haven't
found any. Any tips? Is it it time-based somehow? For machines running
3.4.1 is there some way I can predict when/if it will strike?

Thanks!
-Dan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.