From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 11:47:54 +0800
Message-ID: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0642646848559356174=="
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============0642646848559356174==
Content-Type: multipart/alternative; boundary=14dae934059548840b04cfea9d57

--14dae934059548840b04cfea9d57
Content-Type: text/plain; charset=ISO-8859-1

Hi developers,
I met some domU issues and the log suggests missing interrupt.
Details from here:
http://www.gossamer-threads.com/lists/xen/users/263938#263938
In summary, this is the suspicious log:

(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3

I've checked the code in question and found that mode 3 is an 'reserved_1'
mode.
I want to trace down the source of this mode setting to root-cause the
issue.
But I'm not an xen developer, and am even a newbie as a xen user.
Could anybody give me instructions about how to enable detailed debug log?
It could be better if I can get advice about experiments to perform /
switches to try out etc.

My SW config:
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
domU: Debian wheezy 3.2.x stock kernel.

Thanks,
Timothy

--14dae934059548840b04cfea9d57
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi developers,<br>I met some domU issues and the log suggests missing inter=
rupt.<br>Details from here: <a href=3D"http://www.gossamer-threads.com/list=
s/xen/users/263938#263938">http://www.gossamer-threads.com/lists/xen/users/=
263938#263938</a><br>
In summary, this is the suspicious log:<br><br>(XEN) vmsi.c:122:d32767 Unsu=
pported delivery mode 3<br><br>I&#39;ve checked the code in question and fo=
und that mode 3 is an &#39;reserved_1&#39; mode.<br>I want to trace down th=
e source of this mode setting to root-cause the issue.<br>
But I&#39;m not an xen developer, and am even a newbie as a xen user. <br>C=
ould anybody give me instructions about how to enable detailed debug log?<b=
r>It could be better if I can get advice about experiments to perform / swi=
tches to try out etc.<br>
<br>My SW config:<br>dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.=
3-4)<br>domU: Debian wheezy 3.2.x stock kernel.<br><br>Thanks,<br>Timothy<b=
r>

--14dae934059548840b04cfea9d57--


--===============0642646848559356174==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============0642646848559356174==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 07:06:24 +0000
Message-ID: <B6C2EB9186482D47BD0C5A9A483456440339D2CD@SHSMSX101.ccr.corp.intel.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4255746506243060713=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Content-Language: en-US
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>
Cc: "Zhang, Xiantao" <xiantao.zhang@intel.com>
List-Id: xen-devel@lists.xenproject.org

--===============4255746506243060713==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_B6C2EB9186482D47BD0C5A9A483456440339D2CDSHSMSX101ccrcor_"

--_000_B6C2EB9186482D47BD0C5A9A483456440339D2CDSHSMSX101ccrcor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Maybe you need to  provide more information about your VGA device,  for exa=
mple,  "lspci -vvv".   In addition,  from your log, seems expansion rom bar=
 is not correctly handled.  You may refer to this wiki page to check whethe=
r something is missed in your side.   http://wiki.xen.org/wiki/Xen_VGA_Pass=
through
Xiantao

From: xen-devel-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.o=
rg] On Behalf Of G.R.
Sent: Monday, December 03, 2012 11:48 AM
To: xen-devel
Subject: [Xen-devel] Issue about domU missing interrupt

Hi developers,
I met some domU issues and the log suggests missing interrupt.
Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#2=
63938
In summary, this is the suspicious log:

(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3

I've checked the code in question and found that mode 3 is an 'reserved_1' =
mode.
I want to trace down the source of this mode setting to root-cause the issu=
e.
But I'm not an xen developer, and am even a newbie as a xen user.
Could anybody give me instructions about how to enable detailed debug log?
It could be better if I can get advice about experiments to perform / switc=
hes to try out etc.

My SW config:
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
domU: Debian wheezy 3.2.x stock kernel.

Thanks,
Timothy

--_000_B6C2EB9186482D47BD0C5A9A483456440339D2CDSHSMSX101ccrcor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Maybe you need to &nbsp;p=
rovide more information about your VGA device,&nbsp; for example,&nbsp; &#8=
220;lspci &#8211;vvv&#8221;. &nbsp;&nbsp;In addition,&nbsp; from your log, =
seems expansion rom bar is not
 correctly handled. &nbsp;You may refer to this wiki page to check whether =
something is missed in your side. &nbsp;&nbsp;<a href=3D"http://wiki.xen.or=
g/wiki/Xen_VGA_Passthrough">http://wiki.xen.org/wiki/Xen_VGA_Passthrough</a=
><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Xiantao<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> xen-deve=
l-bounces@lists.xen.org [mailto:xen-devel-bounces@lists.xen.org]
<b>On Behalf Of </b>G.R.<br>
<b>Sent:</b> Monday, December 03, 2012 11:48 AM<br>
<b>To:</b> xen-devel<br>
<b>Subject:</b> [Xen-devel] Issue about domU missing interrupt<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi developers,<br>
I met some domU issues and the log suggests missing interrupt.<br>
Details from here: <a href=3D"http://www.gossamer-threads.com/lists/xen/use=
rs/263938#263938">
http://www.gossamer-threads.com/lists/xen/users/263938#263938</a><br>
In summary, this is the suspicious log:<br>
<br>
(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
<br>
I've checked the code in question and found that mode 3 is an 'reserved_1' =
mode.<br>
I want to trace down the source of this mode setting to root-cause the issu=
e.<br>
But I'm not an xen developer, and am even a newbie as a xen user. <br>
Could anybody give me instructions about how to enable detailed debug log?<=
br>
It could be better if I can get advice about experiments to perform / switc=
hes to try out etc.<br>
<br>
My SW config:<br>
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)<br>
domU: Debian wheezy 3.2.x stock kernel.<br>
<br>
Thanks,<br>
Timothy<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_B6C2EB9186482D47BD0C5A9A483456440339D2CDSHSMSX101ccrcor_--


--===============4255746506243060713==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============4255746506243060713==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 03 Dec 2012 08:46:26 +0000
Message-ID: <50BC74F202000078000AD2FA@nat28.tlf.novell.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "G.R." <firemeteor@users.sourceforge.net>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 03.12.12 at 04:47, "G.R." <firemeteor@users.sourceforge.net> wrote:
> Hi developers,
> I met some domU issues and the log suggests missing interrupt.
> Details from here:
> http://www.gossamer-threads.com/lists/xen/users/263938#263938 
> In summary, this is the suspicious log:
> 
> (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> 
> I've checked the code in question and found that mode 3 is an 'reserved_1'
> mode.
> I want to trace down the source of this mode setting to root-cause the
> issue.
> But I'm not an xen developer, and am even a newbie as a xen user.
> Could anybody give me instructions about how to enable detailed debug log?
> It could be better if I can get advice about experiments to perform /
> switches to try out etc.

Please check the list archives, this issue was discussed in great
lengths a couple of months ago (and should be fixed in current
trees).

Jan

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mats Petersson <mats.petersson@citrix.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 10:15:08 +0000
Message-ID: <50BC7BAC.8050107@citrix.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On 03/12/12 03:47, G.R. wrote:
> Hi developers,
> I met some domU issues and the log suggests missing interrupt.
> Details from here: 
> http://www.gossamer-threads.com/lists/xen/users/263938#263938
> In summary, this is the suspicious log:
>
> (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>
> I've checked the code in question and found that mode 3 is an 
> 'reserved_1' mode.
> I want to trace down the source of this mode setting to root-cause the 
> issue.
> But I'm not an xen developer, and am even a newbie as a xen user.
> Could anybody give me instructions about how to enable detailed debug log?
> It could be better if I can get advice about experiments to perform / 
> switches to try out etc.
>
> My SW config:
> dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> domU: Debian wheezy 3.2.x stock kernel.
>
> Thanks,
> Timothy
Are you passing hardware (PCI Passthrough) to the HVM guest?
What are the exact messages in the DomU?

--
Mats

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 20:43:00 +0800
Message-ID: <CAKhsbWYh+FPR0rE1LBNVNEanqLKGSD-McCZz-oMRC80yqVk6kQ@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC74F202000078000AD2FA@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4004368494276883589=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <50BC74F202000078000AD2FA@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============4004368494276883589==
Content-Type: multipart/alternative; boundary=14dae9340595e7b08304cff21693

--14dae9340595e7b08304cff21693
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 3, 2012 at 4:46 PM, Jan Beulich <JBeulich@suse.com> wrote:

> >>> On 03.12.12 at 04:47, "G.R." <firemeteor@users.sourceforge.net> wrote:
> > Hi developers,
> > I met some domU issues and the log suggests missing interrupt.
> > Details from here:
> > http://www.gossamer-threads.com/lists/xen/users/263938#263938
> > In summary, this is the suspicious log:
> >
> > (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> >
> > I've checked the code in question and found that mode 3 is an
> 'reserved_1'
> > mode.
> > I want to trace down the source of this mode setting to root-cause the
> > issue.
> > But I'm not an xen developer, and am even a newbie as a xen user.
> > Could anybody give me instructions about how to enable detailed debug
> log?
> > It could be better if I can get advice about experiments to perform /
> > switches to try out etc.
>
> Please check the list archives, this issue was discussed in great
> lengths a couple of months ago (and should be fixed in current
> trees).
>
>
Thanks, I just found the thread you mentioned:
http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.html

I can confirm that the debian version of the xen 4.1.3 still misses this
patch.
Given the fact that xen 4.1.3 releases after the patch, I guess it is only
intended for v4.2.0?

Do you believe this patch should work for v4.1.3 either?
But anyway, I'm going to try my luck later...

Thanks,
Timothy

--14dae9340595e7b08304cff21693
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, Dec 3, 2012 a=
t 4:46 PM, Jan Beulich <span dir=3D"ltr">&lt;<a href=3D"mailto:JBeulich@sus=
e.com" target=3D"_blank">JBeulich@suse.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">
<div class=3D"im">&gt;&gt;&gt; On 03.12.12 at 04:47, &quot;G.R.&quot; &lt;<=
a href=3D"mailto:firemeteor@users.sourceforge.net">firemeteor@users.sourcef=
orge.net</a>&gt; wrote:<br>
&gt; Hi developers,<br>
&gt; I met some domU issues and the log suggests missing interrupt.<br>
&gt; Details from here:<br>
&gt; <a href=3D"http://www.gossamer-threads.com/lists/xen/users/263938#2639=
38" target=3D"_blank">http://www.gossamer-threads.com/lists/xen/users/26393=
8#263938</a><br>
&gt; In summary, this is the suspicious log:<br>
&gt;<br>
&gt; (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
&gt;<br>
&gt; I&#39;ve checked the code in question and found that mode 3 is an &#39=
;reserved_1&#39;<br>
&gt; mode.<br>
&gt; I want to trace down the source of this mode setting to root-cause the=
<br>
&gt; issue.<br>
&gt; But I&#39;m not an xen developer, and am even a newbie as a xen user.<=
br>
&gt; Could anybody give me instructions about how to enable detailed debug =
log?<br>
&gt; It could be better if I can get advice about experiments to perform /<=
br>
&gt; switches to try out etc.<br>
<br>
</div>Please check the list archives, this issue was discussed in great<br>
lengths a couple of months ago (and should be fixed in current<br>
trees).<br>
<br></blockquote><div><br>Thanks, I just found the thread you mentioned:<br=
><a href=3D"http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.h=
tml">http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.html</a>=
<br>
<br>I can confirm that the debian version of the xen 4.1.3 still misses thi=
s patch.<br>Given the fact that xen 4.1.3 releases after the patch, I guess=
 it is only intended for v4.2.0?<br><br>Do you believe this patch should wo=
rk for v4.1.3 either?<br>
But anyway, I&#39;m going to try my luck later... <br><br>Thanks,<br>Timoth=
y</div></div></div>

--14dae9340595e7b08304cff21693--


--===============4004368494276883589==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============4004368494276883589==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 03 Dec 2012 13:06:05 +0000
Message-ID: <50BCB1CD02000078000AD3F7@nat28.tlf.novell.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC74F202000078000AD2FA@nat28.tlf.novell.com>
	<CAKhsbWYh+FPR0rE1LBNVNEanqLKGSD-McCZz-oMRC80yqVk6kQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWYh+FPR0rE1LBNVNEanqLKGSD-McCZz-oMRC80yqVk6kQ@mail.gmail.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "G.R." <firemeteor@users.sourceforge.net>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 03.12.12 at 13:43, "G.R." <firemeteor@users.sourceforge.net> wrote:
> On Mon, Dec 3, 2012 at 4:46 PM, Jan Beulich <JBeulich@suse.com> wrote:
> 
>> >>> On 03.12.12 at 04:47, "G.R." <firemeteor@users.sourceforge.net> wrote:
>> > Hi developers,
>> > I met some domU issues and the log suggests missing interrupt.
>> > Details from here:
>> > http://www.gossamer-threads.com/lists/xen/users/263938#263938 
>> > In summary, this is the suspicious log:
>> >
>> > (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>> >
>> > I've checked the code in question and found that mode 3 is an
>> 'reserved_1'
>> > mode.
>> > I want to trace down the source of this mode setting to root-cause the
>> > issue.
>> > But I'm not an xen developer, and am even a newbie as a xen user.
>> > Could anybody give me instructions about how to enable detailed debug
>> log?
>> > It could be better if I can get advice about experiments to perform /
>> > switches to try out etc.
>>
>> Please check the list archives, this issue was discussed in great
>> lengths a couple of months ago (and should be fixed in current
>> trees).
>>
>>
> Thanks, I just found the thread you mentioned:
> http://lists.xen.org/archives/html/xen-devel/2012-06/msg01909.html 
> 
> I can confirm that the debian version of the xen 4.1.3 still misses this
> patch.
> Given the fact that xen 4.1.3 releases after the patch, I guess it is only
> intended for v4.2.0?
> 
> Do you believe this patch should work for v4.1.3 either?

I don't think to date a backport of it to 4.1.x was requested.

Jan

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 21:06:40 +0800
Message-ID: <CAKhsbWaA5vqWMxr_v4_ADct5WqrCTrRSOAHQjO=dh7M6nLLNrw@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<B6C2EB9186482D47BD0C5A9A483456440339D2CD@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2949336765687338523=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <B6C2EB9186482D47BD0C5A9A483456440339D2CD@SHSMSX101.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============2949336765687338523==
Content-Type: multipart/alternative; boundary=e89a8f5036c8921d1904cff26b69

--e89a8f5036c8921d1904cff26b69
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 3, 2012 at 3:06 PM, Zhang, Xiantao <xiantao.zhang@intel.com>wro=
te:

>  Maybe you need to  provide more information about your VGA device,  for
> example,  =93lspci =96vvv=94.   In addition,  from your log, seems expans=
ion rom
> bar is not correctly handled.  You may refer to this wiki page to check
> whether something is missed in your side.
> http://wiki.xen.org/wiki/Xen_VGA_Passthrough****
>
> Xiantao****
>
> **
>
I'm using the IGD coming with the H77M chipset, here are the lspci -vvv
output from dom0:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd
Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA
controller])
    Subsystem: ASRock Incorporation Device 0162
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort- <TAbor=
t-
<MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 95
    Region 0: Memory at f7800000 (64-bit, non-prefetchable) [size=3D4M]
    Region 2: Memory at e0000000 (64-bit, prefetchable) [size=3D256M]
    Region 4: I/O ports at f000 [size=3D64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=3D1/1 Maskable- 64bit-
        Address: fee00018  Data: 0000
    Capabilities: [d0] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=3D0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst- PME-Enable- DSel=3D0 DScale=3D0 PME-
    Capabilities: [a4] PCI Advanced Features
        AFCap: TP+ FLR+
        AFCtrl: FLR-
        AFStatus: TP-
    Kernel driver in use: i915

And in domU respectively:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd
Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA
controller])
    Subsystem: ASRock Incorporation Device 0162
    Physical Slot: 2
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort- <TAbor=
t-
<MAbort- >SERR- <PERR- INTx+
    Latency: 64
    Interrupt: pin A routed to IRQ 78
    Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=3D4M]
    Region 2: Memory at e0000000 (64-bit, prefetchable) [size=3D256M]
    Region 4: I/O ports at c100 [size=3D64]
    Expansion ROM at <unassigned> [disabled]
    Capabilities: [90] MSI: Enable+ Count=3D1/1 Maskable- 64bit-
        Address: fee33000  Data: 4300
    Capabilities: [d0] Power Management version 2
        Flags: PMEClk- DSI+ D1- D2- AuxCurrent=3D0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst+ PME-Enable- DSel=3D0 DScale=3D0 PME-
    Kernel driver in use: i915

They are pretty much the same from my point of view except for some
interrupt config.
The 'expansion ROM' are disabled in both case.
But what does this mean after all? Could you give a brief intro for my
education?

I did not find anything obvious missing from the wiki page.
I would like to note that I'm using an AsRock H77m-itx board.
Even when the chipset is not formally classified as vt-d capable (yes, I
noticed your email domain),
Intel is still shipping H77 based vt-d capable board (
http://www.intel.com/support/motherboards/desktop/sb/CS-030922.htm).
I guess this should not count as a missing piece, right?

Thanks,
Timothy

>  **
>
> *From:* xen-devel-bounces@lists.xen.org [mailto:
> xen-devel-bounces@lists.xen.org] *On Behalf Of *G.R.
> *Sent:* Monday, December 03, 2012 11:48 AM
> *To:* xen-devel
> *Subject:* [Xen-devel] Issue about domU missing interrupt****
>
> ** **
>
> Hi developers,
> I met some domU issues and the log suggests missing interrupt.
> Details from here:
> http://www.gossamer-threads.com/lists/xen/users/263938#263938
> In summary, this is the suspicious log:
>
> (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>
> I've checked the code in question and found that mode 3 is an 'reserved_1=
'
> mode.
> I want to trace down the source of this mode setting to root-cause the
> issue.
> But I'm not an xen developer, and am even a newbie as a xen user.
> Could anybody give me instructions about how to enable detailed debug log=
?
> It could be better if I can get advice about experiments to perform /
> switches to try out etc.
>
> My SW config:
> dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> domU: Debian wheezy 3.2.x stock kernel.
>
> Thanks,
> Timothy****
>

--e89a8f5036c8921d1904cff26b69
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Dec 3, 20=
12 at 3:06 PM, Zhang, Xiantao <span dir=3D"ltr">&lt;<a href=3D"mailto:xiant=
ao.zhang@intel.com" target=3D"_blank">xiantao.zhang@intel.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D""><span style=3D"font-size:11pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:rgb(31,73,125)">Maybe you need to =A0provide =
more information about your VGA device,=A0 for example,=A0 =93lspci =96vvv=
=94. =A0=A0In addition,=A0 from your log, seems expansion rom bar is not
 correctly handled. =A0You may refer to this wiki page to check whether som=
ething is missed in your side. =A0=A0<a href=3D"http://wiki.xen.org/wiki/Xe=
n_VGA_Passthrough" target=3D"_blank">http://wiki.xen.org/wiki/Xen_VGA_Passt=
hrough</a><u></u><u></u></span></p>

<p class=3D""><span style=3D"font-size:11pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:rgb(31,73,125)">Xiantao<u></u><u></u></span><=
/p>
<p class=3D""><span style=3D"font-size:11pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:rgb(31,73,125)"><u></u></span></p></div></div=
></blockquote><div>I&#39;m using the IGD coming with the H77M chipset, here=
 are the lspci -vvv output from dom0:<br>
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Ge=
n Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])=
<br>=A0=A0=A0 Subsystem: ASRock Incorporation Device 0162<br>=A0=A0=A0 Cont=
rol: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- S=
ERR- FastB2B- DisINTx+<br>
=A0=A0=A0 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dfast &gt;TAbor=
t- &lt;TAbort- &lt;MAbort- &gt;SERR- &lt;PERR- INTx-<br>=A0=A0=A0 Latency: =
0<br>=A0=A0=A0 Interrupt: pin A routed to IRQ 95<br>=A0=A0=A0 Region 0: Mem=
ory at f7800000 (64-bit, non-prefetchable) [size=3D4M]<br>
=A0=A0=A0 Region 2: Memory at e0000000 (64-bit, prefetchable) [size=3D256M]=
<br>=A0=A0=A0 Region 4: I/O ports at f000 [size=3D64]<br>=A0=A0=A0 Expansio=
n ROM at &lt;unassigned&gt; [disabled]<br>=A0=A0=A0 Capabilities: [90] MSI:=
 Enable+ Count=3D1/1 Maskable- 64bit-<br>
=A0=A0=A0 =A0=A0=A0 Address: fee00018=A0 Data: 0000<br>=A0=A0=A0 Capabiliti=
es: [d0] Power Management version 2<br>=A0=A0=A0 =A0=A0=A0 Flags: PMEClk- D=
SI+ D1- D2- AuxCurrent=3D0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)<br>=A0=A0=A0 =
=A0=A0=A0 Status: D0 NoSoftRst- PME-Enable- DSel=3D0 DScale=3D0 PME-<br>
=A0=A0=A0 Capabilities: [a4] PCI Advanced Features<br>=A0=A0=A0 =A0=A0=A0 A=
FCap: TP+ FLR+<br>=A0=A0=A0 =A0=A0=A0 AFCtrl: FLR-<br>=A0=A0=A0 =A0=A0=A0 A=
FStatus: TP-<br>=A0=A0=A0 Kernel driver in use: i915<br><br>And in domU res=
pectively:<br><br>00:02.0 VGA compatible controller: Intel Corporation Xeon=
 E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00=
 [VGA controller])<br>
