From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: e1000-devel@lists.sourceforge.net
Cc: netdev@vger.kernel.org
Subject: Re: e1000e: 1 second spins in e1000_acquire_swflag_ich8lan?
Date: Sun, 26 May 2013 19:48:52 -0500 [thread overview]
Message-ID: <20130527004851.GA3065@lintop> (raw)
In-Reply-To: <20130526164634.GA7241@lintop.rgmadvisors.com>
On Sun, May 26, 2013 at 11:46:34AM -0500, Shawn Bohrer wrote:
> I guess I have two questions:
>
> 1) Do these need to be mdelays instead of msleeps? It looks like in
> my case this is called from process context, but I didn't audit all of
> the callers of this function and maybe it can happen from interrupt
> context too?
>
> 2) Any idea why I'm hitting this in the first place?
Well, as is probably expected doing a cold boot of the system fixed
the issue (a warm reboot did not), so I'm guessing the hardware was
simply in a bad state. It seems a bit excessive to me that this code
can spin in the kernel for up to a second, and it appears on my system
it was doing this every two seconds.
--
Shawn
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
prev parent reply other threads:[~2013-05-27 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 16:46 e1000e: 1 second spins in e1000_acquire_swflag_ich8lan? Shawn Bohrer
2013-05-27 0:48 ` Shawn Bohrer [this message]
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=20130527004851.GA3065@lintop \
--to=shawn.bohrer@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.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).