From: Eric Dumazet <eric.dumazet@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: warnings in 2.6.37-rc1+
Date: Wed, 10 Nov 2010 06:59:38 +0100 [thread overview]
Message-ID: <1289368778.2700.23.camel@edumazet-laptop> (raw)
In-Reply-To: <20101110054948.GA16612@gamma.logic.tuwien.ac.at>
Le mercredi 10 novembre 2010 à 14:49 +0900, Norbert Preining a écrit :
> Hi all
>
> (please keep in Cc, thanks)
>
> [ 1592.320059] ------------[ cut here ]------------
> [ 1592.320077] WARNING: at net/ipv4/devinet.c:137 in_dev_finish_destroy+0x3d/0x6e()
> [ 1592.320083] Hardware name: VGN-Z11VN_B
> [ 1592.320088] Modules linked in: vboxnetadp vboxnetflt sco bnep rfcomm l2cap crc16 binfmt_misc dm_crypt dm_mod isofs btrfs zlib_deflate crc32c libcrc32c vfat fat hso fuse vboxdrv loop uinput snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi arc4 snd_rawmidi snd_seq_midi_event snd_seq iwlagn iwlcore mac80211 snd_timer btusb firewire_ohci firewire_core bluetooth snd_seq_device tpm_infineon sony_laptop snd soundcore crc_itu_t cfg80211 rfkill joydev snd_page_alloc
> [ 1592.320207] Pid: 0, comm: kworker/0:0 Tainted: P W 2.6.37-rc1+ #3
> [ 1592.320213] Call Trace:
> [ 1592.320218] <IRQ> [<ffffffff81035075>] warn_slowpath_common+0x80/0x98
> [ 1592.320236] [<ffffffff810350a2>] warn_slowpath_null+0x15/0x17
> [ 1592.320245] [<ffffffff81352ede>] in_dev_finish_destroy+0x3d/0x6e
> [ 1592.320257] [<ffffffff8132b5f7>] ipv4_dst_destroy+0x53/0x58
> [ 1592.320266] [<ffffffff81314c26>] dst_destroy+0x78/0xd6
> [ 1592.320275] [<ffffffff8132b340>] dst_free+0x1a/0x29
> [ 1592.320283] [<ffffffff8132b358>] dst_rcu_free+0x9/0xb
> [ 1592.320292] [<ffffffff8107b5fd>] __rcu_process_callbacks+0x173/0x265
> [ 1592.320301] [<ffffffff8107b72e>] rcu_process_callbacks+0x3f/0x60
> [ 1592.320310] [<ffffffff81039e1c>] __do_softirq+0x8f/0x140
> [ 1592.320322] [<ffffffff810563fa>] ? tick_program_event+0x21/0x23
> [ 1592.320331] [<ffffffff8100304c>] call_softirq+0x1c/0x28
> [ 1592.320339] [<ffffffff81004c23>] do_softirq+0x33/0x68
> [ 1592.320347] [<ffffffff8103a036>] irq_exit+0x36/0x8b
> [ 1592.320358] [<ffffffff81019699>] smp_apic_timer_interrupt+0x88/0x96
> [ 1592.320366] [<ffffffff81002b13>] apic_timer_interrupt+0x13/0x20
> [ 1592.320371] <EOI> [<ffffffff811ae0ef>] ? acpi_idle_enter_simple+0xc8/0xfa
> [ 1592.320389] [<ffffffff811ae0ea>] ? acpi_idle_enter_simple+0xc3/0xfa
> [ 1592.320401] [<ffffffff812e053c>] cpuidle_idle_call+0x9e/0xd6
> [ 1592.320408] [<ffffffff81001484>] cpu_idle+0x56/0x9c
> [ 1592.320418] [<ffffffff813816c8>] start_secondary+0x199/0x19d
> [ 1592.320426] ---[ end trace 5f7d0c35de1972f1 ]---
>
> followed by a strange message:
> [ 1592.320431] Freeing alive in_device ffff88013e49b200
>
> happened several times, starting after a wake up from suspend to ram.
>
> Best wishes
Should be solved by a patch David will send to Linus in next round.
http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=18943d292facbc70e6a36fc62399ae833f64671b
Thanks
parent reply other threads:[~2010-11-10 5:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20101110054948.GA16612@gamma.logic.tuwien.ac.at>]
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=1289368778.2700.23.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=preining@logic.at \
/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