=A0=A0=A0 Subsystem: ASRock Incorporation Device 0162<br>=A0=A0=A0 Physical=
 Slot: 2<br>=A0=A0=A0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGA=
Snoop- ParErr- Stepping- SERR- FastB2B- DisINTx+<br>=A0=A0=A0 Status: Cap+ =
66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dfast &gt;TAbort- &lt;TAbort- &lt;MAbo=
rt- &gt;SERR- &lt;PERR- INTx+<br>
=A0=A0=A0 Latency: 64<br>=A0=A0=A0 Interrupt: pin A routed to IRQ 78<br>=A0=
=A0=A0 Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=3D4M]<=
br>=A0=A0=A0 Region 2: Memory at e0000000 (64-bit, prefetchable) [size=3D25=
6M]<br>=A0=A0=A0 Region 4: I/O ports at c100 [size=3D64]<br>
=A0=A0=A0 Expansion ROM at &lt;unassigned&gt; [disabled]<br>=A0=A0=A0 Capab=
ilities: [90] MSI: Enable+ Count=3D1/1 Maskable- 64bit-<br>=A0=A0=A0 =A0=A0=
 =A0Address: fee33000=A0 Data: 4300<br>=A0=A0=A0 Capabilities: [d0] Power M=
anagement version 2<br>=A0=A0=A0 =A0=A0 =A0Flags: PMEClk- DSI+ D1- D2- AuxC=
urrent=3D0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)<br>
=A0=A0=A0 =A0=A0 =A0Status: D0 NoSoftRst+ PME-Enable- DSel=3D0 DScale=3D0 P=
ME-<br>=A0=A0=A0 Kernel driver in use: i915<br><br>They are pretty much the=
 same from my point of view except for some interrupt config.<br>The &#39;e=
xpansion ROM&#39; are disabled in both case. <br>
But what does this mean after all? Could you give a brief intro for my educ=
ation?<br><br>I did not find anything obvious missing from the wiki page. <=
br>I would like to note that I&#39;m using an AsRock H77m-itx board.<br>
Even when the chipset is not formally classified as vt-d capable (yes, I no=
ticed your email domain), <br>Intel is still shipping H77 based vt-d capabl=
e board (<a href=3D"http://www.intel.com/support/motherboards/desktop/sb/CS=
-030922.htm">http://www.intel.com/support/motherboards/desktop/sb/CS-030922=
.htm</a>).<br>
I guess this should not count as a missing piece, right?<br><br>Thanks,<br>=
Timothy<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lin=
k=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div><p class=3D""><span style=3D"font-size:11pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:rgb(31,73,125)">=A0<u></u></span></p>
<div style=3D"border-width:medium medium medium 1.5pt;border-style:none non=
e none solid;border-color:-moz-use-text-color -moz-use-text-color -moz-use-=
text-color blue;padding:0in 0in 0in 4pt">
<div>
<div style=3D"border-width:1pt medium medium;border-style:solid none none;b=
order-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;paddin=
g:3pt 0in 0in">
<p class=3D""><b><span style=3D"font-size:10pt;font-family:&quot;Tahoma&quo=
t;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-size:10pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=3D"mailto:xen=
-devel-bounces@lists.xen.org" target=3D"_blank">xen-devel-bounces@lists.xen=
.org</a> [mailto:<a href=3D"mailto:xen-devel-bounces@lists.xen.org" target=
=3D"_blank">xen-devel-bounces@lists.xen.org</a>]
<b>On Behalf Of </b>G.R.<br>
<b>Sent:</b> Monday, December 03, 2012 11:48 AM<br>
<b>To:</b> xen-devel<br>
<b>Subject:</b> [Xen-devel] Issue about domU missing interrupt<u></u><u></u=
></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D""><u></u>=A0<u></u></p>
<p class=3D"">Hi developers,<br>
I met some domU issues and the log suggests missing interrupt.<br>
Details from here: <a href=3D"http://www.gossamer-threads.com/lists/xen/use=
rs/263938#263938" target=3D"_blank">
http://www.gossamer-threads.com/lists/xen/users/263938#263938</a><br>
In summary, this is the suspicious log:<br>
<br>
(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
<br>
I&#39;ve checked the code in question and found that mode 3 is an &#39;rese=
rved_1&#39; mode.<br>
I want to trace down the source of this mode setting to root-cause the issu=
e.<br>
But I&#39;m not an xen developer, and am even a newbie as a xen user. <br>
Could anybody give me instructions about how to enable detailed debug log?<=
br>
It could be better if I can get advice about experiments to perform / switc=
hes to try out etc.<br>
<br>
My SW config:<br>
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)<br>
domU: Debian wheezy 3.2.x stock kernel.<br>
<br>
Thanks,<br>
Timothy<u></u><u></u></p>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--e89a8f5036c8921d1904cff26b69--


--===============2949336765687338523==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============2949336765687338523==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 21:14:55 +0800
Message-ID: <CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2115664862363947947=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <50BC7BAC.8050107@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Mats Petersson <mats.petersson@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============2115664862363947947==
Content-Type: multipart/alternative; boundary=20cf301d42320f0ee104cff28910

--20cf301d42320f0ee104cff28910
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson <mats.petersson@citrix.com>wrote:

> On 03/12/12 03:47, G.R. wrote:
>
>> Hi developers,
>> I met some domU issues and the log suggests missing interrupt.
>> Details from here: http://www.gossamer-threads.**
>> com/lists/xen/users/263938#**263938<http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>> In summary, this is the suspicious log:
>>
>> (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>>
>> I've checked the code in question and found that mode 3 is an
>> 'reserved_1' mode.
>> I want to trace down the source of this mode setting to root-cause the
>> issue.
>> But I'm not an xen developer, and am even a newbie as a xen user.
>> Could anybody give me instructions about how to enable detailed debug log?
>> It could be better if I can get advice about experiments to perform /
>> switches to try out etc.
>>
>> My SW config:
>> dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>> domU: Debian wheezy 3.2.x stock kernel.
>>
>> Thanks,
>> Timothy
>>
> Are you passing hardware (PCI Passthrough) to the HVM guest?
> What are the exact messages in the DomU?
>
>
Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
But this is actually a PVHVM guest since debian stock kernel has PVOP
enabled.
And when I tried another PVOP disabled linux distro (openelec v2.0), I did
not see such msi related error message.
Actually, with that domU I do not see anything obvious wrong from the log,
but I also see nothing from panel (panel receive no signal and go
power-saving) :-(


Back to the issue I was reporting, the domU log looks like this:

Dec 2 21:52:44 debvm kernel: [ 1085.604071] [drm:i915_hangcheck_ring_idle]
*ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
3354], missed IRQ?
Dec 2 21:56:50 debvm kernel: [ 1332.076071] [drm:i915_hangcheck_ring_idle]
*ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
11297], missed IRQ?
Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
timeout, switching to polling mode: last cmd=0x000f0000
Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
codec, disabling MSI: last cmd=0x002f0600
Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
timeout, switching to single_cmd mode: last cmd=0x002f0600


Thanks,
Timothy

--20cf301d42320f0ee104cff28910
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon, Dec 3, 2012 a=
t 6:15 PM, Mats Petersson <span dir=3D"ltr">&lt;<a href=3D"mailto:mats.pete=
rsson@citrix.com" target=3D"_blank">mats.petersson@citrix.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D""><div clas=
s=3D"h5">On 03/12/12 03:47, G.R. wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
Hi developers,<br>
I met some domU issues and the log suggests missing interrupt.<br>
Details from here: <a href=3D"http://www.gossamer-threads.com/lists/xen/use=
rs/263938#263938" target=3D"_blank">http://www.gossamer-threads.<u></u>com/=
lists/xen/users/263938#<u></u>263938</a><br>
In summary, this is the suspicious log:<br>
<br>
(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
<br>
I&#39;ve checked the code in question and found that mode 3 is an &#39;rese=
rved_1&#39; mode.<br>
I want to trace down the source of this mode setting to root-cause the issu=
e.<br>
But I&#39;m not an xen developer, and am even a newbie as a xen user.<br>
Could anybody give me instructions about how to enable detailed debug log?<=
br>
It could be better if I can get advice about experiments to perform / switc=
hes to try out etc.<br>
<br>
My SW config:<br>
dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)<br>
domU: Debian wheezy 3.2.x stock kernel.<br>
<br>
Thanks,<br>
Timothy<br>
</blockquote></div></div>
Are you passing hardware (PCI Passthrough) to the HVM guest?<br>
What are the exact messages in the DomU?<br>
<br></blockquote><br>Yes, I&#39;m doing PCI passthrough (the IGD, audio &am=
p;&amp; USB controller).<br>But this is actually a PVHVM guest since debian=
 stock kernel has PVOP enabled.<br>And when I tried another PVOP disabled l=
inux distro (openelec v2.0), I did not see such msi related error message.<=
br>
Actually, with that domU I do not see anything obvious wrong from the log, =
but I also see nothing from panel (panel receive no signal and go power-sav=
ing) :-(<br><br><br>Back to the issue I was reporting, the domU log looks l=
ike this:<br>
<br><font color=3D"black" face=3D"Verdana,Arial,Helvetica"><font color=3D"b=
lack" face=3D"Verdana,Arial,Helvetica">Dec  2 21:52:44 debvm kernel: [ 1085=
.604071] [drm:i915_hangcheck_ring_idle] <br>*ERROR* Hangcheck timer elapsed=
... blt ring idle [waiting on 3354, at <br>
3354], missed IRQ? <br>Dec  2 21:56:50 debvm kernel: [ 1332.076071] [drm:i9=
15_hangcheck_ring_idle] <br>*ERROR* Hangcheck timer elapsed... render ring =
idle [waiting on 11297, at <br>11297], missed IRQ? <br>Dec  2 22:32:48 debv=
m kernel: [    7.220073] hda-intel: azx_get_response <br>
timeout, switching to polling mode: last cmd=3D0x000f0000 <br>Dec  2 22:45:=
32 debvm kernel: [  776.392084] hda-intel: No response from <br>codec, disa=
bling MSI: last cmd=3D0x002f0600 <br>Dec  2 22:45:33 debvm kernel: [  777.4=
00075] hda_intel: azx_get_response <br>
timeout, switching to single_cmd mode: last cmd=3D0x002f0600 </font></font>=
<br><br><br>Thanks,<br>Timothy<br></div></div>

--20cf301d42320f0ee104cff28910--


--===============2115664862363947947==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============2115664862363947947==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mats Petersson <mats.petersson@citrix.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 13:19:47 +0000
Message-ID: <50BCA6F3.8060804@citrix.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "G.R." <firemeteor@users.sourceforge.net>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On 03/12/12 13:14, G.R. wrote:
> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson 
> <mats.petersson@citrix.com <mailto:mats.petersson@citrix.com>> wrote:
>
>     On 03/12/12 03:47, G.R. wrote:
>
>         Hi developers,
>         I met some domU issues and the log suggests missing interrupt.
>         Details from here:
>         http://www.gossamer-threads.com/lists/xen/users/263938#263938
>         In summary, this is the suspicious log:
>
>         (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>
>         I've checked the code in question and found that mode 3 is an
>         'reserved_1' mode.
>         I want to trace down the source of this mode setting to
>         root-cause the issue.
>         But I'm not an xen developer, and am even a newbie as a xen user.
>         Could anybody give me instructions about how to enable
>         detailed debug log?
>         It could be better if I can get advice about experiments to
>         perform / switches to try out etc.
>
>         My SW config:
>         dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>         domU: Debian wheezy 3.2.x stock kernel.
>
>         Thanks,
>         Timothy
>
>     Are you passing hardware (PCI Passthrough) to the HVM guest?
>     What are the exact messages in the DomU?
>
>
> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
> But this is actually a PVHVM guest since debian stock kernel has PVOP 
> enabled.
> And when I tried another PVOP disabled linux distro (openelec v2.0), I 
> did not see such msi related error message.
> Actually, with that domU I do not see anything obvious wrong from the 
> log, but I also see nothing from panel (panel receive no signal and go 
> power-saving) :-(
>
>
> Back to the issue I was reporting, the domU log looks like this:
>
> Dec 2 21:52:44 debvm kernel: [ 1085.604071] 
> [drm:i915_hangcheck_ring_idle]
> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
> 3354], missed IRQ?
> Dec 2 21:56:50 debvm kernel: [ 1332.076071] 
> [drm:i915_hangcheck_ring_idle]
> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
> 11297], missed IRQ?
> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
> timeout, switching to polling mode: last cmd=0x000f0000
> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
> codec, disabling MSI: last cmd=0x002f0600
> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
> timeout, switching to single_cmd mode: last cmd=0x002f0600
>
>
> Thanks,
> Timothy
It does sound like there is a fix in 4.2.0, as indicated by Jan, that 
fixes this. I'm not fully clued up to what the policy for backporting 
fixes are, and I haven't looked at the complexity of the fix itself, but 
either updating to the 4.2.0 or a (personal) backport sounds like the 
right solution here.

Unfortunately, I hadn't seen Jan's reply by the time I wrote my response 
to your original email.

--
Mats

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mats Petersson <mats.petersson@citrix.com>
Subject: Re: Issue about domU missing interrupt
Date: Mon, 3 Dec 2012 13:58:07 +0000
Message-ID: <50BCAFEF.7040300@citrix.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <50BCA6F3.8060804@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On 03/12/12 13:19, Mats Petersson wrote:
> On 03/12/12 13:14, G.R. wrote:
>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>> <mats.petersson@citrix.com <mailto:mats.petersson@citrix.com>> wrote:
>>
>>      On 03/12/12 03:47, G.R. wrote:
>>
>>          Hi developers,
>>          I met some domU issues and the log suggests missing interrupt.
>>          Details from here:
>>          http://www.gossamer-threads.com/lists/xen/users/263938#263938
>>          In summary, this is the suspicious log:
>>
>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>>
>>          I've checked the code in question and found that mode 3 is an
>>          'reserved_1' mode.
>>          I want to trace down the source of this mode setting to
>>          root-cause the issue.
>>          But I'm not an xen developer, and am even a newbie as a xen user.
>>          Could anybody give me instructions about how to enable
>>          detailed debug log?
>>          It could be better if I can get advice about experiments to
>>          perform / switches to try out etc.
>>
>>          My SW config:
>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>>          domU: Debian wheezy 3.2.x stock kernel.
>>
>>          Thanks,
>>          Timothy
>>
>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>>      What are the exact messages in the DomU?
>>
>>
>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>> enabled.
>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>> did not see such msi related error message.
>> Actually, with that domU I do not see anything obvious wrong from the
>> log, but I also see nothing from panel (panel receive no signal and go
>> power-saving) :-(
>>
>>
>> Back to the issue I was reporting, the domU log looks like this:
>>
>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>> [drm:i915_hangcheck_ring_idle]
>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>> 3354], missed IRQ?
>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>> [drm:i915_hangcheck_ring_idle]
>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>> 11297], missed IRQ?
>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>> timeout, switching to polling mode: last cmd=0x000f0000
>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>> codec, disabling MSI: last cmd=0x002f0600
>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>>
>>
>> Thanks,
>> Timothy
> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
> fixes this. I'm not fully clued up to what the policy for backporting
> fixes are, and I haven't looked at the complexity of the fix itself, but
> either updating to the 4.2.0 or a (personal) backport sounds like the
> right solution here.
I had a quick look, and it doesn't look that hard to backport that patch.

--
Mats
>
> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
> to your original email.
>
> --
> Mats
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Tue, 4 Dec 2012 11:07:23 +0800
Message-ID: <CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6508738499468714629=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <50BCAFEF.7040300@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Mats Petersson <mats.petersson@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============6508738499468714629==
Content-Type: multipart/alternative; boundary=90e6ba6e8e203b79bb04cffe2a08

--90e6ba6e8e203b79bb04cffe2a08
Content-Type: text/plain; charset=ISO-8859-1

> I had a quick look, and it doesn't look that hard to backport that patch.

Thanks, Mat.
I'm glad to report that the patch do fix my problem.

And yest it is really easy to port since the code did not change across the
two release.
The only change would be line numbers (3841 vs 3803) and one extra comments
before this line:

 static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)

I'm not sure if you are going to release another maintenance version that
include this patch,
but I'll report this to Debain maintainer since it's about to freeze for
v7.0 release and v4.2.0 will not make it.



On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson <mats.petersson@citrix.com>wrote:

> On 03/12/12 13:19, Mats Petersson wrote:
>
>> On 03/12/12 13:14, G.R. wrote:
>>
>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>>> <mats.petersson@citrix.com <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>>> wrote:
>>>
>>>      On 03/12/12 03:47, G.R. wrote:
>>>
>>>          Hi developers,
>>>          I met some domU issues and the log suggests missing interrupt.
>>>          Details from here:
>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#**
>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>>>          In summary, this is the suspicious log:
>>>
>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>>>
>>>          I've checked the code in question and found that mode 3 is an
>>>          'reserved_1' mode.
>>>          I want to trace down the source of this mode setting to
>>>          root-cause the issue.
>>>          But I'm not an xen developer, and am even a newbie as a xen
>>> user.
>>>          Could anybody give me instructions about how to enable
>>>          detailed debug log?
>>>          It could be better if I can get advice about experiments to
>>>          perform / switches to try out etc.
>>>
>>>          My SW config:
>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>>>          domU: Debian wheezy 3.2.x stock kernel.
>>>
>>>          Thanks,
>>>          Timothy
>>>
>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>>>      What are the exact messages in the DomU?
>>>
>>>
>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>>> enabled.
>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>>> did not see such msi related error message.
>>> Actually, with that domU I do not see anything obvious wrong from the
>>> log, but I also see nothing from panel (panel receive no signal and go
>>> power-saving) :-(
>>>
>>>
>>> Back to the issue I was reporting, the domU log looks like this:
>>>
>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>>> [drm:i915_hangcheck_ring_idle]
>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>>> 3354], missed IRQ?
>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>>> [drm:i915_hangcheck_ring_idle]
>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>>> 11297], missed IRQ?
>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>>> timeout, switching to polling mode: last cmd=0x000f0000
>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>>> codec, disabling MSI: last cmd=0x002f0600
>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>>>
>>>
>>> Thanks,
>>> Timothy
>>>
>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>> fixes this. I'm not fully clued up to what the policy for backporting
>> fixes are, and I haven't looked at the complexity of the fix itself, but
>> either updating to the 4.2.0 or a (personal) backport sounds like the
>> right solution here.
>>
> I had a quick look, and it doesn't look that hard to backport that patch.
>
> --
> Mats
>
>
>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>> to your original email.
>>
>> --
>> Mats
>>
>> ______________________________**_________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>>
>>
>
> ______________________________**_________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

--90e6ba6e8e203b79bb04cffe2a08
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

&gt; I had a quick look, and it doesn&#39;t look that hard to backport that=
 patch.<br><br>Thanks, Mat.<br>I&#39;m glad to report that the patch do fix=
 my problem.<br><br>And yest it is really easy to port since the code did n=
ot change across the two release.<br>
The only change would be line numbers (3841 vs 3803) and one extra comments=
 before this line:<br><pre> static int pt_msix_update_one(struct pt_dev *de=
v, int entry_nr)</pre>I&#39;m not sure if you are going to release another =
maintenance version that include this patch,<br>
but I&#39;ll report this to Debain maintainer since it&#39;s about to freez=
e for v7.0 release and v4.2.0 will not make it.<br><br><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Mon, Dec 3, 2012 at 9:58 PM, M=
ats Petersson <span dir=3D"ltr">&lt;<a href=3D"mailto:mats.petersson@citrix=
.com" target=3D"_blank">mats.petersson@citrix.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On 0=
3/12/12 13:19, Mats Petersson wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 03/12/12 13:14, G.R. wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson<br>
&lt;<a href=3D"mailto:mats.petersson@citrix.com" target=3D"_blank">mats.pet=
ersson@citrix.com</a> &lt;mailto:<a href=3D"mailto:mats.petersson@citrix.co=
m" target=3D"_blank">mats.petersson@citrix.<u></u>com</a>&gt;&gt; wrote:<br=
>
<br>
=A0 =A0 =A0On 03/12/12 03:47, G.R. wrote:<br>
<br>
=A0 =A0 =A0 =A0 =A0Hi developers,<br>
=A0 =A0 =A0 =A0 =A0I met some domU issues and the log suggests missing inte=
rrupt.<br>
=A0 =A0 =A0 =A0 =A0Details from here:<br>
=A0 =A0 =A0 =A0 =A0<a href=3D"http://www.gossamer-threads.com/lists/xen/use=
rs/263938#263938" target=3D"_blank">http://www.gossamer-threads.<u></u>com/=
lists/xen/users/263938#<u></u>263938</a><br>
=A0 =A0 =A0 =A0 =A0In summary, this is the suspicious log:<br>
<br>
=A0 =A0 =A0 =A0 =A0(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
<br>
=A0 =A0 =A0 =A0 =A0I&#39;ve checked the code in question and found that mod=
e 3 is an<br>
=A0 =A0 =A0 =A0 =A0&#39;reserved_1&#39; mode.<br>
=A0 =A0 =A0 =A0 =A0I want to trace down the source of this mode setting to<=
br>
=A0 =A0 =A0 =A0 =A0root-cause the issue.<br>
=A0 =A0 =A0 =A0 =A0But I&#39;m not an xen developer, and am even a newbie a=
s a xen user.<br>
=A0 =A0 =A0 =A0 =A0Could anybody give me instructions about how to enable<b=
r>
=A0 =A0 =A0 =A0 =A0detailed debug log?<br>
=A0 =A0 =A0 =A0 =A0It could be better if I can get advice about experiments=
 to<br>
=A0 =A0 =A0 =A0 =A0perform / switches to try out etc.<br>
<br>
=A0 =A0 =A0 =A0 =A0My SW config:<br>
=A0 =A0 =A0 =A0 =A0dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-=
4)<br>
=A0 =A0 =A0 =A0 =A0domU: Debian wheezy 3.2.x stock kernel.<br>
<br>
=A0 =A0 =A0 =A0 =A0Thanks,<br>
=A0 =A0 =A0 =A0 =A0Timothy<br>
<br>
=A0 =A0 =A0Are you passing hardware (PCI Passthrough) to the HVM guest?<br>
=A0 =A0 =A0What are the exact messages in the DomU?<br>
<br>
<br>
Yes, I&#39;m doing PCI passthrough (the IGD, audio &amp;&amp; USB controlle=
r).<br>
But this is actually a PVHVM guest since debian stock kernel has PVOP<br>
enabled.<br>
And when I tried another PVOP disabled linux distro (openelec v2.0), I<br>
did not see such msi related error message.<br>
Actually, with that domU I do not see anything obvious wrong from the<br>
log, but I also see nothing from panel (panel receive no signal and go<br>
power-saving) :-(<br>
<br>
<br>
Back to the issue I was reporting, the domU log looks like this:<br>
<br>
Dec 2 21:52:44 debvm kernel: [ 1085.604071]<br>
[drm:i915_hangcheck_ring_idle]<br>
*ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at<br>
3354], missed IRQ?<br>
Dec 2 21:56:50 debvm kernel: [ 1332.076071]<br>
[drm:i915_hangcheck_ring_idle]<br>
*ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at<b=
r>
11297], missed IRQ?<br>
Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response<br>
timeout, switching to polling mode: last cmd=3D0x000f0000<br>
Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from<br>
codec, disabling MSI: last cmd=3D0x002f0600<br>
Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response<br>
timeout, switching to single_cmd mode: last cmd=3D0x002f0600<br>
<br>
<br>
Thanks,<br>
Timothy<br>
</blockquote>
It does sound like there is a fix in 4.2.0, as indicated by Jan, that<br>
fixes this. I&#39;m not fully clued up to what the policy for backporting<b=
r>
fixes are, and I haven&#39;t looked at the complexity of the fix itself, bu=
t<br>
either updating to the 4.2.0 or a (personal) backport sounds like the<br>
right solution here.<br>
</blockquote></div></div>
I had a quick look, and it doesn&#39;t look that hard to backport that patc=
h.<br>
<br>
--<br>
Mats<div class=3D"HOEnZb"><div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Unfortunately, I hadn&#39;t seen Jan&#39;s reply by the time I wrote my res=
ponse<br>
to your original email.<br>
<br>
--<br>
Mats<br>
<br>
______________________________<u></u>_________________<br>
Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org" target=3D"_blank">Xen-devel@list=
s.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
<br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org" target=3D"_blank">Xen-devel@list=
s.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
</div></div></blockquote></div><br></div>

--90e6ba6e8e203b79bb04cffe2a08--


--===============6508738499468714629==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============6508738499468714629==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Tue, 4 Dec 2012 11:12:19 +0800
Message-ID: <CAKhsbWbbLk5m8ubg3jyfMOxGVCxi=iLynv79w-6gPEdHSc_x5w@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2009236113536242055=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Mats Petersson <mats.petersson@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============2009236113536242055==
Content-Type: multipart/alternative; boundary=14dae93411e9e08a6604cffe3b8e

--14dae93411e9e08a6604cffe3b8e
Content-Type: text/plain; charset=ISO-8859-1

PS: I got one more question about the patch:
Will it make any difference for pure HVM guest?
I also observed issues for win 7 (BSOD after intel display driver
installed) and openelec 2.0 ( linux 3.2 based with pvops disabled, panel
report no-signal).
And I haven't got chance to try them out with that patch.


On Tue, Dec 4, 2012 at 11:07 AM, G.R. <firemeteor@users.sourceforge.net>wrote:

> > I had a quick look, and it doesn't look that hard to backport that patch.
>
> Thanks, Mat.
> I'm glad to report that the patch do fix my problem.
>
> And yest it is really easy to port since the code did not change across
> the two release.
> The only change would be line numbers (3841 vs 3803) and one extra
> comments before this line:
>
>  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>
> I'm not sure if you are going to release another maintenance version that
> include this patch,
> but I'll report this to Debain maintainer since it's about to freeze for
> v7.0 release and v4.2.0 will not make it.
>
>
>
>
> On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson <mats.petersson@citrix.com>wrote:
>
>> On 03/12/12 13:19, Mats Petersson wrote:
>>
>>> On 03/12/12 13:14, G.R. wrote:
>>>
>>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>>>> <mats.petersson@citrix.com <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>>>> wrote:
>>>>
>>>>      On 03/12/12 03:47, G.R. wrote:
>>>>
>>>>          Hi developers,
>>>>          I met some domU issues and the log suggests missing interrupt.
>>>>          Details from here:
>>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#**
>>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>>>>          In summary, this is the suspicious log:
>>>>
>>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>>>>
>>>>          I've checked the code in question and found that mode 3 is an
>>>>          'reserved_1' mode.
>>>>          I want to trace down the source of this mode setting to
>>>>          root-cause the issue.
>>>>          But I'm not an xen developer, and am even a newbie as a xen
>>>> user.
>>>>          Could anybody give me instructions about how to enable
>>>>          detailed debug log?
>>>>          It could be better if I can get advice about experiments to
>>>>          perform / switches to try out etc.
>>>>
>>>>          My SW config:
>>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>>>>          domU: Debian wheezy 3.2.x stock kernel.
>>>>
>>>>          Thanks,
>>>>          Timothy
>>>>
>>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>>>>      What are the exact messages in the DomU?
>>>>
>>>>
>>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>>>> enabled.
>>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>>>> did not see such msi related error message.
>>>> Actually, with that domU I do not see anything obvious wrong from the
>>>> log, but I also see nothing from panel (panel receive no signal and go
>>>> power-saving) :-(
>>>>
>>>>
>>>> Back to the issue I was reporting, the domU log looks like this:
>>>>
>>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>>>> [drm:i915_hangcheck_ring_idle]
>>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>>>> 3354], missed IRQ?
>>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>>>> [drm:i915_hangcheck_ring_idle]
>>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297,
>>>> at
>>>> 11297], missed IRQ?
>>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>>>> timeout, switching to polling mode: last cmd=0x000f0000
>>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>>>> codec, disabling MSI: last cmd=0x002f0600
>>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>>>>
>>>>
>>>> Thanks,
>>>> Timothy
>>>>
>>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>>> fixes this. I'm not fully clued up to what the policy for backporting
>>> fixes are, and I haven't looked at the complexity of the fix itself, but
>>> either updating to the 4.2.0 or a (personal) backport sounds like the
>>> right solution here.
>>>
>> I had a quick look, and it doesn't look that hard to backport that patch.
>>
>> --
>> Mats
>>
>>
>>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>>> to your original email.
>>>
>>> --
>>> Mats
>>>
>>> ______________________________**_________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
>>>
>>>
>>>
>>
>> ______________________________**_________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>
>
>

