From: "Miles Lane" <miles.lane@gmail.com>
To: balbir@linux.vnet.ibm.com
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Hirokazu Takahashi" <taka@valinux.co.jp>
Subject: Re: 2.6.26-rc5-mm1 -- WARNING: at kernel/res_counter.c:49 res_counter_uncharge_locked+0x5a/0x96()
Date: Tue, 10 Jun 2008 10:04:33 -0400 [thread overview]
Message-ID: <a44ae5cd0806100704o180ffbfah9a1c75a62b10753@mail.gmail.com> (raw)
In-Reply-To: <484E0200.6060107@linux.vnet.ibm.com>
Yes, that appears to fix it. Thanks!
Miles
On Tue, Jun 10, 2008 at 12:24 AM, Balbir Singh
<balbir@linux.vnet.ibm.com> wrote:
> Miles Lane wrote:
>> kernel: WARNING: at kernel/res_counter.c:49
>> res_counter_uncharge_locked+0x5a/0x96()
>> kernel: Modules linked in: cpufreq_ondemand cpufreq_conservative sbs
>> sbshc battery ac sbp2 arc4 snd_intel8x0 snd_ac97_codec ac97_bus
>> snd_pcm_oss snd_mixer_oss ecb crypto_blkcipher cryptomgr snd_pcm
>> crypto_algapi snd_seq_dummy rtc b43 snd_seq_oss snd_seq_midi_event
>> mac80211 cfg80211 led_class snd_seq ohci1394 ieee1394 snd_timer
>> snd_seq_device snd shpchp pci_hotplug soundcore snd_page_alloc
>> i2c_nforce2 i2c_core button thermal processor fan
>> kernel: Pid: 4168, comm: expr Tainted: G W 2.6.26-rc5-mm1 #2
>> kernel: [mac80211:warn_on_slowpath+0x95/0x5c6] warn_on_slowpath+0x95/0xf1
>> kernel: [__slab_free+0x268/0x7ff] ? __slab_free+0x268/0x7ff
>> kernel: [processor:trace_hardirqs_on+0x27/0xde1c] ? trace_hardirqs_on+0x27/0x37
>> kernel: [free_hot_cold_page+0x454/0x4c3] ? free_hot_cold_page+0x454/0x4c3
>> kernel: [paravirt_get_lazy_mode+0x1c/0x37] ? paravirt_get_lazy_mode+0x1c/0x37
>> kernel: [unmap_vmas+0x984/0xd55] ? unmap_vmas+0x984/0xd55
>> kernel: [res_counter_uncharge+0x26/0x6b] ? res_counter_uncharge+0x26/0x6b
>> kernel: [res_counter_uncharge_locked+0x5a/0x96]
>> res_counter_uncharge_locked+0x5a/0x96
>> kernel: [res_counter_uncharge+0x40/0x6b] res_counter_uncharge+0x40/0x6b
>> kernel: [memrlimit_cgroup_uncharge_as+0x47/0x57]
>> memrlimit_cgroup_uncharge_as+0x47/0x57
>> kernel: [unmap_region+0x14e/0x29e] unmap_region+0x14e/0x29e
>> kernel: [do_munmap+0x339/0x41d] do_munmap+0x339/0x41d
>> kernel: [sys_munmap+0x76/0xa1] sys_munmap+0x76/0xa1
>> kernel: [sysenter_past_esp+0x78/0xc5] sysenter_past_esp+0x78/0xc5
>> kernel: =======================
>> kernel: ---[ end trace c305141495cb1ca4 ]---
>>
>
> Hi,
>
> Could you please see if the patch at
>
> http://lkml.org/lkml/2008/6/9/274
>
> fixes your problem
>
>
> --
> Warm Regards,
> Balbir Singh
> Linux Technology Center
> IBM, ISTL
>
prev parent reply other threads:[~2008-06-10 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 22:21 Miles Lane
2008-06-10 4:24 ` Balbir Singh
2008-06-10 14:04 ` Miles Lane [this message]
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=a44ae5cd0806100704o180ffbfah9a1c75a62b10753@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
/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®