From owner-freebsd-bugs Fri Jan 5 15:08:48 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA09273 for bugs-outgoing; Fri, 5 Jan 1996 15:08:48 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA09258 for ; Fri, 5 Jan 1996 15:08:38 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.6.12/8.6.4) with ESMTP id BAA12642; Sat, 6 Jan 1996 01:08:24 +0200 Received: (hsu@localhost) by katiska.clinet.fi (8.7.3/8.6.4) id BAA05016; Sat, 6 Jan 1996 01:08:31 +0200 (EET) Date: Sat, 6 Jan 1996 01:08:31 +0200 (EET) Message-Id: <199601052308.BAA05016@katiska.clinet.fi> From: Heikki Suonsivu To: se@zpr.uni-koeln.de (Stefan Esser) Cc: freebsd-bugs@freebsd.org In-reply-to: se@zpr.uni-koeln.de's message of 4 Jan 1996 13:13:41 +0200 Subject: Re: kern/929: NCR support broken? Organization: Clinet Ltd, Espoo, Finland References: <199601041005.AA15056@Sysiphos> Sender: owner-bugs@freebsd.org Precedence: bulk On Jan 4, 6:12, Heikki Suonsivu wrote: } } Jan 3 11:18:53 katiska /kernel: ncr?: scatter/gather failed (residue=814260224) } A request to read 800MB of data has been } issued, but there was no way to setup a } In that case this should generate a panic, not an error message ? Don't think that the driver should panic in that situation in general ... If kernel requests a read which is larger than physical memory, it can be pretty sure something in the kernel is seriously confused. And if a kernel is seriosly confused, anything, including filesystem corruption, may occur. I stick with my words, anything like this is a panic situation. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi work +358-0-4375209 fax -4555276 home -8031121