From: Jiri Slaby <jirislaby@gmail.com>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
linux-video@atrey.karlin.mff.cuni.cz
Subject: Re: BUG kmalloc-4096: Poison overwritten
Date: Sun, 06 Jun 2010 08:27:43 +0200 [thread overview]
Message-ID: <4C0B3FDF.6080303@gmail.com> (raw)
In-Reply-To: <4C0B3C5B.5040703@gmail.com>
On 06/06/2010 08:12 AM, Justin P. Mattock wrote:
> =============================================================================
>
> [ 0.002046] BUG kmalloc-4096: Poison overwritten
> [ 0.002051]
> -----------------------------------------------------------------------------
>
> [ 0.002052]
> [ 0.002063] INFO: 0xffff88003ec09e00-0xffff88003ec09e9f. First byte
> 0x20 instead of 0x6b
> [ 0.002073] INFO: Slab 0xffffea0000dba1c0 objects=7 used=1
> fp=0xffff88003ec09048 flags=0x40000000000040c3
> [ 0.002082] INFO: Object 0xffff88003ec09048 @offset=4168
> fp=0xffff88003ec0a090
> [ 0.002083]
> [ 0.002093] Bytes b4 0xffff88003ec09038: 00 00 00 00 00 00 00 00 5a
> 5a 5a 5a 5a 5a 5a 5a ........ZZZZZZZZ
> [ 0.002114] Object 0xffff88003ec09048: 6b 6b 6b 6b 6b 6b 6b 6b 6b
> 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
...
> 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
> [ 0.002999] Object 0xffff88003ec09df8: 6b 6b 6b 6b 6b 6b 6b 6b 20
> 07 20 07 20 07 20 07 kkkkkkkk........
> [ 0.002999] Object 0xffff88003ec09e08: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e18: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e28: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e38: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e48: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e58: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e68: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e78: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e88: 20 07 20 07 20 07 20 07 20
> 07 20 07 20 07 20 07 ................
> [ 0.002999] Object 0xffff88003ec09e98: 20 07 20 07 20 07 20 07 6b
> 6b 6b 6b 6b 6b 6b 6b ........kkkkkkkk
> [ 0.002999] Object 0xffff88003ec09ea8: 6b 6b 6b 6b 6b 6b 6b 6b 6b
Just guessing, grey spaces which should go to video ram?
--
js
next prev parent reply other threads:[~2010-06-06 6:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 6:12 BUG kmalloc-4096: Poison overwritten Justin P. Mattock
2010-06-06 6:27 ` Jiri Slaby [this message]
2010-06-06 6:41 ` Justin P. Mattock
2010-06-06 21:06 ` Justin P. Mattock
2010-06-06 21:33 ` BUG kmalloc-4096: Poison overwritten (2.6.35-rc2) Jiri Slaby
2010-06-06 22:05 ` Justin P. Mattock
2010-06-07 2:16 ` Frank Pan
2010-06-07 3:25 ` Dave Airlie
2010-06-07 3:55 ` Linus Torvalds
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=4C0B3FDF.6080303@gmail.com \
--to=jirislaby@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-video@atrey.karlin.mff.cuni.cz \
--cc=x86@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 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.