From: Jeff Garzik <jeff@garzik.org>
To: Mourad De Clerck <mourad@aquazul.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Marvell 6121 AHCI: hotplug not reliable?
Date: Thu, 13 Aug 2009 09:19:13 -0400 [thread overview]
Message-ID: <4A8412D1.2070506@garzik.org> (raw)
In-Reply-To: <4A8406EE.1040203@aquazul.com>
Mourad De Clerck wrote:
> Hello,
>
> I've got a box with an Asus M2V motherboard and a Marvell 6121 SATA
> controller. Kernel version 2.6.30.
>
> It works in general, but from time to time it stops detecting the disks
> when I hotplug them. So usually hotplug works, but sometimes it just
> stops working.
>
> If I unload the ahci module, and reload it (with the marvell_enable=1
> parm), it detects the disks again and works without any further issues -
> until the next failed hotplug.
>
> Is there anything that can be done about this?
>
> In attachment, the kernel log with at the end (at [128508.539280]) a
> failed hotplug, after which I unload/reload the ahci module and things
> work again (starting at [147111.353555]).
> [128508.539280] ata1: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen
> [128508.539306] ata1: irq_stat 0x02400000, PHY RDY changed
> [128508.539333] ata1: hard resetting link
> [128514.300013] ata1: link is slow to respond, please be patient (ready=0)
> [128518.556015] ata1: COMRESET failed (errno=-16)
> [128518.556040] ata1: hard resetting link
> [128524.320015] ata1: link is slow to respond, please be patient (ready=0)
> [128528.576014] ata1: COMRESET failed (errno=-16)
> [128528.576039] ata1: hard resetting link
> [128534.340014] ata1: link is slow to respond, please be patient (ready=0)
> [128563.628015] ata1: COMRESET failed (errno=-16)
> [128563.628041] ata1: limiting SATA link speed to 1.5 Gbps
> [128563.628062] ata1: hard resetting link
> [128568.664014] ata1: COMRESET failed (errno=-16)
> [128568.664038] ata1: reset failed, giving up
> [128568.664059] ata1: EH complete
hmmmm. Since PHY_RDY-leads-to-failure is a very rare report for this
chip, my initial guess would be indicative of either a power, SATA port,
or SATA cable problem.
PHY_RDY is essentially an indication of whether or not the host-device
SATA connection is alive and transmitting SATA packets (FIS's). If
PHY_RDY changes, it means the hardware -thinks- that the SATA connection
changed.
Jeff
next prev parent reply other threads:[~2009-08-13 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 12:28 Marvell 6121 AHCI: hotplug not reliable? Mourad De Clerck
2009-08-13 13:19 ` Jeff Garzik [this message]
2009-08-13 13:40 ` Mourad De Clerck
2009-08-14 9:30 ` Tejun Heo
2009-08-14 21:01 ` Mourad De Clerck
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=4A8412D1.2070506@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mourad@aquazul.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).