From owner-freebsd-hackers Mon Aug 25 21:21:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05175 for hackers-outgoing; Mon, 25 Aug 1997 21:21:23 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05135 for ; Mon, 25 Aug 1997 21:21:09 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id VAA21878 for ; Mon, 25 Aug 1997 21:21:04 -0700 (PDT) Message-Id: <199708260421.VAA21878@dragon.awen.com> From: "Mike Burgett" To: "hackers@freebsd.org" Date: Mon, 25 Aug 97 21:21:03 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: special malloc needs... Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 26 Aug 1997 13:22:50 +0930, Mike Smith wrote: >It's almost guaranteed that either there is a hidden agenda (and I hate >it when people don't explain their stupid questions), or the individual >in question doesn't understand what they're asking. > >So Mike, what is it? Well, it doesn't really matter if it can't be done, does it? There's some speculation about the K6 problems that have been seen, being a L1 cache bug that can occur when addressing memory exactly 32M apart. Just wanted to try a diagnostic, to see if it can be provoked, without hacking into the kernel. Sorry 'bout the stupid question. --Mike