From: Danny Milosavljevic <dannym@scratchpost.org>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: 24087@debbugs.gnu.org
Subject: bug#24087: recovery from suspend is broken with recent libreboot + linux-libre 4.7
Date: Sun, 31 Jul 2016 02:40:17 +0200 [thread overview]
Message-ID: <20160731024017.1cee9a8e@scratchpost.org> (raw)
In-Reply-To: <87r3af4fux.fsf@we.make.ritual.n0.is>
My machine just crashed with a Linux oops (with blinking caps lock and everything) - the second time it did that, ever.
I have crashkernel enabled - but unfortunately the kernel that Guix installed didn't have all the flags enabled that I need to be able to generate the crashdump.
See http://dedoimedo.com/computers/kdump.html#mozTocId967714
Also, I have 2 CPUs and kdump only supports 1 CPU :(
What's the standard way to recover just the oops text? I didn't see any text.
next prev parent reply other threads:[~2016-07-31 0:41 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
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 [this message]
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=20160731024017.1cee9a8e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=24087@debbugs.gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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.