From: Eric Dumazet <eric.dumazet@gmail.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
David Miller <davem@davemloft.net>, Ingo Molnar <mingo@elte.hu>,
Francois Romieu <romieu@fr.zoreil.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] r8169: Fix rtl8169_rx_interrupt()
Date: Tue, 16 Mar 2010 16:05:33 +0100 [thread overview]
Message-ID: <1268751933.3094.45.camel@edumazet-laptop> (raw)
In-Reply-To: <20100316145914.GB3332@swordfish.minsk.epam.com>
Le mardi 16 mars 2010 à 17:00 +0200, Sergey Senozhatsky a écrit :
> Nope!
> Here it is:
>
>
> [17250.998293] ------------[ cut here ]------------
> [17250.998305] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xc1/0x125()
> [17250.998308] Hardware name: F3JC
> [17250.998312] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> [17250.998315] Modules linked in: pktgen ppp_async crc_ccitt ipv6 ppp_generic slhc snd_hwdep snd_hda_codec_si3054 snd_hda_codec_realtek sdhci_pci sdhci asus_laptop sparse_keymap
> mmc_core led_class snd_hda_intel snd_hda_codec snd_pcm snd_timer snd_page_alloc rng_core sg evdev i2c_i801 snd soundcore psmouse r8169 serio_raw mii uhci_hcd ehci_hcd sr_mod
> usbcore cdrom sd_mod ata_piix
> [17250.998371] Pid: 3985, comm: kpktgend_0 Tainted: G W 2.6.34-rc1-dbg-git6-r8169 #46
> [17250.998375] Call Trace:
> [17250.998383] [<c102e353>] warn_slowpath_common+0x65/0x7c
> [17250.998388] [<c126b654>] ? dev_watchdog+0xc1/0x125
> [17250.998393] [<c102e39e>] warn_slowpath_fmt+0x24/0x27
> [17250.998398] [<c126b654>] dev_watchdog+0xc1/0x125
> [17250.998405] [<c1036bbb>] ? run_timer_softirq+0x120/0x1eb
> [17250.998411] [<c1036c11>] run_timer_softirq+0x176/0x1eb
> [17250.998416] [<c1036bbb>] ? run_timer_softirq+0x120/0x1eb
> [17250.998421] [<c126b593>] ? dev_watchdog+0x0/0x125
> [17250.998426] [<c1032df9>] __do_softirq+0x8d/0x117
> [17250.998431] [<c1032eae>] do_softirq+0x2b/0x43
> [17250.998436] [<c1032fd3>] irq_exit+0x38/0x75
> [17250.998442] [<c1014e75>] smp_apic_timer_interrupt+0x66/0x74
> [17250.998448] [<c12c812a>] apic_timer_interrupt+0x36/0x3c
> [17250.998457] [<c1185d18>] ? do_raw_spin_trylock+0x28/0x37
> [17250.998464] [<c12c7101>] _raw_spin_lock+0x2f/0x58
> [17250.998472] [<f80855ca>] ? spin_lock+0x8/0xa [pktgen]
> [17250.998478] [<f80855ca>] spin_lock+0x8/0xa [pktgen]
> [17250.998484] [<f80873b6>] pktgen_thread_worker+0x9b/0x631 [pktgen]
> [17250.998491] [<c103f9f1>] ? autoremove_wake_function+0x0/0x2f
> [17250.998497] [<c103f9f1>] ? autoremove_wake_function+0x0/0x2f
> [17250.998503] [<f808731b>] ? pktgen_thread_worker+0x0/0x631 [pktgen]
> [17250.998508] [<c103f6ce>] kthread+0x6a/0x6f
> [17250.998514] [<c103f664>] ? kthread+0x0/0x6f
> [17250.998520] [<c1002e42>] kernel_thread_helper+0x6/0x1a
> [17250.998523] ---[ end trace a22d306b065d4a68 ]---
> [17251.011663] r8169 0000:02:00.0: eth0: link up
>
> [17419.011748] NOHZ: local_softirq_pending 08
>
>
But this stack trace is on pktgen side (the sender), and my patch was
about the receiver ?
I wonder if you dont hit another problem :)
next prev parent reply other threads:[~2010-03-16 15:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100307192305.GA598@elte.hu>
2010-03-08 12:51 ` inconsistent lock state Oleg Nesterov
2010-03-15 21:01 ` Eric Dumazet
2010-03-15 21:09 ` David Miller
2010-03-16 0:33 ` [PATCH] r8169: Fix rtl8169_rx_interrupt() Eric Dumazet
2010-03-16 6:50 ` Sergey Senozhatsky
2010-03-16 7:12 ` Eric Dumazet
2010-03-16 14:50 ` Sergey Senozhatsky
2010-03-16 15:00 ` Sergey Senozhatsky
2010-03-16 15:05 ` Eric Dumazet [this message]
2010-03-16 15:10 ` Sergey Senozhatsky
2010-03-16 15:20 ` Eric Dumazet
2010-03-16 18:26 ` Sergey Senozhatsky
2010-03-16 18:48 ` Eric Dumazet
2010-03-16 19:02 ` Sergey Senozhatsky
2010-03-17 7:25 ` Sergey Senozhatsky
2010-03-17 7:37 ` Eric Dumazet
2010-03-17 7:58 ` Sergey Senozhatsky
2010-03-17 10:58 ` Sergey Senozhatsky
2010-03-17 13:54 ` Eric Dumazet
2010-03-18 12:28 ` Sergey Senozhatsky
2010-03-17 23:55 ` Francois Romieu
2010-03-18 12:32 ` Sergey Senozhatsky
2010-03-18 13:31 ` Sergey Senozhatsky
2010-03-25 11:30 ` Sergey Senozhatsky
2010-03-25 13:19 ` Eric Dumazet
2010-03-25 13:48 ` Sergey Senozhatsky
2010-03-26 20:29 ` François Romieu
2010-03-31 12:08 ` Eric Dumazet
2010-04-02 1:43 ` David Miller
2010-04-02 13:51 ` Eric Dumazet
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=1268751933.3094.45.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=romieu@fr.zoreil.com \
--cc=sergey.senozhatsky@gmail.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