John Asher wrote: > I am also using the 6-CURRENT kernel i386 (i686) have somethimes at > heavy load the same errors. > turn off preemption and let me know how it goes then.. > Sep 16 12:41:45 xxx kernel: FreeBSD 6.0-CURRENT #0: Wed Sep 15 15:27:42 CE > ST 2004 > > Sep 16 14:37:45 xxx kernel: ad1: TIMEOUT - READ_DMA retrying (2 retries le > ft) LBA=14578175 > > I completely updated my sourcetree at that day, and recompiled the > kernel, since that time this error occurs. > > Best regards, > > John Asher. > > On Thu, 16 Sep 2004 21:17:45 +0200, Daniel Eriksson > <daniel_k_eriksson_at_telia.com> wrote: > >> >> This is a me-too report: >> >> After upgrading a 6-CURRENT kernel and world from 2004.09.09.08.00.00 to >> 2004.09.16.13.00.00, I am now getting these messages on a machine that >> previously worked just fine: >> >> ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=75822564 >> ad0: WARNING - READ_DMA no interrupt but good status >> ad12: TIMEOUT - READ_DMA retrying (2 retries left) LBA=107702399 >> ad12: WARNING - READ_DMA no interrupt but good status >> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=150299860 >> ad2: WARNING - READ_DMA no interrupt but good status >> ad3: TIMEOUT - READ_DMA retrying (2 retries left) LBA=150375742 >> ad3: WARNING - READ_DMA no interrupt but good status >> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=68555470 >> ad2: WARNING - READ_DMA no interrupt but good status >> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=152916568 >> ad2: WARNING - READ_DMA no interrupt but good status >> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=177638432 >> ad2: WARNING - READ_DMA no interrupt but good status >> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=326989843 >> ad14: WARNING - READ_DMA no interrupt but good status >> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=327711355 >> ad14: WARNING - READ_DMA no interrupt but good status >> >> I only get the messages when I blast the discs with I/O, like when doing >> fsck on all the file systems simultaneously. Also, fsck does not >> report any >> problems so all operations seem to succeed. >> >> Other then cvsup'ing the new sources, no other changes were made to the >> machine or the configuration. >> >> /Daniel Eriksson >> >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe_at_freebsd.org" > > > >Received on Mon Sep 20 2004 - 05:01:02 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:12 UTC