Date: Thu, 4 Jan 1996 11:05:53 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: Heikki Suonsivu <hsu@clinet.fi> Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: kern/929: NCR support broken? Message-ID: <199601041005.AA15056@Sysiphos> In-Reply-To: Heikki Suonsivu <hsu@clinet.fi> "Re: kern/929: NCR support broken?" (Jan 4, 6:12)
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 4, 6:12, Heikki Suonsivu wrote: } Subject: Re: kern/929: NCR support broken? } } In article <199601031822.AA02901@Sysiphos> se@zpr.uni-koeln.de (Stefan Esser) writes: } } Subject: kern/929: NCR support broken? } } } Jan 3 11:18:53 katiska /kernel: ncr?: scatter/gather failed (residue=814260224) } } This is a bug in the higher level code. } } A request to read 800MB of data has been } issued, but there was no way to setup a } scatter/gather table for that transfer } (and I doubt you had had the RAM to stuff } away the data read :) } } 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 ... It just returns a failure code, and if success was vital, then the kernel can decide to panic. But if this might help diagnose the problem, then a panic might be useful just for testing purposes (and you could add it yourself, BTW). (I could send a patch, too, if you have trouble to locate the right place to apply it ...) If I remember right, some consistency checking code has been added to some VM functions to catch this (???) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601041005.AA15056>