https://bugs.freedesktop.org/show_bug.cgi?id=67790
Priority: medium
Bug ID: 67790
Assignee: dri-devel(a)lists.freedesktop.org
Summary: error message on suspend: *ERROR* Could not force DPM
to low
Severity: normal
Classification: Unclassified
OS: All
Reporter: johannes.hirte(a)fem.tu-ilmenau.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
…
[View More]Component: DRM/Radeon
Product: DRI
On suspend dmesg shows the following error message:
[ 236.137036] PM: Syncing filesystems ... done.
[ 236.673588] Freezing user space processes ... (elapsed 0.007 seconds) done.
[ 236.680901] Freezing remaining freezable tasks ... (elapsed 0.000 seconds)
done.
[ 236.681975] Suspending console(s) (use no_console_suspend to debug)
[ 236.693223] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 236.695019] sd 0:0:0:0: [sda] Stopping disk
[ 237.336598] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low.
[ 239.009616] radeon 0000:01:00.0: power state changed by ACPI to D3cold
[ 239.009696] PM: suspend of devices complete after 2315.934 msecs
[ 239.009861] PM: late suspend of devices complete after 0.162 msecs
I've not seen any problems, suspend and resume worked correct so far.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=67722
Priority: medium
Bug ID: 67722
Assignee: dri-devel(a)lists.freedesktop.org
Summary: RV620 GPU kept resetting with radeon.dpm=1
([drm:r600_ib_test] *ERROR* radeon: fence wait failed
(-35).)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: daisuke14164(a)gmail.com
Hardware: x86-64 (AMD64)
…
[View More] Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
Created attachment 83593
--> https://bugs.freedesktop.org/attachment.cgi?id=83593&action=edit
dmesg
Graphics: ATI RV620/M82 [Mobility Radeon HD 3450/3470]
Kernel: latest git build of drm-fixes-3.11
Mesa: latest git build
OS: Arch
ARCH: x86_64
DE: KDE 4.11 RC
https://bugs.freedesktop.org/show_bug.cgi?id=66963 was fixed but here comes new
problem. When booting into X(KDE splash screen), it seemed to freeze(even after
a cold reset), but I managed to switch to tty and get the dmesg. Xorg log is
fine. In the end I have to shutdown.
This situation seems to be more often than normal booting.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=67178
Priority: medium
Bug ID: 67178
Assignee: dri-devel(a)lists.freedesktop.org
Summary: discrete radeon HD 6400M/7400M intense heating even
though it's "off"
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: tpo_deb(a)sourcepole.ch
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
…
[View More] Component: DRM/Radeon
Product: DRI
kernel 3.11-rc1 (also tested with 3.10 from Debian, 3.7, 3,2)
# lspci -vnnn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd
Generation Core Processor Family Integrated Graphics Controller
[8086:0116] (rev 09) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff)
(prog-if ff)
This is a HP Pavillon dv7 6130ez
Sometimes, at random, the radeon card goes into full heat production mode. This
seems to occur a while (a few minutes?) after wakeup from resume, however I'm
not sure about that. Suspending and resuming the laptop a few times (1 <= x <=
~4) seems to calm the card down again.
Power consumption according to powertop goes from ~14W up to ~50W. This happens
even though the card should be in theory switched off. Aka:
# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS: :Off:0000:01:00.0
# echo IGD > /sys/kernel/debug/vgaswitcheroo/switch
# echo OFF > /sys/kernel/debug/vgaswitcheroo/switch
doesn't seem to have no effect whatsoever.
It *seems* that setting "radeon.dpm=1" kernel boot options and then:
# echo "battery" > /sys/class/drm/card$no/device/power_dpm_state
puts the card in an "active" but "relatively low" power consumption mode. It is
then using about 20W (instead of the "normal" ~14W) so it's continuously faning
out slightly warm air. And it "seems that when the card is running in this
mode, then it won't get so often, or ever (I'm not very sure) into the berserk
heating mode.
The lowest observed power consumption of the laptop is ~7W. It'd be very nice
if it'd be possible to shut the card down electrically via software and stay in
this 7W mode.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=67169
Priority: medium
Bug ID: 67169
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Black screen after waking from sleep
Severity: normal
Classification: Unclassified
OS: All
Reporter: marco(a)scannadinari.co.uk
Hardware: Other
Status: NEW
Version: 9.1
Component: Drivers/DRI/Radeon
Product: Mesa
Created …
[View More]attachment 82813
--> https://bugs.freedesktop.org/attachment.cgi?id=82813&action=edit
xorg log
Waking the screen from sleep wakes it but all i get is a black screen. I am
able to type and change ttys, etc, but after `systemctl restart gdm` as root
the screen gets 'No signal'.
The setting that causes this is GNOME's 'Blank screen' option in
Settings>Power>Blank Screen
I can confirm that AMD's proprietary drivers fix this.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=67002
Priority: medium
Bug ID: 67002
Assignee: dri-devel(a)lists.freedesktop.org
Summary: evergreen: after resume from suspend-to-ram operation
is really slow with the latest DPM changes
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: jackdachef(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
…
[View More] Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Using the drm-code from drm-fixes-3.11 branch
(http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11) against a 3.10
final kernel as explained in following post
(http://phoronix.com/forums/showthread.php?82357-drm-fixes-3-11-with-3-10-st…)
the card used is a HD5850, evergreen; ~amd64 Gentoo Linux, Intel Core i7 860,
gcc 4.8.1, 2.17
I tested suspend-to-ram which in a prior state of drm-next would lock up the
box (so much progress has been made - yay ! :) ):
via following command:
pm-suspend --quirk-dpms-on --quirk-s3-mode --quirk-vbe-post --quirk-vga-mode3
launched from VT1 (no X running)
first things noticable:
it takes longer (compared to the non-DPM driver) to turn off the computer so I
first thought that it had hardlocked (fans were still spinning, screen turned
off, harddisks +/- off - after some time the box went to suspend/sleep)
it also takes longer to resume and for the screen to turn on
following behavior is observable after the resume from suspend-to-ram:
dmesg shows:
[ 178.031724] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 178.430546] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control:
Rx
[ 178.430652] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 179.052821] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 180.073918] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 181.095014] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 182.116110] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 182.120733] ata1: link is slow to respond, please be patient (ready=0)
[ 182.122735] ata3: link is slow to respond, please be patient (ready=0)
[ 182.128740] ata5: link is slow to respond, please be patient (ready=0)
[ 182.130763] ata6: link is slow to respond, please be patient (ready=0)
[ 183.137207] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 184.158303] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 185.179399] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 186.200496] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 186.817477] ata1: COMRESET failed (errno=-16)
[ 186.819524] ata3: COMRESET failed (errno=-16)
[ 186.825487] ata5: COMRESET failed (errno=-16)
[ 186.827492] ata6: COMRESET failed (errno=-16)
[ 187.221593] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 187.241615] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[ 187.241618] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).
[ 187.241650] [drm] ib test on ring 0 succeeded in 0 usecs
[ 187.241683] [drm] ib test on ring 3 succeeded in 1 usecs
[ 187.246731] switching from power state:
[ 187.246732] ui class: none
[ 187.246733] internal class: boot
[ 187.246733] caps: video
[ 187.246734] uvd vclk: 0 dclk: 0
[ 187.246734] power level 0 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246735] power level 1 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246735] power level 2 sclk: 40000 mclk: 90000 vddc: 1000
vddci: 0
[ 187.246736] status: c b
[ 187.246736] switching to power state:
[ 187.246737] ui class: performance
[ 187.246737] internal class: none
[ 187.246738] caps: single_disp video
[ 187.246738] uvd vclk: 0 dclk: 0
[ 187.246739] power level 0 sclk: 15700 mclk: 30000 vddc: 950
vddci: 1100
[ 187.246739] power level 1 sclk: 55000 mclk: 90000 vddc: 1038
vddci: 1100
[ 187.246740] power level 2 sclk: 72500 mclk: 100000 vddc: 1088
vddci: 1100
[ 187.246740] status: r
[ 188.350006] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 188.380064] ata3.00: configured for UDMA/133
[ 188.380117] sd 2:0:0:0: [sdb] Starting disk
[ 188.511188] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 188.523242] ata6.00: configured for UDMA/133
[ 188.523276] sd 5:0:0:0: [sdd] Starting disk
[ 190.500189] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 190.513376] ata5.00: configured for UDMA/133
[ 190.513455] sd 4:0:0:0: [sdc] Starting disk
[ 191.462213] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 191.506493] ata1.00: configured for UDMA/133
[ 191.506573] sd 0:0:0:0: [sda] Starting disk
[ 192.356977] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 192.356978] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D3DE (len 55, WS 0, PS 0) @ 0xD401
[ 192.376632] PM: resume of devices complete after 15600.251 msecs
so suspend & resume works but with caveats - now wanted to see how X is
running:
launched up lightdm & logged into xfce4.10 :
compiz-fusion (0.8*)/compositing is very very slow: e.g. when grabbing a window
at the top with left mouse button and trying to move it - it moves only for
several millimeters on screen (22'' screen with 1920x1080 resolution) - thus
unusable
when switching to xfwm4 (running Xfce4.10) moving windows around is somewhat
acceptable - appears even fluid, launching up chromium and switching between
tabs via ctrl + pgup/pgdown is noticably laggy
launching glxgears via gnome-terminal - it seemingly looks ok (gears smoothly
turning) [FPS locked to around 60]
running glxgears via: R600_LLVM=0 vblank_mode=0 glxgears
there's noticable, "micro"-stuttering and the FPS is around 260-290 if I recall
correctly
echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level
or
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
doesn't make a difference - also FPS is significantly lower compared to
"normal" operation (around 10x faster, e.g. 2900-3600 FPS with the non-DPM and
"high" profile)
next step was launching gnome-terminal from the below panel, then after sudo su
-> dmesg
and wanted to do further tests (e.g. sensors output)
-> X crashed
[ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199
last fence id 0x0000000000000198)
X (or lightdm) couldn't be launched after that anymore, VT output was still
shown - so I restarted via shutdown -r now
hope that information helps in tracking down this issue
I really love this new driver - now only operation after resume needs to work
also, since I used it quite a lot :) (it does work with the non-DPM)
similar message and behavior was seen on july 3rd/4th after several hours of
operation & uptime (no suspend and resume):
[ 973.217246] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[ 973.217254] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000199
last fence id 0x0000000000000198)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=66963
Priority: medium
Bug ID: 66963
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600: linux 3.11RC1 isn't booting with radeon.dpm=1
option in grub
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: ken20001(a)ukr.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
…
[View More]Component: DRM/Radeon
Product: DRI
Linux 3.11RC1 isnt' booting with radeon.dpm=1 option in grub: screen becomes
blank after grub trying to boot it. Without radeon.dpm=1 option system boots
well. So, it seems, DPM isn't working.
Graphics: Radeon HD2600 XT
Linux: 3.11RC1
OS: Kubuntu 13.04
KDE: 4.11 beta2
Please, ask me for any additional info needed to help fix this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=65091
Priority: medium
Bug ID: 65091
Assignee: dri-devel(a)lists.freedesktop.org
Summary: power_profile not working for HD5650
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: nevehanter(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
I …
[View More]have HD5650 with Intel i3 Ironlake (1-Gen) switcheable graphics.
My problem is that changing power_profile in radeon gives me nothing.
I have enabled KMS, use vgaswitcheroo to disable i915 and switch X to radeon.
Changing anything in radeon params at kernel parameters gives me also nothing.
It always stay at the same clocks:
For auto/low/mid/high profile
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 100000 kHz
current engine clock: 99990 kHz
default memory clock: 157000 kHz
current memory clock: 156930 kHz
voltage: 1000 mV
PCIE lanes: 16
And it should be engine: 550000 kHz and memory 800000 kHz ( values taken from
windows )
I wanted to know if you could provide fix for it, and I'm open in helping with
providing every information.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=65068
Priority: medium
Bug ID: 65068
Assignee: dri-devel(a)lists.freedesktop.org
Summary: AtomBIOS stuck after suspend/resume cycle whilst GPU
turned off
Severity: normal
Classification: Unclassified
OS: All
Reporter: austin.lund(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/…
[View More]Radeon
Product: DRI
Created attachment 79884
--> https://bugs.freedesktop.org/attachment.cgi?id=79884&action=edit
dmesg output when trying to switch back to radeon gpu.
I have two GPUs in my system:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Whistler [Radeon HD 6600M/6700M/7600M Series]
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
This is a macbookpro8,2 and hence the gmuxer is controlled by the apple-gmux
driver.
If I suspend the system to ram whilst on the integrated gpu (i.e. the intel
gpu), then after resume switch back to the radeon, I get a GPU hang.
I've attached the dmesg output that I get when I try this.
I'm using linux 3.10-rc3. I don't have X running when doing this
(vgaswitcheroo won't allow this).
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]