<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!" href="https://bugs.freedesktop.org/show_bug.cgi?id=84500#c28">Comment # 28</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!" href="https://bugs.freedesktop.org/show_bug.cgi?id=84500">bug 84500</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to Alexandre Demers from <a href="show_bug.cgi?id=84500#c27">comment #27</a>) > (In reply to Christian König from <a href="show_bug.cgi?id=84500#c22">comment #22</a>) > > Keep in mind that this might actually be a user space problem and that > > different kernel versions work or don't work only be coincident. > > > > If you can get me an SSH access to the box I could take a look as well. > > Attaching a debugger to the process in question shouldn't be to hard. > > By the way, if I understand correctly, if the bug is in userspace and was > introduced around the same time kernel 3.17-rcX went out, would it appears > when using a previous kernel version? I'm trying to figure out a way to > distinguish one from the other because from where I am in the bisection, I > was unable to reproduce the bug with a 3.16 kernel, but it does appear > before 3.17-rc1... It is possible that a new kernel let this problem surface by coincident. E.g. a slightly different memory layout or allocation timing and instead of changing two random pixel on the screen we change the command buffer and the whole box crashes and/or shows this error. All you can do is to try to figure out when the corruption happens. The kernel copies the command buffer content from userspace to a kernel buffer and then checks the content of the kernel buffer. Might be a good idea to print the content of the userspace buffer as well and compare both?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>