linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>
Subject: T61 SATA error in log
Date: Thu, 27 Sep 2007 17:21:08 +1000	[thread overview]
Message-ID: <1190877668.30275.3.camel@pasglop> (raw)

Saw that popping up in my log today on a brand new T61 thinkpad:

[  427.712000] ata1.00: exception Emask 0x2 SAct 0x18 SErr 0x0 action 0x2 frozen
[  427.712000] ata1.00: (spurious completions during NCQ issue=0x0 SAct=0x18 FIS=004040a1:00000024)
[  427.712000] ata1.00: cmd 61/08:18:f4:74:54/00:00:04:00:00/40 tag 3 cdb 0x0 data 4096 out
[  427.712000]          res 40/00:28:64:e4:51/00:00:04:00:00/40 Emask 0x2 (HSM violation)
[  427.712000] ata1.00: cmd 61/08:20:84:10:81/00:00:04:00:00/40 tag 4 cdb 0x0 data 4096 out
[  427.712000]          res 40/00:28:64:e4:51/00:00:04:00:00/40 Emask 0x2 (HSM violation)
[  428.024000] ata1: soft resetting port
[  428.196000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  428.204000] ata1.00: configured for UDMA/100
[  428.204000] ata1: EH complete
[  428.204000] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
[  428.204000] sd 0:0:0:0: [sda] Write Protect is off
[  428.204000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[  428.204000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Kernel recovered just fine and things seem smooth so far. Is that something I need
to worry about ?

Kernel is ubuntu gutsy's 2.6.22 and controller is:

Cheers,00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0])
        Subsystem: Lenovo Unknown device 20a7
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 218
        Region 0: I/O ports at 1c50 [size=8]
        Region 1: I/O ports at 1c44 [size=4]
        Region 2: I/O ports at 1c48 [size=8]
        Region 3: I/O ports at 1c40 [size=4]
        Region 4: I/O ports at 1c20 [size=32]
        Region 5: Memory at fe226000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/2 Enable+
                Address: fee0300c  Data: 4152
        Capabilities: [70] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a8] #12 [0010]


Cheers,
Ben.



             reply	other threads:[~2007-09-27  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  7:21 Benjamin Herrenschmidt [this message]
2007-09-27 20:35 ` T61 SATA error in log Tejun Heo
2007-09-27 23:36   ` Benjamin Herrenschmidt
2007-09-27 23:50     ` Tejun Heo

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=1190877668.30275.3.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --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).