From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74751] resume from suspend broken with 3.15-rc1 and rc2 kernels
Date: Tue, 29 Apr 2014 07:07:32 +0000 [thread overview]
Message-ID: <bug-74751-2300-zknY67AYqS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-74751-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=74751
Niko Montonen <montonen.niko@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |montonen.niko@gmail.com
--- Comment #10 from Niko Montonen <montonen.niko@gmail.com> ---
I have a Lenovo ThinkPad Edge E325 with the upgraded version of Tasev's APU,
the E450, with the HD6320 Wrestler graphics chipset, and I'm suffering from an
issue that would appear to be the same as this.
I'm currently running 3.14.1 on the machine, and it works just fine, but
3.15-rc1 and 3.15-rc3 both fail to resume from suspend (I haven't tested rc2).
The machine hangs completely (network interfaces do not resume etc.), so I'm
unable to get dmesg after suspend.
I feel it's worth noting that the machine also completely ignores the lid
closing with 3.15-rc3, and I believe there are lots of ACPI changes in 3.15,
which would explain a lot.
Are there notes somewhere on how to get some useful debug info for situations
like this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-29 7:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 16:32 [Bug 74751] New: resume from suspend broken with 3.15-rc1 and rc2 kernels bugzilla-daemon
2014-04-24 16:33 ` [Bug 74751] " bugzilla-daemon
2014-04-24 16:34 ` bugzilla-daemon
2014-04-24 16:34 ` bugzilla-daemon
2014-04-25 13:46 ` bugzilla-daemon
2014-04-25 13:56 ` bugzilla-daemon
2014-04-25 13:58 ` bugzilla-daemon
2014-04-25 18:01 ` bugzilla-daemon
2014-04-25 18:03 ` bugzilla-daemon
2014-04-25 18:04 ` bugzilla-daemon
2014-04-28 14:20 ` bugzilla-daemon
2014-04-29 7:07 ` bugzilla-daemon [this message]
2014-04-29 7:08 ` bugzilla-daemon
2014-04-29 7:08 ` bugzilla-daemon
2014-04-29 8:41 ` bugzilla-daemon
2014-04-29 12:30 ` bugzilla-daemon
2014-04-29 12:31 ` bugzilla-daemon
2014-04-29 12:41 ` bugzilla-daemon
2014-05-05 16:22 ` bugzilla-daemon
2014-05-12 14:25 ` bugzilla-daemon
2014-05-12 14:26 ` bugzilla-daemon
2014-05-13 14:56 ` bugzilla-daemon
2014-05-15 15:17 ` bugzilla-daemon
2014-05-25 18:30 ` bugzilla-daemon
2014-05-27 12:20 ` bugzilla-daemon
2014-05-27 12:22 ` bugzilla-daemon
2014-05-30 8:13 ` bugzilla-daemon
2014-06-01 8:09 ` bugzilla-daemon
2014-06-18 14:59 ` 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-74751-2300-zknY67AYqS@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.