From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:37371)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1ScB3b-0004aR-Aq
	for qemu-devel@nongnu.org; Wed, 06 Jun 2012 03:53:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1ScB3T-00032I-Um
	for qemu-devel@nongnu.org; Wed, 06 Jun 2012 03:53:30 -0400
Received: from mx1.redhat.com ([209.132.183.28]:39069)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1ScB3T-000325-MU
	for qemu-devel@nongnu.org; Wed, 06 Jun 2012 03:53:23 -0400
Message-ID: <4FCF0C6C.6050206@redhat.com>
Date: Wed, 06 Jun 2012 10:53:16 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4FA17998.9040001@siemens.com>
	<1B2F3665-DC41-4553-800E-D14A0F876553@suse.de>
	<4FA27754.1070005@siemens.com> <4FCE593E.5020708@siemens.com>
In-Reply-To: <4FCE593E.5020708@siemens.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Sporadic AHCI boot failures
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Kevin Wolf <kwolf@redhat.com>, "Ren, Yongjie" <yongjie.ren@intel.com>, Marcelo Tosatti <mtosatti@redhat.com>, Alexander Graf <agraf@suse.de>, qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>

On 06/05/2012 10:08 PM, Jan Kiszka wrote:
>>>
>>> Do things work again after system_reset on the monitor? Maybe the reset function is just broken and we finish some asynchronous stuff after reset?
>> 
>> The problem both occurs after power on as well as reset. Sometimes it
>> takes multiple system_reset calls to get the system booting.
> 
> Think I found it: There is bug in the new in-kernel PIT userspace code
> that lets Seabios detect some 4..7 MHz CPU. So all the timeouts finish
> way too early. This also affects IDE and possible other stuff in the
> bios that depends on timeouts.
> 
> Digging into this...
> 

This is probably Yongjie Ren's problem as well.


-- 
error compiling committee.c: too many arguments to function