From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: High CPU temp, suspend problem - xen 4.1.5-pre, linux 3.7.x
Date: Tue, 26 Mar 2013 13:17:16 +0100 [thread overview]
Message-ID: <515191CC.6060609@invisiblethingslab.com> (raw)
In-Reply-To: <20130325141701.GI11546@phenom.dumpdata.com>
[-- Attachment #1.1: Type: text/plain, Size: 4093 bytes --]
On 25.03.2013 15:17, Konrad Rzeszutek Wilk wrote:
> On Mon, Mar 25, 2013 at 12:36:31PM +0100, Marek Marczykowski wrote:
>> On 22.03.2013 17:56, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Mar 22, 2013 at 04:34:11PM +0100, Marek Marczykowski wrote:
>>> This reminds me of something. I recall a long long time ago seeing something like this....
>>> Completly forgot about this until now. The difference was whether the Xen's cpu_idle
>>> as running a) the acpi_idle (so using the different C-states), or b) the default one
>>> (so just using HLT).
>>>
>>> With the b), during resume it would get half-way through
>>> (http://darnok.org/xen/devel.acpi-s3.v1.serial.log) while with a) it would actually
>>> continue on - http://darnok.org/xen/devel.acpi-s3.v0.serial.log
>>>
>>> This was on some MSI MS-7680/H61M-P23 (MS-7680) motherboard.
>>>
>>> Oh look: http://lists.xen.org/archives/html/xen-devel/2011-06/msg02059.html
>>>
>>> And it looks Kevin's recommendation was use the a) case with max_cstates=1
>>> to narrow it down.
>>
>> When default_idle used, resume doesn't work at all (even the first one). Details:
>> (1) With max_cstates=1, without xen-acpi-processor module: default_idle used.
>> Suspend succeed, but always hang at resume.
>
> AHA! So the bug persist.
>>
>> (2) With max_cstate=1, with xen-acpi-processor module loaded: acpi_idle used.
>> Suspend succeed, resume also, but after resume above problem exists (high
>> temperature, C2-C3 states only present on CPU0, subsequent suspends always
>> ends up with reboot).
>>
>> (3) Without max_cstate=1, with xen-acpi-processor module loaded: same as (2).
>>
>> (4) Without max_cstate=1, without xen-acpi-processor module loaded: same as (1).
>>
>> One more observation: when xen compiled with debug=y, (2) and (4) cases
>> behaves the same as (1).
>
> Oh, that is something new.
Finally got serial console :)
The debug=y problem is (actually at resume):
(XEN) Assertion 'test_bit(vector, cfg->used_vectors)' failed at io_apic.c:542
(XEN) ----[ Xen-4.1.5-rc1 x86_64 debug=y Tainted: C ]----
(XEN) CPU: 0
(XEN) RIP: e008:[<ffff82c48015e288>] smp_irq_move_cleanup_interrupt+0x1c3/0x23d
(XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor
(XEN) rax: 0000000000000000 rbx: 00000000000000e9 rcx: ffff82c48029ff18
(XEN) rdx: 00000000000000e9 rsi: 000000000000002a rdi: ffff830421060538
(XEN) rbp: ffff82c48029ff08 rsp: ffff82c48029feb8 r8: ffff88041820eb60
(XEN) r9: 0000000000000000 r10: 0000000000007ff0 r11: 0000000000000000
(XEN) r12: ffff830421080250 r13: ffff830421060534 r14: ffff82c48029ff18
(XEN) r15: ffff82c4802dd9e0 cr0: 000000008005003b cr4: 00000000000026f0
(XEN) cr3: 0000000300b81000 cr2: ffff880402070198
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008
(XEN) Xen stack trace from rsp=ffff82c48029feb8:
(XEN) 0000000000000000 000000000000e030 ffff82c48029ff18 ffff82c4802dd9e0
(XEN) ffff8802cac3c7c0 00000000ffff3729 00000000ffff3729 000000013fff3728
(XEN) ffffffff81b907c0 00000000ffff3729 00007d3b7fd600c7 ffff82c48014de60
(XEN) 00000000ffff3729 ffffffff81b907c0 000000013fff3728 00000000ffff3729
(XEN) ffffffff81a01e18 00000000ffff3729 0000000000000000 0000000000007ff0
(XEN) 0000000000000000 ffff88041820eb60 ffff8803fd1820a8 ffffffff81b90a88
(XEN) 000000000000002a 000000000000002a 00000000ffff372a 0000002000000000
(XEN) ffffffff8105dd5a 000000000000e033 0000000000000246 ffffffff81a01db8
(XEN) 000000000000e02b 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 ffff8300ca9a0000 0000000000000000
(XEN) 0000000000000000
(XEN) Xen call trace:
(XEN) [<ffff82c48015e288>] smp_irq_move_cleanup_interrupt+0x1c3/0x23d
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion 'test_bit(vector, cfg->used_vectors)' failed at io_apic.c:542
(XEN) ****************************************
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 553 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-26 12:17 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 20:50 High CPU temp, suspend problem - xen 4.1.5-pre, linux 3.7.x Marek Marczykowski
2013-03-15 3:00 ` Dario Faggioli
2013-03-15 3:22 ` Marek Marczykowski
2013-03-15 13:02 ` Konrad Rzeszutek Wilk
2013-03-22 15:34 ` Marek Marczykowski
2013-03-22 16:56 ` Konrad Rzeszutek Wilk
2013-03-25 11:36 ` Marek Marczykowski
2013-03-25 14:17 ` Konrad Rzeszutek Wilk
2013-03-25 14:56 ` Marek Marczykowski
2013-03-26 12:17 ` Marek Marczykowski [this message]
2013-03-26 13:11 ` Jan Beulich
2013-03-26 13:50 ` Marek Marczykowski
2013-03-26 15:47 ` Andrew Cooper
2013-03-26 16:12 ` Andrew Cooper
2013-03-26 16:47 ` Marek Marczykowski
2013-03-26 16:03 ` Jan Beulich
2013-03-26 16:45 ` Marek Marczykowski
2013-03-26 17:02 ` Andrew Cooper
2013-03-26 17:42 ` Marek Marczykowski
2013-03-26 17:54 ` Andrew Cooper
2013-03-26 18:21 ` Marek Marczykowski
2013-03-26 18:50 ` Andrew Cooper
2013-03-27 8:50 ` Marek Marczykowski
2013-03-27 8:58 ` Jan Beulich
2013-03-27 8:52 ` Jan Beulich
2013-03-27 9:03 ` Jan Beulich
2013-03-27 14:01 ` Marek Marczykowski
2013-03-27 14:31 ` Marek Marczykowski
2013-03-27 14:46 ` Andrew Cooper
2013-03-27 14:49 ` Marek Marczykowski
2013-03-27 15:51 ` Marek Marczykowski
2013-03-27 16:27 ` Andrew Cooper
2013-03-27 18:16 ` Marek Marczykowski
2013-03-27 18:56 ` Andrew Cooper
2013-03-28 14:43 ` Marek Marczykowski
2013-03-28 10:50 ` Jan Beulich
2013-03-28 11:53 ` Andrew Cooper
2013-03-28 12:54 ` Jan Beulich
2013-03-28 13:19 ` Jan Beulich
2013-03-27 14:52 ` Andrew Cooper
2013-03-27 15:47 ` Konrad Rzeszutek Wilk
2013-03-27 16:56 ` Andrew Cooper
2013-03-27 17:15 ` Marek Marczykowski
2013-03-28 17:41 ` Andrew Cooper
2013-03-28 17:44 ` Marek Marczykowski
2013-03-28 17:50 ` Andrew Cooper
2013-03-29 0:26 ` Marek Marczykowski
2013-03-28 16:13 ` Jan Beulich
2013-03-28 19:03 ` Marek Marczykowski
2013-04-01 13:53 ` Ben Guthro
2013-04-02 1:13 ` Marek Marczykowski
2013-04-02 14:05 ` Konrad Rzeszutek Wilk
2013-04-15 22:09 ` Marek Marczykowski
2013-04-15 23:36 ` Ben Guthro
2013-04-15 23:51 ` konrad wilk
2013-04-16 0:19 ` Ben Guthro
2013-04-16 0:46 ` Ben Guthro
2013-04-16 3:20 ` konrad wilk
2013-04-16 1:02 ` Marek Marczykowski
2013-04-16 8:47 ` Jan Beulich
2013-04-16 11:49 ` Ben Guthro
2013-04-16 11:57 ` Jan Beulich
2013-04-16 12:09 ` Ben Guthro
2013-04-16 12:51 ` Jan Beulich
2013-03-28 16:25 ` Jan Beulich
2013-03-28 16:31 ` Marek Marczykowski
2013-03-28 16:52 ` Jan Beulich
2013-03-28 17:09 ` Marek Marczykowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515191CC.6060609@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).