freebsd stable - Oct 2015 - 9-STABLE showing disk timeouts

Hi,

I'm in the process of updating a machine to 9-STABLE from a week or two
ago. When compiling masses of ports something never seen before happens:

Oct 19 11:54:26 puma kernel: ahcich3: Timeout on slot 28 port 0
Oct 19 11:54:26 puma kernel: ahcich3: is 00000008 cs 00000000 ss 00000000 rs
ffffffff tfd 50 serr 00000000 cmd 00007c17
Oct 19 11:54:26 puma kernel: (ada1:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61
40 7f 6b aa 40 09 00 00 00 00 00
Oct 19 11:54:26 puma kernel: (ada1:ahcich3:0:0:0): CAM status: Command timeout
Oct 19 11:54:26 puma kernel: (ada1:ahcich3:0:0:0): Retrying command

And another one:

Oct 18 15:16:20 puma kernel: ahcich3: Timeout on slot 19 port 0
Oct 18 15:16:20 puma kernel: ahcich3: is 00000008 cs 00000000 ss 00000000 rs
ffffffff tfd 50 serr 00000000 cmd 00007317
Oct 18 15:16:20 puma kernel: (ada1:ahcich3:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61
08 df c6 5d 40 11 00 00 00 00 00
Oct 18 15:16:21 puma kernel: (ada1:ahcich3:0:0:0): CAM status: Command timeout
Oct 18 15:16:21 puma kernel: (ada1:ahcich3:0:0:0): Retrying command

These are the two occurances I saw running through on the console, there may be
more.

The disk is one of those funny things getting active when idle after writing big
files to it:
ada1: <TOSHIBA DT01ACA200 MX4OABB0> ATA8-ACS SATA 3.x device

ahci1: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port
0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem
0xfe4ffc00-0xfe4fffff irq 19 at device 17.0 on pci0
ahci1: AHCI v1.20 with 4 6Gbps ports, Port Multiplier supported
ahcich2: <AHCI channel> at channel 0 on ahci1
ahcich3: <AHCI channel> at channel 1 on ahci1
ahcich4: <AHCI channel> at channel 2 on ahci1
ahcich5: <AHCI channel> at channel 3 on ahci1

What is happening there and why?
Do I need to worry?

TIA,
Marc

-- 
Marc Santhoff <M.Santhoff at web.de>

Hi,

On Mon, 19 Oct 2015 18:05:15 +0200
Marc Santhoff <M.Santhoff at web.de> wrote:
> What is happening there and why?
I have the same problem with one specific connection. Can you check the
cable? Can you switch to another connector?
> Do I need to worry?
Not, if it was the connection.

Erich