Date: Thu, 11 Mar 2004 03:25:33 -0600 (CST)
From: Bruce Allen <ballen@gravity.phys.uwm.edu>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@RZ.TU-Ilmenau.DE>
cc: Henrik Persson <nix@syndicalist.net>, linux-kernel@vger.kernel.org
Subject: Re: Strange DMA-errors and system hang with Promise 20268
In-Reply-To: <20040310154137.GC31893@darkside.22.kls.lan>
Message-ID: <Pine.GSO.4.21.0403110321090.11871-100000@dirac.phys.uwm.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1681
Lines: 37

> 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.

OK, thanks for the reassurance.  There have been some warnings about
promise 20262 and 20265 controllers interacting badly with smartmontools
(locking up systems).  See
http://cvs.sourceforge.net/viewcvs.py/smartmontools/sm5/WARNINGS?view=markup
Perhaps this is in some way related.

Cheers,
	Bruce

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/