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 84500] [radeonsi] radeon 0000:01:00.0: Packet0 not allowed!
Date: Sat, 11 Oct 2014 14:56:51 +0000	[thread overview]
Message-ID: <bug-84500-502-nYfJDd1Kvx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84500-502@http.bugs.freedesktop.org/>


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

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

--- Comment #23 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(In reply to Christian König from comment #22)
> 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.

I've been having a hard time getting the error lately (not encountered in the
last two days with a kernel 3.17-rc4). I'll go back to a newer kernel and I'll
see if the Packet0 bug still happens as often as before.

About the SSH connection, that could be possible if needed in time.

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

[-- Attachment #1.2: Type: text/html, Size: 1729 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:[~2014-10-11 14:56 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30  6:00 [Bug 84500] New: [radeonsi] radeon 0000:01:00.0: Packet0 not allowed! bugzilla-daemon
2014-09-30  6:04 ` [Bug 84500] " bugzilla-daemon
2014-09-30  7:18 ` bugzilla-daemon
2014-09-30 13:07 ` bugzilla-daemon
2014-09-30 13:28 ` bugzilla-daemon
2014-10-01  6:05 ` bugzilla-daemon
2014-10-01 15:51 ` bugzilla-daemon
2014-10-02  3:29 ` bugzilla-daemon
2014-10-02 12:32 ` bugzilla-daemon
2014-10-02 22:21 ` bugzilla-daemon
2014-10-03  6:21 ` bugzilla-daemon
2014-10-03 19:17 ` bugzilla-daemon
2014-10-03 19:21 ` bugzilla-daemon
2014-10-04  4:42 ` bugzilla-daemon
2014-10-04  8:45 ` bugzilla-daemon
2014-10-05 15:16 ` bugzilla-daemon
2014-10-06  4:27 ` bugzilla-daemon
2014-10-06  4:36 ` bugzilla-daemon
2014-10-10  4:33 ` bugzilla-daemon
2014-10-10 18:25 ` bugzilla-daemon
2014-10-10 21:06 ` bugzilla-daemon
2014-10-11  1:39 ` bugzilla-daemon
2014-10-11 13:52 ` bugzilla-daemon
2014-10-11 14:56 ` bugzilla-daemon [this message]
2014-10-13  5:34 ` bugzilla-daemon
2014-10-19 11:16 ` bugzilla-daemon
2014-10-19 12:23 ` bugzilla-daemon
2014-10-19 18:28 ` bugzilla-daemon
2014-10-19 20:35 ` bugzilla-daemon
2014-10-20  7:19 ` bugzilla-daemon
2014-10-24 15:54 ` bugzilla-daemon
2014-10-27 18:18 ` bugzilla-daemon
2014-10-27 22:14 ` bugzilla-daemon
2014-10-27 22:19 ` bugzilla-daemon
2014-10-27 22:22 ` bugzilla-daemon
2014-11-11  9:32 ` bugzilla-daemon
2014-11-11 13:51 ` bugzilla-daemon
2014-11-12 16:27 ` bugzilla-daemon
2014-11-17  1:37 ` bugzilla-daemon
2014-11-27 12:33 ` bugzilla-daemon
2014-11-27 22:59 ` bugzilla-daemon
2015-01-16  4:39 ` bugzilla-daemon
2015-02-02 21:56 ` bugzilla-daemon
2015-02-02 21:57 ` bugzilla-daemon
2015-02-18  7:53 ` bugzilla-daemon
2015-02-19 11:40 ` bugzilla-daemon
2015-02-19 15:44 ` bugzilla-daemon
2015-02-19 15:44 ` bugzilla-daemon
2015-02-28 15:59 ` bugzilla-daemon
2015-02-28 18:57 ` bugzilla-daemon
2015-03-17 14:19 ` bugzilla-daemon
2015-03-17 14:20 ` bugzilla-daemon
2015-03-31 10:04 ` bugzilla-daemon
2015-09-28 22:35 ` bugzilla-daemon
2015-09-29  8:05 ` bugzilla-daemon
2015-09-29 22:42 ` bugzilla-daemon
2019-11-19  8:57 ` 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-84500-502-nYfJDd1Kvx@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