This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Bug when disabling/enabling a PT device with MSI enable

To: Kamala Narasimhan <Kamala.Narasimhan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Bug when disabling/enabling a PT device with MSI enabled
From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
Date: Wed, 25 Nov 2009 09:42:38 +0200
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 24 Nov 2009 23:43:04 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vvUrToG0dcHE5UeNZf7Waww/uNfm2eGR+17RJyvET7U=; b=RJBfvbX4eM2Ni9x3YWsg9RR3FHLjcaakVOp6Vmf3aKiBka2Ec9127+9mmx2npyrqjz kOZkC5hNbsyq0Ze7WC3X6Oa4uGbNWfQLxYqOEYg2xgr7sEWi8prSQY4dhwcHOEuaeDJw Ki1D3JDtISdoWo/hqV3+gBSm7KMdqEGtuV844=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=E9HdjR8RBZLK+FNw6jlZWshk+t/TUinj+D7JWQIqoYabpzUupb87isL3sKJ8bioLUY PM+qB4S6Ejr4N/U2SRR8z9sk5STvQH6OE644uVrEQ44vwi8Q1qLPfPYopnClMaO+HxFW 7FuTFEBA/se0aLBs48uqj7as8LJ07jKiNtBCs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5997D0BE578D47409D1EBD41DFD341F489F5F54E84@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <8686c3cd0911241042n1b6f84a9u3623518baa021cc2@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F489F5F54E84@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

1) It's not display, i am using a wlan device (which Windows tends to
disable and re-enable in certain cases)
2) I am using a 2.6.24 xen kernel

I will do the check with the 2.6.18 xen kernel, and see if it's
responsible for this bug.

On Wed, Nov 25, 2009 at 4:25 AM, Kamala Narasimhan
<Kamala.Narasimhan@xxxxxxxxxx> wrote:
> Couple of questions -
> 1) What kind of device are you referring to below?  Display by any chance?
> 2) Which tree is your dom0 kernel based on?
> There is a chance you are missing some msi patches in your dom0 kernel.  You 
> might want to do a quick search for msi patches in 
> http://xenbits.xen.org/staging/linux-2.6.18-xen.hg?rev=msi and see if you are 
> missing anything obvious.  I recently encountered a similar issue in a 
> slightly different situation, a subset of the problem was caused because of 
> missing msi patches.
> Kamala
>> -----Original Message-----
>> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
>> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tom Rotenberg
>> Sent: Tuesday, November 24, 2009 1:43 PM
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-devel] Bug when disabling/enabling a PT device with MSI
>> enabled
>> Hi,
>> I am using the xen-3,4, and i am doing pass-through for a device with
>> MSI enabled (the device of-course supports MSI) to a domU with Windows
>> XP. When i disable and then re-enable the device using Windows device
>> manager, everything looks like it's working fine, but the device seems
>> to malfunction.
>> After digging a little bit, i saw that the problem is, because the bit
>> of the interrupt-status (bit 3) in the status register (offset 0x6 in
>> the PCI config space) was turned on somehow -  this proibably caused
>> the MSI to malfunction (because the IntX assertion was enabled - thus
>> disabling the MSI) - and this lead to the problem i experienced.
>> Any ideas on how to solve this issue?
>> Tom
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel

Xen-devel mailing list