Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422861Ab3CVSYq (ORCPT ); Fri, 22 Mar 2013 14:24:46 -0400 Received: from co9ehsobe004.messaging.microsoft.com ([207.46.163.27]:45916 "EHLO co9outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422649Ab3CVSYo (ORCPT ); Fri, 22 Mar 2013 14:24:44 -0400 X-Forefront-Antispam-Report: CIP:160.33.194.230;KIP:(null);UIP:(null);IPV:NLI;H:usculsndmail03v.am.sony.com;RD:mail.sonyusa.com;EFVD:NLI X-SpamScore: -5 X-BigFish: VPS-5(zzbb2dI98dI936eI1432I14ffIzz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz17326ah8275dh8275bhz2fh2a8h668h839h947hd25hf0ah10d2h1288h12a5h12a9h12bdh137ah13b6h1441h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19c3h1b0ah1155h) Message-ID: <514CA1A5.1090606@am.sony.com> Date: Fri, 22 Mar 2013 11:23:33 -0700 From: Frank Rowand Reply-To: User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc14 Thunderbird/3.1.10 MIME-Version: 1.0 To: Mats Liljegren CC: Alan Stern , "gregkh@linuxfoundation.org" , "linux-usb@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-omap@vger.kernel.org" , "balbi@ti.com" , "netdev@vger.kernel.org" Subject: Re: [BUG] bisected: PandaBoard smsc95xx ethernet driver error from USB timeout References: <514BC5C3.9080808@am.sony.com> <20130322100329.GH29378@enea.se> In-Reply-To: <20130322100329.GH29378@enea.se> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginatorOrg: am.sony.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3592 Lines: 87 On 03/22/13 03:03, Mats Liljegren wrote: > Frank Rowand wrote: >> On 03/21/13 07:41, Alan Stern wrote: >>> On Wed, 20 Mar 2013, Frank Rowand wrote: >>> >>>> Hi All, >>>> >>>> Not quite sure quite where the problem is (USB, OMAP, smsc95xx driver, other???), >>>> so casting the nets wide... >>>> >>>> The PandaBoard frequently fails to boot with an eth0 error when mounting >>>> the root file system via NFS (ethernet driver fails due to a USB timeout; >>>> no ethernet means NFS won't work). A typical set of error messages is: >>>> >>>> [ 3.264373] smsc95xx 1-1.1:1.0: usb_probe_interface >>>> [ 3.269500] smsc95xx 1-1.1:1.0: usb_probe_interface - got id >>>> [ 3.275543] smsc95xx v1.0.4 >>>> [ 8.078674] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-1.1, smsc95xx USB 2.0 Ethernet, 82:b9:1d:fa:67:0d >>>> [ 8.091003] hub 1-1:1.0: state 7 ports 5 chg 0000 evt 0002 >>>> [ 13.509918] usb 1-1.1: swapper/0 timed out on ep0out len=0/4 >>>> [ 13.515869] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000108 >>>> [ 13.523559] smsc95xx 1-1.1:1.0: eth0: Failed to write ADDRL: -110 >>>> [ 13.529998] IP-Config: Failed to open eth0 >>>> >>>> I have bisected this to: >>>> >>>> commit 18aafe64d75d0e27dae206cacf4171e4e485d285 >>>> Author: Alan Stern >>>> Date: Wed Jul 11 11:23:04 2012 -0400 >>>> >>>> USB: EHCI: use hrtimer for the I/O watchdog >>> >>> I don't understand how that commit could cause a timeout unless there >>> are at least two other bugs present in your system. >>> >>>> Note that to compile this version of the kernel, an additional fix must >>>> also be applied: >>>> >>>> commit ba5952e0711b14d8d4fe172671f8aa6091ace3ee >>>> Author: Ming Lei >>>> Date: Fri Jul 13 17:25:24 2012 +0800 >>>> >>>> USB: ehci-omap: fix compile failure(v1) >>>> >>>> The symptom can be worked around by retrying the USB access if a timeout >>>> occurs. This is clearly _not_ the fix, just a hack that I used to >>>> investigate the problem: >>>> >>>> http://article.gmane.org/gmane.linux.rt.user/9773 >>>> >>>> My kernel configuration is: >>>> >>>> arch/arm/configs/omap2plus_defconfig >>>> >>>> plus to get the ethernet driver I add: >>>> >>>> CONFIG_USB_EHCI_HCD >>>> CONFIG_USB_NET_SMSC95XX >>>> >>>> I found the problem on 3.6.11, but have not replicated it on 3.9-rcX >>>> yet because my config fails to build on 3.9-rc1 and 3.9-rc2. I'll try >>>> to work on that issue tomorrow. >>> >>> Let me know how it works out. >> >> My PandaBoard builds fail on 3.9-rcX due to ARM multiplatform issues. >> Either there is something I need to change about the way I build it, >> or it is broken (that is a side issue). My simple expedient was to >> hack around multiplatform, and just make it build (patch below if >> anyone else wants a _temporary_ hack). > > I have built 3.9-RC2 for PandaBoard ES and the only problem I have seen is > that you need to add "LOADADDR=0x80008000" when building uImage target. Yes, that is essentially what my hack patch does. The result of my patch is that arch/arm/boot/Makefile is invoked with MACHINE="arch/arm/mach-omap2" so that at the top of the makefile, the "include $(srctree)/$(MACHINE)/Makefile.boot" which pulls in the proper values for addresses. -Frank -- 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/