From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Gerwitz Subject: bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9) Date: Wed, 30 Jan 2019 23:07:52 -0500 Message-ID: <87ef8th3l3.fsf@gnu.org> References: <877eevq5i6.fsf@gnu.org> <87y37boqhk.fsf@gnu.org> <87y376ktcc.fsf@gnu.org> <8736pblkyw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:35497) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gp3ex-0001jg-NF for bug-guix@gnu.org; Wed, 30 Jan 2019 23:09:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gp3ew-0000fN-WD for bug-guix@gnu.org; Wed, 30 Jan 2019 23:09:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:52811) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gp3ew-0000fA-Sf for bug-guix@gnu.org; Wed, 30 Jan 2019 23:09:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gp3ew-0001zD-FV for bug-guix@gnu.org; Wed, 30 Jan 2019 23:09:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8736pblkyw.fsf@gnu.org> (Mike Gerwitz's message of "Tue, 29 Jan 2019 07:14:15 -0500") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 34176@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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. =2D-=20 Mike Gerwitz --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJcUnSYAAoJEIyRe39dxRuieKMP/j90cHI9Izy0cIuLRrG/TIt4 6FatkT4mI6LR4d6uALBn66M+hEZrx39dEfmy+MhGVUXrfW+rOlKzB0v7qoQIe7/o 7QHVpthSzO8Hmw9LQ0R5yIxUXp/gH9mz9f6xgOQ3PmFsNmxvlPJi28zj8RWC6CcM YeY33Oi+jlKzC1Fh1hPwHcYJihqCsnecCR4YVxHKMJrBkejlmA0sKTElkhfMMo9r tqe6OZ+BKkuu9oMV58Y0vKmtqDILXaznn9Mus+GirTmmYQFuHE9Yj3x6w+KCgdFm 8RlLX6kuzB+J2tLkd3W5qznBgFfe4eZLkhl43cy4Hi/eQe3BB+Irt5Mo+ZW1Qli+ vDczv1ZMEcnCcTiYAOEQRpJbwiAhLGJK/C8McykocHcQCzNxAfHNJGfn8W6hed6i jBOGjNzM8j+8WwIPPX4qGlw38kY6z7GziNhkcqUf+bTrl0dDfb6ucLhdh2YrA2iS xpMUHTifwotHRu1ARY8H0GDRPrwYph9VQBDzNZVS9TWphXQZNumeLY2mD3f3PJaj g0fEg0fNmEzicAfC4GBhHdaAwEZSetmkOm8JZVZEe2oA8YtPO6aiDsDW0GNPess0 KA+YMQkguMj/M3v5l+o10ymP54sYR7Gxbps1cg3u4AdtlFpFO27zn+rGAtooJUXs Emk/+MEIoROU7fwXzrVo =pr/P -----END PGP SIGNATURE----- --=-=-=--