:also got those while running:
:
:----8<---- messages ----8<----
:Nov 20 20:38:02 tower kernel: ad4: READ command timeout tag=0 serv=0 status 50 dmastatus 00 - resetting
:Nov 20 20:38:02 tower kernel: ata2: resetting devices .. ata2: mask=03 ostat0=50 ostat2=00
:Nov 20 20:38:02 tower kernel: ad4: ATAPI 00 00
:Nov 20 20:38:02 tower kernel: ata2-slave: ATAPI 00 00
:Nov 20 20:38:02 tower kernel: ata2: mask=03 stat0=50 stat1=00
:Nov 20 20:38:02 tower kernel: ad4: ATA 01 a5
:Nov 20 20:38:02 tower kernel: ata2: devices=01
:Nov 20 20:38:02 tower kernel: ad4: success setting WDMA2 on generic chip
:Nov 20 20:38:02 tower kernel: done
:Nov 20 20:38:34 tower kernel: ad4: READ command timeout tag=0 serv=0 status 50 dmastatus 00 - resetting
:Nov 20 20:38:34 tower kernel: ata2: resetting devices .. ata2: mask=03 ostat0=50 ostat2=00
:Nov 20 20:38:34 tower kernel: ad4: ATAPI 00 00
:Nov 20 20:38:34 tower kernel: ata2-slave: ATAPI 00 00
:Nov 20 20:38:34 tower kernel: ata2: mask=03 stat0=50 stat1=00
:Nov 20 20:38:34 tower kernel: ad4: ATA 01 a5
:Nov 20 20:38:34 tower kernel: ata2: devices=01
:Nov 20 20:38:34 tower kernel: ad4: success setting WDMA2 on generic chip
:Nov 20 20:38:34 tower kernel: done
:---->8---- messages ---->8----
:
:Andy
Ok, now try the latest HEAD (with all my recent clock commits) with and
without the ATA Patch #6. The "one hour off" problem that I fixed also
effects the callout timers, and I'm hoping that gets rid of the command
timeouts.
-Matt
Matthew Dillon
<dillon@backplane.com>