From: Dan Gora <dan.gora@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Panic on boot on Sun Blade 6270
Date: Tue, 16 Mar 2010 08:48:45 -0300 [thread overview]
Message-ID: <4779de451003160448m6fe61237l1de1deb550520244@mail.gmail.com> (raw)
In-Reply-To: <4B9F68B2020000780003519B@vpn.id2.novell.com>
On Tue, Mar 16, 2010 at 7:17 AM, Jan Beulich <JBeulich@novell.com> wrote:
> So are you saying even plain SLE11 doesn't work on that box?
No, I'm not saying that.. SLES 11 + Xen 3.3.1 "works" (yes I have a
problem with it, but I'm still trying to figure it out). In trying to
figure out my other problem I wanted to upgrade Xen to something later
but was not having any luck building and installing Xen from the hg
repo. So I went to download.suse.com and downloaded the Xen 3.4.1
SRPMS, used rpmbuild to build the RPMS, installed those and that
panics on boot. I could not install the 4.0.0 RPMs because there were
conflicts with the required prerequisites and what I already
installed, so I gave up.
> If so, why didn't you report this to our support folks yet?
I haven't reported the 3.4.1 crash just because:
1) I just found it a couple of days ago.
2) I don't have a support contract.
3) I'm really busy trying to solve the issue with my board.
>
> As said above - it's supposed to work (both with the 3.3.1 that SLE11
> ships with [or really, with the most recent maintenance updates in
> place for both kernel and Xen] and upstream versions down to 3.2.0).
> The only limitation I know about for certain (Sun?) systems is that
> not all interrupts may be usable by their devices/drivers. That
> limitation goes away only with 4.0 (i.e. earlier upstream versions
> won't - afaict - get you anywhere either if this is the case).
So we should be able use 4.0 on SLES 11 somehow? How can I install a
newer Xen on this system. The only way that I can get anything to
work that I compile from source is using the Xen 3.3.1 SRPM and using
rpmbuild to build the RPMs from that. With that I can also modify the
3.3.1 Xen a bit to add printfs and the like to actually debug the
problem with my board (although that process is a total pain).
Is it possible to build something from the hg Xen repo and install it
on the SLES 11 system and have it work? There seem to be a lot of
suse specific patches in the SRPMs, but I haven't gone through them to
see what they are all about...
thanks
dan
next prev parent reply other threads:[~2010-03-16 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 21:40 Panic on boot on Sun Blade 6270 Dan Gora
2010-03-11 21:55 ` Dan Gora
2010-03-12 1:35 ` Jiang, Yunhong
2010-03-12 4:01 ` Dan Gora
2010-03-12 6:20 ` Jiang, Yunhong
2010-03-12 13:37 ` Dan Gora
2010-03-12 7:13 ` Keir Fraser
2010-03-12 13:37 ` Dan Gora
2010-03-12 13:43 ` Dan Gora
2010-03-12 16:44 ` Pasi Kärkkäinen
2010-03-12 17:37 ` Dan Gora
2010-03-15 9:21 ` Jan Beulich
2010-03-16 2:39 ` Dan Gora
2010-03-16 10:17 ` Jan Beulich
2010-03-16 11:48 ` Dan Gora [this message]
2010-03-16 12:56 ` Jan Beulich
2010-03-12 17:21 ` Dan Gora
2010-03-11 22:42 ` Keir Fraser
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=4779de451003160448m6fe61237l1de1deb550520244@mail.gmail.com \
--to=dan.gora@gmail.com \
--cc=JBeulich@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).