From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org
Subject: Re: next-0704: WARNING: at kernel/sched.c:4254 add_preempt_count; PANIC
Date: Mon, 7 Jul 2008 09:32:41 +0200 [thread overview]
Message-ID: <19f34abd0807070032wb6a2d50s99de5950132016f5@mail.gmail.com> (raw)
In-Reply-To: <487159DA.708@gmail.com>
On Mon, Jul 7, 2008 at 1:48 AM, Alexander Beregalov
<a.beregalov@gmail.com> wrote:
> Hi
>
> WARNING: at kernel/sched.c:4254 add_preempt_count+0x61/0x63()
> Modules linked in: i2c_nforce2
> Pid: 3620, comm: rtorrent Not tainted 2.6.26-rc8-next-20080704 #5
> [<c038e436>] ? printk+0xf/0x11
> [<c011b681>] warn_on_slowpath+0x41/0x7b
> [<c0157a94>] ? mmap_region+0x1c5/0x414
> [<c0156499>] ? remove_vma+0x50/0x56
> [<c0159836>] ? anon_vma_prepare+0x52/0xc5
...
> BUG: unable to handle kernel paging request at fffef4f1
> IP: [<c0103c53>] dump_trace+0xa5/0xe2
> *pde = 00007067 *pte = 00000000
> Oops: 0000 [#1] PREEMPT DEBUG_PAGEALLOC
> last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:02:00.1/class
> Modules linked in: i2c_nforce2
>
> Pid: 3620, comm: rtorrent Not tainted (2.6.26-rc8-next-20080704 #5)
> EIP: 0060:[<c0103c53>] EFLAGS: 00210097 CPU: 0
> EIP is at dump_trace+0xa5/0xe2
> EAX: fffefffc EBX: fffef4f1 ECX: c0396978 EDX: c0455a08
> ESI: 5a5a5a5a EDI: f4d4c084 EBP: f4d4bf34 ESP: f4d4bf14
^--- POISON_INUSE
But I don't know if this is really significant, given that it's not
the first error you're getting. It may also be just a remnant of the
memset() that marks the SLUB objects as such. (Or something like
that.)
Too bad the recursive page fault stops us from getting the Code: line.
Config would be nice :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-07 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 23:48 Alexander Beregalov
2008-07-07 6:23 ` Alexander Beregalov
2008-07-07 6:35 ` Ingo Molnar
2008-07-07 7:32 ` Vegard Nossum [this message]
2008-07-07 7:46 ` Alexander Beregalov
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=19f34abd0807070032wb6a2d50s99de5950132016f5@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@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