Thanks. This also points out that I mistakenly said DMA rather than
UDMA. Someone else mentioned to me that MDMA worked for them as well.
It would have been "fine" if the serverworks driver didn't leave UDMA on
when it's off by default in the CONFIG. At least then you would be
making the choice to specifically enable UDMA at your own risk...
| This was observed across a large number of boxes in a rendering farm so its
| not a one off flawed box, and across two board vendors. I reported it to
| serverworks who were interested but couldnt reproduce it in their lab.
Quite possible. I'm only seeing this on ServerWorks mobos with IDE as
primary (vs SCSI). I heard third-hand via a FreeBSD post that it's an
OSB4 issue effecting them as well. Are Seagates a requirement for the
issues?
As to whether they can reproduce it... I'm not holding my breath for
them to try.
Thanks much for the info,
-- Ken. ken@irridia.com - 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/