netdev - Re: [BUG] bisected: PandaBoard smsc95xx ethernet driver error from USB timeout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Mar 2013 13:32:31 -0700
From:	Frank Rowand <frank.rowand@...sony.com>
To:	unlisted-recipients:; (no To-header on input)
CC:	Ming Lei <tom.leiming@...il.com>,
	"stern@...land.harvard.edu" <stern@...land.harvard.edu>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"balbi@...com" <balbi@...com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"steve.glendinning@...c.com" <steve.glendinning@...c.com>
Subject: Re: [BUG] bisected: PandaBoard smsc95xx ethernet driver error from
 USB timeout

On 03/21/13 13:25, Frank Rowand wrote:
> On 03/21/13 02:00, Ming Lei wrote:

< snip >

> ----------
> There are some timeout messages that I am not positive are symptoms of
> the problem.  With these messages, the smsc95xx driver initialization is
> successful, so the ethernet device is available.  For the first bisect
> attempt, I did not treat these messages as errors.  For the second bisect
> attempt I treated these messages as errors.  A typical example of the
> timeout message is:
> 
>   [    9.537811] hub 1-1:1.0: state 7 ports 5 chg 0000 evt 0002
>   [   17.056701] usb 1-1.1: swapper/0 timed out on ep0out len=0/4
>   [   17.062652] smsc95xx 1-1.1:1.0: eth0: Failed to write register index 0x00000108
>   [   17.070343] smsc95xx 1-1.1:1.0: eth0: Failed to write ADDRL: -110
>   [   17.076751] IP-Config: Failed to open eth0

Oops, pasted the wrong example.  This is an example of a timeout, but the
driver still works, and the system boots:

  [    6.072357] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-1.1, smsc95xx USB 2.0 Ethernet, fa:50:73:02:79:67
  [    6.084655] hub 1-1:1.0: state 7 ports 5 chg 0000 evt 0002
  [   11.220672] usb 1-1.1: swapper/0 timed out on ep0out len=4/4
  [   18.183441] usb 1-1.1: link qh8-0001/dc8d6640 start 2 [1/0 us]
  [   19.822296] IP-Config: Complete:

> 
>   The mention of swapper is not relevent, it just happens to be the
>   current process when the time out occurs.
> 
> I have only seen these timeout messages in the boot log, so they may not
> be a very visible symptom.  They also _might_ be unrelated to the problem,
> but my gut feel is that they are related.

< snip >

-Frank

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html