From owner-freebsd-hardware Fri Nov 8 14:24:04 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14078 for hardware-outgoing; Fri, 8 Nov 1996 14:24:04 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA14059 for ; Fri, 8 Nov 1996 14:23:50 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA27828 (5.67b/IDA-1.5 for ); Fri, 8 Nov 1996 23:23:32 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.2/8.6.9) id XAA04916; Fri, 8 Nov 1996 23:23:28 +0100 (MET) Message-Id: <199611082223.XAA04916@x14.mi.uni-koeln.de> Date: Fri, 8 Nov 1996 23:23:27 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: jacs@gnome.co.uk (Chris Stenton) Cc: hardware@freebsd.org Subject: Re: ncro 810 oops error In-Reply-To: ; from Chris Stenton on Nov 5, 1996 12:03:55 +0000 References: X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chris Stenton writes: > > > I have recently upgraded to a Asus Pentium PRO Motherboard with their > NCR810 SCSI controller. While using the Amanda backup programme I am > getting a large number of errors from the controller. > > They are of the form. > > Nov 5 11:51:35 hawk /kernel: ncr?: scatter/gather failed (residue=493925376). A request to transfer some 500MB of data was issued to the driver. The scatter/gather table covers only 64KB, your memory perhaps 32MB or 64MB, so the call can't be satisfied :) The driver can't do anything about this, the parameters it receives are invalid. > They only seem to happen when it is backing up partitions other than > the root partition. > I have tried putting the Tape drive on a second controller but it made > no difference. I did not have this problem with my GigaByte Neptune > board using their NCR810 controller. This is not a hardware or controller specific problem (IMHO). You could have some file system corruption, that leads to this problem, or there could be a kernel problem (eg. missing lock). Please try a FSCK on your partitions first, and if you don't find anything, then build a kernel with a current version of /sys/pci/ncr.c. It contains some diagnostic code, which I thought might help find the cause of the out-of-bound parameter being passed ... Regards, STefan