From: "Michael Büsch" <m@bues.ch>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Pavel Emelyanov <xemul@parallels.com>,
Eric Dumazet <edumazet@google.com>,
linux-netdev <netdev@vger.kernel.org>,
"David S.Miller" <davem@davemloft.net>,
Mel Gorman <mgorman@suse.de>
Subject: Re: atl1c issues on 3.8.2
Date: Fri, 15 Mar 2013 20:44:57 +0100 [thread overview]
Message-ID: <20130315204457.21d46b89@milhouse> (raw)
In-Reply-To: <1363302362.29475.42.camel@edumazet-glaptop>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Fri, 15 Mar 2013 00:06:02 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> You could try various DEBUGing stuff, like CONFIG_DEBUG_PAGEALLOC and
> CONFIG_SLUB_DEBUG_ON
This bug is so weird, so I did some double-checking.
Just to minimize the mistakes on my side.
I compiled a kernel without the revert of the original commit
and without the skb fix you suggested.
It turns out that I am only able to reproduce the issue, if the ath9k interface is
up while testing the atl1c ethernet.
And I also double-checked that reverting the original commit fixes the issue.
No stalls with up or down ath9k then.
So that confirms my previous results.
I tried to enable pagealloc debug and slub debug on a kernel with the suggested skb
fix, but without the revert of the commit. Nothing special appeared
in the logs. I'm currently building a kernel with almost all debugging options
turned on. I will test that tomorrow.
Thanks for your help.
--
Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-15 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:17 atl1c issues on 3.8.2 Michael Büsch
2013-03-12 15:45 ` Eric Dumazet
[not found] ` <20130312180942.4198e88e@milhouse>
2013-03-13 5:57 ` Eric Dumazet
2013-03-14 14:31 ` Eric Dumazet
2013-03-14 22:17 ` Michael Büsch
2013-03-14 23:06 ` Eric Dumazet
2013-03-15 19:44 ` Michael Büsch [this message]
2013-03-22 11:28 ` Michael Büsch
2013-05-27 16:43 ` Michael Büsch
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=20130315204457.21d46b89@milhouse \
--to=m@bues.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=mgorman@suse.de \
--cc=netdev@vger.kernel.org \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).