Re: Undo aic7xxx changes

[Stephan von Krawczynski (skraw@ithnet.com)]

On Fri, 30 May 2003 09:34:56 -0400
Jeff Garzik <jgarzik@xxxxxxxxx> wrote:

> On Fri, May 30, 2003 at 10:09:00AM +0200, Stephan von Krawczynski wrote:
> > Hello Marcelo,
> > 
> > I tried plain rc6 now and have to tell you it does not survive a single day
> > of my usual tests. It freezes during tar from 3ware-driven IDE to
> > aic-driven SDLT. This is identical to all previous rc (and some pre)
> > releases of 2.4.21. So far I can tell you that the only thing that has
> > recently cured this problem is replacing the aic-driver with latest of
> > justins' releases.
> 
> So Justin's driver fixes your 3ware problems???

This is _no_ 3ware problem. As I told you data comes from 3ware and goes to
aic. The problem occurs if using plain-version aic and is gone if using justins
latest releases.
As long as we do nothing with the aic driver there is no problem at all (3ware
works fine here).

> And exactly what -rc/-pre release stopped working for you?

Very good question. I can check, but I need one day per version to check. It
may well be that in fact none of the pre/rc releases worked, we have this box
since about pre3 and to my knowledge we always had the problem. Boy, we were
quite happy when we found out that Justins stuff got it going - it already got
on our nerves quite a bit ;-)

If you want to know about some special kernel release just tell me and I will
try it.

Maybe I should tell again details about the test setup as not all may remember
in this long-lasting thread.
Basically the problem seldomly arises after booting. I have the impression that
this got in fact better over the releases, earlier pre's froze earlier.
what we do:
1) copy around 50 - 100 GB of data via nfs to a 3ware drive (always works well)
2) tar this data on the nfs server from 3ware drive to aic(-driven) SDLT
(quantum)
3) verify the archived data via tar

freezes happen while 2) or 3). If you reboot after 1) they are very rare, never
on any later rc-release.
As this whole things takes time we do it overnight and have a look at the box
next morning. Not a single plain release is ok on the next morning. Checking
the logs we find out it froze in 2) or 3).
If you do exactly the same thing on exactly the same box with exactly the same
data but Justins driver everything is ok (aic-20030523). It was not ok with
aic-20030520 (just to mention this), aic-20030502 was quite ok (survived 14 days).

What else can I tell you?

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