From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "Alessandro Guido" <ag@alessandroguido.name>
Cc: "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [BUG] kernel BUG at net/core/dev.c:1328!
Date: Tue, 22 Jul 2008 22:18:45 +0200 [thread overview]
Message-ID: <5a4c581d0807221318l12989994u121f07dad47f5a0a@mail.gmail.com> (raw)
In-Reply-To: <d4b984a30807220254t1aaf6ac4q874329966511b0c5@mail.gmail.com>
On Tue, Jul 22, 2008 at 11:54 AM, Alessandro Guido
<ag@alessandroguido.name> wrote:
> Got a WARNING this morning (2.6.26-05752-g93ded9b) and I think it's related.
>
>
> WARNING: at net/core/dev.c:1330 __netif_schedule+0x53/0x60()
> Modules linked in:
> Pid: 5, comm: events/0 Not tainted 2.6.26-05752-g93ded9b #1
> [<c011bc64>] warn_on_slowpath+0x54/0xa0
> [<c0135483>] ? getnstimeofday+0x53/0x100
> [<c0132d1c>] ? ktime_get_ts+0x4c/0x50
> [<c012ba67>] ? insert_work+0x57/0x70
> [<c012c129>] ? queue_work+0x39/0x60
> [<c012c1e5>] ? queue_delayed_work+0x25/0x30
> [<c012c201>] ? schedule_delayed_work+0x11/0x20
> [<c030398a>] ? linkwatch_schedule_work+0x3a/0xb0
> [<c02f78d3>] __netif_schedule+0x53/0x60
> [<c0262a80>] ipw_bg_link_up+0x160/0x1f0
> [<c035ae4e>] ? schedule+0x1de/0x3f0
> [<c012bdef>] run_workqueue+0x6f/0x160
> [<c0262920>] ? ipw_bg_link_up+0x0/0x1f0
> [<c012c08f>] worker_thread+0x7f/0xe0
> [<c012f5d0>] ? autoremove_wake_function+0x0/0x50
> [<c012c010>] ? worker_thread+0x0/0xe0
> [<c012f15a>] kthread+0x3a/0x70
> [<c012f120>] ? kthread+0x0/0x70
> [<c0103d77>] kernel_thread_helper+0x7/0x10
> =======================
I also hit a very similar one on my Dell D610 with onboard
ipw2200 wireless (already kerneloops'd, BTW):
WARNING: at net/core/dev.c:1330 __netif_schedule+0x2a/0x63()
Modules linked in: fuse sunrpc iptable_filter ip_tables
ip6table_filter ip6_tables x_tables ipv6 cpufreq_ondemand ppdev pcmcia
dcdbas parport_pc parport snd_intel8x0 snd_intel8x0m snd_ac97_codec
snd_seq_dummy ac97_bus snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device snd_pcm_oss pcspkr snd_mixer_oss snd_pcm snd_timer snd
ipw2200 soundcore snd_page_alloc i2c_i801 ieee80211 ieee80211_crypt
yenta_socket rsrc_nonstatic pcmcia_core video output pata_acpi
ata_piix uhci_hcd ehci_hcd [last unloaded: microcode]
Pid: 5, comm: events/0 Not tainted 2.6.26-git9 #5
[<c0118cda>] warn_on_slowpath+0x46/0x80
[<c0113a91>] ? __enqueue_entity+0xe3/0xeb
[<c0113754>] ? __wake_up+0x31/0x3b
[<c0125ebb>] ? __queue_work+0x2d/0x32
[<c0125f05>] ? queue_work+0x2a/0x34
[<c01261ff>] ? queue_delayed_work+0x11/0x23
[<c0126227>] ? schedule_delayed_work+0x16/0x1b
[<c02ce1d5>] ? linkwatch_schedule_work+0x58/0x99
[<c02ce278>] ? linkwatch_fire_event+0x62/0x66
[<c02c567f>] __netif_schedule+0x2a/0x63
[<f8990009>] ipw_bg_link_up+0xae/0x173 [ipw2200]
[<c0125a0f>] run_workqueue+0x7d/0xf6
[<f898ff5b>] ? ipw_bg_link_up+0x0/0x173 [ipw2200]
[<c0125cec>] worker_thread+0xb7/0xc3
[<c0128862>] ? autoremove_wake_function+0x0/0x38
[<c0125c35>] ? worker_thread+0x0/0xc3
[<c01285d3>] kthread+0x3e/0x63
[<c0128595>] ? kthread+0x0/0x63
[<c0103003>] kernel_thread_helper+0x7/0x10
But it works - to the point that I'm connected to my wireless
router without apparent issues.
--alessandro
"Give me love / Or give me hate
Give me anything that's not just ok"
(Sophia, 'Weightless')
next prev parent reply other threads:[~2008-07-22 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 16:14 Alessandro Guido
2008-07-21 16:20 ` David Miller
2008-07-22 9:54 ` Alessandro Guido
2008-07-22 20:18 ` Alessandro Suardi [this message]
2008-07-22 22:56 ` David Miller
2008-07-23 7:57 ` Alessandro Guido
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
2008-07-23 22:30 ` David Miller
2008-07-24 1:01 ` Wang Chen
2008-07-24 6:18 ` Markus Trippelsdorf
2008-07-21 17:08 ` [BUG] kernel BUG at net/core/dev.c:1328! Alessandro Guido
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=5a4c581d0807221318l12989994u121f07dad47f5a0a@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=ag@alessandroguido.name \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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
all inboxes | Powered by JetHome®