From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony Wright <anthony@overnetdata.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: dmidecode doesn't work under xen 4.1.1 on certain hardware
Date: Mon, 10 Oct 2011 12:15:22 -0400 [thread overview]
Message-ID: <20111010161522.GD28646@phenom.oracle.com> (raw)
In-Reply-To: <4E930E71.7000306@overnetdata.com>
On Mon, Oct 10, 2011 at 04:25:37PM +0100, Anthony Wright wrote:
> On 06/10/2011 17:07, Konrad Rzeszutek Wilk wrote:
> >>> If you feel adventours you could use the oss.oracle.com/git/kwilk/xen.git
> >>> tree. Mainly the #linux-next or #testing branch. They both have David's new
> >>> e820 code.
> >>>
> >>> The way to get it is:
> >>>
> >>> git clone oss.oracle.com/git/kwilk/xen.git
> >>> cd xen
> >>> git checkout origin/linux-next
> >>> make -j90
> >> Sorry it panicked :-(
> >> I've attached two photos of the two flavours of panic & a copy of the
> >> config.
> > No serial console? Did it panic when you booted as baremetal?
> Sorry - no serial console - I hadn't really intended to become part
> kernel hacker!! We're looking for leads to see if we can set it up, but
> I'm going to have to look through the attic into some old dusty boxes...
Heheh.
>
> It runs through fine on bare metal.
Ok, this was the #linux-next branch right? If you did:
git checkout v3.1-rc8
and built that kernel does it work? (Trying to figure out if the patches
in #linux-next are the cause of your failure).
>
> >> It seems to get through the initial kernel boot and hands over to my
> >> init script, but panics early on in that process, probably at the point
> >> that udev is loading modules.
> > Looks completly unrelated to the dmidecode issue. Lets attack one thing
> > at a time.
> >
> > Can you move the ioatdma.ko as .bak so it wont load and try again.
> I moved the ioatdma.ko module out of the way, but I'm still getting the
> panics in my init script as udev registers the devices. It's the same
> panic as I attached a photo of in the previous email (the one with
> xen_force_evtchk_callback & do_coprocessor_segment_overrun in the call
> stack).
Oh, I somehow missed the do_coprocessor_segment_overrun. That looks to
be something entirely new or perhaps: http://bugs.debian.org/642154
Hm, let me take a look at the photos once more.
next prev parent reply other threads:[~2011-10-10 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 11:22 dmidecode doesn't work under xen 4.1.1 on certain hardware Anthony Wright
2011-09-23 13:32 ` Konrad Rzeszutek Wilk
2011-09-23 14:49 ` Anthony Wright
2011-09-26 14:13 ` Konrad Rzeszutek Wilk
2011-09-26 14:48 ` Anthony Wright
2011-09-26 19:37 ` Konrad Rzeszutek Wilk
2011-09-28 9:08 ` Anthony Wright
2011-09-28 13:28 ` Konrad Rzeszutek Wilk
2011-09-28 16:07 ` Anthony Wright
2011-09-28 16:32 ` Konrad Rzeszutek Wilk
2011-09-28 17:02 ` David Vrabel
2011-10-04 12:19 ` Anthony Wright
2011-10-05 15:16 ` Konrad Rzeszutek Wilk
2011-10-06 12:53 ` Anthony Wright
2011-10-06 16:07 ` Konrad Rzeszutek Wilk
2011-10-10 15:25 ` Anthony Wright
2011-10-10 16:15 ` Konrad Rzeszutek Wilk [this message]
2011-10-10 16:18 ` Konrad Rzeszutek Wilk
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=20111010161522.GD28646@phenom.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=anthony@overnetdata.com \
--cc=david.vrabel@citrix.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.