All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Michael Jogback <lm@jogback.se>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: Problem w/ hotplug on sata_sil24 w/ PMP (sil3726)
Date: Sat, 18 Oct 2008 18:52:09 +0200	[thread overview]
Message-ID: <20081018165209.GA7754@cleopatra.jogback.se> (raw)
In-Reply-To: <48F595DB.4030301@kernel.org>

* Tejun Heo <tj@kernel.org> [2008-10-15 16:03:55]:

> Can you please try the followings?
> 
> 1. If you swap the drive on the second slot with another one, does the
>    detection problem stay with the port or follow the drive?

It doesn't follow the drive. It sort of stays with port in that sense
that it happens on the first equipped port after the first one (which is
probed by the controllers BIOS). If I leave the second port empty, it
happens on the third when I do a cold boot.

I have also moved the drives around, and it does not follow the drive.

One odd thing that I've noticed is that it's only happening on my
Samsung drives, I've got a couple of WD aswell and they seem to work.

> 2. Does "libata.force=1.5Gbps" make any difference?

No, same behaviour.

> 3. Apply the patch and post log after failed hotplug.
> 

I had to change it to:
ata_port_printk(ap, KERN_WARNING,  "XXX error_intr irq_stat=0x%x\n", irq_stat);

I hope that was correct.

Yank the drive:
[   82.081889] ata3: XXX error_intr irq_stat=0x8040800
[   82.095851] ata3.04: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xf
[   82.095913] ata3: SError: { PHYRdyChg CommWake DevExch }
[   82.096037] ata3.04: hard resetting link
[   83.183919] ata3.04: SATA link down (SStatus 0 SControl 320)
[   83.184006] ata3: failed to recover some devices, retrying in 5 secs
[   88.756273] ata3.04: hard resetting link
[   89.092417] ata3.04: SATA link down (SStatus 0 SControl 320)
[   89.092504] ata3: failed to recover some devices, retrying in 5 secs
[   95.136519] ata3.04: hard resetting link
[   95.504418] ata3.04: SATA link down (SStatus 0 SControl 320)
[   95.504467] ata3.04: disabled
[   96.102757] ata3: EH complete
[   96.102711] ata3.04: detaching (SCSI 3:4:0:0)
[   96.102711] sd 3:4:0:0: [sdp] Synchronizing SCSI cache
[   96.102711] sd 3:4:0:0: [sdp] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[   96.102711] sd 3:4:0:0: [sdp] Stopping disk
[   96.102711] sd 3:4:0:0: [sdp] START_STOP FAILED
[   96.102711] sd 3:4:0:0: [sdp] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

