public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr@rogers.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [Fedora][libata][4.4-rc0/rc1] Disk cache/write error? - FLUSH CACHE EXT / WRITE FPDMA QUEUED
Date: Mon, 16 Nov 2015 20:27:54 -0500	[thread overview]
Message-ID: <2166717.D432rernxe@segfault> (raw)

Hello devs,

Something unusual happened today, disk locked up, went into bad state, 
rebooted with sysctl magic key, BIOS reported disk showed no OS found, hard 
powered off machine then everything was normal.

Any changes recently in libata that might have caused the disk to perform a 
bad operation?

SMART reports no faults in tests (Will perform long test later), I don't 
suspect disk failure (231 days, not rollover counter)

kernel: 4.4.0-0.rc0.git9.2.fc24.x86_64
Filesystem: EXT4, options: noatime,nodiratime

Boot command line:

BOOT_IMAGE=/boot/vmlinuz-4.4.0-0.rc0.git9.2.fc24.x86_64 
root=UUID=f834b05c-55f3-407b-9a63-fc6b04d4c845 ro rhgb slub_debug=- 
cgroup_disable=memory console=tty0 console=ttyS0,115200n8 nmi_watchdog=0 
video=LVDS-1:d video=VGA-0:e audit=0 radeon.gartsize=8192 intel_iommu=igfx_off 
radeon.lockup_timeout=0 radeon.vm_size=16 rd.driver.blacklist=dell_rbtn 
LANG=en_US.UTF-8

Laptop: Dell Precision M6800
BIOS: Version A15 

Controller: 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA 
Controller [RAID mode] (rev 04)


SMART Log:

Error 1 occurred at disk power-on lifetime: 5559 hours (231 days + 15 hours)
  When the command that caused the error occurred, the device was active or 
idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 03 80 04 11 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ea 00 00 00 00 00 a0 00      02:59:36.641  FLUSH CACHE EXT
  61 00 88 ff ff ff 4f 00      02:59:36.641  WRITE FPDMA QUEUED
  61 00 30 ff ff ff 4f 00      02:59:36.640  WRITE FPDMA QUEUED
  61 00 20 ff ff ff 4f 00      02:59:35.952  WRITE FPDMA QUEUED
  61 00 90 ff ff ff 4f 00      02:59:35.952  WRITE FPDMA QUEUED

Thanks,
Shawn


                 reply	other threads:[~2015-11-17  1:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2166717.D432rernxe@segfault \
    --to=shawn.starr@rogers.com \
    --cc=linux-kernel@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