linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jure Pe??ar <pegasus@nerv.eu.org>
Cc: linux-ide@vger.kernel.org, albertl@mail.com, jgarzik@pobox.com
Subject: Re: gigabyte iRam not seen by linux
Date: Sat, 11 Mar 2006 17:58:43 +0900	[thread overview]
Message-ID: <20060311085843.GA9067@htj.dyndns.org> (raw)
In-Reply-To: <20060311092013.487c1263.pegasus@nerv.eu.org>

Hello, again.

On Sat, Mar 11, 2006 at 09:20:13AM +0100, Jure Pe??ar wrote:
> On Sat, 11 Mar 2006 12:31:43 +0900
> Tejun Heo <htejun@gmail.com> wrote:
> 
> > Can you apply the following patch and try again?
> 
> OK, now we have this:
> 
> SCSI subsystem initialized
> libata version 1.20 loaded.
> sata_nv 0000:00:0e.0: version 0.8
> ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LSA0] -> GSI 23 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:0e.0 to 64
> ata_device_add: ENTER
> ata_host_add: ENTER
> ata_port_start: prd alloc, virt ffff810076c7e000, dma 76c7e000
> ata1: SATA max UDMA/133 cmd 0xE800 ctl 0xE482 bmdma 0xE000 irq 16
> ata_host_add: ENTER
> ata_port_start: prd alloc, virt ffff810074551000, dma 74551000
> ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE082 bmdma 0xE008 irq 16
> ata_device_add: probe begin
> ata_device_add: ata1: probe begin
> ata1: SATA link up 1.5 Gbps (SStatus 113)
> ata_bus_reset: ENTER, host 1, port 0
> ata_bus_reset: devmask=0x1
> ata_bus_softreset: ata1: bus reset via SRST
> ata_dev_try_classify: dev=0, TF 00 00:01:01:00:00 a0 50

It's reporting 0x00 for FEATURE when it should report 0x01 (indicates
diagnostic passed).

> ata_bus_reset: EXIT
> ata_dev_identify: ENTER/EXIT (host 1, dev 0) -- nodev
> ata_dev_identify: ENTER/EXIT (host 1, dev 1) -- nodev
> ata_device_add: ata1: probe end
> scsi0 : sata_nv

The patch at the tail of this mail makes ata_dev_try_classify() ignore
diagnostic code in FEATURE.  If the iRam successfully gets attached
with the patch, can you please post 'hdparm -I /dev/sdX' and 'hdparm
--Istdout /dev/sdX' of the iRam?  We're pretty curious.

Jeff, this reminds me that low level drivers which don't use
ata_dev_try_classify (ahci and sil24) currently don't check the
diagnostic codes.  Any ideas how this should be dealt with?

--- a/drivers/scsi/libata-core.c
+++ b/drivers/scsi/libata-core.c
@@ -477,7 +477,7 @@ ata_dev_try_classify(struct ata_port *ap
 	else if ((device == 0) && (err == 0x81))
 		/* do nothing */ ;
 	else
-		return ATA_DEV_NONE;
+		/*return ATA_DEV_NONE*/;
 
 	/* determine if device is ATA or ATAPI */
 	class = ata_dev_classify(&tf);

  reply	other threads:[~2006-03-11  8:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10  0:36 gigabyte iRam not seen by linux Jure Pečar
2006-03-10 17:51 ` Tejun Heo
2006-03-11  2:02   ` Albert Lee
2006-03-11  2:46     ` Jure Pečar
2006-03-11  3:31       ` Tejun Heo
2006-03-11  8:20         ` Jure Pečar
2006-03-11  8:58           ` Tejun Heo [this message]
2006-03-11 16:12             ` Eric D. Mudama
2006-03-11 16:33               ` Tejun Heo
2006-03-11 16:43             ` Jure Pečar
  -- strict thread matches above, loose matches on Subject: below --
2006-03-15 19:34 Bryan Fink

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=20060311085843.GA9067@htj.dyndns.org \
    --to=htejun@gmail.com \
    --cc=albertl@mail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=pegasus@nerv.eu.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).