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] system lockup

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] system lockup
From: Mike Waychison <Michael.Waychison@xxxxxxx>
Date: Fri, 13 Aug 2004 18:53:10 -0400
Delivery-date: Fri, 13 Aug 2004 23:56:20 +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: Mozilla Thunderbird 0.5 (X11/20040208)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,


I've recently managed to get a 2.6.7 dom0 to boot without any major
problems.  I had seen the hwclock issues and the nosegfixup issues fly
by and these seem to be all worked out now.


Another issue though is still lingering for me, and I'm a little
clueless as to how to go about debugging it.


It seems that once I log into my gnome session, everything is aok for
the first little while, until eventually I get a segfault pop-up for
wnck-applet.  I've never seen this segfault before, and am not sure if
it is xen or 2.6.7 related (I'm still running a 2.6.1 variant).
However, a few seconds later, whether or not I click the 'ok' in the
segfault dialog, the machine seems to lock hard.


I've tested this w/ & w/o both a) removing the /lib/tls directory and b)
the nosegfixup kernel option.


Has anyone else seen this?  or possibly know of any other cause for this?

I will try updating to vanilla 2.6.7 tonight to see the issue remains.




Also:


A while ago, I tried building the xenolinux-2.6.7-dom0 kernel with a
pentium II cpu target.  The system appeared to boot up properly, however
X couldn't start as there seemed to be a mysterious SIGBUS being sent.
For now, I'm using a PIV build on this PII..


Thanks,

- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBHUZVdQs4kOxk3/MRAgDsAJ421NUq5IUMdmNKNTvoqsWz1TqeeQCeOU66
A5S+sHksUBrbjtBH2nTlFNk=
=mA/7
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>