All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Sporadic AHCI boot failures
Date: Tue, 05 Jun 2012 21:08:46 +0200	[thread overview]
Message-ID: <4FCE593E.5020708@siemens.com> (raw)
In-Reply-To: <4FA27754.1070005@siemens.com>

On 2012-05-03 14:17, Jan Kiszka wrote:
> On 2012-05-02 18:26, Alexander Graf wrote:
>>
>>
>> On 02.05.2012, at 20:14, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>
>>> Hi,
>>>
>>> I'm running a Win7 VM over AHCI, rebooting quite frequently. Depending
>>> on host system load, I'm facing a lot of sporadic boot failures (disk
>>> not found), obviously in SeaBIOS. Could it be that some timeout in the
>>> init code bites us here? AHCI_LINK_TIMEOUT or AHCI_RESET_TIMEOUT? Just a
>>> guess, I haven't debugged this yet.
>>
>> Hm, I'd be surprised if that's the problem.
>>
>> 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...

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-06-05 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 18:14 [Qemu-devel] Sporadic AHCI boot failures Jan Kiszka
2012-05-02 21:26 ` Alexander Graf
2012-05-03 12:17   ` Jan Kiszka
2012-06-05 19:08     ` Jan Kiszka [this message]
2012-06-06  7:53       ` Avi Kivity

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=4FCE593E.5020708@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.