From owner-freebsd-current Tue Jul 9 23:38: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1788E37B408; Tue, 9 Jul 2002 23:37:59 -0700 (PDT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01F3D43E31; Tue, 9 Jul 2002 23:37:57 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id g6A6aTS26584; Wed, 10 Jul 2002 16:06:29 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Wed, 10 Jul 2002 16:07:39 +0930 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id QAA22763; Wed, 10 Jul 2002 16:04:27 +0930 (CST) Received: by salex001.dsto.defence.gov.au with Internet Mail Service (5.5.2653.19) id ; Wed, 10 Jul 2002 16:04:41 +0930 Message-ID: <108E7D907871D6118B5000306E0189F8575893@ednex504.dsto.defence.gov.au> From: "Thyer, Matthew" To: "'Peter Wemm'" Cc: "'FreeBSD-CURRENT'" Subject: Re: Remember my ill-fated i386 smp pmap optimizations? Date: Wed, 10 Jul 2002 16:04:32 +0930 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > John Baldwin wrote: > > > > On 08-Jul-2002 Peter Wemm wrote: [snip] > > > Excuse me while I go outside and shoot myself. > > > > Hahahaha! > > > > Glad to see you have fixed them. :) > > Unfortunately, there are still more problems. :-( > > I have found some of them. And what is really scary is that I have > verified that some of what Terry has been FUD'ing(*) about for our TLB > (mis)management is actually correct. :-( We have code that simply will not > work (ie: vm86 will explode when doing VESA calls) if certain accidental > conditions that mask the bugs no longer occur. Probably why my Pentium-III 866 locks up (with a continuous beep from the PC speaker) when I switch virtual consoles (no X running) when doing disk I/O and one console is running the standard 80x25 and the other is running 132x60. Seems to happen every time so far and has done so for several months. It doesn't happen on my Celeron 450 Slot-1 (actually a 300a running at 100Mhz FSB instead of 66MHz) with an Nvidia TNT2 16MB, Western digital something 20GB also using 80x25 and 132x60. (also GENERIC kernel and v.new -CURRENT). The P-III 866 has an Nvidia GeForce2 MX400 64MB, IBM 120GXP 40GB drive, very new -CURRENT and GENERIC kernel. extract of /boot/loader.conf has: hw.ata.wc="1" hw.ata.tags="1" <----------- This line not on the Celeron 450 box as vesa_load="YES" the WD drive cant do tagged command queing extract of /etc/rc.conf has: font8x16="cp437-8x16.fnt" font8x14="cp437-8x14.fnt" font8x8="cp437-8x8.fnt" -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Edinburgh PO Box 1500 EDINBURGH South Australia 5111 IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message