Bug 67722 - RV620 GPU kept resetting with radeon.dpm=1 ([drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).)
Summary: RV620 GPU kept resetting with radeon.dpm=1 ([drm:r600_ib_test] *ERROR* radeon...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-03 19:27 UTC by Daniel
Modified: 2019-11-19 08:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (116.52 KB, text/plain)
2013-08-03 19:27 UTC, Daniel
no flags Details

Description Daniel 2013-08-03 19:27:55 UTC
Created attachment 83593 [details]
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.
Comment 1 Alex Deucher 2013-08-06 13:37:37 UTC
(In reply to comment #0)
> 
> 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.

Are you saying this same problem happens even without dpm enabled?
Comment 2 Daniel 2013-08-06 14:38:46 UTC
No, I mean without dpm enabled all boots are OK. This happens only when I enable dpm, not always, occasionally. Sometimes even after a cold reset, if shutdown by force counts.
Comment 3 Martin Peres 2019-11-19 08:36:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/360.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.