[Bug 73314] New: Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18'

* [Bug 73314] New: Juniper: fails to suspend after merging tag 'drm-intel-next-2013-10-18'
@ 2014-01-05 22:23 bugzilla-daemon
  2019-11-19  8:41 ` [Bug 73314] " bugzilla-daemon
  0 siblings, 1 reply; 2+ messages in thread
From: bugzilla-daemon @ 2014-01-05 22:23 UTC (permalink / raw)
  To: dri-devel

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

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

          Priority: medium
            Bug ID: 73314
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Juniper: fails to suspend after merging tag
                    'drm-intel-next-2013-10-18'
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: blade@debian.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Created attachment 91530
  --> https://bugs.freedesktop.org/attachment.cgi?id=91530&action=edit
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.

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

[-- Attachment #1.2: Type: text/html, Size: 3326 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

^ permalink raw reply	[flat|nested] 2+ messages in thread