From: Stefan Schmiedl <s@xss.de>
To: jdm <jdm@jdm.myzen.co.uk>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Black Screen of Death
Date: Fri, 19 Jul 2019 08:48:26 +0200 [thread overview]
Message-ID: <1943989105.20190719084826@xss.de> (raw)
In-Reply-To: <20190719062856.5ffe5b44@jdm.myzen.co.uk>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
"jdm" <jdm@jdm.myzen.co.uk>, 19.07.2019, 07:28:
> I have updated firmware line in kernel as this now includes a few extra
> lines so not loading all of the available firmware.
> Thanks for advice and I'll see how I get on.
Can you trigger the crash by (over-)exerting the system?
A few years ago I had a box with 4x4GB of RAM and a similar
crash only occurred during heavy load, say recompiling gcc
with -j 9. Turned out that _two_ of the four RAM modules were
faulty. And statistical evidence led me to the conclusion
that those were only used when the first 8GB were exhausted.
If you can spare the box for a day, boot into memtest and
let it run for at least 12 hours.
s.
[-- Attachment #2: Type: text/html, Size: 1063 bytes --]
next prev parent reply other threads:[~2019-07-19 6:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:29 [gentoo-user] Black Screen of Death jdm
2019-07-18 23:30 ` gentoo-user
2019-07-19 0:59 ` Adam Carter
2019-07-19 5:09 ` jdm
2019-07-19 5:28 ` jdm
2019-07-19 6:48 ` Stefan Schmiedl [this message]
2019-08-01 0:02 ` Bill Kenworthy
2019-07-19 10:59 ` Mick
[not found] ` <20190718233058.01FAEE07AE@pigeon.gentoo.org>
2019-07-19 11:52 ` Alan Mackenzie
2019-07-19 12:27 ` Rich Freeman
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 5:08 Rick Harris
2009-01-15 18:49 ` John
2009-01-14 18:58 John
2009-01-14 19:41 ` Willie Wong
2009-01-14 21:02 ` John
2009-01-14 22:13 ` John
2009-01-14 22:26 ` Dale
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=1943989105.20190719084826@xss.de \
--to=s@xss.de \
--cc=gentoo-user@lists.gentoo.org \
--cc=jdm@jdm.myzen.co.uk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox