From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefan Kuhne <stefan.kuhne@gmx.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: Please test xen/stable-2.6.32.x in xen.git
Date: Thu, 8 Apr 2010 10:59:23 -0400 [thread overview]
Message-ID: <20100408145923.GA10345@phenom.dumpdata.com> (raw)
In-Reply-To: <4BBD9DC7.603@access.denied>
> > 3). serial log of your Dom0 with debug options cranked up: Xen command
> > line requires you to have 'loglvl=all' and the Linux line to have
> > 'debug'. For details look in http://wiki.xensource.com/xenwiki/XenParavirtOps
> > in the section titled "Are there more debugging options I could enable
> > to troubleshoot booting problems"
>
> These option are running, but I've no serial port.
Looking at the files I am under the impression that your Dom0 is a
pretty recent one, say 2.6.31. There was a missing patch that did not
share IRQs in that tree that got added.. on 2010-02-19:
commit 733bcb9a1a2d8dba3a4ef3edc3bc009f56251404
Merge: be30a4f 7ec723a
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Date: Fri Feb 19 14:18:19 2010 -0800
Merge branch 'xen/pcifront' into xen/master
* xen/pcifront:
xen-pci: Take advantage of the shared IRQ flags.
xen/apic: fix shared irq device passthrough
I am curious whether you have that or not?
If you see that, then you are set on your Dom0 side.
Your DomU kernel is a mystery to me. From your [4] it looks as
an old PCI front driver, say 2.6.27 or 2.6.18 type. I've looked briefly
at fli4l-3.5.0-rev18309 web-site and the kernels I found there had no
Xen support. So.. what kernel is this?
It is paramount for the Dom0 and DomU to both have the patches for
shared IRQ to work properly. At some point the Dom0 code paths had it,
but not the DomUs. Nowadays, all of the Jeremy's xen trees should have
it: xen/stable-2.6.31.x , xen/stable-2.6.32.x and xen/next.
>
> > 4). your console log of DomU. This is usually the output from 'xm
> > console <your guest>'
>
> [3].
>
> > 5). cat /proc/interrupts in Dom0
>
> [4].
>
> > 6). cat /proc/interrupts in DomU
>
> [5].
>
> Regards,
> Stefan Kuhne
>
> --
> [1]: http://skweb.buetow.org/Linux/EisXen/xen-4.0.0/lspci-dom0.txt
> [2]: http://skweb.buetow.org/Linux/EisXen/xen-4.0.0/lspci-domU.txt
> [3]: http://skweb.buetow.org/Linux/EisXen/xen-4.0.0/starting-domU.txt
> [4]: http://skweb.buetow.org/Linux/EisXen/xen-4.0.0/interrupts-dom0.txt
> [5]: http://skweb.buetow.org/Linux/EisXen/xen-4.0.0/interrupts-domU.txt
>
next prev parent reply other threads:[~2010-04-08 14:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 17:58 Please test xen/stable-2.6.32.x in xen.git Jeremy Fitzhardinge
2010-03-31 18:14 ` Stefan Kuhne
2010-03-31 19:06 ` Jeremy Fitzhardinge
2010-03-31 20:26 ` Stefan Kuhne
2010-03-31 20:31 ` Jeremy Fitzhardinge
2010-04-01 7:38 ` Stefan Kuhne
2010-04-01 17:55 ` Martinx - ジェームズ
2010-04-01 19:35 ` Jeremy Fitzhardinge
2010-04-01 20:29 ` Martinx - ジェームズ
2010-04-01 20:06 ` Konrad Rzeszutek Wilk
2010-04-01 19:06 ` Jeremy Fitzhardinge
2010-04-01 19:55 ` Stefan Kuhne
2010-04-01 20:08 ` Jeremy Fitzhardinge
2010-04-01 21:04 ` Stefan Kuhne
2010-04-01 21:49 ` Jeremy Fitzhardinge
2010-04-01 21:54 ` Stefan Kuhne
2010-04-01 22:02 ` Jeremy Fitzhardinge
2010-04-01 22:08 ` Stefan Kuhne
2010-04-02 10:51 ` Pasi Kärkkäinen
2010-04-03 14:10 ` X-Server doesn't start under Xen 4.0-rc9 & 2.6.31.11 pvops on top of F12 Boris Derzhavets
2010-04-06 18:30 ` Jeremy Fitzhardinge
2010-04-06 21:37 ` Boris Derzhavets
2010-04-06 22:01 ` Jeremy Fitzhardinge
2010-04-06 22:40 ` Mark Hurenkamp
2010-04-06 22:41 ` Jeremy Fitzhardinge
2010-04-06 23:08 ` Mark Hurenkamp
2010-04-07 11:30 ` Boris Derzhavets
2010-04-07 16:20 ` Boris Derzhavets
2010-04-06 22:38 ` Mark Hurenkamp
2010-04-06 22:40 ` Jeremy Fitzhardinge
2010-04-02 13:11 ` Bugs in 2.6.31.12-pvops Carsten Schiers
2010-04-02 18:11 ` Jeremy Fitzhardinge
2010-04-08 0:30 ` Please test xen/stable-2.6.32.x in xen.git Konrad Rzeszutek Wilk
[not found] ` <4BBD9DC7.603@access.denied>
2010-04-08 14:59 ` Konrad Rzeszutek Wilk [this message]
2010-03-31 18:45 ` Pasi Kärkkäinen
2010-03-31 20:10 ` Olivier B.
2010-03-31 20:32 ` Olivier B.
2010-03-31 20:35 ` Jeremy Fitzhardinge
2010-03-31 20:43 ` Olivier B.
2010-04-05 16:53 ` Guillaume Rousse
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=20100408145923.GA10345@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=stefan.kuhne@gmx.net \
--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).