Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756654AbaD1TYk (ORCPT ); Mon, 28 Apr 2014 15:24:40 -0400 Received: from mail-ve0-f180.google.com ([209.85.128.180]:63627 "EHLO mail-ve0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754630AbaD1TYj (ORCPT ); Mon, 28 Apr 2014 15:24:39 -0400 MIME-Version: 1.0 In-Reply-To: <201404281922.19399.linux@rainbow-software.org> References: <201404281303.24977.linux@rainbow-software.org> <57283945f737477b90e5ae31b9403799@fmsmsx156.amr.corp.intel.com> <1398703903.97992.10.camel@djiang5-desk1.amr.corp.intel.com> <201404281922.19399.linux@rainbow-software.org> Date: Mon, 28 Apr 2014 12:24:38 -0700 Message-ID: Subject: Re: 3.2.57 regression: isci driver broken: Unable to reset I T nexus? From: Dan Williams To: Ondrej Zary Cc: "Jiang, Dave" , "Paszkiewicz, Artur" , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Ben Hutchings Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [ adding Ben ] On Mon, Apr 28, 2014 at 10:22 AM, Ondrej Zary wrote: > On Monday 28 April 2014 18:51:44 Jiang, Dave wrote: >> On Mon, 2014-04-28 at 16:28 +0000, Ondrej Zary wrote: >> > On Monday 28 April 2014 17:50:29 Jiang, Dave wrote: >> > > On Mon, 2014-04-28 at 13:03 +0200, Ondrej Zary wrote: >> > > > Hello, >> > > > just upgraded a server running 3.2.54-2 to 3.2.57-3 (Debian Wheezy) >> > > > and it does not boot anymore because of isci driver breakage. >> > > >> > > I would not run anything less than 3.8 for the isci controller. 3.2 is >> > > VERY old for that particular driver and likely very unstable. The >> > > product version of that driver plus libsas started with 3.8. Also I'm >> > > concerned that you aren't using the platform OEM parameters. You need >> > > to turn your OROM or EFI driver on for the SAS controller. >> > >> > It's a Cisco UCS C22 M3 server with a crappy LSI fakeraid that cannot >> > even be disabled. It was a pain to make it boot properly - had to use >> > dmraid. But it has been working fine since then (2012). Until now. >> >> Yes but just because it has been working doesn't mean it is a good idea >> to run unstable code.... You need the driver updates and the libsas >> updates for it to function properly. Does this fail on 3.14? If it is >> that patch I have a feeling it may be interacting badly with whatever is >> was in 3.2 libsas that may not be a problem with latest kernels.... It >> is odd to see all those hard resets however.... Did you have them when >> it was working for you? > > Didn't know that it was unstable - it worked with no problems, better than > some products marked as stable :) > 3.13 works fine - I've installed it from wheezy-backports to work-around the > bug. > > The log from working 3.2.54 is below (at the end) - there's one reset for each > port. > I think the right answer for 3.2 is to drop commit 584ec1226519 "isci: fix reset timeout handling". libsas and its libata interaction went through significant overhaul after 3.2 so it's not surprising that a change to reset handling regresses like this. Ideally there would be a backport of latest libsas available for 3.2, but no one to my knowledge is working on that. -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/