https://bugzilla.kernel.org/show_bug.cgi?id=71891
Mike Diehl (noahwittman0...@gmail.com) changed:
What|Removed |Added
CC||noahwittman0...@gm
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #50 from Weber K. ---
Forgot to mention: And relatime,lazytime,commit=60 in fstab
I believe maybe dpm need some fs information to work well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Weber K. changed:
What|Removed |Added
CC||weberkai at yahoo.com.br
--- Comment #49 from
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #48 from Christian König ---
(In reply to closesrc from comment #47)
> how do I apply the patch, any instructions please? thanks.
You simply don't. This bug is already closed and the fix upstream. No need to
apply anything manually a
https://bugzilla.kernel.org/show_bug.cgi?id=71891
closesrc changed:
What|Removed |Added
CC||bluesinn at outlook.com
--- Comment #47 from c
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #46 from Alex Deucher ---
The original issue reported was fixed. Please file a new bug if you are having
an issue.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
J changed:
What|Removed |Added
CC||joerg.schaible at gmx.de
--- Comment #45 from J ---
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #44 from Dino ---
Solved. Last line before this happened was
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
It works after passing radeon.dpm=0 to boot options.
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Dino changed:
What|Removed |Added
CC||dino.omanovic.15 at gmail.com
--- Comment #43 from
https://bugzilla.kernel.org/show_bug.cgi?id=71891
sdh changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #41 from Christian K?nig ---
(In reply to sdh from comment #40)
> Hi. Do we close this bug report now that I can successfully boot into 3.15
> along with the radeon module?
I think we can close it, but it's your bug report you need to
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #40 from sdh ---
Hi. Do we close this bug report now that I can successfully boot into 3.15
along with the radeon module?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #39 from Christian K?nig ---
(In reply to Howard Chu from comment #38)
> I'm also seeing this UVD not responding on a Trinity laptop - Asus N56DP
> with A10-4600M and discrete GPU. Was working fine on 3.12, fails on 3.13 and
> 3.14. I
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Howard Chu changed:
What|Removed |Added
CC||hyc at highlandsun.com
--- Comment #38 from
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #37 from sdh ---
(In reply to Christian K?nig from comment #32)
> I've pushed the workaround upstream. So you should at least have a booting
> system. Just don't try to use any accelerated video decoding since that
> would crash the bo
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #36 from Alex Deucher ---
(In reply to Dieter N?tzel from comment #35)
> (In reply to Alex Deucher from comment #33)
> > I wonder if UVD uses the reference clock directly, or if it uses xclk. If
> > it uses xclk, they may explain the
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #35 from Dieter N?tzel ---
(In reply to Alex Deucher from comment #33)
> I wonder if UVD uses the reference clock directly, or if it uses xclk. If
> it uses xclk, they may explain the problems. Can you post your dmesg output
> with t
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #34 from Christian K?nig ---
(In reply to Alex Deucher from comment #33)
> I wonder if UVD uses the reference clock directly, or if it uses xclk. If
> it uses xclk, they may explain the problems.
They can be different? Yeah that woul
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #33 from Alex Deucher ---
I wonder if UVD uses the reference clock directly, or if it uses xclk. If it
uses xclk, they may explain the problems. Can you post your dmesg output with
this patch applied?
diff --git a/drivers/gpu/drm/ra
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #32 from Christian K?nig ---
(In reply to sdh from comment #30)
> Hi. Any update on this?
I've pushed the workaround upstream. So you should at least have a booting
system. Just don't try to use any accelerated video decoding since th
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #31 from sdh ---
I just noticed I'm getting the following errors during the sleep and wake up
cycle:
[drm:rv730_stop_dpm] *ERROR* Could not force DPM to low
[drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed
Kernel is
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #30 from sdh ---
Hi. Any update on this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #29 from Alex Deucher ---
(In reply to Yuking from comment #28)
> My video card is HD6850, motherboard is ASUS P8Z68-LE.
>
> System can not boot up with radeon module very often. After powerup, the
> screen always goes blank, no any i
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Yuking changed:
What|Removed |Added
CC||yuking_net at sohu.com
--- Comment #28 from Yuki
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #27 from sdh ---
(In reply to Christian K?nig from comment #25)
> Please provide the content of the registers CG_UPLL_FUNC_CNTL,
> CG_UPLL_FUNC_CNTL_2 and CG_UPLL_FUNC_CNTL_3. E.g. install radeontool and
> execute:
>
> radeonreg regma
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #26 from Dieter N?tzel ---
0x718 0x20010002 (536936450)
0x71c 0x021f2111 (35594513)
0x720 0x102774da (271021274)
Only for 3.15.0-rc2-1-desktop-lower-clocks.
Do you need more? --- Need some sleep, badly!
Cheers, Dieter.
--
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #25 from Christian K?nig ---
Thanks for testing this Dieter, that actually saved me quite some time.
The formular for the clock is (fb_div*ref_clock)/(fb_factor*post_div).
fb_factor is a fixed value comming from the hardware design (
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Dieter N?tzel changed:
What|Removed |Added
CC||Dieter at nuetzel-hh.de
--- Comment #24 f
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #23 from sdh ---
(In reply to Christian K?nig from comment #22)
> Possible fix v2.
> Meanwhile please test the attached patch.
> It won't fix the issue, but might at least allow your system to boot.
Yes indeed, thank you. Successfully
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Christian K?nig changed:
What|Removed |Added
Attachment #131871|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #21 from Christian K?nig ---
(In reply to sdh from comment #19)
> Anything I can do to help debug this?
Well, do you have some experience with kernel hacking?
The problem is somewhere in rv770_set_uvd_clocks found in the kernel sourc
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Ciel Avenir changed:
What|Removed |Added
CC||cielartisan at gmail.com
--- Comment #20 fr
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #19 from sdh ---
Anything I can do to help debug this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #18 from Christian K?nig ---
I did got your original message, I just didn't had time to look into it.
There must be something wrong with the clock settings for your system, I just
don't know what it is.
--
You are receiving this mai
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #17 from sdh ---
ping again. I'm wondering whether you're very busy, or this email is getting
buried in your inbox.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #16 from sdh ---
ping.
I guess the above response got lost in the huge amount of mails you must be
receiving :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #15 from sdh ---
Thanks, that helped :)
Doing a 'modprobe radeon' after booting up gives the following errors:
radeon :01:00.0: GPU lockup CP stall for more than 1msec
radeon :01:00.0: GPU lockup (waiting for 0x000
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #14 from Christian K?nig ---
(In reply to sdh from comment #13)
> Can you suggest me a good way to debug this and read the logs? Everything
> hangs up, so I do a hard reboot and start with nomodeset parameter to see
> the logs. Is ther
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #13 from sdh ---
Can you suggest me a good way to debug this and read the logs? Everything hangs
up, so I do a hard reboot and start with nomodeset parameter to see the logs.
Is there a better way to do this?
--
You are receiving thi
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #12 from Christian K?nig ---
(In reply to sdh from comment #11)
> Nopes. It makes the UVD errors go away, but the boot still gets stuck at the
> same point. Everything hangs up, requiring me to do a hard reboot.
Well that the UVD erro
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #11 from sdh ---
Nopes. It makes the UVD errors go away, but the boot still gets stuck at the
same point. Everything hangs up, requiring me to do a hard reboot.
Weirdly, I could not find any errors in either syslog or Xorg, which make
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #10 from Christian K?nig ---
Created attachment 131871
--> https://bugzilla.kernel.org/attachment.cgi?id=131871&action=edit
Possible fix.
Please try the attached patch.
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #9 from sdh ---
Hi,
Any update on this? Is there any other information required to fix the bug?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #8 from sdh ---
I suppose you mean these firmwares:
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/radeon
The Arch Linux package is built from the latest commit, and is installed on my
laptop.
% modinfo
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Christian K?nig changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #6 from sdh ---
s/Is enough/Is it enough/
Sorry for the typo, meant it as a question.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #5 from sdh ---
Finally got around to doing this. And the result:
ec5891fbe1b078b191b25a13a2cc40b58fb7a693 is the first bad commit
commit ec5891fbe1b078b191b25a13a2cc40b58fb7a693
Author: Christian K?nig
Date: Mon Apr 8 12:41:36 201
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #4 from sdh ---
Have never done it before. Will attempt to do it when I have some free time and
report back :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #3 from Alex Deucher ---
if 3.12 works, can you use git to bisect?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #2 from sdh ---
Booting with 3.12 kernel gives no such error. Using 3.13, booting from the Arch
install iso gives the above errors.
The only difference with radeon.dpm=0 is that the line
"rv770_restrict_performance_levels_before_switc
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
51 matches
Mail list logo
