On Fri, Oct 15, 2010 at 03:45:06AM +0200, Ruben Kerkhof wrote:
Is there anything I can do to help resolve this?
Would rolling back this commit have any impact on other operating systems?
Patch below should fix the problem.
diff --git a/src/acpi-dsdt.dsl b/src/acpi-dsdt.dsl
index
On Fri, Oct 15, 2010 at 09:01, Gleb Natapov g...@redhat.com wrote:
On Fri, Oct 15, 2010 at 03:45:06AM +0200, Ruben Kerkhof wrote:
Is there anything I can do to help resolve this?
Would rolling back this commit have any impact on other operating systems?
Patch below should fix the problem.
Thanks a lot for all :)
Kindest regards,
Giam Teck Choon
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Kevin,
On Tue, Oct 12, 2010 at 09:11, Kevin O'Connor ke...@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
On 10/11/2010 07:53 PM, Ruben Kerkhof wrote:
On Mon, Oct 11, 2010 at 18:57, Avi Kivitya...@redhat.com wrote:
On 10/11/2010 06:29 PM, Ruben Kerkhof wrote:
Hi Avi,
On Sun, Aug 15, 2010 at 13:00, Avi Kivitya...@redhat.comwrote:
I'm betting 73b48d914f9 is the cause, but let's
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'Connorke...@koconnor.net
Gleb, Kevin, any ideas?
On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor 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
On 10/12/2010 09:14 AM, Gleb Natapov wrote:
On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor 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
On 10/12/2010 09:25 AM, Avi Kivity wrote:
On 10/12/2010 09:14 AM, Gleb Natapov wrote:
On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor wrote:
On Tue, Oct 12, 2010 at 08:49:58AM +0200, Avi Kivity wrote:
On 10/11/2010 07:53 PM, Ruben Kerkhof wrote:
On 10/12/2010 09:33 AM, Avi Kivity wrote:
Aha! The piix4 specification updates says:
• IRQ9OUT#/GPO29 should be labeled as IRQ9OUT/GPO29
Even more explicitly:
14. IRQ9OUT# Is Active HI
Problem: The signal identified as IRQ9OUT#/GPO29, pin F3, is not
active level LO, it is active
On Tue, Oct 12, 2010 at 09:33:42AM +0200, Avi Kivity wrote:
On 10/12/2010 09:25 AM, Avi Kivity wrote:
On 10/12/2010 09:14 AM, Gleb Natapov wrote:
On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor wrote:
On Tue, Oct 12, 2010 at 08:49:58AM +0200, Avi Kivity wrote:
On 10/11/2010 07:53
On 10/12/2010 09:40 AM, Gleb Natapov wrote:
• IRQ9OUT#/GPO29 should be labeled as IRQ9OUT/GPO29
So it looks like it should be active high, and seabios is wrong in
listing it as active low. Perhaps other OSes have quirks to force it
to active high.
It is even stranger then that.
Hi Avi,
On Sun, Aug 15, 2010 at 13:00, Avi Kivity a...@redhat.com wrote:
I'm betting 73b48d914f9 is the cause, but let's see the full bisect.
system_powerdown with FreeBSD 8.1 works on 73b48d914f9.
I've bisected the issue to commit 76e617c.
Let me know if I should do some other tests.
On 10/11/2010 06:29 PM, Ruben Kerkhof wrote:
Hi Avi,
On Sun, Aug 15, 2010 at 13:00, Avi Kivitya...@redhat.com wrote:
I'm betting 73b48d914f9 is the cause, but let's see the full bisect.
system_powerdown with FreeBSD 8.1 works on 73b48d914f9.
I've bisected the issue to commit 76e617c.
On Mon, Oct 11, 2010 at 18:57, Avi Kivity a...@redhat.com wrote:
On 10/11/2010 06:29 PM, Ruben Kerkhof wrote:
Hi Avi,
On Sun, Aug 15, 2010 at 13:00, Avi Kivitya...@redhat.com wrote:
I'm betting 73b48d914f9 is the cause, but let's see the full bisect.
system_powerdown with FreeBSD 8.1
On Mon, Aug 16, 2010 at 1:53 AM, Teck Choon Giam
giamteckch...@gmail.com wrote:
On Mon, Aug 16, 2010 at 12:19 AM, Avi Kivity a...@redhat.com wrote:
On 08/15/2010 07:15 PM, Teck Choon Giam wrote:
Let me know if I have done anything wrong about the bisecting... ...
All looks fine, but what
On 08/15/2010 02:32 AM, Teck Choon Giam wrote:
Can you try to bisect between qemu-kvm-0.12.3 and 0.12.4 to see which commit
introduced the regression?
Actually I am not so sure about how to do the bisecting as the below
steps always produce different configure for me. Any pointers?
# cd
That's fine - you'll be running upstream qemu instead of qemu-kvm. Just
remember to add -enable-kvm to the command line. Use ./configure
--target-list=x86_64-softtmmu to cut down on compile time.
Yes, I am doing so about the --target-list but missed out the
-enable-kvm command option prior
On 08/15/2010 07:15 PM, Teck Choon Giam wrote:
Let me know if I have done anything wrong about the bisecting... ...
All looks fine, but what are the results? git should say something like
'x is first bad commit' which is the interesting part.
--
error compiling committee.c: too
Hi Avi,
Sorry for such super late reply as I have been caught up with personal
matters thus unable to do testing etc.
The following are my report about system_powerdown on various versions:
system_powerdown Status Report:
|=|
| Version
On Sun, May 16, 2010 at 7:52 PM, Avi Kivity a...@redhat.com wrote:
On 05/15/2010 04:19 AM, Teck Choon Giam wrote:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
Compared with what version?
--
error compiling
On 05/19/2010 12:23 PM, Teck Choon Giam wrote:
On Sun, May 16, 2010 at 7:52 PM, Avi Kivitya...@redhat.com wrote:
On 05/15/2010 04:19 AM, Teck Choon Giam wrote:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
On 05/15/2010 04:19 AM, Teck Choon Giam wrote:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
Compared with what version?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this
15.05.2010 05:19, Teck Choon Giam пишет:
Hi,
Anyone encountered the same issue as me about system_powerdown no
longer working since upgraded to qemu-kvm 0.12.4?
Works For Me (tm)
Tried with winXP and win7 and linux guests.
/mjt
--
To unsubscribe from this list: send the line unsubscribe kvm
24 matches
Mail list logo
