From owner-freebsd-current@FreeBSD.ORG Sun Nov 11 16:33:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E7B916A417 for ; Sun, 11 Nov 2007 16:33:42 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id BEE8813C481 for ; Sun, 11 Nov 2007 16:33:41 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.local (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id lABGXNBY030772; Sun, 11 Nov 2007 17:33:23 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <47372ED3.8030004@deepcore.dk> Date: Sun, 11 Nov 2007 17:33:23 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Arno J. Klaassen" References: <47326FB8.50602@fusiongol.com> <4732CEE3.3070003@lxnt.info> <4732DA32.3090601@deepcore.dk> <4732E18A.6040802@lxnt.info> <4732E37F.9020707@deepcore.dk> <4732E7C2.3030403@lxnt.info> <4736DC08.3030809@deepcore.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Nathan Butcher , Alexander Sabourenkov , freebsd-current@freebsd.org Subject: Re: Remaining SATA (and other) issues TAKE 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2007 16:33:42 -0000 Arno J. Klaassen wrote: > I still test first on releng_6, but initial testing indicates > it solves my problems. > =20 > Thank you very much! > =20 Now it would be interesting to know if both parts of the patch are=20 needed, can you test that ? That is just the part that changes the burst length, and just the part=20 that hacks the SG list. > NB, I still get an error in ata_pci_attach() when > bus_alloc_resource_any() for ATA_BMADDR_RID : > > pci0: child atapci0 requested type 4 for rid 0x20, but the BAR says i= t is an memio > > When I retry with "ctlr->r_type1 =3D SYS_RES_MEMORY" (diff attached) > it says : > > atapci0: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xfba00000 > > which it anyway says as well a bit later when attaching : > > ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49 > atapci0: [MPSAFE] > atapci0: Reserved 0x20000 bytes for rid 0x20 type 3 at 0xfba00000 > atapci0: Reserved 0x1000 bytes for rid 0x1c type 3 at 0xfbb00000 > atapci0: [MPSAFE] > > > Just if ever this info helps you; the failing bus_alloc_resource_any() > for ATA_BMADDR_RID does not seem to have any influence. > =20 That's just harmless verbose chatter from the PCI subsystem. It needs to = grow functionality to tell what kind of resources are there. I'll change ATA to take advantage of that when present, until then I=20 have no intention of poking around PCI space registers on my own. Keep snot and beard sorted as we say over here :) -S=F8ren