https://bugs.freedesktop.org/show_bug.cgi?id=66963
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #297 from Nicola Mori ---
@Mihai I'm using dpm since years on my Mobility 3470 and I only experience
random freezes very rarely. The only thing that's really annoying for me is
this:
https://bugs.freedesktop.org/show_bug.cgi?id=949
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #296 from Mihai Coman ---
Hello,
On a whim I've decided to try radeon.dpm=1 again. I've been running it for the
past couple of days and I haven't had gotten any lockups, and I used to get
them in the first 30 min. The temp. decrease
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #295 from Alex Deucher ---
(In reply to Kyle K from comment #294)
> Hello,
>
> I have been having problem with my HD6870 for some time. I experienced it on
> 4.7/4.8/4.9 kernels (haven't tested earlier). My HD6870 works great out of
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #294 from Kyle K ---
Hello,
I have been having problem with my HD6870 for some time. I experienced it on
4.7/4.8/4.9 kernels (haven't tested earlier). My HD6870 works great out of the
box with DPM enabled, I do not have any issues fo
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #293 from Armin Wehrfritz ---
I have been running a AMD/ATI RV635 with dpm enabled for over a day now without
any issues. I also suspended (to memory) and resumed the system several times
without problems.
My system informations:
Sys
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #292 from Weber K. ---
(In reply to Weber K. from comment #291)
> Hi!
>
> I have HD 6850 and Kernel 4.4.14.
>
> This problem appeared for me when I changed rootflags.
> Solved with rootflags=relatime,lazytime,commit=60 in kernel par
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #291 from Weber K. ---
Hi!
I have HD 6850 and Kernel 4.4.14.
This problem appeared for me when I changed rootflags.
Solved with rootflags=relatime,lazytime,commit=60 in kernel parameters.
HTH
Best regards
Weber Kai
--
You are re
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #290 from Zetok ---
Created attachment 126166
--> https://bugs.freedesktop.org/attachment.cgi?id=126166&action=edit
dmesg with reverted 02376d8282b88f07d0716da6155094c8760b1a13 on 4.6.3
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #289 from Zetok ---
Created attachment 126165
--> https://bugs.freedesktop.org/attachment.cgi?id=126165&action=edit
dmesg without reverted 02376d8282b88f07d0716da6155094c8760b1a13 on 4.6.3
--
You are receiving this mail because:
Y
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Zetok changed:
What|Removed |Added
CC||zetok at openmailbox.org
--- Comment #288 from Z
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #287 from bugs.freedesktop.org at spam.lublink.net ---
The following commands from comment #239 seems to have corrected the issue on
my Raden HD3650 Mobility:
>> echo high > /sys/class/drm/card0/device/power_dpm_force_performance_leve
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Alex Deucher changed:
What|Removed |Added
CC||bugs.freedesktop.org at spam.l
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #285 from Kajzer ---
(In reply to Michel Dänzer from comment #284)
> Those are standard symptoms of a GPU hang and failed reset. Those symptoms
> can be caused by an unlimited number of different problems. Since you're
> getting thos
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #284 from Michel Dänzer ---
(In reply to Kajzer from comment #274)
> (In reply to Michel Dänzer from comment #273)
> > The original description of this report says: "screen becomes blank after
> > grub trying to boot it". Please fil
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #283 from Alex Deucher ---
(In reply to Kajzer from comment #282)
> I'm running now on kernel compiled with first method, if previous bisect was
> indeed done right I don't expect dpm freeze.
>
> Anyway, thanks for the second method,
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #282 from Kajzer ---
(In reply to Alex Deucher from comment #280)
> You don't need to start the bisect again. `git bisect reset` will clean up
> the bisect and reset your current HEAD to where it was when started the
> bisect. At th
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #281 from Kajzer ---
Nice, I'll start compiling now and will run that image for a few days.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scr
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #280 from Alex Deucher ---
(In reply to Kajzer from comment #279)
> (In reply to RafaÅ MiÅecki from comment #277)
> > Don't start the bisect again, just try the commit Michel told about.
> >
> > git reset --hard 77497f2735ad6e29c5
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #279 from Kajzer ---
(In reply to RafaÅ MiÅecki from comment #277)
> Don't start the bisect again, just try the commit Michel told about.
>
> git reset --hard 77497f2735ad6e29c55475e15e9790dbfa2c2ef8
>
> Then compile the kernel,
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #278 from Alex Deucher ---
Be careful. There are two issues here:
1. The general instability of dpm on r6xx (what this bug is about)
2. A potential additional dpm stability issue perhaps introduced by the
bisected commit
Solving the
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #277 from RafaÅ MiÅecki ---
(In reply to Kajzer from comment #276)
> I understand, well I'm glad I'm not alone, it was starting to feel weird, so
> basically I decided to give up today. You gave me strength now to continue :)
I can
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #276 from Kajzer ---
(In reply to Nicola Mori from comment #275)
> You are not the only one, Kajzer. I have exactly the same issue on my RV620,
> but I don't have the possibility to bisect nor I know how to do it. I
> appreciate your
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #275 from Nicola Mori ---
(In reply to Kajzer from comment #274)
> Anyway, it doesn't matter, seems like I'm the only one with this issue, or
> at least the only one reporting it.
You are not the only one, Kajzer. I have exactly the
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #274 from Kajzer ---
(In reply to Michel Dänzer from comment #273)
> The original description of this report says: "screen becomes blank after
> grub trying to boot it". Please file your own report.
When it happens screen freeze for
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #273 from Michel Dänzer ---
(In reply to Kajzer from comment #272)
> Problem manifest itself exactly the same as this dpm problem.
The original description of this report says: "screen becomes blank after grub
trying to boot it". Pl
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #272 from Kajzer ---
(In reply to Michel Dänzer from comment #270)
> Kajzer, I don't think this has anything to do with the original problem
> reported here anymore but should be tracked in a separate report.
I missed this in my pre
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #271 from Kajzer ---
(In reply to Michel Dänzer from comment #270)
> Are you 100% (or at least 99.99...% :) sure that the problem doesn't happen
> without this commit?
No I'm not, that's what bisect gave me, I don't know which one i
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #270 from Michel Dänzer ---
Kajzer, I don't think this has anything to do with the original problem
reported here anymore but should be tracked in a separate report.
(In reply to Kajzer from comment #269)
> # first bad commit: [0237
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #269 from Kajzer ---
Done :
git bisect start '--' 'drivers/gpu/drm/radeon'
# good: [19583ca584d6f574384e17fe7613dfaeadcdc4a6] Linux 3.16
git bisect good 19583ca584d6f574384e17fe7613dfaeadcdc4a6
# bad: [bfe01a5ba2490f299e1d2d5508cbbba
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #268 from Kajzer ---
(In reply to Alex Deucher from comment #266)
> No, you can't skip them. 3.16.0+ just means 3.16.0 plus additional commits
> on top of it. Once of those commits may be a problematic one.
Thanks, I get it now.
I'
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #267 from Ilia Mirkin ---
(In reply to Kajzer from comment #265)
> One question though, if I'm 100% positive that v3.16 is good, should I skip
> bisects (mark them as good) if they end up as 3.16.0+ image after bisect ?
On the bright
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #266 from Alex Deucher ---
(In reply to Kajzer from comment #265)
> Could be the case. Bug is hard to reproduce because it happens only in games
> and at random intervals. And you can't idle it. Sadly I don't have much time
> for gami
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #265 from Kajzer ---
(In reply to Alex Deucher from comment #264)
> (In reply to Kajzer from comment #263)
> > git bisect visualize
> > commit 6101b3ae94b4f266456308824e9ca4eab1235d1a
> > Author: Alex Deucher
> > Date: Tue Aug 19
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #264 from Alex Deucher ---
(In reply to Kajzer from comment #263)
> git bisect visualize
> commit 6101b3ae94b4f266456308824e9ca4eab1235d1a
> Author: Alex Deucher
> Date: Tue Aug 19 11:54:15 2014 -0400
>
> drm/radeon: fix acti
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #263 from Kajzer ---
(In reply to Alex Deucher from comment #251)
> (In reply to Kajzer from comment #250)
> > With kernels 3.17 and 3.18 I have freezes when playing some games, those
> > freezes can happen somewhere between 10 minute
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #262 from Armin Wehrfritz ---
I just stumbled across this bug report, where similar lockups were reported for
different GPUs:
https://bugzilla.kernel.org/show_bug.cgi?id=85421
>From there I understood that the mesa version may have a
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #261 from Armin Wehrfritz ---
I just tested dpm for the radeon RV635 card in my Thinkpad T500 with the kernel
4.0.4-2.g4f5e0d5-desktop x86_64 under OpenSUSE 13.2.
I probably should mention that I have not tested to change
'power_dpm_
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #260 from Guram Savinov ---
I mean that we should try two old powersave methods: profiles and dynamic
frequency switching: https://wiki.archlinux.org/index.php/ATI#Powersaving
I used to use profiles and I didn't have any problems with
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #259 from Maciej Gluszek ---
Sorry, I was wrong after all. After 2 days i got a lockup again and went back
to the old method.
When i don't set DPM at boot GPU is overheating and the fan goes crazy. When
setting performance to somethi
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #258 from Guram Savinov ---
(In reply to Maciej Gluszek from comment #257)
> @Guram Savinov: I also tried setting DPM + high performance for my HD3650
> and it worked but the fan was still running too loud (not overheating just
> loud
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #257 from Maciej Gluszek ---
@Guram Savinov: I also tried setting DPM + high performance for my HD3650 and
it worked but the fan was still running too loud (not overheating just loud).
Then i installed Kernel 4.0, removed "high perfo
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #256 from Guram Savinov ---
What is the progress of this issue?
I have this bug for a long time since I set DPM on for my HD3650(RV635 chip).
My current kernel is 3.13.0-48-generic from Ubuntu.
Few days ago I set this two kernel par
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Maciej Gluszek changed:
What|Removed |Added
CC||info at maciejgluszek.com
--- Comment #
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Alex Deucher changed:
What|Removed |Added
CC||littel.jo at gmail.com
--- Comment #254 f
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Alex Deucher changed:
What|Removed |Added
CC||pavol at klacansky.com
--- Comment #253 f
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #252 from Kajzer ---
(In reply to Alex Deucher from comment #251)
> (In reply to Kajzer from comment #250)
> > With kernels 3.17 and 3.18 I have freezes when playing some games, those
> > freezes can happen somewhere between 10 minute
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #251 from Alex Deucher ---
(In reply to Kajzer from comment #250)
> With kernels 3.17 and 3.18 I have freezes when playing some games, those
> freezes can happen somewhere between 10 minutes and 1 hour.
> Freeze occur only in games.
>
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #250 from Kajzer ---
With kernels 3.17 and 3.18 I have freezes when playing some games, those
freezes can happen somewhere between 10 minutes and 1 hour.
Freeze occur only in games.
With kernel 3.16 everything is normal and there are
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #249 from Kajzer ---
Patch is working fine, had zero issues.
However, it still hangs on boot sometimes, it doesn't actually hang, it looks
like it's crashed for a couple of seconds, monitor flashes on and off, then it
boots but withou
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #248 from Laurento Frittella ---
(In reply to Alex Deucher from comment #247)
> Not until it's tested and it proves to work reliably on all the problematic
> systems here.
Unfortunately I tried your patch on kernel 3.17.1 and it does
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #247 from Alex Deucher ---
(In reply to Mateusz JoÅczyk from comment #246)
> (In reply to Alex Deucher from comment #244)
> > Created attachment 106085 [details] [review] [review]
> > workaround for basic enablement
> >
> > As per f
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #246 from Mateusz Jo?czyk ---
(In reply to Alex Deucher from comment #244)
> Created attachment 106085 [details] [review]
> workaround for basic enablement
>
> As per feedback from the last few comments the attached patch forces the
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #245 from Kajzer ---
(In reply to comment #244)
> Created attachment 106085 [details] [review]
> workaround for basic enablement
>
> As per feedback from the last few comments the attached patch forces the
> performance level to high
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #244 from Alex Deucher ---
Created attachment 106085
--> https://bugs.freedesktop.org/attachment.cgi?id=106085&action=edit
workaround for basic enablement
As per feedback from the last few comments the attached patch forces the
per
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #243 from Kajzer ---
I mean, sure, it's not dynamic and it runs on max, but Ill take it.
It is what it is, on auto it freezes, theres not much I can do about it.
This way I can switch manually from high to low when needed, yeah its a
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #242 from Kajzer ---
(In reply to comment #241)
> (In reply to comment #239)
> > echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
> >
> > echo performance > /sys/class/drm/card0/device/power_dpm_state
>
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #241 from Alex Deucher ---
(In reply to comment #239)
> echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
>
> echo performance > /sys/class/drm/card0/device/power_dpm_state
This is effectively the same as di
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #240 from Kajzer ---
Update: just had a crash on boot, I guess Ill try your options for boot and see
will it happen again.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #239 from Kajzer ---
@Shawn Starr,
I can confirm 100% that there are no freezes anymore with auto->high and
balanced->performance.
I can tell that for sure because I was able to reproduce freeze every time.
With this there were no f
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #238 from Paul Bodenbenner ---
I am pretty sure that the problem which I encounter isn't related to a thermal
problem. At the next hang I will check if I still can connect through ssh for
checking logs.
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #237 from Shawn Starr ---
Can people try the following options:
Boot your kernel with:
radeon.runpm=1 radeon.dpm=1 [ radeon.hard_reset=1 optional one]
Get the correct PCI address from sysfs)
echo high >
/sys/devices/pci:00/000
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #236 from Harald Judt ---
Ok, unfortunately I only thought I was lucky. My X server froze again, but the
machine remained accessible via ssh, so here is the last part of the dmesg:
radeon :01:00.0: ring 0 stalled for more than 10
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #235 from Harald Judt ---
With the latest kernel 3.15.6 my RV635 boots fine and no longer hangs. The only
problems that are still present are when resuming from hibernation. Even there
things are much better now, because most times th
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #234 from Paul Bodenbenner ---
Just want to note:
Still about every 10 time of booting or waking up from suspend an / the hard
freeze occurs with an up-to-date Arch Linux installation.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #233 from Francisco Pina Martins ---
@lockheed:
The frosting screen forced me to do a reboot, since after it happened, X became
unusably slow.
I am using the stable version of mesa: 10.1.3-1
I have used mesa-git in the past (well be
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #232 from lockheed ---
@Francisco,
Thanks for the clarification.
This ?frosting? screne problem ? does it freeze the screen apart from
scrambling, and forces you to reboot?
I found that on 3.13 I was able to use my laptop sometimes f
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #231 from Francisco Pina Martins ---
@lockheed:
During initial testing (linux 3.11-rcX - 3.11.X) I used to have booting
problems.
During 3.12 - 3.13, I had the "frosting" screen problem during usage.
Since 3.14 I am not experiencing a
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #230 from lockheed ---
(In reply to comment #229)
> Just wanted to add that after I started using linux-3.14.x my issues with
> DPM are gone when using my Mobility Radeon 3650 (rv635/M86). Everything is
> just working fine.
> Once aga
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #229 from Francisco Pina Martins ---
Just wanted to add that after I started using linux-3.14.x my issues with DPM
are gone when using my Mobility Radeon 3650 (rv635/M86). Everything is just
working fine.
Once again, thanks for all th
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #228 from sleepforlife ---
I think I got the same problem
kernel 3.14.2-1 on arch linux.
lspci | egrep "VGA|3D|Display"
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV635/M86 [Mobility Radeon HD 3650]
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #227 from Nicola Mori ---
This morning I got my first black screen on boot since the update to kernel
3.14. The subsequent boot went fine. On the journal boot log I noticed that the
first boot hangs just before this line:
apr 22 09:0
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #226 from Kajzer ---
Gotta correct something about what I said regarding Steam and some games not
working with open drivers, just found out what the problem was with that,
problem was patent S3TC, installing very small library libtxc_
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #225 from Kajzer ---
(In reply to comment #219)
> Also, my understanding was that this bug list is for DPM problems in the
> newest mesa. If this is so, then I don't even know why are you in this
> thread in the first place, since yo
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #224 from Alex Deucher ---
(In reply to comment #223)
> Ok, thanks for enlightening me. I had things confused. So this is a kernel
> bug list? I thought it is X-related.
https://bugs.freedesktop.org covers lots of projects including
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #223 from lockheed ---
> It's part of the radeon kernel driver. It doesn't matter what userspace
> drivers (mesa, xf86-video-ati) you use.
Ok, thanks for enlightening me. I had things confused. So this is a kernel bug
list? I though
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #222 from Alex Deucher ---
(In reply to comment #221)
> > Mesa and dpm are unrelated. This bug is about dpm stability on rv6xx asics
> > regardless of what version of the userspace drivers you are using.
>
> So what is DPM dependant
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #221 from lockheed ---
> Mesa and dpm are unrelated. This bug is about dpm stability on rv6xx asics
> regardless of what version of the userspace drivers you are using.
So what is DPM dependant on/part of? xf86-video-ati?
--
You a
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #220 from Alex Deucher ---
(In reply to comment #219)
>
> Also, my understanding was that this bug list is for DPM problems in the
> newest mesa. If this is so, then I don't even know why are you in this
> thread in the first place,
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #219 from lockheed ---
> Yeah, well it's a weird thing this problem, it crashes for you and it
> doesn't crash for me, you can boot every time and I can't boot every time,
> you see performance and features and I don't.
>
> Although,
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #218 from Kajzer ---
(In reply to comment #217)
> Yeah, that's the whole point. Performance and features are already here.
> What is not here is working DPM. As it is now, if crashes profusely on our
> chips.
Yeah, well it's a weird
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #217 from lockheed ---
> However, dpm was still working fine and that's the point of this topic I
> think :)
> Performance and mesa features will come in time I guess. Main thing for me is
> dpm, powersaving.
Yeah, that's the whole
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #216 from Kajzer ---
(In reply to comment #215)
> (In reply to comment #214)
> > On my RV635 things are really great, still not a single crash, DPM working
> > without any issues.
> > Running 24/7 for weeks.
> >
>
> Try mesa 10.1 or
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #215 from lockheed ---
(In reply to comment #214)
> On my RV635 things are really great, still not a single crash, DPM working
> without any issues.
> Running 24/7 for weeks.
>
Try mesa 10.1 or 10.2
I thought that is the whole point
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #214 from Kajzer ---
On my RV635 things are really great, still not a single crash, DPM working
without any issues.
Running 24/7 for weeks.
However, still seeing dark screen on boot sometimes, eventually it's going to
boot and then i
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #213 from Sergey ---
(In reply to comment #212)
> Do other users with RV620 experience
> the same? For what concerns my experience, dpm can be deemed as stable for
> RV620.
I still see the issue. (I use RV620)
Actually for me it is
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #212 from Nicola Mori ---
During the last two weeks I had no problem with dpm on my RV620 with kernel
3.14. I booted every day, sometimes multiple times, and the system never hanged
on boot nor during normal usage. Do other users with
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #211 from lockheed ---
(In reply to comment #210)
> I note, the GPU never recovers, when it attempts to Xorg is basically
> frozen, I can VT switch to console but sometimes switching back to X it
> deadlocks completely.
>
You are luc
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #210 from Shawn Starr ---
It's same for me, I can have several days of stability on my W500 w/ RV636 (HD
3650) and then GPU reset.
I note, the GPU never recovers, when it attempts to Xorg is basically frozen, I
can VT switch to conso
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #209 from lockheed ---
> (In reply to comment #207)
> Hm, that's interesting, I'm using the same driver RV635, card is HD 3650
> Had the system up for 3 days and had no crash, had to reboot for other
> reasons.
> Watched many videos (
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #208 from Kajzer ---
(In reply to comment #207)
> Well, for me nothing changed on RV635. Computer boots perfectly fine, but
> video still crashes on random state dpm changes, sometimes in 10 minutes,
> sometimes in 10 hours after boot
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #207 from lockheed ---
Well, for me nothing changed on RV635. Computer boots perfectly fine, but video
still crashes on random state dpm changes, sometimes in 10 minutes, sometimes
in 10 hours after boot. But always when there is unsa
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #206 from Kajzer ---
With kernel 3.14 things are much better, sometimes it doesn't boot but that's
very rarely, once booted everything works fine, had no crashes at all.
The only problem for me is that I cannot run any game from steam
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #205 from Bryan Quigley ---
1. (In reply to comment #199)
I've reproduced the hang without X, instead using kmscon.
This causes the graphics hang (can still switch back to the original VT and
kill it though): /usr/local/bin/kmscon -
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #204 from Nicola Mori ---
Created attachment 96597
--> https://bugs.freedesktop.org/attachment.cgi?id=96597&action=edit
Xorg.0.log for failed start of X server
@Thierry: understood, I still do not experience any hang but I'll keep
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #203 from Thierry Vignaud ---
(In reply to comment #202)
> With linux 3.14-RC8 things are much better for my RV620 (Mobility HD3470). I
> booted about ten times without any hang, only once I was dumped to tty with
That's just the law
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #202 from Nicola ---
With linux 3.14-RC8 things are much better for my RV620 (Mobility HD3470). I
booted about ten times without any hang, only once I was dumped to tty with X
server refusing to start (unfortunately I lost the log, th
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #201 from Michel D?nzer ---
*** Bug 74420 has been marked as a duplicate of this bug. ***
--
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=66963
Alex Deucher changed:
What|Removed |Added
CC||qwrules at gmail.com
--- Comment #200 fro
https://bugs.freedesktop.org/show_bug.cgi?id=66963
--- Comment #199 from Bryan Quigley ---
Latest kernel (daily build from the 12th) get's me a bit closer:
Instead of booting to a video hang (monitor switch to powersave mode) it now
hangs with the monitor on.
> > Does it hang the entire system a
1 - 100 of 154 matches
Mail list logo