From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: frankpzh@gmail.com, "Greg KH" <gregkh@suse.de>,
"Ortwin Glück" <odi@odi.ch>,
linux-kernel@vger.kernel.org, jirislaby@gmail.com
Subject: Re: BUG kmalloc-4096: Poison overwritten (2.6.35-rc2)
Date: Sun, 06 Jun 2010 15:05:04 -0700 [thread overview]
Message-ID: <4C0C1B90.6080407@gmail.com> (raw)
In-Reply-To: <1275860015-6643-1-git-send-email-jslaby@suse.cz>
On 06/06/2010 02:33 PM, Jiri Slaby wrote:
> On 06/06/2010 11:06 PM, Justin P. Mattock wrote:
>> On 06/05/2010 11:27 PM, Jiri Slaby wrote:
>>> 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?
>>>
>>
>>
>> o.k. I bisected this down to this commit:
>> 962400e8fd29
>> reverting gets dmesg to not
>> have a Poison overwritten..
>
> This definitely makes sense.
>
>> as for the screen blankness I think this
>> did cause it..keep in mind the blankness(black)
>> is not everytime(every so often)
>> here's some images of it:
>> http://www.flickr.com/photos/44066293@N08/4676350524/
>> http://www.flickr.com/photos/44066293@N08/4676350016/
>
> Yes, as I guessed, the "grey spaces" were written to some random space
> instead of video ram where they should overwrite (clear) the characters
> which you see on the pictures.
>
> Does the patch below help?
>
> ---
> drivers/char/vt.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/vt.c b/drivers/char/vt.c
> index 1296c42..e123958 100644
> --- a/drivers/char/vt.c
> +++ b/drivers/char/vt.c
> @@ -304,8 +304,8 @@ static void scrup(struct vc_data *vc, unsigned int t, unsigned int b, int nr)
> d = (unsigned short *)(vc->vc_origin + vc->vc_size_row * t);
> s = (unsigned short *)(vc->vc_origin + vc->vc_size_row * (t + nr));
> scr_memmovew(d, s, (b - t - nr) * vc->vc_size_row);
> - scr_memsetw(d + (b - t - nr) * vc->vc_size_row, vc->vc_video_erase_char,
> - vc->vc_size_row * nr);
> + scr_memsetw((void *)d + (b - t - nr) * vc->vc_size_row,
> + vc->vc_video_erase_char, vc->vc_size_row * nr);
> }
>
> static void scrdown(struct vc_data *vc, unsigned int t, unsigned int b, int nr)
o.k. applied the above patch,
and yes I dont see the Poison overwritten
in dmesg, as well as the messages in the
pics that I uploaded..
so I can say that the above fixes the issue
(will monitor the system the remainder
of the day to see if anything happens..)
Reported-and-Bisected-By: Justin P. Mattock <justinmattock@gmail.com>
cheers,
Justin P. Mattock
next prev parent reply other threads:[~2010-06-06 22:04 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
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 [this message]
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=4C0C1B90.6080407@gmail.com \
--to=justinmattock@gmail.com \
--cc=frankpzh@gmail.com \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=odi@odi.ch \
/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.