All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Dmitry <dmonakhov@openvz.org>
Cc: John Tyree <johntyree@gmail.com>, Theodore Ts'o <tytso@mit.edu>,
	Eric Sandeen <sandeen@redhat.com>,
	Jiaying Zhang <jiayingz@google.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>
Subject: Re: PROBLEM: Disk continually remounts and hardlocks the entire system if running on battery.
Date: Tue, 18 Jan 2011 18:18:26 -0600	[thread overview]
Message-ID: <4D362DD2.8070606@gmail.com> (raw)
In-Reply-To: <87ipxlj1vd.fsf@dmon-lp.sw.ru>

(CCing linux-ide)

On 01/18/2011 04:14 PM, Dmitry wrote:
> On Tue, 18 Jan 2011 22:46:34 +0100, John Tyree<johntyree@gmail.com>  wrote:
>> [1.] Disk continually remounts and hardlocks the entire system if running on
>> battery.
>>
>> [2.] When I unplug the power cord from laptop, the harddrive immediately
>> stops spinning and nothing happens for up to ten seconds or more. During
>> this
>> time, absolutely nothing works except the mouse moving around in X.
>> Applications do not redraw their guis, Can't launch anything or close
>> anything. Just have to wait until it remounts and I hear the drive spin up.
>> At that time, everything snaps back to life as if nothing has happened.
>>
>> dmesg shows the following:
> oh, just look at ata errors, definitely this is not fs's problem,
> it's looks like your disk is dieing, Your options:
> 1) plug/unplug sata cable :), in my experience this is the root of cause
>     in 50% of cases.
> 2) smart ctl logs
>>
>> [28687.441335] ata1.00: configured for UDMA/33
>> [28687.441345] ata1: EH complete
>> [28687.443153] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled,
>> doesn't support DPO or FUA
>> [28688.563053] EXT4-fs (sda5): re-mounted. Opts: commit=600
>> [28688.570501] EXT4-fs (dm-0): re-mounted. Opts: commit=600
>> [28727.760100] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x110000 action
>> 0x6 frozen
>> [28727.760115] ata1: SError: { PHYRdyChg Dispar }
>> [28727.760126] ata1.00: failed command: WRITE DMA EXT
>> [28727.760144] ata1.00: cmd 35/00:08:5d:8b:e1/00:00:17:00:00/e0 tag 0 dma
>> 4096 out
>> [28727.760148]          res 40/00:f4:00:00:00/00:00:00:00:00/40 Emask 0x4
>> (timeout)
>> [28727.760156] ata1.00: status: { DRDY }
>> [28727.760170] ata1: hard resetting link
>> [28728.066096] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>> [28728.067819] ata1.00: configured for UDMA/33
>> [28728.068309] ata1.00: device reported invalid CHS sector 0
>> [28728.068337] ata1: EH complete
>> [28730.395512] ata1.00: configured for UDMA/33
>> [28730.395520] ata1: EH complete
>> [28730.430938] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
>> doesn't support DPO or FUA
>> [28730.953631] EXT4-fs (sda5): re-mounted. Opts: commit=0
>> [28730.958914] EXT4-fs (dm-0): re-mounted. Opts: commit=0
>>
>> This happens everytime the power is unplugged and continutes to happen, with
>> the harddrive spinning up and working for about 10 seconds before it happens
>> again. When the power is plugged back in, everything goes right back to
>> normal. This started with vanilla 2.6.37 from linus's git. I thought it
>> might
>> have something to do with laptop-mode, but disabling it did not change
>> anything.

Hmm, it seems like there's some kind of glitch happening on the SATA 
link. In this case it looks like PHY ready change event(s) happened. I 
would tend to suspect this being some kind of hardware problem. Are you 
sure this doesn't occur on older kernels?

  parent reply	other threads:[~2011-01-19  0:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=_GSgFpsidp35-RDT3i6zhimXtyR=d6UtFmfMe@mail.gmail.com>
2011-01-18 22:14 ` PROBLEM: Disk continually remounts and hardlocks the entire system if running on battery Dmitry
     [not found]   ` <AANLkTinCOrSBrLKxZfYw3HYNS=t8y8XqLxMXrjMWr1vb@mail.gmail.com>
2011-01-18 23:04     ` Dmitry
2011-01-19  0:18   ` Robert Hancock [this message]
     [not found]     ` <AANLkTi=ePSM7QTQgouAeP8xwLE0xFr3kW7iuBCqg8Wxb@mail.gmail.com>
2011-01-19 14:43       ` Robert Hancock
2011-01-19 14:59         ` Ted Ts'o
2011-01-19 15:01   ` 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=4D362DD2.8070606@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=dmonakhov@openvz.org \
    --cc=jiayingz@google.com \
    --cc=johntyree@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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.