From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216156] New: kmemleak: Not scanning unknown object at 0xc00000007f000000
Date: Mon, 20 Jun 2022 23:14:43 +0000 [thread overview]
Message-ID: <bug-216156-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216156
Bug ID: 216156
Summary: kmemleak: Not scanning unknown object at
0xc00000007f000000
Product: Platform Specific/Hardware
Version: 2.5
Kernel Version: 5.19-rc3
Hardware: PPC-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: erhard_f@mailbox.org
Regression: No
Created attachment 301230
--> https://bugzilla.kernel.org/attachment.cgi?id=301230&action=edit
dmesg (5.19-rc3, PowerMac G5 11,2)
Happens every boot with kmemleak enabled:
[...]
PowerMac motherboard: PowerMac G5 Dual Core
ioremap() called early from .btext_map+0x64/0xc0. Use early_ioremap() instead
ioremap() called early from .iommu_init_early_dart+0x260/0x924. Use
early_ioremap() instead
kmemleak: Not scanning unknown object at 0xc00000007f000000
CPU: 0 PID: 0 Comm: swapper Not tainted 5.19.0-rc3-PMacG5+ #2
Call Trace:
[c00000000113faf0] [c0000000006c03d0] .dump_stack_lvl+0x7c/0xc4 (unreliable)
[c00000000113fb80] [c0000000002dff90] .kmemleak_no_scan+0xe0/0x100
[c00000000113fc00] [c000000000d487e8] .iommu_init_early_dart+0x2f0/0x924
[c00000000113fd40] [c000000000d49984] .pmac_probe+0x1b0/0x20c
[c00000000113fde0] [c000000000d36ee8] .setup_arch+0x1b8/0x674
[c00000000113feb0] [c000000000d316f4] .start_kernel+0xdc/0xb74
[c00000000113ff90] [c00000000000c5d8] start_here_common+0x1c/0x44
DART table allocated at: (____ptrval____)
DART IOMMU initialized for U4 type chipset
Using PowerMac machine description
printk: bootconsole [udbg0] enabled
CPU maps initialized for 1 thread per core
[...]
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-06-20 23:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 23:14 bugzilla-daemon [this message]
2022-06-20 23:15 ` [Bug 216156] kmemleak: Not scanning unknown object at 0xc00000007f000000 bugzilla-daemon
2022-06-20 23:30 ` bugzilla-daemon
2022-06-20 23:37 ` bugzilla-daemon
2022-08-25 0:39 ` bugzilla-daemon
2022-08-25 0:40 ` bugzilla-daemon
2022-11-14 22:11 ` bugzilla-daemon
2022-11-14 22:12 ` bugzilla-daemon
2023-08-19 23:00 ` bugzilla-daemon
2023-08-19 23:01 ` bugzilla-daemon
2023-10-05 23:41 ` [Bug 216156] [bisected] " bugzilla-daemon
2023-10-05 23:43 ` bugzilla-daemon
2023-10-05 23:43 ` bugzilla-daemon
2023-10-09 4:36 ` bugzilla-daemon
2023-10-09 15:50 ` bugzilla-daemon
2023-10-10 12:14 ` bugzilla-daemon
2023-10-10 18:21 ` bugzilla-daemon
2024-04-19 8:30 ` bugzilla-daemon
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=bug-216156-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.