From: Matt Ayres <matta@tektonic.net>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: Re: [Xen-users] xen 3.0 Test CD v1 released
Date: Sun, 27 Nov 2005 15:35:34 -0500 [thread overview]
Message-ID: <438A1896.90503@tektonic.net> (raw)
In-Reply-To: <7a6ac9a5a944921f7929f84abb3651ff@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 25 Nov 2005, at 17:33, Matt Ayres wrote:
>
>> Can you comment if the bugs I've reported in bugzilla #'s 402, 405,
>> and 406 have been fixed/assigned? I tried to change a few of our
>> (unixshell.com) users over to a 3.0 server and it turned out poorly.
>> We have serial console (with logging) setup for our servers so when a
>> system panics or sends an oops so I am more than capable of capturing
>> it submitting bugs for any troubles, but I received those different 3
>> panics and the system couldn't stay up for more than a few hours (I
>> had even tried turning off PAE and SMP support). This was all using
>> snapshots from around 11/13. I know there have been many, many
>> commits since then.
>
> 402 and 405 are the same bug. Can you really repro it with a non-PAE
> kernel? It looks related to using swiotlb to access memory >4GB.
>
I should have documented this better, I believe due to the panics in
402/405 I switched to non-PAE, non-SMP dom0 and domU kernels and then
produced 406.
> If you can repro 406 with a debug build of Xen (debug=y make) then the
> backtrace will make much more sense.
>
I can try to do this. Of course I can't guarantee to get the panic, but
if I get do see anything I'll make sure the kernels are built with
debugging enabled.
next prev parent reply other threads:[~2005-11-27 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 14:18 xen 3.0 Test CD v1 released Ian Pratt
2005-11-25 17:33 ` [Xen-users] " Matt Ayres
2005-11-25 17:39 ` Keir Fraser
2005-11-27 20:35 ` Matt Ayres [this message]
2005-11-28 16:54 ` Fraser Campbell
2005-11-30 11:51 ` Chris Bainbridge
2005-11-30 18:32 ` Joe Ammond
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=438A1896.90503@tektonic.net \
--to=matta@tektonic.net \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.