protocol.h:28:44: internal compiler error: Illegal instruction
Assuming that you are running stable 64 bit Slackware 15.0 and studying
how gcc was built at http://ftp.slackware.com/pub/slackware/ slackware64-15.0/source/d/gcc/gcc.SlackBuild there doesn't seem to be any such flags for x86_64. However, if you are running 32 bit Slackware 15.0, those gcc i586 packages has been compiled to require the instruction set
of an i586 yet tuned for i686 CPUs.
But in most cases, newer CPUs support the instructions of all older CPUs
and sometimes add some more instructions. Could it be that your CPU is broken, lacking support for some instruction that it were supposed to
have?
Maybe it will work better if you recompile gcc with -march=native ?
I want to avoid a rebuild of GCC if I can, because then *my* GCC won't
sync with the OS's one and Bad Things can happen. I'll play around with compiler flags in the meantime. I'm on the GCC mailing list so last
resort is check there, but I though I'd try everything else first before making a dumb mistake in front of the GCC masters.
All I can think of is that the USB stick I used for the image is
getting "holes" in it. One of the packages I knew to be good was not installing and I had to fetch a new copy of it (same stick) and it
worked.
If you can't trust your ways to transfer Slackware packages, all stock Slackware packages come with a .asc file which can be used together with
gpg to check that the packages is OK and from the right source.
Bying machines and memory supporting ECC is more expensive than memory without ECC, but it is really nice to have those days when the memory
starts to go bad.
The choices are to identiyfy the bad DIMM and replace it or simply
remove it and let the machine continue its life with less RAM, or to
simply retire that 15 year old hardware.
My Omni OS machine is from 2012,
On Wed, 30 Sep 2026 21:25:51 -0400, jayjwa wrote:
All I can think of is that the USB stick I used for the image is
getting "holes" in it. One of the packages I knew to be good was not
installing and I had to fetch a new copy of it (same stick) and it
worked.
If you can't trust your ways to transfer Slackware packages, all stock Slackware packages come with a .asc file which can be used together with
gpg to check that the packages is OK and from the right source. Even
easier is to use the CHECKSUMS.md5 file to check all the packages at once.
Speaking of being able to trust hardware... Last weeks I have had some machines compressing data with xz, on one of those machines xz sometimes segfaults. Sometimes that machine also hangs hard, requiring a reboot. At reboot, the machine tells me that its ECC RAM has been able to find correctable memory errors in one of two DIMMS. Most likely, the machine
has also suffered from some non correctable errors causing those
segfaults and hangs.
Bying machines and memory supporting ECC is more expensive than memory without ECC, but it is really nice to have those days when the memory
starts to go bad. In this case, I can say that this 15 year old machine
has a bad memory. There is nothing wrong with the software installation,
no point in trying to do a reinstall of the OS. The choices are to
identiyfy the bad DIMM and replace it or simply remove it and let the machine continue its life with less RAM, or to simply retire that 15 year old hardware.
Without ECC, I might have spent days or weeks trying to reinstall
software, and maybe taking the machine offline for some day to run
memtest. Now, with ECC, the machine itself has pinpointed the problem.
regards Henrik
There is another way to deal with bad RAM. If you run memtest86+ on the system and find only a few bad regions, you can add some arguments toI saw options for Grub, but thankfully system76 has asked for the bad
the kernel command-line to mark those regions as reserved.
I saw options for Grub, but thankfully system76 has asked for the bad
module to be shipped back (and only the bad one). Right now I'm running
with half memory. Hopefully they ship the new replacement shortly.
In all these years, I never saw a system so badly "off" - and all
because of a bad stick of ram. That was a very hard problem to track
down. In the past, I've taken ram modules from old machines, put them
into new ones, and kept on going with that much more memory. This was
the first time I've seen bad ram out of the box.
Not an issue since:
uptime
13:20:54 up 14 days, 1:54, 2 users, load average: 1.09, 1.36, 1.57
My bad RAM was new, as well. I upgraded the memory from two 4GB sticks
to two 8GB sticks a year or two ago, and one had the small bad regions.
It's disappointing, but I'm not going to make a fuss over losing 8kB of
RAM.
With prices as they are today, I'm kicking myself for not getting 32GB
of RAM back then. That much costs as much today as the whole box was
worth back when I got it.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 53:50:04 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |