From: Mike Galbraith <efault@gmx.de>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test7 DEBUG_PAGEALLOC oops
Date: Sat, 11 Oct 2003 13:15:52 +0200 [thread overview]
Message-ID: <5.2.1.1.2.20031011120059.01e81718@pop.gmx.net> (raw)
In-Reply-To: <3F87CF3D.8080402@colorfullife.com>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
At 11:37 AM 10/11/2003 +0200, Manfred Spraul wrote:
>Mike wrote:
>
>>Unable to handle kernel paging request at virtual address c034a000
>>printing eip:
>>c0134d5a
>>*pde = 00102027
>>*pte = 0034a000
>Fault trying to read from address 0xc034a000: the page is not mapped.
>
>>Oops: 0000 [#1]
>>CPU: 0
>>EIP: 0060:[<c0134d5a>] Not tainted
>>EFLAGS: 00010002
>>EIP is at store_stackinfo+0x4e/0x80
>In store_stackinfo: the function stores a backtrace of the last
>kmem_cache_free caller in the object - might be useful, and the memory is
>not used.
>
>>eax: 00000000 ebx: c7802f98 ecx: c0301390 edx: c030138c
>>esi: c0349ffe edi: 017e0008 ebp: c0349da6 esp: c0349d96
>>ds: 007b es: 007b ss: 0068
>>Process swapper (pid: 0, threadinfo=c0348000 task=c02fcbe0)
>The esp value is sane, the stack is at 0xc0348000, and the fault is at
>'a000: just behind the end of the stack.
>I assume the fauling line is
> svalue = *sptr++;
Exactly.
>It looks like store stackinfo accesses memory behind the end of the stack.
Yeah, I'm trying to figure out why. The below (if dang mailer actually
inlines it) kludge allows me to boot, so I suppose I need to ponder addr
wrt _stext and _etext.
>Which gcc version do you use? Could you send me mm/slab.o?
gcc-2.95.3. slab.o coming via private mail.
-Mike
[-- Attachment #2: Type: text/plain, Size: 467 bytes --]
--- mm/slab.c.org Sat Oct 11 12:25:24 2003
+++ mm/slab.c Sat Oct 11 12:26:02 2003
@@ -864,12 +864,11 @@
while (((long) sptr & (THREAD_SIZE-1)) != 0) {
svalue = *sptr++;
- if (kernel_text_address(svalue)) {
+ if (kernel_text_address(svalue))
*addr++=svalue;
- size -= sizeof(unsigned long);
- if (size <= sizeof(unsigned long))
- break;
- }
+ size -= sizeof(unsigned long);
+ if (size <= sizeof(unsigned long))
+ break;
}
}
next prev parent reply other threads:[~2003-10-11 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 9:37 Manfred Spraul
2003-10-11 11:15 ` Mike Galbraith [this message]
2003-10-11 12:06 ` Manfred Spraul
2003-10-11 15:52 ` Mike Galbraith
2003-10-11 17:34 ` Manfred Spraul
2003-10-12 5:11 ` Mike Galbraith
2003-10-12 6:58 ` Manfred Spraul
2003-10-12 8:52 ` Mike Galbraith
2003-10-12 12:08 ` Thomas Molina
2003-10-12 14:13 ` Thomas Molina
2003-10-12 22:36 ` Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 13:04 2.6.0-test7 oops in proc_pid_stat Olaf Hering
2003-10-09 22:04 ` Linus Torvalds
2003-10-10 6:50 ` 2.6.0-test7 DEBUG_PAGEALLOC oops Mike Galbraith
2003-10-10 16:52 ` Zwane Mwaikambo
2003-10-11 7:01 ` Mike Galbraith
2003-10-11 7:03 ` Zwane Mwaikambo
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=5.2.1.1.2.20031011120059.01e81718@pop.gmx.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=zwane@arm.linux.org.uk \
/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®