From owner-freebsd-stable Thu Dec 23 11:40:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E500C1570E for ; Thu, 23 Dec 1999 11:40:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA06281; Thu, 23 Dec 1999 19:45:09 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01331; Thu, 23 Dec 1999 20:25:56 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 20:25:56 +0100 From: Wilko Bulte To: Bjoern Fischer Cc: stable@FreeBSD.ORG Subject: Re: /boot/loader fails to reset AMD K6-II FPU Message-ID: <19991223202556.C1056@yedi.iaf.nl> References: <19991222042320.A749@frolic.no-support.loc> <19991222204703.B833@yedi.iaf.nl> <19991222232741.A1344@frolic.no-support.loc> <19991223001940.C37471@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991223001940.C37471@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Dec 23, 1999 at 12:19:42AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 12:19:42AM +0100, Wilko Bulte wrote: > On Wed, Dec 22, 1999 at 11:27:41PM +0100, Bjoern Fischer wrote: > > On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote: > > [...] > > > > When I reboot the system from the /boot/loader > > > > command line (with `reboot'), the system is > > > > being resetted, the kernel loads and starts, > > > > and when the FPU is being initialized the kernel > > > > traps. > > [...] > > > Works fine on my Asus T2P4 with the same CPU: > > > > > > WKB ~>dmesg | grep -i amd > > > CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) > > > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > > AMD Features=0x80000800 > > > > > > But what date is your -stable? > > > > My stable is as fresh as Dec 20th (per CTM). > > I'll buildworld for the latest -stable (3.4-stable I guess ;-) > and see what happens. Will take a while to do. I'm now at 3.4-stable and things work like before: as a charm. Looks like the BIOS problem suggested before might be the culprit. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message