From: batouzo <batouzo@gmx.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [drm] [radeon] [3.1.4] slub memory corruption in drm_vblank_cleanup
Date: Wed, 14 Dec 2011 00:33:04 +0100 [thread overview]
Message-ID: <jc8nbg$j3j$1@dough.gmane.org> (raw)
In-Reply-To: <20111213233157.GD2339@homer.localdomain>
On 12/14/2011 12:31 AM, Jerome Glisse wrote:
>> Allocated in drm_vblank_init+0x139/0x260 [drm] + Freed in
>> drm_vblank_cleanup+0x78/0x90 [drm]
>> Allocated in drm_vblank_init+0xbe/0x260 [drm] + Freed in
>> drm_vblank_cleanup+0x48/0x90 [drm]
>>
>> It is Amd Bulldozer computer, with Radeon card:
>> 01:00.0 VGA compatible controller: ATI Technologies Inc Cedar PRO
>> [Radeon HD 5450]
>>
>> messages: http://pastebin.com/NXN5EPtG
>> config used: http://pastebin.com/AeVxEX7c
>
> Do you boot your kernel with kexec ? Does the patch help :
Nope. Already seen that kexec bugfix on LKML but I start system normally
not with kexec.
> http://people.freedesktop.org/~glisse/0001-drm-radeon-disable-possible-GPU-writeback-early-v3.patch
> If not please open bug on bugs.freedesktop.org against radeon driver.
ok
next prev parent reply other threads:[~2011-12-13 23:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 21:26 [drm] [radeon] [3.1.4] slub memory corruption in drm_vblank_cleanup batouzo
2011-12-13 23:31 ` Jerome Glisse
2011-12-13 23:33 ` batouzo [this message]
2011-12-13 23:46 ` Jerome Glisse
2011-12-13 23:47 ` Jerome Glisse
2011-12-14 7:00 ` batouzo
2011-12-14 14:10 ` Alex Deucher
2011-12-14 16:32 ` batouzo
2011-12-14 16:40 ` Alex Deucher
2011-12-14 17:12 ` batouzo
2011-12-14 17:21 ` Alex Deucher
2011-12-14 17:27 ` batouzo
2011-12-14 17:40 ` Alex Deucher
2011-12-14 17:49 ` batouzo
2011-12-14 18:14 ` Alex Deucher
2011-12-14 16:18 ` Jerome Glisse
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='jc8nbg$j3j$1@dough.gmane.org' \
--to=batouzo@gmx.com \
--cc=dri-devel@lists.freedesktop.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.