From: Mike Gerwitz <mtg@gnu.org>
To: 34176@debbugs.gnu.org
Subject: bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9)
Date: Wed, 30 Jan 2019 23:07:52 -0500 [thread overview]
Message-ID: <87ef8th3l3.fsf@gnu.org> (raw)
In-Reply-To: <8736pblkyw.fsf@gnu.org> (Mike Gerwitz's message of "Tue, 29 Jan 2019 07:14:15 -0500")
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Tue, Jan 29, 2019 at 07:14:15 -0500, Mike Gerwitz wrote:
> reopen 34176
> thanks
I guess I don't have permission to do this, since nothing happened. Can
someone do this for me?
Alternatively, if this seems outside the scope of something we'd want to
track in Guix, just leave it closed.
> On Sun, Jan 27, 2019 at 10:34:11 -0500, Mike Gerwitz wrote:
> I have to go to work shortly, so I'll play around with it a little more
> later tonight and see if e.g. plugging in my Nitrokey (actually using
> the USB hub) had an effect. With that said, I use my Nitrokey every day
> (but I did _not_ use it most of the times I was trying to debug this
> issue) and I thought I've had suspend issues with it before. I guess
> we'll see.
I was not able to figure it out with the time I had available to spend
on this the past couple of nights. It's once again locking up when
resuming, and I cannot get it to resume correctly.
--
Mike Gerwitz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2019-01-31 4:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 5:58 bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9) Mike Gerwitz
2019-01-23 6:08 ` Mike Gerwitz
2019-01-23 9:55 ` Efraim Flashner
2019-01-23 9:56 ` Gábor Boskovits
2019-01-27 15:34 ` Mike Gerwitz
2019-01-28 7:12 ` Chris Marusich
2019-01-28 9:53 ` Christopher Lemmer Webber
2019-01-29 12:14 ` Mike Gerwitz
2019-01-31 4:07 ` Mike Gerwitz [this message]
2019-01-31 7:02 ` Mark H Weaver
2019-02-01 3:56 ` Mike Gerwitz
2019-05-12 14:16 ` Mike Gerwitz
2019-05-16 0:57 ` Mike Gerwitz
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef8th3l3.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=34176@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).