From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DwOiv-0003uI-Ag for garchives@archives.gentoo.org; Sat, 23 Jul 2005 18:27:45 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6NIQDSb018529; Sat, 23 Jul 2005 18:26:13 GMT Received: from smtp104.mail.sc5.yahoo.com (smtp104.mail.sc5.yahoo.com [66.163.169.223]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6NIKAWV006390 for ; Sat, 23 Jul 2005 18:20:11 GMT Received: (qmail 65752 invoked from network); 23 Jul 2005 18:20:51 -0000 Received: from unknown (HELO ?192.168.50.105?) (richard?j?fish@212.180.33.26 with plain) by smtp104.mail.sc5.yahoo.com with SMTP; 23 Jul 2005 18:20:50 -0000 Message-ID: <42E28B33.2040502@asmallpond.org> Date: Sat, 23 Jul 2005 20:23:47 +0200 From: Richard Fish User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: [New Development] - was 1.) Kernel panic - not syncing: Aiee, killing interupt handler References: <1121911713.14090.82.camel@sysconcept.ca> <42E1FCEF.3030000@asmallpond.org> <1122137932.11718.8.camel@sysconcept.ca> <200507231910.27210.ti.liame@email.it> <1122139131.11718.13.camel@sysconcept.ca> In-Reply-To: <1122139131.11718.13.camel@sysconcept.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 098a1322-5303-49f8-a5f4-3131c73b3d52 X-Archives-Hash: fcf1e83ef825a409e83dabc2fdd2b4ac Joseph wrote: >>[...] >> >> >>>-bash: ./memtest.sh: /bin/bash2: bad interpreter: No such file or >>>directory >>> >>>On both boxes the I have bash-3.0 so what is it looking for? >>> >>> >>Correct the first line of the script from "#!/bin/bash2" to >>"#!/bin/bash" and everything will be fine. >> >>Ciao >> Francesco >> >> > >Thank you, yes that is what I did as soon as I posted the message. >Though it puzzle me whey it runs on my main server and not on the new >box? > >Ps. my mean server pass the memtest.sh without any errors, I'm only >curious the result of that bad rum sticks that pass memtest86 on the >new box. I will re-run both test and post the results. > > My guess is still that if you relax the memory timings in the BIOS, the "bad" RAM will start to work fine. Of course, *I* would still return it and get RAM that actually performs to the specs on the box, but that's just me! :-> -Richard -- gentoo-user@gentoo.org mailing list