From owner-freebsd-current@freebsd.org Fri Mar 25 23:42:19 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 588DBADD975 for ; Fri, 25 Mar 2016 23:42:19 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward15m.cmail.yandex.net (forward15m.cmail.yandex.net [IPv6:2a02:6b8:b030::9c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 169811C9E; Fri, 25 Mar 2016 23:42:18 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [IPv6:2a02:6b8:0:2519::121]) by forward15m.cmail.yandex.net (Yandex) with ESMTP id 8EDFF21928; Sat, 26 Mar 2016 02:42:15 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id 2E88D67403D9; Sat, 26 Mar 2016 02:42:15 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id nbXmVQ9VEX-gESm4DbE; Sat, 26 Mar 2016 02:42:14 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1458949334; bh=zFbFXBpCLdkxbXQRkhIBgIYAFMuiydyzSWwFFLtkw0g=; h=Subject:To:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=pj1xRm8ZQH7urrtlA8lcIddgYVQqjKAWples2Rd1FvJ7nmcaf43vQQFtm/Tgj5X9n 9QuyLvLgshixJeDa6B2R1GDoAYAPuCRnpA3mB3wvRD9MacpI+0M0loDiKIPSrViSyp B0jSwZr3+4MKW8NmcsMYT1C7gl1XaUa4qilG3ypk= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-ForeignMX: US X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: SD card adapter doesn't working anymore To: Ian Lepore , FreeBSD Current References: <56F5A0A9.8030207@FreeBSD.org> <1458947510.1091.91.camel@freebsd.org> From: Ruslan Makhmatkhanov Message-ID: <56F5CCBA.3020009@yandex.ru> Date: Sat, 26 Mar 2016 02:41:46 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <1458947510.1091.91.camel@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 26 Mar 2016 05:23:43 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Fri, 25 Mar 2016 23:42:19 -0000 Ian Lepore wrote on 03/26/16 02:11 AM: > On Fri, 2016-03-25 at 23:33 +0300, Ruslan Makhmatkhanov wrote: >> Hello, >> >> I have this in pciconf output: >> >> ===================================================================== >> = >> none1@pci0:36:0:0: class=0x088000 card=0x167e103c >> chip=0x2392197b >> rev=0x30 hdr=0x00 >> vendor = 'JMicron Technology Corp.' >> device = 'SD/MMC Host Controller' >> class = base peripheral >> >> none2@pci0:36:0:3: class=0x088000 card=0x167e103c >> chip=0x2393197b >> rev=0x30 hdr=0x00 >> vendor = 'JMicron Technology Corp.' >> device = 'MS Host Controller' >> class = base peripheral >> ===================================================================== >> = >> >> And my SD-card controller is not working anymore (it worked on >> -current >> on the same laptop year or two ago). Do I need to load some kld to >> make >> it working, or support for this controllers was dropped altogether >> for >> some reason? I have mostly vanilla GENERIC at r296772, but it >> actually >> stopped to work much earlier. >> >> Thanks. >> > > Do you have a pciconf entry for class=080501 chip=0x2391197b, device > would probably be "SD Host Controller", and if so, is it none@pci or > sdhci_pci@pci ? If sdhci_pci attached, there would be dmesg output for > it, and I'm curious whether any irq-related error showed up when it > attached. > > The only change I can find that might have some effect is a switch to > MSI-based interrupts some time ago. That was MFC'd to 10-stable in > r271051, and that's very close to range cited in that PR. > > It might be worth trying to set hw.sdhci.enable_msi=0 in loader.conf > and see if it makes a difference. > > -- Ian Sorry, but nothing has changed in pciconf/dmesg with this option at boot. -- Regards, Ruslan T.O.S. Of Reality