From: "Chris Friesen" <cfriesen@nortel.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: issues with kmemleak backport
Date: Tue, 19 Jan 2010 15:01:01 -0600 [thread overview]
Message-ID: <4B561D8D.1000003@nortel.com> (raw)
In-Reply-To: <4B55F3EF.9020408@nortel.com>
I realized that I could disable CONFIG_VT, and the previous issue went
away. The system got further into the boot and started bringing up
userspace, but then gave the error below.
BUG: unable to handle kernel paging request at 83234000
IP: [<c048ad32>] scan_block+0xb2/0x100
Oops: 0000 [#1] SMP
Modules linked in: ipmi_serial_terminal_mode ipmi_serial ipmi_msghandler
ipmi_devintf
Pid: 506, comm: kmemleak Not tainted (2.6.27-pne #25)
EIP: 0060:[<c048ad32>] EFLAGS: 00010293 CPU: 1
EIP is at scan_block+0xb2/0x100
EAX: 00000001 EBX: 00000000 ECX: 00000000 EDX: 8323779c
ESI: 83234000 EDI: 83237799 EBP: f6f8bf90 ESP: f6f8bf80
DS: 0068 ES: 007b FS: 00d8 GS: 0000 SS: 0068
Process kmemleak (pid: 506, ti=f6f8a000 task=f799da40 task.ti=f6f8a000)
Stack: 00000000 00000000 f60a5454 00000000 f6f8bfc0 c048affd 00000001
c0435330
00000206 00000001 00000000 00000002 f6f8bfb8 000927c0 c048b6c0
00000000
f6f8bfd0 c048b70e c08a66b0 00000000 f6f8bfe0 c043f6cc c043f690
00000000
Call Trace:
[<c048affd>] ? kmemleak_scan+0x11d/0x3c0
[<c0435330>] ? process_timeout+0x0/0x40
[<c048b6c0>] ? kmemleak_scan_thread+0x0/0xc0
[<c048b70e>] ? kmemleak_scan_thread+0x4e/0xc0
[<c043f6cc>] ? kthread+0x3c/0x70
[<c043f690>] ? kthread+0x0/0x70
[<c0404737>] ? kernel_thread_helper+0x7/0x10
=======================
Code: 15 50 7d 92 c0 c7 43 10 4c 7d 92 c0 89 43 14 89 10 89 ca 89 d8 e8
af c1 38 00 8d b4 26 00 00 00 00 83 c6 04 39 f7 7621 8b 45 08 <8b> 1e 85
c0 0f 84 6c ff ff ff e8 ff aa 38 00 e8 fa fe ff ff 85
Looking at the function offset it appears that kmemleak_scan() is
calling scan_block() for the per-cpu section.
I'll keep digging, but any suggestions would be appreciated.
Chris
next prev parent reply other threads:[~2010-01-19 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 18:03 issues with kmemleak backport Chris Friesen
2010-01-19 21:01 ` Chris Friesen [this message]
2010-01-20 17:51 ` Chris Friesen
2010-01-20 22:58 ` Catalin Marinas
2010-01-21 15:34 ` Chris Friesen
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=4B561D8D.1000003@nortel.com \
--to=cfriesen@nortel.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@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