From: Frank Rowand <frank.rowand@am.sony.com>
To: Thomas Gleixner <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: linux-3.6.11-rt30 smoke test on ARM
Date: Thu, 7 Mar 2013 19:55:47 -0800 [thread overview]
Message-ID: <51396143.5060108@am.sony.com> (raw)
linux-3.6.11-rt30 builds and boots on some ARM boards (PandaBoard, Realview) for:
- SMP, PREEMPT_RT_FULL
- SMP, PREEMPT_NONE
- UP, PREEMPT_RT_FULL
- UP, PREEMPT_NONE
The PandaBoard frequently fails to boot with an eth0 error. I have
only seen this for SMP, PREEMPT_NONE. This same error also occurs
in 3.6.7 without the RT_PREEMPT patches applied, so this does not
appear to be an RT_PREEMPT issue.
This error also occurred in the previous smoke test of linux-3.6.7-rt18
http://permalink.gmane.org/gmane.linux.rt.user/9202
The boot error starts with the USB time out on ep0out:
[ 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
The boot error can be avoided with a workaround that simply retries
the failed USB command. I will reply to this email with the patch.
-Frank
next reply other threads:[~2013-03-08 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 3:55 Frank Rowand [this message]
2013-03-08 4:03 ` linux-3.6.11-rt30 smoke test on ARM Frank Rowand
2013-03-11 17:34 ` Sebastian Andrzej Siewior
2013-03-13 0:44 ` Frank Rowand
2013-03-21 20:26 ` Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51396143.5060108@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox