linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Brad Campbell <brad@wasp.net.au>
Cc: Andy Warner <andyw@pobox.com>, Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org
Subject: Re: libata oops 2.6.11-rc4 yesterdays BK
Date: Mon, 21 Feb 2005 08:27:49 +0400	[thread overview]
Message-ID: <42196345.5040501@wasp.net.au> (raw)
In-Reply-To: <4216BD10.2070008@wasp.net.au>

Brad Campbell wrote:

> 
> Have been unable to hit the bug with SMART disabled (Kernel unchanged). 
> So...... Pass through (or SMART in particular) is not really safe on UP 
> either, you just have to work really hard at it to hit the corner cases.

I tried it last night with the latest and greatest Vanilla BK + libata + libata-dev and really 
pounded the poor machine hard with very rude bash scripts doing SMART polling from two separate 
tasks (so randomly I would poll the same drive with two different queries simultaneously) and I 
could certainly fail drives out of the array, but no oops.

So yes, SMART is causing timeouts but no longer causing an oops here.

Now I have also replaced the PSU with a much better specced unit, so that may have also been a 
contributing factor to the oops. (The 12v rail was running on the edge).

If this rebuild this morning gets through then I'll go back to the old kernel that was oopsing and 
try it again to compare.

Regards,
Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

  reply	other threads:[~2005-02-21  4:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  4:28 libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-16 11:01 ` Brad Campbell
2005-02-16 17:25   ` Jeff Garzik
2005-02-16 20:54     ` Brad Campbell
2005-02-16 21:40       ` Andy Warner
2005-02-16 22:47         ` Jeff Garzik
2005-02-16 23:49           ` Andy Warner
2005-02-16 23:58             ` Jeff Garzik
2005-02-17  0:20               ` Andy Warner
2005-02-17  5:08                 ` Jeff Garzik
2005-02-17 14:59                   ` Andy Warner
2005-02-17 19:13                     ` Jeff Garzik
2005-02-17 19:25                       ` Andy Warner
2005-02-17 22:36                         ` Jeff Garzik
2005-02-17 19:42                       ` Which SATA Combos To Consider? Danny Cox
2005-02-17 20:55                         ` Jeff Garzik
2005-02-18  0:25                         ` Ryan Bourgeois
2005-02-18  0:44                           ` Johny Ågotnes
2005-02-18  0:52                             ` Jeff Garzik
2005-02-21 23:50                               ` Johny Ågotnes
2005-02-21 23:50                               ` Johny Ågotnes
2005-02-22  1:55                                 ` Johny Ågotnes
2005-02-18  6:13         ` libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-19  4:14           ` Brad Campbell
2005-02-21  4:27             ` Brad Campbell [this message]
2005-02-22 10:09               ` Brad Campbell

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=42196345.5040501@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=andyw@pobox.com \
    --cc=jgarzik@pobox.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 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).