From: "Michel Dänzer" <michel@daenzer.net>
To: Esben Stien <b0ef@esben-stien.name>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Packet0 not allowed
Date: Tue, 15 Jul 2014 18:31:39 +0900 [thread overview]
Message-ID: <53C4F4FB.3050401@daenzer.net> (raw)
In-Reply-To: <8738e3j81s.fsf@quasar.esben-stien.name>
On 15.07.2014 18:16, Esben Stien wrote:
> Michel Dänzer <michel@daenzer.net> writes:
>
>> Any other interesting messages before those?
>
> Yeah, sorry, I just counted 9700 of those lines since boot, so I missed
> those.
>
> http://esben-stien.name/share/kern.log.txt
Looks like userspace is submitting invalid command streams to the kernel.
So, what are you doing / trying to do when this happens?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-07-15 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 22:45 Packet0 not allowed Esben Stien
2014-07-15 1:48 ` Michel Dänzer
2014-07-15 9:16 ` Esben Stien
2014-07-15 9:31 ` Michel Dänzer [this message]
2014-07-15 12:36 ` Esben Stien
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=53C4F4FB.3050401@daenzer.net \
--to=michel@daenzer.net \
--cc=b0ef@esben-stien.name \
--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