Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Bruce Link <Bruce@1045.ca>
Cc: linux-ide@vger.kernel.org, 1063474@bugs.launchpad.net
Subject: Re: System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset.
Date: Wed, 14 Aug 2013 00:17:47 -0600	[thread overview]
Message-ID: <520B210B.5040700@gmail.com> (raw)
In-Reply-To: <520AB4D8.1000208@1045.ca>

On 08/13/2013 04:36 PM, Bruce Link wrote:
> On bootup, when trying to attach to a Lite-on iHOS-104 DVD drive, the
> kernel attempts to establish a connection to the CD drive at a variety
> of speeds. Ultimately it fails with a "TEST_UNIT_READY failed
> (err_mask=0x4)" message
>
> ****************************************************************
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063474
>
> ****************************************************************
> The relevant DMESG output is listed below:
> watchtv@teevee:~$ dmesg|grep ata5
> [    1.088342] ata5: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc400
> irq 23
> [    1.556031] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    1.564134] ata5.00: ATAPI: ATAPI   iHOS104, WL0F, max UDMA/100
> [    1.580115] ata5.00: configured for UDMA/100
> [    6.580029] ata5.00: qc timeout (cmd 0xa0)
> [    6.580036] ata5.00: TEST_UNIT_READY failed (err_mask=0x4)
> [    7.048044] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [    7.072129] ata5.00: configured for UDMA/100
> [   29.856040] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> [   29.856063] ata5.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0
> dma 96 in
> [   29.856065] ata5.00: status: { DRDY }
> [   29.856071] ata5: hard resetting link
> [   29.856073] ata5: nv: skipping hardreset on occupied port
> [   30.324070] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   30.348152] ata5.00: configured for UDMA/100
> [   35.348125] ata5.00: qc timeout (cmd 0xa0)
> [   35.348132] ata5.00: TEST_UNIT_READY failed (err_mask=0x4)
> [   35.348139] ata5: hard resetting link
> [   35.348141] ata5: nv: skipping hardreset on occupied port
> [   35.816115] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   35.840125] ata5.00: configured for UDMA/100
> [   36.835824] ata5: EH complete
> [   67.840151] ata5: limiting SATA link speed to 1.5 Gbps
> [   67.840159] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> [   67.840178] ata5.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0
> dma 16512 in
> [   67.840181] ata5.00: status: { DRDY }
> [   67.840187] ata5: hard resetting link
> [   67.840188] ata5: nv: skipping hardreset on occupied port
> [   68.308056] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   68.332176] ata5.00: configured for UDMA/100
> [   68.343497] ata5: EH complete
> [   75.808054] ata5.00: limiting speed to UDMA/66:PIO4
> [   75.808061] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> [   75.808081] ata5.00: cmd a0/01:00:00:20:00/00:00:00:00:00/a0 tag 0
> dma 16416 in
> [   75.808084] ata5.00: status: { DRDY }
> [   75.808089] ata5: hard resetting link
> [   75.808091] ata5: nv: skipping hardreset on occupied port
> [   76.276050] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   76.300125] ata5.00: configured for UDMA/66
> [   76.307490] ata5: EH complete
> [  136.868049] ata5.00: limiting speed to UDMA/33:PIO4
> [  136.868058] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen
> [  136.868078] ata5.00: cmd a0/01:00:00:20:00/00:00:00:00:00/a0 tag 0
> dma 16416 in
> [  136.868081] ata5.00: status: { DRDY }
> [  136.868087] ata5: hard resetting link
> [  136.868089] ata5: nv: skipping hardreset on occupied port
> [  137.332073] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [  137.356170] ata5.00: configured for UDMA/33
> [  137.866272] ata5: EH complete

These NVIDIA SATA controllers are a pain as they all seem to have a 
different set of bugs related to hardreset, etc. What happens if you 
boot up without the drive connected and then plug in the cable after the 
system boots up?

  reply	other threads:[~2013-08-14  6:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 22:36 System fails to connect to iHOS-104 DVD drive with nvidia MCP61 chipset Bruce Link
2013-08-14  6:17 ` Robert Hancock [this message]
2013-08-14 22:17   ` Bruce Link
2013-08-15  5:36     ` Robert Hancock
2013-08-16  2:47       ` Bruce Link
2013-08-17 17:32         ` Bruce Link
2013-08-18  7:05           ` Robert Hancock
2013-08-24  0:34             ` Bruce Link
     [not found]               ` <CADLC3L0wXmVDgHPOFEkeiXD9sDUBg3tZePcJ-gRfoRN5-fXE1w@mail.gmail.com>
     [not found]                 ` <52180F76.3070803@1045.ca>
2013-08-24  3:11                   ` Robert Hancock
2013-08-24 15:54                     ` Bruce Link
     [not found]                     ` <5218D74A.5020305@1045.ca>
2013-09-06 23:17                       ` Bruce Link
2013-09-07  1:53                         ` Robert Hancock
2013-09-08 12:25                           ` Tejun Heo
2013-09-18  0:35                     ` Bruce Link
2013-09-18  1:40                       ` Robert Hancock
2013-09-18 22:27                         ` Bruce Link
2013-10-19  0:04                           ` Bruce Link
     [not found]                           ` <5261CC95.1050903@1045.ca>
2013-10-22  1:17                             ` Robert Hancock
2013-11-09 21:02                               ` Bruce Link

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=520B210B.5040700@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=1063474@bugs.launchpad.net \
    --cc=Bruce@1045.ca \
    --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