https://bugs.freedesktop.org/show_bug.cgi?id=84500
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=87278
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|REOPENE
0.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0405200C
VM fault (0x0c, vmid 2) at page 1152747, read from CB_CMASK (82)
I always get the errors above and sometimes I get the gpu lockup and also
sometimes the Packet0 not allowed!.
The possible fix in #c10 does not help.
--
You are receiving this mail beca
https://bugzilla.kernel.org/show_bug.cgi?id=199385
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=199385
Bug ID: 199385
Summary: Lockup radeon :01:00.0: Packet0 not allowed!
Product: Drivers
Version: 2.5
Kernel Version: 4.15.15
Hardware: All
OS: Linux
Tree
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #54 from Chernovsky Oleg ---
> Great! You are the guy who also did the fan control patches aren't you?
Yep, that's me, thanks!
I also stalkered Michel Dänzer for explanations of GTT and VMM at some time :)
> As first step please t
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #53 from Christian König ---
(In reply to Chernovsky Oleg from comment #52)
> Created attachment 118502 [details]
> dmesg log
>
> Just got this bug and GPU lockup while trying to play Guild Wars through
> wine.
> Happens when I rota
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #52 from Chernovsky Oleg ---
Created attachment 118502
--> https://bugs.freedesktop.org/attachment.cgi?id=118502&action=edit
dmesg log
Just got this bug and GPU lockup while trying to play Guild Wars through wine.
Happens when I ro
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Daniel Scharrer changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #29 from Daniel Scharrer ---
With Mesa git-3bdbc1e, LLVM r236436 and Linux 4.0.1-gentoo my previous Talos
traces don't produce any GPU VM faults anymore. However, the game still does.
Here is a new trace:
http://constexpr.org/tmp/Ta
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Christoph Haag changed:
What|Removed |Added
Attachment #114793|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #27 from Christoph Haag ---
Created attachment 114806
--> https://bugs.freedesktop.org/attachment.cgi?id=114806&action=edit
Output with R600_DEBUG=ps,vs,gs
Uhm, good luck with that 7 megabyte file. Not sure what's the binary garbag
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #26 from Tom Stellard ---
Can you run the game with R600_DEBUG=ps,vs,gs and post the output?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was sc
ink you need a beta key to play) with
wine (wine-staging with csmt, I admit), I get a lot of GPU problems with
radeonsi.
I've seen "radeon 0000:01:00.0: Packet0 not allowed!" and a lot of GPU faults,
so perhaps it is related.
It's kinda unplayable with radeonsi because it
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #51 from Vladimir Ysikov ---
Created attachment 114754
--> https://bugs.freedesktop.org/attachment.cgi?id=114754&action=edit
dmesg log
I got same issue playing in Dota 2 and Alt+Tab in firefox.
Radeon 7950, kernel 4.0rc4, mesa-git,
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #50 from patches at portaildulibre.fr ---
Created attachment 114385
--> https://bugs.freedesktop.org/attachment.cgi?id=114385&action=edit
dmesg for M6700
--
You are receiving this mail because:
You are the assignee for the bug.
---
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #49 from patches at portaildulibre.fr ---
Happens with 3.18.9-100.fc20.x86_64
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #24 from ArneJ ---
I also see a lot of these messages in The Talos Principle on a R9 270X here:
...
[416091.177464] radeon :01:00.0: GPU fault detected: 147 0x000a0401
[416091.177467] radeon :01:00.0: VM_CONTEXT1_PROTECTION
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #48 from Alex Deucher ---
Dump the IB in userspace before submission and compare it to what gets dumped
in the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #47 from Chernovsky Oleg ---
Got this bug today.
How can I know whether is it user-space IB assembly corruption or kernel-space
error? I have all sources at hand, where to look at?
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=84500
Alexandre Demers changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Alexandre Demers changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #46 from Alexandre Demers ---
(In reply to Lorenzo Bona from comment #45)
> Since yesterday I've been testing last drm-fixes-3.19 kernel with old radeon
> firmwares. I mean before big upgrade on 24th of July.
>
> I've played Dota2 an
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #45 from Lorenzo Bona ---
Since yesterday I've been testing last drm-fixes-3.19 kernel with old radeon
firmwares. I mean before big upgrade on 24th of July.
I've played Dota2 and watched videos on flash and on mpv with vdpau, and I
c
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Daniel Scharrer changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #44 from Lorenzo Bona ---
I'm hitting this error too.
Playing Dota2 (my only game) causes this to appear in dmesg.
drm-fixes-3.19, mesa/ddx/xserver/drm from git.
The GPU is a R7-265.
The distribution is debian sid.
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #21 from Alexandre Demers ---
(In reply to Daniel Scharrer from comment #20)
> I can confirm that the GPU fault errors are gone, but still get Packet0
> errors (both in game and in the apitrace from Comment 7).
>
> Also, there were s
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #20 from Daniel Scharrer ---
I can confirm that the GPU fault errors are gone, but still get Packet0 errors
(both in game and in the apitrace from Comment 7).
Also, there were still GPU fault errors in The Talos Principle and demo (b
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #19 from Alexandre Demers ---
(In reply to Marek Olšák from comment #17)
> This seems to be fixed with current Mesa git. Can you confirm?
Indeed, no GPU faults and no Packet 0 observered. SS3 doesn't crash the whole
desktop anymore
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #18 from Christoph Haag ---
(In reply to Marek Olšák from comment #17)
> This seems to be fixed with current Mesa git. Can you confirm?
I played for a while and the problems were gone for me.
The performance is still very bad and
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #17 from Marek Olšák ---
This seems to be fixed with current Mesa git. Can you confirm?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrub
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #43 from Ãyvind Saether ---
Created attachment 113076
--> https://bugs.freedesktop.org/attachment.cgi?id=113076&action=edit
dmesg with packet not allowed error
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #42 from Ãyvind Saether ---
Happens with 3.19.0-rc6, no idea what triggered it.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
UR
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #41 from Alexandre Demers ---
There is an application that still triggers the Packet0 error: Serious Sam 3. I
could get an apitrace if someone thinks it could be useful.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #16 from Arash ---
Created attachment 111751
--> https://bugs.freedesktop.org/attachment.cgi?id=111751&action=edit
sorry i should've attached it
--
You are receiving this mail because:
You are the assignee for the bug.
---
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #15 from Arash ---
same issue, dota2 and with no Packet0 message.
kernel 3.18
llvm git
mesa git
r9-270x/radeonsi
it happens fairly frequently (or every time i pick 'morphling') :(
i haven't had this problem with 6570 (r600g)...
...
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #14 from Alexandre Demers ---
(In reply to Alexandre Demers from comment #13)
> Created attachment 111430 [details]
> VM faults and Packet0 error when quitting the current game
>
> on R9 270X with today's latest mesa, drm, ddx from g
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #13 from Alexandre Demers ---
Created attachment 111430
--> https://bugs.freedesktop.org/attachment.cgi?id=111430&action=edit
VM faults and Packet0 error when quitting the current game
on R9 270X with today's latest mesa, drm, ddx
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #12 from Alexandre Demers ---
Sorry, it has been a couple of weeks, but I confirm I have the same problem
with my R9 270X. I'm using latest mesa, drm, ddx from git repositories on a
3.19-rc1 kernel.
I'll be attaching my log. I'll als
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #11 from Christoph Haag ---
(In reply to Marek Olšák from comment #10)
> Created attachment 111036 [details] [review]
> possible fix for VM faults
>
> Does this patch fix the VM faults?
I don't think it does for me. I still get
r
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #10 from Marek Olšák ---
Created attachment 111036
--> https://bugs.freedesktop.org/attachment.cgi?id=111036&action=edit
possible fix for VM faults
Does this patch fix the VM faults?
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #9 from Michel Dänzer ---
Note that I'm only getting the VM faults with my Cape Verde card, not with my
Kaveri. Seems to be SI specific.
I haven't been able to reproduce the Packet0 error with this apitrace.
--
You are receiving t
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Michel Dänzer changed:
What|Removed |Added
CC|tstellar at gmail.com |maraeo at gmail.com
--- Comment #8 f
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #7 from Daniel Scharrer ---
(In reply to Michel Dänzer from comment #3)
> Does the environment variable R600_DEBUG=nodma avoid this problem?
No change here either. But now that you mention it: IIRC SS3 did sometimes lock
up the GPU
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Michel Dänzer changed:
What|Removed |Added
CC||tstellar at gmail.com
--- Comment #6 fr
S
> 0x12088001
> [ 6001.212249] VM fault (0x01, vmid 9) at page 267395474, read from TC (136)
>
> There are also a few "Packet0 not allowed" errors (followed by a hex dump):
>
> [15446.473341] radeon :01:00.0: Packet0 not allowed!
>
> So far it's only the
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #4 from Christoph Haag ---
(In reply to Michel Dänzer from comment #3)
> Does the environment variable R600_DEBUG=nodma avoid this problem?
No, R600_DEBUG=nodma does not help.
--
You are receiving this mail because:
You are the as
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #3 from Michel Dänzer ---
Does the environment variable R600_DEBUG=nodma avoid this problem?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was s
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Christoph Haag changed:
What|Removed |Added
CC||haagch at frickel.club
--- Comment #2 f
https://bugs.freedesktop.org/show_bug.cgi?id=87278
--- Comment #1 from Daniel Scharrer ---
Created attachment 110809
--> https://bugs.freedesktop.org/attachment.cgi?id=110809&action=edit
standard output from The Talos Principle and Serious Sam 3
The standard output has this repeated a few time
https://bugs.freedesktop.org/show_bug.cgi?id=87278
Bug ID: 87278
Summary: Packet0 not allowed and GPU fault detected errors with
Serious Engine games
Product: Mesa
Version: git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #40 from Alexandre Demers ---
(In reply to drago01 from comment #39)
> I am seeing those messages too here:
>
> radeon :02:00.0: Packet0 not allowed!
>
> on a R9 270X ... no hangs or anything else just the mes
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #39 from drago01 at gmail.com ---
I am seeing those messages too here:
radeon :02:00.0: Packet0 not allowed!
on a R9 270X ... no hangs or anything else just the message in the log (3.17.3
/ mesa 10.3.3 on F20).
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #38 from Alexandre Demers ---
For the last couple of days, I've been playing with kernel 3.19 drm-next and
with some previously problematic 3.18 kernel versions. I was unable to
reproduce the problem.
Mesa was updated a couple of tim
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #37 from Alexandre Demers ---
Well, the bisection was not conclusive... A branch's head commit produced the
error, but I was unable to reproduce it earlier in that branch... I'll have to
dig again in that branch and make sure it is re
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #36 from Alexandre Demers ---
Almost, I will be testing my last commit tonight (if I did no mistake along the
way). I'll have a look at the patch after that.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #35 from Michel Dänzer ---
(In reply to Alexandre Demers from comment #32)
> I'm still bisecting.
Did you get somewhere with the bisection? If not (or regardless), might be
worth testing the Mesa patches I attached to bug 85647.
--
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #34 from Dieter Nützel ---
(In reply to Dieter Nützel from comment #33)
> Hello Alexandre,
>
> maybe you can take a look, here to speed things up?
> https://bugzilla.kernel.org/show_bug.cgi?id=86891
> Comment #3 and #4.
I'll testi
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #33 from Dieter Nützel ---
Hello Alexandre,
maybe you can take a look, here to speed things up?
https://bugzilla.kernel.org/show_bug.cgi?id=86891
Comment #3 and #4.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #32 from Alexandre Demers ---
(In reply to José Suárez from comment #31)
> I've been testing linux 3.18 rc1 for a few days and I've found it to be
> quite stable with regard to this bug. No hangs for me yet, but the Patcket0
> massa
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #31 from José Suárez ---
I've been testing linux 3.18 rc1 for a few days and I've found it to be quite
stable with regard to this bug. No hangs for me yet, but the Patcket0 massages
still show up in dmesg.
--
You are receiving thi
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #30 from Maciej ---
Imagine bug like this happening on Windows, customers would go nuts and it
would be fixed asap by AMD... But hey, Linux is not second class citizen,
right?
--
You are receiving this mail because:
You are the assi
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #29 from Michel D?nzer ---
(In reply to Alexandre Demers from comment #27)
> 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
>
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #28 from Christian K?nig ---
(In reply to Alexandre Demers from comment #27)
> (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 wor
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #27 from Alexandre Demers ---
(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 g
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #26 from Erich Seifert ---
I'm also getting "Packet0 not allowed!" messages with a Radeon HD 7770 (Cape
Verde XT) video card on kernel 3.17.0 and 3.17.1.
I experienced several random crashes with 3.17.0, but I'
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #25 from Zolt?n B?sz?rm?nyi ---
I see "Packet0 not allowed" messages on 3.17.0 / 3.17.1 under Fedora 21.
The video card is R9 270X, also Pitcairn.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #24 from Alexandre Demers ---
(In reply to Alexandre Demers from comment #23)
> (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 wo
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #23 from Alexandre Demers ---
(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 g
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #22 from Christian K?nig ---
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 we
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #21 from Alexandre Demers ---
(In reply to John Bridgman from comment #20)
> Yes, AFAIK HD 78xx is Pitcairn and HD 79xx is Tahiti.
Well, I'm sick (literally) and I mixed Jos?'s dmesg with mine. Everything is
fine with the device ID t
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #20 from John Bridgman ---
Yes, AFAIK HD 78xx is Pitcairn and HD 79xx is Tahiti.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
UR
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #19 from Alexandre Demers ---
Hmmm, dummy question but I must ask: isn't a HD 7950 supposed to be a Tahiti
GPU? Because when looking in dmesg, it seems to load a Pitcairn ucode... My
research seems to say it is indeed a Tahiti GPU...
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #18 from Alexandre Demers ---
I add to come back in my bisection because the result couldn't make sense. It's
taking longer than expected...
--
You are receiving this mail because:
You are the assignee for the bug.
-- ne
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #17 from Alexandre Demers ---
(In reply to Alexandre Demers from comment #16)
> It may be related to general GPU crashes seen other bugs: while bisecting, I
> hit a loop of GPU resets just after logging in until I rebooted.
Refering
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #16 from Alexandre Demers ---
It may be related to general GPU crashes seen other bugs: while bisecting, I
hit a loop of GPU resets just after logging in until I rebooted.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #15 from Alexandre Demers ---
Slowly bisecting: b401796 would be good (haven't had a Packet0 error since
yesterday) and 005f8005 would be bad. Continuing.
--
You are receiving this mail because:
You are the assignee for the bug.
---
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #14 from Andy Furniss ---
(In reply to Alexandre Demers from comment #13)
> (In reply to Jos? Su?rez from comment #12)
> > I compiled 3.17rc7 with the packet0 patch. You can find a dmesg log just
> > above this message.
> >
> > Runni
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #13 from Alexandre Demers ---
(In reply to Jos? Su?rez from comment #12)
> I compiled 3.17rc7 with the packet0 patch. You can find a dmesg log just
> above this message.
>
> Running firefox with RADEON_DUMP_CS=1 didn't produce any du
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #12 from Jos? Su?rez ---
I compiled 3.17rc7 with the packet0 patch. You can find a dmesg log just above
this message.
Running firefox with RADEON_DUMP_CS=1 didn't produce any dump. Is it because I
need the mesa dbg packages (not curr
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #11 from Jos? Su?rez ---
Created attachment 107281
--> https://bugs.freedesktop.org/attachment.cgi?id=107281&action=edit
Dmesg while hitting a packet0
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #10 from Alexandre Demers ---
(In reply to Jos? Su?rez from comment #9)
> I have been trying linux 3.16 with the packet0 patch and after some testing
> I haven't got any Packet0 message in the dmesg log. So I guess it must be
> relate
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #9 from Jos? Su?rez ---
I have been trying linux 3.16 with the packet0 patch and after some testing I
haven't got any Packet0 message in the dmesg log. So I guess it must be related
to the 3.17 rc's. I don't remember getting similar c
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #8 from Christian K?nig ---
(In reply to Michel D?nzer from comment #7)
> So, it looks like the value for the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL
> register and the following PKT3_SET_CONTEXT_REG header were scribbled over
> with the v
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #7 from Michel D?nzer ---
> [25322.031213]0x000b
This value is written to the R_028A3C_VGT_GROUP_VECT_1_FMT_CNTL register.
However, the driver only ever writes 0 to that register, in si_init_config().
> [25322.031214]
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #6 from Alexandre Demers ---
And as a sidenote: aside from the attached CS dump, others are present in
dmesg, but they did not trigger a GPU reset. It seems the last one that I had
encountered and that I attached was just too much for
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #5 from Alexandre Demers ---
Created attachment 107162
--> https://bugs.freedesktop.org/attachment.cgi?id=107162&action=edit
One CS dump
Got this CS dump when using Firefox while playing a few streams in Flash (it
happens often whe
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #4 from Alex Deucher ---
Created attachment 107128
--> https://bugs.freedesktop.org/attachment.cgi?id=107128&action=edit
dump full CS when we hit a packet 0
This kernel patch should make it much easier to debug. When you hit the e
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #3 from Alexandre Demers ---
(In reply to comment #2)
> Can you run the browser with the environment variable RADEON_DUMP_CS=1, and
> attach any command stream dumps that generates on stderr?
I'll run firefox with this env var later
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #2 from Michel D?nzer ---
Can you run the browser with the environment variable RADEON_DUMP_CS=1, and
attach any command stream dumps that generates on stderr?
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freedesktop.org/show_bug.cgi?id=84500
--- Comment #1 from Alexandre Demers ---
Even when UVD is manually disabled, the error still shows in dmesg.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment wa
https://bugs.freedesktop.org/show_bug.cgi?id=84500
Priority: medium
Bug ID: 84500
Assignee: dri-devel at lists.freedesktop.org
Summary: [radeonsi] radeon :01:00.0: Packet0 not allowed!
Severity: normal
Classification: Unclassified
On 15.07.2014 18:16, Esben Stien wrote:
> Michel D?nzer 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 comma
Michel D?nzer writes:
> Looks like userspace is submitting invalid command streams to the kernel.
> So, what are you doing / trying to do when this happens?
Well, I haven't really done anything since I booted the computer 11 days
ago. No games, basically, because I had that freeze I told you abo
Michel D?nzer 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
--
Esben Stien is b0ef at e s a
http://www. s tn m
ir
On 15.07.2014 07:45, Esben Stien wrote:
> I get loads of these in dmesg:
>
> [950253.948694] radeon :04:00.0: Packet0 not allowed!
When doing what?
Any other interesting messages before those?
--
Earthling Michel D?nzer| http://www.amd.com
Libre
I get loads of these in dmesg:
[950253.948694] radeon :04:00.0: Packet0 not allowed!
For debugging purposes:
mesa-git.2014-07-03
llvm-3.4.2
linux-3.16-rc3
xf86-video-ati-7.4.0
xorg-server-1.14.2
glamor-egl-0.6.0
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI
98 matches
Mail list logo
