mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maarten Maathuis" <madman2003@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: Re: [sata_nv] timeout waiting for ADMA IDLE, stat=0x440
Date: Tue, 28 Aug 2007 16:06:41 +0200	[thread overview]
Message-ID: <6d4bc9fc0708280706q278fe285kdf90a27f40d2a55@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708281515340.3018@fbirervta.pbzchgretzou.qr>

I have not had any issues, i swapped the cable because a while ago i
had to check the connection of the drive after the bios failed to
detect the drive. That is why i considered that a posibility. Kernel
2.6.18 does not have NCQ support for nvidia chipsets, so that cannot
be it.

Maarten.

On 8/28/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>
> On Aug 25 2007 15:37, Maarten Maathuis wrote:
> >
> >A broken cable seems like a realistic possibility, so i swapped it for
> >another cable. I will try if that solves the problem.
>
> Hi, did you have any success/failure, other updates?
> I am facing a similar problem (just posted to linux-ide@vger.kernel.org),
> but also with 2.6.18, and it does not look like an NCQ or loose cable problem (got a
> backplane, and sda is working normal).
>
>         Jan
> --
>

  parent reply	other threads:[~2007-08-28 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.JryGluomV43EviuSMJKX+JI+tvU@ifi.uio.no>
2007-08-24 23:24 ` Robert Hancock
2007-08-25 13:37   ` Maarten Maathuis
     [not found]     ` <Pine.LNX.4.64.0708281515340.3018@fbirervta.pbzchgretzou.qr>
2007-08-28 14:06       ` Maarten Maathuis [this message]
2007-09-05 16:48         ` Andrew Morton
2007-09-05 16:54           ` Maarten Maathuis
2007-09-06 11:07           ` Jan Engelhardt
2007-08-24 17:11 Maarten Maathuis

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=6d4bc9fc0708280706q278fe285kdf90a27f40d2a55@mail.gmail.com \
    --to=madman2003@gmail.com \
    --cc=jengelh@computergmbh.de \
    --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

all inboxes | Powered by JetHome®