linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: John Tyree <johntyree@gmail.com>, Dmitry <dmonakhov@openvz.org>,
	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: Wed, 19 Jan 2011 09:59:28 -0500	[thread overview]
Message-ID: <20110119145928.GC3043@thunk.org> (raw)
In-Reply-To: <AANLkTimh01GO1wxOWzYmPsyh0EuTCuxzr6+krNVTjRCP@mail.gmail.com>

On Wed, Jan 19, 2011 at 08:43:03AM -0600, Robert Hancock wrote:
> 
> That doesn't look like the same thing - in their case it doesn't look
> like any SATA errors are occurring, just a remount (presumably
> triggered by some userspace software).

If you have laptop mode, you definitely want to disable it, and see if
that makes a difference.  That being said, if userspace code is able
to trigger errors like that from the hardware, I'd say at first glance
the kernel should do a better job protecting itself from buggy
software, even if it is buggy software running as root....

	       	     	      	       	       - Ted

      reply	other threads:[~2011-01-19 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=_GSgFpsidp35-RDT3i6zhimXtyR=d6UtFmfMe@mail.gmail.com>
     [not found] ` <87ipxlj1vd.fsf@dmon-lp.sw.ru>
2011-01-19  0:18   ` PROBLEM: Disk continually remounts and hardlocks the entire system if running on battery Robert Hancock
     [not found]     ` <AANLkTi=ePSM7QTQgouAeP8xwLE0xFr3kW7iuBCqg8Wxb@mail.gmail.com>
2011-01-19 14:43       ` Robert Hancock
2011-01-19 14:59         ` Ted Ts'o [this message]

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=20110119145928.GC3043@thunk.org \
    --to=tytso@mit.edu \
    --cc=dmonakhov@openvz.org \
    --cc=hancockrwd@gmail.com \
    --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=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 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).