unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Mike Gerwitz <mtg@gnu.org>
Cc: 34176@debbugs.gnu.org
Subject: bug#34176: X200 kernel panic on S3 resume (linux-libre > 4.18.9)
Date: Mon, 28 Jan 2019 04:53:40 -0500	[thread overview]
Message-ID: <874l9tumzf.fsf@dustycloud.org> (raw)
In-Reply-To: <87y376ktcc.fsf@gnu.org>

Mike Gerwitz writes:

> On Wed, Jan 23, 2019 at 01:08:39 -0500, Mike Gerwitz wrote:
>> Right after sending this message, I recalled that I used powertop to do
>> "auto tuning".  Sure enough, one of the lines was this:
>>
>>    Good          Autosuspend for USB device UHCI Host Controller [usb6]
>>
>> By disabling it, it runs this command:
>>
>>   echo on > /sys/bus/usb/devices/usb6/power/control
>>
>> And it resolves my suspend issues on 4.20.3-gnu.
>
> [...]
>
>> This bug can be closed.
>
> Sorry, I take that back.  I could have sworn it did resolve the issue,
> but that does not seem to be the case.
>
> This seems unrelated to powertop; `auto' seems to be the default setting
> of /sys/bus/usb/devices/*/power/control, which is reset on reboot.  In
> any case, setting it to `on' does not solve my suspend issue.
>
> It's not a hardware issue, because earlier kernel versions work just
> fine.
>
> I tried debugging this further, but even on a minimal Guix system, I
> cannot seem to work around the problem.
>
> Any advice, anyone?

Recently I had to switch back to my x200 and found that it wouldn't
suspend anymore, and I wasn't sure why.  Then I somehow screwed up my
system and had to do a reinstall of guix and suspend worked again.  I
wasn't sure why... now I seem to have the answer.  When I reinstalled, I
must not have done so from the latest guix versions.

cwebber@jasmine:~$ uname -a
Linux jasmine 4.17.3-gnu #1 SMP 1 x86_64 GNU/Linux

So I guess if I did a system upgrade, I would have the problem again :)

Note that I am running this x200 with a (somewhat out of date) Libreboot
install.

  parent reply	other threads:[~2019-01-28  9:54 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 [this message]
2019-01-29 12:14     ` Mike Gerwitz
2019-01-31  4:07       ` Mike Gerwitz
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=874l9tumzf.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=34176@debbugs.gnu.org \
    --cc=mtg@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).