From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Marczykowski Subject: Re: Only CPU0 active after ACPI S3, xen 4.1.3 Date: Fri, 21 Dec 2012 14:33:40 +0100 Message-ID: <50D46534.2010304@invisiblethingslab.com> References: <50B7AF8A.5010304@invisiblethingslab.com> <50B88B8402000078000ACC4C@nat28.tlf.novell.com> <50B8D9A9.60502@invisiblethingslab.com> <50B8DAEA0200007800090B69@nat28.tlf.novell.com> <50B8DC55.8000308@invisiblethingslab.com> <50BC653E02000078000AD28C@nat28.tlf.novell.com> <50BDFA38.7030009@invisiblethingslab.com> <50D335E6.902@invisiblethingslab.com> <50D39C73.906@invisiblethingslab.com> <50D3EB03.4000109@invisiblethingslab.com> <50D4322102000078000B1F80@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6756500380364205732==" Return-path: In-Reply-To: <50D4322102000078000B1F80@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Ben Guthro , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============6756500380364205732== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig402B9D1679D83C05483AA8CA" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig402B9D1679D83C05483AA8CA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 21.12.2012 09:55, Jan Beulich wrote: >>>> On 21.12.12 at 05:52, Marek Marczykowski wrote: >> On 21.12.2012 00:17, Marek Marczykowski wrote: >>> With this patch applied (on 4.1.4 and 4.3-unstable), I've got origina= l=20 >> symptom >>> - only CPU0 active after ACPI S3. Didn't get reboot after few tries. >>> "xl debug-key r" output attached. >>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1= =2E3 - on >>> 4.1.2 none of above problems happened. >> >> I've done bisect on xen 4.1 and found problematic commit: >> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427=20 >=20 > In that case, using "sched_ratelimit_us=3D0" should make the > problem go away again - did you try that? This option does not help when trying 4.1.4, but does when trying xen com= piled from above c/s. >> Unfortunately in xen-unstable parent of corresponding commit still hav= e the >> same problem, so there must be something more wrong. >=20 > Which is why we'd need to be really certain that the c/s you > spotted really is relevant here (to me it doesn't look like having > an effect on resume at all). So perhaps there is other problematic commit, which was backported to 4.1= later (than it is in xen-unstable). --=20 Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab --------------enig402B9D1679D83C05483AA8CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ1GU1AAoJENuP0xzK19csBA8H/i1yKq5VPr0QFy4V4QkN2kEq 4ylSiLI+W5YWHsqOjc1JLgw00nTQQxNCUE/KTZWJ44Ho9gb8cymFXWL/bYgm/15d qShC5tUssba5lE7ZLCaZPIravavbPkPIem6yjHDZhLndBAUsLOCV2kfEFAe/bvVv CCBHlRA0NTJX4URoyk27iCi/xD/chJjdWvkAa0o2Am/0e5l6g5b9MxUOCbHMt0tl lkMKezh6iNBggC1m0WgG6bqgw+SWnyhj//KFoSrV2YKRJ6RUH6OtBB4QtGd/u8c3 AF+6/EoQhEccqhdtu5V5R7H7PGtJgvCgtE/GhO8IDUj1/TO/eIiaCd7SFu2hxc0= =bYdT -----END PGP SIGNATURE----- --------------enig402B9D1679D83C05483AA8CA-- --===============6756500380364205732== 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 --===============6756500380364205732==--