dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66932] Screen corruption on Cayman with dpm enabled
Date: Wed, 17 Jul 2013 11:09:00 +0000	[thread overview]
Message-ID: <bug-66932-502-kEdZkux5J5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66932-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=66932

--- Comment #12 from Martin Andersson <g02maran@gmail.com> ---
Take this information with a grain of salt, since I'm testing stuff without
really knowing whats going on.

I found it interesting that the dmesg with the mc dump didn't print anything
from the first for loop in the patch, so I did some testing.

I added a bunch of debug printks to radeon_atom_init_mc_reg_table to see what
was happening. I found that num_entries is 13, but what was more interesting
was that some printks was skipped and now I got a kernel oops (NULL pointer
dereference).

It looked like this while loop was executed once (without problems), then
strange things happended:
while (!(reg_block->asRegIndexBuf[i].ucPreRegDataLength &
ACCESS_PLACEHOLDER)...

So I added this printk before and after "i++;" in that while loop:
printk(KERN_INFO "debug=%u", reg_block->asRegIndexBuf[i].ucPreRegDataLength);

gcc didn't complain about the first printk but for the second it said this:
drivers/gpu/drm/radeon/radeon_atombios.c:3741:60: warning: array subscript is
above array bounds [-Warray-bounds]

It might be a false positive but it matches with my debug printks, everything
is fine until the second iteration in that while loop. After that the execution
jumps further down in the function and crashes.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2206 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-07-17 11:09 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:45 [Bug 66932] New: Screen corruption on Cayman with dpm enabled bugzilla-daemon
2013-07-15 15:54 ` [Bug 66932] " bugzilla-daemon
2013-07-16  1:05 ` bugzilla-daemon
2013-07-16  5:11 ` bugzilla-daemon
2013-07-16 13:21 ` bugzilla-daemon
2013-07-16 17:10 ` bugzilla-daemon
2013-07-16 20:43 ` bugzilla-daemon
2013-07-16 20:47 ` bugzilla-daemon
2013-07-16 21:10 ` bugzilla-daemon
2013-07-16 21:23 ` bugzilla-daemon
2013-07-17  1:45 ` bugzilla-daemon
2013-07-17  9:13 ` bugzilla-daemon
2013-07-17 11:09 ` bugzilla-daemon [this message]
2013-07-17 16:40 ` bugzilla-daemon
2013-07-17 16:42 ` bugzilla-daemon
2013-07-17 16:48 ` bugzilla-daemon
2013-07-17 17:02 ` bugzilla-daemon
2013-07-17 17:13 ` bugzilla-daemon
2013-07-17 17:47 ` bugzilla-daemon
2013-07-17 17:49 ` bugzilla-daemon
2013-07-17 17:52 ` bugzilla-daemon
2013-07-17 17:55 ` bugzilla-daemon
2013-07-17 18:00 ` bugzilla-daemon
2013-07-17 18:02 ` bugzilla-daemon
2013-07-17 18:10 ` bugzilla-daemon
2013-07-17 18:14 ` bugzilla-daemon
2013-07-17 18:15 ` bugzilla-daemon
2013-07-17 18:16 ` bugzilla-daemon
2013-07-17 18:25 ` bugzilla-daemon
2013-07-17 20:38 ` bugzilla-daemon
2013-07-17 20:46 ` bugzilla-daemon
2013-07-17 21:42 ` bugzilla-daemon
2013-07-17 21:52 ` bugzilla-daemon
2013-08-13 23:09 ` 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-66932-502-kEdZkux5J5@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox