From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 11 11:45:37 2011 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A0F91065670; Mon, 11 Apr 2011 11:45:37 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2E8768FC12; Mon, 11 Apr 2011 11:45:35 +0000 (UTC) Received: by bwz12 with SMTP id 12so5701341bwz.13 for ; Mon, 11 Apr 2011 04:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G9BQ3zwgHBT7BdwUZNdsYv68G14r1GwnTtE2M1D3eVU=; b=VvVf2MGuC8i0q3NMg+UGmOt9xCJHuW5PPxylD/kTyXKlZNBH9hL62mj3YIS50B5xdv XErvPyaWyIOWuXMOFVj1PBX5NEQNQqVyCWBZXU5whLPXAW29dxxxqJnRzLuEMPL3OyTk 5mQpy4+43qSfVZzhsequIl5d1Od4EtwCS9lhg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=cXDU94NzZ8kc/HuPG9RvomWLzm41cIEnzRRr5IJnKzABrSafkh0aqnhcvkuh2QeYcW te8Bms1oJi35EYpEanUqIPLqvmTkE5g35xv5ac5d61/0j9aVABMtXx9kYzX/VTc4KIRM ZYinK189nI8EJkUnpRb4+SG4Yi7cAGE5p9Z8k= Received: by 10.204.19.70 with SMTP id z6mr2234940bka.204.1302522335053; Mon, 11 Apr 2011 04:45:35 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id b6sm3161321bkb.22.2011.04.11.04.45.33 (version=SSLv3 cipher=OTHER); Mon, 11 Apr 2011 04:45:34 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DA2E9DC.108@FreeBSD.org> Date: Mon, 11 Apr 2011 14:45:32 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110310 Thunderbird/3.1.9 MIME-Version: 1.0 To: Alexander Best References: <20110331223339.GA13682@freebsd.org> <201104010843.47367.jhb@freebsd.org> <20110404204316.GA11367@freebsd.org> <4D9D9917.3030102@FreeBSD.org> <20110410115644.GA55815@freebsd.org> <4DA210D3.5090807@FreeBSD.org> <20110411025646.GA46088@freebsd.org> <4DA2A33B.8010807@FreeBSD.org> <20110411083821.GA80320@freebsd.org> <4DA2C14F.60905@FreeBSD.org> <20110411093415.GA87477@freebsd.org> In-Reply-To: <20110411093415.GA87477@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: multiple issues with devstat_*(9) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 11:45:37 -0000 On 11.04.2011 12:34, Alexander Best wrote: > On Mon Apr 11 11, Alexander Motin wrote: >> Alexander Best wrote: >>> On Mon Apr 11 11, Alexander Motin wrote: >>>> Alexander Best wrote: >>>>> my cd0 is a pata atapi dvdrom drive and i have the following in my kernel conf: >>>>> >>>>> device atacore >>>>> device ahci >>>>> device atajmicron >>>>> device atapci >>>>> #device atapicd >>>>> device atapicam >>>>> >>>>> device umass >>>>> device scbus >>>>> device cd >>>>> device pass >>>>> device da >>>>> device random >>>>> device pty >>>>> device md >>>>> >>>>> the dmesg entries for cd0 are: >>>>> >>>>> cam_periph_alloc: attempt to re-allocate valid device cd0 rejected >>>>> cdasync: Unable to attach new device due to status 0x6 >>>>> cd0 at ata2 bus 0 scbus8 target 0 lun 0 >>>>> cd0: Removable CD-ROM SCSI-0 device >>>>> cd0: 3.300MB/s transfers >>>>> cd0: cd present [2149024 x 2048 byte records] >>>> Aha, that's it. It is atapicam's lie. atapicam is one of a things that >>>> will go away during migration to CAM ATA. If you remove `device >>>> atapicam`, but add `options ATA_CAM` instead, CAM will manage that bus >>>> directly and report it as ATA. >>> >>> thanks for the hint. i also read the following in the ahci(4) man page: >>> >>> " Driver features include support for Serial ATA and ATAPI devices, ..." >>> >>> ...does that mean that my DVD drive can also attach to the ahci driver? >> >> If it is SATA and you connect it to AHCI controller -- yes, it will work >> with ahci(4) controller driver. > > no it's PATA. thanks for the help. i'll remove atapicam from my kernel conf > and add ATA_CAM. > > maybe we could have a list of supported controllers in the ahci(4) man page. We could do it (you can find list of known inside ahci.c), but unlike others, AHCI is an open specification, so that list will never be complete. Also on some chipsets AHCI support also depends on BIOS, so specification of just a chipset revisions can be inaccurate. > will the ataahci driver also dissapear soon? Yes, at least disabled. Same as most part of the atasiliconimage and the atamarvell. -- Alexander Motin