From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, stefan.kuhne@gmx.net
Cc: mark.hurenkamp@xs4all.nl
Subject: Re: Please test xen/stable-2.6.32.x in xen.git
Date: Wed, 7 Apr 2010 20:30:34 -0400 [thread overview]
Message-ID: <20100408003034.GA11193@phenom.dumpdata.com> (raw)
In-Reply-To: <4BB4FA2D.7020902@access.denied>
On Thu, Apr 01, 2010 at 09:55:25PM +0200, Stefan Kuhne wrote:
> Am 01.04.2010 21:06, schrieb Jeremy Fitzhardinge:
>
> Hello Jeremy,
>
> > Is irq 18 being shared with your wlan device? Is it USB which stops
> > working after this message, or does it take the whole machine out? Does
> > it work if you disable USB (unload the module, or boot with nousb)?
> >
> yes, WLAN has IRQ18 to.
> Dom0 Kernel has no module for it ;).
>
> All hangs. Even "CTRL + ALT + DEL" doesn't work.
> I can test it later or tomorrow (MEST).
>
Can you send me following siz things so I can have an idea what is at
miss:
1). lspci -vvv output in Dom0
2). lspci -vvv output in DomU
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"
4). your console log of DomU. This is usually the output from 'xm
console <your guest>'
5). cat /proc/interrupts in Dom0
6). cat /proc/interrupts in DomU
Thanks.
next prev parent reply other threads:[~2010-04-08 0:30 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 ` Konrad Rzeszutek Wilk [this message]
[not found] ` <4BBD9DC7.603@access.denied>
2010-04-08 14:59 ` Please test xen/stable-2.6.32.x in xen.git Konrad Rzeszutek Wilk
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=20100408003034.GA11193@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=mark.hurenkamp@xs4all.nl \
--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).