From: Wang Chen <wangchen@cn.fujitsu.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>,
David Miller <davem@davemloft.net>
Cc: Alessandro Guido <ag@alessandroguido.name>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] skge: resolve tx multiqueue bug
Date: Wed, 23 Jul 2008 23:21:14 +0800 [thread overview]
Message-ID: <48874C6A.1020604@cn.fujitsu.com> (raw)
In-Reply-To: <20080723140347.GA2245@gentoox2.trippelsdorf.de>
Markus Trippelsdorf said the following on 2008-7-23 22:03:
> On Wed, Jul 23, 2008 at 12:18:27PM +0200, Markus Trippelsdorf wrote:
>> On Wed, Jul 23, 2008 at 04:50:13PM +0800, Wang Chen wrote:
>>> Markus Trippelsdorf said the following on 2008-7-23 13:40:
>>>> On Tue, Jul 22, 2008 at 11:54:26AM +0200, Alessandro Guido wrote:
>>>>> Got a WARNING this morning (2.6.26-05752-g93ded9b) and I think it's related.
>>>> Same thing here (latest git):
>>>>
>>>> skge eth1: enabling interface
>>>> skge eth1: disabling interface
>>>> ------------[ cut here ]------------
>>>> WARNING: at net/core/dev.c:1344 __netif_schedule+0x24/0x6d()
>>>> Pid: 1904, comm: ip Not tainted 2.6.26-06077-gc010b2f #33
>>>> [<ffffffff8020b3eb>] system_call_after_swapgs+0x7b/0x80
>> ...
>>>> ---[ end trace 92936ef183e09876 ]---
>>>> skge eth1: enabling interface
>>>> skge eth1: Link is up at 100 Mbps, full duplex, flow control both
>>>>
>>> Markus, please try this.
>>>
>>> - Add netif_start_queue() in ->open()
>>> - netif_carrier_*() is enough, remove netif_*_queue()
>> Unfortunately, your patch does not fix this. I still get the same warning.
>>
>
> This patch works for me:
Your patch works for me too. So I think it's better than mine. :)
Tested-by: Wang Chen <wangchen@cn.fujitsu.com>
Dave, since Markus and me tested this patch, would you please apply it?
next prev parent reply other threads:[~2008-07-23 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4b984a30807210914nd4d0db5yb7b93ca5143ff0d5@mail.gmail.com>
[not found] ` <d4b984a30807210914nd4d0db5yb7b93ca5143ff0d5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-21 16:20 ` [BUG] kernel BUG at net/core/dev.c:1328! David Miller
2008-07-22 9:54 ` Alessandro Guido
[not found] ` <d4b984a30807220254t1aaf6ac4q874329966511b0c5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-22 20:18 ` Alessandro Suardi
2008-07-22 22:56 ` David Miller
[not found] ` <20080722.155611.176476925.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-07-23 7:57 ` Alessandro Guido
[not found] ` <d4b984a30807230057t319eca71g32262305bdb07582-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-23 13:16 ` Alessandro Suardi
2008-07-23 5:40 ` WARNING: " Markus Trippelsdorf
2008-07-23 8:50 ` [PATCH] skge: resolve tx multiqueue bug Wang Chen
2008-07-23 10:18 ` Markus Trippelsdorf
2008-07-23 14:03 ` Markus Trippelsdorf
2008-07-23 15:21 ` Wang Chen [this message]
[not found] ` <48874C6A.1020604-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-07-23 22:30 ` David Miller
[not found] ` <20080723.153000.172383135.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-07-24 1:01 ` Wang Chen
2008-07-24 6:18 ` Markus Trippelsdorf
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=48874C6A.1020604@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=ag@alessandroguido.name \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--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).