linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: James Andrewartha <jamesa@daa.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk, htejun@gmail.com
Subject: Re: SC1200 failure in 2.6.23 and 2.6.24-rc1-git10
Date: Wed, 07 Nov 2007 17:31:11 -0500	[thread overview]
Message-ID: <47323CAF.2030102@rtr.ca> (raw)
In-Reply-To: <20071107211932.M35475@visp.net.lb>

Denys Fedoryshchenko wrote:
> On Wed, 07 Nov 2007 14:12:55 -0500, Mark Lord wrote
>>> WRAP ~ #./hdparm -I /dev/hda
>>>
>>> /dev/hda:
>>>
>>> ATAPI Write-once device, with non-removable media
>>>         Model Number:       SanDisk SDP3B-16
>>>         Serial Number:      24313671615
>>>         Firmware Revision:  vdd 1.00
>>> Standards:
>>>         Likely used: 3
>>> Configuration:
>>>         DRQ response: 50us.
>>>         Packet size: Unknown
>>> Capabilities:
>>>         LBA, IORDY(may be)(cannot be disabled)
>>>         Buffer size: 1.0kB      bytes avail on r/w long: 4
>>>         DMA: not supported
>>>         PIO: pio0 pio1
>> "ATAPI Write-once device"  ???
>>
>> That cannot be correct (??).  Is this with hdparm-7.7 (latest 
>> sourceforge) ?? Can you show us the "hdparm --Istdout" output as 
>> well, please.
>>
>> thanks.
> Yes latest hdparm-7.7.
...

> WRAP ~ #./hdparm --Istdout /dev/hda
> 
> /dev/hda:
> 844a 01ea 0000 0002 0000 0240 0020 0000
..

CFA spec requires 848a in word[0], not 844a, which explains
why hdparm thought it might be ATAPI.  I've updated my hdparm
source to detect this for hdparm-7.8 (unreleased).
That card (16MB) is definitely buggy.
But your other (1GB) card looks fine.

Thanks.  Somebody else may help with the libata issue.




  reply	other threads:[~2007-11-07 22:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071101213013.M54162@visp.net.lb>
2007-11-07  6:15 ` SC1200 failure in 2.6.23 and 2.6.24-rc1-git10 Andrew Morton
2007-11-07 13:27   ` Denys Fedoryshchenko
2007-11-07 15:23     ` James Andrewartha
2007-11-07 16:06       ` Denys Fedoryshchenko
2007-11-07 19:12         ` Mark Lord
2007-11-07 21:22           ` Denys Fedoryshchenko
2007-11-07 22:31             ` Mark Lord [this message]
2007-11-07 22:54               ` Alan Cox
2007-11-07 21:36           ` Denys Fedoryshchenko
2007-11-07 23:20           ` Jeff Garzik
2007-11-07 23:24             ` Mark Lord
2007-11-07 23:49             ` Denys Fedoryshchenko
2007-11-08  0:01             ` Denys Fedoryshchenko
2007-11-08  0:30               ` Bartlomiej Zolnierkiewicz
2007-11-08  7:16                 ` Denys Fedoryshchenko
2007-11-08 10:48                   ` Alan Cox
2007-11-08 16:44                     ` Denys Fedoryshchenko
2007-11-08 17:31                       ` Jeff Garzik
2007-11-08 19:56                         ` Denys Fedoryshchenko
2007-11-08 22:40                           ` Alan Cox
2007-11-09  1:44                           ` Tejun Heo
     [not found] <fa.FFqM2AneKZLH2d3/UIeCMjE/RLE@ifi.uio.no>
2007-11-08  1:41 ` Robert Hancock
2007-11-08  7:01   ` Denys Fedoryshchenko

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=47323CAF.2030102@rtr.ca \
    --to=liml@rtr.ca \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=denys@visp.net.lb \
    --cc=htejun@gmail.com \
    --cc=jamesa@daa.com.au \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).