Yu, Ping Y
2005-Aug-16 02:38 UTC
[Xen-devel]service OS could not reboot or halt in latest xen-unstable
Hi, folks, I found that the latest xen-unstable could not reboot or halt. Here are detailed info. Could anybody take a look at this issue? I installed the latest xen-unstable 6179. When I typeed "halt -p" in service OS, I found that the machine hanged after the following output: INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal INIT: Sending processes the KILL signal Stopping cups-config-daemon: [ OK ] Stopping HAL daemon: [ OK ] Stopping system message bus: [ OK ] Stopping atd: [ OK ] Stopping cups: [ OK ] Shutting down xfs: [ OK ] Stopping Canna server: [ OK ] Shutting down console mouse services: [ OK ] Stopping sshd:[ OK ] Shutting down sendmail: [ OK ] Shutting down sm-client: [ OK ] Stopping vncserver: [ OK ] Shutting down smartd: Then I have to shut down the host manually. After reboot again, I typed "reboot" in service OS. Service OS hanged again. INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signal INIT: Sending processes the KILL signal Stopping cups-config-daemon: [ OK ] Stopping HAL daemon: [ OK ] Stopping system message bus: [ OK ] Stopping atd: [ OK ] Stopping cups: [ OK ] Shutting down xfs: [ OK ] Stopping Canna server: [ OK ] Shutting down console mouse services: [ OK ] Stopping sshd:[ OK ] Shutting down sendmail: [ OK ] Shutting down sm-client: [ OK ] Stopping vncserver: [ OK ] Shutting down smartd: Sincerely Yours Yu Ping _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Pratt
2005-Aug-16 06:55 UTC
RE: [Xen-devel]service OS could not reboot or halt in latest xen-unstable
> I found that the latest xen-unstable could not reboot or > halt. Here are detailed > > info. Could anybody take a look at this issue? > > > > I installed the latest xen-unstable 6179. When I typeed "halt > -p" in serviceDo you know when it last worked for you? Is this in dom0 or domU? Please can you enable magic sysrq and try sending a sysrq ''t''. Thanks, Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel