From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: adam radford <aradford@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: Re: stuck in megaraid_sas.c megasas_adp_reset_gen2
Date: Wed, 11 Apr 2012 15:44:27 -0600 [thread overview]
Message-ID: <201204111544.27866.thomas@fjellstrom.ca> (raw)
In-Reply-To: <CAHtARFERLPA345Qsp=-_+5BGAdOrLaJ+HLGzqENBFNRXNJMDhg@mail.gmail.com>
On Wed Apr 11, 2012, adam radford wrote:
> On Wed, Apr 11, 2012 at 1:17 PM, Thomas Fjellstrom <thomas@fjellstrom.ca>
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
No problem.
Things are quite similar. Startup goes like:
<detected a onboard sata ports>
scsi: waiting for bus probes to complete...
Refined TSC...
Switched to clocksource tsc
<pause here>
udevd[...]: timeout: killing '/sbin/modprobe -b ...' (lots of these, so much
that I hit scroll lock so I can see the kernel messages as they come up)
scsi 0:0:0:0: megasas: RESET cmd=12 retries=0
megasas: [ 0] waiting for 1 commands to complete
(many more waiting messages)
<hung task kworker/u:4>
Call Trace:
[<ffffffff810641d0>] ? async_synchronize_cookie_domain+0xb2/...c
[<ffffffff8105f583>] ? add_wait_queue+0x3c/0x3c
....
megasas: [55] waiting for 1 commands to complete
....
megasas: [175] waiting for 1 commands to complete
megasas: moving cmd[0]:ffff880234bcb940:0:ffff88002339beec0 the defer queue as
internal
megaraid_sas: FW detected to be in faultstate, restarting it...
ADP_RESET_GEN2: HostDiag=a0
(10s wait)
megaraid_sas: FW restarted successfully,initializing next stage...
megaraid_sas: HBA recovery state machine,state 2 starting...
(30s wait)
megasas: Waiting for FW to come to ready state
megasas: FW now in ready state
megaraid_sas: command ffff880234bcb940, ffff8802339beec0:0detected to be pending
while HBA reset
megasas: ffff880234bcb940 scsi cmd [12]detected on the internal queue, issue
again.
megasas: reset successful
scsi: 0:0:0:0: megasas: RESET cmd=12 retries 0
megaraid_sas: no pending cmds after reset
megasas: reset successful
(20s wait)
(device offlined message here, missed it this time)
(detected all sata devices)
And it stalled there.
> -Adam
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next prev parent reply other threads:[~2012-04-11 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 23:16 stuck in megaraid_sas.c megasas_adp_reset_gen2 Thomas Fjellstrom
2012-03-21 23:36 ` adam radford
2012-03-21 23:52 ` Thomas Fjellstrom
2012-04-11 20:17 ` Thomas Fjellstrom
2012-04-11 20:57 ` adam radford
2012-04-11 21:44 ` Thomas Fjellstrom [this message]
2012-04-12 8:11 ` adam radford
2012-04-12 18:16 ` Thomas Fjellstrom
2012-04-13 18:50 ` Thomas Fjellstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201204111544.27866.thomas@fjellstrom.ca \
--to=thomas@fjellstrom.ca \
--cc=aradford@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.