I’m runnning a AAEON AEC-6810 with 20 Gig Hard Drive and Compact Flash.
Everything boots and runs fine when booted from the HD.
Everything runs and seems to work ok when booted from the Compact Flash
which is configured on the Secondary IDE Controller. However traceinfo is
reporting “Cache invalidated caused by Timeout” on both read and write
access to the CF card. I’ve tried other Fsys.xxx drivers but only the
Fsys.eide seems to work.
Does anyone have a clue as to how to solve this or is it something I can
just ignore???
Thanks in advance…
Steve Higgs wrote:
Everything runs and seems to work ok when booted from the Compact Flash
which is configured on the Secondary IDE Controller. However traceinfo is
reporting “Cache invalidated caused by Timeout” on both read and write
access to the CF card. I’ve tried other Fsys.xxx drivers but only the
Fsys.eide seems to work.
Does anyone have a clue as to how to solve this or is it something I can
just ignore???
It can be ignored. It only happens for removable devices (hence CF and
not HD). After a timeout period, cached data for removable devices is
invalidated, which means a physical read of the device to refresh it.
So not an error, normal operation for removable. If your CF is wired
in such a way as to not really be removable (eg on-board vs in a PCMCIA
card) you can use the option “eide -R” to have the driver advertise it
as non-removable, which will have better performance because the cache
timeout/invalidation/refresh will not be performed.
Thanks John for the response. This makes total sense as my functional
testing has also proven this.
“John Garvey” <jgarvey@qnx.com> wrote in message
news:dr2vn5$h38$1@inn.qnx.com…
Steve Higgs wrote:
Everything runs and seems to work ok when booted from the Compact Flash
which is configured on the Secondary IDE Controller. However traceinfo is
reporting “Cache invalidated caused by Timeout” on both read and write
access to the CF card. I’ve tried other Fsys.xxx drivers but only the
Fsys.eide seems to work.
Does anyone have a clue as to how to solve this or is it something I can
just ignore???
It can be ignored. It only happens for removable devices (hence CF and
not HD). After a timeout period, cached data for removable devices is
invalidated, which means a physical read of the device to refresh it.
So not an error, normal operation for removable. If your CF is wired
in such a way as to not really be removable (eg on-board vs in a PCMCIA
card) you can use the option “eide -R” to have the driver advertise it
as non-removable, which will have better performance because the cache
timeout/invalidation/refresh will not be performed.