From: Frank Blaschka <blaschka@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: GRO with non napi driver: BUG in __napi_complete
Date: Tue, 17 Mar 2009 09:35:21 +0100 [thread overview]
Message-ID: <49BF60C9.1080100@linux.vnet.ibm.com> (raw)
Hi,
I try to activate GRO on a non napi driver (2.6.29-rc8). Running an iperf test
causes a bug in __napi_complete.
kernel BUG at net/core/dev.c:2625!
illegal operation: 0001 <DD>#1<A8> PREEMPT SMP
Modules linked in:
CPU: 1 Not tainted 2.6.29-rc8-00124-g5bee17f #8
Process swapper (pid: 0, task: 000000002ff7ccc0, ksp: 000000002ff97d48)
Krnl PSW : 0404d00180000000 00000000002d1f4e (__napi_complete+0x82/0x88)
R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 EA:3
...
<DD> 261.377396<A8> Call Trace:
<DD> 261.377400<A8> (<DD><00000000002cb752><A8> process_backlog+0xba/0x104)
<DD> 261.377410<A8> <DD><00000000002cb5ba><A8> net_rx_action+0x102/0x1e0
<DD> 261.377418<A8> <DD><000000000004921e><A8> __do_softirq+0x92/0x168
<DD> 261.377428<A8> <DD><0000000000020936><A8> do_softirq+0x96/0xb0
<DD> 261.377436<A8> <DD><00000000000493c0><A8> irq_exit+0x70/0x80
<DD> 261.377444<A8> <DD><000000000025789c><A8> do_IRQ+0x174/0x194
<DD> 261.377455<A8> <DD><00000000000258da><A8> io_return+0x0/0x8
<DD> 261.377464<A8> <DD><00000000000246fe><A8> vtime_stop_cpu+0xb2/0xc0
<DD> 261.377473<A8> (<DD><00000007005b1007><A8> 0x7005b1007)
What is the intention process_backlog calls __napi_complete() instead of
napi_complete(), this looks suspicious to me. Can anybody help?
Thanks,
Frank
next reply other threads:[~2009-03-17 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 8:35 Frank Blaschka [this message]
2009-03-17 10:22 ` GRO with non napi driver: BUG in __napi_complete Herbert Xu
2009-03-17 20:11 ` David Miller
2009-03-27 19:05 ` Tom Herbert
2009-03-27 22:50 ` David Miller
2009-03-17 15:49 ` Jean-Pascal Billaud
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=49BF60C9.1080100@linux.vnet.ibm.com \
--to=blaschka@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).