all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: 24087@debbugs.gnu.org
Subject: bug#24087: recovery from suspend is broken with recent libreboot + linux-libre 4.7
Date: Thu, 28 Jul 2016 16:04:36 +0000	[thread overview]
Message-ID: <87k2g5da0b.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160728142137.1aeb86fb@scratchpost.org>

Hi,

Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi,
>
>> I know more people than just me are using libreboot here, do you have
>> any problems with suspend and recovery?
>
> I have a X200 and some time after waking up from suspend on the first larger disk access it hangs, losing all the dirty sector payload in the process. This is Guix-specific, the same machine works just fine on Ubuntu.
>
>> Following this[0] thread you can see the problems I have with libreboot
>> latest (latest at the time of flashing) experimental release.
>
>> Can you test (if your system is already libreboot testing, if not wait
>> for either the next release candidate which should happen soon or be
>> ready to unbrick it) and provide logs so that we can fix it in our
>> system?
>
> I don't update the BIOS (I disabled the ability to do so in the chip settings).
>
> Given the ability for an update to brick, I only flashed it once before there was any data on the machine - and I don't plan on doing it again on this machine.
>
> I do actual work on this machine and were it not booting it would be much worse than wakeup not working.
>
> I sometimes non-thinkingly close the laptop lid so it crashes from time to time. So if logs help I can provide those.
>
> Also, dmidecode stopped working some time ago so I can't check which libreboot version I have.
>
> $ sudo dmidecode 
> Password: 
> # dmidecode 2.12
> SMBIOS 2.7 present.
> 8 structures occupying 382 bytes.
> Table at 0xBDAB4020.
>
> /dev/mem: Operation not permitted
> Table is unreachable, sorry.

This seems to be normal for GuixSD.  I don't have much knowledge about
how the kernel and drivers here are packaged and configured, maybe some
/dev/ devices are left out or we have more restriction than 'standard'
systems. With libreboot and Gentoo, or at least with coreboot and Gentoo
dmidecode worked… I think. I know that it works when I flash from ubuntu
livedisk.

Output for me (if not already written in my logs) is this:
# dmidecode 2.12
SMBIOS 2.7 present.
8 structures occupying 386 bytes.
Table at 0x7DAA0020.

/dev/mem: Operation not permitted
Table is unreachable, sorry.


> $ uname -a
> Linux dayas 4.6.4-gnu #1 SMP 1 x86_64 GNU/Linux

-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-07-28 16:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  8:58 bug#24087: recovery from suspend is broken with recent libreboot + linux-libre 4.7 ng0
2016-07-28 12:21 ` Danny Milosavljevic
2016-07-28 16:04   ` ng0 [this message]
2016-07-29 10:51     ` ng0
2016-07-30  4:26   ` Mark H Weaver
2016-07-30  6:24     ` Clément Lassieur
2016-07-30  8:38       ` ng0
2016-07-30 20:38         ` Clément Lassieur
2016-07-31  2:49         ` Mark H Weaver
2016-07-31 20:18       ` Ricardo Wurmus
2016-08-01 14:23     ` ng0
2016-08-08 22:23   ` Danny Milosavljevic
2016-07-31  0:40 ` Danny Milosavljevic
2016-07-31 19:23   ` Vincent Legoll
2016-08-19  7:58 ` ng0
2016-08-22 22:50   ` Clément Lassieur
2017-05-27 15:26     ` Clément Lassieur
2017-05-27 18:38       ` Christopher Allan Webber
2017-05-27 19:30         ` Clément Lassieur
     [not found] ` <handler.24087.B.146963323422208.ack@debbugs.gnu.org>
2016-08-19  8:03   ` bug#24087: Acknowledgement (recovery from suspend is broken with recent libreboot + linux-libre 4.7) ng0
2016-08-22 22:39 ` bug#24087: ng0

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=87k2g5da0b.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=24087@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.