linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andreas Radke <a.radke@arcor.de>,
	linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata drive loosing connection/resetting port
Date: Tue, 14 Aug 2007 19:15:52 +0900	[thread overview]
Message-ID: <46C180D8.9060005@gmail.com> (raw)
In-Reply-To: <6bffcb0e0708131311k51238bb0l63eeb2fce53e3481@mail.gmail.com>

Michal Piotrowski wrote:
> Hi Andreas,
> 
> [Adding Jeff and linux-ide to CC]
> 
> On 13/08/07, Andreas Radke <a.radke@arcor.de> wrote:
>> running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
>> Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
>> minutes:
>>
>> ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400101 action 0x2 frozen
>> ata1.00: (irq_stat 0x08000000, interface fatal error)
>> ata1.00: cmd ca/00:f8:18:d2:27/00:00:00:00:00/e6 tag 0 cdb 0x0 data
>> 126976 out res 50/00:00:80:2b:3d/00:00:00:00:00/e0 Emask 0x10 (ATA bus
>> error) ata1: soft resetting port
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> ata1.00: configured for UDMA/133
>> ata1: EH complete
>> sd 0:0:0:0: [sda] 145226112 512-byte hardware sectors (74356 MB)
>> sd 0:0:0:0: [sda] Write Protect is off
>> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
>> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>>
>>
>> hard disc is a Western Digital 10k Raptor connected to the ICH9R. on
>> the second port of the southbridge is another Samsung hard disc drive
>> connected without errors. both controllers are running ahci mode.
>>
>> lsmod:
>> sr_mod                 16548  0
>> cdrom                  38312  1 sr_mod
>> sd_mod                 25088  6
>> pata_jmicron            5888  0
>> ahci                   22404  4
>> libata                119440  2 pata_jmicron,ahci
>>
>> i've tried changing the SATA cables and also the power wire to the
>> disc without success. i checked the disc successfully with Hitachi
>> drive fitness test. it has worked without any trouble so far in a Intel
>> P965 ICH8 based mainboard.
>>
>> any idea how to find the reason?

Most likely a hardware issue.

* Please try a different harddrive/cable and connect to a different port.

* Get a different power supply and see whether that changes anything.

-- 
tejun

  reply	other threads:[~2007-08-14 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070813220241.3f4b8df5@workstation64.home>
2007-08-13 20:11 ` sata drive loosing connection/resetting port Michal Piotrowski
2007-08-14 10:15   ` Tejun Heo [this message]
2007-08-14 20:19     ` Andreas Radke
2007-08-15  6:19       ` Tejun Heo
2007-08-15 13:48         ` Andreas Radke
2007-08-16 10:53           ` Tejun Heo
2007-08-16 16:01             ` Andreas Radke

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=46C180D8.9060005@gmail.com \
    --to=htejun@gmail.com \
    --cc=a.radke@arcor.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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).