Date: Thu, 16 Dec 1999 01:08:20 -0800 From: Devin Butterfield <dbutter@wireless.net> To: djb@Wit389306.student.utwente.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA driver problem?? (lost disk contact) Message-ID: <3858AC04.1ACEB813@wireless.net> References: <38588452.3383809C@wireless.net> <199912160729.IAA58142@freebsd.dk> <19991216091950.B8469@relativity.student.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, "Dave J. Boers" wrote: > > On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote: > > It seems Devin Butterfield wrote: > > > I just recently compiled a kernel with the new ATA driver and have > > > discovered a problem: if I run sysinstall, right when it says "probing > > > devices, please wait (this can be a while)" error messages saying... > > [snip] > > > and after printing these messages a number of times, sysinstall will > > > finally come up. If I quit sysinstall and then run it again, probing > > > goes well and there are no timeouts. The interesting thing is that I can > > > reproduce this problem by rebooting and running sysinstall. So, this > > > only happens when running sysinstall for the first time after a boot. > > <snip> > > > > Hmm, I'd put my disks on different channels, but thats just for > > performance sake. I'm currently trying every wierd setup I can > > imagine with the HW I have for testing, but I havn't been able > > to get any of my test setups to exhibit this behavior... > > > > But I'm working on it... > > I am still having "disc contact lost messages" regularly too. I've been > posting about them on several occasions some time ago. [SNIP] > There are two important aspects of the problem: > > 1. The problem does not always occur: it's unpredictable > 2. When it occurs, I can actually hear the disk spinning down and then up > again. > [SNIP] 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? Thanks again! -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3858AC04.1ACEB813>