Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756535Ab3ICPcb (ORCPT ); Tue, 3 Sep 2013 11:32:31 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:63790 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756228Ab3ICPc0 (ORCPT ); Tue, 3 Sep 2013 11:32:26 -0400 MIME-Version: 1.0 X-Originating-IP: [121.6.72.52] In-Reply-To: <86vc2ib1yt.fsf@void.printf.net> References: <86vc2ib1yt.fsf@void.printf.net> Date: Tue, 3 Sep 2013 23:32:25 +0800 Message-ID: Subject: Re: BCM57765: timeout waiting for hardware interrupt From: Daniel J Blueman To: Chris Ball Cc: "linux-mmc@vger.kernel.org" , Linux Kernel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 8442 Lines: 164 On 3 September 2013 19:04, Chris Ball wrote: > On Tue, Sep 03 2013, Daniel J Blueman wrote: >> Please let me know if there's a better vector for reporting and >> looking into this issue, if you can. > > Do you know whether it's ever worked on this hardware? If so, could > you try bisecting to find the first bad commit? Yes; the card reader works when an ethernet cable is plugged into the first PCI function on the chip, the Broadcom NIC (see comment #3): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1067222 Google also use this in one of their Chromebook models: https://groups.google.com/a/chromium.org/forum/#!msg/chromium-os-reviews/nwFj3KVQy_Y/FOckx1trSkUJ > If not, I suspect it's going to be very difficult to debug/fix > remotely, and we need to wait for someone who has the hardware and > wants to create the fix. (Or get the hardware into the hands of > someone who's willing to take a look.) Got hardware and willing to take a look; just was wanting some tips on where to look with your experience of SDHCI/MMC. Doing some further debugging, the card reader's parent device (the NIC) is in D3 [1] while the card reader is in D0. I'll add the missing device IDs to the tg3 driver and force it to bring the NIC into D0 and see what happens. Daniel --- [1] $ sudo lspci -s 3:0 -vv 03:00.0 Ethernet controller: Broadcom Corporation Device 16a3 (rev 10) Subsystem: Broadcom Corporation Device 16b4 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- 03:00.1 SD Host controller: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader (rev 10) (prog-if 01) Subsystem: Broadcom Corporation Device 96bc Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [160 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb: Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Kernel driver in use: sdhci-pci -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/