[GLLUG] Re: Still having problems

Thomas Alan Hearn hearntho at msu.edu
Wed Jul 14 00:31:34 EDT 2004


Still no go,
 I tried switching the memory sticks with no luck.  Also tried disabling 
just about everything in the BIOS, USB, IEE1394, Parallel and Serial, and 
still getting the same problems. 

Any more ideas? 

Thanks for all the suggestions so far,
Tom 

Sean O'Malley writes: 

> It _might_ not be a bad memory issue, but...  When the OS loads if say in
> the spot where the bad memory is and it never uses it, you won't see any
> ill effects. You will get ill effects if it does try to read from it. For
> example, if under windows or linux you have say the driver for a car jack
> loaded into that part of memory, it doesn't matter because you don't own a
> car, thus the OS never tries to utilize the software loaded into that part
> of memory. 
> 
> If say one day you do want to use your automated carjack, then it will act
> flaky. 
> 
> Memory is consistantly allocated the same way for every OS at boot
> typically, (depending on the system) it will load slot 1, until it
> is filled then start with slot 2, etc. So if your your first memory module
> is bad but you swap it into the second slot. It changes what data is
> being stored in that memory by the OS. Thus it crashes in a different
> spot. It only works if you can _consistantly_ get the software to load
> identically like off a cd where nothing is changed. 
> 
> If the swap, doesn't change anything. You can probably cross that off your
> list as a culprit. 
> 
>  
> 
> On Tue, 13 Jul 2004, Thomas Alan Hearn wrote: 
> 
>> Sean,
>>  The memory works fine with all other operating systems on the machine, I've
>> installed windows, and even Redhat 9.0 (Shrike) on it, with no problems.
>> Slackware 10 also runs fine?? 
>>
>> Tom 
>>
>> Sean O'Malley writes: 
>>
>> >
>> >
>> > On Tue, 13 Jul 2004, Rich Clark wrote:
>> >> I'd say good call.  You may also want to question if the memory is not the
>> >> problem also.  I had a stick here that for love nor money would work in
>> >> any machine I put it in, most running Mandrake 10 Comm on several, and one
>> >> with Windows XP on it.  Needless to say, I returned it.
>> >
>> > If you can, swap slot 1 and slot 2 of your memory around and see if that
>> > changes the point at which it is crashing consistantly. If it does then it
>> > is most likely bad memory.
>> >
>> > That should at least eliminate one of the choices in the 'guessing why I
>> > hate x86 hardware' game.
>> >
>> > Does hyperthreading still cause whacky crashes?
>> >
>> > _______________________________________________
>> > linux-user mailing list
>> > linux-user at egr.msu.edu
>> > http://www.egr.msu.edu/mailman/listinfo/linux-user
>> > 
>>
>> 
>>
>  
> 
 




More information about the linux-user mailing list