From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
To: Bruce Allen <ballen@gravity.phys.uwm.edu>
Cc: Henrik Persson <nix@syndicalist.net>, linux-kernel@vger.kernel.org
Subject: Re: Strange DMA-errors and system hang with Promise 20268
Date: Wed, 10 Mar 2004 16:41:37 +0100 [thread overview]
Message-ID: <20040310154137.GC31893@darkside.22.kls.lan> (raw)
In-Reply-To: <Pine.GSO.4.21.0403100547430.8400-100000@dirac.phys.uwm.edu>
On Wed, Mar 10, 2004 at 05:50:12AM -0600, Bruce Allen wrote:
> > > I suspect it having something to do with 2.4.25 new "One last
> > > read after the timeout" in ide-iops.c and accessing the drive
> > > while selftest running (possibly especially short selftest).
> Does the disk's SMART error log (smartctl -l error) show any entries
Just in addition, to point this out more clearly:
I personally don't suspect smartmontools having some
problem.
I run debians smartmontools package since a long time
and it does the selftests a long time as well. It never
had problems with it, it wasnt updated close to first
occurence of the problem or changed in any other way.
I have 4 disks, 2 on the onboard VIA controller, 2 on
the Promise. The problem always occured on the Promise
(like Henrik pointed too) disk.
I more suspect any kernel ide <-> promise-driver timing
problem. Maybe smartmontools makes it more possibe that
this timing problem occurs, maybe not (with Henriks
answer to my question I rather favorite the 'maybe not'),
maybe it's even just some load issue making the problem
occur.
Mario
--
<jv> Oh well, config
<jv> one actually wonders what force in the universe is holding it
<jv> and makes it working
<Beeth> chances and accidents :)
next prev parent reply other threads:[~2004-03-10 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 19:47 Henrik Persson
2004-03-06 19:55 ` Henrik Persson
2004-03-07 1:05 ` Mario 'BitKoenig' Holbe
2004-03-08 13:30 ` Henrik Persson
2004-03-10 11:50 ` Bruce Allen
2004-03-10 12:36 ` Mario 'BitKoenig' Holbe
2004-03-10 15:00 ` Henrik Persson
2004-03-11 9:36 ` Bruce Allen
2004-03-11 14:31 ` Henrik Persson
2004-03-10 15:41 ` Mario 'BitKoenig' Holbe [this message]
2004-03-11 9:25 ` Bruce Allen
2004-05-19 17:20 ` Sebastian
2004-05-19 17:28 ` Mario 'BitKoenig' Holbe
2004-05-19 18:12 ` Sebastian
[not found] ` <1648.128.150.143.219.1084992082.squirrel@webmail.seven4sky.com>
2004-05-19 20:12 ` Strange DMA-errors... (was: ...and system hang with Promise 20268) Sebastian
2004-05-19 23:47 ` Mario 'BitKoenig' Holbe
2004-05-20 9:23 ` Strange DMA-errors and system hang with Promise 20268 Bruce Allen
2004-05-20 10:35 ` Strange DMA-errors and system hang with SMART (was: ...and system hang with Promise 20268) Sebastian
2004-05-23 12:46 ` Bruce Allen
2004-06-02 19:00 ` Sebastian
2004-06-03 15:06 ` Bruce Allen
2004-05-29 14:42 ` Strange DMA-errors and system hang with Promise 20268 Mario 'BitKoenig' Holbe
2004-05-29 22:51 ` Gene Heskett
2004-05-30 10:41 ` Henrik Persson
2004-06-04 20:09 ` Bruce Allen
[not found] ` <200405052339.i45NdXsx003369@darkside.22.kls.lan>
[not found] ` <1083849053.6994.10.camel@vega>
2004-05-06 14:22 ` Mario 'BitKoenig' Holbe
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=20040310154137.GC31893@darkside.22.kls.lan \
--to=mario.holbe@rz.tu-ilmenau.de \
--cc=ballen@gravity.phys.uwm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@syndicalist.net \
/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
all inboxes | Powered by JetHome®