From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761265Ab2DKU5Y (ORCPT ); Wed, 11 Apr 2012 16:57:24 -0400 Received: from mail-we0-f174.google.com ([74.125.82.174]:60615 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761200Ab2DKU5X (ORCPT ); Wed, 11 Apr 2012 16:57:23 -0400 MIME-Version: 1.0 In-Reply-To: <201204111417.28893.thomas@fjellstrom.ca> References: <201203211716.45418.thomas@fjellstrom.ca> <201203211752.05576.thomas@fjellstrom.ca> <201204111417.28893.thomas@fjellstrom.ca> Date: Wed, 11 Apr 2012 13:57:21 -0700 Message-ID: Subject: Re: stuck in megaraid_sas.c megasas_adp_reset_gen2 From: adam radford To: thomas@fjellstrom.ca Cc: lkml , linux-scsi@vger.kernel.org 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 On Wed, Apr 11, 2012 at 1:17 PM, Thomas Fjellstrom wrote: >> >> ADP_RESET_GEN2: HostDiag=a0 >> >> followed by a bunch of: >> >> RESET_GEN2: retry=%x, hostdiag=a4 >> >> Now I'm not sure the hostdiag should be different between the two. if this >> aN identifier is similar to the aN identifiers in the MegaCli tool, then >> it would mean its trying to reset a device that doesn't exist? I only have >> a single M1015 card installed. host diag register output a0 or a4 has absolutely nothing to do with MegaCli -aN command line argument for specifying adapter number. > I just got a second M1015 card in today and gave it a go. Similar issues, > different log messages. (hand typed from picture taken of screens) > > Lots of: > > megasas: Waiting for 1 commands to complete Can you try booting with kernel command line argument pcie_aspm=off -Adam