From owner-freebsd-hackers Tue May 30 06:18:37 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA21622 for hackers-outgoing; Tue, 30 May 1995 06:18:37 -0700 Received: from redline.ru (root@mail.redline.ru [194.87.69.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA21566 for ; Tue, 30 May 1995 06:18:15 -0700 Date: Tue, 30 May 1995 17:11:59 +0400 (GMT+0400) From: Anthony Graphics X-Sender: agl@mail.redline.ru To: "Rodney W. Grimes" cc: freebsd-hackers@FreeBSD.org Subject: Re: 950412 hangs on ncr0 probing: In-Reply-To: <199505300935.CAA03294@gndrsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Tue, 30 May 1995, Rodney W. Grimes wrote: The problem was processor for sure. I've replaced it with another one from the production machine and everything then compiled flawlessly (the processor was stepping 0 however also) AGL > Date: Tue, 30 May 1995 02:35:02 -0700 (PDT) > From: Rodney W. Grimes > To: Anthony Graphics > Cc: freebsd-hackers@FreeBSD.org > Subject: Re: 950412 hangs on ncr0 probing: > > > > > tOn Tue, 30 May 1995, Rodney W. Grimes wrote: > > > > > Can you please send me ALL of the markings on both the top and > > > the bottom of the chip. I have an open incident number with Intel > > > on this and need that information to add to the report. If possible > > > get your hands on a stepping 1 CPU and see if the problem just goes > > > away. > > > > > Top markings: > > Intel(r) > > IntelDX4 tm > > iCOMP tm index=435 > > > > A80486DX4-100 > > | C405053W > > | &E 3VOLT SX900 > > | INTEL (M)(C)'89'93 > > > > Marks on the Bottom (on the pin's grid side): > > A4212608CA > > White label: WARRANTY VOID IF TORN > > Well then, go get it replace under WARRANTY :-) :-) :-) > > > 13080595 > > > > Don't know what's under the label: and I checked it twice, > > so the possibility of mistake here is minimal. > > Okay, thanks, I will call Intel in the morning and add it to my > current incident report. > > > AGL > > > I need *ALL* the numbers, both top and bottom. If there is a white > > > tag on the bottom of the CPU that says warranty void if removed do > > > not remove it. If you have a warranty on the CPU chip take it back > > > and get a stepping 1 CPU from who ever you got it from. > > > > Ok, I have another DX100 in the production machine under Linux, will have > > to wait until the non-pick hours to check the stepping of it > > (/proc/cpuinfo in linux ain't reporting stepping) Btw can you tell me > > what's stepping (I have in turn to explain to our suppliers I suspect). Is > > it something like release? > > It is something like a release, there are stepping numbers and mask > revisions. The stepping number gives you a rought idea of what revision > the chip is at, kinda like knowing it is 2.0 but not if it is 2.0.1 or > 2.0.2 or 2.0.3, with that SX900 number I can look up in a table and > find out exactly what mask revision it is (kinda like knowing it is > infact exactly 2.0.3). Intel needs this for the incident report since > the problem may be with only one mask revision. > > They also need the other gunk to figure out what fab it was built > in (this is the number under that white tag since I don't see a fab > plant id in the ones you gave me (most of them say ``MALAY''). > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD >