https://bugs.freedesktop.org/show_bug.cgi?id=67002
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #13 from jackdachef at gmail.com ---
I'll give radeon.aspm=0 a try - are there any more things I could test ?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML a
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #12 from jackdachef at gmail.com ---
(In reply to comment #11)
> I had to restart due to some other issue
>
> and it wouldn't "successfully" resume anymore:
>
> the lag/slowdown was there again
>
>
> forcing performance_level to "l
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #13 from jackdac...@gmail.com ---
I'll give radeon.aspm=0 a try - are there any more things I could test ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
dri-
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #12 from jackdac...@gmail.com ---
(In reply to comment #11)
> I had to restart due to some other issue
>
> and it wouldn't "successfully" resume anymore:
>
> the lag/slowdown was there again
>
>
> forcing performance_level to "low"
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #11 from jackdachef at gmail.com ---
I had to restart due to some other issue
and it wouldn't "successfully" resume anymore:
the lag/slowdown was there again
forcing performance_level to "low" or "auto" didn't seem to make a differ
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #10 from jackdachef at gmail.com ---
(In reply to comment #9)
> Maybe unrelated to this bug report, but with today's Linus' master
> (04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue
> left is that I get:
>
> [d
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #9 from Andre Heider ---
Maybe unrelated to this bug report, but with today's Linus' master
(04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue left
is that I get:
[drm:rv770_stop_dpm] *ERROR* Could not force DPM
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #11 from jackdac...@gmail.com ---
I had to restart due to some other issue
and it wouldn't "successfully" resume anymore:
the lag/slowdown was there again
forcing performance_level to "low" or "auto" didn't seem to make a differenc
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #10 from jackdac...@gmail.com ---
(In reply to comment #9)
> Maybe unrelated to this bug report, but with today's Linus' master
> (04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue
> left is that I get:
>
> [drm:
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #8 from jackdachef at gmail.com ---
ok,so the atombios error is fixed now
what would the next step be to gradually fix this ? (so the uvd error after
resume & gpu lock/hang)
switch to gcc 4.7* ? would that make a change ?
the gcc 4.
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #9 from Andre Heider ---
Maybe unrelated to this bug report, but with today's Linus' master
(04012e3076943f17c8cfc77a196701c8f0b8964f) the only suspend/resume issue left
is that I get:
[drm:rv770_stop_dpm] *ERROR* Could not force DPM
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #8 from jackdac...@gmail.com ---
ok,so the atombios error is fixed now
what would the next step be to gradually fix this ? (so the uvd error after
resume & gpu lock/hang)
switch to gcc 4.7* ? would that make a change ?
the gcc 4.8*/
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #7 from jackdachef at gmail.com ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > The atombios messages are due to bug 67043. You can revert the patch
> > > referenced in that bug to fix that.
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #7 from jackdac...@gmail.com ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > The atombios messages are due to bug 67043. You can revert the patch
> > > referenced in that bug to fix that. da
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #6 from Alex Deucher ---
(In reply to comment #5)
> (In reply to comment #4)
> > The atombios messages are due to bug 67043. You can revert the patch
> > referenced in that bug to fix that. danvet supposed has a v2 of that patch
> >
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #5 from jackdachef at gmail.com ---
(In reply to comment #4)
> The atombios messages are due to bug 67043. You can revert the patch
> referenced in that bug to fix that. danvet supposed has a v2 of that patch
> which doesn't break re
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #4 from Alex Deucher ---
The atombios messages are due to bug 67043. You can revert the patch
referenced in that bug to fix that. danvet supposed has a v2 of that patch
which doesn't break resume.
Also, does it work any better if y
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #3 from jackdachef at gmail.com ---
at least according to the kernel logs the atombios error seems to have been
introduced, is new with the new DPM code (running the new firmware both with
old and new driver)
--
You are receiving thi
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #2 from jackdachef at gmail.com ---
(In reply to comment #1)
> Can you retry with current drm-fixes? There has been a fix which might help
> at least for the UVD errors.
sure:
uvd seems to have initialized better/correctly now:
[
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #1 from Michel D?nzer ---
Can you retry with current drm-fixes? There has been a fix which might help at
least for the UVD errors.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #6 from Alex Deucher ---
(In reply to comment #5)
> (In reply to comment #4)
> > The atombios messages are due to bug 67043. You can revert the patch
> > referenced in that bug to fix that. danvet supposed has a v2 of that patch
> >
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #5 from jackdac...@gmail.com ---
(In reply to comment #4)
> The atombios messages are due to bug 67043. You can revert the patch
> referenced in that bug to fix that. danvet supposed has a v2 of that patch
> which doesn't break resum
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #4 from Alex Deucher ---
The atombios messages are due to bug 67043. You can revert the patch
referenced in that bug to fix that. danvet supposed has a v2 of that patch
which doesn't break resume.
Also, does it work any better if y
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #3 from jackdac...@gmail.com ---
at least according to the kernel logs the atombios error seems to have been
introduced, is new with the new DPM code (running the new firmware both with
old and new driver)
--
You are receiving this m
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #2 from jackdac...@gmail.com ---
(In reply to comment #1)
> Can you retry with current drm-fixes? There has been a fix which might help
> at least for the UVD errors.
sure:
uvd seems to have initialized better/correctly now:
[ 33.
https://bugs.freedesktop.org/show_bug.cgi?id=67002
--- Comment #1 from Michel Dänzer ---
Can you retry with current drm-fixes? There has been a fix which might help at
least for the UVD errors.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=67002
jackdachef at gmail.com changed:
What|Removed |Added
Summary|evergreen: after resume |evergreen: after resume
https://bugs.freedesktop.org/show_bug.cgi?id=67002
jackdac...@gmail.com changed:
What|Removed |Added
Summary|evergreen: after resume |evergreen: after resume
29 matches
Mail list logo