From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Peter <sw98234@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Date: Sat, 26 Aug 2006 23:46:05 +0100 [thread overview]
Message-ID: <1156632365.3007.298.camel@localhost.localdomain> (raw)
In-Reply-To: <ecpru4$9t3$1@sea.gmane.org>
Ar Sad, 2006-08-26 am 16:12 +0000, ysgrifennodd Peter:
> 2) VMWare. I have noticed recently that the errors are occurring during or
> after VMWare is run.
Then please report them to the vmware people unless you can reproduce it
from a clean boot which never touched vmware or loaded any vmware
modules.
The only real way this error can occur other than hardware is if
something crapped on the drive configuration. If it is triggered by
vmware you know who to talk to 8)
next prev parent reply other threads:[~2006-08-26 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 16:12 wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error } Peter
2006-08-26 17:41 ` Peter
2006-08-26 22:46 ` Alan Cox [this message]
2006-08-27 7:11 ` Rogier Wolff
2006-08-27 10:49 ` Peter
2006-08-27 17:44 ` RESOLVED: " Peter
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=1156632365.3007.298.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sw98234@hotmail.com \
/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