[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2018-06-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=21452

Adam Jackson  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #11 from Adam Jackson  ---
Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you
continue to experience issues with current releases.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
https://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-23 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452


Stefano Carignano  changed:

   What|Removed |Added

  Attachment #26037|0   |1
is obsolete||




-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-23 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #10 from Stefano Carignano   2009-05-23 
09:44:07 PST ---
(In reply to comment #9)

> Then the lockup appears to be with the the clock or pcie code for you chip.
> 
> What your patch did is to make all of the power management code conditional on
> the ClockGating option.  Effectively disabling power management all together.


So (if I understand correctly) to put it simply power management just doesn't
work on my board, right? If you have any suggestion / thing you'd like me to
try / thing you want to know please tell me, since power management was really
the only thing holding me to the proprietary drivers...


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-22 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #9 from Alex Deucher   2009-05-22 08:32:41 PST ---
(In reply to comment #8)

> Well it might be me but actually rebuilding the driver with those lines
> uncommented and adding in xorg.conf an
> 
> Option "ClockGating" "False"
> 
> line (I had no clock gating options in xorg.conf before) doesn't fix the
> problem, ie. my laptop still hangs. 
> 

Then the lockup appears to be with the the clock or pcie code for you chip.

What your patch did is to make all of the power management code conditional on
the ClockGating option.  Effectively disabling power management all together.

 if (info->pm.clock_gating_enabled)
-   RADEONSetClockGating(pScrn, FALSE);
+  //   RADEONSetClockGating(pScrn, FALSE);
 if (info->pm.force_low_power_enabled || info->pm.dynamic_mode_enabled)
RADEONSetStaticPowerMode(pScrn, POWER_DEFAULT);

the top "if" statement now applies to both the following "if" statement.  the
logic is now:
if (info->pm.clock_gating_enabled)
if (info->pm.force_low_power_enabled || info->pm.dynamic_mode_enabled)
RADEONSetStaticPowerMode(pScrn, POWER_DEFAULT);


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-22 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #8 from Stefano Carignano   2009-05-22 
01:12:34 PST ---

> (In reply to comment #5)

> Removing the "ClockGating" option from your config will also prevent that code
> from being called.
> 


Well it might be me but actually rebuilding the driver with those lines
uncommented and adding in xorg.conf an

Option "ClockGating" "False"

line (I had no clock gating options in xorg.conf before) doesn't fix the
problem, ie. my laptop still hangs. 


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-20 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #7 from Alex Deucher   2009-05-20 10:40:55 PST ---
(In reply to comment #6)
> > 
> > Removing the "ClockGating" option from your config will also prevent that 
> > code
> > from being called.
> > 
> 
> but wouldn't that mean that (in both cases?) power management is not fully
> running on my board? or does ForceLowPowerMode somewhat override/surpasses
> ClockGating's function anyway?
> 

There are 3 options which can be used individually or combined:

1. ClockGating - Enables chips specific power saving features like clock gating
that are handled by the hardware directly.  This doesn't really do much on
r6xx/r7xx boards yet.
2. DynamicPM - Automatically reduces the engine clock and pcie lanes when dpms
has powered down the displays
3. ForceLowPowerMode - Runs the chip at a constant reduced engine clock and
pcie lanes.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-20 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #6 from Stefano Carignano   2009-05-20 
09:04:27 PST ---

> 
> Removing the "ClockGating" option from your config will also prevent that code
> from being called.
> 

but wouldn't that mean that (in both cases?) power management is not fully
running on my board? or does ForceLowPowerMode somewhat override/surpasses
ClockGating's function anyway?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-20 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #5 from Alex Deucher   2009-05-20 07:06:25 PST ---
(In reply to comment #4)
> Created an attachment (id=26037)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=26037) [details]
> my fix attempt at radeon_pm.c
> 

Removing the "ClockGating" option from your config will also prevent that code
from being called.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-20 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #4 from Stefano Carignano   2009-05-20 
06:09:03 PST ---
Created an attachment (id=26037)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=26037)
my fix attempt at radeon_pm.c


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-20 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #3 from Stefano Carignano   2009-05-20 
04:59:36 PST ---
Okay, looking around a bit I found a quick workaround: from the irc log
http://www.radeonhd.org/?page=archive_display&c=radeon&m=4&y=2009&d=2009-4-15
I have read:

tormod: agd5f: ok it helped. now X starts, but the laptop freezes solid when I
switch VT
agd5f: tormod: comment out the RADEONSetClockGating() calls in
RADEONPMEnterVT() and RADEONPMLeaveVT() and RADEONPMFini()
agd5f: in radeon_pm.c
tormod: thanks
agd5f: tormod: I'll commit a fix

I found that those three lines actually were not commented in current git code,
so I commented them and now I can switch back to console / shutdown the system
properly. Whether removing those lines is dangerous (and that's why agd5f
hasn't removed them yet) or it is the right way to do it, I really have no
idea.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-05-15 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #2 from Stefano Carignano   2009-05-15 
03:02:36 PST ---
Little update: upgraded to latest 1.6.2-rc X server and latest git
xf86-video-ati package, linux 2.6.30-rc4. Still getting the same behaviour, now
noticed a bad message in dmesg after trying to shut down X via
ctl-alt-backspace:

[   68.474307] [drm] wait idle failed status : 0x 0x
[   68.596881] [drm] wait idle failed status : 0x 0x
[   68.720096] [drm] wait idle failed status : 0x 0x
[   68.720105] BUG: unable to handle kernel NULL pointer dereference at (null)
[   68.720109] IP: [] radeon_read_ring_rptr+0x26/0x29
[radeon]
[   68.720119] PGD 0
[   68.720121] Oops:  [#1] PREEMPT SMP
[   68.720124] last sysfs file:
/sys/devices/LNXSYSTM:00/device:00/ACPI0003:00/power_supply/ACAD/type
[   68.720127] CPU 1
[   68.720128] Modules linked in: radeon drm ath5k
[   68.720133] Pid: 2328, comm: X Not tainted 2.6.30-rc4 #1 Satellite A300
[   68.720135] RIP: 0010:[]  []
radeon_read_ring_rptr+0x26/0x29 [radeon]
[   68.720142] RSP: 0018:8800be307c80  EFLAGS: 00013246
[   68.720144] RAX: 8800be054980 RBX: 8800bf83d000 RCX:
c20010252000
[   68.720147] RDX: 002c RSI:  RDI:
8800bf83d000
[   68.720149] RBP: 8800bf83e000 R08: 8800bf83e000 R09:
0001
[   68.720151] R10: 8800be0cdd80 R11: 7ff2 R12:
8800bf752900
[   68.720153] R13: 8800bf9a9b00 R14: 0008 R15:
0009
[   68.720156] FS:  7fd047b1c6f0() GS:880001035000()
knlGS:
[   68.720158] CS:  0010 DS:  ES:  CR0: 8005003b
[   68.720160] CR2:  CR3: 00201000 CR4:
06e0
[   68.720162] DR0:  DR1:  DR2:

[   68.720165] DR3:  DR6: 0ff0 DR7:
0400
[   68.720167] Process X (pid: 2328, threadinfo 8800be306000, task
8800bedd2220)
[   68.720169] Stack:
[   68.720170]  a0048834 8800bf83d000 a00561ba
8800bf83d000
[   68.720174]  a004b7e6 8800bd8ea4c0 8800bf83e000
8800bd8ea4c0
[   68.720177]  a0021c60 8800bd8ea4c0 8800bdbf0e40
8800bd8ea4c0
[   68.720181] Call Trace:
[   68.720183]  [] ? radeon_commit_ring+0x44/0x9a [radeon]
[   68.720189]  [] ? r600_do_cp_idle+0xc8/0xd1 [radeon]
[   68.720196]  [] ? radeon_do_release+0x5c/0x1a2 [radeon]
[   68.720209]  [] ? drm_lastclose+0x40/0x294 [drm]
[   68.720222]  [] ? __fput+0xcd/0x16a
[   68.720227]  [] ? filp_close+0x5f/0x6a
[   68.720230]  [] ? need_resched+0x1a/0x23
[   68.720234]  [] ? put_files_struct+0x60/0xbd
[   68.720237]  [] ? do_exit+0x197/0x5fd
[   68.720240]  [] ? do_group_exit+0x67/0x93
[   68.720243]  [] ? get_signal_to_deliver+0x375/0x393
[   68.720247]  [] ? get_pageblock_migratetype+0x17/0x18
[   68.720250]  [] ? do_notify_resume+0x83/0x6d8
[   68.720254]  [] ? _spin_unlock_irq+0x2b/0x39
[   68.720254]  [] ? thread_return+0x3e/0x99
[   68.720254]  [] ? hrtimer_nanosleep+0x9c/0x108
[   68.720254]  [] ? retint_signal+0x3d/0x7f
[   68.720254] Code: 31 c0 c3 90 90 f6 87 d6 03 00 00 08 48 8b 87 10 01 00 00
74 09 89 f6 48 03 70 18 8b 06 c3 c1 ee 02 89 f6 48 c1 e6 02 48 03 70 18 <8b> 06
c3 83 7f 74 00 74 07 31 f6 e9 ca ff ff ff 66 83 bf d4 03
[   68.720254] RIP  [] radeon_read_ring_rptr+0x26/0x29
[radeon]
[   68.720254]  RSP 
[   68.720254] CR2: 
[   68.720316] ---[ end trace 342357252ce6c353 ]---
[   68.720318] Fixing recursive fault but reboot is needed!


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati


[Bug 21452] Hang when switching back to console if the ForceLowPowerMode option is enabled

2009-04-28 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=21452





--- Comment #1 from Stefano Carignano   2009-04-28 
04:56:03 PST ---
Ok, maybe the '[drm] wait idle failed status' lines are not directly related to
the problem: I tried running the X server as root with no wm and I got the very
same behaviour, but I managed to kill -9 the X process (which, I forgot to
mention, takes 100% cpu when it hangs) via ssh, and didn't get these messages.
Even after killing the process though, the laptop screen would remain stuck on
the X screen, with the mouse pointer disappeared. No further output on
Xorg.0.log


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
xorg-driver-ati mailing list
xorg-driver-ati@lists.x.org
http://lists.x.org/mailman/listinfo/xorg-driver-ati