From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: system lockup
Date: Fri, 13 Aug 2004 19:59:36 -0400 [thread overview]
Message-ID: <411D55E8.5070809@sun.com> (raw)
In-Reply-To: <E1BvlO9-0006uP-00@mta1.cl.cam.ac.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian Pratt wrote:
>>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.
>
>
> That's good to hear.
>
>
>>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.
>
>
> Is this all in domain 0 or another domain?
This is all dom0. I haven't had the chance to load up any other domains
yet. My main concern at this point is getting my hardware working :)
>
> Can it be repeated with 2.4, or will your filesystem not boot
> with a 2.4 kernel? (BTW: what file system are you using?)
>
>
>>I've tested this w/ & w/o both a) removing the /lib/tls directory and b)
>>the nosegfixup kernel option.
>
>
> It's useful to know its not a tls issue.
>
>
>>Has anyone else seen this? or possibly know of any other cause for this?
>
>
> Could you hook up a serial console to the machine? If you start
> Xen with the appropriate (e.g. 'com1=115200,8n1') option there's
> a fair chance that either Xen or more likely, domain 0, will
> write some sort of crash message to the console when the machine
> locks. A 'debug=y' build of Xen might help.
I'll hopefully be able to try something eventually. I just moved, so at
this point I'm living out of cardboard boxes 8)
Out of curiosity, is there any way to get the Xen console/crash dumps on
the console (as opposed to serial)?
>
>
>>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..
>
>
> That's very weird. The other way around I could sort of
> understand...
Ah, I just checked my latest build, and it is in fact a PII build. I
saw this issue a couple days ago: I may have had an inconsistent build.
Sorry for the noise :)
- --
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)
iD8DBQFBHVXodQs4kOxk3/MRAu8aAJ0Z5/QGwq2smkZ7dUAO+GJEFpfLqACeOINe
fqiUr1AYwVmCxRfE+XxryMU=
=oQpz
-----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
next prev parent reply other threads:[~2004-08-13 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 22:53 system lockup Mike Waychison
2004-08-13 23:23 ` Ian Pratt
2004-08-13 23:59 ` Mike Waychison [this message]
2004-08-14 0:20 ` Ian Pratt
2004-08-14 8:32 ` Keir Fraser
2004-08-16 13:59 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2007-02-27 1:20 Roman Mashak
2002-10-21 0:02 System lockup Bill Leckey
2002-10-21 11:30 ` Alan Cox
2002-10-21 21:44 ` Bill Leckey
2002-10-27 22:26 ` Bill Leckey
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=411D55E8.5070809@sun.com \
--to=michael.waychison@sun.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--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.