From owner-freebsd-current Thu Dec 16 1:41:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 464EC14FE2 for ; Thu, 16 Dec 1999 01:41:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA89041; Thu, 16 Dec 1999 10:41:35 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912160941.KAA89041@freebsd.dk> Subject: Re: ATA driver problem?? (lost disk contact) In-Reply-To: <3858AC04.1ACEB813@wireless.net> from Devin Butterfield at "Dec 16, 1999 01:08:20 am" To: dbutter@wireless.net (Devin Butterfield) Date: Thu, 16 Dec 1999 10:41:35 +0100 (CET) Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Devin Butterfield wrote: > That's interesting...In my case it is quite easily reproduced (very > predictable). All I have to do is reboot and then run sysinstall and > when it probes the devices the disks time out. So far I have not been > able to get this behavior at any other time. > > I should also note that it repeatedly try's "resetting devices...done." > many times (number of times it does this varies). > > Soren, since the problem is reproducible in my case, can you think of > anything else I can try to help shed some light on what might be causing > these time-outs we are having? Hmm, does the problem persist if you increase the timeout in ata-disk.c to some too big value, like 100 secs or so?? If so, there is something causing the timeout function to be called without a real timeout. This could be the problem, I just dont see how that would be possible... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message