public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Wed, 4 Sep 2024 06:37:18 -0500	[thread overview]
Message-ID: <2c2bf733-5e5b-7efa-5933-e9bcde133510@gmail.com> (raw)
In-Reply-To: <e199875e-bd57-0e91-5cf0-af770cd55fcc@gmail.com>

Dale wrote:
>
> Here's the update.  Grant and a couple others were right.  So was some
> of my search results, which varied widely.  Shortly after my reply to
> Grant, I shutdown the new rig.  I set my old rig back up so I can watch
> TV.  Then I booted the ever handy Ventoy USB stick and ran the memtest
> included with the Gentoo Live image.  Within minutes, rut roh.  :-(  The
> middle section of the test screen went red.  It spit out a bunch of "f"
> characters.  I took a pic but haven't downloaded it yet but I figure it
> has been seen before.  Pic is to get new memory stick.  Figure I need to
> prove it is bad.
>
> Anyway, I removed one stick of memory, it still failed.  Then I switched
> sticks.  That one passed the test with no errors.  I put the original
> stick back in but in another slot.  Within minutes, it failed the same
> as before.  So, I put the good stick in and booted into the Gentoo Live
> image.  I mounted my OS, chrooted in and did a emerge -ae @system.  The
> bad stick is on my desk.  It looks sad.  Like me. 
>
> Once the emerge was done, I booted back into the OS itself.  Everything
> seems to be working but I'm back down to 32GBs of memory.  I'm trying to
> start a emerge -ae world but got to start a new thread first.  It claims
> some weird things that sounds weird but I don't think it is related to
> the memory issue. 
>
> I wonder how much fun getting this memory replaced is going to be.  o_O 
>
> Dale
>
> :-)  :-) 
>


I forgot to ask, is there anything else that bad memory could affect? 
I'm doing the emerge -e world to make sure no programs were affected but
what about other stuff?  Could this affect hard drive data for example? 
Just the things I created while stick was bad I'd hope. 

Just wondering what I should look out for here. 

Dale

:-)  :-) 


  parent reply	other threads:[~2024-09-04 11:37 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04  0:12 ` [gentoo-user] " Grant Edwards
2024-09-04  0:39   ` Dale
2024-09-04  4:16     ` corbin bird
2024-09-06 20:15     ` Dale
2024-09-06 23:17       ` Michael
2024-09-07  3:02         ` Dale
2024-09-07 22:12     ` Wols Lists
2024-09-08  1:59       ` Dale
2024-09-08 13:32         ` Michael
2024-09-08  9:15       ` Michael
2024-09-08 20:19         ` Wol
2024-09-04  7:53   ` Raffaele Belardi
2024-09-04  4:26 ` [gentoo-user] " Eli Schwartz
2024-09-04 10:48 ` [gentoo-user] " Dale
2024-09-04 11:05   ` Frank Steinmetzger
2024-09-04 11:21     ` Dale
2024-09-04 15:57       ` Peter Humphrey
2024-09-04 19:09       ` Grant Edwards
2024-09-04 21:08         ` Frank Steinmetzger
2024-09-04 21:22           ` Grant Edwards
2024-09-04 21:53             ` Dale
2024-09-04 22:07               ` Grant Edwards
2024-09-04 22:14                 ` Dale
2024-09-04 22:38                 ` Michael
2024-09-05  0:11                   ` Dale
2024-09-05  8:05                     ` Michael
2024-09-05  8:36                       ` Dale
2024-09-05  8:42                         ` Michael
2024-09-05 10:53                           ` Dale
2024-09-05 11:08                             ` Michael
2024-09-05 11:30                               ` Dale
2024-09-05 18:55                                 ` Frank Steinmetzger
2024-09-05 22:06                                   ` Michael
2024-09-06  0:43                                     ` Dale
2024-09-06 12:21                                       ` Michael
2024-09-06 21:41                                         ` Frank Steinmetzger
2024-09-07  9:37                                           ` Michael
2024-09-07 16:28                                             ` Frank Steinmetzger
2024-09-07 17:08                                           ` Mark Knecht
2024-09-14 19:46                                           ` Dale
2024-09-15 22:29                                             ` Frank Steinmetzger
2024-09-16 10:24                                               ` Dale
2024-09-07 22:48                                     ` Wols Lists
2024-09-08  9:37                                       ` Michael
2024-09-05  9:08                   ` Frank Steinmetzger
2024-09-05  9:36                     ` Michael
2024-09-05 10:01                       ` Frank Steinmetzger
2024-09-05 10:59                         ` Dale
2024-09-04 14:21     ` Grant Edwards
2024-09-04 11:37   ` Dale [this message]
2024-09-04 14:23     ` Grant Edwards
2024-09-04 15:58       ` Peter Humphrey
2024-09-04 19:28         ` Dale
2024-09-25 20:41 ` 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=2c2bf733-5e5b-7efa-5933-e9bcde133510@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox