Date: Wed, 17 Mar 2010 13:30:59 +0100 From: Kai Gallasch <gallasch@free.de> To: Alexander Motin <mav@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org, Pawel Jakub Dawidek <pjd@FreeBSD.org> Subject: Re: proliant server lockups with freebsd-amd64-stable (2010-03-10) Message-ID: <20100317133059.51245776@orwell.free.de> In-Reply-To: <20100312222659.0198dd03@orwell.free.de> References: <20100311133916.42ba69b0@orwell.free.de> <20100312115028.GG1819@garage.freebsd.pl> <4B9A8A27.8050608@FreeBSD.org> <20100312222659.0198dd03@orwell.free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am Fri, 12 Mar 2010 20:38:31 +0200 > schrieb Alexander Motin <mav@FreeBSD.org>: > > > Pawel Jakub Dawidek wrote: > > > On Thu, Mar 11, 2010 at 01:39:16PM +0100, Kai Gallasch wrote: > > >> I have some trouble with an opteron server locking up > > >> spontaneously. It looses all networks connectivity and even > > >> through console I can get no shell. > > >> > > >> Lockups occur mostly under disk load (periodic daily, bacula > > >> backup running, make buildworld/buildkernel) and I can provoke > > >> them easily. > > > [...] > > >> 4 0 0 0 LL *cissmtx 0xffffff04ed820c00 > > >> [g_down] > > > [...] > > >> 100046 L *cissmtx 0xffffff04ed820c00 > > >> [irq257: ciss0] > > > [...] > > > > > > I was analizing similar problem as potential ZFS bug. It turned > > > out to be bug in ciss(4) and I believe mav@ (CCed) has fix for > > > that. > > > > That my patch is already at 8-STABLE since r204873 of 2010-03-08. > > Make sure you have it. Rebuilding the kernel with your 8-STABLE commited ciss patch seems to have resolved this issue. Server now has an uptime of 5 days and survives under high filesystem load. Alexander, thanks for fixing ciss. Kai. -- Da das Pferd pfluegt, lasst uns den Esel satteln.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100317133059.51245776>