From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <andi@firstfloor.org>, linux-ide@vger.kernel.org
Subject: Re: libata exception handling messages at boot on qemu
Date: Tue, 8 Jan 2008 22:21:09 +0100 [thread overview]
Message-ID: <20080108212109.GA2403@one.firstfloor.org> (raw)
In-Reply-To: <20080108210428.63c90f9d@lxorguk.ukuu.org.uk>
On Tue, Jan 08, 2008 at 09:04:28PM +0000, Alan Cox wrote:
> On Tue, 8 Jan 2008 20:23:52 +0100
> Andi Kleen <andi@firstfloor.org> 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?
>
> libata actually bothers to check things like data directions and device
> state. This as far as I can tell is a qemu bug. I did look at the
> relevant code but it was so vomitously horrible I didn't investigate in
> detail. I believe the Xen qemu fork is ok ?
It's fixed in qemu CVS as Jim pointed out. Still it's a little annoying
to always have to update qemu from rpms to CVS.
Since I assume that qemu code base is wide spread and if a workaround
is not too ugly I think it would be nice if the kernel handled that.
-Andi
next prev parent reply other threads:[~2008-01-08 21:18 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
2008-01-08 21:04 ` Alan Cox
2008-01-08 21:21 ` Andi Kleen [this message]
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=20080108212109.GA2403@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).