Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes: > No tags, like you said. Previously, with a tags-capable kernel, > enabling tags would cause a continuous stream of timeouts and resets > on both disks.
Just for kicks, I removed the #if 0 in ata-disk.c and got exactly the same symptoms as before: ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad0: 9641MB <IBM-DTTA-371010> [19590/16/63] at ata0-master tagged UDMA33 ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ata0: resetting devices .. ad0: invalidating queued requests done ad0: no request for tag=0 ad0: invalidating queued requests ad1: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata1-master tagged UDMA33 acd0: CD-RW <HL-DT-ST GCE-8400B> at ata0-slave WDMA2 ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad0: READ command timeout tag=0 serv=1 - resetting ad0: invalidating queued requests ad0: trying fallback to PIO mode ata0: resetting devices .. ad0: invalidating queued requests done ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ata1: resetting devices .. ad1: invalidating queued requests done ad1: no request for tag=0 ad1: invalidating queued requests ad1: no request for tag=0 ad1: invalidating queued requests ad1: READ command timeout tag=0 serv=1 - resetting ad1: invalidating queued requests ad1: trying fallback to PIO mode ata1: resetting devices .. ad1: invalidating queued requests done it never even got to mounting root, I grew tired of waiting and coldbooted it. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message