MEMORY errors explian please.
If you mean data corruption please use those words, they are screaming red
flags for attention.
On 18 Aug 2002, Ed Sweetman wrote:
> Ok, devfs was removed and I got the old way working again. cerberus
> reports MEMORY errors when dma is enabled on the promise controller less
> than 30 seconds after the test has begun. Just like every other time
> i've had dma enabled on the promise controller.
>
> So it's not preempt. It's not devfs. So now we have to face the fact
> that it's either a hardware conflict that linux cannot handle or a
> device driver bug.
>
> Any other suggestions?
>
> Now that i'm down to vanilla 2.4.19 perhaps it's time for some real
> tests?
>
>
> On Sun, 2002-08-18 at 05:16, Ed Sweetman wrote:
> > On Sun, 2002-08-18 at 05:10, Alexander Viro wrote:
> > >
> > >
> > > On 18 Aug 2002, Ed Sweetman wrote:
> > >
> > > > (overview written in hindsight of writing email)
> > > > I ran all these tests on ide/host2/bus0/target0/lun0/part1
> > >
> > > Don't be silly - if you want to test anything, devfs is the last thing
> > > you want on the system.
> > >
> > >
> >
> >
> > OK, i can remove devfs, but I dont really see how that would make dma
> > transfers (memory) become corrupted and pio mode transfers (memory) to
> > not.
> >
> > I'm going to remove it, but i dont see how it's going to affect what's
> > going on.
>
>
>
Andre Hedrick
LAD Storage Consulting Group
-
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/