Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 4 September 2024 02:12:51 CEST, Grant Edwards wrote: >On 2024-09-03, Dale wrote: > >> I was trying to re-emerge some packages. The ones I was working on >> failed with "internal compiler error: Segmentation fault" or similar >> being the common reason for failing. > >In my experience, that usually means failing RAM. I'd try running >memtest86 for a day or two. > >-- >Grant > Also out of memory might cause a segmentation fault. Dale, do you have a swap partition or file? At least three of the packages you mention are quite memory hungry, depending on your -j options in make.conf. You should see an OOM error in the syslog if this is the case, is there any hint in it? Raf
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Dale wrote: > Howdy, > > I was trying to re-emerge some packages. The ones I was working on > failed with "internal compiler error: Segmentation fault" or similar > being the common reason for failing. I did get gcc to compile and > install. But other packages are failing, but some are compiling just > fine. <<>> > Open to ideas. I hope I don't have to move back to the old rig while > sorting this out. O_O Oh, I updated my old rig this past weekend. Not > a single problem on it. Everything updated just fine. > > Thanks. > > Dale > > :-) :-) > 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 :-) :-)
[gentoo-user] The following update(s) have been skipped due to unsatisfied dependencies
Howdy, I don't do emerge -e world very often but this is weird. This is the complaint emerge spits out: !!! The following update(s) have been skipped due to unsatisfied dependencies !!! triggered by backtracking: x11-drivers/nvidia-drivers:0 x11-base/xorg-drivers:0 x11-base/xorg-server:0 x11-drivers/xf86-input-libinput:0 xfce-base/xfce4-settings:0 xfce-base/xfce4-meta:0 x11-drivers/xf86-video-vesa:0 x11-misc/sddm:0 kde-plasma/plasma-meta:6 I checked with equery, they all in the tree, installed even. What is emerge trying to tell me? I also get this which may or may not be related. !!! Ebuilds for the following packages are either all !!! masked or don't exist: app-backup/mkstage4 kde-plasma/plasma-meta sys-kernel/gentoo-sources:6.9.10 sys-kernel/gentoo-sources:6.9.4 x11-drivers/nvidia-drivers x11-drivers/xf86-video-vesa xfce-base/xfce4-meta I get the gentoo-sources and mkstage4. It always complains about those. The others tho, what's emerge fussing about? Ideas? I emerge something weird to cause that? Is emerge going wonky over nothing? Dale :-) :-)
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Am Wed, Sep 04, 2024 at 05:48:29AM -0500 schrieb Dale: > I wonder how much fun getting this memory replaced is going to be. o_O I once had a bad stick of Crucial Ballistix DDR3. I think it also started with GCC segfaults. So I took a picture of the failing memtest, e-mailed that to crucial and they sent me instructions what to do. I keep the packaging of all my tech stuff, so I put the sticks into their blister (I bought it as a kit, so I had to send in both sticks), put a paper note in for which one was faulty and sent them off to Crucial in Ireland. After two weeks or so I got a new kit in the mail. Thankfully by that time I had two kits for the maximum of 4 × 8 GiB, so I was able to continue using my PC. -- Grüße | Greetings | Salut | Qapla’ Please do not share anything from, with or about me on any social network. An empty head is easier to nod with. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Frank Steinmetzger wrote: > Am Wed, Sep 04, 2024 at 05:48:29AM -0500 schrieb Dale: > >> I wonder how much fun getting this memory replaced is going to be. o_O > I once had a bad stick of Crucial Ballistix DDR3. I think it also started > with GCC segfaults. So I took a picture of the failing memtest, e-mailed > that to crucial and they sent me instructions what to do. > > I keep the packaging of all my tech stuff, so I put the sticks into their > blister (I bought it as a kit, so I had to send in both sticks), put a paper > note in for which one was faulty and sent them off to Crucial in Ireland. > After two weeks or so I got a new kit in the mail. Thankfully by that time I > had two kits for the maximum of 4 × 8 GiB, so I was able to continue using > my PC. > I ordered another set of memory sticks. I figure I will have to send them both back which means no memory at all. I wasn't planning to go to 128GBs yet but guess I am now. Once new ones come in, I'll start working on getting them swapped. I don't recall ever having a memory stick go bad before. I've had to reseat one before but not just plain go bad. I noticed that that qtweb package now wants 32GBs of space to build now. Dang, I feel for someone using a Raspberry Pi. That thing is getting really big. I didn't set up swap so I had to create a swapfile. Dale :-) :-)
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
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 :-) :-)
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 2024-09-04, Frank Steinmetzger wrote: > Am Wed, Sep 04, 2024 at 05:48:29AM -0500 schrieb Dale: > >> I wonder how much fun getting this memory replaced is going to be. o_O > > I once had a bad stick of Crucial Ballistix DDR3. I think it also started > with GCC segfaults. So I took a picture of the failing memtest, e-mailed > that to crucial and they sent me instructions what to do. Yep, I got free replacement from Crucial once years ago also. It was pretty easy, but it took a week or two. -- Grant
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 2024-09-04, Dale wrote: > 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? Unfortunately, yes. I have had some failing RAM that resulted in some files getting corrupted. -- Grant
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On Wednesday 4 September 2024 12:21:19 BST Dale wrote: > I wasn't planning to go to 128GBs yet but guess I am now. I considered doubling up to 128GB a few months ago, but the technical help people at Armari (the workstation builder) told me that I'd need to jump through a few hoops. Not only would the chips need to have been selected for that purpose, but I'd have to do a fair amount of BIOS tuning while running performance tests. I decided not to push my luck. -- Regards, Peter.
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On Wednesday 4 September 2024 15:23:13 BST Grant Edwards wrote: > On 2024-09-04, Dale wrote: > > I forgot to ask, is there anything else that bad memory could affect? How long have you got? ;-) -- Regards, Peter.
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 2024-09-04, Dale wrote: > I ordered another set of memory sticks. I figure I will have to send > them both back which means no memory at all. I wasn't planning to go to > 128GBs yet but guess I am now. [...] Good luck. The last time I had one fail, I needed the machine for work and couldn't wait for the replacement to ship. So, I went to either MicroCenter or Best Buy and picked up another pair of SIMMs with the exact same specs (different brand, of course). A couple weeks later, my replacemnts arrived. "Yippe!" I say to myself, "twice as much RAM!" I plugged them in alongside the recently purchased pair. Wouldn't work. Either pair of SIMMs worked fine by themselves, but the only way I could get both pairs to work together was to drop the clock speed down to about a third the speed they were supposed to support. I read and re-read the motherboard specs and manual. I spent hours tweaking different memory settings in the BIOS, but no joy. Now I've got a backup pair of SIMMs sitting on the shelf. -- Grant
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Peter Humphrey wrote: > On Wednesday 4 September 2024 15:23:13 BST Grant Edwards wrote: >> On 2024-09-04, Dale wrote: >>> I forgot to ask, is there anything else that bad memory could affect? > How long have you got? ;-) > Well, the new files I downloaded, I can let Qbittorrent check what it downloaded. If it passes the tests, then I can copy those over and replace what I copied over in the last week or so. I think this stick of memory only went bad in the past couple days. Shouldn't be many files. I'd hope reading wouldn't corrupt a file. Emerge -e world is still going strong. Still wondering about problem in other thread tho. Dale :-) :-)
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Am Wed, Sep 04, 2024 at 07:09:43PM - schrieb Grant Edwards: > On 2024-09-04, Dale wrote: > > > I ordered another set of memory sticks. I figure I will have to send > > them both back which means no memory at all. I wasn't planning to go to > > 128GBs yet but guess I am now. [...] > > Good luck. > > […] > I plugged them in alongside the recently purchased pair. Wouldn't > work. Either pair of SIMMs worked fine by themselves, but the only way > I could get both pairs to work together was to drop the clock speed > down to about a third the speed they were supposed to support. Indeed that was my first thought when Dale mentioned getting another pair. I don’t know if it’s true for all Ryzen chips, but if you use four sticks, they may not work at the maximum speed advertised by AMD (not counting in overlcocking). If you kept the settings to Auto you shouldn’t get problems, but RAM may work slower then. OTOH, since you don’t do hard-core gaming or scientific number-crunching, it is unlikely you will notice a difference in your every-day computing. -- Grüße | Greetings | Salut | Qapla’ Please do not share anything from, with or about me on any social network. How can I know what I’m thinking before I hear what I’m saying? signature.asc Description: PGP signature
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 2024-09-04, Frank Steinmetzger wrote: > Am Wed, Sep 04, 2024 at 07:09:43PM - schrieb Grant Edwards: >> […] >> I plugged them in alongside the recently purchased pair. Wouldn't >> work. Either pair of SIMMs worked fine by themselves, but the only way >> I could get both pairs to work together was to drop the clock speed >> down to about a third the speed they were supposed to support. > > Indeed that was my first thought when Dale mentioned getting another > pair. I don’t know if it’s true for all Ryzen chips, but if you use > four sticks, they may not work at the maximum speed advertised by > AMD (not counting in overlcocking). If you kept the settings to Auto > you shouldn’t get problems, but RAM may work slower then. Yea, I thought auto should work, but it didn't. I had to manually lower the RAM clock speed to get all four to work at the same time. The BIOS screens were a bit mind-boggling (very high on graphics, dazzle, and flash -- very low on usability). So it's possible I didn't really have auto mode correctly enabled. > OTOH, since you don’t do hard-core gaming or scientific > number-crunching, it is unlikely you will notice a difference in > your every-day computing. In my case I compared an "emerge" that took several minutes, and it took significantly longer with the lower RAM clock speed. I decided I was better off with fewer GB of faster RAM.
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Grant Edwards wrote: > On 2024-09-04, Frank Steinmetzger wrote: >> Am Wed, Sep 04, 2024 at 07:09:43PM - schrieb Grant Edwards: >>> […] >>> I plugged them in alongside the recently purchased pair. Wouldn't >>> work. Either pair of SIMMs worked fine by themselves, but the only way >>> I could get both pairs to work together was to drop the clock speed >>> down to about a third the speed they were supposed to support. >> Indeed that was my first thought when Dale mentioned getting another >> pair. I don’t know if it’s true for all Ryzen chips, but if you use >> four sticks, they may not work at the maximum speed advertised by >> AMD (not counting in overlcocking). If you kept the settings to Auto >> you shouldn’t get problems, but RAM may work slower then. > Yea, I thought auto should work, but it didn't. I had to manually > lower the RAM clock speed to get all four to work at the same > time. The BIOS screens were a bit mind-boggling (very high on > graphics, dazzle, and flash -- very low on usability). So it's > possible I didn't really have auto mode correctly enabled. > >> OTOH, since you don’t do hard-core gaming or scientific >> number-crunching, it is unlikely you will notice a difference in >> your every-day computing. > In my case I compared an "emerge" that took several minutes, and it > took significantly longer with the lower RAM clock speed. I decided I > was better off with fewer GB of faster RAM. > > At one point, I looked for a set of four sticks of the memory. I couldn't find any. They only come in sets of two. I read somewhere that the mobo expects each pair to be matched. Thing is, things change. My mobo may work different or something or they figured out some better coding. The downside, my mobo is a somewhat older tech. Given the number of components on each stick, it's pretty amazing they work at all. I recall our conversation about the number of transistors on a CPU. I suspect memory is right up there with it. 32GBs on a stick is a lot. I think they have larger sticks too. That means even more. Also, mine puts on a fancy light show. It has LEDs that change colors. Annoying at times. Needs a off switch. LOL My emerge -e world is still chugging along. Not a single failure yet. I started Qbittorrent and it complained about files. I did run fsck on the file system tho and it did fix a few things, like it always does. It always finds something to improve on. I told QB to force a recheck, within minutes, it was off to the races again. It appears to be fixing any bad files. Sort of neat that it can do that. Dale :-) :-) P. S. With my TV not connected, my monitor situation went weird. I guess when I get the new rig back to normal, it will work like it did before.
[gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On 2024-09-04, Dale wrote: > At one point, I looked for a set of four sticks of the memory. I > couldn't find any. They only come in sets of two. I read somewhere > that the mobo expects each pair to be matched. Yep, that's definitely how it was supposed to work. I fully expected my two (identically spec'ed) sets of two work. All the documentation I could find said it should. It just didn't. :/ -- Grant
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Grant Edwards wrote: > On 2024-09-04, Dale wrote: > >> At one point, I looked for a set of four sticks of the memory. I >> couldn't find any. They only come in sets of two. I read somewhere >> that the mobo expects each pair to be matched. > Yep, that's definitely how it was supposed to work. I fully expected > my two (identically spec'ed) sets of two work. All the documentation I > could find said it should. It just didn't. :/ > > -- > Grant > Well, when I get them all in, I'll post back how it went, unless I P. S. it somewhere. It could be a while. They claim they will be here Friday. Who knows. Then comes the testing part. Of course, testing the set I had didn't work out either. o_O QB is fixing quite a few files tho. H. It could take years for me to watch all those videos. O_O Dale :-) :-)
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
On Wednesday 4 September 2024 23:07:17 BST Grant Edwards wrote: > On 2024-09-04, Dale wrote: > > At one point, I looked for a set of four sticks of the memory. I > > couldn't find any. They only come in sets of two. I read somewhere > > that the mobo expects each pair to be matched. > > Yep, that's definitely how it was supposed to work. I fully expected > my two (identically spec'ed) sets of two work. All the documentation I > could find said it should. It just didn't. :/ > > -- > Grant Often you have to dial down latency and/or increase voltage when you add more RAM modules. It is a disappointment when faster memory has to be slowed down because those extra two sticks you bought on ebay at a good price, are of a slightly lower spec. Some MoBos are more tolerant than others. I have had systems which failed to work when the additional RAM modules were not part of a matching kit. I've had others which would work no matter what you threw at them. High performance MoBos which have highly strung specs, tend to require lowering frequency/increasing latency when you add more RAM. Regarding Dale's question, which has already been answered - yes, anything the bad memory has touched is suspect of corruption. Without ECC RAM a dodgy module can cause a lot of damage before it is discovered. This is why I *always* run memtest86+ overnight whenever I get a new system, or add new RAM. I've only had one fail over the years, but I'd better be safe than sorry. ;-) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Michael wrote: > On Wednesday 4 September 2024 23:07:17 BST Grant Edwards wrote: >> On 2024-09-04, Dale wrote: >>> At one point, I looked for a set of four sticks of the memory. I >>> couldn't find any. They only come in sets of two. I read somewhere >>> that the mobo expects each pair to be matched. >> Yep, that's definitely how it was supposed to work. I fully expected >> my two (identically spec'ed) sets of two work. All the documentation I >> could find said it should. It just didn't. :/ >> >> -- >> Grant > Often you have to dial down latency and/or increase voltage when you add more > RAM modules. It is a disappointment when faster memory has to be slowed down > because those extra two sticks you bought on ebay at a good price, are of a > slightly lower spec. > > Some MoBos are more tolerant than others. I have had systems which failed to > work when the additional RAM modules were not part of a matching kit. I've > had others which would work no matter what you threw at them. High > performance MoBos which have highly strung specs, tend to require lowering > frequency/increasing latency when you add more RAM. > > Regarding Dale's question, which has already been answered - yes, anything > the > bad memory has touched is suspect of corruption. Without ECC RAM a dodgy > module can cause a lot of damage before it is discovered. This is why I > *always* run memtest86+ overnight whenever I get a new system, or add new > RAM. > I've only had one fail over the years, but I'd better be safe than sorry. ;-) When I built this rig, I first booted the Gentoo Live boot image and just played around a bit. Mostly to let the CPU grease settle in a bit. Then I ran memtest through a whole test until it said it passed. Only then did I start working on the install. The rig has ran without issue until I noticed gkrellm temps were stuck. They wasn't updating as temps change. So, I closed gkrellm but then it wouldn't open again. Ran it in a console and saw the error about missing module or something. Then I tried to figure out that problem which lead to seg fault errors. Well, that lead to the thread and the discovery of a bad memory stick. I check gkrellm often so it was most likely less than a day. Could have been only hours. Knowing I check gkrellm often, it was likely only a matter of a couple hours or so. The only reason it might have went longer, the CPU was mostly idle. I watch more often when the CPU is busy, updates etc. I just hope I can put in all four sticks and it work once the bad set is replaced. I miss having 64GBs of memory already. Oh, QB is redoing a lot of files. It seems it picked up on some . . . issues. :/ Dale :-) :-)
[gentoo-user] Wayland and CPU load
Greetings, Has anyone else seen grossly excessive CPU load since adopting the new Wayland way of doing things? /Top/ is showing 1300% going on kwin_wayland and the whole of the rest going on plasmashell. I need hardly say this doesn't make a responsive system. -- Regards, Peter.
