From owner-freebsd-current Thu Jan 20 21:26: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DD9414C18 for ; Thu, 20 Jan 2000 21:26:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA56373; Thu, 20 Jan 2000 21:16:56 -0800 (PST) (envelope-from dillon) Date: Thu, 20 Jan 2000 21:16:56 -0800 (PST) From: Matthew Dillon Message-Id: <200001210516.VAA56373@apollo.backplane.com> To: Peter Wemm Cc: arnee , current@FreeBSD.ORG, Gerald Abshez Subject: Re: ...(file transfer crashes system) ethernet driver or IP stack bug? References: <20000121050838.165DE1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Hmm. If possible I would try backing away from the ata driver entirely :> and going back to the 'wd' driver. This isn't to say that the ata :> driver is the problem, but it *could* be the problem. A number of peopl : e :> have had problems with the ata driver. There isn't anything else in your :> config that strikes a chord... the rest of it looks ok to me. : :Not possible. the wd driver doesn't support the Promise ATA-66 controllers :that he is using. : :Cheers, :-Peter Fubar. The crashes are occuring all over the place -- ip_input, ffs_blkfree, ip_output. Maybe it's a BIOS configuration problem... perhaps the ram is configured to be too fast or something like that. I don't know. This has all the earmarks of overclocking or a memory problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message