From: Jim Paris <jim@jtan.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata exception handling messages at boot on qemu
Date: Tue, 8 Jan 2008 15:17:15 -0500 [thread overview]
Message-ID: <20080108201715.GA20226@jim.sh> (raw)
In-Reply-To: <20080108192352.GA9110@basil.nowhere.org>
Andi Kleen wrote:
>
> Is there a workaround for the long ugly boot messages on sees
> with libata and qemu (0.9.0 CVS 070719)? It boots eventually, but it looks
> quite ugly.
>
> I suppose that's a qemu device model bug or could it be a Linux
> problem?
I believe this has been fixed in QEMU CVS:
http://www.mail-archive.com/qemu-devel@nongnu.org/msg11844.html
-jim
next prev parent reply other threads:[~2008-01-08 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 19:23 libata exception handling messages at boot on qemu Andi Kleen
2008-01-08 20:17 ` Jim Paris [this message]
2008-01-08 21:04 ` Alan Cox
2008-01-08 21:21 ` Andi Kleen
2008-01-08 21:19 ` Alan Cox
2008-01-08 21:37 ` Andi Kleen
2008-01-08 21:40 ` Alan Cox
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=20080108201715.GA20226@jim.sh \
--to=jim@jtan.com \
--cc=andi@firstfloor.org \
--cc=linux-ide@vger.kernel.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).