Date: Mon, 26 Jul 2010 18:16:59 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen <staale@kristoffersen.ws> To: freebsd-current@freebsd.org Subject: Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm Message-ID: <20100726161659.GB64981@putsch.kolbu.ws> In-Reply-To: <4C473F2F.8000206@stillbilde.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-07-21 at 20:40, Svein Skogen (Listmail account) wrote: > On 21.07.2010 18:33, Ståle Kristoffersen wrote: <snip> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100726161659.GB64981>