From: Kip Macy <kip.macy@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: periodic DOM0 reboot before getting prompt
Date: Thu, 10 Mar 2005 20:39:18 -0800 [thread overview]
Message-ID: <b1fa29170503102039f9fe954@mail.gmail.com> (raw)
about half the time DOM0 reboots itself before getting to the prompt
(if it makes it to the prompt it is reasonably stable)
This is running with ChangeSet 1.1306
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
smpint3: 0000 [#1]
_sPREEMPTend SMP
_stModuleop s linked in:
disabCPU: 1
le_local_APIC
EIP: 0061:[<c04cec1d>] Not tainted VLI
(XEN) EFLDomain 0 shutdown: rebooting machine.AGS: 00001246 (2.6.10-xen0)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
reply other threads:[~2005-03-11 4:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b1fa29170503102039f9fe954@mail.gmail.com \
--to=kip.macy@gmail.com \
--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.