From owner-freebsd-bugs  Thu Oct  7  5:20:10 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 3A73914E5B
	for <freebsd-bugs@FreeBSD.org>; Thu,  7 Oct 1999 05:20:07 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id FAA57716;
	Thu, 7 Oct 1999 05:20:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Date: Thu, 7 Oct 1999 05:20:02 -0700 (PDT)
Message-Id: <199910071220.FAA57716@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: tedm@toybox.placo.com
Subject: Re: i386/13706: FreeBSD identifies all 80486 processors as DX chips
Reply-To: tedm@toybox.placo.com
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR i386/13706; it has been noted by GNATS.

From: tedm@toybox.placo.com
To: "Matt Behrens" <mbehrens@globaldsl.com>,
	freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: i386/13706: FreeBSD identifies all 80486 processors as DX chips
Date: Thu, 07 Oct 99 02:44:46 +0800

 Hmmm....   Question for you:  Do you actually _have_ a 486SX that you tested
 this on?
 
 On my Compaq Presario 486DX2/66 machine running 2.2.8 the output of dmesg
 shows:
 
 CPU: i486DX (486-class CPU)
 
 This the only line - there is no additional line showing Origin or features.
 Also, the CPU line does NOT show DX2, it only shows DX.
 
 On a customer 486/25SX I see the exact same result, the CPU line shows
 i486DX, _not_ i486SX, and there is no Origin or features line.
 
 Both of those systems are running custom-built kernels with only the
 cpu I486_CPU defined in the kernel config file.
 
 On a system of mine running 3.2, Generic kernel, I see exactly the same
 behavior.  I even went and built a custom kernel - and found EXACTLY THE
 SAME BEHAVIOR!!!.  This was on yet another system running a 486DX2.
 
 Ted
 
 
 //--- forwarded letter -------------------------------------------------------
 > X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.5-22 i586)
 > MIME-Version: 1.0
 > Date: Wed, 06 Oct 99 14:10:43 -0400
 > From: "Matt Behrens" <mbehrens@globaldsl.com>
 > To: freebsd-gnats-submit@freebsd.org,
 >     tedm@toybox.placo.com
 > Subject: Re: i386/13706: FreeBSD identifies all 80486 processors as DX chips
 
 > 
 > Didn't your dmesg come with two lines after the CPU: line, which look
 > like this (from my DX2/40 laptop):
 > 
 > CPU: i486 DX2 (486-class CPU)
 >   Origin = "GenuineIntel"  Id = 0x435  Stepping=5
 >   Features=0x3<FPU,VME>
 > 
 > >From my 3.2-RELEASE sources (specifically, src/sys/i386/i386):
 > 
 > ---
 > #if defined(I486_CPU) || defined(I586_CPU) || defined(I686_CPU)
 >         if(*cpu_vendor)
 >                 printf("  Origin = \"%s\"",cpu_vendor);
 >         if(cpu_id)
 >                 printf("  Id = 0x%x", cpu_id);
 > 
 > 	.
 > 	.	
 > 	.
 > 
 >         /* Avoid ugly blank lines: only print newline when we have to.
 > */
 >         if (*cpu_vendor || cpu_id)
 >                 printf("\n");
 > 
 > #endif
 > ---
 > 
 > This section of code has been updated but still showed Origin, Id, and
 > etc. back in 2.2.8.
 > 
 > I would think that making sure you have
 > 
 > cpu		"I486_CPU"
 > 
 > in your kernel config would at least get the appropriate information to
 > see why your SX chip isn't being detected correctly.
 > 
 
 
 
 //----------------------------------------------------------------------------
 // Ted Mittelstaedt  - tedm@toybox.placo.com
 // 
 // Just because something CAN be done, doesn't mean that it SHOULD be done.
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message