Plug the drive:
[  103.696514] ata3: XXX error_intr irq_stat=0x8040800
[  103.712305] ata3.04: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xf
[  103.712368] ata3: SError: { PHYRdyChg CommWake DevExch }
[  103.712493] ata3.04: hard resetting link
[  104.452364] ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  104.452447] ata3: XXX error_intr irq_stat=0x60002
[  104.468214] ata3.04: failed to IDENTIFY (I/O error, err_mask=0x11)
[  104.468288] ata3.15: hard resetting link
[  107.671458] ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[  107.671657] ata3.00: hard resetting link
[  108.030320] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  108.030396] ata3.01: hard resetting link
[  108.418464] ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  108.418541] ata3.02: hard resetting link
[  108.762278] ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  108.762292] ata3.03: hard resetting link
[  109.097482] ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  109.097556] ata3.04: hard resetting link
[  109.432900] ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  109.432975] ata3.05: hard resetting link
[  110.062677] ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
[  110.074170] ata3.00: configured for UDMA/100
[  110.087041] ata3.01: configured for UDMA/100
[  110.099889] ata3.02: configured for UDMA/100
[  110.112772] ata3.03: configured for UDMA/100
[  110.112848] ata3: XXX error_intr irq_stat=0x60002
[  110.125182] ata3.04: failed to IDENTIFY (I/O error, err_mask=0x11)
[  110.125257] ata3.15: hard resetting link
[  112.253161] ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[  112.253413] ata3.00: hard resetting link
[  112.589297] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  112.589372] ata3.01: hard resetting link
[  112.925296] ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  112.925371] ata3.02: hard resetting link
[  113.261297] ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  113.261372] ata3.03: hard resetting link
[  113.597296] ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  113.597371] ata3.04: hard resetting link
[  113.937936] ata3.04: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  113.938011] ata3.05: hard resetting link
[  114.274271] ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
[  114.289542] ata3.00: configured for UDMA/100
[  114.302397] ata3.01: configured for UDMA/100
[  114.315239] ata3.02: configured for UDMA/100
[  114.328084] ata3.03: configured for UDMA/100
[  114.328161] ata3: XXX error_intr irq_stat=0x60002
[  114.340527] ata3.04: failed to IDENTIFY (I/O error, err_mask=0x11)
[  114.340601] ata3.04: failed to recover link after 3 tries, disabling
[  114.340673] ata3: failed to recover PMP, retrying in 5 secs
[  119.350834] ata3.15: hard resetting link
[  121.478839] ata3.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[  121.799894] ata3.00: hard resetting link
[  122.135051] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[  122.135126] ata3.01: hard resetting link
[  122.470974] ata3.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  122.471049] ata3.02: hard resetting link
[  122.806974] ata3.02: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  122.807049] ata3.03: hard resetting link
[  123.142974] ata3.03: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  123.143049] ata3.05: hard resetting link
[  123.478974] ata3.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320)
[  123.491861] ata3.00: configured for UDMA/100
[  123.504712] ata3.01: configured for UDMA/100
[  123.517553] ata3.02: configured for UDMA/100
[  123.530403] ata3.03: configured for UDMA/100
[  123.862927] ata3: EH complete

The drive seems to come alive and seems to start at [  119.350834] above.
But then it's been tried 3 times and is already disabled.

BR
/LM

  reply	other threads:[~2008-10-18 16:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-11 14:27 Problem w/ hotplug on sata_sil24 w/ PMP (sil3726) Lars Michael Jogback
2008-10-14  5:51 ` Tejun Heo
2008-10-14 20:19   ` Lars Michael Jogback
2008-10-15  7:03     ` Tejun Heo
2008-10-18 16:52       ` Lars Michael Jogback [this message]
2008-10-23 18:14         ` Lars Michael Jogback
2008-10-27  7:35           ` Tejun Heo
2008-10-27  7:38             ` Tejun Heo
2008-10-27  8:47               ` Lars Michael Jogback
2008-10-27 19:40               ` Lars Michael Jogback
2008-11-10  6:47                 ` Tejun Heo
2008-11-10 18:26                   ` Lars Michael Jogback
2008-11-11  2:56                     ` Tejun Heo
     [not found] <359604ECF8F440408B9634E6146249B42923805F@mail.scl.local>
     [not found] ` <20110628095723.GC3386@htj.dyndns.org>
2011-06-30 17:53   ` Derry Bryson
2011-07-12 15:01     ` tj
2011-07-12 19:21       ` Derry Bryson
2011-07-13 13:34         ` tj
2011-07-13 14:39           ` tj
2011-07-13 16:23             ` Derry Bryson
2011-07-14  7:14               ` tj
2011-07-14 17:37                 ` Derry Bryson
2011-07-21  9:00                   ` tj
2011-07-21 16:22                     ` Derry Bryson
2011-07-22  9:50                       ` tj
2011-07-22 17:29                         ` Derry Bryson
2011-07-22 19:34                         ` Derry Bryson
2011-07-30 12:54                           ` tj
2011-09-30 21:54                             ` Mike I
2011-10-06  5:48                               ` Gwendal Grignou
     [not found]                                 ` <CAMHSBOV8rSW3jumpx8URZrgo8w1He9zruP7yAOw7uhQOaAj3Xg@mail.gmail.com>
2011-10-06  6:07                                   ` Gwendal Grignou
2011-10-08 18:25                                 ` Michael Ihrcke
2011-10-12  2:06                                   ` Michael Ihrcke
2011-10-13  2:09                                     ` Mike I

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=20081018165209.GA7754@cleopatra.jogback.se \
    --to=lm@jogback.se \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.