Date: Thu, 13 Jan 2011 10:04:32 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Joachim Tingvold <joachim@tingvold.com> Cc: freebsd-scsi@FreeBSD.org Subject: Re: mps0-troubles Message-ID: <4D2EB210.1050103@FreeBSD.org> In-Reply-To: <B2CFC8A1-FA1D-4718-99C3-AC3430A905C2@tingvold.com> References: <mailpost.1294832739.2809102.16331.mailing.freebsd.scsi@FreeBSD.cs.nctu.edu.tw> <4D2DAA45.30602@FreeBSD.org> <B2CFC8A1-FA1D-4718-99C3-AC3430A905C2@tingvold.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Joachim Tingvold wrote: > On Wed, Jan 12, 2011, at 14:19:01PM GMT+01:00, Alexander Motin wrote: >> dmesg you've shown shown many command timeouts on multiple devices. As >> soon as default ATA timeout is about 30 seconds - it may cause >> significant delays before recovery sequence will manage it. That could >> result in delays you observed. > > I let the computer stay on for about 7-8 hours after I sent my previous > email, and it was still frozen. I had to physically reset the computer > to get it operational again. > >> What's more suspicious is that timeouts happened same time on >> AHCI-attached disk and several disks on mps controller. I can hardly >> assume that two completely different controllers and drivers triggered >> some unrelated problems simultaneously. > > If I were copying from the AHCI-attached disk to the mps controller, and > the AHCI-attached disk timeouts, wouldn't this cause the disks on the > mps controller to timeout as well? No. Timeout means that disk doesn't respond to request. If you just stuck on AHCI disk -- mps disks should be just idle. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D2EB210.1050103>