kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ruben Kerkhof <ruben@rubenkerkhof.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: Avi Kivity <avi@redhat.com>,
	Teck Choon Giam <giamteckchoon@gmail.com>,
	kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>,
	seabios@seabios.org
Subject: Re: system_powerdown not working for qemu-kvm 0.12.4?
Date: Fri, 15 Oct 2010 03:45:06 +0200	[thread overview]
Message-ID: <AANLkTin6CJC6LCccKhXiDYqTrnROR3Bg10baJJYM3bGE@mail.gmail.com> (raw)
In-Reply-To: <20101012071124.GA10190@morn.localdomain>

Hi Kevin,

On Tue, Oct 12, 2010 at 09:11, Kevin O'Connor <kevin@koconnor.net> wrote:
> On Tue, Oct 12, 2010 at 08:49:58AM +0200, Avi Kivity wrote:
>>  On 10/11/2010 07:53 PM, Ruben Kerkhof wrote:
>> >5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6 is the first bad commit
>> >commit 5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6
>> >Author: Kevin O'Connor<kevin@koconnor.net>
>> Gleb, Kevin, any ideas?
>>
>> (summary: qemu-kvm doesn't acpi shutdown freebsd 8.1 with this
>> commit; qemu.git does.  May be due to interrupt polarity which kvm
>> implements but qemu does not)
>
> The only thing in commit 5c99b6c9 that could cause an issue is that it
> has the compiled acpi changes actually made in commit 29f4b912, but I
> don't see how that would be a problem to reboots:
>
> diff --git a/src/acpi-dsdt.dsl b/src/acpi-dsdt.dsl
> index cee038a..2bede25 100644
> --- a/src/acpi-dsdt.dsl
> +++ b/src/acpi-dsdt.dsl
> @@ -58,7 +58,10 @@ DefinitionBlock (
>  #define prt_slot2(nr) prt_slot(nr, LNKB, LNKC, LNKD, LNKA)
>  #define prt_slot3(nr) prt_slot(nr, LNKC, LNKD, LNKA, LNKB)
>                prt_slot0(0x0000),
> -               prt_slot1(0x0001),
> +               Package() { 0x0001ffff, 0, 0, 9 },
> +               Package() { 0x0001ffff, 1, LNKB, 0 },
> +               Package() { 0x0001ffff, 2, LNKC, 0 },
> +               Package() { 0x0001ffff, 3, LNKD, 0 },
>                prt_slot2(0x0002),
>                prt_slot3(0x0003),
>                prt_slot0(0x0004),
>
> Can you confirm that commit 4c94b7ea works reliably while commit
> 5c99b6c9 does not?
>
> -Kevin
>

Yes, that's correct.

Is there anything I can do to help resolve this?
Would rolling back this commit have any impact on other operating systems?

Regards,

Ruben

  parent reply	other threads:[~2010-10-15  1:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15  1:19 system_powerdown not working for qemu-kvm 0.12.4? Teck Choon Giam
2010-05-15  9:36 ` Michael Tokarev
2010-05-16 11:52 ` Avi Kivity
2010-05-19  9:23   ` Teck Choon Giam
2010-05-19 16:22     ` Avi Kivity
2010-08-14 23:32       ` Teck Choon Giam
2010-08-15 11:00         ` Avi Kivity
2010-08-15 16:15           ` Teck Choon Giam
2010-08-15 16:19             ` Avi Kivity
2010-08-15 17:53               ` Teck Choon Giam
2010-10-07 12:30                 ` Teck Choon Giam
2010-10-11 16:29           ` Ruben Kerkhof
2010-10-11 16:57             ` Avi Kivity
2010-10-11 17:53               ` Ruben Kerkhof
2010-10-12  6:49                 ` Avi Kivity
2010-10-12  7:11                   ` Kevin O'Connor
2010-10-12  7:14                     ` Gleb Natapov
2010-10-12  7:25                       ` Avi Kivity
2010-10-12  7:33                         ` Avi Kivity
2010-10-12  7:39                           ` Avi Kivity
2010-10-12  7:40                           ` Gleb Natapov
2010-10-12  7:44                             ` Avi Kivity
2010-10-15  1:45                     ` Ruben Kerkhof [this message]
2010-10-15  7:01                       ` Gleb Natapov
2010-10-15 14:26                         ` Ruben Kerkhof
2010-10-15 15:53                           ` Teck Choon Giam

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=AANLkTin6CJC6LCccKhXiDYqTrnROR3Bg10baJJYM3bGE@mail.gmail.com \
    --to=ruben@rubenkerkhof.com \
    --cc=avi@redhat.com \
    --cc=giamteckchoon@gmail.com \
    --cc=gleb@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kvm@vger.kernel.org \
    --cc=seabios@seabios.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).