From owner-freebsd-scsi Sun Jun 1 23:05:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29188 for freebsd-scsi-outgoing; Sun, 1 Jun 1997 23:05:58 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29183 for ; Sun, 1 Jun 1997 23:05:55 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA18904 for ; Mon, 2 Jun 1997 08:05:56 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id IAA02179 for freebsd-scsi@freebsd.org; Mon, 2 Jun 1997 08:10:20 +0200 (MEST) Date: Mon, 2 Jun 1997 08:10:20 +0200 (MEST) From: Christoph Kukulies Message-Id: <199706020610.IAA02179@gil.physik.rwth-aachen.de> To: freebsd-scsi@freebsd.org Subject: ncr timeout - command already dequeued... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I posted the exact message already in hackers over the weekend: I'm getting spurious timeouts once every couple of days, sometimes within 24 hours. Symptom is that the whole system hangs - no disk access possible anymore. It is a system with two ncr/PCI controllers, now exchanged the cheapo ones against SC200 (ASUS) - no change. MB is a Chaintech, AmdK5/PR133, 64MB, 3GB+3GB Quantum Tempest (slow) wired to a 6GB ccd drive. I wonder if either, the two controller situation or the fact that ccd is running upon it leads to this weird behaviour or if the cause is in some other hardware component. I will be exchanging the MB this week but I'm posting this also here just in case someone else might have an idea if the culprit might be in either the ncr code or the scsi driver. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de