--14dae93411e9e08a6604cffe3b8e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

PS: I got one more question about the patch:<br>Will it make any difference=
 for pure HVM guest?<br>I also observed issues for win 7 (BSOD after intel =
display driver installed) and openelec 2.0 ( linux 3.2 based with pvops dis=
abled, panel report no-signal).<br>
And I haven&#39;t got chance to try them out with that patch.<br><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Dec 4, 2012 at =
11:07 AM, G.R. <span dir=3D"ltr">&lt;<a href=3D"mailto:firemeteor@users.sou=
rceforge.net" target=3D"_blank">firemeteor@users.sourceforge.net</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; I had a quick look, a=
nd it doesn&#39;t look that hard to backport that patch.<br><br></div>Thank=
s, Mat.<br>
I&#39;m glad to report that the patch do fix my problem.<br><br>And yest it=
 is really easy to port since the code did not change across the two releas=
e.<br>
The only change would be line numbers (3841 vs 3803) and one extra comments=
 before this line:<br><pre> static int pt_msix_update_one(struct pt_dev *de=
v, int entry_nr)</pre>I&#39;m not sure if you are going to release another =
maintenance version that include this patch,<br>

but I&#39;ll report this to Debain maintainer since it&#39;s about to freez=
e for v7.0 release and v4.2.0 will not make it.<div class=3D"HOEnZb"><div c=
lass=3D"h5"><br><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_=
quote">
On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mats.petersson@citrix.com" target=3D"_blank">mats.petersson@cit=
rix.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div>On 03/12/12 13:19, Mats Petersson =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 03/12/12 13:14, G.R. wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson<br>
&lt;<a href=3D"mailto:mats.petersson@citrix.com" target=3D"_blank">mats.pet=
ersson@citrix.com</a> &lt;mailto:<a href=3D"mailto:mats.petersson@citrix.co=
m" target=3D"_blank">mats.petersson@citrix.<u></u>com</a>&gt;&gt; wrote:<br=
>
<br>
=A0 =A0 =A0On 03/12/12 03:47, G.R. wrote:<br>
<br>
=A0 =A0 =A0 =A0 =A0Hi developers,<br>
=A0 =A0 =A0 =A0 =A0I met some domU issues and the log suggests missing inte=
rrupt.<br>
=A0 =A0 =A0 =A0 =A0Details from here:<br>
=A0 =A0 =A0 =A0 =A0<a href=3D"http://www.gossamer-threads.com/lists/xen/use=
rs/263938#263938" target=3D"_blank">http://www.gossamer-threads.<u></u>com/=
lists/xen/users/263938#<u></u>263938</a><br>
=A0 =A0 =A0 =A0 =A0In summary, this is the suspicious log:<br>
<br>
=A0 =A0 =A0 =A0 =A0(XEN) vmsi.c:122:d32767 Unsupported delivery mode 3<br>
<br>
=A0 =A0 =A0 =A0 =A0I&#39;ve checked the code in question and found that mod=
e 3 is an<br>
=A0 =A0 =A0 =A0 =A0&#39;reserved_1&#39; mode.<br>
=A0 =A0 =A0 =A0 =A0I want to trace down the source of this mode setting to<=
br>
=A0 =A0 =A0 =A0 =A0root-cause the issue.<br>
=A0 =A0 =A0 =A0 =A0But I&#39;m not an xen developer, and am even a newbie a=
s a xen user.<br>
=A0 =A0 =A0 =A0 =A0Could anybody give me instructions about how to enable<b=
r>
=A0 =A0 =A0 =A0 =A0detailed debug log?<br>
=A0 =A0 =A0 =A0 =A0It could be better if I can get advice about experiments=
 to<br>
=A0 =A0 =A0 =A0 =A0perform / switches to try out etc.<br>
<br>
=A0 =A0 =A0 =A0 =A0My SW config:<br>
=A0 =A0 =A0 =A0 =A0dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-=
4)<br>
=A0 =A0 =A0 =A0 =A0domU: Debian wheezy 3.2.x stock kernel.<br>
<br>
=A0 =A0 =A0 =A0 =A0Thanks,<br>
=A0 =A0 =A0 =A0 =A0Timothy<br>
<br>
=A0 =A0 =A0Are you passing hardware (PCI Passthrough) to the HVM guest?<br>
=A0 =A0 =A0What are the exact messages in the DomU?<br>
<br>
<br>
Yes, I&#39;m doing PCI passthrough (the IGD, audio &amp;&amp; USB controlle=
r).<br>
But this is actually a PVHVM guest since debian stock kernel has PVOP<br>
enabled.<br>
And when I tried another PVOP disabled linux distro (openelec v2.0), I<br>
did not see such msi related error message.<br>
Actually, with that domU I do not see anything obvious wrong from the<br>
log, but I also see nothing from panel (panel receive no signal and go<br>
power-saving) :-(<br>
<br>
<br>
Back to the issue I was reporting, the domU log looks like this:<br>
<br>
Dec 2 21:52:44 debvm kernel: [ 1085.604071]<br>
[drm:i915_hangcheck_ring_idle]<br>
*ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at<br>
3354], missed IRQ?<br>
Dec 2 21:56:50 debvm kernel: [ 1332.076071]<br>
[drm:i915_hangcheck_ring_idle]<br>
*ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at<b=
r>
11297], missed IRQ?<br>
Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response<br>
timeout, switching to polling mode: last cmd=3D0x000f0000<br>
Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from<br>
codec, disabling MSI: last cmd=3D0x002f0600<br>
Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response<br>
timeout, switching to single_cmd mode: last cmd=3D0x002f0600<br>
<br>
<br>
Thanks,<br>
Timothy<br>
</blockquote>
It does sound like there is a fix in 4.2.0, as indicated by Jan, that<br>
fixes this. I&#39;m not fully clued up to what the policy for backporting<b=
r>
fixes are, and I haven&#39;t looked at the complexity of the fix itself, bu=
t<br>
either updating to the 4.2.0 or a (personal) backport sounds like the<br>
right solution here.<br>
</blockquote></div></div>
I had a quick look, and it doesn&#39;t look that hard to backport that patc=
h.<br>
<br>
--<br>
Mats<div><div><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Unfortunately, I hadn&#39;t seen Jan&#39;s reply by the time I wrote my res=
ponse<br>
to your original email.<br>
<br>
--<br>
Mats<br>
<br>
______________________________<u></u>_________________<br>
Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org" target=3D"_blank">Xen-devel@list=
s.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
<br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org" target=3D"_blank">Xen-devel@list=
s.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--14dae93411e9e08a6604cffe3b8e--


--===============2009236113536242055==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============2009236113536242055==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@suse.com>
Subject: Re: Issue about domU missing interrupt
Date: Tue, 04 Dec 2012 10:15:58 +0000
Message-ID: <50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mats Petersson <mats.petersson@citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

>>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
>>  I had a quick look, and it doesn't look that hard to backport that patch.
> 
> Thanks, Mat.
> I'm glad to report that the patch do fix my problem.
> 
> And yest it is really easy to port since the code did not change across the
> two release.
> The only change would be line numbers (3841 vs 3803) and one extra comments
> before this line:
> 
>  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
> 
> I'm not sure if you are going to release another maintenance version that
> include this patch,
> but I'll report this to Debain maintainer since it's about to freeze for
> v7.0 release and v4.2.0 will not make it.

Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
out?

Jan

> On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
> <mats.petersson@citrix.com>wrote:
> 
>> On 03/12/12 13:19, Mats Petersson wrote:
>>
>>> On 03/12/12 13:14, G.R. wrote:
>>>
>>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>>>> <mats.petersson@citrix.com 
> <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>>>> wrote:
>>>>
>>>>      On 03/12/12 03:47, G.R. wrote:
>>>>
>>>>          Hi developers,
>>>>          I met some domU issues and the log suggests missing interrupt.
>>>>          Details from here:
>>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
>>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>>>>          In summary, this is the suspicious log:
>>>>
>>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>>>>
>>>>          I've checked the code in question and found that mode 3 is an
>>>>          'reserved_1' mode.
>>>>          I want to trace down the source of this mode setting to
>>>>          root-cause the issue.
>>>>          But I'm not an xen developer, and am even a newbie as a xen
>>>> user.
>>>>          Could anybody give me instructions about how to enable
>>>>          detailed debug log?
>>>>          It could be better if I can get advice about experiments to
>>>>          perform / switches to try out etc.
>>>>
>>>>          My SW config:
>>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>>>>          domU: Debian wheezy 3.2.x stock kernel.
>>>>
>>>>          Thanks,
>>>>          Timothy
>>>>
>>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>>>>      What are the exact messages in the DomU?
>>>>
>>>>
>>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>>>> enabled.
>>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>>>> did not see such msi related error message.
>>>> Actually, with that domU I do not see anything obvious wrong from the
>>>> log, but I also see nothing from panel (panel receive no signal and go
>>>> power-saving) :-(
>>>>
>>>>
>>>> Back to the issue I was reporting, the domU log looks like this:
>>>>
>>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>>>> [drm:i915_hangcheck_ring_idle]
>>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>>>> 3354], missed IRQ?
>>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>>>> [drm:i915_hangcheck_ring_idle]
>>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>>>> 11297], missed IRQ?
>>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>>>> timeout, switching to polling mode: last cmd=0x000f0000
>>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>>>> codec, disabling MSI: last cmd=0x002f0600
>>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>>>>
>>>>
>>>> Thanks,
>>>> Timothy
>>>>
>>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>>> fixes this. I'm not fully clued up to what the policy for backporting
>>> fixes are, and I haven't looked at the complexity of the fix itself, but
>>> either updating to the 4.2.0 or a (personal) backport sounds like the
>>> right solution here.
>>>
>> I had a quick look, and it doesn't look that hard to backport that patch.
>>
>> --
>> Mats
>>
>>
>>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>>> to your original email.
>>>
>>> --
>>> Mats
>>>
>>> ______________________________**_________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org 
>>> http://lists.xen.org/xen-devel 
>>>
>>>
>>>
>>
>> ______________________________**_________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org 
>> http://lists.xen.org/xen-devel 
>>

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
Subject: Re: Issue about domU missing interrupt
Date: Tue, 4 Dec 2012 13:01:05 +0200
Message-ID: <20121204110105.GX8912@reaktio.net>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Mats Petersson <mats.petersson@citrix.com>, xen-devel <xen-devel@lists.xen.org>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
> >>  I had a quick look, and it doesn't look that hard to backport that patch.
> > 
> > Thanks, Mat.
> > I'm glad to report that the patch do fix my problem.
> > 
> > And yest it is really easy to port since the code did not change across the
> > two release.
> > The only change would be line numbers (3841 vs 3803) and one extra comments
> > before this line:
> > 
> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
> > 
> > I'm not sure if you are going to release another maintenance version that
> > include this patch,
> > but I'll report this to Debain maintainer since it's about to freeze for
> > v7.0 release and v4.2.0 will not make it.
> 
> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
> out?
> 

It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
so I'd say it should be a candidate for Xen 4.1.4.

-- Pasi

> Jan
> 
> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
> > <mats.petersson@citrix.com>wrote:
> > 
> >> On 03/12/12 13:19, Mats Petersson wrote:
> >>
> >>> On 03/12/12 13:14, G.R. wrote:
> >>>
> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
> >>>> <mats.petersson@citrix.com 
> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
> >>>> wrote:
> >>>>
> >>>>      On 03/12/12 03:47, G.R. wrote:
> >>>>
> >>>>          Hi developers,
> >>>>          I met some domU issues and the log suggests missing interrupt.
> >>>>          Details from here:
> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
> >>>>          In summary, this is the suspicious log:
> >>>>
> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> >>>>
> >>>>          I've checked the code in question and found that mode 3 is an
> >>>>          'reserved_1' mode.
> >>>>          I want to trace down the source of this mode setting to
> >>>>          root-cause the issue.
> >>>>          But I'm not an xen developer, and am even a newbie as a xen
> >>>> user.
> >>>>          Could anybody give me instructions about how to enable
> >>>>          detailed debug log?
> >>>>          It could be better if I can get advice about experiments to
> >>>>          perform / switches to try out etc.
> >>>>
> >>>>          My SW config:
> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> >>>>          domU: Debian wheezy 3.2.x stock kernel.
> >>>>
> >>>>          Thanks,
> >>>>          Timothy
> >>>>
> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
> >>>>      What are the exact messages in the DomU?
> >>>>
> >>>>
> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
> >>>> enabled.
> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
> >>>> did not see such msi related error message.
> >>>> Actually, with that domU I do not see anything obvious wrong from the
> >>>> log, but I also see nothing from panel (panel receive no signal and go
> >>>> power-saving) :-(
> >>>>
> >>>>
> >>>> Back to the issue I was reporting, the domU log looks like this:
> >>>>
> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
> >>>> [drm:i915_hangcheck_ring_idle]
> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
> >>>> 3354], missed IRQ?
> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
> >>>> [drm:i915_hangcheck_ring_idle]
> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
> >>>> 11297], missed IRQ?
> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
> >>>> timeout, switching to polling mode: last cmd=0x000f0000
> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
> >>>> codec, disabling MSI: last cmd=0x002f0600
> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
> >>>>
> >>>>
> >>>> Thanks,
> >>>> Timothy
> >>>>
> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
> >>> fixes this. I'm not fully clued up to what the policy for backporting
> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
> >>> right solution here.
> >>>
> >> I had a quick look, and it doesn't look that hard to backport that patch.
> >>
> >> --
> >> Mats
> >>
> >>
> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
> >>> to your original email.
> >>>
> >>> --
> >>> Mats
> >>>
> >>> ______________________________**_________________
> >>> Xen-devel mailing list
> >>> Xen-devel@lists.xen.org 
> >>> http://lists.xen.org/xen-devel 
> >>>
> >>>
> >>>
> >>
> >> ______________________________**_________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org 
> >> http://lists.xen.org/xen-devel 
> >>
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Tue, 4 Dec 2012 23:20:28 +0800
Message-ID: <CAKhsbWYoCfWAOsBsxbpScYRHD1h5o-WOK2Hd3yj0XhC5eGvC3Q@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8011718497973607544=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20121204110105.GX8912@reaktio.net>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: Mats Petersson <mats.petersson@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============8011718497973607544==
Content-Type: multipart/alternative; boundary=14dae9340bfbea4e3b04d00867c0

--14dae9340bfbea4e3b04d00867c0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 4, 2012 at 7:01 PM, Pasi K=E4rkk=E4inen <pasik@iki.fi> wrote:

> On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
> > >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net>
> wrote:
> > >>  I had a quick look, and it doesn't look that hard to backport that
> patch.
> > >
> > > Thanks, Mat.
> > > I'm glad to report that the patch do fix my problem.
> > >
> > > And yest it is really easy to port since the code did not change
> across the
> > > two release.
> > > The only change would be line numbers (3841 vs 3803) and one extra
> comments
> > > before this line:
> > >
> > >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
> > >
> > > I'm not sure if you are going to release another maintenance version
> that
> > > include this patch,
> > > but I'll report this to Debain maintainer since it's about to freeze
> for
> > > v7.0 release and v4.2.0 will not make it.
> >
> > Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
> > out?
> >
>
> It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
> so I'd say it should be a candidate for Xen 4.1.4.
>
>
Hi, it seems that the patch has some side effect on pure HVM guest.
For openelec 2.0 guest, which is based on linux 3.2.x with PVOP disabled, I
see such syndrome in qemu-dm-xxx.log:

pt_msgaddr64_reg_write: Error: why comes to Upper Address without 64 bit
support??
pt_pci_write_config: Internal error: Invalid write emulation return
value[-1]. I/O emulator exit.

The guest dies immediately after the log, I have no way to check guest
kernel log.
Without the patch, this guest can boot without obvious error log even the
VGA passthrough does not quite work.
I'll check the code to see what does these log mean...

Thanks,
Timothy


> -- Pasi
>
> > Jan
> >
> > > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson
> > > <mats.petersson@citrix.com>wrote:
> > >
> > >> On 03/12/12 13:19, Mats Petersson wrote:
> > >>
> > >>> On 03/12/12 13:14, G.R. wrote:
> > >>>
> > >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
> > >>>> <mats.petersson@citrix.com
> > > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
> > >>>> wrote:
> > >>>>
> > >>>>      On 03/12/12 03:47, G.R. wrote:
> > >>>>
> > >>>>          Hi developers,
> > >>>>          I met some domU issues and the log suggests missing
> interrupt.
> > >>>>          Details from here:
> > >>>>          http://www.gossamer-threads.
> **com/lists/xen/users/263938#**
> > >>>> 263938 <
> http://www.gossamer-threads.com/lists/xen/users/263938#263938>
> > >>>>          In summary, this is the suspicious log:
> > >>>>
> > >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> > >>>>
> > >>>>          I've checked the code in question and found that mode 3 i=
s
> an
> > >>>>          'reserved_1' mode.
> > >>>>          I want to trace down the source of this mode setting to
> > >>>>          root-cause the issue.
> > >>>>          But I'm not an xen developer, and am even a newbie as a x=
en
> > >>>> user.
> > >>>>          Could anybody give me instructions about how to enable
> > >>>>          detailed debug log?
> > >>>>          It could be better if I can get advice about experiments =
to
> > >>>>          perform / switches to try out etc.
> > >>>>
> > >>>>          My SW config:
> > >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4=
)
> > >>>>          domU: Debian wheezy 3.2.x stock kernel.
> > >>>>
> > >>>>          Thanks,
> > >>>>          Timothy
> > >>>>
> > >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
> > >>>>      What are the exact messages in the DomU?
> > >>>>
> > >>>>
> > >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
> > >>>> But this is actually a PVHVM guest since debian stock kernel has
> PVOP
> > >>>> enabled.
> > >>>> And when I tried another PVOP disabled linux distro (openelec
> v2.0), I
> > >>>> did not see such msi related error message.
> > >>>> Actually, with that domU I do not see anything obvious wrong from
> the
> > >>>> log, but I also see nothing from panel (panel receive no signal an=
d
> go
> > >>>> power-saving) :-(
> > >>>>
> > >>>>
> > >>>> Back to the issue I was reporting, the domU log looks like this:
> > >>>>
> > >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
> > >>>> [drm:i915_hangcheck_ring_idle]
> > >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354,
> at
> > >>>> 3354], missed IRQ?
> > >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
> > >>>> [drm:i915_hangcheck_ring_idle]
> > >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on
> 11297, at
> > >>>> 11297], missed IRQ?
> > >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_respon=
se
> > >>>> timeout, switching to polling mode: last cmd=3D0x000f0000
> > >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response
> from
> > >>>> codec, disabling MSI: last cmd=3D0x002f0600
> > >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel:
> azx_get_response
> > >>>> timeout, switching to single_cmd mode: last cmd=3D0x002f0600
> > >>>>
> > >>>>
> > >>>> Thanks,
> > >>>> Timothy
> > >>>>
> > >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, th=
at
> > >>> fixes this. I'm not fully clued up to what the policy for backporti=
ng
> > >>> fixes are, and I haven't looked at the complexity of the fix itself=
,
> but
> > >>> either updating to the 4.2.0 or a (personal) backport sounds like t=
he
> > >>> right solution here.
> > >>>
> > >> I had a quick look, and it doesn't look that hard to backport that
> patch.
> > >>
> > >> --
> > >> Mats
> > >>
> > >>
> > >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my
> response
> > >>> to your original email.
> > >>>
> > >>> --
> > >>> Mats
> > >>>
> > >>> ______________________________**_________________
> > >>> Xen-devel mailing list
> > >>> Xen-devel@lists.xen.org
> > >>> http://lists.xen.org/xen-devel
> > >>>
> > >>>
> > >>>
> > >>
> > >> ______________________________**_________________
> > >> Xen-devel mailing list
> > >> Xen-devel@lists.xen.org
> > >> http://lists.xen.org/xen-devel
> > >>
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

--14dae9340bfbea4e3b04d00867c0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Tue, Dec 4, 2012 a=
t 7:01 PM, Pasi K=E4rkk=E4inen <span dir=3D"ltr">&lt;<a href=3D"mailto:pasi=
k@iki.fi" target=3D"_blank">pasik@iki.fi</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
<div class=3D"im">On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wro=
te:<br>
&gt; &gt;&gt;&gt; On 04.12.12 at 04:07, &quot;G.R.&quot; &lt;<a href=3D"mai=
lto:firemeteor@users.sourceforge.net">firemeteor@users.sourceforge.net</a>&=
gt; wrote:<br>
&gt; &gt;&gt; =A0I had a quick look, and it doesn&#39;t look that hard to b=
ackport that patch.<br>
&gt; &gt;<br>
&gt; &gt; Thanks, Mat.<br>
&gt; &gt; I&#39;m glad to report that the patch do fix my problem.<br>
&gt; &gt;<br>
&gt; &gt; And yest it is really easy to port since the code did not change =
across the<br>
&gt; &gt; two release.<br>
&gt; &gt; The only change would be line numbers (3841 vs 3803) and one extr=
a comments<br>
&gt; &gt; before this line:<br>
&gt; &gt;<br>
&gt; &gt; =A0static int pt_msix_update_one(struct pt_dev *dev, int entry_nr=
)<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m not sure if you are going to release another maintenance =
version that<br>
&gt; &gt; include this patch,<br>
&gt; &gt; but I&#39;ll report this to Debain maintainer since it&#39;s abou=
t to freeze for<br>
&gt; &gt; v7.0 release and v4.2.0 will not make it.<br>
&gt;<br>
&gt; Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is<br>
&gt; out?<br>
&gt;<br>
<br>
</div>It&#39;s already in Xen 4.2, it&#39;s confirmed to fix a bug in Xen 4=
.1,<br>
so I&#39;d say it should be a candidate for Xen 4.1.4.<br>
<span class=3D""><font color=3D"#888888"><br></font></span></blockquote><di=
v><br>Hi, it seems that the patch has some side effect on pure HVM guest.<b=
r>For openelec 2.0 guest, which is based on linux 3.2.x with PVOP disabled,=
 I see such syndrome in qemu-dm-xxx.log:<br>
<br>pt_msgaddr64_reg_write: Error: why comes to Upper Address without 64 bi=
t support??<br>pt_pci_write_config: Internal error: Invalid write emulation=
 return value[-1]. I/O emulator exit.<br><br>The guest dies immediately aft=
er the log, I have no way to check guest kernel log.<br>
Without the patch, this guest can boot without obvious error log even the V=
GA passthrough does not quite work.<br>I&#39;ll check the code to see what =
does these log mean...<br><br>Thanks,<br>Timothy<br>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">
<span class=3D""><font color=3D"#888888">
-- Pasi<br>
</font></span><div><div class=3D"h5"><br>
&gt; Jan<br>
&gt;<br>
&gt; &gt; On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson<br>
&gt; &gt; &lt;<a href=3D"mailto:mats.petersson@citrix.com">mats.petersson@c=
itrix.com</a>&gt;wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; On 03/12/12 13:19, Mats Petersson wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; On 03/12/12 13:14, G.R. wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson<br>
&gt; &gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:mats.petersson@citrix.com">mats=
.petersson@citrix.com</a><br>
&gt; &gt; &lt;mailto:<a href=3D"mailto:mats.petersson@citrix.">mats.peterss=
on@citrix.</a>**com&lt;<a href=3D"mailto:mats.petersson@citrix.com">mats.pe=
tersson@citrix.com</a>&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0On 03/12/12 03:47, G.R. wrote:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0Hi developers,<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0I met some domU issues and the log=
 suggests missing interrupt.<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0Details from here:<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0<a href=3D"http://www.gossamer-thr=
eads." target=3D"_blank">http://www.gossamer-threads.</a>**com/lists/xen/us=
ers/263938#**<br>
&gt; &gt;&gt;&gt;&gt; 263938 &lt;<a href=3D"http://www.gossamer-threads.com=
/lists/xen/users/263938#263938" target=3D"_blank">http://www.gossamer-threa=
ds.com/lists/xen/users/263938#263938</a>&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0In summary, this is the suspicious=
 log:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0(XEN) vmsi.c:122:d32767 Unsupporte=
d delivery mode 3<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0I&#39;ve checked the code in quest=
ion and found that mode 3 is an<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0&#39;reserved_1&#39; mode.<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0I want to trace down the source of=
 this mode setting to<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0root-cause the issue.<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0But I&#39;m not an xen developer, =
and am even a newbie as a xen<br>
&gt; &gt;&gt;&gt;&gt; user.<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0Could anybody give me instructions=
 about how to enable<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0detailed debug log?<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0It could be better if I can get ad=
vice about experiments to<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0perform / switches to try out etc.=
<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0My SW config:<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0dom0: Debian wheezy (3.6 experimen=
tal kernel, xen 4.1.3-4)<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0domU: Debian wheezy 3.2.x stock ke=
rnel.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0Thanks,<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0 =A0 =A0Timothy<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0Are you passing hardware (PCI Passthrough)=
 to the HVM guest?<br>
&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0What are the exact messages in the DomU?<b=
r>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Yes, I&#39;m doing PCI passthrough (the IGD, audio &a=
mp;&amp; USB controller).<br>
&gt; &gt;&gt;&gt;&gt; But this is actually a PVHVM guest since debian stock=
 kernel has PVOP<br>
