It seems Peter Jeremy wrote:
> Yesterday, I upgraded my system from mid-Jan to the latest
> (cvs-cur.6044) to see if it would cure some hard-hangs.
>
> Last night, I got the following messages:
>
> Feb 1 18:00:21 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting
> Feb 1 18:00:21 gsmx07 /kernel: ata1: resetting devices .. done
> Feb 1 18:00:21 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting
> Feb 1 18:00:21 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout
>waiting for command=ef s=00 e=64
> Feb 1 18:00:21 gsmx07 /kernel: done
> Feb 1 18:05:40 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting
> Feb 1 18:05:40 gsmx07 /kernel: ata1: resetting devices .. done
> Feb 1 18:05:40 gsmx07 /kernel: ad0: ad_timeout: lost disk contact - resetting
> Feb 1 18:05:40 gsmx07 /kernel: ata0: resetting devices .. ata0-slave: timeout
>waiting for command=ef s=00 e=64
> Feb 1 18:05:40 gsmx07 /kernel: done
>
> The system should have been virtually quiescent at this time. Any
> suggestions? I am running soft-updates.
> Feb 1 11:49:38 gsmx07 /kernel: ad0: 6187MB <FUJITSU MPB3064ATU E> [13410/15/63] at
>ata0-master using UDMA33
> Feb 1 11:49:38 gsmx07 /kernel: ad2: 1222MB <QUANTUM FIREBALL_TM1280A> [2484/16/63]
>at ata1-master using WDMA2
Try to switch of DMA on ad2 with the systel like documented ata.4 and
see if that helps...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
