From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 7 05:20:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45A6916A46B; Fri, 7 Dec 2007 05:20:44 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.200.14]) by mx1.freebsd.org (Postfix) with ESMTP id 465CD13C4CE; Fri, 7 Dec 2007 05:20:43 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:18643 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S8372511AbXLGFI0 (ORCPT + 1 other); Fri, 7 Dec 2007 08:08:26 +0300 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <4758D544.5060405@yandex.ru> Date: Fri, 07 Dec 2007 08:08:20 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: cokane@FreeBSD.org References: <475897DB.1010308@FreeBSD.org> <4758B6E8.7030502@rcn.com> <4758BEAB.6020306@FreeBSD.org> In-Reply-To: <4758BEAB.6020306@FreeBSD.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Gary Corcoran Subject: Re: Overlap in PCI memory ranges X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2007 05:20:44 -0000 Coleman Kane wrote: > My apologies. The lines *should* read (mem ranges overlap): > > atapci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0609000-0xd06093ff irq 16 at device 18.0 on pci0 > ..... > pcm0: mem > 0xd0608000-0xd060bfff irq 16 at device 20.2 on pci0 Why you want to do it? Your SATA controoler doesn't works? Can you show a bit more log messages related to the atapci0? Also can you show `pciconf -l | grep ^atapci`? -- WBR, Andrey V. Elsukov