&gt; &gt;&gt;&gt;&gt; enabled.<br>
&gt; &gt;&gt;&gt;&gt; And when I tried another PVOP disabled linux distro (=
openelec v2.0), I<br>
&gt; &gt;&gt;&gt;&gt; did not see such msi related error message.<br>
&gt; &gt;&gt;&gt;&gt; Actually, with that domU I do not see anything obviou=
s wrong from the<br>
&gt; &gt;&gt;&gt;&gt; log, but I also see nothing from panel (panel receive=
 no signal and go<br>
&gt; &gt;&gt;&gt;&gt; power-saving) :-(<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Back to the issue I was reporting, the domU log looks=
 like this:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Dec 2 21:52:44 debvm kernel: [ 1085.604071]<br>
&gt; &gt;&gt;&gt;&gt; [drm:i915_hangcheck_ring_idle]<br>
&gt; &gt;&gt;&gt;&gt; *ERROR* Hangcheck timer elapsed... blt ring idle [wai=
ting on 3354, at<br>
&gt; &gt;&gt;&gt;&gt; 3354], missed IRQ?<br>
&gt; &gt;&gt;&gt;&gt; Dec 2 21:56:50 debvm kernel: [ 1332.076071]<br>
&gt; &gt;&gt;&gt;&gt; [drm:i915_hangcheck_ring_idle]<br>
&gt; &gt;&gt;&gt;&gt; *ERROR* Hangcheck timer elapsed... render ring idle [=
waiting on 11297, at<br>
&gt; &gt;&gt;&gt;&gt; 11297], missed IRQ?<br>
&gt; &gt;&gt;&gt;&gt; Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: a=
zx_get_response<br>
&gt; &gt;&gt;&gt;&gt; timeout, switching to polling mode: last cmd=3D0x000f=
0000<br>
&gt; &gt;&gt;&gt;&gt; Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel:=
 No response from<br>
&gt; &gt;&gt;&gt;&gt; codec, disabling MSI: last cmd=3D0x002f0600<br>
&gt; &gt;&gt;&gt;&gt; Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel:=
 azx_get_response<br>
&gt; &gt;&gt;&gt;&gt; timeout, switching to single_cmd mode: last cmd=3D0x0=
02f0600<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt; Timothy<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; It does sound like there is a fix in 4.2.0, as indicated =
by Jan, that<br>
&gt; &gt;&gt;&gt; fixes this. I&#39;m not fully clued up to what the policy=
 for backporting<br>
&gt; &gt;&gt;&gt; fixes are, and I haven&#39;t looked at the complexity of =
the fix itself, but<br>
&gt; &gt;&gt;&gt; either updating to the 4.2.0 or a (personal) backport sou=
nds like the<br>
&gt; &gt;&gt;&gt; right solution here.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt; I had a quick look, and it doesn&#39;t look that hard to back=
port that patch.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; --<br>
&gt; &gt;&gt; Mats<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Unfortunately, I hadn&#39;t seen Jan&#39;s reply by the t=
ime I wrote my response<br>
&gt; &gt;&gt;&gt; to your original email.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt; Mats<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; ______________________________**_________________<br>
&gt; &gt;&gt;&gt; Xen-devel mailing list<br>
&gt; &gt;&gt;&gt; <a href=3D"mailto:Xen-devel@lists.xen.org">Xen-devel@list=
s.xen.org</a><br>
&gt; &gt;&gt;&gt; <a href=3D"http://lists.xen.org/xen-devel" target=3D"_bla=
nk">http://lists.xen.org/xen-devel</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; ______________________________**_________________<br>
&gt; &gt;&gt; Xen-devel mailing list<br>
&gt; &gt;&gt; <a href=3D"mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xe=
n.org</a><br>
&gt; &gt;&gt; <a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">=
http://lists.xen.org/xen-devel</a><br>
&gt; &gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
<div class=3D"im">&gt; Xen-devel mailing list<br>
&gt; <a href=3D"mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a>=
<br>
&gt; <a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://li=
sts.xen.org/xen-devel</a><br>
<br>
</div>_______________________________________________<br>
<div class=3D""><div class=3D"h5">Xen-devel mailing list<br>
<a href=3D"mailto:Xen-devel@lists.xen.org">Xen-devel@lists.xen.org</a><br>
<a href=3D"http://lists.xen.org/xen-devel" target=3D"_blank">http://lists.x=
en.org/xen-devel</a><br>
</div></div></blockquote></div><br></div>

--14dae9340bfbea4e3b04d00867c0--


--===============8011718497973607544==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============8011718497973607544==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 00:05:39 +0100
Message-ID: <28369388.20121205000539@eikelenboom.it>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20121204110105.GX8912@reaktio.net>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: =?utf-8?Q?Pasi_K=C3=A4rkk=C3=A4inen?= <pasik@iki.fi>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org


Tuesday, December 4, 2012, 12:01:05 PM, you wrote:

> On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
>> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
>> >>  I had a quick look, and it doesn't look that hard to backport that patch.
>> > 
>> > Thanks, Mat.
>> > I'm glad to report that the patch do fix my problem.
>> > 
>> > And yest it is really easy to port since the code did not change across the
>> > two release.
>> > The only change would be line numbers (3841 vs 3803) and one extra comments
>> > before this line:
>> > 
>> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>> > 
>> > I'm not sure if you are going to release another maintenance version that
>> > include this patch,
>> > but I'll report this to Debain maintainer since it's about to freeze for
>> > v7.0 release and v4.2.0 will not make it.
>> 
>> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
>> out?
>> 

> It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
> so I'd say it should be a candidate for Xen 4.1.4.

Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
(XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3

Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.

--
Sander

> -- Pasi

>> Jan
>> 
>> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
>> > <mats.petersson@citrix.com>wrote:
>> > 
>> >> On 03/12/12 13:19, Mats Petersson wrote:
>> >>
>> >>> On 03/12/12 13:14, G.R. wrote:
>> >>>
>> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>> >>>> <mats.petersson@citrix.com 
>> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>> >>>> wrote:
>> >>>>
>> >>>>      On 03/12/12 03:47, G.R. wrote:
>> >>>>
>> >>>>          Hi developers,
>> >>>>          I met some domU issues and the log suggests missing interrupt.
>> >>>>          Details from here:
>> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
>> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>> >>>>          In summary, this is the suspicious log:
>> >>>>
>> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>> >>>>
>> >>>>          I've checked the code in question and found that mode 3 is an
>> >>>>          'reserved_1' mode.
>> >>>>          I want to trace down the source of this mode setting to
>> >>>>          root-cause the issue.
>> >>>>          But I'm not an xen developer, and am even a newbie as a xen
>> >>>> user.
>> >>>>          Could anybody give me instructions about how to enable
>> >>>>          detailed debug log?
>> >>>>          It could be better if I can get advice about experiments to
>> >>>>          perform / switches to try out etc.
>> >>>>
>> >>>>          My SW config:
>> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>> >>>>          domU: Debian wheezy 3.2.x stock kernel.
>> >>>>
>> >>>>          Thanks,
>> >>>>          Timothy
>> >>>>
>> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>> >>>>      What are the exact messages in the DomU?
>> >>>>
>> >>>>
>> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>> >>>> enabled.
>> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>> >>>> did not see such msi related error message.
>> >>>> Actually, with that domU I do not see anything obvious wrong from the
>> >>>> log, but I also see nothing from panel (panel receive no signal and go
>> >>>> power-saving) :-(
>> >>>>
>> >>>>
>> >>>> Back to the issue I was reporting, the domU log looks like this:
>> >>>>
>> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>> >>>> [drm:i915_hangcheck_ring_idle]
>> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>> >>>> 3354], missed IRQ?
>> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>> >>>> [drm:i915_hangcheck_ring_idle]
>> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>> >>>> 11297], missed IRQ?
>> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>> >>>> timeout, switching to polling mode: last cmd=0x000f0000
>> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>> >>>> codec, disabling MSI: last cmd=0x002f0600
>> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>> >>>>
>> >>>>
>> >>>> Thanks,
>> >>>> Timothy
>> >>>>
>> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>> >>> fixes this. I'm not fully clued up to what the policy for backporting
>> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
>> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
>> >>> right solution here.
>> >>>
>> >> I had a quick look, and it doesn't look that hard to backport that patch.
>> >>
>> >> --
>> >> Mats
>> >>
>> >>
>> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>> >>> to your original email.
>> >>>
>> >>> --
>> >>> Mats
>> >>>
>> >>> ______________________________**_________________
>> >>> Xen-devel mailing list
>> >>> Xen-devel@lists.xen.org 
>> >>> http://lists.xen.org/xen-devel 
>> >>>
>> >>>
>> >>>
>> >>
>> >> ______________________________**_________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org 
>> >> http://lists.xen.org/xen-devel 
>> >>
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 11:51:13 +0000
Message-ID: <alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<28369388.20121205000539@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <28369388.20121205000539@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>, Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>, Anthony Perard <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, 4 Dec 2012, Sander Eikelenboom wrote:
> Tuesday, December 4, 2012, 12:01:05 PM, you wrote:
> 
> > On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
> >> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
> >> >>  I had a quick look, and it doesn't look that hard to backport that patch.
> >> > 
> >> > Thanks, Mat.
> >> > I'm glad to report that the patch do fix my problem.
> >> > 
> >> > And yest it is really easy to port since the code did not change across the
> >> > two release.
> >> > The only change would be line numbers (3841 vs 3803) and one extra comments
> >> > before this line:
> >> > 
> >> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
> >> > 
> >> > I'm not sure if you are going to release another maintenance version that
> >> > include this patch,
> >> > but I'll report this to Debain maintainer since it's about to freeze for
> >> > v7.0 release and v4.2.0 will not make it.
> >> 
> >> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
> >> out?
> >> 
> 
> > It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
> > so I'd say it should be a candidate for Xen 4.1.4.
> 
> Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
> (XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3
> 
> Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.
> 

The patch is supposed to fix a bug affecting msi_translate but in
upstream QEMU we haven't implemented msi_translate at all! So in this
case the cause of the bug (and as a consequence the fix) must be a
different one.



> Sander
> 
> > -- Pasi
> 
> >> Jan
> >> 
> >> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
> >> > <mats.petersson@citrix.com>wrote:
> >> > 
> >> >> On 03/12/12 13:19, Mats Petersson wrote:
> >> >>
> >> >>> On 03/12/12 13:14, G.R. wrote:
> >> >>>
> >> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
> >> >>>> <mats.petersson@citrix.com 
> >> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
> >> >>>> wrote:
> >> >>>>
> >> >>>>      On 03/12/12 03:47, G.R. wrote:
> >> >>>>
> >> >>>>          Hi developers,
> >> >>>>          I met some domU issues and the log suggests missing interrupt.
> >> >>>>          Details from here:
> >> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
> >> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
> >> >>>>          In summary, this is the suspicious log:
> >> >>>>
> >> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> >> >>>>
> >> >>>>          I've checked the code in question and found that mode 3 is an
> >> >>>>          'reserved_1' mode.
> >> >>>>          I want to trace down the source of this mode setting to
> >> >>>>          root-cause the issue.
> >> >>>>          But I'm not an xen developer, and am even a newbie as a xen
> >> >>>> user.
> >> >>>>          Could anybody give me instructions about how to enable
> >> >>>>          detailed debug log?
> >> >>>>          It could be better if I can get advice about experiments to
> >> >>>>          perform / switches to try out etc.
> >> >>>>
> >> >>>>          My SW config:
> >> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> >> >>>>          domU: Debian wheezy 3.2.x stock kernel.
> >> >>>>
> >> >>>>          Thanks,
> >> >>>>          Timothy
> >> >>>>
> >> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
> >> >>>>      What are the exact messages in the DomU?
> >> >>>>
> >> >>>>
> >> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
> >> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
> >> >>>> enabled.
> >> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
> >> >>>> did not see such msi related error message.
> >> >>>> Actually, with that domU I do not see anything obvious wrong from the
> >> >>>> log, but I also see nothing from panel (panel receive no signal and go
> >> >>>> power-saving) :-(
> >> >>>>
> >> >>>>
> >> >>>> Back to the issue I was reporting, the domU log looks like this:
> >> >>>>
> >> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
> >> >>>> [drm:i915_hangcheck_ring_idle]
> >> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
> >> >>>> 3354], missed IRQ?
> >> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
> >> >>>> [drm:i915_hangcheck_ring_idle]
> >> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
> >> >>>> 11297], missed IRQ?
> >> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
> >> >>>> timeout, switching to polling mode: last cmd=0x000f0000
> >> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
> >> >>>> codec, disabling MSI: last cmd=0x002f0600
> >> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
> >> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
> >> >>>>
> >> >>>>
> >> >>>> Thanks,
> >> >>>> Timothy
> >> >>>>
> >> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
> >> >>> fixes this. I'm not fully clued up to what the policy for backporting
> >> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
> >> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
> >> >>> right solution here.
> >> >>>
> >> >> I had a quick look, and it doesn't look that hard to backport that patch.
> >> >>
> >> >> --
> >> >> Mats
> >> >>
> >> >>
> >> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
> >> >>> to your original email.
> >> >>>
> >> >>> --
> >> >>> Mats
> >> >>>
> >> >>> ______________________________**_________________
> >> >>> Xen-devel mailing list
> >> >>> Xen-devel@lists.xen.org 
> >> >>> http://lists.xen.org/xen-devel 
> >> >>>
> >> >>>
> >> >>>
> >> >>
> >> >> ______________________________**_________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@lists.xen.org 
> >> >> http://lists.xen.org/xen-devel 
> >> >>
> >> 
> >> 
> >> 
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> 
> 
> 

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 13:02:22 +0100
Message-ID: <1662073313.20121205130222@eikelenboom.it>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<28369388.20121205000539@eikelenboom.it>
	<alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>, Anthony Perard <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org


Wednesday, December 5, 2012, 12:51:13 PM, you wrote:

> On Tue, 4 Dec 2012, Sander Eikelenboom wrote:
>> Tuesday, December 4, 2012, 12:01:05 PM, you wrote:
>> 
>> > On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
>> >> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
>> >> >>  I had a quick look, and it doesn't look that hard to backport that patch.
>> >> > 
>> >> > Thanks, Mat.
>> >> > I'm glad to report that the patch do fix my problem.
>> >> > 
>> >> > And yest it is really easy to port since the code did not change across the
>> >> > two release.
>> >> > The only change would be line numbers (3841 vs 3803) and one extra comments
>> >> > before this line:
>> >> > 
>> >> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>> >> > 
>> >> > I'm not sure if you are going to release another maintenance version that
>> >> > include this patch,
>> >> > but I'll report this to Debain maintainer since it's about to freeze for
>> >> > v7.0 release and v4.2.0 will not make it.
>> >> 
>> >> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
>> >> out?
>> >> 
>> 
>> > It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
>> > so I'd say it should be a candidate for Xen 4.1.4.
>> 
>> Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
>> (XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3
>> 
>> Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.
>> 

> The patch is supposed to fix a bug affecting msi_translate but in
> upstream QEMU we haven't implemented msi_translate at all! So in this
> case the cause of the bug (and as a consequence the fix) must be a
> different one.

Ok will see if i can find out what is going on. Probably have to force msi_translate=0.

I noticed "qemu-xen" doesn't make a log file in /var/log/xen as "qemu-dm" does, is this expected ?


>> Sander
>> 
>> > -- Pasi
>> 
>> >> Jan
>> >> 
>> >> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
>> >> > <mats.petersson@citrix.com>wrote:
>> >> > 
>> >> >> On 03/12/12 13:19, Mats Petersson wrote:
>> >> >>
>> >> >>> On 03/12/12 13:14, G.R. wrote:
>> >> >>>
>> >> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>> >> >>>> <mats.petersson@citrix.com 
>> >> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>> >> >>>> wrote:
>> >> >>>>
>> >> >>>>      On 03/12/12 03:47, G.R. wrote:
>> >> >>>>
>> >> >>>>          Hi developers,
>> >> >>>>          I met some domU issues and the log suggests missing interrupt.
>> >> >>>>          Details from here:
>> >> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
>> >> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>> >> >>>>          In summary, this is the suspicious log:
>> >> >>>>
>> >> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>> >> >>>>
>> >> >>>>          I've checked the code in question and found that mode 3 is an
>> >> >>>>          'reserved_1' mode.
>> >> >>>>          I want to trace down the source of this mode setting to
>> >> >>>>          root-cause the issue.
>> >> >>>>          But I'm not an xen developer, and am even a newbie as a xen
>> >> >>>> user.
>> >> >>>>          Could anybody give me instructions about how to enable
>> >> >>>>          detailed debug log?
>> >> >>>>          It could be better if I can get advice about experiments to
>> >> >>>>          perform / switches to try out etc.
>> >> >>>>
>> >> >>>>          My SW config:
>> >> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>> >> >>>>          domU: Debian wheezy 3.2.x stock kernel.
>> >> >>>>
>> >> >>>>          Thanks,
>> >> >>>>          Timothy
>> >> >>>>
>> >> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>> >> >>>>      What are the exact messages in the DomU?
>> >> >>>>
>> >> >>>>
>> >> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>> >> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>> >> >>>> enabled.
>> >> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>> >> >>>> did not see such msi related error message.
>> >> >>>> Actually, with that domU I do not see anything obvious wrong from the
>> >> >>>> log, but I also see nothing from panel (panel receive no signal and go
>> >> >>>> power-saving) :-(
>> >> >>>>
>> >> >>>>
>> >> >>>> Back to the issue I was reporting, the domU log looks like this:
>> >> >>>>
>> >> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>> >> >>>> 3354], missed IRQ?
>> >> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>> >> >>>> 11297], missed IRQ?
>> >> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>> >> >>>> timeout, switching to polling mode: last cmd=0x000f0000
>> >> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>> >> >>>> codec, disabling MSI: last cmd=0x002f0600
>> >> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>> >> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>> >> >>>>
>> >> >>>>
>> >> >>>> Thanks,
>> >> >>>> Timothy
>> >> >>>>
>> >> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>> >> >>> fixes this. I'm not fully clued up to what the policy for backporting
>> >> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
>> >> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
>> >> >>> right solution here.
>> >> >>>
>> >> >> I had a quick look, and it doesn't look that hard to backport that patch.
>> >> >>
>> >> >> --
>> >> >> Mats
>> >> >>
>> >> >>
>> >> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>> >> >>> to your original email.
>> >> >>>
>> >> >>> --
>> >> >>> Mats
>> >> >>>
>> >> >>> ______________________________**_________________
>> >> >>> Xen-devel mailing list
>> >> >>> Xen-devel@lists.xen.org 
>> >> >>> http://lists.xen.org/xen-devel 
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >> ______________________________**_________________
>> >> >> Xen-devel mailing list
>> >> >> Xen-devel@lists.xen.org 
>> >> >> http://lists.xen.org/xen-devel 
>> >> >>
>> >> 
>> >> 
>> >> 
>> >> _______________________________________________
>> >> Xen-devel mailing list
>> >> Xen-devel@lists.xen.org
>> >> http://lists.xen.org/xen-devel
>> 
>> 
>> 

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 12:07:07 +0000
Message-ID: <alpine.DEB.2.02.1212051206250.8801@kaball.uk.xensource.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<28369388.20121205000539@eikelenboom.it>
	<alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
	<1662073313.20121205130222@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1662073313.20121205130222@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>, Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>, Anthony Perard <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 5 Dec 2012, Sander Eikelenboom wrote:
> Wednesday, December 5, 2012, 12:51:13 PM, you wrote:
> 
> > On Tue, 4 Dec 2012, Sander Eikelenboom wrote:
> >> Tuesday, December 4, 2012, 12:01:05 PM, you wrote:
> >> 
> >> > On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
> >> >> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
> >> >> >>  I had a quick look, and it doesn't look that hard to backport that patch.
> >> >> > 
> >> >> > Thanks, Mat.
> >> >> > I'm glad to report that the patch do fix my problem.
> >> >> > 
> >> >> > And yest it is really easy to port since the code did not change across the
> >> >> > two release.
> >> >> > The only change would be line numbers (3841 vs 3803) and one extra comments
> >> >> > before this line:
> >> >> > 
> >> >> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
> >> >> > 
> >> >> > I'm not sure if you are going to release another maintenance version that
> >> >> > include this patch,
> >> >> > but I'll report this to Debain maintainer since it's about to freeze for
> >> >> > v7.0 release and v4.2.0 will not make it.
> >> >> 
> >> >> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
> >> >> out?
> >> >> 
> >> 
> >> > It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
> >> > so I'd say it should be a candidate for Xen 4.1.4.
> >> 
> >> Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
> >> (XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3
> >> 
> >> Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.
> >> 
> 
> > The patch is supposed to fix a bug affecting msi_translate but in
> > upstream QEMU we haven't implemented msi_translate at all! So in this
> > case the cause of the bug (and as a consequence the fix) must be a
> > different one.
> 
> Ok will see if i can find out what is going on. Probably have to force msi_translate=0.
> 
> I noticed "qemu-xen" doesn't make a log file in /var/log/xen as "qemu-dm" does, is this expected ?

No, it is not. You should get the usual /var/log/xen/qemu-dm-domainname.log file.


> >> Sander
> >> 
> >> > -- Pasi
> >> 
> >> >> Jan
> >> >> 
> >> >> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
> >> >> > <mats.petersson@citrix.com>wrote:
> >> >> > 
> >> >> >> On 03/12/12 13:19, Mats Petersson wrote:
> >> >> >>
> >> >> >>> On 03/12/12 13:14, G.R. wrote:
> >> >> >>>
> >> >> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
> >> >> >>>> <mats.petersson@citrix.com 
> >> >> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
> >> >> >>>> wrote:
> >> >> >>>>
> >> >> >>>>      On 03/12/12 03:47, G.R. wrote:
> >> >> >>>>
> >> >> >>>>          Hi developers,
> >> >> >>>>          I met some domU issues and the log suggests missing interrupt.
> >> >> >>>>          Details from here:
> >> >> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
> >> >> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
> >> >> >>>>          In summary, this is the suspicious log:
> >> >> >>>>
> >> >> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
> >> >> >>>>
> >> >> >>>>          I've checked the code in question and found that mode 3 is an
> >> >> >>>>          'reserved_1' mode.
> >> >> >>>>          I want to trace down the source of this mode setting to
> >> >> >>>>          root-cause the issue.
> >> >> >>>>          But I'm not an xen developer, and am even a newbie as a xen
> >> >> >>>> user.
> >> >> >>>>          Could anybody give me instructions about how to enable
> >> >> >>>>          detailed debug log?
> >> >> >>>>          It could be better if I can get advice about experiments to
> >> >> >>>>          perform / switches to try out etc.
> >> >> >>>>
> >> >> >>>>          My SW config:
> >> >> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
> >> >> >>>>          domU: Debian wheezy 3.2.x stock kernel.
> >> >> >>>>
> >> >> >>>>          Thanks,
> >> >> >>>>          Timothy
> >> >> >>>>
> >> >> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
> >> >> >>>>      What are the exact messages in the DomU?
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
> >> >> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
> >> >> >>>> enabled.
> >> >> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
> >> >> >>>> did not see such msi related error message.
> >> >> >>>> Actually, with that domU I do not see anything obvious wrong from the
> >> >> >>>> log, but I also see nothing from panel (panel receive no signal and go
> >> >> >>>> power-saving) :-(
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> Back to the issue I was reporting, the domU log looks like this:
> >> >> >>>>
> >> >> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
> >> >> >>>> [drm:i915_hangcheck_ring_idle]
> >> >> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
> >> >> >>>> 3354], missed IRQ?
> >> >> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
> >> >> >>>> [drm:i915_hangcheck_ring_idle]
> >> >> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
> >> >> >>>> 11297], missed IRQ?
> >> >> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
> >> >> >>>> timeout, switching to polling mode: last cmd=0x000f0000
> >> >> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
> >> >> >>>> codec, disabling MSI: last cmd=0x002f0600
> >> >> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
> >> >> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> Thanks,
> >> >> >>>> Timothy
> >> >> >>>>
> >> >> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
> >> >> >>> fixes this. I'm not fully clued up to what the policy for backporting
> >> >> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
> >> >> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
> >> >> >>> right solution here.
> >> >> >>>
> >> >> >> I had a quick look, and it doesn't look that hard to backport that patch.
> >> >> >>
> >> >> >> --
> >> >> >> Mats
> >> >> >>
> >> >> >>
> >> >> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
> >> >> >>> to your original email.
> >> >> >>>
> >> >> >>> --
> >> >> >>> Mats
> >> >> >>>
> >> >> >>> ______________________________**_________________
> >> >> >>> Xen-devel mailing list
> >> >> >>> Xen-devel@lists.xen.org 
> >> >> >>> http://lists.xen.org/xen-devel 
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >> >> ______________________________**_________________
> >> >> >> Xen-devel mailing list
> >> >> >> Xen-devel@lists.xen.org 
> >> >> >> http://lists.xen.org/xen-devel 
> >> >> >>
> >> >> 
> >> >> 
> >> >> 
> >> >> _______________________________________________
> >> >> Xen-devel mailing list
> >> >> Xen-devel@lists.xen.org
> >> >> http://lists.xen.org/xen-devel
> >> 
> >> 
> >> 
> 
> 

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 13:11:28 +0100
Message-ID: <182397271.20121205131128@eikelenboom.it>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<28369388.20121205000539@eikelenboom.it>
	<alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
	<1662073313.20121205130222@eikelenboom.it>
	<alpine.DEB.2.02.1212051206250.8801@kaball.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <alpine.DEB.2.02.1212051206250.8801@kaball.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>, Anthony Perard <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org


Wednesday, December 5, 2012, 1:07:07 PM, you wrote:

> On Wed, 5 Dec 2012, Sander Eikelenboom wrote:
>> Wednesday, December 5, 2012, 12:51:13 PM, you wrote:
>> 
>> > On Tue, 4 Dec 2012, Sander Eikelenboom wrote:
>> >> Tuesday, December 4, 2012, 12:01:05 PM, you wrote:
>> >> 
>> >> > On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
>> >> >> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
>> >> >> >>  I had a quick look, and it doesn't look that hard to backport that patch.
>> >> >> > 
>> >> >> > Thanks, Mat.
>> >> >> > I'm glad to report that the patch do fix my problem.
>> >> >> > 
>> >> >> > And yest it is really easy to port since the code did not change across the
>> >> >> > two release.
>> >> >> > The only change would be line numbers (3841 vs 3803) and one extra comments
>> >> >> > before this line:
>> >> >> > 
>> >> >> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>> >> >> > 
>> >> >> > I'm not sure if you are going to release another maintenance version that
>> >> >> > include this patch,
>> >> >> > but I'll report this to Debain maintainer since it's about to freeze for
>> >> >> > v7.0 release and v4.2.0 will not make it.
>> >> >> 
>> >> >> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
>> >> >> out?
>> >> >> 
>> >> 
>> >> > It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
>> >> > so I'd say it should be a candidate for Xen 4.1.4.
>> >> 
>> >> Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
>> >> (XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3
>> >> 
>> >> Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.
>> >> 
>> 
>> > The patch is supposed to fix a bug affecting msi_translate but in
>> > upstream QEMU we haven't implemented msi_translate at all! So in this
>> > case the cause of the bug (and as a consequence the fix) must be a
>> > different one.
>> 
>> Ok will see if i can find out what is going on. Probably have to force msi_translate=0.
>> 
>> I noticed "qemu-xen" doesn't make a log file in /var/log/xen as "qemu-dm" does, is this expected ?

> No, it is not. You should get the usual /var/log/xen/qemu-dm-domainname.log file.

OK .. i was expecting a qemu-xen-domainname, so will double check :-)

Thx !

>> >> Sander
>> >> 
>> >> > -- Pasi
>> >> 
>> >> >> Jan
>> >> >> 
>> >> >> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
>> >> >> > <mats.petersson@citrix.com>wrote:
>> >> >> > 
>> >> >> >> On 03/12/12 13:19, Mats Petersson wrote:
>> >> >> >>
>> >> >> >>> On 03/12/12 13:14, G.R. wrote:
>> >> >> >>>
>> >> >> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>> >> >> >>>> <mats.petersson@citrix.com 
>> >> >> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>> >> >> >>>> wrote:
>> >> >> >>>>
>> >> >> >>>>      On 03/12/12 03:47, G.R. wrote:
>> >> >> >>>>
>> >> >> >>>>          Hi developers,
>> >> >> >>>>          I met some domU issues and the log suggests missing interrupt.
>> >> >> >>>>          Details from here:
>> >> >> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
>> >> >> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>> >> >> >>>>          In summary, this is the suspicious log:
>> >> >> >>>>
>> >> >> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>> >> >> >>>>
>> >> >> >>>>          I've checked the code in question and found that mode 3 is an
>> >> >> >>>>          'reserved_1' mode.
>> >> >> >>>>          I want to trace down the source of this mode setting to
>> >> >> >>>>          root-cause the issue.
>> >> >> >>>>          But I'm not an xen developer, and am even a newbie as a xen
>> >> >> >>>> user.
>> >> >> >>>>          Could anybody give me instructions about how to enable
>> >> >> >>>>          detailed debug log?
>> >> >> >>>>          It could be better if I can get advice about experiments to
>> >> >> >>>>          perform / switches to try out etc.
>> >> >> >>>>
>> >> >> >>>>          My SW config:
>> >> >> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>> >> >> >>>>          domU: Debian wheezy 3.2.x stock kernel.
>> >> >> >>>>
>> >> >> >>>>          Thanks,
>> >> >> >>>>          Timothy
>> >> >> >>>>
>> >> >> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>> >> >> >>>>      What are the exact messages in the DomU?
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>> >> >> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>> >> >> >>>> enabled.
>> >> >> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>> >> >> >>>> did not see such msi related error message.
>> >> >> >>>> Actually, with that domU I do not see anything obvious wrong from the
>> >> >> >>>> log, but I also see nothing from panel (panel receive no signal and go
>> >> >> >>>> power-saving) :-(
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Back to the issue I was reporting, the domU log looks like this:
>> >> >> >>>>
>> >> >> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>> >> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>> >> >> >>>> 3354], missed IRQ?
>> >> >> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>> >> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>> >> >> >>>> 11297], missed IRQ?
>> >> >> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>> >> >> >>>> timeout, switching to polling mode: last cmd=0x000f0000
>> >> >> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>> >> >> >>>> codec, disabling MSI: last cmd=0x002f0600
>> >> >> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>> >> >> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Thanks,
>> >> >> >>>> Timothy
>> >> >> >>>>
>> >> >> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>> >> >> >>> fixes this. I'm not fully clued up to what the policy for backporting
>> >> >> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
>> >> >> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
>> >> >> >>> right solution here.
>> >> >> >>>
>> >> >> >> I had a quick look, and it doesn't look that hard to backport that patch.
>> >> >> >>
>> >> >> >> --
>> >> >> >> Mats
>> >> >> >>
>> >> >> >>
>> >> >> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>> >> >> >>> to your original email.
>> >> >> >>>
>> >> >> >>> --
>> >> >> >>> Mats
>> >> >> >>>
>> >> >> >>> ______________________________**_________________
>> >> >> >>> Xen-devel mailing list
>> >> >> >>> Xen-devel@lists.xen.org 
>> >> >> >>> http://lists.xen.org/xen-devel 
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>
>> >> >> >> ______________________________**_________________
>> >> >> >> Xen-devel mailing list
>> >> >> >> Xen-devel@lists.xen.org 
>> >> >> >> http://lists.xen.org/xen-devel 
>> >> >> >>
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> _______________________________________________
>> >> >> Xen-devel mailing list
>> >> >> Xen-devel@lists.xen.org
>> >> >> http://lists.xen.org/xen-devel
>> >> 
>> >> 
>> >> 
>> 
>> 

