From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi 4 stability dependent in RAM
Date: Thu, 19 Nov 2020 00:27:27 -0800 [thread overview]
Message-ID: <CAJSxfmKhuNA1VoyDwsx7oxO6k+UMevH84-D2TkSnGOXg0L2dEw@mail.gmail.com> (raw)
In-Reply-To: <861191CA-7AB2-4BF6-BD47-FFC89414C9A4@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
I've been using an RPI4B with 4GB as my main term for several months. It
pxe boots (no SD card) and I leave the session on, but run screenlock to
guard against cat walk (pun?). It has rebooted once, but I'm pretty sure it
was due to power fluctuations (didn't see it happen). I built the kernel on
May 31st, with the latest patches at the time.
On Wed, Nov 18, 2020 at 3:17 PM Anthony Sorace <a@9srv.net> wrote:
> > Richard asked:
> > The pi4 is very sensitive to power supply voltage. Are you using
> > an "official" pi4 power supply (5.2v)?
>
> Yes; same power supply on the 4GB and 1GB models. That is, same exact
> unit, on the same outlet. I had all sorts of problems with my first
> several Pi
> and know better than to mess around with that now.
>
> > The pi4 flashes the red power LED to indicate undervoltage, so you can
> look
> > out for that if you don't have a monitor to see the lightning bolt on.
>
> Is this lightning bolt a hardware feature? Like, it overlays it on the
> display,
> even on Plan 9? I've never seen it. I'll watch for the power LED indicator.
>
> I've also got the bad behavior on two different 1GB models, so it's at
> least
> pretty unlikely to be a hardware issue.
>
> Then this went other places. Is anyone else running a 4GB Pi 4 with
> Richard's
> latest kernel, successfully? Terminal or cpu?
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-Me8b421ac4f9f1b8cff689226
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2939 bytes --]
next prev parent reply other threads:[~2020-11-19 8:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 0:30 a
2020-11-14 0:56 ` a
2020-11-14 9:35 ` Richard Miller
2020-11-14 11:14 ` Steve Simon
2020-11-14 11:24 ` Richard Miller
2020-11-14 14:48 ` hiro
2020-11-14 15:05 ` Richard Miller
2020-11-14 15:12 ` hiro
2020-11-14 16:58 ` Bakul Shah
2020-11-14 18:12 ` hiro
2020-11-22 10:48 ` hiro
2020-11-23 22:46 ` [9fans] node-red Bakul Shah
2020-11-14 15:29 ` [9fans] Raspberry Pi 4 stability dependent in RAM Richard Miller
2020-11-14 16:15 ` hiro
2020-11-14 11:24 ` Richard Miller
2020-11-18 23:13 ` Anthony Sorace
2020-11-19 0:15 ` Thaddeus Woskowiak
2020-11-19 7:37 ` Steve Simon
2020-11-19 8:27 ` Skip Tavakkolian [this message]
2020-11-20 23:05 ` Stuart Morrow
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=CAJSxfmKhuNA1VoyDwsx7oxO6k+UMevH84-D2TkSnGOXg0L2dEw@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).