From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 16:17:02 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 801631065675 for ; Mon, 26 Jul 2010 16:17:02 +0000 (UTC) (envelope-from staale@kristoffersen.ws) Received: from mail-forward.uio.no (mail-forward.uio.no [129.240.10.42]) by mx1.freebsd.org (Postfix) with ESMTP id 00D428FC24 for ; Mon, 26 Jul 2010 16:17:01 +0000 (UTC) Received: from mail-mx2.uio.no ([129.240.10.30]) by pat.uio.no with esmtp (Exim 4.67) (envelope-from ) id 1OdQMO-00005w-DT for freebsd-current@freebsd.org; Mon, 26 Jul 2010 18:17:00 +0200 Received: from putsch.kolbu.ws ([158.36.191.193]) by mail-mx2.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1OdQMN-0001s0-V9 for freebsd-current@freebsd.org; Mon, 26 Jul 2010 18:17:00 +0200 Received: from chiller by putsch.kolbu.ws with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OdQMN-000DZ3-Kn for freebsd-current@freebsd.org; Mon, 26 Jul 2010 18:16:59 +0200 Date: Mon, 26 Jul 2010 18:16:59 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: freebsd-current@freebsd.org Message-ID: <20100726161659.GB64981@putsch.kolbu.ws> References: <20100715160048.GA61891@alchemy.franken.de> <20100715175225.GA52693@putsch.kolbu.ws> <20100716103125.GA73878@putsch.kolbu.ws> <20100718122022.GW4706@alchemy.franken.de> <20100719170654.GA19889@putsch.kolbu.ws> <20100720101736.GD4706@alchemy.franken.de> <20100720115528.GA88965@putsch.kolbu.ws> <4C45938B.8000604@stillbilde.net> <20100721163311.GA45556@putsch.kolbu.ws> <4C473F2F.8000206@stillbilde.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4C473F2F.8000206@stillbilde.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 410DE942B254F8E89E5CACCB3CFC7F777960D3A6 X-UiO-SPAM-Test: remote_host: 158.36.191.193 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 1877 max/h 13 blacklist 0 greylist 0 ratelimit 0 Subject: Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2010 16:17:02 -0000 On 2010-07-21 at 20:40, Svein Skogen (Listmail account) wrote: > On 21.07.2010 18:33, Ståle Kristoffersen wrote: > > I -might- have solved my problem. It has now ran for 24h without timeouts, > > and with a bit of load on it. I think I might have ran into the seagate + > > NCQ-problem, even tho seagate's webpage told me my drives was not affected > > (according to the serial numbers). I did however update the following > > num drives firmware > > 6x ST31000340AS SD15 > > 4x ST31500341AS SD17 > > I have 8 of the last type (31500341AS) mine running on CC1H firmware, > connected to my MFI. Not a single glitch so far. I also have 8 of those :) Part of my problem is that they are all connected to a sas expander, and when one drive gets in trouble everything is reset, so I can't see which drives is causing the problems. Thats why I flashed every drive I could find an update for. > > to firmware SD1B (old SD17) and SD1A (old SD15), and that looks like it has > > done the trick. I'll report back in a week or so if the problem has not > > reappeared. > > Hope it's fixed for you. I'm still keeping an eye on the MPT code to see > if someone changes something that CAN be affecting my timeout > issues/reset, and if I see something promising, I'm willing to dump out > the entire server to tapes, and test run (I have sufficient spare tapes > to actually test without losing data), but such a job will take me a > week to prepare, and another to test. Quite a bit of time for something > that "may" solve my problem... ;) It still runs fine now after 6 days, so I'm optimistic :) Not a single timeout. Good luck with your tape drive. -- Ståle Kristoffersen