kern/153205: PIONEER DVD-RW: timeout with ahci(4), OK with ata(4) + ATA_CAM

[Dmitry Pryanishnikov]

>Number:         153205
>Category:       kern
>Synopsis:       PIONEER DVD-RW: timeout with ahci(4), OK with ata(4) + ATA_CAM
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 16 08:50:06 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Dmitry Pryanishnikov
>Release:        RELENG_8
>Organization:
Home
>Environment:
FreeBSD lynx.homenet 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Thu Dec 16 01:36:59 EET 2010     root at lynx.homenet:/databig/obj/databig/ftp/RELENG_8/src.101215/sys/lynx  amd64

>Description:
Hardware: INTEL D975XBX2 mb, Intel Core2 Quad CPU (Q6600), 8Gb of ECC RAM, PATA HDD (SAMSUNG SP1614N), SATA HDD (Seagate ST31000520AS), SATA DVD-RW (PIONEER DVR-215D). Both SATA HDD and SATA DVD-RW are connected to Intel ICH7 SATA300 controller. Worked w/o problems using old ata(4) driver, still works OK using ata(4) in ATA_CAM mode. However, loading ahci(4) results in HDD still working, but DVD-RW doesn't even get detected during the boot (I've tried different SATA ports on this controller and different SATA cables - results are the same).

Kernel configuration:

http://sites.google.com/site/lynxripe/freebsd/pr/20101216-ahci/lynx?attredirects=0&d=1

loader.conf for ata(4) case (for using ahci(4) I simply load it from the loader's prompt):

http://sites.google.com/site/lynxripe/freebsd/pr/20101216-ahci/loader.conf?attredirects=0&d=1

Verbose dmesg w/o ahci module (DVD-RW attached by ata(4) and works OK):

http://sites.google.com/site/lynxripe/freebsd/pr/20101216-ahci/dmesg-v.boot?attredirects=0&d=1

Verbose dmesg with ahci module (DVD-RW does not attach):

http://sites.google.com/site/lynxripe/freebsd/pr/20101216-ahci/dmesg-v-ahci.boot?attredirects=0&d=1

I'm ready to provide any additional information about this HW and try patches on it.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: