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: Mon, 14 Jan 2013 04:28:48 +0100 Message-ID: <50F37B70.2070202@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> <50D46534.2010304@invisiblethingslab.com> <50E554C302000078000B29BA@nat28.tlf.novell.com> <50F10B33.9040705@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1724813227148980910==" Return-path: In-Reply-To: <50F10B33.9040705@invisiblethingslab.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) --===============1724813227148980910== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4E51A3B9FA98E8072B0FF650" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4E51A3B9FA98E8072B0FF650 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12.01.2013 08:05, Marek Marczykowski wrote: > On 03.01.2013 09:52, Jan Beulich wrote: >>>>> On 21.12.12 at 14:33, Marek Marczykowski >> wrote: >>> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>>> On 21.12.12 at 05:52, Marek Marczykowski =20 >>> 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 orig= inal=20 >>>>> symptom >>>>>> - only CPU0 active after ACPI S3. Didn't get reboot after few trie= s. >>>>>> "xl debug-key r" output attached. >>>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and = 4.1.3 - 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 >>>> >>>> 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= =20 >>> compiled from above c/s. >> >> Are you saying that on 4.1.4 this doesn't take effect? Are there >> any log messages indicating so? The above being the top most >> change to sched_credit.c, this difference in behavior pretty odd. >=20 > I can no longer reproduce this bug on 4.1.3-rc1-pre (above sched_credit= c/s) > with or without sched_ratelimit_us=3D0. So it must be some mistake duri= ng > previous testing. > Also the problem from email subject is rather rare and not observed aft= er ~20 > suspend-resume cycles... >=20 > Just to summary: > 4.1.3-rc1-pre (above sched_credit c/s) - works ok > 4.1.4 regardless of sched_ratelimit_us=3D0 reboots at resume > 4.1.5-pre reboots at resume regardless of sched_ratelimit_us option > 4.1.5-pre with "Introduce system_state variable" reverted works fine - > regardless of sched_ratelimit_us option >=20 > "4.1.5-pre" was c/s 23436:2ae6267371d8, but still the same effects on > 23441:2a91623a5807. Just after sending this email I've suspended laptop (running 4.1.5-pre wi= th above commit reverted, but without sched_ratelimit_us=3D0 option). After = few hours it hanged at resume (don't know at which state, but somehow early -= before reinitialize of console). The same xen version suspended for short= er time period (2-5min) resumed without problem. I've retried suspend for 4-= 5h and got reboot. The same version (still with "system_state" commit reverted), but _with_ sched_ratelimit_us=3D0 resumes well even after many hours. So sched_ratelimit_us option makes some difference even on most recent 4.= 1 xen, but it needs patience to spot it... Maybe above "works ok" for 4.1.3-rc1-pre isn't really true because I've t= ested short suspend periods. --=20 Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab --------------enig4E51A3B9FA98E8072B0FF650 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 undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ83twAAoJENuP0xzK19csoLEH/j9emQkHhJbXHAdz3rReZQjI Oa64APzvCbCvTPrZEuoLdd/Ilae330F/M0yQNadIrYla9bfLbGDBkNGS4IHS6uCl 9+GqQF84/RxpQa6iu9MVoNMq/MxC/U+ZVoLeGeq1vBG7HarbGXBQpHVBzgcUpn7s KJ/2ch6CaQJgNjrhk6C3tz1IUeuKxOt10CobJR7ENXN2ugtQ2U4GtUAv/7hj+Hvx PSOC8AeV7QLP0FMAIOHyBDm59ThwXX3aaYPkbvQgXADIx9C8JbWpJblhzJ4LKSuJ VMZt3VoWvmBlsA5u3lPjY2Kkr012uisHwFGgc6yD/Cxo1OCHQ0B5AVXAxidpqqY= =QXYY -----END PGP SIGNATURE----- --------------enig4E51A3B9FA98E8072B0FF650-- --===============1724813227148980910== 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 --===============1724813227148980910==--