Re: woody: segfaulting all over the place
On Wed, Aug 29, 2001 at 01:22:21PM -0500, Dimitri Maziuk wrote: > I suspect that memory words may be stripped accross both modules, so > the error remains at the same address after the swap (in the different > part of the same word). Can you test each module separately? Or put > them in a different bank? > yup, did it all.. tested the original module only, tested the added module only, swapped them.. the error remains the same, i.e. the same test fails at the same address.. that's what makes it so hard for me to find a solution: it's not one module that fails and the other works, i could replace it, i could even replace them both given the cheapness of memory but i don't see what that would do because memtest doesn't really lead me to the conclusion that it's the normal ram that causes the pain.. it still could be anything.. rather frustrated, but thankful, of course, frank.
Re: woody: segfaulting all over the place
* Frank Preut ([EMAIL PROTECTED]) spake thusly: ... > i didn't think of memory because i didn't change anything there in the > last six months.. but maybe it got wrecked recently so i tested it with > the latest version 2.7 of memtest.. and indeed it came up with an error > at the address 04e0 during test no. 4 so i tried playing around with the > two 64 mb modules and the exact same error occurs no matter which module > is installed in which lot.. ?? wtf, what is wrong here? and why did it > work before, i'm quite sure that i got an error when i tested memory > before.. could it be the cache (32k of level 1, 512 of level 2)? and > couldn't do anything about that, right? Memory words may be stripped accross both modules. If so, swapping the modules will put the error in a different part of the same word, and the address will not change. Maybe. Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key The wombat is a mixture of chalk and clay used for respiration. -- MegaHal
Re: woody: segfaulting all over the place
* Frank Preut ([EMAIL PROTECTED]) spake thusly: > On Tue, Aug 28, 2001 at 02:48:06PM -0300, Miguel Griffa wrote: > > it happend to me once, it was memory, > > you can donwload a boot disk with a mem tester (memtest86, as mentioned > > before) > > and see what it says > > > > hm, so i'm on the wrong track? let's see.. > > i didn't think of memory because i didn't change anything there in the > last six months.. but maybe it got wrecked recently so i tested it with > the latest version 2.7 of memtest.. and indeed it came up with an error > at the address 04e0 during test no. 4 so i tried playing around with the > two 64 mb modules and the exact same error occurs no matter which module > is installed in which lot.. ?? wtf, what is wrong here? and why did it > work before, i'm quite sure that i got an error when i tested memory > before.. could it be the cache (32k of level 1, 512 of level 2)? and > couldn't do anything about that, right? I suspect that memory words may be stripped accross both modules, so the error remains at the same address after the swap (in the different part of the same word). Can you test each module separately? Or put them in a different bank? Dima -- E-mail dmaziuk at bmrb dot wisc dot edu (@work) or at crosswinds dot net (@home) http://www.bmrb.wisc.edu/descript/gpgkey.dmaziuk.ascii -- GnuPG 1.0.4 public key The wombat is a mixture of chalk and clay used for respiration. -- MegaHal
Re: woody: segfaulting all over the place
On Tue, Aug 28, 2001 at 02:48:06PM -0300, Miguel Griffa wrote: > it happend to me once, it was memory, > you can donwload a boot disk with a mem tester (memtest86, as mentioned > before) > and see what it says > hm, so i'm on the wrong track? let's see.. i didn't think of memory because i didn't change anything there in the last six months.. but maybe it got wrecked recently so i tested it with the latest version 2.7 of memtest.. and indeed it came up with an error at the address 04e0 during test no. 4 so i tried playing around with the two 64 mb modules and the exact same error occurs no matter which module is installed in which lot.. ?? wtf, what is wrong here? and why did it work before, i'm quite sure that i got an error when i tested memory before.. could it be the cache (32k of level 1, 512 of level 2)? and couldn't do anything about that, right? hm, i'll see what happens and whether the problem occurs.. i guess i can't do anything about it right now.. thanks anyway to both of you.. f.
Re: woody: segfaulting all over the place
it happend to me once, it was memory, you can donwload a boot disk with a mem tester (memtest86, as mentioned before) and see what it says On Tue, Aug 28, 2001 at 06:08:42PM +0200, Frank Preut wrote: > hello friends, > i recently did a fresh install of potato and immediately > dist-upgraded to woody.. now, after playing around with it for a few > days and installing the stuff i wanted i have this strange windows like > problem: after i've been working on the computer (or after it has just > been sitting around idle, even) some program might or might not give me > a segfault and from then on i can't do anything anymore.. well, almost, > at least, some apps might or might not work, i can't log on and when i > get so far as to give the halt command init often says: switching to > runlevel 0, sending the term signal, sending the kill signal, no more > processes left in this runlevel and then nothing happens.. or i get Id > "[number]" respawning too fast, disabled for five minutes.. gosh, i have > absolutely no idea what this is all about, i upgraded to kernel > 2.4.8-586 but iirc the strange behaviour started before that.. i > installed a 3com 905c tx m recently (it has nothing to do so far, no > network as of yet) but it happens even when i delete the driver and the > card is not seen by the system.. > > what i don't understand is why is almost any app segfaulting on me? i'm > trying hard to get rid of windows and now my gnu/linux crashes in the > same haphazard manner as the redmond shit.. is this all about init, is > something perhaps hosed there? i would be really grateful for any help > so that we could at least file a bug.. right now this would be against > woody as a whole, i fear.. :-/ > > here's the hardware config: > > pII 350 on an intel board (440bx chipset) > nVidia riva 128 graphics (btw: x4 doesn't work in 800x600 anymore on > that one), es1371 soundchip (all on board) > wd ac26400b harddrive, teac 532ea cdrom > as mentioned above 3com 905c nic > > all crappy stuff, i know, but it works and as a student i don't have the > dough to get a new box every two years.. though it's well about time.. > :-( > > again, thanks for any help offered, i'm at a total loss here.. > > frank. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: woody: segfaulting all over the place
On 28 Aug 2001 18:08:42 +0200, Frank Preut wrote: > hello friends, > i recently did a fresh install of potato and immediately > dist-upgraded to woody.. now, after playing around with it for a few > days and installing the stuff i wanted i have this strange windows like > problem: after i've been working on the computer (or after it has just > been sitting around idle, even) some program might or might not give me > a segfault and from then on i can't do anything anymore.. well, almost, > at least, some apps might or might not work, i can't log on and when i > get so far as to give the halt command init often says: switching to > runlevel 0, sending the term signal, sending the kill signal, no more > processes left in this runlevel and then nothing happens.. or i get Id > "[number]" respawning too fast, disabled for five minutes.. gosh, i have > absolutely no idea what this is all about, i upgraded to kernel > 2.4.8-586 but iirc the strange behaviour started before that.. i > installed a 3com 905c tx m recently (it has nothing to do so far, no > network as of yet) but it happens even when i delete the driver and the > card is not seen by the system.. > > what i don't understand is why is almost any app segfaulting on me? i'm > trying hard to get rid of windows and now my gnu/linux crashes in the > same haphazard manner as the redmond shit.. is this all about init, is > something perhaps hosed there? i would be really grateful for any help > so that we could at least file a bug.. right now this would be against > woody as a whole, i fear.. :-/ > > here's the hardware config: > > pII 350 on an intel board (440bx chipset) > nVidia riva 128 graphics (btw: x4 doesn't work in 800x600 anymore on > that one), es1371 soundchip (all on board) > wd ac26400b harddrive, teac 532ea cdrom > as mentioned above 3com 905c nic I'd check your memory with memtest86 to see if thats your problem. Otherwise ... are you overclocking? --mike
woody: segfaulting all over the place
hello friends, i recently did a fresh install of potato and immediately dist-upgraded to woody.. now, after playing around with it for a few days and installing the stuff i wanted i have this strange windows like problem: after i've been working on the computer (or after it has just been sitting around idle, even) some program might or might not give me a segfault and from then on i can't do anything anymore.. well, almost, at least, some apps might or might not work, i can't log on and when i get so far as to give the halt command init often says: switching to runlevel 0, sending the term signal, sending the kill signal, no more processes left in this runlevel and then nothing happens.. or i get Id "[number]" respawning too fast, disabled for five minutes.. gosh, i have absolutely no idea what this is all about, i upgraded to kernel 2.4.8-586 but iirc the strange behaviour started before that.. i installed a 3com 905c tx m recently (it has nothing to do so far, no network as of yet) but it happens even when i delete the driver and the card is not seen by the system.. what i don't understand is why is almost any app segfaulting on me? i'm trying hard to get rid of windows and now my gnu/linux crashes in the same haphazard manner as the redmond shit.. is this all about init, is something perhaps hosed there? i would be really grateful for any help so that we could at least file a bug.. right now this would be against woody as a whole, i fear.. :-/ here's the hardware config: pII 350 on an intel board (440bx chipset) nVidia riva 128 graphics (btw: x4 doesn't work in 800x600 anymore on that one), es1371 soundchip (all on board) wd ac26400b harddrive, teac 532ea cdrom as mentioned above 3com 905c nic all crappy stuff, i know, but it works and as a student i don't have the dough to get a new box every two years.. though it's well about time.. :-( again, thanks for any help offered, i'm at a total loss here.. frank.
