Bug 73314 - Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18'
Summary: Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18'
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-05 22:23 UTC by Eduard Bloch
Modified: 2019-11-19 08:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
General system information (41.18 KB, application/octet-stream)
2014-01-05 22:23 UTC, Eduard Bloch
no flags Details

Description Eduard Bloch 2014-01-05 22:23:02 UTC
Created attachment 91530 [details]
General system information

Hello,

I have a Radeon HD5770 and I cannot use s2ram with Linux kernel 3.13.rc*. It has been working fine for years, currently with kernel 3.12.0. I tried to bisect on the Linus tree and the first commit where it started failing is

# first bad commit: [be51e4a78155ff6c5d9299bf726e86b554e21117] Merge tag 'drm-intel-next-2013-10-18' of git://people.freedesktop.org/~danvet/drm-intel into drm-next

However, the symptoms look slightly different. With that commit, the system hangs on suspend. With later revisions, it reboots after 3-5 seconds. Not sure what makes the difference, maybe it's the new option CONFIG_DPM_WATCHDOG but OTOH I disabled it later and it still keeps rebooting. And I am not sure which kernel module is exactly the troublemaker, I excluded "radeon" from the initramfs list and this seemed to make the difference (suspend worked from initramfs environment) but maybe something else is involved too.

I am attaching some information (messages, pci list, config) which might be useful. If you want me to work with kgdb/kdb, this may take a couple of days until I can get a COM port breakout cable for the mainboard.
Comment 1 Martin Peres 2019-11-19 08:41:42 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/424.


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.