https://bugs.freedesktop.org/show_bug.cgi?id=98016
Ernst Sjöstrand changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #15 from Alex Deucher ---
Created attachment 127542
--> https://bugs.freedesktop.org/attachment.cgi?id=127542&action=edit
possible fix
Does this patch fix the issue?
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #14 from Alex Deucher ---
(In reply to Ernst Sjöstrand from comment #12)
> Couldn't get anything after modprobe, the computer really dies.
> However updating the firmware fixed it.
>
> Should there be some kind of check or do you co
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #13 from Ernst Sjöstrand ---
I was running the Ubuntu firmware from Xenial, the firmware bundled in Wily
fixed it.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #12 from Ernst Sjöstrand ---
Couldn't get anything after modprobe, the computer really dies.
However updating the firmware fixed it.
Should there be some kind of check or do you consider this fixed?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #11 from Alex Deucher ---
Odd. We haven't seen any failures internally with Fiji and 3 VCE rings
enabled. Can you provide a log of the failure? Try manually loading amdgpu
after boot. E.g., append modprobe.blacklist=amdgpu to the
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #10 from Ernst Sjöstrand ---
Created attachment 127299
--> https://bugs.freedesktop.org/attachment.cgi?id=127299&action=edit
Patch that fixes the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #9 from Ernst Sjöstrand ---
I know what may have been fooling me.
I run sudo make install on Ubuntu. It adds a .old entry in grub.
However that .old entry doesn't have a .old initrd, where the amdgpu kernel
module lives, it shares in
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #8 from Ernst Sjöstrand ---
I have never been able to reproduce the problem with self-compiled 4.8-rc8 from
that workspace so I think my local builds are working at least.
drm/amd/amdgpu: enable clockgating only after late init
sound
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #7 from Andy Furniss ---
(In reply to Ernst Sjöstrand from comment #6)
> Do you think I can get both false positives and false negatives?
> Have tested a bit more but still behaving in a silly way...
I guess your issue not as clear
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #6 from Ernst Sjöstrand ---
Do you think I can get both false positives and false negatives?
Have tested a bit more but still behaving in a silly way...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #5 from Andy Furniss ---
Also the way 4.9-wip changes and things get merged may not make bisecting a
long way back that easy compared to something like mesa.
I notice it's changed again 17 hours ago - it may even work now without you
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #4 from Andy Furniss ---
(In reply to Ernst Sjöstrand from comment #3)
> This seems to be very hard to reproduce. Perhaps it's related to the kernel
> I'm rebooting from or some complex combination.
> Pretty hard to debug when the co
https://bugs.freedesktop.org/show_bug.cgi?id=98016
Ernst Sjöstrand changed:
What|Removed |Added
Summary|[bisected] Fury fails to|[bisected] Fury fails to
14 matches
Mail list logo
