From: Hector Palacios <hector.palacios@digi.com>
To: linux-rt-users@vger.kernel.org
Cc: lclaudio@uudg.org, rostedt@goodmis.org, efault@gmx.de
Subject: infinite spin in RT when booting with DHCP on
Date: Wed, 01 Feb 2012 13:28:16 +0100 [thread overview]
Message-ID: <4F292FE0.7090302@digi.com> (raw)
Hello,
I'm working on a 2.6.31.14 kernel on ARM where I applied the RT PREEMPT patch
2.6.31.12-rt21.
When booting my platform with DHCP on, the DHCP request is sent by the network driver
before the PHY has even started the autonegotiation.
Since the PHY is not ready, the TX interrupt returns with NETDEV_TX_BUSY but the
softirq [sirq-net-tx] seems to have entered an infinite spin, as my system is
practically hung and 'top' reveals [sirq-net-tx/0] is consuming 95% of CPU. This is
preventing the PHY autonegotiation (which is scheduled as a delayed work) to start, so
the PHY is never ready and the packet never reaches the network.
I was wondering if this situation resembles what the patch by Ingo Molnar "tasklet/rt:
Prevent tasklets from going into infinite spin in RT" describes.
This patch is already in 2.6.31.12-rt21 patch which I'm using so either it is a
different problem or a corner case of the same issue.
Could anyone tell whether it is the same or a different problem?
Thank you
--
Héctor Palacios
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-02-01 12:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 12:28 Hector Palacios [this message]
2012-02-02 12:38 ` infinite spin in RT when booting with DHCP on Tim Sander
2012-02-02 12:57 ` Hector Palacios
2012-02-02 14:25 ` Tim Sander
2012-02-02 15:32 ` Tim Sander
2012-02-02 15:53 ` Hector Palacios
2012-02-02 18:10 ` Steven Rostedt
2012-02-03 10:09 ` Hector Palacios
2012-02-03 10:54 ` John Ogness
2012-02-03 14:26 ` Steven Rostedt
2012-02-02 17:33 ` Steven Rostedt
2012-02-02 18:21 ` Steven Rostedt
2012-02-02 20:13 ` Uwe Kleine-König
2012-02-02 21:34 ` Steven Rostedt
2012-02-02 23:44 ` Tim Sander
2012-02-03 9:45 ` Tim Sander
2012-02-06 14:49 ` Tim Sander
2012-02-03 10:23 ` Hector Palacios
2012-02-03 10:35 ` Uwe Kleine-König
2012-02-03 16:14 ` Hector Palacios
2012-02-03 16:43 ` Steven Rostedt
2012-02-03 17:25 ` Hector Palacios
2012-02-03 17:39 ` Steven Rostedt
2012-02-03 19:25 ` Uwe Kleine-König
2012-02-03 20:04 ` Steven Rostedt
2012-02-06 8:51 ` Hector Palacios
2012-02-06 13:27 ` Steven Rostedt
2012-02-08 20:41 ` Thomas Gleixner
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=4F292FE0.7090302@digi.com \
--to=hector.palacios@digi.com \
--cc=efault@gmx.de \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).