Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Jun 2015 09:31:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 199495] relates to Bug 195349 - CAM status: command timeout
Message-ID:  <bug-199495-8-EOzFsRHKNu@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-199495-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-199495-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199495

--- Comment #2 from Yudi <yudi.tux@gmail.com> ---
I just want to update my original post it had some inaccurate info.
First, this bug is present in v9.3 as well as v10.1 but NOT in v11. 

I have added the following to /boot/loader.conf but did not resolve the issue:
"hint.atapci.0.msi="0" (also 1)
"hint.atapci.1.msi="0"
"hint.ahci.0.msi="1"

I even tried rebuilding the kernel but looks like it did not fix the issue.
Well, this was my first time building a custom kernel, so I am not sure I got
this right.

the steps I followed were:

I used the LINT config instead of creating my own,

# svn checkout svn-mirror/base/head     /usr/src
# cd /usr/src/sys/amd64/conf && make LINT
# cd /usr/src 
# make buildkernel KERNCONF=LINT 
# make installkernel KERNCONF=LINT

one of the replies I receive on the mailing list suggested this is not the
right way to rebuild the kernel. He said I was using v11 source files to build
the kernel for v10.

I dont think that was accurate. Can someone please explain how I can apply the
patch.

Bit of info on the system,
the Hitachi drives are in a 2-way mirror connected to 3Gbps SATA ports (AHCI
mode) which I am not using until I fix this issue. OS is installed on the
samsung drives (2-way mirror) connected to 1.5Gbps SATA ports  running in IDE
mode (cannot change this to AHCI without installing a hacked version of BIOS
which I dont want to do).

I would greatly appreciate any advise on how to fix this issue.
Below I added some output from the system that might help.

=============================
output of "camcontrol devlist"
===================================
<Hitachi HDS723030ALA640 MKAOAA10>  at scbus0 target 0 lun 0 (ada0,pass0)
<Hitachi HDS723030ALA640 MKAOAA10>  at scbus2 target 0 lun 0 (ada1,pass1)
<SAMSUNG HM080HI AB100-17>         at scbus4 target 0 lun 0 (ada2,pass2)
<SAMSUNG HM080HI AB100-17>         at scbus4 target 1 lun 0 (ada3,pass3)
======================================================
====================================
ERROR from /var/log/messages
=================================

Jun 28 21:22:47 10p1test kernel: (ada3:ata0:0:1:0): READ_DMA. ACB: c8 00 88 00
41 44 00 00 00 00 01 00
Jun 28 21:22:47 10p1test kernel: (ada3:ata0:0:1:0): CAM status: Command timeout
Jun 28 21:22:47 10p1test kernel: (ada3:ata0:0:1:0): Retrying command
Jun 28 21:23:21 10p1test kernel: (ada2:ata0:0:0:0): READ_DMA. ACB: c8 00 0d 30
c0 45 00 00 00 00 01 00
Jun 28 21:23:21 10p1test kernel: (ada2:ata0:0:0:0): CAM status: Command timeout
Jun 28 21:23:21 10p1test kernel: (ada2:ata0:0:0:0): Retrying command
Jun 28 21:40:33 10p1test kernel: (ada2:ata0:0:0:0): READ_DMA. ACB: c8 00 51 30
70 45 00 00 00 00 01 00
Jun 28 21:40:33 10p1test kernel: (ada2:ata0:0:0:0): CAM status: Command timeout
Jun 28 21:40:33 10p1test kernel: (ada2:ata0:0:0:0): Retrying command
========================================

output of  "dmesg | grep ahci"

    =============================
    ahci0: <AMD SB7x0/SB8x0/SB9x0 AHCI SATA controller> port
0xd000-0xd007,0xc000-0xc003,0xb000-0xb007,0xa000-0xa003,0x9000-0x900f mem
0xfe6ffc00-0xfe6fffff irq 19 at device 17.0 on pci0
    ahci0: AHCI v1.20 with 4 3Gbps ports, Port Multiplier supported
    ahcich0: <AHCI channel> at channel 0 on ahci0
    ahcich1: <AHCI channel> at channel 1 on ahci0
    ahcich2: <AHCI channel> at channel 2 on ahci0
    ahcich3: <AHCI channel> at channel 3 on ahci0
    ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
    ada1 at ahcich2 bus 0 scbus2 target 0 lun 0

======================================


output of "dmesg |grep ada"
============================
 random: selecting highest priority adaptor <Dummy>
random: selecting highest priority adaptor <Yarrow>
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <Hitachi HDS723030ALA640 MKAOAA10> ATA8-ACS SATA 3.x device
ada0: Serial Number MK0301YHKT8A2A
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ahcich2 bus 0 scbus2 target 0 lun 0
ada1: <Hitachi HDS723030ALA640 MKAOAA10> ATA8-ACS SATA 3.x device
ada1: Serial Number MK0301YHKV1JWD
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad8
ada2 at ata0 bus 0 scbus4 target 0 lun 0
ada2: <SAMSUNG HM080HI AB100-17> ATA-7 SATA 1.x device
ada2: Serial Number S0ZAJD0P700140
ada2: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada2: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad0
ada3 at ata0 bus 0 scbus4 target 1 lun 0
ada3: <SAMSUNG HM080HI AB100-17> ATA-7 SATA 1.x device
ada3: Serial Number S0ZAJD0P700102
ada3: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada3: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad1
===============================

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199495-8-EOzFsRHKNu>