From: Robert Hancock <hancockrwd@gmail.com>
To: Andrei Martynov <andrei.martynov@web.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: porting IDE patches to PATA driver
Date: Fri, 03 Jul 2009 19:17:41 -0600 [thread overview]
Message-ID: <4A4EADB5.6070609@gmail.com> (raw)
In-Reply-To: <149127909.20090703115022@web.de>
On 07/03/2009 03:50 AM, Andrei Martynov wrote:
> Monday, June 29, 2009, 4:53:49 PM, Alan Cox wrote:
>
>> The only other thing I can see is the way it hangs around waiting a bit
>> for the DMA to finish after the DMA completion event occurs - that might
>> be your problem if they goofed and reported DMA complete too early.
>
> Thank you very much for your advices. Reading from disk works fine now
> but writing attempt results in a series of similar error messages.
> What is the meaning of this error? Is there any documentation that may
> be useful to understand libata error messages?
>
> ~ # cp /hdd/c/Test/test.dat /hdd/d
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: BMDMA stat 0x6
BMDMA status 0x6 means DMA failed because the adapter encountered an
error transferring data to/from host memory (from the PCI ATA host
adapter spec). Some problem in the adapter setup?
> ata1.00: cmd 35/00:98:40:6f:fe/00:01:20:00:00/e0 tag 0 dma 208896 out
> res 50/00:00:d7:70:fe/00:00:20:00:00/e0 Emask 0x20 (host bus error)
> ata1.00: status: { DRDY }
> jasper_set_piomode: devno = 0
> jasper_tune_chipset: slave = 0 speed = 0x0c
> jasper_set_dmamode: devno = 0
> jasper_tune_chipset: slave = 0 speed = 0x22
> ata1.00: configured for MWDMA2
> ata1: EH complete
> sd 0:0:0:0: [sda] 586070255 512-byte hardware sectors (300068 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> ata1.00: BMDMA stat 0x6
> ata1.00: cmd 35/00:a0:b0:72:fe/00:01:20:00:00/e0 tag 0 dma 212992 out
> res 50/00:00:4f:74:fe/00:00:20:00:00/e0 Emask 0x20 (host bus error)
> ata1.00: status: { DRDY }
> jasper_set_piomode: devno = 0
> jasper_tune_chipset: slave = 0 speed = 0x0c
> jasper_set_dmamode: devno = 0
> jasper_tune_chipset: slave = 0 speed = 0x22
> ata1.00: configured for MWDMA2
> ata1: EH complete
>
>
prev parent reply other threads:[~2009-07-04 1:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 8:09 porting IDE patches to PATA driver Andrei Martynov
2009-06-25 8:23 ` Alan Cox
2009-06-25 8:38 ` Re[2]: " Andrei Martynov
2009-06-25 9:05 ` Alan Cox
2009-06-25 10:30 ` Re[2]: " Andrei Martynov
2009-06-25 11:29 ` Alan Cox
2009-06-26 13:24 ` Re[2]: " Andrei Martynov
2009-06-26 13:46 ` Alan Cox
2009-06-26 14:40 ` Re[2]: " Andrei Martynov
2009-06-26 16:21 ` Alan Cox
2009-06-28 20:33 ` Sergei Shtylyov
2009-06-29 12:31 ` Alan Cox
2009-06-29 12:01 ` Re[2]: " Andrei Martynov
2009-06-29 14:53 ` Alan Cox
2009-07-03 9:50 ` Re[2]: " Andrei Martynov
2009-07-04 1:17 ` Robert Hancock [this message]
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=4A4EADB5.6070609@gmail.com \
--to=hancockrwd@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrei.martynov@web.de \
--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).