Re: sig 11 problem when compiling kernel???
Marcus Brinkmann [EMAIL PROTECTED] wrote (regarding hardware problems indicated by failed kernel compiles): You can also change the bios setings, adding more wait states or so. This is a good idea. I forgot to mention that I already did that. Hi! Also you *may* have faulty cache on the motherboard - try disabling it and pray that the warranty is still on .. SRAM chips are much more sensitive to static discharges than normal DRAM chips. I've been dealing a lot with plain chips going to production usage and know that it ain't bs what they say about grounding. Also the reason may be heat - CPU or regulators near it. Check that the processor has deacent heatsink AND thermal compound between them. Just plain hetsink without anything between processor and it won't do much good. -- Frank --j -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
Lawrence [EMAIL PROTECTED] wrote (ragarding hardware problems indicated by failed kernel compiles): because you are using K6, make sure that it is made after week 30. K6 before week 30 will trigger a bug where people cannot compile Linux kernel if there are more than 32MB in their computer. It only happens to Linux world and in fact the bug is uncovered by Linux guys. Thanks for the tip. I don't _think_ this is my problem. I have only 24 MB of RAM and I have an AMD K5-P90 rather than a K6. My motherboard manual's title page says Pentium(tm) PCI KM-T5-V Rev:2.0 Main Board with no other identification in the manual. It does show jumpers for bus speed and clock multiplier, so after I try pulling unnecessary cards I'll be interested in seeing what happens if I choose a slower speed. -- Frank -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
Marcus Brinkmann [EMAIL PROTECTED] wrote (regarding hardware problems indicated by failed kernel compiles): You can also change the bios setings, adding more wait states or so. This is a good idea. I forgot to mention that I already did that. -- Frank -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
On Sun, Oct 26, 1997 at 02:36:12PM -0600, Frank Sergeant wrote: [EMAIL PROTECTED] (Thalia L. Hooker) wrote Anyways, my next step was to 'make zImage'. I kept getting Sig 11 errors though not at the same point of compilation: gcc: Internal compiler error: program cc1 got fatal signal 11 I seem to have (nearly) the same problem on my AMD K90 system, According to http://www.chorus.com/~poulot/k6bug.html this could be a K6 bug. I only bought mine 6 weeks ago and haven't had this problem luckily. It only happens when you have 32MB of RAM. I have 64mb here. Hamish -- Hamish Moffatt, StudIEAust [EMAIL PROTECTED], [EMAIL PROTECTED] Student, computer science computer systems engineering.3rd year, RMIT. http://hamish.home.ml.org/ (PGP key here) CPOM: [* ] 58% The opposite of a profound truth may well be another profound truth. --Bohr -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
[EMAIL PROTECTED] (Thalia L. Hooker) wrote Anyways, my next step was to 'make zImage'. I kept getting Sig 11 errors though not at the same point of compilation: gcc: Internal compiler error: program cc1 got fatal signal 11 ... After reading the FAQ, it seemed that my problems were typical of the ones described by other users. I have tried at least 30 times starting over from: make dep ; make clean make zImage So, has any one had the same thing happen to them and did it turn out to be a RAM problem? Or, how were you able to solve it? I seem to have (nearly) the same problem on my AMD K90 system, except the error I usually get is segmentation fault. Again, it happens at random places during a kernel compile. (I delete the last .obj file and restart the compile with 'make zImage' and the compile continues. Eventually, I make it all the way through with a successful compile.) I also run into it perhaps 1 out of 3 times when I do a large LaTeX compile, again at random places in the compile. I am inclined to believe that the sig 11 and the segmentation faults are indeed symptoms of bad hardware. Last May, I spent several days swapping RAM SIMMs around, hoping to get a good set that would cure the kernel compile symptom, but with no luck. I have tentatively concluded that my problem is not bad RAM but some other hardware problem. My next step, when I have the strength to face it, is to pull all the non-essential cards and try again. I also have a few additional SIMMs to try, just in case all the others I tried were bad. If pulling the cards doesn't solve it, I will see if I can jump the motherboard to reduce the CPU clock speed and/or bus speed. I already tried turning off the CPU and motherboard caches, without that solving it. This really is a fascinating topic, I think. How can we (at least I) get any work done when I don't have full confidence in my working platform? Well, on this same machine, W95 (often) and plain DOS (sometimes) lock up on me. I spend more time in Linux, though, and it essentially never locks up on me, but does bomb out on kernel or LaTeX compiles. At least under Linux, the error is caught gracefully and I continue to have a command prompt and working operating system, whereas W95 is extremely rude in requiring the machine to be powered off. So, I would say, from my experience on this one machine, that, given the same level of faulty hardware, Linux is much more reliable. Now, another interesting point: if indeed the problems I've experienced on this machine are really _hardware_ problems, and even though W95 cannot cope with those failures gracefully, is it possible that W95 runs reliably given flawless hardware? That is, is it possible that W95 gets a worse reputation than it deserves due to unsuspected bad hardware? Perhaps I will take to recommending that customers purchase only Hewlett-Packward PCs. Would that solve it? (At least, Hewlett-Packward seems to have a good reputation for quality hardware.) -- Frank [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
On Sun, Oct 26, 1997 at 02:36:12PM -0600, Frank Sergeant wrote: [EMAIL PROTECTED] (Thalia L. Hooker) wrote I seem to have (nearly) the same problem on my AMD K90 system, except the error I usually get is segmentation fault. Again, it happens at random places during a kernel compile. (I delete the last .obj file and restart the compile with 'make zImage' and the compile continues. Eventually, I make it all the way through with a successful compile.) I also run into it perhaps 1 out of 3 times when I do a large LaTeX compile, again at random places in the compile. I am inclined to believe that the sig 11 and the segmentation faults are indeed symptoms of bad hardware. Last May, I spent several days swapping RAM SIMMs around, hoping to get a good set that would cure the kernel compile symptom, but with no luck. I have tentatively concluded that my problem is not bad RAM but some other hardware problem. My next step, when I have the strength to face it, is to pull all the non-essential cards and try again. I also have a few additional SIMMs to try, just in case all the others I tried were bad. If pulling the cards doesn't solve it, I will see if I can jump the motherboard to reduce the CPU clock speed and/or bus speed. I already tried turning off the CPU and motherboard caches, without that solving it. You can also change the bios setings, adding more wait states or so. Now, another interesting point: if indeed the problems I've experienced on this machine are really _hardware_ problems, and even though W95 cannot cope with those failures gracefully, is it possible that W95 runs reliably given flawless hardware? That is, is it possible that W95 gets a worse reputation than it deserves due to unsuspected bad hardware? Perhaps I will take to recommending that customers purchase only Hewlett-Packward PCs. Would that solve it? (At least, Hewlett-Packward seems to have a good reputation for quality hardware.) Please notice, that a kernel compile stresses the machine to its end. Linux does use the power of your machine more than windoze. You can have a flawless working Win machine (well, what you call flawless windoze...:) and Linux does seg11 anyway, because windozw does not use the power of the machine. Linux does faster RAM access, so adding waitstates in the bios may help. Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
because you are using K6, make sure that it is made after week 30. K6 before week 30 will trigger a bug where people cannot compile Linux kernel if there are more than 32MB in their computer. It only happens to Linux world and in fact the bug is uncovered by Linux guys. Frank Sergeant wrote: [EMAIL PROTECTED] (Thalia L. Hooker) wrote Anyways, my next step was to 'make zImage'. I kept getting Sig 11 errors though not at the same point of compilation: gcc: Internal compiler error: program cc1 got fatal signal 11 ... After reading the FAQ, it seemed that my problems were typical of the ones described by other users. I have tried at least 30 times starting over from: make dep ; make clean make zImage So, has any one had the same thing happen to them and did it turn out to be a RAM problem? Or, how were you able to solve it? I seem to have (nearly) the same problem on my AMD K90 system, except the error I usually get is segmentation fault. Again, it happens at random places during a kernel compile. (I delete the last .obj file and restart the compile with 'make zImage' and the compile continues. Eventually, I make it all the way through with a successful compile.) I also run into it perhaps 1 out of 3 times when I do a large LaTeX compile, again at random places in the compile. I am inclined to believe that the sig 11 and the segmentation faults are indeed symptoms of bad hardware. Last May, I spent several days swapping RAM SIMMs around, hoping to get a good set that would cure the kernel compile symptom, but with no luck. I have tentatively concluded that my problem is not bad RAM but some other hardware problem. My next step, when I have the strength to face it, is to pull all the non-essential cards and try again. I also have a few additional SIMMs to try, just in case all the others I tried were bad. If pulling the cards doesn't solve it, I will see if I can jump the motherboard to reduce the CPU clock speed and/or bus speed. I already tried turning off the CPU and motherboard caches, without that solving it. This really is a fascinating topic, I think. How can we (at least I) get any work done when I don't have full confidence in my working platform? Well, on this same machine, W95 (often) and plain DOS (sometimes) lock up on me. I spend more time in Linux, though, and it essentially never locks up on me, but does bomb out on kernel or LaTeX compiles. At least under Linux, the error is caught gracefully and I continue to have a command prompt and working operating system, whereas W95 is extremely rude in requiring the machine to be powered off. So, I would say, from my experience on this one machine, that, given the same level of faulty hardware, Linux is much more reliable. Now, another interesting point: if indeed the problems I've experienced on this machine are really _hardware_ problems, and even though W95 cannot cope with those failures gracefully, is it possible that W95 runs reliably given flawless hardware? That is, is it possible that W95 gets a worse reputation than it deserves due to unsuspected bad hardware? Perhaps I will take to recommending that customers purchase only Hewlett-Packward PCs. Would that solve it? (At least, Hewlett-Packward seems to have a good reputation for quality hardware.) -- Frank [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: sig 11 problem when compiling kernel???
On Fri, Oct 24, 1997 at 02:14:56PM -0500, Thalia L. Hooker wrote: Hi! For kernel compiling, try using the kernel-package deb file. It is a lot of easier with it, and you avoid common mistakes. For your seg11 problem, try pulling the RAM out and put it in again. Follow the suggestions in the FAQ you read. Try other RAM's, or try your RAM's in another computer (with linux and gcc). thank you, Marcus -- Rhubarb is no Egyptian god. Marcus Brinkmann [EMAIL PROTECTED] http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
