From owner-freebsd-current Sun Jan 17 19:53:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03709 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:53:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtpott1.nortel.ca (smtpott1.nortel.ca [192.58.194.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03684 for ; Sun, 17 Jan 1999 19:53:31 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zcars01t by smtpott1; Sun, 17 Jan 1999 22:52:57 -0500 Received: from wmerh01z.ca.nortel.com by zcars01t; Sun, 17 Jan 1999 22:52:22 -0500 Received: from hcarp00g.ca.nortel.com (atrens@hcarp00g.ca.nortel.com@wmerh01z) by wmerh01z.ca.nortel.com with ESMTP (8.7.1/8.7.1) id WAA21901; Sun, 17 Jan 1999 22:52:22 -0500 (EST) Date: Sun, 17 Jan 1999 23:01:38 -0500 (EST) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Problems with new IDE's & -current In-Reply-To: <36A24D5E.F1875A83@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Jan 1999, Karl Pielorz wrote: Karl, Let's see your (dmesg) probe messages ... :) they may shed some light on what's happening. I don't claim to be an expert on wd.c but from what I can tell it seems that controller and drive capabilities are probed separately, its conceivable you've hit upon an untested code path. ide_pci.c has been changing a lot lately (probably four times in the last seven days) - after capturing your dmesg output, try a fresh kernel and look for differences in probed controller/drive capabilities... Andrew. +----------------------------------------------------+ = Andrew Atrens - Nortel Networks (atrens@nortel.ca) = = P.O. Box 3511, Station C Ottawa, Canada = = = = All opinions expressed are mine, not Nortel's. = +----------------------------------------------------+ -- > Date: Sun, 17 Jan 1999 20:51:42 +0000 > From: Karl Pielorz > To: current@FreeBSD.ORG > Subject: Problems with new IDE's & -current > > Hi, > > I have a system that's meant as a 'backup disk spool' - it has a 2Gb SCSI > drive to boot from, and then 2 x 16Gb IDE drives (IBM-DTTA-351680's). > > The system works fine so long as I stick to using the SCSI drives... If I use > the IDE's (e.g. backup another machine to them, tar / untar 'usr/src' to them) > I start getting problems, > > e.g. > > Jan 14 13:01:42 magpie /kernel: wd0: interrupt timeout: > Jan 14 13:01:42 magpie /kernel: wd0: status 58 error 0 > Jan 15 17:56:52 magpie /kernel: lnc0: Missed packet -- no receive buffer > Jan 15 17:57:43 magpie /kernel: lnc0: Missed packet -- no receive buffer > > The machine also has an NE-2100 embedded network card. We have 4 other > identical machines to this, all SCSI based - all work without any problems... > > Is there anything that can be done? - at a guess I'd say the IDE's/wcd0 are > timing out on interrupts, which is then stuffing the network (as the systems > been waiting around too long for wcd0's IRQ's?)... > > The machine is a dual P90 (running SMP) - I get the problems even with a > single CPU kernel... It's running Neptune chipset (quite old) - and only has 1 > IDE channel. > > Any pointers? - The drives do appear to work OK, i.e. no corruption, but the > _whole_ machine appears to 'stall' when the above occurs = not good... :-( > > I've tried 3.0-Release and 3.0-Current as of 7th Jan, '99 - Both exhibit > identical symptoms... > > -Kp > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message