From mboxrd@z Thu Jan  1 00:00:00 1970
From: "G.R." <firemeteor@users.sourceforge.net>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 20:58:53 +0800
Message-ID: <CAKhsbWZsVhLg1-b72T8ojaJu8o7cJW3jRubku8ygfHbkzeyMJA@mail.gmail.com>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<CAKhsbWYoCfWAOsBsxbpScYRHD1h5o-WOK2Hd3yj0XhC5eGvC3Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8044711677056468962=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAKhsbWYoCfWAOsBsxbpScYRHD1h5o-WOK2Hd3yj0XhC5eGvC3Q@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= <pasik@iki.fi>
Cc: Mats Petersson <mats.petersson@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============8044711677056468962==
Content-Type: multipart/alternative; boundary=90e6ba6e8e2070dd2804d01a8bec

--90e6ba6e8e2070dd2804d01a8bec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 4, 2012 at 11:20 PM, G.R. <firemeteor@users.sourceforge.net>wro=
te:

> On Tue, Dec 4, 2012 at 7:01 PM, Pasi K=E4rkk=E4inen <pasik@iki.fi> wrote:
>
>> On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
>> > >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net>
>> wrote:
>> > >>  I had a quick look, and it doesn't look that hard to backport that
>> patch.
>> > >
>> > > Thanks, Mat.
>> > > I'm glad to report that the patch do fix my problem.
>> > >
>> > > And yest it is really easy to port since the code did not change
>> across the
>> > > two release.
>> > > The only change would be line numbers (3841 vs 3803) and one extra
>> comments
>> > > before this line:
>> > >
>> > >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>> > >
>> > > I'm not sure if you are going to release another maintenance version
>> that
>> > > include this patch,
>> > > but I'll report this to Debain maintainer since it's about to freeze
>> for
>> > > v7.0 release and v4.2.0 will not make it.
>> >
>> > Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
>> > out?
>> >
>>
>> It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
>> so I'd say it should be a candidate for Xen 4.1.4.
>>
>>
> Hi, it seems that the patch has some side effect on pure HVM guest.
> For openelec 2.0 guest, which is based on linux 3.2.x with PVOP disabled,
> I see such syndrome in qemu-dm-xxx.log:
>
> pt_msgaddr64_reg_write: Error: why comes to Upper Address without 64 bit
> support??
> pt_pci_write_config: Internal error: Invalid write emulation return
> value[-1]. I/O emulator exit.
>
> The guest dies immediately after the log, I have no way to check guest
> kernel log.
> Without the patch, this guest can boot without obvious error log even the
> VGA passthrough does not quite work.
> I'll check the code to see what does these log mean...
>

I did some analysis and it really looks like a bug to me.
Since this is a patch back-ported from 4.2.0, I would like to ask is there
any follow up patch that would fix this issue?
Please see my analysis below:

Here is part of the qemu-dm log, with debug log enabled at compile time:

dm-command: hot insert pass-through pci dev
register_real_device: Assigning real physical device 00:1b.0 ...
pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No
such file or directory: 0x0:0x1b.0x0
pt_register_regions: IO region registered (size=3D0x00004000
base_addr=3D0xf7c10004)
pt_msi_setup: msi mapped with pirq 36
pci_intx: intx=3D1
register_real_device: Real physical device 00:1b.0 registered successfuly!
IRQ type =3D MSI-INTx
...
pt_pci_read_config: [00:06.0]: address=3D0000 val=3D0x0000*8086* len=3D2
pt_pci_read_config: [00:06.0]: address=3D0002 val=3D0x0000*1e20* len=3D2
...
*pt_pci_write_config: [00:06.0]: address=3D0068* val=3D0x00000000 len=3D4
...
pt_pci_write_config: [00:06.0]: address=3D0062 val=3D0x00000081 len=3D2
*pt_msgctrl_reg_write: guest enabling MSI, disable MSI-INTx translation*
pci_intx: intx=3D1
*pt_msi_disable: Unmap msi with pirq 36*
pt_msgctrl_reg_write: setup msi for dev 30
pt_msi_setup: msi mapped with pirq 36
pt_msi_update: Update msi with pirq 36 gvec 51 gflags 1303
pt_pci_read_config: [00:06.0]: address=3D0062 val=3D0x00000081 len=3D2
pt_pci_write_config: [00:06.0]: address=3D0062 val=3D0x00000081 len=3D2
pt_pci_write_config: [00:06.0]: address=3D0064 val=3D0xfee0300c len=3D4
*pt_pci_write_config: [00:06.0]: address=3D0068* val=3D0x00000000 len=3D4
pt_msgaddr64_reg_write: Error: why comes to Upper Address without 64 bit
support??
pt_pci_write_config: Internal error: Invalid write emulation return
value[-1]. I/O emulator exit.


Here the device in question should is the audio controller, 00:1b.0 in the
host, which is 64 bit capable:
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family
High Definition Audio Controller (rev 04)
    Capabilities: [60] MSI: Enable+ Count=3D1/1 Maskable- 64bit+
        Address: 00000000fee00378  Data: 0000

And there is also a successful write to offset 0x68 above, while the second
write fails the I/O emulator.

pt_disable_msi_translate is called after the pt_msgctrl_reg_write log above=
:
            PT_LOG("guest enabling MSI-X, disable MSI-INTx translation\n");
            pt_disable_msi_translate(ptdev);


The patch added pt_msi_disable() call into this function, And the
pt_msi_disable function has these lines:
out:
    /* clear msi info */
    dev->msi->flags =3D 0;
    dev->msi->pirq =3D -1;
    dev->msi_trans_en =3D 0;

As a result, the flags are cleared -- this is new to the patch.
And I believe this change caused the failure in pt_msgaddr64_write():

