WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Reboot weirdness

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Reboot weirdness
From: Paul Dorman <pauld@xxxxxxxxx>
Date: Wed, 22 Sep 2004 10:51:28 +1200
Delivery-date: Tue, 21 Sep 2004 23:56:10 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.7
Hi all,

well, as determined yesterday my spontaneous reboot problem, which was 
occuring after a pause at the "Sep 22 09:02:25 Xen1 kernel: e1000: eth0: 
e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex" point has nothing to do 
with the e100 network problem.

After taking out the console=ttyS0 line, I see that things get further. 
Looking at my syslog reveals little about what's actually going wrong 
however. Here's the output:

Sep 22 09:02:27 Xen1 rpc.statd[1350]: Version 1.0.6 Starting
Sep 22 09:02:27 Xen1 rpc.statd[1350]: statd running as root. chown
/var/lib/nfs/sm to choose different user
Sep 22 09:02:28 Xen1 ntpd[1379]: ntpd 4.2.0a@1:4.2.0a-11-r Tue Jul 27
04:55:54 CEST 2004 (1)
Sep 22 09:02:28 Xen1 ntpd[1379]: precision = 1.000 usec
Sep 22 09:02:28 Xen1 ntpd[1379]: Listening on interface wildcard, 0.0.0.0#123
Sep 22 09:02:28 Xen1 ntpd[1379]: Listening on interface eth0, 10.10.10.242#123
Sep 22 09:02:28 Xen1 ntpd[1379]: Listening on interface lo, 127.0.0.1#123
Sep 22 09:02:28 Xen1 ntpd[1379]: kernel time sync status 0040
Sep 22 09:02:28 Xen1 /usr/sbin/cron[1407]: (CRON) INFO (pidfile fd = 3)
Sep 22 09:02:28 Xen1 /usr/sbin/cron[1412]: (CRON) STARTUP (fork ok)
Sep 22 09:02:28 Xen1 /usr/sbin/cron[1412]: (CRON) INFO (Running @reboot jobs)

I'm going to try deactivating ntpd for a start. Does anyone have a clue as to 
what is going on here?

Cheers for your help,
Paul.


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Reboot weirdness, Paul Dorman <=