public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: david@lang.hm
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Intel X25E doesn't work with nv sata in current kernels
Date: Tue, 19 May 2009 15:57:05 +0900	[thread overview]
Message-ID: <4A125841.5000608@kernel.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0905181041310.15782@asgard>

david@lang.hm wrote:
> according to but 12703 ( http://bugzilla.kernel.org/show_bug.cgi?id=12703 )
> this worked with older kernels, but with 2.6.29.[13] and 2.6.30-rc6
> 
> according to this ticket it did work with older vendor kernels, but it's
> not clear which ones (and no older vanilla kernels)
> 
> I have verified that this drive does work on a PCI controller card in
> the same machine (with the same cables), so this is definantly a
> controller/kernel issue
> 
> booting with libata.force=#:nohrst (with # being the SATA controller
> that the SSD is on) does allow it to be detected, but the patch listed
> in the ticket
> 
> diff --git a/drivers/ata/sata_nv.c b/drivers/ata/sata_nv.c
> index 6cda12b..6673b1d 100644
> --- a/drivers/ata/sata_nv.c
> +++ b/drivers/ata/sata_nv.c
> @@ -1565,7 +1565,7 @@ static int nv_noclassify_hardreset(struct ata_link
> *link, unsigned int *class,
>         bool online;
>         int rc;
> 
> -       rc = sata_link_hardreset(link, sata_deb_timing_hotplug, deadline,
> +       rc = sata_link_hardreset(link, sata_deb_timing_long, deadline,
>                                  &online, NULL);
>         return online ? -EAGAIN : rc;
>  }
> 
> does not work.
> 
> Tejun Heo was working on this back in April, but it looks like the
> troubleshooting petered out.
> 
> one issue that I did notice, in the dmesg I see
> 
> $ grep SATA dmesg
> ata1: SATA max UDMA/133 cmd 0xd480 ctl 0xd400 bmdma 0xcc00 irq 11
> ata2: SATA max UDMA/133 cmd 0xd080 ctl 0xd000 bmdma 0xcc08 irq 11
> ata1: SATA link down (SStatus 100 SControl 300)
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3: SATA max UDMA/133 cmd 0xc880 ctl 0xc800 bmdma 0xc080 irq 5
> ata4: SATA max UDMA/133 cmd 0xc480 ctl 0xc400 bmdma 0xc088 irq 5
> ata3: SATA link down (SStatus 0 SControl 300)
> ata4: SATA link down (SStatus 0 SControl 300)
> ata5: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb480 irq 10
> ata6: SATA max UDMA/133 cmd 0xb880 ctl 0xb800 bmdma 0xb488 irq 10
> ata5: SATA link down (SStatus 0 SControl 300)
> ata6: SATA link down (SStatus 0 SControl 300)
> 
> note the ata1 line. it detects something different than the links where
> there really is nothing plugged in, but it doesn't come up
> 
> booting with nohrst results in SStatus 123

Great, a new tester.  :-)

Let's track it on the bz.

Thanks.

-- 
tejun

  reply	other threads:[~2009-05-19  6:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 17:51 Intel X25E doesn't work with nv sata in current kernels david
2009-05-19  6:57 ` Tejun Heo [this message]
2009-06-09  2:16   ` david
2009-06-10  1:34     ` Tejun Heo

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=4A125841.5000608@kernel.org \
    --to=tj@kernel.org \
    --cc=david@lang.hm \
    --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