Date: Mon, 15 Mar 2010 18:21:06 +0100 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Nenhum_de_Nos <matheus@eternamente.info> Cc: freebsd-stable@freebsd.org Subject: Re: ahci errors on 8-stable Message-ID: <4B9E6C82.8050403@omnilan.de> In-Reply-To: <20100308204458.9e0d51a8.matheus@eternamente.info> References: <80587c73d8c5ee56d8890d04179024b8.squirrel@cygnus.homeunix.com> <20100308222653.GA87837@icarus.home.lan> <20100308204458.9e0d51a8.matheus@eternamente.info>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Nenhum_de_Nos schrieb am 09.03.2010 00:44 (localtime): > On Mon, 8 Mar 2010 14:26:53 -0800 > Jeremy Chadwick <freebsd@jdc.parodius.com> wrote: > >> On Mon, Mar 08, 2010 at 06:38:02PM -0300, Nenhum_de_Nos wrote: >>> I've seen these errors in a production machine in deep disk load (scp and >>> bsdtar in heavy use): >> Please provide the output from the following commands: > > As I had huge disk activity when those messages appeared, I did reboot after and now no more are there. I think the vmstat command should be issued when the problem was happening right ? (if so I can run the backup tar's and see what happens). What disks do you use? I have similar timeouts and mav has the hd firmware in mind to be the culprit http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-02/msg00737.html In my case it's the samsung EcoGreen SpinPouint F2 1.5TB, Firmware 1AG01113 and 1AG01118. The disk on ahcich2 (where the timeouts appear) has the newer firmware. -Harry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkuebIMACgkQLDqVQ9VXb8jWKwCeNMN/hPaw7OFBwoPRpR7QWJzH 85EAoIvYrojDlGPLcplmdqoWfOQBHxMh =VAL8 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B9E6C82.8050403>