From: Eric Dumazet <eric.dumazet@gmail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"jcliburn@gmail.com" <jcliburn@gmail.com>,
"chris.snook@gmail.com" <chris.snook@gmail.com>,
netdev <netdev@vger.kernel.org>, Josh Boyer <jwboyer@gmail.com>
Subject: Re: NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out
Date: Thu, 16 Feb 2012 07:18:02 +0100 [thread overview]
Message-ID: <1329373082.5646.9.camel@edumazet-laptop> (raw)
In-Reply-To: <C6B7BB6C-D1B8-4454-A2B2-558FCA5B0BBD@m3y3r.de>
Le jeudi 16 février 2012 à 07:13 +0100, Thomas Meyer a écrit :
> Hello Eric,
>
> >
> > Thomas, have you had the chance to test this patch ?
>
> Yes, I'm running 3.2.6 with your patch applied for 3 days now. I didn't see above warning yet, but the warning was rather seldom, so I'll keep an eye on it in the next weeks.
>
> Thanks for the patch!
>
Thanks for testing !
Do have any idea of what could set skb mark to 1 on some packets on your
setup ?
Some firewall rules or tc rules ?
next prev parent reply other threads:[~2012-02-16 6:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329063403.1449.14.camel@localhost.localdomain>
[not found] ` <CA+5PVA52+0vOMF6+tvMPkgzhdTKJRQnrjD4FfVmBZs0TMDJ5cg@mail.gmail.com>
2012-02-14 7:36 ` NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out Eric Dumazet
2012-02-16 4:34 ` Eric Dumazet
2012-02-16 6:13 ` Thomas Meyer
2012-02-16 6:18 ` Eric Dumazet [this message]
2012-02-16 6:23 ` Thomas Meyer
2012-02-16 6:43 ` [PATCH] atl1c: dont use highprio tx queue Eric Dumazet
2012-02-16 12:36 ` Josh Boyer
2012-02-16 13:12 ` Eric Dumazet
2012-02-19 23:59 ` David Miller
2012-02-16 7:09 ` NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out Huang, Xiong
2012-02-21 17:56 ` Thomas Meyer
2012-02-21 18:14 ` Eric Dumazet
2012-02-24 19:20 ` Eric Dumazet
2012-02-25 9:52 ` Thomas Meyer
2012-06-06 0:38 ` Jonathan Nieder
2012-06-07 12:37 ` Thomas Meyer
2012-06-07 12:52 ` Eric Dumazet
2012-06-07 21:30 ` Huang, Xiong
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=1329373082.5646.9.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=thomas@m3y3r.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