From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>
Subject: [sched-devel/latest] WARNING: at mm/slub.c:2443
Date: Mon, 21 Apr 2008 23:10:41 +0200 [thread overview]
Message-ID: <200804212310.41729.elendil@planet.nl> (raw)
I got the following warning while running sched-devel/latest.
I was not doing any tracing at that point (for the glibc compilation issue).
I suspect it was while I was using a KDE application (amarok) as the
desktop froze for a few seconds at one point.
Cheers,
FJP
------------[ cut here ]------------
WARNING: at mm/slub.c:2443 kmem_cache_destroy+0x168/0x1a9()
Modules linked in: snd_rtctimer i915 drm tun ppdev lp ac battery nfs lockd
nfs_acl sunrpc bridge llc fuse lm85 hwmon_vid cpufreq_ondemand acpi_cpufreq
freq_table firewire_sbp2 ipv6 snd_hda_intel snd_pcm_oss snd_mixer_oss
snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi
snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse snd parport_pc
i2c_i801 button iTCO_wdt parport serio_raw i2c_core intel_agp joydev
soundcore evdev pcspkr snd_page_alloc ext3 jbd mbcache dm_mirror
dm_snapshot dm_mod ide_cd_mod ata_piix ata_generic sg sr_mod cdrom sd_mod
piix usbhid hid floppy ahci libata scsi_mod dock ide_pci_generic ide_core
firewire_ohci firewire_core crc_itu_t ehci_hcd uhci_hcd e1000e thermal
processor fan
Pid: 32428, comm: cat Not tainted 2.6.26-rc0-sched-devel.git-x86-latest.git
#3
Call Trace:
[<ffffffff80237c7b>] warn_on_slowpath+0x58/0x6b
[<ffffffff80273676>] ? get_pageblock_migratetype+0x1b/0x1d
[<ffffffff80274291>] ? free_hot_page+0xb/0xd
[<ffffffff802742ab>] ? __free_pages+0x18/0x21
[<ffffffff80292170>] ? __free_slab+0xdc/0xe9
[<ffffffff80293c5d>] kmem_cache_destroy+0x168/0x1a9
[<ffffffff803974d8>] mon_text_release+0x89/0xae
[<ffffffff80299254>] __fput+0xb9/0x161
[<ffffffff8029957b>] fput+0x14/0x16
[<ffffffff80296892>] filp_close+0x66/0x71
[<ffffffff80239eea>] put_files_struct+0x77/0xcb
[<ffffffff80239f72>] __exit_files+0x34/0x39
[<ffffffff8023b1ec>] do_exit+0x256/0x683
[<ffffffff8023b694>] do_group_exit+0x7b/0x96
[<ffffffff8024409f>] get_signal_to_deliver+0x2c4/0x2f1
[<ffffffff8020b9bb>] do_notify_resume+0xd0/0x8d5
[<ffffffff80232e0d>] ? default_wake_function+0x0/0xf
[<ffffffff80397b45>] ? mon_text_read_u+0x2b/0x2b6
[<ffffffff802eb576>] ? security_file_permission+0x11/0x13
[<ffffffff80298bce>] ? vfs_read+0xa4/0xde
[<ffffffff8020c374>] ? sysret_signal+0x1c/0x27
[<ffffffff8020c5f7>] ptregscall_common+0x67/0xb0
---[ end trace 55672de67f8b5497 ]---
next reply other threads:[~2008-04-21 21:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 21:10 Frans Pop [this message]
2008-04-22 13:40 ` [sched-devel/latest] WARNING: at mm/slub.c:2443 Ingo Molnar
2008-04-22 17:27 ` Pekka J Enberg
2008-04-22 19:22 ` Christoph Lameter
2008-04-22 21:32 ` Pete Zaitcev
2008-04-23 5:21 ` Pekka J Enberg
2008-04-23 6:51 ` Pete Zaitcev
2008-04-23 7:31 ` Pekka Enberg
2008-04-23 7:34 ` Pekka Enberg
2008-04-23 17:13 ` Pete Zaitcev
2008-04-23 7:38 ` Pekka J Enberg
2008-04-23 17:11 ` Pete Zaitcev
2008-04-23 17:35 ` Pekka Enberg
2008-04-23 18:15 ` Frans Pop
2008-04-24 14:13 ` Frans Pop
2008-05-02 9:17 ` Pekka Enberg
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=200804212310.41729.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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