From: Ben Hutchings <bhutchings@solarflare.com>
To: tim.gardner@canonical.com
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Fix atl1c event race (was Re: 2.6.38 dev_watchdog WARNING)
Date: Wed, 20 Apr 2011 19:13:27 +0100 [thread overview]
Message-ID: <1303323207.2823.22.camel@bwh-desktop> (raw)
In-Reply-To: <4DAF1F1D.1020108@canonical.com>
On Wed, 2011-04-20 at 11:59 -0600, Tim Gardner wrote:
[...]
> I've been focusing on atl1c while trying to understand why link status
> flapping could cause these watchdog timeouts. I've a couple of log files
> with link state change information:
>
> http://bugs.launchpad.net/bugs/766273
> https://launchpadlibrarian.net/69926580/BootDmesg.txt
> https://launchpadlibrarian.net/69926583/CurrentDmesg.txt
>
> One thing of note is that there are 2 link UP messages in a row,
> something that should only be able to happen if there has been an
> intervening device reset (which is not evident in the logs). I've
> noticed that the work event scheduling is kind of racy, so perhaps this
> will help. See attached.
I'm not going to spend any significant time looking at atl1c, as that's
really not my job! The atlx maintainers may be covering atl1c as well,
so try cc'ing them.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-04-20 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 17:40 2.6.38 dev_watchdog WARNING Tim Gardner
2011-04-19 18:20 ` Ben Greear
2011-04-19 18:49 ` Ben Hutchings
2011-04-20 17:59 ` Fix atl1c event race (was Re: 2.6.38 dev_watchdog WARNING) Tim Gardner
2011-04-20 18:13 ` Ben Hutchings [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=1303323207.2823.22.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=tim.gardner@canonical.com \
/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