From: Jeff Garzik <jeff@garzik.org>
To: Sergey Spiridonov <sena@hurd.homeunix.org>
Cc: linux-kernel@vger.kernel.org,
Linux IDE mailing list <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: Sat, 23 Aug 2008 18:38:36 -0400 [thread overview]
Message-ID: <48B0916C.4080805@garzik.org> (raw)
In-Reply-To: <g8p6po$nm$1@ger.gmane.org>
Sergey Spiridonov wrote:
> Hi
>
> I got kernel errors [1] and [2] followed by SATA reset on heavy load on
> the hard drive connected to the GA-MA790FX-DS5 onboard controller
> Jmicron 20360/20363 (JMB363) (here is lspci [3]). Hard drive connected
> to the another onboard (south bridge from AMD SB600) controller works
> without problem.
>
> I got two 1TB Seagate hard disks, ST31000340AS and ST31000340NS. I
> connected one to Jmicron JMB363, another to SB600. After some testing
> with several instances of bonnie++ I got kernel errors [1] and [2].
> After this I exchanged hard disks connections. The one which was
> connected to JMB363 I connected to SB600 and vs versa. Errors, timeouts
> and hard drive resetting happened always on the hard drive which is
> connected to the JMB363 (in log file it is sdb). There are no errors if
> both drives are connected to the SB600.
>
> Here [4] is complete (before i get errors) dmesg output after system is
> booted.
>
> I already replaced (took from working PC) power supply, memory, video
> card and dvd drive. I get same problems also with this devices. So
> problem must be motherboard, software or CPU. CPU seems to work O.K.
>
> It looks like the problem is motherboard or ahci ata driver. Does
> somebody have any clue about it? Is chip JMB363 broken or linux driver
> is broken?
>
> [1] http://hurd.homeunix.org/~sena/GA-MA790FX-DS5/dmesg-sata-errors.txt
> [2] http://hurd.homeunix.org/~sena/GA-MA790FX-DS5/dmesg-sata-errors2.txt
> [3] http://hurd.homeunix.org/~sena/GA-MA790FX-DS5/lspci.txt
> [4] http://hurd.homeunix.org/~sena/GA-MA790FX-DS5/dmesg-after-boot.txt
See http://ata.wiki.kernel.org/index.php/Libata_error_messages for an
introduction.
In general, tons of ATA bus errors and SError register bits means that
problems are coming from the ATA bus, a.k.a. the SATA cable and its
related connections.
So... suspect bad cables, bad port connectors, cable interference,
motherboard-caused interference or grounding problems, power supply
problems.
Jeff
next parent reply other threads:[~2008-08-23 22:38 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 ` Jeff Garzik [this message]
2008-08-23 23:27 ` GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363 (JMB363) kernel 2.6.25-2 Debian/Lenny Chr
2008-08-24 0:27 ` Sergey Spiridonov
2008-08-24 4:39 ` Jeff Garzik
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=48B0916C.4080805@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).