3882     /* check whether the type is 64 bit or not */
3883     if (!(ptdev->msi->flags & PCI_MSI_FLAGS_64BIT))
3884     {
3885         /* exit I/O emulator */
3886         PT_LOG("Error: why comes to Upper Address without 64 bit
support??\n");
3887         return -1;
3888     }


I only see flags setup in  pt_msgctrl_reg_init() function. I guess this is
not called this time.

Thanks,
Timothy

--90e6ba6e8e2070dd2804d01a8bec
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Tue, Dec 4, 2012 a=
t 11:20 PM, G.R. <span dir=3D"ltr">&lt;<a href=3D"mailto:firemeteor@users.s=
ourceforge.net" target=3D"_blank">firemeteor@users.sourceforge.net</a>&gt;<=
/span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"gmail_extra=
"><div class=3D"gmail_quote"><div>On Tue, Dec 4, 2012 at 7:01 PM, Pasi K=E4=
rkk=E4inen <span dir=3D"ltr">&lt;<a href=3D"mailto:pasik@iki.fi" target=3D"=
_blank">pasik@iki.fi</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div>On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:<br>
&gt; &gt;&gt;&gt; On 04.12.12 at 04:07, &quot;G.R.&quot; &lt;<a href=3D"mai=
lto:firemeteor@users.sourceforge.net" target=3D"_blank">firemeteor@users.so=
urceforge.net</a>&gt; wrote:<br>
&gt; &gt;&gt; =A0I had a quick look, and it doesn&#39;t look that hard to b=
ackport that patch.<br>
&gt; &gt;<br>
&gt; &gt; Thanks, Mat.<br>
&gt; &gt; I&#39;m glad to report that the patch do fix my problem.<br>
&gt; &gt;<br>
&gt; &gt; And yest it is really easy to port since the code did not change =
across the<br>
&gt; &gt; two release.<br>
&gt; &gt; The only change would be line numbers (3841 vs 3803) and one extr=
a comments<br>
&gt; &gt; before this line:<br>
&gt; &gt;<br>
&gt; &gt; =A0static int pt_msix_update_one(struct pt_dev *dev, int entry_nr=
)<br>
&gt; &gt;<br>
&gt; &gt; I&#39;m not sure if you are going to release another maintenance =
version that<br>
&gt; &gt; include this patch,<br>
&gt; &gt; but I&#39;ll report this to Debain maintainer since it&#39;s abou=
t to freeze for<br>
&gt; &gt; v7.0 release and v4.2.0 will not make it.<br>
&gt;<br>
&gt; Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is<br>
&gt; out?<br>
&gt;<br>
<br>
</div>It&#39;s already in Xen 4.2, it&#39;s confirmed to fix a bug in Xen 4=
.1,<br>
so I&#39;d say it should be a candidate for Xen 4.1.4.<br>
<span><font color=3D"#888888"><br></font></span></blockquote></div><div><br=
>Hi, it seems that the patch has some side effect on pure HVM guest.<br>For=
 openelec 2.0 guest, which is based on linux 3.2.x with PVOP disabled, I se=
e such syndrome in qemu-dm-xxx.log:<br>



<br>pt_msgaddr64_reg_write: Error: why comes to Upper Address without 64 bi=
t support??<br>pt_pci_write_config: Internal error: Invalid write emulation=
 return value[-1]. I/O emulator exit.<br><br>The guest dies immediately aft=
er the log, I have no way to check guest kernel log.<br>



Without the patch, this guest can boot without obvious error log even the V=
GA passthrough does not quite work.<br>I&#39;ll check the code to see what =
does these log mean...<br></div></div></div></blockquote><div><br>I did som=
e analysis and it really looks like a bug to me.<br>

Since this is a patch back-ported from 4.2.0, I would like to ask is there =
any follow up patch that would fix this issue?<br>Please see my analysis be=
low:<br>
<br>Here is part of the qemu-dm log, with debug log enabled at compile time=
:<br><br><span style=3D"font-family:courier new,monospace">dm-command: hot =
insert pass-through pci dev<br>register_real_device: Assigning real physica=
l device 00:1b.0 ...<br>

pt_iomul_init: Error: pt_iomul_init can&#39;t open file /dev/xen/pci_iomul:=
 No such file or directory: 0x0:0x1b.0x0<br>pt_register_regions: IO region =
registered (size=3D0x00004000 base_addr=3D0xf7c10004)<br>pt_msi_setup: msi =
mapped with pirq 36<br>

pci_intx: intx=3D1<br>register_real_device: Real physical device 00:1b.0 re=
gistered successfuly!<br>IRQ type =3D MSI-INTx<br>...<br>pt_pci_read_config=
: [00:06.0]: address=3D0000 val=3D0x0000<b>8086</b> len=3D2<br>pt_pci_read_=
config: [00:06.0]: address=3D0002 val=3D0x0000<b>1e20</b> len=3D2<br>

...<br><b>pt_pci_write_config: [00:06.0]: address=3D0068</b> val=3D0x000000=
00 len=3D4<br>...<br>pt_pci_write_config: [00:06.0]: address=3D0062 val=3D0=
x00000081 len=3D2<br><b>pt_msgctrl_reg_write: guest enabling MSI, disable M=
SI-INTx translation</b><br>

pci_intx: intx=3D1<br><b>pt_msi_disable: Unmap msi with pirq 36</b><br>pt_m=
sgctrl_reg_write: setup msi for dev 30<br>pt_msi_setup: msi mapped with pir=
q 36<br>pt_msi_update: Update msi with pirq 36 gvec 51 gflags 1303<br>pt_pc=
i_read_config: [00:06.0]: address=3D0062 val=3D0x00000081 len=3D2<br>

pt_pci_write_config: [00:06.0]: address=3D0062 val=3D0x00000081 len=3D2<br>=
pt_pci_write_config: [00:06.0]: address=3D0064 val=3D0xfee0300c len=3D4<br>=
<b>pt_pci_write_config: [00:06.0]: address=3D0068</b> val=3D0x00000000 len=
=3D4<br>pt_msgaddr64_reg_write: Error: why comes to Upper Address without 6=
4 bit support??<br>

pt_pci_write_config: Internal error: Invalid write emulation return value[-=
1]. I/O emulator exit.<br></span><br><span style=3D"font-family:courier new=
,monospace"></span></div></div><br>Here the device in question should is th=
e audio controller, 00:1b.0 in the host, which is 64 bit capable:<br>


00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family=
 High Definition Audio Controller (rev 04)<br>=A0=A0=A0 Capabilities: [60] =
MSI: Enable+ Count=3D1/1 Maskable- 64bit+<br>=A0=A0=A0 =A0=A0=A0 Address: 0=
0000000fee00378=A0 Data: 0000<br>

<br>And there is also a successful write to offset 0x68 above, while the se=
cond write fails the I/O emulator.<br>
<br>pt_disable_msi_translate is called after the pt_msgctrl_reg_write log a=
bove:<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 PT_LOG(&quot;guest enabling MSI-=
X, disable MSI-INTx translation\n&quot;);<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0 pt_disable_msi_translate(ptdev);<br>


<br><br>The patch added pt_msi_disable() call into this function, And the p=
t_msi_disable function has these lines:<br><span style=3D"font-family:couri=
er new,monospace">out:<br>=A0=A0=A0 /* clear msi info */<br>=A0=A0=A0 dev-&=
gt;msi-&gt;flags =3D 0;<br>

=A0=A0=A0 dev-&gt;msi-&gt;pirq =3D -1;<br>=A0=A0=A0 dev-&gt;msi_trans_en =
=3D 0;</span><br>
<br>As a result, the flags are cleared -- this is new to the patch. <br>And=
 I believe this change caused the failure in pt_msgaddr64_write():<br><br><=
span style=3D"font-family:courier new,monospace">3882=A0=A0=A0=A0 /* check =
whether the type is 64 bit or not */<br>

3883=A0=A0=A0=A0 if (!(ptdev-&gt;msi-&gt;flags &amp; PCI_MSI_FLAGS_64BIT))<=
br>3884=A0=A0=A0=A0 {<br>3885=A0=A0=A0=A0=A0=A0=A0=A0 /* exit I/O emulator =
*/<br>3886=A0=A0=A0=A0=A0=A0=A0=A0 PT_LOG(&quot;Error: why comes to Upper A=
ddress without 64 bit support??\n&quot;);<br>

3887=A0=A0=A0=A0=A0=A0=A0=A0 return -1;<br>3888=A0=A0=A0=A0 }</span><br><br=
><br>I only see flags setup in=A0 pt_msgctrl_reg_init() function. I guess t=
his is not called this time.<br><br>Thanks,<br>Timothy<br>
</div>

--90e6ba6e8e2070dd2804d01a8bec--


--===============8044711677056468962==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============8044711677056468962==--

From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: Issue about domU missing interrupt
Date: Wed, 5 Dec 2012 16:34:01 +0100
Message-ID: <32870747.20121205163401@eikelenboom.it>
References: <CAKhsbWZo6XPL81Cq8U7wFA-f1ZEiOHja8_Br4D3k2QGwMN=wag@mail.gmail.com>
	<50BC7BAC.8050107@citrix.com>
	<CAKhsbWYym9Xd5ZD=PSX5EzFr-pyeYeCXcZOcZBPQMFuWtP+rwQ@mail.gmail.com>
	<50BCA6F3.8060804@citrix.com> <50BCAFEF.7040300@citrix.com>
	<CAKhsbWbx+Lt+R9rbRJOQ5+PG1jcnkB+X-qRX3SeUrS_6VCr-Ww@mail.gmail.com>
	<50BDDB6E02000078000ADA98@nat28.tlf.novell.com>
	<20121204110105.GX8912@reaktio.net>
	<28369388.20121205000539@eikelenboom.it>
	<alpine.DEB.2.02.1212051149100.8801@kaball.uk.xensource.com>
	<1662073313.20121205130222@eikelenboom.it>
	<alpine.DEB.2.02.1212051206250.8801@kaball.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <alpine.DEB.2.02.1212051206250.8801@kaball.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Mats Petersson <mats.petersson@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, "G.R." <firemeteor@users.sourceforge.net>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <JBeulich@suse.com>, Anthony Perard <anthony.perard@citrix.com>
List-Id: xen-devel@lists.xenproject.org


Wednesday, December 5, 2012, 1:07:07 PM, you wrote:

> On Wed, 5 Dec 2012, Sander Eikelenboom wrote:
>> Wednesday, December 5, 2012, 12:51:13 PM, you wrote:
>> 
>> > On Tue, 4 Dec 2012, Sander Eikelenboom wrote:
>> >> Tuesday, December 4, 2012, 12:01:05 PM, you wrote:
>> >> 
>> >> > On Tue, Dec 04, 2012 at 10:15:58AM +0000, Jan Beulich wrote:
>> >> >> >>> On 04.12.12 at 04:07, "G.R." <firemeteor@users.sourceforge.net> wrote:
>> >> >> >>  I had a quick look, and it doesn't look that hard to backport that patch.
>> >> >> > 
>> >> >> > Thanks, Mat.
>> >> >> > I'm glad to report that the patch do fix my problem.
>> >> >> > 
>> >> >> > And yest it is really easy to port since the code did not change across the
>> >> >> > two release.
>> >> >> > The only change would be line numbers (3841 vs 3803) and one extra comments
>> >> >> > before this line:
>> >> >> > 
>> >> >> >  static int pt_msix_update_one(struct pt_dev *dev, int entry_nr)
>> >> >> > 
>> >> >> > I'm not sure if you are going to release another maintenance version that
>> >> >> > include this patch,
>> >> >> > but I'll report this to Debain maintainer since it's about to freeze for
>> >> >> > v7.0 release and v4.2.0 will not make it.
>> >> >> 
>> >> >> Any thoughts on backporting this to 4.1.x, now or after 4.1.4 is
>> >> >> out?
>> >> >> 
>> >> 
>> >> > It's already in Xen 4.2, it's confirmed to fix a bug in Xen 4.1,
>> >> > so I'd say it should be a candidate for Xen 4.1.4.
>> >> 
>> >> Just tried switching the device model to "qemu-xen", seems this one isn't upstream either.
>> >> (XEN) [2012-12-04 22:49:25] vmsi.c:108:d32767 Unsupported delivery mode 3
>> >> 
>> >> Running xen-unstable as of today, with device-model "qemu-xen" for this hvm guest.
>> >> 
>> 
>> > The patch is supposed to fix a bug affecting msi_translate but in
>> > upstream QEMU we haven't implemented msi_translate at all! So in this
>> > case the cause of the bug (and as a consequence the fix) must be a
>> > different one.

Using msi_translate=0 didn't change a thing, still got "unsupported delivery mode" and a non working passthrough device.
lspci in the HVM shows MSI-X enabled for the device, but it doesn't function properly.

00:05.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) (prog-if 30 [XHCI])
        Subsystem: Micro-Star International Co., Ltd. Device 4257
        Physical Slot: 5
        Flags: bus master, fast devsel, latency 0, IRQ 36
        Memory at f3250000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [50] Power Management version 3
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [90] MSI-X: Enable+ Count=8 Masked-
        Capabilities: [a0] Express Endpoint, MSI 00
        Capabilities: [100] #1033
        Kernel driver in use: xhci_hcd


Disabling MSI completly for the HVM (by using pci=nomsi for the HVM kernel) makes passthrough device work ok with normal interrupts.

Looking into qemu-xen-dir/hw i do see xen-msi.c, so there seems to be work done in that area ?

>>
>> Ok will see if i can find out what is going on. Probably have to force msi_translate=0.
>> 
>> I noticed "qemu-xen" doesn't make a log file in /var/log/xen as "qemu-dm" does, is this expected ?

> No, it is not. You should get the usual /var/log/xen/qemu-dm-domainname.log file.

You were right, all though it lacks a bit in verbosity i guess ... the only 2 lines i'm getting are:

char device redirected to /dev/pts/17
Issued domain 25 poweroff

Instead of the 99 lines of output when using qemu-xen-traditional.


>> >> Sander
>> >> 
>> >> > -- Pasi
>> >> 
>> >> >> Jan
>> >> >> 
>> >> >> > On Mon, Dec 3, 2012 at 9:58 PM, Mats Petersson 
>> >> >> > <mats.petersson@citrix.com>wrote:
>> >> >> > 
>> >> >> >> On 03/12/12 13:19, Mats Petersson wrote:
>> >> >> >>
>> >> >> >>> On 03/12/12 13:14, G.R. wrote:
>> >> >> >>>
>> >> >> >>>> On Mon, Dec 3, 2012 at 6:15 PM, Mats Petersson
>> >> >> >>>> <mats.petersson@citrix.com 
>> >> >> > <mailto:mats.petersson@citrix.**com<mats.petersson@citrix.com>>>
>> >> >> >>>> wrote:
>> >> >> >>>>
>> >> >> >>>>      On 03/12/12 03:47, G.R. wrote:
>> >> >> >>>>
>> >> >> >>>>          Hi developers,
>> >> >> >>>>          I met some domU issues and the log suggests missing interrupt.
>> >> >> >>>>          Details from here:
>> >> >> >>>>          http://www.gossamer-threads.**com/lists/xen/users/263938#** 
>> >> >> >>>> 263938 <http://www.gossamer-threads.com/lists/xen/users/263938#263938>
>> >> >> >>>>          In summary, this is the suspicious log:
>> >> >> >>>>
>> >> >> >>>>          (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3
>> >> >> >>>>
>> >> >> >>>>          I've checked the code in question and found that mode 3 is an
>> >> >> >>>>          'reserved_1' mode.
>> >> >> >>>>          I want to trace down the source of this mode setting to
>> >> >> >>>>          root-cause the issue.
>> >> >> >>>>          But I'm not an xen developer, and am even a newbie as a xen
>> >> >> >>>> user.
>> >> >> >>>>          Could anybody give me instructions about how to enable
>> >> >> >>>>          detailed debug log?
>> >> >> >>>>          It could be better if I can get advice about experiments to
>> >> >> >>>>          perform / switches to try out etc.
>> >> >> >>>>
>> >> >> >>>>          My SW config:
>> >> >> >>>>          dom0: Debian wheezy (3.6 experimental kernel, xen 4.1.3-4)
>> >> >> >>>>          domU: Debian wheezy 3.2.x stock kernel.
>> >> >> >>>>
>> >> >> >>>>          Thanks,
>> >> >> >>>>          Timothy
>> >> >> >>>>
>> >> >> >>>>      Are you passing hardware (PCI Passthrough) to the HVM guest?
>> >> >> >>>>      What are the exact messages in the DomU?
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Yes, I'm doing PCI passthrough (the IGD, audio && USB controller).
>> >> >> >>>> But this is actually a PVHVM guest since debian stock kernel has PVOP
>> >> >> >>>> enabled.
>> >> >> >>>> And when I tried another PVOP disabled linux distro (openelec v2.0), I
>> >> >> >>>> did not see such msi related error message.
>> >> >> >>>> Actually, with that domU I do not see anything obvious wrong from the
>> >> >> >>>> log, but I also see nothing from panel (panel receive no signal and go
>> >> >> >>>> power-saving) :-(
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Back to the issue I was reporting, the domU log looks like this:
>> >> >> >>>>
>> >> >> >>>> Dec 2 21:52:44 debvm kernel: [ 1085.604071]
>> >> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >> >>>> *ERROR* Hangcheck timer elapsed... blt ring idle [waiting on 3354, at
>> >> >> >>>> 3354], missed IRQ?
>> >> >> >>>> Dec 2 21:56:50 debvm kernel: [ 1332.076071]
>> >> >> >>>> [drm:i915_hangcheck_ring_idle]
>> >> >> >>>> *ERROR* Hangcheck timer elapsed... render ring idle [waiting on 11297, at
>> >> >> >>>> 11297], missed IRQ?
>> >> >> >>>> Dec 2 22:32:48 debvm kernel: [ 7.220073] hda-intel: azx_get_response
>> >> >> >>>> timeout, switching to polling mode: last cmd=0x000f0000
>> >> >> >>>> Dec 2 22:45:32 debvm kernel: [ 776.392084] hda-intel: No response from
>> >> >> >>>> codec, disabling MSI: last cmd=0x002f0600
>> >> >> >>>> Dec 2 22:45:33 debvm kernel: [ 777.400075] hda_intel: azx_get_response
>> >> >> >>>> timeout, switching to single_cmd mode: last cmd=0x002f0600
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> Thanks,
>> >> >> >>>> Timothy
>> >> >> >>>>
>> >> >> >>> It does sound like there is a fix in 4.2.0, as indicated by Jan, that
>> >> >> >>> fixes this. I'm not fully clued up to what the policy for backporting
>> >> >> >>> fixes are, and I haven't looked at the complexity of the fix itself, but
>> >> >> >>> either updating to the 4.2.0 or a (personal) backport sounds like the
>> >> >> >>> right solution here.
>> >> >> >>>
>> >> >> >> I had a quick look, and it doesn't look that hard to backport that patch.
>> >> >> >>
>> >> >> >> --
>> >> >> >> Mats
>> >> >> >>
>> >> >> >>
>> >> >> >>> Unfortunately, I hadn't seen Jan's reply by the time I wrote my response
>> >> >> >>> to your original email.
>> >> >> >>>
>> >> >> >>> --
>> >> >> >>> Mats
>> >> >> >>>
>> >> >> >>> ______________________________**_________________
>> >> >> >>> Xen-devel mailing list
>> >> >> >>> Xen-devel@lists.xen.org 
>> >> >> >>> http://lists.xen.org/xen-devel 
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>
>> >> >> >> ______________________________**_________________
>> >> >> >> Xen-devel mailing list
>> >> >> >> Xen-devel@lists.xen.org 
>> >> >> >> http://lists.xen.org/xen-devel 
>> >> >> >>
>> >> >> 
>> >> >> 
>> >> >> 
>> >> >> _______________________________________________
>> >> >> Xen-devel mailing list
>> >> >> Xen-devel@lists.xen.org
>> >> >> http://lists.xen.org/xen-devel
>> >> 
>> >> 
>> >> 
>> 
>>