From: Yasir Assam <mail@endlessvoid.com>
To: xen-devel@lists.xensource.com
Subject: 4.0.0 rc2: possible bugs
Date: Tue, 02 Feb 2010 22:12:21 +1100 [thread overview]
Message-ID: <4B680895.4000203@endlessvoid.com> (raw)
I built rc2 and used the pvops kernel pulled from git for dom0 (make
linux-2.6-pvops-build).
dom0 runs much slower than the the vanilla kernel (without xen), and the
system as a whole, including the domUs I'm running, seems sluggish.
More of a concern is that I'm getting random segfaults in the domUs. I
have 2 domUs running: one using the 2.6.18-xen (built for 3.4.2), and
another using kernel.org 2.6.32.7. I can't be sure it's not a hardware
problem (as I've also upgraded my MB) but both the RAM (tested with
Memtest86) and the HD (tested with the WD diagnostic tool) seem ok.
Here's a sample of the domU segfaults (I can't reproduce them - they're
random):
gnome-panel[3232]: segfault at 7f5264a27390 ip 00007f5263a8205d sp
00007fff74ce9630 error 4 in libc-2.10.2.so[7f5263a11000+14a000]
sshd[6373]: segfault at 000000ffadffd8ff rip 000000ffadffd8ff rsp
00007fffb61abab8 error 14
At one point I was using the dom0 kernel for one of the domUs and that
crashed a few times, so I switched to kernel.org's 2.6.32.7
The domU using 2.6.18-xen has always been rock-solid before under 3.4.2
and earlier (it uses Debian Stable).
Let me know if you want log/config files.
Thanks,
Yasir
next reply other threads:[~2010-02-02 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 11:12 Yasir Assam [this message]
2010-02-02 16:47 ` 4.0.0 rc2: possible bugs Pasi Kärkkäinen
2010-02-02 22:41 ` Yasir Assam
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=4B680895.4000203@endlessvoid.com \
--to=mail@endlessvoid.com \
--cc=xen-devel@lists.xensource.com \
/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.