mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maarten Maathuis" <madman2003@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: jengelh@computergmbh.de, linux-kernel@vger.kernel.org,
	"Robert Hancock" <hancockr@shaw.ca>,
	linux-ide@vger.kernel.org
Subject: Re: [sata_nv] timeout waiting for ADMA IDLE, stat=0x440
Date: Wed, 5 Sep 2007 18:54:52 +0200	[thread overview]
Message-ID: <6d4bc9fc0709050954p5c769864q1088310c0a70061b@mail.gmail.com> (raw)
In-Reply-To: <20070905094845.1d2f84cb.akpm@linux-foundation.org>

At this point it safe to say that it was a cable related issue.

I swapped it to be sure and i haven't had issues since.

Sincerely,

Maarten Maathuis.

On 9/5/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Tue, 28 Aug 2007 16:06:41 +0200 "Maarten Maathuis" <madman2003@gmail.com> wrote:
> > 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).
> > >
>
> This is a rather comedic email thread, with people top-posting, others
> leaving others off the cc list, Robert's MUA reliably and inexplicably
> mangling both In-Reply-To: and References: thus breaking threading, no
> visible sign of how Jan got involved and no linux-ide cc's.
>
> Enough time has passed for everyone to forget all about this.  So Maarten,
> if you still believe that this is still a kernel bug then please update us
> on its status and provide a full description for linux-ide..  Please use
> reply-to-all for that.
>
> Thanks.
>

  reply	other threads:[~2007-09-05 16:55 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
2007-09-05 16:48         ` Andrew Morton
2007-09-05 16:54           ` Maarten Maathuis [this message]
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=6d4bc9fc0709050954p5c769864q1088310c0a70061b@mail.gmail.com \
    --to=madman2003@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=jengelh@computergmbh.de \
    --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

all inboxes | Powered by JetHome®