Date: Tue, 30 May 1995 02:35:02 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: agl@mac.glas.apc.org (Anthony Graphics) Cc: freebsd-hackers@FreeBSD.org Subject: Re: 950412 hangs on ncr0 probing: Message-ID: <199505300935.CAA03294@gndrsh.aac.dev.com> In-Reply-To: <Pine.LNX.3.91.950530130739.7551A-100000@mail.redline.ru> from "Anthony Graphics" at May 30, 95 01:20:48 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505300935.CAA03294>