All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Langga <klangga@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Drive not detected upon resume from suspend-to-ram [sata_promise]
Date: Wed, 18 Jul 2012 16:11:06 +0800	[thread overview]
Message-ID: <CAHmELnVRCcLBdF5G1t=NPDu=5LiOgFVeKJ-Kw=Gqp8eJFz_t7Q@mail.gmail.com> (raw)

Hi! I'm having problems with resuming from suspend-to-ram.
Specifically, the hard drive fails to be detected. Here is the card
info from lspci:

03:05.0 Mass storage controller: Promise Technology, Inc. PDC20375
(SATA150 TX2plus) (rev 02)
        Subsystem: Promise Technology, Inc. PDC20375 (SATA150 TX2plus)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 96 (1000ns min, 4500ns max), Cache Line Size: 576 bytes
        Interrupt: pin A routed to IRQ 20
        Region 0: I/O ports at e800 [size=64]
        Region 1: I/O ports at e400 [size=16]
        Region 2: I/O ports at e000 [size=128]
        Region 3: Memory at febff000 (32-bit, non-prefetchable) [size=4K]
        Region 4: Memory at febc0000 (32-bit, non-prefetchable) [size=128K]
        Expansion ROM at febe0000 [disabled] [size=16K]
        Capabilities: [60] Power Management version 2
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: sata_promise


Here are the relevant messages from syslog:

<...pm-suspend...>
sata_promise 0000:03:05.0: PCI INT A disabled
<...resuming...>
sata_promise 0000:03:05.0: restoring config space at offset 0xf (was
0x1204010e, writing 0x1204010a)
sata_promise 0000:03:05.0: restoring config space at offset 0xc (was
0x80001, writing 0xfebe0000)
sata_promise 0000:03:05.0: restoring config space at offset 0x8 (was
0x900000, writing 0xfebc0000)
sata_promise 0000:03:05.0: restoring config space at offset 0x7 (was
0x800000, writing 0xfebff000)
sata_promise 0000:03:05.0: restoring config space at offset 0x6 (was
0x8201, writing 0xe001)
sata_promise 0000:03:05.0: restoring config space at offset 0x5 (was
0x8101, writing 0xe401)
sata_promise 0000:03:05.0: restoring config space at offset 0x4 (was
0x8001, writing 0xe801)
sata_promise 0000:03:05.0: restoring config space at offset 0x3 (was
0x0, writing 0x6090)
sata_promise 0000:03:05.0: restoring config space at offset 0x1 (was
0x2300000, writing 0x2300113)
sata_promise 0000:03:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
<...>
ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x100 action 0x6
ata3: SError: { UnrecovData }
ata3.00: failed command: IDENTIFY DEVICE
ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/40 tag 0 pio 512 in
ata3.00: status: { DRDY ERR }
ata3.00: error: { ABRT }
ata3: hard resetting link
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: both IDENTIFYs aborted, assuming NODEV
ata3.00: revalidation failed (errno=-2)
ata3: hard resetting link
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: both IDENTIFYs aborted, assuming NODEV
ata3.00: revalidation failed (errno=-2)
ata3: hard resetting link
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3.00: both IDENTIFYs aborted, assuming NODEV
ata3.00: revalidation failed (errno=-2)
ata3.00: disabled
ata3: EH complete


I am using pm-suspend to suspend-to-ram and my OS is Debian Wheezy.
Any help would be greatly appreciated. Thanks!

             reply	other threads:[~2012-07-18  8:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  8:11 Kenneth Langga [this message]
2012-07-19  0:38 ` Drive not detected upon resume from suspend-to-ram [sata_promise] Srikanth TS
2012-07-19  1:26   ` Kenneth Langga

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='CAHmELnVRCcLBdF5G1t=NPDu=5LiOgFVeKJ-Kw=Gqp8eJFz_t7Q@mail.gmail.com' \
    --to=klangga@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 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.