From owner-freebsd-current@FreeBSD.ORG Wed Nov 22 21:04:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94B6916A407; Wed, 22 Nov 2006 21:04:27 +0000 (UTC) (envelope-from sepotvin@videotron.ca) Received: from tomts28-srv.bellnexxia.net (tomts28.bellnexxia.net [209.226.175.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A23143D73; Wed, 22 Nov 2006 21:03:51 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from toip41-bus.srvr.bell.ca ([67.69.240.42]) by tomts28-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20061122210419.IVQX774.tomts28-srv.bellnexxia.net@toip41-bus.srvr.bell.ca>; Wed, 22 Nov 2006 16:04:19 -0500 Received: from unknown (HELO mail.telcobridges.com) ([67.70.237.76]) by toip41-bus.srvr.bell.ca with ESMTP; 22 Nov 2006 16:04:19 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAGxIZEVDRu1M/2dsb2JhbAA Received: from [10.0.0.213] (yoda.telcobridges.com [10.0.0.213]) (authenticated bits=0) by mail.telcobridges.com (8.13.3/8.13.3) with ESMTP id kAML41HK059922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Nov 2006 16:04:09 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <455C2290.6010907@videotron.ca> Date: Thu, 16 Nov 2006 03:34:24 -0500 From: "Stephane E. Potvin" User-Agent: Thunderbird 1.5.0.8 (X11/20061111) MIME-Version: 1.0 To: Doug Barton References: <4564996D.50808@FreeBSD.org> In-Reply-To: <4564996D.50808@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: EHCI problem on -current, and unknown devs 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: Wed, 22 Nov 2006 21:04:27 -0000 Doug Barton wrote: > [ No response from the -usb list, so I'll try here. ] > > Howdy, > > I have a new Dell Latitude D620, and using recent -current I get this: > > ehci0: mem > 0xffa80000-0xffa803ff irq 20 at device 29.7 on pci0 > ehci0: Could not map memory > device_attach: ehci0 attach returned 6 > > FWIW, I also saw a user on the -stable list report this same problem. > I'm assuming this is bad, but what to do about it? > > > I'm also getting some unknown devices: > > uhub4: 2> on uhub0 > uhub5: 3> on uhub4 > ugen2: addr 6> on uhub4 > uhub6: 2> on uhub3 > > Vendor ID 0x413c is Dell, and is already in the usbdevs file. The > other vendor is O2, and I got their ID for the attached patch from the > list at http://www.usb.org/developers/tools. The 0x0058 device is > already in our usbdevs file, it's the port replicator (docking > station) that the laptop is plugged into currently. I added the 0x8103 > device in the attached patch based on an entry in the NetBSD usbdevs > file. (The entry makes sense to me as well, since I have one of those.) > > So I have two questions ... for the devices (and vendors) that are > already in my local usbdevs file, why are they still showing up by ID? > And how do I find the device IDs for the two unknown devices? I > imagine that the O2 device is related to my built in smart card > reader, not sure about the other one. > Hi Doug, I had the same problem with my Dell Inspiron 9400 and fixed it using the following patch: Index: sys/kern/subr_rman.c =================================================================== RCS file: /home/FreeBSD/ncvs/src/sys/kern/subr_rman.c,v retrieving revision 1.53 diff -u -r1.53 subr_rman.c --- sys/kern/subr_rman.c 11 Sep 2006 19:31:52 -0000 1.53 +++ sys/kern/subr_rman.c 2 Nov 2006 03:05:34 -0000 @@ -170,7 +170,7 @@ /* Skip entries before us. */ for (s = TAILQ_FIRST(&rm->rm_list); - s && s->r_end + 1 < r->r_start; + s && s->r_end < r->r_start; s = TAILQ_NEXT(s, r_link)) ; This code was added in revision 1.53 when support for intelligent merging was added. When r_end is equal to UINT_MAX, adding one will cause it to overflow, creating quite a mess in the entries ordering. I'm not sure the fix I did is completely correct as I didn't had time to check if the +1 is needed at all in this case. At least it fixed the problem for me. Regards, Steph