linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Sergey Spiridonov <sena@hurd.homeunix.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363  (JMB363) kernel 2.6.25-2 Debian/Lenny
Date: Sun, 24 Aug 2008 00:39:36 -0400	[thread overview]
Message-ID: <48B0E608.4050205@garzik.org> (raw)
In-Reply-To: <g8q9mg$v2p$1@ger.gmane.org>

Sergey Spiridonov wrote:
> Hi
> 
> Jeff Garzik wrote:
> 
>> So...  suspect bad cables, bad port connectors, cable interference,
>> motherboard-caused interference or grounding problems, power supply
>> problems.
> 
> I did exchange power supply and I did exchange hard drives. The same
> hard drive with the same cable works with SB600 and produces errors with
> JMB363. So looks like it is not cable or hard drive problem. May be the
> problem is JMB363 port connector on the motherboard. How can I check it?

Try new motherboard of same brand and model :/

In general, tons of ATA bus errors and SError complaints indicate some 
sort of problem at the physical layer/level.  Its always possible that 
software is to blame, but bug report patterns so far tend to point to 
hardware.

	Jeff



  reply	other threads:[~2008-08-24  4:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <g8p6po$nm$1@ger.gmane.org>
2008-08-23 22:38 ` GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363 (JMB363) kernel 2.6.25-2 Debian/Lenny Jeff Garzik
2008-08-23 23:27   ` Chr
2008-08-24  0:27   ` Sergey Spiridonov
2008-08-24  4:39     ` Jeff Garzik [this message]
2008-08-24 23:31       ` Sergey Spiridonov
2008-08-25 14:52         ` xerces8
2008-09-17 12:07         ` Sergey Spiridonov
2008-09-17 15:31           ` Krzysztof Halasa
2008-08-24 16:44     ` xerces8
2008-08-30 11:00       ` Tejun Heo
2008-08-30 18:13         ` xerces8
2008-08-31  9:33           ` 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=48B0E608.4050205@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sena@hurd.homeunix.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).