linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aalderd Bouwman <aalderd.boac@wanadoo.nl>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Seagate SATA 3GB/s drive connected to via vt8251 using ahci	module
Date: Mon, 12 Jun 2006 13:24:16 +0200	[thread overview]
Message-ID: <1150111457.4060.2.camel@anja> (raw)
In-Reply-To: <448D474E.6020706@gmail.com>

Tejun,

#modprobe ahci:
Jun 12 13:13:25 server ahci 0000:00:0f.0: version 1.3
Jun 12 13:13:25 server ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
Jun 12 13:13:32 server ahci 0000:00:0f.0: AHCI 0001.0000 32 slots 4 ports 3 Gbps 0xf impl SATA mode
Jun 12 13:13:32 server ahci 0000:00:0f.0: flags: 64bit ncq pm led clo pmp pio slum part 
Jun 12 13:13:32 server ata17: SATA max UDMA/133 cmd 0xE048AD00 ctl 0x0 bmdma 0x0 irq 10
Jun 12 13:13:32 server ata18: SATA max UDMA/133 cmd 0xE048AD80 ctl 0x0 bmdma 0x0 irq 10
Jun 12 13:13:32 server ata19: SATA max UDMA/133 cmd 0xE048AE00 ctl 0x0 bmdma 0x0 irq 10
Jun 12 13:13:32 server ata20: SATA max UDMA/133 cmd 0xE048AE80 ctl 0x0 bmdma 0x0 irq 10
Jun 12 13:13:33 server ata17: SATA link down (SStatus 0 SControl 300)
Jun 12 13:13:33 server scsi16 : ahci
Jun 12 13:13:33 server ata18: SATA link down (SStatus 0 SControl 300)
Jun 12 13:13:33 server scsi17 : ahci
Jun 12 13:13:33 server ata19: SATA link down (SStatus 0 SControl 300)
Jun 12 13:13:33 server scsi18 : ahci
Jun 12 13:13:33 server ata20: SATA link down (SStatus 0 SControl 300)
Jun 12 13:13:33 server scsi19 : ahci

Turning on sata-drive:
Jun 12 13:13:38 server ata18: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
Jun 12 13:13:38 server ata18: (irq_stat 0x00000040, connection status changed)
Jun 12 13:13:38 server ata18: soft resetting port
Jun 12 13:13:38 server ata18: SATA link down (SStatus 1 SControl 300)
Jun 12 13:13:38 server ata18: EH complete
Jun 12 13:13:38 server ata18: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0x2 frozen
Jun 12 13:13:38 server ata18: (irq_stat 0x00000040, connection status changed)
Jun 12 13:13:38 server ata18: soft resetting port
Jun 12 13:13:38 server ata18: SATA link down (SStatus 1 SControl 300)
Jun 12 13:13:38 server ata18: EH complete

Turing off sata-drive:
no messages

Turning on sata-drive:
Jun 12 13:13:58 server ata18: exception Emask 0x10 SAct 0x0 SErr 0x4070000 action 0x2 frozen
Jun 12 13:13:58 server ata18: (irq_stat 0x04400040, connection status changed)
Jun 12 13:13:58 server ata18: soft resetting port
Jun 12 13:13:58 server ata18: SATA link down (SStatus 1 SControl 300)
Jun 12 13:13:58 server ata18: EH complete

Turning off sata-drive:
no messages

Turning on sata-drive:
Jun 12 13:14:13 server ata18: exception Emask 0x10 SAct 0x0 SErr 0x40f0000 action 0x2 frozen
Jun 12 13:14:13 server ata18: (irq_stat 0x04400040, connection status changed)
Jun 12 13:14:13 server ata18: soft resetting port
Jun 12 13:14:13 server ata18: SATA link down (SStatus 1 SControl 300)
Jun 12 13:14:13 server ata18: EH complete

Turning off sata-drive:
no messages

#rmmod ahci:
Jun 12 13:14:23 server ACPI: PCI interrupt for device 0000:00:0f.0 disabled

Loading the ahci-driver while the drive is turned on, the drive is working properly.
I have copied a lot of data to/from this drive and compared this data to the orginal with diff.

Aalderd Bouwman.

On Mon, 2006-06-12 at 19:51 +0900, Tejun Heo wrote:
> Aalderd Bouwman wrote:
> > Jun 12 12:27:24 server ata13.00: (irq_stat 0x40000000)
> > Jun 12 12:27:24 server ata13.00: tag 0 cmd 0x60 Emask 0x1 stat 0x41 err 0x4 (device error)
> > Jun 12 12:27:24 server ata13.00: tag 1 cmd 0x60 Emask 0x1 stat 0x41 err 0x4 (device error)
> > Jun 12 12:27:24 server ata13.00: tag 3 cmd 0x60 Emask 0x1 stat 0x41 err 0x4 (device error)
> > Jun 12 12:27:24 server ata13: soft resetting port
> > Jun 12 12:27:24 server ata13: softreset failed (1st FIS failed)
> > Jun 12 12:27:24 server ata13: softreset failed, retrying in 5 secs
> > Jun 12 12:27:29 server ata13: hard resetting port
> > 
> > Remove sata-connector and then the power-connector of the Seagate drive.
> > (Note that I also have problems with hotplug the Maxtor-drive.
> >  I will post that problem later this day.)
> 
> Can you remove and then replug those?  I wanna see whether the 
> controller is locked up or the drive.
> 


  reply	other threads:[~2006-06-12 11:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 17:30 Seagate SATA 3GB/s drive connected to via vt8251 using ahci module Aalderd Bouwman
2006-06-09  5:44 ` Tejun Heo
2006-06-12 10:42   ` Aalderd Bouwman
2006-06-12 10:51     ` Tejun Heo
2006-06-12 11:24       ` Aalderd Bouwman [this message]
2006-06-18  2:56         ` Tejun Heo
2006-06-19 17:10           ` Aalderd Bouwman
2006-06-19 17:18             ` Tejun Heo
     [not found] ` <1150745738.4302.1.camel@anja>
     [not found]   ` <20060620023312.GA1250@htj.dyndns.org>
2006-06-20 15:21     ` Aalderd Bouwman
2006-06-20 15:37       ` Tejun Heo
2006-06-20 19:31         ` Bastiaan Jacques
2006-06-21  7:25           ` Aalderd Bouwman
2006-06-21 14:12           ` [PATCH] ahci: disable NCQ support on vt8251 Tejun Heo
2006-06-23  3:22             ` Jeff Garzik

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=1150111457.4060.2.camel@anja \
    --to=aalderd.boac@wanadoo.nl \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).