Julian Elischer wrote: > turn off preemption and let me know how it goes then.. I did not have preemption defined in the (SHED_4BSD) kernel I used when I got the error messages below. > >> 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 /Daniel ErikssonReceived on Mon Sep 20 2004 - 05:21:43 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:12 UTC