dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66767] atombios stuck in loop for more than 5secs aborting after suspend to ram
Date: Mon, 22 Jul 2013 21:01:43 +0000	[thread overview]
Message-ID: <bug-66767-502-nt3LpWc6Pq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66767-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4528 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=66767

--- Comment #3 from Martin Bednar <serafean@gmail.com> ---
Created attachment 82844
  --> https://bugs.freedesktop.org/attachment.cgi?id=82844&action=edit
dmesg after resume

dmesg output after a resume from suspend to ram. UVD initialization fails.
Output from 3.11-rc2. on a 
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Madison
[Radeon HD 5000M Series]. Only happens if DPM is enabled.

short dmesg version (mainly radeon output after resume) : 
[  134.652348] [drm] PCIE GART of 512M enabled (table at 0x000000000025D000).
[  134.652517] radeon 0000:01:00.0: WB enabled
[  134.652520] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff88011160fc00
[  134.652521] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff88011160fc0c
[  134.653452] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x000000000005c418 and cpu addr 0xffffc9000639c418
[  134.670153] [drm] ring test on 0 succeeded in 1 usecs
[  134.670213] [drm] ring test on 3 succeeded in 1 usecs
[  134.723748] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19
[  134.723750] PM: Device 00:07 failed to resume: error -19
[  134.962587] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  134.965908] ata6: SATA link down (SStatus 0 SControl 300)
[  134.966739] ata2.00: configured for UDMA/100
[  135.142469] sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't
fully claim to support it.
[  135.142506] sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't
fully claim to support it.
[  135.862145] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  136.771646] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  136.781372] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK)
filtered out
[  136.791321] ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK)
filtered out
[  136.791499] ata1.00: configured for UDMA/133
[  136.804977] sd 0:0:0:0: [sda] Starting disk
[  136.887420] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  137.912701] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  138.937981] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  139.963255] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  140.988548] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  142.013843] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  143.039117] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  144.064413] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  145.089696] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[  145.109806] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
[  145.109873] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD
(-1).
[  145.109874] [drm] Enabling audio support
[  145.109933] [drm] ib test on ring 0 succeeded in 0 usecs
[  145.109978] [drm] ib test on ring 3 succeeded in 1 usecs
[  145.121521] switching from power state:
[  145.121522]  ui class: none
[  145.121524]  internal class: boot 
[  145.121525]  caps: video 
[  145.121527]  uvd    vclk: 0 dclk: 0
[  145.121529]          power level 0    sclk: 45000 mclk: 79000 vddc: 950
vddci: 0
[  145.121530]          power level 1    sclk: 45000 mclk: 79000 vddc: 950
vddci: 0
[  145.121531]          power level 2    sclk: 45000 mclk: 79000 vddc: 950
vddci: 0
[  145.121533]  status: c b 
[  145.121533] switching to power state:
[  145.121534]  ui class: performance
[  145.121535]  internal class: none
[  145.121536]  caps: single_disp video 
[  145.121537]  uvd    vclk: 0 dclk: 0
[  145.121538]          power level 0    sclk: 15000 mclk: 15000 vddc: 900
vddci: 0
[  145.121539]          power level 1    sclk: 30000 mclk: 79000 vddc: 950
vddci: 0
[  145.121540]          power level 2    sclk: 45000 mclk: 79000 vddc: 950
vddci: 0
[  145.121541]  status: r 
[  150.307980] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[  150.307982] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
CBE6 (len 67, WS 0, PS 0) @ 0xCC15
[  151.345217] PM: resume of devices complete after 16856.243 msecs

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5478 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-07-22 21:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 11:25 [Bug 66767] New: atombios stuck in loop for more than 5secs aborting after suspend to ram bugzilla-daemon
2013-07-10 11:25 ` [Bug 66767] " bugzilla-daemon
2013-07-10 13:07 ` bugzilla-daemon
2013-07-10 14:01 ` bugzilla-daemon
2013-07-22 21:01 ` bugzilla-daemon [this message]
2013-07-22 21:04 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-66767-502-nt3LpWc6Pq@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox