WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Problem: WIndows domu switches power off

To: "Kay, Allen M" <allen.m.kay@xxxxxxxxx>
Subject: Re: [Xen-devel] Problem: WIndows domu switches power off
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
Date: Mon, 8 Nov 2010 15:17:52 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 08 Nov 2010 06:18:51 -0800
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=dietmar.hahn@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1289225876; x=1320761876; h=from:to:subject:date:cc:references:in-reply-to: mime-version:content-transfer-encoding:message-id; z=From:=20Dietmar=20Hahn=20<dietmar.hahn@xxxxxxxxxxxxxx> |To:=20"Kay,=20Allen=20M"=20<allen.m.kay@xxxxxxxxx> |Subject:=20Re:=20[Xen-devel]=20Problem:=20WIndows=20domu =20switches=20power=20off|Date:=20Mon,=208=20Nov=202010 =2015:17:52=20+0100|Cc:=20"xen-devel@xxxxxxxxxxxxxxxxxxx" =20<xen-devel@xxxxxxxxxxxxxxxxxxx>|References:=20<2010102 60923.43691.dietmar.hahn@xxxxxxxxxxxxxx>=20<987664A83D2D2 24EAE907B061CE93D53016489A1F3@xxxxxxxxxxxxxxxxxxxxxxxxxxx m>|In-Reply-To:=20<987664A83D2D224EAE907B061CE93D53016489 A1F3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>|MIME-Version:=201.0 |Content-Transfer-Encoding:=207bit|Message-Id:=20<2010110 81517.53256.dietmar.hahn@xxxxxxxxxxxxxx>; bh=hEpOxPvwCSjmTzA8ZcMGaKESCGI6wXl0c8W+FRi3BHU=; b=NAm6bySXOa6/sbX5pao/kjzpBd8W3D354EtfHPEdQi4sHirwa4sHNP4D m6jakeiJSsUuW8m+GicXycvkgIA4vyJnc+wVnfuRDb1Qp1Bmd6esQeKKY aQ57yMSsu5LhdmRsBZi7tVNGoQdRFq5AqNcfbocQTlKDxxi25i9ys/sB4 1d7G5srcSSd/qtaR9Tp57i6BbvN3e7gqvEgxphsN1py0o+8hmMWxfdnGw kYBNBOIyEmH6uSlg+VGsJKgb61BjW;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:From:To:Subject:Date:User-Agent:Cc: References:In-Reply-To:X-KMail-Markup:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=dD8yXhkh376+SdiIT6XTSmRsjxwzmYqSHMZxKMmYye4oa/srfVydzXC7 E0Eca5ZYTGFUSc7zWwQEIdtGyqaTIaJ5pUCmSt05SWm+YTGtELx0j3fDJ fiKrlBrwuhYWPQ12h9m8cVrCo4qo28HiwasMHsHxGdGrqFYYinhMOzx35 0AJwH8QFta9eo+nOn75nuDfRmpWIz58ez9wMDS8fkDZOOSm30ajsDqEfz 5wAV0NtUe5NqyBSrjWTmQwtVlaZyq;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <987664A83D2D224EAE907B061CE93D53016489A1F3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <201010260923.43691.dietmar.hahn@xxxxxxxxxxxxxx> <987664A83D2D224EAE907B061CE93D53016489A1F3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.13.5 (Linux/2.6.34.7-0.5-xen; KDE/4.5.3; x86_64; ; )

Hi Allen,

Am 05.11.2010 schrieb ""Kay, Allen M" <allen.m.kay@xxxxxxxxx>":

> Dietmar,

>

> This is a known issue with WLAN passthrough cause by ME (management engine) interaction. The latest xen-unstable has quirk to workaround issue.

Are you think of this quirk:

http://xenbits.xensource.com/staging/xen-unstable.hg?rev/b48d8f27fca2

> Can you give it a try and let me know if it fixes the problem for you?

I looked at the sources and found your me_wifi_quirk() stuff.

But if I understand the code right, the patch doesn't help.

# lspci -n -s 00:00.0

00:00.0 0600: 8086:0044 (rev 02)

So IS_ILK(id) should be true.

But my WLAN adapter is:

10:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

# lspci -n -s 10:00.0

10:00.0 0280: 8086:422c (rev 35)

And the id 8086:422c is not in your switch statement and therewith

map_me_phantom_function() is not called.

By the way I don't see a pci device 0:22.7

> By the way, which brand of Core i5 laptop do you have. I would like to see if I have one locally.

It's a Fujitsu Lifebook S760

Following the intel spec I checked the device id of the D31:F0 device function:

00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)

# lspci -n -s 00:1f.0

00:1f.0 0601: 8086:3b07 (rev 05)

And this is the Intel® QM57 Chipset.

Thanks.

Dietmar.

For your information:

# lspci

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)

00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)

00:16.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller (rev 06)

00:16.3 Serial controller: Intel Corporation 5 Series/3400 Series Chipset KT Controller (rev 06)

00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05)

00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)

00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)

00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)

00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)

00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)

00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)

00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05)

00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)

00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)

10:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)

ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)

ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)

ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)

ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

>

> Allen

>

> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dietmar Hahn

> Sent: Tuesday, October 26, 2010 12:24 AM

> To: xen-devel@xxxxxxxxxxxxxxxxxxx

> Subject: [Xen-devel] Problem: WIndows domu switches power off

>

>

> Hi list,

>

> I have a special effect on a Laptop with:

>

> cpu: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz with integrated graphics

>

> Chipsatz: Intel QM57

>

> with SLES11 SP1 (xen-4.0 with some patches from Novell)

>

> I passed through the sound and WLAN pci controller to the guest.

>

> I start a Windows 7 guest and while installing the driver for the WLAN

>

> controller within Windows the power of the notebook got switched off.

>

> I couldnt see any message on the serial console.

>

> I tried Windows on bare metall and all runs very well. Later on starting this

>

> Windows guest again the power got switched of after login into Windows - maybe

>

> the WLAN driver got started there.

>

> For a test I prepared a OpenSuSE 11.3 as HVM guest and were able to configure

>

> the WLAN device without any problems.

>

> And here I need some assistance to prevent the power off and to add some tracer

>

> in the hypervisor.

>

> By the way I have no problems with the sound device.

>

> If wanted I can add more informations.

>

> Thanks.

>

> Dietmar.

--

Company details: http://ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel