From owner-freebsd-bugs  Sun May 21 11:48:10 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA25598
          for bugs-outgoing; Sun, 21 May 1995 11:48:10 -0700
Received: from kithrup.com (kithrup.com [140.174.23.40])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA25592
          for <freebsd-bugs@FreeBSD.org>; Sun, 21 May 1995 11:48:09 -0700
Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id LAA13914; Sun, 21 May 1995 11:47:44 -0700
Date: Sun, 21 May 1995 11:47:44 -0700
From: Sean Eric Fagan <sef@kithrup.com>
Message-Id: <199505211847.LAA13914@kithrup.com>
To: bde@zeta.org.au, davidg@Root.COM, freebsd-bugs@FreeBSD.org,
        tege@cygnus.com
Subject: Re: MAJOR problem with FreeBSD-2.0-RELEASE
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>There have been several reports that bounce buffering is broken.  The bt
>driver always enables bounce buffering, although this at best wastes time
>on non-ISA systems.

Some more information:

the system has a Quantum 4.1GByte drive on it (one of the Grand Prix,
supposedly, although it apparantly identifies itself as a slightly different
model).

I just tried running a kernel without bounce buffers, without an ed0 driver,
and with MAXMEM set to 16384.  I booted, and then tried to build bash by

	cd /usr/src/local/bash*
	make

It first gave a warning/error message from the buslogic driver, saying
something about there being more than 33 mbxs (I think it was); there was
then a message from the scsi code saying "oops" something wasn't queued.
The system then got a kernel page fault, and paniced.

Before that, with slightly different kernels, I'd noticed that

	cd /sys/i386/conf
	vi TEGE

would get the buslogic warnings/errors, and vi would come up with an empty
file, or core dump.  If, however, I did

	vi
	:e TEGE

it would work.

I think he is going to install Linux.  This is the second motherboard he's
been unsuccessful in running FreeBSD-2.0 on.

Sean.